[jira] Created: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
Locked
[jira] Created: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
 
|
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. |
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: ------------------------------------ Attachment: axis2.diff libraries.zip > 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 > > Attachments: axis2.diff, libraries.zip > > > 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. |
[jira] Assigned: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker reassigned OFBIZ-3363: ---------------------------------- Assignee: Hans Bakker > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip > > > 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. |
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: ------------------------------------ Attachment: types.xsd testSoap.wsdl > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: ------------------------------------ Description: 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. was: 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. > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: ------------------------------------ Attachment: (was: axis2.diff) > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: ------------------------------------ Attachment: axis2.diff Because old version of diff file required demo data for run test. So I upload new version for diff file. The current diff file create ProductCategory and Product value at runtime for send through web service. > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Closed: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker closed OFBIZ-3363. ------------------------------ Resolution: Fixed Thank you Chattree for this contribution: Committed revision 892712. > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793243#action_12793243 ] chris snow commented on OFBIZ-3363: ----------------------------------- Great work Chatree! In the webtools for an exported service, there is a link next to the Exportable lable to show the wsdl. This link opens the wsdl in a textbox. It would be good if there could be a link to open the wsdl directly so that the wsdl url can easily be copy and pasted to other applications. The patch below is not correct, I couldn't remember how to remove the jsessionid when using <@ofbizUrl> so I have hardcoded paths. ### Eclipse Workspace Patch 1.0 #P ofbiz.trunk Index: framework/webtools/webapp/webtools/service/availableservices.ftl =================================================================== --- framework/webtools/webapp/webtools/service/availableservices.ftl (revision 892801) +++ framework/webtools/webapp/webtools/service/availableservices.ftl (working copy) @@ -62,7 +62,9 @@ </tr> <tr> <td class="label">${uiLabelMap.WebtoolsExportable}</td> - <td>${selectedServiceMap.export}<#if selectedServiceMap.export = "True"> (<a href='<@ofbizUrl>${url}?sel_service_name=${selectedServiceMap.serviceName}&show_wsdl=true</@ofbizUrl>'>${uiLabelMap.WebtoolsShowShowWSDL}</a>)</#if></td> + <td> + ${selectedServiceMap.export}<#if selectedServiceMap.export = "True"> (<a href='<@ofbizUrl>${url}?sel_service_name=${selectedServiceMap.serviceName}&show_wsdl=true</@ofbizUrl>'>${uiLabelMap.WebtoolsShowShowWSDL}</a>) + (<a href='/webtools/control/SOAPService/${selectedServiceMap.serviceName}?wsdl'>${uiLabelMap.WebtoolsOpenWSDL}</a>)</#if></td> <td class="label">${uiLabelMap.WebtoolsLocation}</td> <td><a href='<@ofbizUrl>${url}?constraint=location@${selectedServiceMap.location}</@ofbizUrl>'>${selectedServiceMap.location}</a></td> </tr> > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793248#action_12793248 ] chris snow commented on OFBIZ-3363: ----------------------------------- I have tried exposing findPartiesById, but the web service requires authentication. How can I pass in the authentication credentials? Perhaps these parameters could get added to the generated wsdl documentation for the request method? Many thanks, Chris > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793256#action_12793256 ] chris snow commented on OFBIZ-3363: ----------------------------------- I've removed auth="true" from the findPartiesById and I am trying to call the service. I am sending: {code} <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://ofbiz.apache.org/service/"> <soapenv:Header/> <soapenv:Body> <ser:findPartiesById> <map-Map> <ser:map-Entry> <ser:map-Key> <ser:std-String value="idToFind"/> </ser:map-Key> <ser:map-Value> <ser:std-String value="admin"/> </ser:map-Value> </ser:map-Entry> </map-Map> </ser:findPartiesById> </soapenv:Body> </soapenv:Envelope> {code} but I am receiving: {code} <?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><Response><map-Map> <map-Entry> <map-Key> <std-String value="errorMessage"></std-String> </map-Key> <map-Value> <std-String value="Problem processing the service"></std-String> </map-Value> </map-Entry> </map-Map></Response></soapenv:Body></soapenv:Envelope><?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><Response><map-Map> <map-Entry> <map-Key> <std-String value="errorMessage"></std-String> </map-Key> <map-Value> <std-String value="The following required parameter is missing: [IN] [findPartiesById.idToFind] (The following required parameter is missing: [IN] [findPartiesById.idToFind])"></std-String> </map-Value> </map-Entry> </map-Map></Response></soapenv:Body></soapenv:Envelope> {code} Where am I going wrong? Perhaps this could be used as an example in the FAQ? Many thanks... > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
Re: [jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
Hi, Chris Snow
Because XmlSerializer of OFBiz use tag's name for serialize/deserialze. So SOAP xml message don't need prefix for each tag. Can you change your code like this... {code} <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://ofbiz.apache.org/service/"> <soapenv:Header/> <soapenv:Body> <ser:findPartiesById> <map-Map> <map-Entry> <map-Key> <std-String value="idToFind"/> </map-Key> <map-Value> <std-String value="admin"/> </map-Value> </map-Entry> </map-Map> </ser:findPartiesById> </soapenv:Body> </soapenv:Envelope> {code} How do you think about this solution or it should can use prefix in XML message? Thank you Chatree Srichart |
[jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793469#action_12793469 ] Chatree Srichart commented on OFBIZ-3363: ----------------------------------------- Hi, Chris Snow Because XmlSerializer of OFBiz use tag's name for serialize/deserialze. So SOAP xml message don't need prefix for each tag. Can you change your code like this... {code} <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://ofbiz.apache.org/service/"> <soapenv:Header/> <soapenv:Body> <ser:findPartiesById> <map-Map> <map-Entry> <map-Key> <std-String value="idToFind"/> </map-Key> <map-Value> <std-String value="admin"/> </map-Value> </map-Entry> </map-Map> </ser:findPartiesById> </soapenv:Body> </soapenv:Envelope> {code} How do you think about this solution or it should can use prefix in XML message? Thank you > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793567#action_12793567 ] chris snow commented on OFBIZ-3363: ----------------------------------- Hi Chatree, I will try that later - many thanks! By the way, the original message using the "ser" prefix was automatically generated by SoapUI. Do you also have an example of using a service requiring authentication? Many thanks, Chris > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794796#action_12794796 ] chris snow commented on OFBIZ-3363: ----------------------------------- Hi Chatree, Removing the "ser" prefix does work. However, I would expect to be able to use the example request that is generated by SoapUI with the "ser" prefix. Shall I raise this as a bug? Also, do you have an example of calling a service that has auth="true" enabled? Many thanks, Chris > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
[jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794851#action_12794851 ] chris snow commented on OFBIZ-3363: ----------------------------------- An example using authorisation (this should probably go in the wiki FAQ): {code} <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://ofbiz.apache.org/service/"> <soapenv:Header/> <soapenv:Body> <ser:findPartiesById> <map-Map> <map-Entry> <map-Key> <std-String value="idToFind"/> </map-Key> <map-Value> <std-String value="admin"/> </map-Value> </map-Entry> <map-Entry> <map-Key> <std-String value="login.username"/> </map-Key> <map-Value> <std-String value="admin"/> </map-Value> </map-Entry> <map-Entry> <map-Key> <std-String value="login.password"/> </map-Key> <map-Value> <std-String value="ofbiz"/> </map-Value> </map-Entry> </map-Map> </ser:findPartiesById> </soapenv:Body> </soapenv:Envelope> {code} > 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 > Assignee: Hans Bakker > Fix For: SVN trunk > > Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd > > > 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. |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |