Re: viamichelin web services - no SOAPAction header

2007-03-15 Thread domel

I tried to edit service stub generated by wsdl2java and i have replaced 

_call.setUseSOAPAction(true);
_call.setSOAPActionURI("")

with 

_call.setUseSOAPAction(true);
_call.setSOAPActionURI("getLocationsList")

//the rest of generated code
_call.setSOAPActionURI("");
   
_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
_call.setOperationName(new
javax.xml.namespace.QName("http://service.localization.ws2.viamichelin.com";,
"getLocationsList"));

but those changes didn't bring any effect and the problem still exists.


Anne Thomas Manes wrote:
> 
> Have you set the SOAPAction header in your code?
> 
> On 3/14/07, domel <[EMAIL PROTECTED]> wrote:
>>
>> Hello
>>
>> I'm trying to run sample application for viamichelin webservices.
>> Unfortunately i got following message error
>>
>> Exception in thread "main" 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.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>> at
>> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>> at
>> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>> ...
>>
>> Bellow is  briefly presented my system configuration:
>>
>> Suse Linux 9.3
>> J2SDK 1.4.2.13
>> Jakarta Tomcat 5.0.28
>> Axis 1.4
>> XERCES 2.9.0
>>
>> I also would like to mention that my axis seems to be configured ok. All
>> requred core libraries are present, only 2 optional libraries are missed,
>> but they dont seem to be required.
>> --
>> View this message in context:
>> http://www.nabble.com/viamichelin-web-services---no-SOAPAction-header-tf3404796.html#a9483344
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/viamichelin-web-services---no-SOAPAction-header-tf3404796.html#a948
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: viamichelin web services - no SOAPAction header

2007-03-14 Thread Anne Thomas Manes

Have you set the SOAPAction header in your code?

On 3/14/07, domel <[EMAIL PROTECTED]> wrote:


Hello

I'm trying to run sample application for viamichelin webservices.
Unfortunately i got following message error

Exception in thread "main" 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.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
...

Bellow is  briefly presented my system configuration:

Suse Linux 9.3
J2SDK 1.4.2.13
Jakarta Tomcat 5.0.28
Axis 1.4
XERCES 2.9.0

I also would like to mention that my axis seems to be configured ok. All
requred core libraries are present, only 2 optional libraries are missed,
but they dont seem to be required.
--
View this message in context: 
http://www.nabble.com/viamichelin-web-services---no-SOAPAction-header-tf3404796.html#a9483344
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



viamichelin web services - no SOAPAction header

2007-03-14 Thread domel

Hello

I'm trying to run sample application for viamichelin webservices.
Unfortunately i got following message error

Exception in thread "main" 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.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
...

Bellow is  briefly presented my system configuration:

Suse Linux 9.3
J2SDK 1.4.2.13
Jakarta Tomcat 5.0.28
Axis 1.4
XERCES 2.9.0

I also would like to mention that my axis seems to be configured ok. All
requred core libraries are present, only 2 optional libraries are missed,
but they dont seem to be required. 
-- 
View this message in context: 
http://www.nabble.com/viamichelin-web-services---no-SOAPAction-header-tf3404796.html#a9483344
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: no SOAPAction header - Is a SOAPAction header still required in SOAP 1.2?

2006-04-19 Thread Joshua . White

I have now set the following option so that Axis uses soap 1.2 as the default.

    
        
    

Problem is, I still get the same error.  









[EMAIL PROTECTED]
04/19/2006 10:24 AM
Please respond to axis-user

        
        To:        axis-user@ws.apache.org
        cc:        
        Subject:        no SOAPAction header - Is a SOAPAction header still required in SOAP    1.2?



I though I remember reading that the SOAPAction header is no longer required in SOAP 1.2.  Is this correct? 

I have a client that is sending me a SOAP message and I am receiving the following AXIS error message: 

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.java:1013) 
        at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678) 
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) 
        at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) 
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) 
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) 
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) 
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272) 
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165) 
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153) 
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) 
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) 
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973) 
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880) 
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310) 
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) 
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:179) 

How do I fix this? 

Regards, 

Joshua 

*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*




no SOAPAction header - Is a SOAPAction header still required in SOAP 1.2?

2006-04-19 Thread Joshua . White

I though I remember reading that the SOAPAction header is no longer required in SOAP 1.2.  Is this correct?

I have a client that is sending me a SOAP message and I am receiving the following AXIS error message:

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.java:1013)
        at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
        at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

How do I fix this?

Regards,

Joshua


*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*



Re: Getting "no SOAPAction header" using Apache -> mod_jk -> tomcat (Resolved)

2006-01-10 Thread Paul Spencer

Jim,
In short, very little.  We installed NetCat on the server, which is 
running the current stable Debain.  We then used NetCat to dump the 
request sent to port 80.  Since the client ran correctly outside the 
firewall, we compared the dump when running the client inside and then 
outside the firewall.  This told us the firewall was stripping 
SOAPAction from the http header.


We had to use NetCat instead of the tcpmon because the server is in a 
DMZ with only ssh access.


Relative to the Apache and Mod_JK configuration, their is no difference 
in the configuration for a webservice vs a jsp/servlet application.


Paul Spencer



Jim Azeltine wrote:

So you found the problem and resolved it, but what did you do? I would like to 
know as our customer uses the same configuration.
   
  Jim Azeltine

  Senior Software Engineer, SAIC

Paul Spencer <[EMAIL PROTECTED]> wrote:
  Found the problem :)

The outbound firewall was stripping the http header SOAPAction, thus 
causing the error.


Paul Spencer


Paul Spencer wrote:

I am getting the error below when sending a request to my web service 
that is running on a Tomcat which is frontend by an Apache web server. 
I suspect this is a configuration error related to passing the HTTP 
header to Tomcat, but I am not sure what to look for.


Other tid-bits of information:
1) The wsdl is returned without error, i.e. 
http://foo.com/services/MyWebService?wsdl.


2) The same web service is deployed on Tomcat 5.5.9 without an Apache 
web server front end. It work correctly.


Version Information:
Debian 2.2.6
Apache v1.3.33
mod_jk v1.2.5
Tomcat v4.1.31
Axis v1.3

**
* Error message
**
Jan 6, 2006 3:09:47 PM org.apache.axis.transport.http.AxisServlet 
getSoapAction

SEVERE: 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.java:1013) 

at 
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at 
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) 


at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)


Paul Spencer





  







Re: Getting "no SOAPAction header" using Apache -> mod_jk -> tomcat (Resolved)

2006-01-09 Thread Jim Azeltine
So you found the problem and resolved it, but what did you do? I would like to know as our customer uses the same configuration.     Jim Azeltine  Senior Software Engineer, SAICPaul Spencer <[EMAIL PROTECTED]> wrote:  Found the problem :)The outbound firewall was stripping the http header SOAPAction, thus causing the error.Paul SpencerPaul Spencer wrote:> I am getting the error below when sending a request to my web service > that is running on a Tomcat which is frontend by an Apache web server. > I suspect this is a configuration error related to passing the HTTP > header to Tomcat, but I am not sure what to look for.> > Other tid-bits of information:> 1) The wsdl is returned without error, i.e. >
 http://foo.com/services/MyWebService?wsdl.> > 2) The same web service is deployed on Tomcat 5.5.9 without an Apache > web server front end. It work correctly.> > Version Information:> Debian 2.2.6> Apache v1.3.33> mod_jk v1.2.5> Tomcat v4.1.31> Axis v1.3> > **> * Error message> **> Jan 6, 2006 3:09:47 PM org.apache.axis.transport.http.AxisServlet > getSoapAction> SEVERE: 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.java:1013) > > at >
 org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)> at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)> at > org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)> > > Paul Spencer> >   

Re: Getting "no SOAPAction header" using Apache -> mod_jk -> tomcat (Resolved)

2006-01-09 Thread Paul Spencer

Found the problem :)

The outbound firewall was stripping the http header SOAPAction, thus 
causing the error.


Paul Spencer


Paul Spencer wrote:
I am getting the error below when sending a request to my web service 
that is running on a Tomcat which is frontend by an Apache web server. 
 I suspect this is a configuration error related to passing the HTTP 
header to Tomcat, but I am not sure what to look for.


Other tid-bits of information:
1) The wsdl is returned without error, i.e. 
http://foo.com/services/MyWebService?wsdl.


2) The same web service is deployed on Tomcat 5.5.9 without an Apache 
web server front end.  It work correctly.


Version Information:
  Debian 2.2.6
  Apache v1.3.33
  mod_jk v1.2.5
  Tomcat v4.1.31
  Axis v1.3

**
* Error message
**
Jan 6, 2006 3:09:47 PM org.apache.axis.transport.http.AxisServlet 
getSoapAction

SEVERE: 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.java:1013) 

at 
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at 
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) 


at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)


Paul Spencer






Getting "no SOAPAction header" using Apache -> mod_jk -> tomcat

2006-01-06 Thread Paul Spencer
I am getting the error below when sending a request to my web service 
that is running on a Tomcat which is frontend by an Apache web server. 
 I suspect this is a configuration error related to passing the HTTP 
header to Tomcat, but I am not sure what to look for.


Other tid-bits of information:
1) The wsdl is returned without error, i.e. 
http://foo.com/services/MyWebService?wsdl.


2) The same web service is deployed on Tomcat 5.5.9 without an Apache 
web server front end.  It work correctly.


Version Information:
  Debian 2.2.6
  Apache v1.3.33
  mod_jk v1.2.5
  Tomcat v4.1.31
  Axis v1.3

**
* Error message
**
Jan 6, 2006 3:09:47 PM org.apache.axis.transport.http.AxisServlet 
getSoapAction

SEVERE: 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.java:1013)
at 
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at 
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)


Paul Spencer



Re: no SOAPAction header!

2005-08-10 Thread richard falconer

re - Check your classpath and make sure you are using the right jars...
I'm using the latest axis jar from 1_2_1 ??

csj - thanks that works
At 12:37 09/08/2005, you wrote:

Looks like thte SOAPActionURI is empty... add the correct value, for
example in method 'add' do setSOAPActionURI("add").  The action URI should
match the soapAction in the wsdl for the operation.B

On 8/9/05, richard falconer <[EMAIL PROTECTED]> wrote:
> Hi,
> Still getting the exception being thrown.
>
> The following lines of code were already in the stub, created by the 
wsdl2java:

> _call.setUseSOAPAction(true);
> _call.setSOAPActionURI("");
>
> ta,
> Richard
>
>  > Check your client side BindingStub.java for call.setUseSOAPAction(true)
>  > and call.setSOAPActionURI("blah") for each method that calls invoke.
>  >
>  > Cheers,
>  >
>  >
>  > On Mon, 8 Aug 2005, richard falconer wrote:
>  >
>  > Hi,
>  >
>  > After running an axis (axis-1_2_1) server on Tomcat 5.0 and testing 
it fine
>  > from the same machine, once I began testing from a different machine 
I get

>  > exception below being thrown whether I'm testing it remotely or locally.
>  >
>  > Any suggestions appreciated,
>  > ta Richard
>  >
>  > 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.java: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.java:327)

>  >  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>  >  at
>  >
> 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)

>  >  at
>  >
> 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)

>  >  at
>  >
> 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)

>  >  at
>  >
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

>  >  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>  >  at
>  >
> 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)

>  >  at
>  >
> 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)

>  >  at
>  >
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

>  >  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>  >  at
>  >
> 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)

>  >  at
>  >
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

>  >  at
>  >
> 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)

>  >  at
>  >
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)

>  >  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>  >  at
>  >
> 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

>  >  at
>  >
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

>  >  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>  >  at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>  >  at 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)

>  >  at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
>  >  at
>  >
> 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)

>  >  at
> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
>  >  at
>  >
> 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)

>  >  at java.lang.Thread.run(Thread.java:536)
>  >
>
>
>





Re: no SOAPAction header!

2005-08-09 Thread Anne Thomas Manes
Check your classpath and make sure you are using the right jars...

On 8/9/05, richard falconer <[EMAIL PROTECTED]> wrote:
> Hi,
> Still getting the exception being thrown.
> 
> The following lines of code were already in the stub, created by the 
> wsdl2java:
> _call.setUseSOAPAction(true);
> _call.setSOAPActionURI("");
> 
> ta,
> Richard
> 
>  > Check your client side BindingStub.java for call.setUseSOAPAction(true)
>  > and call.setSOAPActionURI("blah") for each method that calls invoke.
>  >
>  > Cheers,
>  >
>  >
>  > On Mon, 8 Aug 2005, richard falconer wrote:
>  >
>  > Hi,
>  >
>  > After running an axis (axis-1_2_1) server on Tomcat 5.0 and testing it fine
>  > from the same machine, once I began testing from a different machine I get
>  > exception below being thrown whether I'm testing it remotely or locally.
>  >
>  > Any suggestions appreciated,
>  > ta Richard
>  >
>  > 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.java: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.java:327)
>  >  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>  >  at
>  >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
>  >  at
>  >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
>  >  at
>  >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
>  >  at
>  >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>  >  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>  >  at
>  >
> org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
>  >  at
>  >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
>  >  at
>  >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>  >  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>  >  at
>  >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
>  >  at
>  >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>  >  at
>  >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
>  >  at
>  >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
>  >  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>  >  at
>  >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>  >  at
>  >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>  >  at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>  >  at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>  >  at 
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
>  >  at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
>  >  at
>  >
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
>  >  at
> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
>  >  at
>  >
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
>  >  at java.lang.Thread.run(Thread.java:536)
>  >
> 
> 
>


Re: no SOAPAction header!

2005-08-09 Thread richard falconer

Hi,
Still getting the exception being thrown.

The following lines of code were already in the stub, created by the wsdl2java:
_call.setUseSOAPAction(true);
_call.setSOAPActionURI("");

ta,
Richard

> Check your client side BindingStub.java for call.setUseSOAPAction(true)
> and call.setSOAPActionURI("blah") for each method that calls invoke.
>
> Cheers,
>
>
> On Mon, 8 Aug 2005, richard falconer wrote:
>
> Hi,
>
> After running an axis (axis-1_2_1) server on Tomcat 5.0 and testing it fine
> from the same machine, once I began testing from a different machine I get
> exception below being thrown whether I'm testing it remotely or locally.
>
> Any suggestions appreciated,
> ta Richard
>
> 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.java: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.java:327)

>at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>at
> 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)

>at
> 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)

>at
> 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)

>at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> 	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)

>at
> 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)

>at
> 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)

>at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> 	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)

>at
> 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)

>at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

>at
> 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)

>at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> 	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)

>at
> 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

>at
> 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> 	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)

>at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
> 	at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)

>at
> 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
> 	at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)

>at
> 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)

>at java.lang.Thread.run(Thread.java:536)
>




no SOAPAction header!

2005-08-08 Thread richard falconer

Hi,

After running an axis (axis-1_2_1) server on Tomcat 5.0 and testing it fine 
from the same machine, once I began testing from a different machine I get 
exception below being thrown whether I'm testing it remotely or locally.


Any suggestions appreciated,
ta Richard

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.java: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.java:327)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
	at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
	at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
	at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
	at 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
	at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
	at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
	at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
	at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
	at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
	at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
	at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
	at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)

at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
	at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)

at java.lang.Thread.run(Thread.java:536)