A simple SOAP Query?
Locked
 
|
Hey,
I am having real issues with soap. I am not using any complexe data types on my own services, but only strings and integers, so I was hoping that I could rely on the already implemented SOAP component in ofbiz without the need to integrate AXIS2. But even when calling the most simple of all webservices (ping), I am receiving the following error: 2009-04-08 11:08:20,411 (http-0.0.0.0-8080-8) [ RequestHandler.java:326:ERROR] Request SOAPService caused an error with the following message: Fehler beim Aufruf eines Events: org.ofbiz.webapp.event.EventHandlerException: Cannot locate service by name (message) (Cannot locate service by name (message)) So my conclusion is, if I am not mistaken, that the xml document I am sending is not well constructed. I am using the following: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header/> <soapenv:Body> <message>?</message> </soapenv:Body> </soapenv:Envelope> Is that wrong? If so, could anybody parse me a very simple xml document that would qualify for an ofbiz webservice? |
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 from the looks of you errors it is interpreting <message>?</message> as a service name of message then the element must parameterlist (map equivalent) of the service called. take a look at SOAPClientEngine.java it extends GenericAsyncEngine madppiper sent the following on 4/8/2009 2:19 AM: > Hey, > > I am having real issues with soap. I am not using any complexe data types on > my own services, but only strings and integers, so I was hoping that I could > rely on the already implemented SOAP component in ofbiz without the need to > integrate AXIS2. But even when calling the most simple of all webservices > (ping), I am receiving the following error: > > 2009-04-08 11:08:20,411 (http-0.0.0.0-8080-8) [ > RequestHandler.java:326:ERROR] Request SOAPService caused an error with the > following message: Fehler beim Aufruf eines Events: > org.ofbiz.webapp.event.EventHandlerException: Cannot locate service by name > (message) (Cannot locate service by name (message)) > > > So my conclusion is, if I am not mistaken, that the xml document I am > sending is not well constructed. I am using the following: > > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> > <soapenv:Header/> > <soapenv:Body> > <message>?</message> > </soapenv:Body> > </soapenv:Envelope> > > > Is that wrong? If so, could anybody parse me a very simple xml document that > would qualify for an ofbiz webservice? > > Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3HICrP3NbaWWqE4RAsQ9AKDJIj3I2i+lZPRco6g6jpeEtKbMEgCgnPKN nOdGEGdWEMlTcqOG9u7C3Ag= =b5KM -----END PGP SIGNATURE----- |
|
|
Hmm,
well the thing I personally don't understand is that the basic SOAP Interface integrated into OFBiz should work, if not used with complex datatypes, correct? Agreeably the WSDL provided by OFBIz when setting a service to export="true" is not fully WSDL conform, but in theory this should work, right? The ping method is nothing I implemented, but was already existent in the ofbiz trunk and defined as such: <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions targetNamespace="http://ofbiz.apache.org/service/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ofbiz.apache.org/service/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <wsdl:message name="pingRequest"> <wsdl:part name="message" type="xsd:string"/> </wsdl:message> <wsdl:message name="pingResponse"> <wsdl:part name="message" type="xsd:string"/> </wsdl:message> <wsdl:portType name="pingPortType"> <wsdl:operation name="ping"> <wsdl:input message="tns:pingRequest"/> <wsdl:output message="tns:pingResponse"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="pingSoapBinding" type="tns:pingPortType"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="ping"> <soap:operation soapAction=""/> <wsdl:input> <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ofbiz.apache.org/service/" use="literal"/> </wsdl:input> <wsdl:output> <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ofbiz.apache.org/service/" use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="ping"> <wsdl:port binding="tns:pingSoapBinding" name="pingPort"> <soap:address location="http://focworld.nine.ch:8080/webtools/control/SOAPService"/> </wsdl:port> </wsdl:service> </wsdl:definitions> So my xml file should have worked... yet it didn't... Perhaps implementing AXIS2 nonetheless and working all around the problem by creating pojo classes instead is one solution, but I was hoping that since we are not using complex data types we could rely on the soap client already implemented... |
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 did you look at the code? madppiper sent the following on 4/8/2009 3:24 AM: > Hmm, > > well the thing I personally don't understand is that the basic SOAP > Interface integrated into OFBiz should work, if not used with complex > datatypes, correct? > > Agreeably the WSDL provided by OFBIz when setting a service to export="true" > is not fully WSDL conform, but in theory this should work, right? > > The ping method is nothing I implemented, but was already existent in the > ofbiz trunk and defined as such: > > <?xml version="1.0" encoding="UTF-8"?> > <wsdl:definitions targetNamespace="http://ofbiz.apache.org/service/" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" > xmlns:tns="http://ofbiz.apache.org/service/" > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" > xmlns:xsd="http://www.w3.org/2001/XMLSchema"> > <wsdl:message name="pingRequest"> > <wsdl:part name="message" type="xsd:string"/> > </wsdl:message> > <wsdl:message name="pingResponse"> > <wsdl:part name="message" type="xsd:string"/> > </wsdl:message> > <wsdl:portType name="pingPortType"> > <wsdl:operation name="ping"> > > <wsdl:input message="tns:pingRequest"/> > <wsdl:output message="tns:pingResponse"/> > </wsdl:operation> > </wsdl:portType> > <wsdl:binding name="pingSoapBinding" type="tns:pingPortType"> > <soap:binding style="document" > transport="http://schemas.xmlsoap.org/soap/http"/> > <wsdl:operation name="ping"> > <soap:operation soapAction=""/> > <wsdl:input> > > <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" > namespace="http://ofbiz.apache.org/service/" use="literal"/> > </wsdl:input> > <wsdl:output> > <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" > namespace="http://ofbiz.apache.org/service/" use="literal"/> > </wsdl:output> > </wsdl:operation> > </wsdl:binding> > <wsdl:service name="ping"> > <wsdl:port binding="tns:pingSoapBinding" name="pingPort"> > > <soap:address > location="http://focworld.nine.ch:8080/webtools/control/SOAPService"/> > </wsdl:port> > </wsdl:service> > </wsdl:definitions> > > > So my xml file should have worked... yet it didn't... Perhaps implementing > AXIS2 nonetheless and working all around the problem by creating pojo > classes instead is one solution, but I was hoping that since we are not > using complex data types we could rely on the soap client already > implemented... > Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3IcqrP3NbaWWqE4RAqLxAKDBf6vznew/xRNV9ndQa5L0HBG7sQCfYaS+ ACJZhlmtY61qSPAWSU+Blk4= =tTO0 -----END PGP SIGNATURE----- |
|
|
Well, I tried ;)
As far as I understand is this really only the code for the Client, so if I wanted to send an xml document using SOAP thats what I would use, however I am trying to understand the SOAP server really, or better, how OFBIz process those xml documents its receiving on the url... To clarify: I am trying to send an xml document as the above to the following url: http://focworld.nine.ch:8080/webtools/control/SOAPService/ping I am using a soapclient for that on an external machine... |
|
|
HA!
Well, turns out that implementing AXIS2 as described on the wikipage (http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP+using+AXIS2) was really the solution to it all. I'd argue that a basic implementation should be integrated into ofbiz period... Reminds me: I updated Alfredos great zip file a little and could supply you with a more basic alternative to the one uploaded (with the basic Weather Pojo integrated)... I am sure this would be of greater use for most people, since they can start editing the java files directly without having to be concerned about the implementation at all... |
Administrator
|
I want to have a look at it (I downloaded the zip file some times ago) but did not find the time yet... Anyway upload your file and
we will see what we can do... Jacques From: "madppiper" <[hidden email]> > > HA! > > Well, turns out that implementing AXIS2 as described on the wikipage > (http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP+using+AXIS2) > was really the solution to it all. I'd argue that a basic implementation > should be integrated into ofbiz period... > > Reminds me: I updated Alfredos great zip file a little and could supply you > with a more basic alternative to the one uploaded (with the basic Weather > Pojo integrated)... I am sure this would be of greater use for most people, > since they can start editing the java files directly without having to be > concerned about the implementation at all... > -- > View this message in context: http://www.nabble.com/A-simple-SOAP-Query--tp22946566p22955819.html > Sent from the OFBiz - User mailing list archive at Nabble.com. > |
|
|
Sure thing :)
http://docs.ofbiz.org/pages/viewpageattachments.action?pageId=6090 Btw, I also edited the build file, so if you generate the service, it will automatically deploy it on the axis2-webapp as well... I think the zip file contains all the things you need to get stated, just unzip (actually unrar) it in your hotdeploy directory... Please give me feedback if all of the above works as inspected (I had to change a few references of our own project prior uploading) |
|
|
In reply to this post by madppiper-2
Hello!
Paul, I'm glad that the solution was helpful for you. Thank you for providing a simpler and ready to use example for other developers. We are exporting 7 Ofbiz Services and the solution is really useful for complex and simple parameters (because using Axis2 we have fixed some strange errors related to current Ofbiz SOAP implementation) If the Axis2 solution is finally included in Ofbiz, please may somebody post the svn revision of the commit? Thanks!
|
|
|
Has the axis2 service now been integrated into ofbiz core?
Many thanks in advance, Chris
|
|
Administrator
|
Not yet, I'm still working on it. But at this stage it will only be a servlet integration, ie not much more than what is already at
http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP+using+AXIS2 Jacques From: "snowc" <[hidden email]> > > Has the axis2 service now been integrated into ofbiz core? > > Many thanks in advance, > > Chris > > > > Alfredo Rueda wrote: >> >> Hello! >> >> Paul, I'm glad that the solution was helpful for you. Thank you for >> providing a simpler and ready to use example for other developers. >> We are exporting 7 Ofbiz Services and the solution is really useful for >> complex and simple parameters (because using Axis2 we have fixed some >> strange errors related to current Ofbiz SOAP implementation) >> If the Axis2 solution is finally included in Ofbiz, please may somebody >> post the svn revision of the commit? >> >> Thanks! >> >> >> madppiper wrote: >>> >>> HA! >>> >>> Well, turns out that implementing AXIS2 as described on the wikipage >>> (http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP+using+AXIS2) >>> was really the solution to it all. I'd argue that a basic implementation >>> should be integrated into ofbiz period... >>> >>> Reminds me: I updated Alfredos great zip file a little and could supply >>> you with a more basic alternative to the one uploaded (with the basic >>> Weather Pojo integrated)... I am sure this would be of greater use for >>> most people, since they can start editing the java files directly without >>> having to be concerned about the implementation at all... >>> >> >> > > -- > View this message in context: http://www.nabble.com/A-simple-SOAP-Query--tp22946566p25454562.html > Sent from the OFBiz - User mailing list archive at Nabble.com. > |
|
|
Hi Jacques, Servlet integration will be a great improvement on having to manually integrate Axis!
|
|
|
In reply to this post by Jacques Le Roux
Hi Jacques, the example implementations need some additional work to secure them. For example, the examples use the default username and password for the axis admin screens. Also, the services are listed which is undesirable for a internet facing site.
|
|
Administrator
|
Thanks,
I have already thought that I should change the defaut password to use the same as admin in OFBiz. I tried but it was not as easy as I would have thought For the services there are no problems as it should be only available with the right permisions. Jacques From: "snowc" <[hidden email]> > Hi Jacques, the example implementations need some additional work to secure > them. For example, the examples use the default username and password for > the axis admin screens. Also, the services are listed which is undesirable > for a internet facing site. > > > jacques.le.roux wrote: >> >> Not yet, I'm still working on it. But at this stage it will only be a >> servlet integration, ie not much more than what is already at >> http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP+using+AXIS2 >> >> Jacques >> >> From: "snowc" <[hidden email]> >>> >>> Has the axis2 service now been integrated into ofbiz core? >>> >>> Many thanks in advance, >>> >>> Chris >>> >>> >>> >>> Alfredo Rueda wrote: >>>> >>>> Hello! >>>> >>>> Paul, I'm glad that the solution was helpful for you. Thank you for >>>> providing a simpler and ready to use example for other developers. >>>> We are exporting 7 Ofbiz Services and the solution is really useful for >>>> complex and simple parameters (because using Axis2 we have fixed some >>>> strange errors related to current Ofbiz SOAP implementation) >>>> If the Axis2 solution is finally included in Ofbiz, please may somebody >>>> post the svn revision of the commit? >>>> >>>> Thanks! >>>> >>>> >>>> madppiper wrote: >>>>> >>>>> HA! >>>>> >>>>> Well, turns out that implementing AXIS2 as described on the wikipage >>>>> (http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP+using+AXIS2) >>>>> was really the solution to it all. I'd argue that a basic >>>>> implementation >>>>> should be integrated into ofbiz period... >>>>> >>>>> Reminds me: I updated Alfredos great zip file a little and could supply >>>>> you with a more basic alternative to the one uploaded (with the basic >>>>> Weather Pojo integrated)... I am sure this would be of greater use for >>>>> most people, since they can start editing the java files directly >>>>> without >>>>> having to be concerned about the implementation at all... >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/A-simple-SOAP-Query--tp22946566p25454562.html >>> Sent from the OFBiz - User mailing list archive at Nabble.com. >>> >> >> >> > > -- > View this message in context: http://www.nabble.com/A-simple-SOAP-Query--tp22946566p25458590.html > Sent from the OFBiz - User mailing list archive at Nabble.com. > |
|
Administrator
|
In reply to this post by BJ Freeman
Hi Alfredo, Paul,
I had a new look at the Axis2 component cleaned it and "integrated" it in framework directory (actually it only compiles and cleans with the main build task for now). I think it's not what suggested David, but I did not get through a complete integration yet. Now Chatree is looking at it http://markmail.org/message/wtdqhmt5723cjsnn Chatree, I have a note here saying that SOAPClientEngine & SOAPEventHandler are involved. But I guess you are more ahead now Thanks Jacques From: "Alfredo Rueda" <[hidden email]> > > Hello! > > Paul, I'm glad that the solution was helpful for you. Thank you for > providing a simpler and ready to use example for other developers. > We are exporting 7 Ofbiz Services and the solution is really useful for > complex and simple parameters (because using Axis2 we have fixed some > strange errors related to current Ofbiz SOAP implementation) > If the Axis2 solution is finally included in Ofbiz, please may somebody post > the svn revision of the commit? > > Thanks! > > > madppiper wrote: >> >> HA! >> >> Well, turns out that implementing AXIS2 as described on the wikipage >> (http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP+using+AXIS2) >> was really the solution to it all. I'd argue that a basic implementation >> should be integrated into ofbiz period... >> >> Reminds me: I updated Alfredos great zip file a little and could supply >> you with a more basic alternative to the one uploaded (with the basic >> Weather Pojo integrated)... I am sure this would be of greater use for >> most people, since they can start editing the java files directly without >> having to be concerned about the implementation at all... >> > > -- > View this message in context: http://www.nabble.com/A-simple-SOAP-Query--tp22946566p23366335.html > Sent from the OFBiz - User mailing list archive at Nabble.com. > |
|
Administrator
|
Chatree,
It's only related to build task and I don't remember clearly, but I got an issue when cleaning with build.xml it was related to _src-available in common.xml. I did not dig further. Jacques From: "Jacques Le Roux" <[hidden email]> > Hi Alfredo, Paul, > > I had a new look at the Axis2 component cleaned it and "integrated" it in framework directory (actually it only compiles and > cleans > with the main build task for now). I think it's not what suggested David, but I did not get through a complete integration yet. > Now Chatree is looking at it http://markmail.org/message/wtdqhmt5723cjsnn > > Chatree, > > I have a note here saying that SOAPClientEngine & SOAPEventHandler are involved. > But I guess you are more ahead now > > Thanks > > Jacques > > From: "Alfredo Rueda" <[hidden email]> >> >> Hello! >> >> Paul, I'm glad that the solution was helpful for you. Thank you for >> providing a simpler and ready to use example for other developers. >> We are exporting 7 Ofbiz Services and the solution is really useful for >> complex and simple parameters (because using Axis2 we have fixed some >> strange errors related to current Ofbiz SOAP implementation) >> If the Axis2 solution is finally included in Ofbiz, please may somebody post >> the svn revision of the commit? >> >> Thanks! >> >> >> madppiper wrote: >>> >>> HA! >>> >>> Well, turns out that implementing AXIS2 as described on the wikipage >>> (http://docs.ofbiz.org/display/OFBIZ/Export+Ofbiz+Services+that+use+complex+type+parameters+via+SOAP+using+AXIS2) >>> was really the solution to it all. I'd argue that a basic implementation >>> should be integrated into ofbiz period... >>> >>> Reminds me: I updated Alfredos great zip file a little and could supply >>> you with a more basic alternative to the one uploaded (with the basic >>> Weather Pojo integrated)... I am sure this would be of greater use for >>> most people, since they can start editing the java files directly without >>> having to be concerned about the implementation at all... >>> >> >> -- >> View this message in context: http://www.nabble.com/A-simple-SOAP-Query--tp22946566p23366335.html >> Sent from the OFBiz - User mailing list archive at Nabble.com. >> > > |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |