This is good to hear. This is great to hear. This is fantastic to hear. This is damned fantastic to hear ;-)
Up to now, I did not notice that we were using the SoapAction header at all ... I have a handler for that installed in the default http-chain (see the jboss/server/conf/default/axis-config.xml), but that was just to Allow SoapAction as an optional way to identify the target method. Maybe I should take that out? Seems like regular axis and .NET clients will set the header automatically? There are still a few bugs in axis wsdl-generation (jboss.net does currently no overriding of the axis generation methods), such as upper-Case element names for lower-case properties, but I think I have patched that in the checked-in axis.jar - I really should double-check that with their repository and file a patch at apache ... CGJ -----Ursprüngliche Nachricht----- Von: Marius Kotsbak [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 9. April 2002 20:01 An: Marius Kotsbak Cc: Jung , Dr. Christoph; 'Martin Maisey'; [EMAIL PROTECTED] Betreff: Re: [JBoss-user] Bugs in JBoss.NET,SOAP found (NoSoapAction) I verfied it was a bug. I manually downloaded the generated .wsdl-file and added hello in the <wsdlsoap:operation soapAction=""/> field, and then it actually worked :-)) Great work! I think this is easily fixed, don't know if it is in axis or jboss-module. On tir, 2002-04-09 at 19:46, Marius Kotsbak wrote: > I managed to get the ASP-client running on MS Personal Web server > (under > win4lin.com) with the SOAP toolkit 2.0 from microsoft.com to lookup the > wsdl, but when i try to run the hello-method, nothing happens, but I > traced the network traffic and found this: > > > ============================================= > POST /axis/services/Hello HTTP/1.1 > Content-Type: text/xml > User-Agent: SOAP Sdk > Host: marius.kotsbak.com:8080 > Content-Length: 365 > Connection: Keep-Alive > Cache-Control: no-cache > > <?xml version="1.0" encoding="UTF-8" > standalone="no"?><SOAP-ENV:Envelope > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";><SOAP-ENV:Body><S OAPSDK1:hello xmlns:SOAPSDK1="http://localhost:8080/axis/services/Hello";><in0>Bob</in0></S OAPSDK1:hello></SOAP-ENV:Body></SOAP-ENV:Envelope> > > =========Answer from axis== > HTTP/1.1 500 Internal Server Error > Date: Tue, 09 Apr 2002 17:28:03 GMT > Server: Jetty/4.0.0 (Linux 2.4.18-lsmw4l x86) > Servlet-Engine: Jetty/1.1 (Servlet 2.3; JSP 1.2; java 1.3.0) > Content-Type: text/xml; charset=utf-8 > Content-Length: 1538 > > <?xml version="1.0" encoding="UTF-8"?> > <SOAP-ENV:Envelope > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";> > <SOAP-ENV:Body> > <SOAP-ENV:Fault> > <faultcode > xmlns:ns1="http://xml.apache.org/axis/";>ns1:Client.NoSOAPAction</faultcode> > <faultstring>no SOAPAction header!</faultstring> > <detail> > <ns2:stackTrace xmlns:ns2="http://xml.apache.org/axis/";>no > SOAPAction header! > at > org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:509) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:326) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:595) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1357) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1309) > at org.mortbay.http.HttpServer.service(HttpServer.java:744) > at org.jboss.jetty.Jetty.service(Jetty.java:528) > at org.mortbay.http.HttpConnection.service(HttpConnection.java:743) > at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916) > at org.mortbay.http.HttpConnection.handle(HttpConnection.java:758) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:145) > at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) > at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) > at java.lang.Thread.run(Thread.java:498) > </ns2:stackTrace> > </detail> > </SOAP-ENV:Fault> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope> > ================================== > > > > I wounder if this happens because the soapAction="" in the generated > wsdl below: > > ========================================== > <wsdl:operation name="hello"> > <wsdlsoap:operation soapAction=""/> > <wsdl:input> > <wsdlsoap:body use="encoded" > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > namespace="http://localhost:8080/axis/services/Hello"/> > </wsdl:input> > <wsdl:output> > <wsdlsoap:body use="encoded" > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > namespace="http://localhost:8080/axis/services/Hello"/> > </wsdl:output> > </wsdl:operation> > ================================== > > This is the same for all operations. Anyway, is this right? > > Here is the asp-script I am running against the hello-bean from the > testsuite: > > =================================== > <% Option Explicit > > Dim soapClient > set soapclient = CreateObject("MSSOAP.SoapClient") > On Error Resume Next > Call > soapclient.mssoapinit("http://localhost:8080/axis/services/Hello?wsdl";, > "HelloService", "Hello") > if err <> 0 then %> > initialization failed " + <%=err.description%> > <% end if %> > > Test: <%=soapclient.hello("Bob") %> > =========================================================== > > > Another posible bug is that the <ejb-ref> in web-service.xml doesn't > seem to work. When i changed to "helloworld/HelloWorld", it worked. > > BTW: what kind of client (on the M$ platform) are you using, Martin? > > Marius K > SW Dev > Boost communications A/S > Norway > boostcom.no > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
