Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

How can I send header message in Java by using org.apache.axis.client.Stub and java.rmi.Remote?

 
Zeynep Coskun
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a wsdl and this wsdl has a request message like this, in SOAPUI:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:service="www.xxxxx.xx">
<soapenv:Header>
<service:SessionInfo>
<service:UserPassword>?</service:UserPassword>
</service:SessionInfo></soapenv:Header>
<soapenv:Body>
<service:Method1>
<!--Optional:-->
<service:Arguments>
<service:Parameter1>?</service:Parameter1>
<service:Parameter2>?</service:Parameter2>
<!--Optional:-->
<service:Parameter3>?</service:Parameter3>
<!--Optional:-->
<service:Parameter4>?</service:Parameter4>
</service:Arguments>
</service:Method1></soapenv:Body></soapenv:Envelope>

I am having problem while sending header message of this wsdl in Java. I sent the request message in C# and SOAPUI successfully. After importing wsdl in Java I could not access the header part of this request although I was able to access in SOAPUI and C#. I can only access body part of this wsdl in Java but I cannot access soapenv:Header part in Java. Is there a solution for this problem by using org.apache.axis.client.Stub and java.rmi.Remote? How can I add header? Thanks.
 
Roger Sterling
Ranch Hand
Posts: 426
Eclipse IDE Fedora Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You are somewhat ambiguous in your post. What do you mean "I could not access the header part" ? What happens when you try to access it ? Have you experimented with Jersey ? https://jersey.java.net ? Jersey RESTful Web Services framework provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. A JAX-RS resource is an annotated POJO that provides resource methods that are able to handle HTTP requests (and access to headers) for URI paths that the resource is bound to. Which is what I think you are trying to do, but not sure based on your post.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic