Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
-------------------------------------------------------------------------
Key: OFBIZ-3363
URL: https://issues.apache.org/jira/browse/OFBIZ-3363
Project: OFBiz
Issue Type: New Feature
Components: framework
Affects Versions: SVN trunk
Reporter: Chatree Srichart
Fix For: SVN trunk
Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
I change OFBiz's web service API to Axis2.
==Client Engine==
1. XMLSerializer to serialize parameters Map object to XML.
2. create OMElement from XML stream.
3. ServiceClient send SOAP message.
4. get result OMElement.
5. convert XML content in OMElement to results Map object.
==Event Handler==
1. create OMElement from InputStream
2. get service's name
3. XMLSerializer to deserialize parameters XML to Map object
4. call specific service
5. XMLSerializer to serializer service's results Map object to XML
6. create OMElement for service's results
7. send OMElement to response
==Apply Axis2 in OFBiz==
1. apply patch
2. unzip libraries.zip and copy all jar files to framework/service/lib directory
Test SOAP Service
run unit test:
./ant run-single-test -Dtest.component=service -Dtest.case=service-soap-tests
This is a test case that demonstrate service engine can sent both of single
type and complex type
==WSDL==
The testSoap.wsdl file is web service definition language of testSoap service.
Every services require map-Map as type of input/output parameter. In map-Map
consist of key/value pair for service's parameters.
In wsdl:part of wsdl:message has wsdl:documentation which state service's
attribute, consist of
1. name
2. type
3. namespace
4. java-class
5. optional
==WSDL Types==
The types.xsd file is xml schema for complex type
WSDL Types be generated by code. If any one has a better solution please
comment this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
