Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
None
Description
Deepal,
Please see enclosed zip that has a sample service with some simple methods and some methods that use complex java beans. There are about 20 TODO/FIXME comments in the ComplexDataTypesComplexDataTypesSOAP11Test also attached. Can you please take a look at these and get them working?
thanks,
dims
Attachments
Attachments
Issue Links
- is related to
-
AXIS2-1561 Java2WSDL generates incorrect WSDL
- Resolved
-
AXIS2-1720 Java2WSDL malfunction (unexpected mep)
- Resolved
-
AXIS2-2661 Mising type for Parent Class in WSDL
- Resolved
-
AXIS2-2713 Invocation target exception invoking String[] element nillable
- Resolved
-
AXIS2-2769 POJO-blocker: auto-generated wsdl does not contain properties of superclasses
- Resolved
-
AXIS2-2772 RPCMessageReceivers' response is invalid in some situations.
- Resolved
-
AXIS2-1580 RPCMessageReceiver returns a subelement that doesn't conform to the WSDL
- Resolved
-
AXIS2-2759 POJO, Axis2, element for Exception defined multiple times in WSDL
- Resolved
-
AXIS2-2775 nullpointer by invoking web service and RPCMessageReceiver problem
- Resolved
- relates to
-
AXIS2-2741 Attachment using org.apache.axis2.rpc.receivers.RPCMessageReceiver is broken
- Resolved
-
AXIS2-2436 Missing ancestor (POJO) properties in SOAP response
- Resolved
-
AXIS2-2464 java.lang.RuntimeException: Unexpected subelement value
- Resolved