Jax ws header

any one tell me how to set jax ws header and i want to access that values in httprequest at server side.
means i want to send jax ws client values (user name) to server ...

You can use a jax-ws handler and add the header to the message context that is intercepted by the soap handler. Depending on your server there are various ways to attach the handler to the server, you'll need to consult the users guide for your server, but as far as attaching the header its fairly straight forward. Check out this tutorial [http://devplace.wordpress.com/2007/09/24/adding-soap-header-in-java/|http://devplace.wordpress.com/2007/09/24/adding-soap-header-in-java/]

Similar Messages

How do I change the content-type in http header when using JAX-WS?

I need to change Content-Type in http Header. I am using JAX-WS to invoke web service call. Can someone tell me how to do it? Thanks a lot!

LabVIEW does so many wonderful things, but the inability to perform what should be a simple task, such as upgrade a RT chassis within a LV Project, bewilders me. This is going to cost me hours, I just know it...
Is there anything on the Idea Exchange for this?? A quick search shows nothing, so maybe I'll add an entry.
Thoric (CLA, CLED, CTD and LabVIEW Champion)

JAX-WS setting header HTTP basic authentication

Hello
How can I set HTTP header vars in JAX-WS?
I found a lot of questions but no answer works.
This is my code:
Service service = Service.create(url, portName);
OnlineSIUIDef hello = service.getPort(OnlineSIUIDef.class);
Map<String, Object> contextws = ((BindingProvider)service).getRequestContext();
contextws.put(BindingProvider.USERNAME_PROPERTY, SIUI_USERNAME);
contextws.put(BindingProvider.PASSWORD_PROPERTY, SIUI_PASSWORD);
All examples I found on the web are based on such a structure.
Problem is that first is created a new service, then the header vars are changed.
But this can't work because when the service is created(at line 1) error 401 is already thrown.
What is the equivalent in JAX-WS of the following lines?
HttpsURLConnection con = (HttpsURLConnection) url.openConnection();
con.setSSLSocketFactory(factory);
con.setRequestProperty(varName, val);
Can someone help with this problem?
I'm looking for a solution for over a day and I can't find nothing usefull about this.
Thank you.

Hi
Seems that the URL you are referring in Service.create() is a basic auth protected URL(wsdlLocation) ie why you are getting 401 error.
there are different options to resolve this.
Authenticator.setDefault(new Authenticator() {
@Override
protected PasswordAuthentication getPasswordAuthentication() {
 return new PasswordAuthentication(
 SIUI_USERNAME,
 SIUI_PASSWORD.toCharArray());
try to add the above code ,before creating the URL.
2 Download the WSDL from Endpoint and refer that WSDL locally,and dynamically hook the correct endpoint using
contextws.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,"ur Endpoint");
Haven't tried this...
custom SSLSocketFactory come in picture only if you have protected your webservice using one way/2 way SSL.
Thanks,
Paul

Async client with Soap Header (jax-wsi 2.0)

Hi my name's Michele
i have a problem!
I developed simply ws with JWSDP 2.0 (jax-wsi)
I use wsimport for generate artifcats (with XAdditionalHeader), but for Method Async i don't have object for header, in other words
i have this situation
1)Proxy with call Sync ok:
public void WebMetod(Obj body,SoapAut header); // ok body and SoapAut (Header Soap)
2) Async ko:
public Response<ResponseDU>WebMetodAsync(Obj body); //ko, becausw i can't invoke web method withi Header Soap
where is SoapHeader in asynck call ???
i expected th async call:
public Response<ResponseDU>WebMetodAsync(Obj body,SoapQut header) but in Proxy this call not exist
Help me please
bye
sorry for my Pitiful English.

Try this :
In the composite.xml of your mediator process, add "passThroughHeader" property. Probably, that might help.
Read this : Creating Oracle Mediator Routing Rules
Hope it helps !

Jax-ws ws-addressings non-anonymous replyto header asynchronous client

Hi All,
I have an asynchronous jax-ws client with addressingfeature enabled.
This will add the replyto header as anonymous and open a client listening port for the reply message when I execute the asynchronous method to the server.
The client is then waiting for asynchronous reply from the server.
Although I don't know the listening "replyto" address, I can see with netstat that it is listening to a random opened port (TCP).
How can I make the client send the non-anonymous random generated replyto header with the port so that the server can reply to?
Kind Regards,
Tuno

Hi,
there is a bug in 11.1.1.3 which is fixed in 11.1.1.4. but I found a simple workaround.
I changed the web service annotation from the callback function for "@Adressing" from "true" to "false". e.g.
@WebService(targetNamespace="http://xmlns.oracle.com/SOAHelloApp/SOAHelloAsync/SOAHelloAsyncProcess", name="SOAHelloAsyncProcessCallback")
@XmlSeeAlso(
{ ObjectFactory.class })
@SOAPBinding(style=Style.DOCUMENT)
@Addressing(enabled=false, required=false)
so I still have the wrong wsa:Action, but nobody cares.
HTH

Adding to JAX-WS 2.1 response object's header

Hello
We are using JAX-WS 2.1. We have a requirement to have few fields such as userId to be part of SOAP response's header. How to have these added in the header. Using @WebResult(header=true) gets the whole result object into the header which I don't want

Any suggestions

How to bind soap header using jax-rpc

To Whom It May Concern:
I am using Rad7, Ibm Websphere 6.1, on Windows XP.
I created an SoapHeader first using a string and bind it using jax-ws.
It works for jax-ws but unfortunately, my work services uses jax-rpc.
Does anybody know how to bind the soap header using jax-rpc.
Any help or hint would be greatly appreciated it.
Here is my code:
import org.apache.cxf.headers.Header;
import org.apache.cxf.headers.Header.Direction;
import org.apache.cxf.helpers.DOMUtils;
import org.apache.cxf.binding.soap.SoapHeader;
import javax.xml.namespace.QName;
import java.io.StringReader;
import java.util.List;
import java.util.ArrayList;
import javax.xml.ws.BindingProvider;
 @Test
 public void testService() throws Exception {
 try
 URL wsdlURL = new URL("http://localhost:9087/abc/services/ServiceABCService");
 ServiceRequestServiceService service = new ServiceRequestServiceServiceLocator();
 ServiceRequestService port = service.getServiceRequestService(wsdlURL);
 //How to Add Soap Header using jax-ws
 String xml = "<?xml version=\"1.0\" encoding=\"utf-8\"?><ABCHdrRq "
 + "xmlns=\"http://xmlns.ABCgc.net/ABC/2002/header/\" "
 + ">"
 + "<version>1.0</version><srcInfo><chType>abc</chType><chInst>0124</chInst>" +
 "<appName>sSAR</appName><hostName>DW70210521</hostName><userId>fxue</userId>" +
 "</srcInfo><startTimeStamp>2010-06-04T13:44:45.132</startTimeStamp><clientDt>2010-06-04T13:44:53.242</clientDt><serviceInfo><serviceName>ServiceRequestService</serviceName>" +
 "<serviceFunc>addServiceRequest</serviceFunc></serviceInfo>" +
 "<prevTransInfo><prevRqUID>BORS2010-06-04T13:41:10.2067f9368d1-8c5c</prevRqUID>" +
 "<prevRespTimestamp>2010-06-04T13:41:10.871</prevRespTimestamp>"+
 "<prevRespEndTimestamp>2010-06-04T13:41:10.902</prevRespEndTimestamp>+</prevTransInfo>"+
 "</ABCHdrRq>";
 SoapHeader dummyHeader1 = new SoapHeader(new QName("uri:http://xmlns.ABCgc.net/ABC/2002/header/", "ABCHdrRq"),
 DOMUtils.readXml(new StringReader(xml)).getDocumentElement());
 dummyHeader1.setDirection(Direction.DIRECTION_OUT);
 List<Header> headers = new ArrayList<Header>();
 headers.add(dummyHeader1);
 ((BindingProvider)port).getRequestContext().put(Header.HEADER_LIST, headers);
 //How to Add Soap Header to the request using jax-ws
 catch(Exception e)
 System.out.println("Exception message:"+e.getMessage());
Yours,
Frustrated

Well, how an attachment is processed depends on your application logic...if your application logic requires to processing attachments and verify it before processing the SOAP message, handlers could be better option.
If you need to process the attachment while processing the SOAP message, you can do it in the service implementation class.
In both the cases you need to get access to SOAPMessage object and from there get the attachments with getAttachments method.

Invalid Content-Type value on OC4J 10.1.3.4.0 when using JAX-WS

Hi all,
I'm developing web services using JAX-WS on top of OC4J 10.1.3.4.0. I followed the procedure to enable this in the developer guide with success. My web service is running fine but the headers of the HTTP response contains an invalid value for the Content-Type header
The charset element has the value utf-8" (with the double quote included) which is interpreted as a wrong encoding by the client application. 
Below is the HTTP request and response with the error. (I stripped the soap part for clarity) 
 
POST /mywebservice/ HTTP/1.1 
Content-Type: text/xml;charset=UTF-8 
SOAPAction: "http://soap.exemple.com/mywebservice" 
User-Agent: Jakarta Commons-HttpClient/3.0.1 
Host: behs0054:8888 
Content-Length: 2174 
 
<...> soap message 
<hr />
HTTP/1.1 500 Internal Server Error 
Date: Fri, 03 Oct 2008 13:10:43 GMT 
Server: Oracle Containers for J2EE 
Connection: Keep-Alive 
Keep-Alive: timeout=15, max=100 
Content-Type: text/xml;charset=utf-8"
Transfer-Encoding: chunked
<...> soap fault received
<hr />
Thanks a lot for your answers,
Gauthier

Does not only happen when using JAX-WS.
the following servlet code is enough to reproduce the problem :
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
response.setContentType("text/xml;charset=\"utf-8\"");
It only occurs on 10.1.3.4.0 (works fine on 10.1.3.3.0 and 11.1.1.1.0 TP4)
Regards

URGENT **** Need help for JAX-RPC Web Service Proxy deploy to OC4J 10.1.3.5

Hi everyone!
I’m really new to web services.
I’m getting a *500 internal server error* while deploying my JAX-RPC web service Proxy to an Oracle AS, in an OC4J, v. 10.1.3.5.0.
Running my client from my development environment (*jdeveloper 10g, 10.1.3.5.0*) everything functions correctly: from jdeveloper I can contact and use the web service defined by the following endpoint: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
I created a "try_ws_client.jsp" file that runs correctly from my local development environment jdeveloper (that uses an embedded oc4j, v. 10.1.3.5.0) but fails when run from the test server (Oracle AS, in an OC4J, v. 10.1.3.5.0), getting, as I mentioned a 500 internal server error, a white page in IE but with FF the message says: The’s an error in the servlet .....
Here's how I created the ws proxy and how I’m using it to consume the ws I mentioned.
1. I used the jdeveloper “Create Web Service Proxy” wizard (File > New > Business Tier > Web Services > Web Service Prox) and in the WSDL document URL I put: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
2. The operation ended without adding nothing to the web.xml file and creating the proxy files. One of them is: FederaMLOLSoapClient.java that have the WS exposed methods (es: public boolean createUser(String) ) + a “main” method with the example how to use this client to consume the WS.
public static void main(String[] args) {
try {
it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
System.out.println("calling " + myPort.getEndpoint());
// Add your own code here
} catch (Exception ex) {
ex.printStackTrace();
3. In FederaMLOLSoapClient.java I’ve create the method "tyIt":
public String tryIt(String username) {
try {
it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
if(myPort.createUser(String username)) {
return “O.K”;
} else {
return “K.O”;
} catch (Exception ex) {
// logs error
4. I created my try_ws_client.jsp file that creates FederaMLOLSoapClient object and calls the tryIt method, printing the “OK” or “KO” message.
<%@ page import="it.reggiocity.provincia.biblioreggiane.*"%>
<%
String message = "";
FederaMLOLSoapClient obj= new FederaMLOLSoapClient( );
message = obj.tryIt(“AAAAAA70R10H226H”);
%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1252"%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"/>
<title>prova</title>
</head>
<body><%=message%></body>
</html>
The situation is:
My try_ws_client.jsp runs correctly from my jdeveloper and the user is created while creating app.ear and deploying it to my Oracle AS/OC4J as mentioned above, I get a 500 Internal Server Error.
Any idea to find a solution to this problem?
Please help.
Take care.
John M.

Hi,
you want to build the Web Service, or you want to consume the Service as a client? If the latter, Web client (ADF?) or Java client?
Frank

Error in JAX-WS 2.0 & JDeveloper 10.1.3

Hi!!
I'm trying to generate a SOAP Message with this code:
MessageFactory factory =
MessageFactory.newInstance(SOAPConstants.SOAP_1_1_PROTOCOL);
response = factory.createMessage();
SOAPPart parte =
response.getSOAPPart();
parte.setContent(xmlSource);
response.saveChanges();
in line "response.saveChanges();" i have this error:
16-feb-2007 11:00:21 com.sun.xml.messaging.saaj.soap.EnvelopeFactory
createEnvelope
GRAVE: SAAJ0511: Unable to create envelope from given source
16-feb-2007 11:00:21 com.sun.xml.messaging.saaj.soap.SOAPPartImpl
getContentAsStream
GRAVE: SAAJ0547: Error while trying to externalize
16-feb-2007 11:00:21 com.sun.xml.messaging.saaj.soap.MessageImpl
saveChanges
GRAVE: SAAJ0539: Unable to get header stream in saveChanges
16-feb-2007 11:00:21 com.sun.xml.messaging.saaj.soap.MessageImpl
saveChanges
GRAVE: SAAJ0540: Error during saving a multipart message
It's a web application and i'm debugging with OC4J Standalone from
Jdeveloper. The Libraries are the libs of JAX-WS 2.0 and the orion-
web.xml file has:
<web-app-class-loader search-local-classes-first="true"
include-war-manifest-class-path="true"/>
the exception stack:
07/02/16 11:00:59 java.lang.Exception: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Error during saving a multipart message
07/02/16 11:00:59 at genws.MotorXML.getSOAPMessageFromSource(MotorXML.java:443)
07/02/16 11:00:59 at genws.MotorXML.executeWS(MotorXML.java:232)
07/02/16 11:00:59 at PDFController.process(PDFController.java:321)
07/02/16 11:00:59 at es.jcyl.pdf.PDFServletEngine.service(PDFServletEngine.java:114)
07/02/16 11:00:59 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
07/02/16 11:00:59 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
07/02/16 11:00:59 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
07/02/16 11:00:59 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
07/02/16 11:00:59 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
07/02/16 11:00:59 at java.lang.Thread.run(Thread.java:595)
07/02/16 11:00:59 Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Error during saving a multipart message
07/02/16 11:00:59 at com.sun.xml.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:1126)
07/02/16 11:00:59 at es.jcyl.genws.MotorXML.getSOAPMessageFromSource(MotorXML.java:437)
07/02/16 11:00:59 ... 14 more
07/02/16 11:00:59 Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to get header stream in saveChanges:
07/02/16 11:00:59 at com.sun.xml.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:1096)
07/02/16 11:00:59 ... 15 more
07/02/16 11:00:59 Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: SOAP exception while trying to externalize:
Anybody can help me?
Thanks

The error was in the execution of OC4J embebbed. OC4J uses its own libraries for web services and xml.
You can deploy an application with JAX-WS 2.0 if you add this java option:
-Xbootclasspath/p:<dir_libs>\xml-apis.jar;<dir_libs>\xercesImpl.jar;<dir_libs>\xalan.jar;<dir_libs>\saaj.api.jar
And the jars of JAX-WS are added as libraries to the application.
With this solution you solve the problem: OC4J uses this libraries, not their owns, include the xml libraries.

External Web Service - User and password in HTTP header

Hi!
How is it possible to add user and password in the HTTP header in a external web service call?
I have created a "Portal Service from WSDL file - Client side" with the wizard in SAP Developer Studio. I following the Java Development Guide - Web Service Security, and use the secured service connection. I have also created a new System Landscape, but should the new system be based on HTTP, my own PAR or what?
How can I check that the user and password is added to the HTTP header or the SOAP envelope? Do I have to scan http traffic with a proxy as Paros or can I find the request sent from SAP EP in the logs?
Cheers
Asle

Hello All,
I have been struggling a bit while putting a reasonable security framework on a jax-rpc style web service. I'm using JWSDP1.2 to set up the webservice. I've tried to outline my problem below. Please correct me where I'm wrong.
I've been through the Sun's WS tutorials, but they are not really clear on security. However, from them I surmised that there are two decent authentication techniques. HTTP Basic and mutual authentication (MA) . Both have their drawbacks though. HTTP Basic suffers from poor encryption while MA is a bit difficult to set up on both client and server sides. Another problem with MA is that there is no central repository for users/passwords.
OK, what I would really like to do is use my own user database to verify users/passwords i.e. use a HTTP Basic like authentication (but at application level) but run it over SSL for encryption. It seems simple, but is it possible?
Also, I have noted that when I use HTTP Basic on the service side, and use a java client, then setting username/password has no effect. In other words, I can always access the web-service, even with wrong username/password.
Sorry for the long post. Hope someone can help. Thanks.

"error in processing the WS-Security security header" - calling ws OIPM

Hi All,
We are trying to integrate Ebiz and OIPM, when we send request from ebiz to AxfSolutionMediatorService WebService we are getting below error
InvalidSecurity : error in processing the WS-Security security header
<ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" class="javax.xml.ws.soap.SOAPFaultException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message>InvalidSecurity : error in processing the WS-Security security header</message>
<ns2:stackTrace>
<ns2:frame class="oracle.imaging.common.WSSecurityHandler" file="WSSecurityHandler.java" line="134" method="throwSOAPFaultException"/>
<ns2:frame class="oracle.imaging.common.WSSecurityHandler" file="WSSecurityHandler.java" line="119" method="processHeader"/>
<ns2:frame class="oracle.imaging.axf.ws.AxfSolutionMediatorWS" file="AxfSolutionMediatorWS.java" line="66" method="getUserPrincipal"/>
<ns2:frame class="oracle.imaging.axf.ws.AxfSolutionMediatorWS" file="AxfSolutionMediatorWS.java" line="54" method="execute"/>
<ns2:frame class="sun.reflect.GeneratedMethodAccessor2261" line="unknown" method="invoke"/>
<ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
<ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
<ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="92" method="invoke"/>
<ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="74" method="invoke"/>
<ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="151" method="invoke"/>
<ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl" file="EndpointMethodHandlerImpl.java" line="268" method="invoke"/>
<ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="100" method="processRequest"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="866" method="__doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="815" method="_doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="778" method="doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="680" method="runSync"/>
<ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="403" method="process"/>
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="532" method="handle"/>
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="253" method="handle"/>
<ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
<ns2:frame class="weblogic.wsee.jaxws.WLSServletAdapter" file="WLSServletAdapter.java" line="171" method="handle"/>
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="708" method="run"/>
<ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="363" method="doAs"/>
<ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="146" method="runAs"/>
<ns2:frame class="weblogic.wsee.util.ServerSecurityHelper" file="ServerSecurityHelper.java" line="103" method="authenticatedInvoke"/>
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$3" file="HttpServletAdapter.java" line="311" method="run"/>
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="336" method="post"/>
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="95" method="doRequest"/>
<ns2:frame class="weblogic.servlet.http.AbstractAsyncServlet" file="AbstractAsyncServlet.java" line="99" method="service"/>
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHel
per.java" line="227" method="run"/>
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="300" method="execute"/>
<ns2:frame class="weblogic.servlet.internal.TailFilter" file="TailFilter.java" line="26" method="doFilter"/>
<ns2:frame class="weblogic.servlet.internal.FilterChainImpl" file="FilterChainImpl.java" line="56" method="doFilter"/>
<ns2:frame class="oracle.security.jps.ee.http.JpsAbsFilter$1" file="JpsAbsFilter.java" line="111" method="run"/>
<ns2:frame class="java.security.AccessController" file="AccessController.java" line="native" method="doPrivileged"/>
<ns2:frame class="oracle.security.jps.util.JpsSubject" file="JpsSubject.java" line="313" method="doAsPrivileged"/>
<ns2:frame class="oracle.security.jps.ee.util.JpsPlatformUtil" file="JpsPlatformUtil.java" line="413" method="runJaasMode"/>
<ns2:frame class="oracle.security.jps.ee.http.JpsAbsFilter" file="JpsAbsFilter.java" line="94" method="runJaasMode"/>
<ns2:frame class="oracle.security.jps.ee.http.JpsAbsFilter" file="JpsAbsFilter.java" line="161" method="doFilter"/>
<ns2:frame class="oracle.security.jps.ee.http.JpsFilter" file="JpsFilter.java" line="71" method="doFilter"/>
<ns2:frame class="weblogic.servlet.internal.FilterChainImpl" file="FilterChainImpl.java" line="56" method="doFilter"/>
<ns2:frame class="oracle.dms.servlet.DMSServletFilter" file="DMSServletFilter.java" line="136" method="doFilter"/>
<ns2:frame class="weblogic.servlet.internal.FilterChainImpl" file="FilterChainImpl.java" line="56" method="doFilter"/>
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3715" method="wrapRun"/>
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3681" method="run"/>
<ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
<ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="120" method="runAs"/>
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2277" method="securedExecute"/>
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2183" method="execute"/>
<ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1454" method="run"/>
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="209" method="execute"/>
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="178" method="run"/>
</ns2:stackTrace>
</ns2:exception>
The request which we are sending is
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><Security xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><UsernameToken> <Username>AXF</Username> <Password>AXF</Password> </UsernameToken> </Security></soap:Header><soap:Body><execute xmlns="http://service.axf.imaging.oracle/"><request xmlns=""><commandNamespace>UCM_Managed_Attachments</commandNamespace><conversationId></conversationId><requestParameters></requestParameters><role>guest</role><solutionNamespace>UCM_Managed_Attachments</solutionNamespace><systemName>Oracle</systemName><userContext><entry><key>RESP_ID</key><value>50554</value></entry><entry><key>RESP_APPL_ID</key><value>200</value></entry><entry><key>ORG_ID</key><value>204</value></entry><entry><key>USR_ID</key><value>1318</value></entry></userContext><username>operations</username></request></execute></soap:Body></soap:Envelope>
Thanks in Advance,
Rakesh.

I know you've probably solved this but I'll post our working soap message below for others.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:imag="http://imaging.oracle/">
<soapenv:Header xmlns:ns0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:UsernameToken>
<wsse:Username>Username</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">Password</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<imag:getDocument>
<documentId>4.IPM_004280</documentId>
<sectionSet>
<flags>HISTORY</flags>
<flags>FIELDVALUES</flags>
</sectionSet>
</imag:getDocument>
</soapenv:Body>
</soapenv:Envelope>

Exapmle for SOAP Header in WS using JAXRPC Handler

Any one has example of how to use the SOAP Header in Webservice implementation using the JAX RPC handler?
We have a situation where several PL/SQL web services require some context being set in the PL/SQL package. I am planning to use the PL/SQL web service with some soap headers , when present the Handler will take those values from the SOAP header and make the extra pl/sql calls, before the BODY which will be mapped to the pl/sql procedure whose response will be sent back as the WS response..
I will really appreciate if some one show me the example on how to use the JAXRPC handler in JDEV.
Thank you very much.

Probably the easiest way is to insert
@Resource
WebServiceContext wsc;
in your @WebService annotated class.
Depending what you want to do a SOAPHandler might be appropriate.
also possible:
http://www.khapre.org/blog/archives/2008_08_01_index.aspx
Edited by: Konrad KRENTZ on Dec 1, 2009 8:56 PM

Error in oc4j standalone & JAX-WS 2.0

Hi!!
I'm trying to generate a SOAP Message with this code:
MessageFactory factory =
MessageFactory.newInstance(SOAPConstants.SOAP_1_1_PROTOCOL);
response = factory.createMessage();
SOAPPart parte =
response.getSOAPPart();
parte.setContent(xmlSource);
response.saveChanges();
in line "response.saveChanges();" i have this error:
16-feb-2007 11:00:21 com.sun.xml.messaging.saaj.soap.EnvelopeFactory
createEnvelope
GRAVE: SAAJ0511: Unable to create envelope from given source
16-feb-2007 11:00:21 com.sun.xml.messaging.saaj.soap.SOAPPartImpl
getContentAsStream
GRAVE: SAAJ0547: Error while trying to externalize
16-feb-2007 11:00:21 com.sun.xml.messaging.saaj.soap.MessageImpl
saveChanges
GRAVE: SAAJ0539: Unable to get header stream in saveChanges
16-feb-2007 11:00:21 com.sun.xml.messaging.saaj.soap.MessageImpl
saveChanges
GRAVE: SAAJ0540: Error during saving a multipart message
It's a web application and i'm debugging with OC4J Standalone from
Jdeveloper. The Libraries are the libs of JAX-WS 2.0 and the orion-
web.xml file has:
<web-app-class-loader search-local-classes-first="true"
include-war-manifest-class-path="true"/>
the exception stack:
07/02/16 11:00:59 java.lang.Exception: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Error during saving a multipart message
07/02/16 11:00:59 at genws.MotorXML.getSOAPMessageFromSource(MotorXML.java:443)
07/02/16 11:00:59 at genws.MotorXML.executeWS(MotorXML.java:232)
07/02/16 11:00:59 at PDFController.process(PDFController.java:321)
07/02/16 11:00:59 at es.jcyl.pdf.PDFServletEngine.service(PDFServletEngine.java:114)
07/02/16 11:00:59 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
07/02/16 11:00:59 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
07/02/16 11:00:59 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
07/02/16 11:00:59 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
07/02/16 11:00:59 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
07/02/16 11:00:59 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
07/02/16 11:00:59 at java.lang.Thread.run(Thread.java:595)
07/02/16 11:00:59 Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Error during saving a multipart message
07/02/16 11:00:59 at com.sun.xml.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:1126)
07/02/16 11:00:59 at es.jcyl.genws.MotorXML.getSOAPMessageFromSource(MotorXML.java:437)
07/02/16 11:00:59 ... 14 more
07/02/16 11:00:59 Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to get header stream in saveChanges:
07/02/16 11:00:59 at com.sun.xml.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:1096)
07/02/16 11:00:59 ... 15 more
07/02/16 11:00:59 Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: SOAP exception while trying to externalize:
Anybody can help me?
Thanks

The error was in the execution of OC4J embebbed. OC4J uses its own libraries for web services and xml.
You can deploy an application with JAX-WS 2.0 if you add this java option:
-Xbootclasspath/p:<dir_libs>\xml-apis.jar;<dir_libs>\xercesImpl.jar;<dir_libs>\xalan.jar;<dir_libs>\saaj.api.jar
And the jars of JAX-WS are added as libraries to the application.
With this solution you solve the problem: OC4J uses this libraries, not their owns, include the xml libraries.

JAX-WS proxy and WS-ReliableMessaging

Hello all,
JDeveloper 11.1.2.3
I've started the foray into looking at reliable web services as specified by WS-ReliableMessaging. I have a very simple Hello World web service deployed (it was written in C# and deployed on IIS, if you have to ask :P). In JDeveloper, I've generated a JAX-WS Style proxy and test class using the JDeveloper wizard to do so. I've specified that no Async methods be generated and that there are no client OWSM policies (none are deemed compatible with the web service anyway).
I then add a bit of code to my test class and run to test. The first time I run the class, the WS calls work successfully, although after the sequence of calls, I get an exception displayed in the console (see below). If I try to run the class again, the web service calls don't even execute and I get a different exception in the console (again, see below - at least part of this error is captured by my ReliabilityErrorListener). This sequence of events alternates ad-infinitum (odd-numbered attempts work with an exception, even-numbered attempts don't work.
I show my test code here:
 // Add your code to call the desired methods.
 WsrmClientInitFeature f = new WsrmClientInitFeature(true);
 ReliabilityErrorListener listener = new ReliabilityErrorListener()
 public void onReliabilityError(ReliabilityErrorContext context)
 // At a *minimum* do this
 System.out.println("RM sequence failure: " + context.getFaultSummaryMessage());
 // And optionally do this...
 // The context parameter tells you whether a request or the entire
 // sequence has failed. If a sequence fails, you'll get a notification
 // for each undelivered request (if any) on the sequence.
 if (context.isRequestSpecific())
 // We have a single request failure (possibly as part of a larger
 // sequence failure).
 // We can get the original request back like this:
 String operationName = context.getOperationName();
 System.out.println("Failed to deliver request for operation '" + operationName + "'. Fault summary: " +
 context.getFaultSummaryMessage());
 else
 // The entire sequence has encountered an error.
 System.out.println("Entire sequence failed: " + context.getFaultSummaryMessage());
 f.setErrorListener(listener);
 hello = helloService.getWSHttpBindingHello(f);
 WsrmClient c = WsrmClientFactory.getWsrmClientFromPort(hello);
 System.out.println("Sequence ID is " + c.getSequenceId());
 // c.reset();
 System.out.println(hello.getGreeting("John"));
 System.out.println(hello.getGreeting("Fred"));
 System.out.println(hello.getGreeting("Josephine"));
 System.out.println("Sequence ID is " + c.getSequenceId());
 try
 System.out.println(c.getAckRanges().first().lowerBounds);
 System.out.println(c.getAckRanges().first().upperBounds);
 catch (Exception e)
 // c.setFinalMessage();The calls that work look like this in the console:
Sequence ID is null
<05-Mar-2013 14:55:53 o'clock EAT> <Info> <Store> <BEA-280008> <Opening the persistent file store "weblogic.wsee.persistence.WseeFileStore" for recovery: directory=C:\JDeveloper\11.1.2.3\mywork\WSReliableClientPOC\Client requestedWritePolicy="Cache-Flush" fileLockingEnabled=true driver="NIO".>
<05-Mar-2013 14:55:53 o'clock EAT> <Info> <Store> <BEA-280009> <The persistent file store "weblogic.wsee.persistence.WseeFileStore" (569ea4fb-b0fd-4906-bb74-003b6885b1d5) has been opened: blockSize=512 actualWritePolicy="Cache-Flush(single-handle-non-direct)" explicitIOEnforced=false records=57.>
Hello, John. You have just communicated with me using WS-reliablemessaging
Hello, Fred. You have just communicated with me using WS-reliablemessaging
Hello, Josephine. You have just communicated with me using WS-reliablemessaging
Sequence ID is uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffd
1
3
<05-Mar-2013 14:56:03 o'clock EAT> <Error> <WseeRm> <BEA-224016> <An unexpected error occurred: weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
 at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.getConversation(DefaultSendingServiceProvider.java:222)
 at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.stopConversation(DefaultSendingServiceProvider.java:287)
 at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:257)
 at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
 at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
 at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
 at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
 at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
 at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
 at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
<05-Mar-2013 14:56:03 o'clock EAT> <Error> <WseePersist> <BEA-221000> <An unexpected error occurred: java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@6ac27081 - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@6ac27081 - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
 at weblogic.wsee.reliability2.sequence.Sequence.removePropertyChangeListener(Sequence.java:1250)
 at weblogic.wsee.reliability2.store.SequenceMap.shutdownSequence(SequenceMap.java:558)
 at weblogic.wsee.reliability2.store.TimedSequenceMap.shutdownSequence(TimedSequenceMap.java:182)
 at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:274)
 at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
 at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
 at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
 at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
 at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
 at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
 at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
Process exited with exit code 0.The calls that don't work look like this:
Sequence ID is null
<05-Mar-2013 14:57:49 o'clock EAT> <Info> <Store> <BEA-280008> <Opening the persistent file store "weblogic.wsee.persistence.WseeFileStore" for recovery: directory=C:\JDeveloper\11.1.2.3\mywork\WSReliableClientPOC\Client requestedWritePolicy="Cache-Flush" fileLockingEnabled=true driver="NIO".>
<05-Mar-2013 14:57:49 o'clock EAT> <Info> <Store> <BEA-280009> <The persistent file store "weblogic.wsee.persistence.WseeFileStore" (569ea4fb-b0fd-4906-bb74-003b6885b1d5) has been opened: blockSize=512 actualWritePolicy="Cache-Flush(single-handle-non-direct)" explicitIOEnforced=false records=59.>
RM sequence failure:
weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
Failed to deliver request for operation 'GetGreeting'. Fault summary:
weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
Exception in thread "main" java.lang.AssertionError: weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
 at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:689)
 at com.sun.xml.ws.client.Stub.process(Stub.java:272)
 at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
 at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
 at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
 at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
 at $Proxy36.getGreeting(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
 at $Proxy35.getGreeting(Unknown Source)
 at org.tempuri.WSHttpBinding_HelloClient.main(WSHttpBinding_HelloClient.java:96)
Caused by: weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
 at weblogic.wsee.reliability2.store.SourceSequenceSender.checkForPermanentSendFailure(SourceSequenceSender.java:549)
 at weblogic.wsee.reliability2.store.SourceSequenceSender.handleFailureForSuspendedFiber(SourceSequenceSender.java:604)
 at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponseForSuspendedFiber(SourceSequenceSender.java:452)
 at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponse(SourceSequenceSender.java:293)
 at weblogic.wsee.reliability2.store.SourceSequenceSender.send(SourceSequenceSender.java:184)
 at weblogic.wsee.sender.DefaultProvider.Conversation.sendOneRequest(Conversation.java:671)
 at weblogic.wsee.sender.DefaultProvider.Conversation.sendPendingRequests(Conversation.java:579)
 at weblogic.wsee.sender.DefaultProvider.Conversation.access$1400(Conversation.java:44)
 at weblogic.wsee.sender.DefaultProvider.Conversation$2.timerExpired(Conversation.java:476)
 at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
 at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
 at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:258)
 at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:273)
 at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponseForSuspendedFiber(SourceSequenceSender.java:442)
 ... 10 more
Caused by: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
 at weblogic.wsee.reliability2.tube.WsrmTubelineDeploymentListener$WsrmClientProtocolTube.processResponse(WsrmTubelineDeploymentListener.java:222)
 at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:877)
 at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
 at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
 at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
 at com.sun.xml.ws.client.Stub.process(Stub.java:272)
 at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:238)
 ... 12 more
<05-Mar-2013 14:57:58 o'clock EAT> <Error> <WseeRm> <BEA-224016> <An unexpected error occurred: weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
 at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.getConversation(DefaultSendingServiceProvider.java:222)
 at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.stopConversation(DefaultSendingServiceProvider.java:287)
 at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:257)
 at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
 at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
 at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
 at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
 at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
 at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
 at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
<05-Mar-2013 14:57:58 o'clock EAT> <Error> <WseePersist> <BEA-221000> <An unexpected error occurred: java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@79424b7b - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@79424b7b - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
 at weblogic.wsee.reliability2.sequence.Sequence.removePropertyChangeListener(Sequence.java:1250)
 at weblogic.wsee.reliability2.store.SequenceMap.shutdownSequence(SequenceMap.java:558)
 at weblogic.wsee.reliability2.store.TimedSequenceMap.shutdownSequence(TimedSequenceMap.java:182)
 at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:274)
 at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
 at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
 at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
 at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
 at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
 at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
 at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
Process exited with exit code 1.Does anyone have any insight about this behaviour?
Thanks,
John

Some additional information for the second case. Using HTTP analyzer in JDeveloper, I can see 2 HTTP POSTs going to the web service. The first one is to initiate the WS-RM sequence and shows an offered conversation identifier and the reply shows that the server has given its own identifier instead of the offered one:
request:
POST http://xgis-lel-05717.ad.xglobal.com:80/WSReliablePOC/HelloService.svc HTTP/1.1
Proxy-Authorization:
Content-type: application/soap+xml;charset="utf-8";action="http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence"
Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Host: xgis-lel-05717.ad.xglobal.com
Proxy-Connection: Keep-Alive
Content-Length: 1620
X-HTTPAnalyzer-Rules: 1@localhost:8099
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
 <env:Header>
 <wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" env:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
 <wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffb</wsa:MessageID>
 <wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</wsa:To>
 <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
 <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
 </ReplyTo>
 <FaultTo xmlns="http://www.w3.org/2005/08/addressing">
 <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
 </FaultTo>
 </env:Header>
 <env:Body xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
 <wsrm:CreateSequence>
 <wsrm:AcksTo xmlns:wsa="http://www.w3.org/2005/08/addressing">
 <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
 <wsa:ReferenceParameters xmlns:clspi="http://www.oracle.com/wsee/jaxws/cluster/spi">
 <clspi:PhysicalStoreName
 xmlns:wsa="http://www.w3.org/2005/08/addressing"
 xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" wsa:IsReferenceParameter="true">WseeFileStore</clspi:PhysicalStoreName>
 </wsa:ReferenceParameters>
 </wsrm:AcksTo>
 <wsrm:Expires>P1D</wsrm:Expires>
 <wsrm:Offer>
 <wsrm:Identifier>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffe</wsrm:Identifier>
 <wsrm:Expires>P1D</wsrm:Expires>
 </wsrm:Offer>
 </wsrm:CreateSequence>
 </env:Body>
</env:Envelope>
reply:
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Cache-Control: private
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
Content-Length: 673
Server: Microsoft-IIS/7.5
Date: Tue, 05 Mar 2013 12:10:44 GMT
X-HTTPAnalyzer-RuleName: Pass through :
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
 <s:Header>
 <a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse</a:Action>
 <a:RelatesTo>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffb</a:RelatesTo>
 </s:Header>
 <s:Body>
 <CreateSequenceResponse xmlns="http://schemas.xmlsoap.org/ws/2005/02/rm">
 <Identifier>urn:uuid:b6886ed1-6cf2-40a4-99a3-f17cc5a295d7</Identifier>
 <Expires>P1D</Expires>
 <Accept>
 <AcksTo>
 <a:Address>http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</a:Address>
 </AcksTo>
 </Accept>
 </CreateSequenceResponse>
 </s:Body>
</s:Envelope>The second POST shows the JDeveloper proxy calling the web service and sending a wsrm:Identifier value that the one originally offered by JDeveloper (see the sequence acknowledgement), not the one the server advised to use:
request:
POST http://xgis-lel-05717.ad.xglobal.com:80/WSReliablePOC/HelloService.svc HTTP/1.1
Proxy-Authorization:
Content-type: application/soap+xml;charset="utf-8";action="http://tempuri.org/Hello/GetGreeting"
Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Host: xgis-lel-05717.ad.xglobal.com
Proxy-Connection: Keep-Alive
Content-Length: 1444
X-HTTPAnalyzer-Rules: 1@localhost:8099
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">
 <S:Header>
 <wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</wsa:To>
 <wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://tempuri.org/Hello/GetGreeting</wsa:Action>
 <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
 <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
 </ReplyTo>
 <FaultTo xmlns="http://www.w3.org/2005/08/addressing">
 <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
 </FaultTo>
 <wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffc</wsa:MessageID>
 <wsrm:SequenceAcknowledgement xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
 <wsrm:Identifier>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-725c9c83:13d3a75543c:-7ffe</wsrm:Identifier>
 <wsrm:AcknowledgementRange Lower="1" Upper="3"/>
 </wsrm:SequenceAcknowledgement>
 <wsrm:Sequence
 xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm" S:mustUnderstand="true">
 <wsrm:Identifier>urn:uuid:b6886ed1-6cf2-40a4-99a3-f17cc5a295d7</wsrm:Identifier>
 <wsrm:MessageNumber>1</wsrm:MessageNumber>
 </wsrm:Sequence>
 </S:Header>
 <S:Body>
 <GetGreeting
 xmlns:ns2="http://schemas.microsoft.com/2003/10/Serialization/" xmlns="http://tempuri.org/">
 <name>John</name>
 </GetGreeting>
 </S:Body>
</S:Envelope>
response:
HTTP/1.1 500 Internal Server Error
Content-Type: application/soap+xml; charset=utf-8
Cache-Control: private
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
Content-Length: 710
Server: Microsoft-IIS/7.5
Date: Tue, 05 Mar 2013 12:10:52 GMT
X-HTTPAnalyzer-RuleName: Pass through :
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
 <s:Header>
 <a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
 </s:Header>
 <s:Body>
 <s:Fault>
 <s:Code>
 <s:Value>s:Sender</s:Value>
 <s:Subcode>
 <s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/rm">a:UnknownSequence</s:Value>
 </s:Subcode>
 </s:Code>
 <s:Reason>
 <s:Text xml:lang="en-GB">The value of wsrm:Identifier is not a known Sequence identifier.</s:Text>
 </s:Reason>
 <s:Detail>
 <r:Identifier xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-725c9c83:13d3a75543c:-7ffe</r:Identifier>
 </s:Detail>
 </s:Fault>
 </s:Body>
</s:Envelope>This seems to be an issue in the JDev-generated Proxy (still need to find out why it happens "every other time" and not "every time." The time it works, JDeveloper is sending the Identifier returned by the service. The time it works, however - you can also see that the "conversation not found" exception is referring to the original "offered" identifier and not the one that was used in the conversation. I'm now starting to suspect that the proxy generation for WS-RM may be a bit buggy. Anyone else with experience in this area?
A quick look at support.oracle.com does find note 1082278.1 which although for old versions of WebLogic, that WS-RM isn't supported for JAX-WS in WLS, but is supported for JAX-RPC. Since this seems to be for publishing web services, it is not at all clear as to whether this applies to me. In any case, the JDeveloper WS proxy wizard won't let me generate a JAX-RPC proxy, instead saying that the WSDL has no SOAP 1.1 bindings (which is correct, it has SOAP 1.2 bindings).
John
John

Jax ws header

Similar Messages

Maybe you are looking for