Hello Jacques!
The Axis2 Ofbiz Component is simply an Ofbiz Component that has:
1. Axis2 1.4 Distribution stored in a subdirectory.
2. The Ofbiz build system is connected to Axis2 build system via an Ant
build.xml file
3. A java file that is a Web Services Facade to Ofbiz Services that want to
be exported.
So, the only code that need to be published is:
1. The java file that is a Web Services Facade to Ofbiz Services that want
to be exported.
This file contains simply a Java Class that has 1 wrapper method for
each Ofbiz Service that want to be exported. Axis2 does the job of exporting
java methods as WebServices. It's amazing!
2. The build.xml of the component that builds the java file and puts the
class file in an specific Axis2 directory
The Ofbiz community may consider to include this ready to use Axis2 Ofbiz
component that includes Axis2 Distribution and some Ofbiz Services exported
via SOAP as an example of use.
So, in this case the JIRA issue could be an idea more than code changes of
existing Ofbiz code?
How can I publish this idea as a JIRA issue?
If the community thinks that is a good idea, then I will be glad to provide
an example code (for instance 2 Ofbiz services that use complex types
exported via SOAP), the build.xml and the documentation. The example code
will be a java file that exports two Ofbiz Services that come with Ofbiz
Distribution (now I'm exporting customer specific Ofbiz Services, that is
why It's nonsense to publish this java file.)
Regards,
Alfredo
jacques.le.roux wrote:
>
> Hello Alfredo,
>
> Did you create a such Axis2 component ? If yes couls you think about
> creating a Jira issue and submit a patch ?
>
> Thanks
>
> Jacques
>
> From: "Alfredo Rueda" <[email protected]>
>>
>> Hello Dhruv!
>>
>> A collection of Ofbiz services have been exposed as Web Services using
>> this
>> solution:
>>
>> http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP
>>
>> These Web Services have been deployed in a production environment and are
>> working perfectly fine.
>>
>> I suggest you to follow the steps, and I will be glad to help you if you
>> run
>> into trouble at some point in the process.
>>
>> Once you finish you can create your own Axis2 Ofbiz Component to provide
>> a
>> cleaner solution. This Axis2 Ofbiz Component will serve as a Web Service
>> Facade to comunicate Ofbiz with other systems.
>>
>> Regards,
>>
>> Alfredo Rueda
>>
>>
>> Dhruv Datta wrote:
>>>
>>> Hi Frns,
>>>
>>> I am using "wsimport" tool to read an existing WSDL file of OFBiz
>>> framework and want to generate artifacts. I need these because I am
>>> doing load testing on Web Service and retrieve data like the average
>>> time requierd to obtain the reponse from a webservice.
>>>
>>> So I've following questions:
>>>
>>> 1) How to expose the existing WebServices of the OFBiz ?
>>> 2) What meaningful data will these services provide?
>>>
>>> I am trying to expose a Web Service by using following syntax:
>>>
>>> E:\WSDL>wsimport -d .
>>> http://localhost:8080/webtools/control/SOAPService/cancelScheduledJob?WSDL
>>>
>>> And I am getting following error :
>>>
>>> warning: R2716 WSI-BasicProfile ver. 1.0, namespace attribute not
>>> allowed in doc/lit for soapbind:body: "cancelScheduledJob"
>>> warning: R2716 WSI-BasicProfile ver. 1.0, namespace attribute not
>>> allowed in doc/lit for soapbind:body: "cancelScheduledJob"
>>> error: Invalid wsdl:operation "cancelScheduledJob": its a
>>> document-literal operation, message part must refer to a schema
>>> element declaration
>>>
>>>
>>> Any help would be greatly appreciated.
>>>
>>> Thanks in Advance.
>>>
>>> Dhruv.
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-expose-Web-Service-of-OFBiz---tp22077891p22158082.html
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context:
http://www.nabble.com/How-to-expose-Web-Service-of-OFBiz---tp22077891p22160487.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
