More info on this - After confirming that the SOAP 1.1 spec expects this
header, I added the marked line of code to controller.jsp at this
snippet (sorry I currently don't have the CVS tooling to do a diff and
post a real patch):
URLConnection connection = targetURL.openConnection();
connection.setDoOutput(true);
connection.setRequestProperty("SOAPAction",""); // added this
line
That fixed my problem and the console now operates with Axis 1.2 Final.
The header will be superfluous with SOAP 1.2, but won't hurt either....
Steve Olson
-----Original Message-----
From: Steve Viens [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 08, 2005 6:51 AM
To: [email protected]
Subject: RE: Question on beta console
Steve,
I've haven't run into that problem ... can you tell me a little more
about your environment. Which JDK? Servlet Engine? (etc).
I don't know what the future holds for the console. I created it merely
to assist with testing. If you can confirm that a missing SOAPAction
header is the problem (even better - produce a patch - probably to
controller.jsp) it would be appreciated.
If anyone else has tried the console and run into this problem please
comment.
Steve
-----Original Message-----
From: Olson, Steve [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 07, 2005 2:52 PM
To: [email protected]
Subject: Question on beta console
I've just today downloaded jUDDI (the nightly snapshot), built it, and
deployed it under Tomcat 5.5.9. So I'm pretty new to all this and could
have messed up, but the happyjuddi page returns no errors, so I tried
some of the console stuff. Everything console operation I try (queries
and saves) results in this callstack, complaining about a missing
SOAPAction HTTP request header that Axis 1.2 evidently requires:
2005-06-07 12:58:10,572 [http-8080-Processor24] ERROR
org.apache.axis.EXCEPTIONS - Generating fault class AxisFault
faultCode: {http://xml.apache.org/axis/}Client.NoSOAPAction
faultSubcode:
faultString: no SOAPAction header!
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:no SOAPAction header!
at
org.apache.axis.transport.http.AxisServlet.getSoapAction(AxisServlet.jav
a:1004)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.j
ava:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAcc
essLogValve.java:481)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:85
6)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:744)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint
.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow
erWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:684)
at java.lang.Thread.run(Unknown Source)
Looking at the JSP that posts the admin URL, it has no request headers I
can see at all. If anyone is familiar with what might cause this
exception, I'd appreciate the info.
Steve Olson
*******************************
The information contained in this message may be privileged and/or confidential
and
protected from disclosure. If the reader of this message is not the intended
recipient,
or an employee or agent responsible for delivering this message to the intended
recipient,
you are hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited. Note that any views or opinions presented
in this
message are solely those of the author and do not necessarily represent those
of Ameren.
All emails are subject to monitoring and archival. Finally, the recipient
should check
this message and any attachments for the presence of viruses. Ameren accepts no
liability
for any damage caused by any virus transmitted by this email. If you have
received this in
error, please notify the sender immediately by replying to the message and
deleting the
material from any computer. Ameren Corporation
*******************************
