1. Development of the service side
A. Axis2 does not support transactions. Database additions and deletions are generally required for transaction processing, but in the external interface is not configurable transactions.
Workaround: Either write a proxy class or perform transaction management directly in DAO.
B. Axis2 does not support method overloading.
Method overloads cannot be used in externally published interfaces.
[WARN] We don ' t support method overloading. ignoring [Updateclassifytask]
[WARN] We don ' t support method overloading. ignoring [Updateclassifytask]
[WARN] We don ' t support method overloading. ignoring [Updateclassifytask]
If you write multiple methods with duplicate names, only one is registered in the service.
Workaround: None. Either change to a different method name or find a way to pass the argument.
C. AXIS2 1.4.1 does not support java.util.Date type
Time portion of Java.util.Date is missing from SOAP response in Axis2 1.5
Look at these axis2 bugs, it's too inconvenient to use them.
Although there is a solution on the bug page of Apache's official website, I put dateservuce. The AAR file still reported the same error after examination:
[ERROR] Date string can not is less than charactors
caused by:java.lang.NumberFormatException:date string can not is less than charactors
I do not know what is the meaning of the date is to convert a bit? So depressed--!
AXIS2 1.5 can only return the date part, the time part is lost!
Workaround: Change the date type to string type, which is the safest, but may not match the requirements, should not be considered a good solution.
D. Axis2 cannot pass a data collection of type list.
WORKAROUND: Convert the list to an array type. It's not a problem.
E. Configuring the Axis2 servlet is the time to configure the form as/services/*, because local code already contains the address when generating the local code, can not be manually filled in the address, found that if configured as/erbservices/* this way can not
AXIS2 Development WebService