On Wed, Apr 10, 2002 at 08:50:56AM +0200, Jung , Dr. Christoph wrote:
> 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?
I don't think so. Seems like the SOAP toolkit depends on using that field on calling.
It is just the wsdl-generation that isn't recoginzing it. Tried with CVS version of
axis, but jbosss miss a class then. Also tried to dig into jboss.net and axis source
code. Found a useSoapAction, but nowhere to set it. It also seemed like it is using
the operation-name + someting else as soapAction. It might be a bug in axis, as I
checked the CVS-source, and couldn't get it to work. Could you identify where the bug
is, so it could be reported to axis, if it is a axis-problem.
>
> 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 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
> >
> > > standalone="no"?> > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> >
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";> OAPSDK1:hello
> xmlns:SOAPSDK1="http://localhost:8080/axis/services/Hello";>Bob OAPSDK1:hello>
> >
> > =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
> >
> >
> > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
> >
> >
> > >
> xmlns:ns1="http://xml.apache.org/axis/";>ns1:Client.NoSOAPAction
> >no SOAPAction header!
> >
> > 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.SocketL
