JAX-WS 2.0 support

I have set of BPEL processes which should talk to the Asynchronous Web Services. Does Oracle support JAX-WS 2.0?
-Anil

We will support JAX-WS in our next generation fusion stack (named 11) so not for now unfortunately .. but we support async call outs / receives based on WSA (means as long as your service expects WSA headers everything shoudl work out fine)
hth clemens

Similar Messages

JAX-RPC, JAXM, JAXR supported in WLS6.1?

Does wls6.1 support JAX API's? If not, when will they be supported? Thanks much.
Siming

Hi Siming,
The JAX Pack (i.e. JAX-RPC, JAXM, JAXB, JAXR, etc.) are still merely JSRs, with
no "real" consensus on whether they will ever be otherwise. This being the case,
it is unlikely that you will see support for them in WebLogic Server, in the near
future (3 to 6 months). You can always run the Sun RIs (Reference Implementations)
under WebLogic Server (I have done this with both JAXB and JAXM), if you would
like to experiment with these technologies.
Regards,
Mike Wooten
"Siming Mu" <[email protected]> wrote:
>
Does wls6.1 support JAX API's? If not, when will they be supported?
Thanks much.
Siming

Why does jax-ws not support bpel

I would like to put my jax-ws services in some bpel process, but I've read in JBoss forum that jax-ws doesn't support BPEL. Why is it so? Can anybody explain it to me ? Why putting BPEL into JBI module "saves the situation"?
I would be gratefull for any kind of articles, links, explanations...
Thanks,
Kasia

Well, they can - I use it on the machine to watch videos and to read while exercising, without the Nike+ app. The Nike app measures the distance you've travelled, doesn't it? Would it work on a treadmill, in which you're not really travelling any distance? I can't remember the specifics... but in any event, you should be able to run the iPhone app on the app, the display just won't be optimized for the iPad.

Https transport support for JAX-WS WebServices

Hi All ,
I am trying to implement JAX-WS WebServices that support https transport .To do so I added the following annotation *@Policy(uri = "policy:Wssp1.2-2007-Https-BasicAuth.xml)* in my Jws Implementation file for the JAX-WS WebServices but I got parsing error.Can anyone please confirm that JAX-WS supports the policy annotation in Impl file.If it is supported can a link/pointer/example could be given to implement https enabled JAX-WS WebService and the required configuration in wsdl file.
Thanks and Regards

It does but you've specified a policy that uses both HTTPS and basic HTTP authentication. If you require just HTTPS use "Wssp1.2-Https.xml". In turn you must enable the SSL port on the WLS server. See this blog post: http://one-size-doesnt-fit-all.blogspot.com/2009/02/enabling-ssl-and-disabling-non-ssl_17.html
If you use JDev to generate the JAX-WS web services, given the policy annotation JDev willl put the policy in the WSDL file appropriately.
CM.

Weblogic 10.3TP, JAX-WS and Spring integration

Hi all
We are using JAX-WS and Spring (2.0.6) and our target platform will be Weblogic 10.3. We would like to benefit from Spring injection in our web service classes. However I cannot get it to work. I follow the instructions described here: [url https://jax-ws-commons.dev.java.net/spring]https://jax-ws-commons.dev.java.net/spring and I use version 1.7 of jaxws-spring
When deploying the sample project I get the following error:
2007-12-06 09:28:42,238 ERROR [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'com.sun.xml.ws.transport.http.servlet.SpringBinding' defined in ServletContext resource [WEB-INF/applicationContext.xml]:
Cannot create inner bean '(inner bean)' of type [org.jvnet.jax_ws_commons.spring.SpringService] while setting bean property 'service';
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation;
nested exception is java.lang.ClassCastException: org.jvnet.jax_ws_commons.spring.SpringService$ContainerWrapper cannot be cast to weblogic.wsee.jaxws.WLSContainer
Caused by:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation;
nested exception is java.lang.ClassCastException: org.jvnet.jax_ws_commons.spring.SpringService$ContainerWrapper cannot be cast to weblogic.wsee.jaxws.WLSContainer
Caused by:
java.lang.ClassCastException: org.jvnet.jax_ws_commons.spring.SpringService$ContainerWrapper cannot be cast to weblogic.wsee.jaxws.WLSContainer
        at weblogic.wsee.jaxws.framework.policy.WSDLGeneratorExtension.start(WSDLGeneratorExtension.java:113)
        at com.sun.xml.ws.wsdl.writer.WSDLGeneratorExtensionFacade.start(WSDLGeneratorExtensionFacade.java:67)
        at com.sun.xml.ws.wsdl.writer.WSDLGenerator.generateDocument(WSDLGenerator.java:353)
        at com.sun.xml.ws.wsdl.writer.WSDLGenerator.doGeneration(WSDLGenerator.java:276)
        at com.sun.xml.ws.server.EndpointFactory.generateWSDL(EndpointFactory.java:427)
        at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:196)
        at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
        at org.jvnet.jax_ws_commons.spring.SpringService.getObject(SpringService.java:333)
        at org.jvnet.jax_ws_commons.spring.SpringService.getObject(SpringService.java:45)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectFromFactoryBean(AbstractBeanFactory.java:1236)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1207)
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:219)
...It sounds like JAX-WS - Spring integration is not supported in Weblogic 10.3TP.
Has anyone been able to get the sample project working?
Does anyone know if the final version of Weblogic 10.3 will have JAX-WS Spring injection support?
Thanks
Dries

anybody can help?
thanks

How to ignore extra WSDL operation when using JAX-WS?

Hello,
I'm migrating from Apache Axis2 to JAX-WS and i'm having the following issue:
I have a large WSDL file of size = 140 KB, however my client application invokes only 2 operations, so i removed all the other operations from the WSDL.
I successfully generated the stubs using "*wsimport* on the trimmed WSDL, and i put the original WSDL location in the +Service+ constructor:
MyService stub = new MyService(new URL(<original WSDL location>), new QName(<package>, <MyServiceName>));
when i ran the client, i got the following exception:
The Endpoint validation failed to validate due to the following errors: :: Invalid Endpoint Interface :: :: The operation names in the WSDL portType do not match the method names in the SEI or Web service implementation class.
Because of that, i got the original WSDL again, run *wsimport" on it, but it fails this time, with this error:
[ERROR] undefined simple or complex type 'soapenc:Array'
line 1086 of file:/root/DecisionControllerWS.wsdl
Googling the error, JAX-WS doesn't support RPC/Encoding.
So i'm stuck here, can't work with the trimmed WSD, can't generate the stubs with the full WSDL!
Any advise? thanks in advance.

I'm not a WSDL guru, but it seems that the location of the web service implementation is defaulted to the local host in the WSDL:
<port binding="s0:DecisionControllerWSSoapBinding" name="DecisionControllerWS">
<s1:address location="http://localhost:7001/rtds/webservices-adapter/DecisionControllerWS"/>
</port>
That's why i put the original WSDL location when i created the service, to point to the web service implementation, Was i wrong? because i found a property which can achieve that for me:
javax.xml.ws.BindingProvider.ENDPOINT_ADDRESS_PROPERTY
What if i edited the address location in the trimmed WSDL to point to the implementation, and used the default Service constructor to point to the local trimmed WSD file?

Policy Annotation in WebServices Impl file for JAX-WS WebServices

Hi All ,
I am trying to implement JAX-WS WebServices that support https transport .To do so I added the following annotation *@Policy(uri = "policy:Wssp1.2-2007-Https-BasicAuth.xml)* in my Jws Implementation file for the JAX-WS WebServices but I got parsing error.Can anyone please confirm that JAX-WS supports the policy annotation in Impl file.If it is supported can a link/pointer/example could be given to implement https enabled JAX-WS WebService and the required configuration in wsdl file.
Thanks and Regards

For 11g, install the examples with a custom installation (have to specify that check mark that is not checked by default).
The look here:
<MIDDLEWARE_HOME>\wlserver_10.3\samples\server\examples\src\examples\webservices\wss1.1

Request/Response From Long running Service to BPEL

Hi,
I have long running web service which I plan to implement as a EJB30 Webservice.
I need to add support for Async callback Repsonse to the BPEL process calling this ejb service.
Since jax-ws is not supported by the current version of Oracle I cannot use that.
Can I use the Java concurrent api in side the EJB and implement the EJB as a stateful EJB with support for WS-Addressing?
I do not want to use the JMS, becuse of the additional coding of multiple Message beans to send and receive the message.
What other options do I have here?

<con:fault xmlns:con="http://www.bea.com/wli/sb/context"> is an osb internal fault and not a soap:Fault
BPEL process will fault if it receives either a soap:fault or a custom fault defined in the wsdl. so change your proxy service error handling to replace $body to one of these.
If you don't have reply with failure action, osb will return a soap:Fault ( generated by the system error handler) and bpel will fault , but the error info in $fault will be lost..
One way to address this is to define a Fault message for the service in the wsdl ( port type will have input, output and fault elements for the operation) and in the osb error handler transform $ fault to the fault message format and do a reply.

Using Studio to develop DII Client for DiningGuide example

Hi,
I am trying to develop a DII client to the DiningGuide example from the Java Studio Enterprise Tutorials and Code Camps:
http://developers.sun.com/prodtech/javatools/jsenterprise/learning/tutorials/index.html
I am using Studio6 with Application Server 7 update 3 with Java WSDP 1.3 [JAX-RPC 1.1 support]
The question is how does Studio support JAX-RPC DII client development ? I understand that the config.xml file is different between Static stub based client and a DII client. Please let me know as to how to configure
Studio to do this.
Below is the code that is new in the DIIClient shown in 3 sections:
- imports area in CustomerReviewTable.java
- getCustomerReviewByName method in CustomerReviewTable.java
[Basically taking the code from
http://java.sun.com/webservices/docs/1.0/tutorial/doc/JAXRPC6.html#75222
and modifying this to use this service and make appropriate
changes for the return value (Vector).
I suspect that this is where the problem is but need help to fix
it. - Thanks!!]
- Variables declaration new for DIIClient
- The WSDL for the DGWebService service is also shown
I tried it with both JAXRPC 1.0 and JAXRPC 1.1 [Setting this for the
Service in Studio 6] and regenerating the Service code
but did not see any difference.
Right now, with the code shown below, I do not get any exceptions, but
it doesnot show any reviews [Vector returned is null].
Really appreciate your help,
Sridhar.
============ imports area in CustomerReviewTable.java ===============
package DIIClient;
import javax.swing.table.*;
import java.util.*;
import WebService.DGWebServiceClientGenClient.*;
/* New for DII */
import javax.xml.rpc.Call;
import javax.xml.rpc.Service;
import javax.xml.rpc.JAXRPCException;
import javax.xml.namespace.QName;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.ParameterMode;
========= getCustomerReviewByName method in CustomerReviewTable.java
=========
private Vector getCustomerReviewByName(java.lang.String
restaurantname) {
Vector custList = new Vector();
try {
/* Old Static Stub in the Swing Client that works:
WebService.DGWebServiceClientGenClient.DGWebService service2
= new
WebService.DGWebServiceClientGenClient.DGWebService_Impl();
WebService.DGWebServiceClientGenClient.DGWebServiceServantInterface
port = service2.getDGWebServiceServantInterfacePort();
custList =
(java.util.Vector)port.getCustomerreviewsByRestaurant(restaurantname);
/* New DII Code below ... */
System.out.println("Now using DII Code ...");
ServiceFactory factory = ServiceFactory.newInstance();
Service service = factory.createService(new
QName(qnameService));
QName port = new QName(qnamePort);
Call call = service.createCall(port);
call.setTargetEndpointAddress(endPointAddress);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new
Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
QName QNAME_TYPE_VECTOR = new QName(NS_XSD, "vector");
call.setReturnType(QNAME_TYPE_VECTOR);
call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
"getCustomerreviewsByRestaurant"));
call.addParameter("String_1", QNAME_TYPE_STRING,
ParameterMode.IN);
String[] params = { restaurantname };
custList = (java.util.Vector) call.invoke (params);
System.out.println(custList);
catch (Exception ex) {
System.err.println("Caught an exception." );
ex.printStackTrace();
return custList;
============ Variables declaration new for DIIClient ====================
//Variables declaration new for DIIClient
private static String qnameService = "DGWebService";
private static String qnamePort = "DGWebServiceServantInterface";
private static String endPointAddress =
"http://localhost:80/DGWebService/DGWebService";
private static String BODY_NAMESPACE_VALUE = "urn:DGWebService/wsdl";
private static String ENCODING_STYLE_PROPERTY =
"javax.xml.rpc.encodingstyle.namespace.uri";
// private static String NS_XSD = "http://www.w3.org/2001/XMLSchema";
private static String NS_XSD =
"http://java.sun.com/jax-rpc-ri/internal";
private static String URI_ENCODING =
"http://schemas.xmlsoap.org/soap/encoding/";
//http://schemas.xmlsoap.org/soap/encoding/
//http://java.sun.com/jax-rpc-ri/internal
============ The WSDL for the DGWebService service =================
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="DGWebService" targetNamespace="urn:DGWebService/wsdl"
xmlns:tns="urn:DGWebService/wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns2="http://java.sun.com/jax-rpc-ri/internal"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:ns3="urn:DGWebService/types">
<types>
<schema targetNamespace="http://java.sun.com/jax-rpc-ri/internal"
xmlns:tns="http://java.sun.com/jax-rpc-ri/internal"
xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<import namespace="urn:DGWebService/types"/>
<complexType name="vector">
<complexContent>
<extension base="tns:list">
<sequence/></extension></complexContent></complexType>
<complexType name="list">
<complexContent>
<extension base="tns:collection">
<sequence/></extension></complexContent></complexType>
<complexType name="collection">
<complexContent>
<restriction base="soap11-enc:Array">
<attribute ref="soap11-enc:arrayType"
wsdl:arrayType="anyType[]"/></restriction></complexContent></complexType></schema>
<schema targetNamespace="urn:DGWebService/types"
xmlns:tns="urn:DGWebService/types"
xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<import namespace="http://java.sun.com/jax-rpc-ri/internal"/>
<complexType name="CustomerreviewDetail">
<sequence>
<element name="customername" type="string"/>
<element name="restaurantname" type="string"/>
<element name="review" type="string"/>
<element name="sampleProperty"
type="string"/></sequence></complexType>
<complexType name="RestaurantDetail">
<sequence>
<element name="address" type="string"/>
<element name="cuisine" type="string"/>
<element name="description" type="string"/>
<element name="neighborhood" type="string"/>
<element name="phone" type="string"/>
<element name="rating" type="int"/>
<element name="restaurantname" type="string"/>
<element name="sampleProperty"
type="string"/></sequence></complexType></schema></types>
<message name="DGWebServiceServantInterface_createCustomerreview">
<part name="String_1" type="xsd:string"/>
<part name="String_2" type="xsd:string"/>
<part name="String_3" type="xsd:string"/></message>
<message
name="DGWebServiceServantInterface_createCustomerreviewResponse"/>
<message name="DGWebServiceServantInterface_getAllRestaurants"/>
<message name="DGWebServiceServantInterface_getAllRestaurantsResponse">
<part name="result" type="ns2:vector"/></message>
<message name="DGWebServiceServantInterface_getCustomerreviewDetail"/>
<message
name="DGWebServiceServantInterface_getCustomerreviewDetailResponse">
<part name="result" type="ns3:CustomerreviewDetail"/></message>
<message
name="DGWebServiceServantInterface_getCustomerreviewsByRestaurant">
<part name="String_1" type="xsd:string"/></message>
<message
name="DGWebServiceServantInterface_getCustomerreviewsByRestaurantResponse">
<part name="result" type="ns2:vector"/></message>
<message name="DGWebServiceServantInterface_getRestaurantDetail"/>
<message name="DGWebServiceServantInterface_getRestaurantDetailResponse">
<part name="result" type="ns3:RestaurantDetail"/></message>
<portType name="DGWebServiceServantInterface">
<operation name="createCustomerreview" parameterOrder="String_1
String_2 String_3">
<input
message="tns:DGWebServiceServantInterface_createCustomerreview"/>
<output
message="tns:DGWebServiceServantInterface_createCustomerreviewResponse"/></operation>
<operation name="getAllRestaurants">
<input message="tns:DGWebServiceServantInterface_getAllRestaurants"/>
<output
message="tns:DGWebServiceServantInterface_getAllRestaurantsResponse"/></operation>
<operation name="getCustomerreviewDetail">
<input
message="tns:DGWebServiceServantInterface_getCustomerreviewDetail"/>
<output
message="tns:DGWebServiceServantInterface_getCustomerreviewDetailResponse"/></operation>
<operation name="getCustomerreviewsByRestaurant"
parameterOrder="String_1">
<input
message="tns:DGWebServiceServantInterface_getCustomerreviewsByRestaurant"/>
<output
message="tns:DGWebServiceServantInterface_getCustomerreviewsByRestaurantResponse"/></operation>
<operation name="getRestaurantDetail">
<input
message="tns:DGWebServiceServantInterface_getRestaurantDetail"/>
<output
message="tns:DGWebServiceServantInterface_getRestaurantDetailResponse"/></operation></portType>
<binding name="DGWebServiceServantInterfaceBinding"
type="tns:DGWebServiceServantInterface">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="rpc"/>
<operation name="createCustomerreview">
<soap:operation soapAction=""/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></output></operation>
<operation name="getAllRestaurants">
<soap:operation soapAction=""/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></output></operation>
<operation name="getCustomerreviewDetail">
<soap:operation soapAction=""/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></output></operation>
<operation name="getCustomerreviewsByRestaurant">
<soap:operation soapAction=""/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></output></operation>
<operation name="getRestaurantDetail">
<soap:operation soapAction=""/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
namespace="urn:DGWebService/wsdl"/></output></operation></binding>
<service name="DGWebService">
<port name="DGWebServiceServantInterfacePort"
binding="tns:DGWebServiceServantInterfaceBinding">
<soap:address
location="http://localhost:80/DGWebService/DGWebService"/></port></service></definitions>
=================================================================

you may have a little better luck in the JNI forum.

Integrate OC4J 10.0.x in Oracle Application Server 10g

Ok, i have a Oracle Application Server 10g Enterprise Instance including Infrastructure on a Linux-Server. Its OC4J is a 9.0.4 OC4J following the J2EE 1.3 standard.
So now Oracles offers a newer 10.0.x Developer Betarelease of OC4J wich will be in Production soon and happily enough this release implements J2EE 1.4 with real JAX-RPC Web Service Support (I need Web Services with Attachments!).
My question: How to integrate a 10.0.x-Version of OC4J in an Oracle Application Server 10g Enterprise (v 9.0.x) Installation ??? Whitepapers? Documentations? Internetlinks would help alot !
Thanks and keep the good work alive, oracle rules!!!
bye from germany, marc

Marc,
I don't have an answer for you (sorry), but actually, OC4J stand-alone is a complete application server -- unless Oracle have hacked it so much as to intentionally turn it into a not complete application server (it wouldn't surprise me ;-) Perhaps OC4J stand-alone will be sufficient for your requirements?
In case you are unaware, OC4J is derived from the "OrionServer". Unfortunately, their Web site is down temporarily, but these other sites may be enlightening:
http://www.orionsupport.com
http://kb.atlassian.com
Good Luck,
Avi.

Plugin based Web Service with session management

I am trying to make a web service in java with jax-ws that should support extensions to the service without rebuilding the project. I thought it might be possible to make a standard web service and the let each plugin create their own service, making the client side plugin point to both the standard service and the plugin specific one. This way I could have user management and such in the standard service and the more plugin specific one in an other service. The problem is though, how do I make a common session for all the services? All services are running at the same server and on the same domain name.
I checked the HTTP headers and found out that the JSESSIONID was changing when I created a new port on the client side. I was trying to implement a SOAPHandler to edit the cookie in the HTTP header, hoping that this will lead to the same session across the services. But found it hard. It was no problem reading the "Set-cookie" header, setting the cookie on the new requests was harder, as the CookieJar object seems to be internal [1]. And the MessageContext.HTTP_REQUEST_HEADERS wasn't created at the time my handlers run. Is there an easy solution to this?
I am not sure if my idea is a good solution to the main problem, and all other ideas are more than welcome. I hope it is possible to extend the features of my server without rebuilding the project. If anything is unclear, feel free to ask :)
[1] com.sun.xml.internal.ws.client.http.CookieJar

Adhir_Mehta wrote:
Could you explain plug in scenario with one example?Ok. We have not chosen exactly how to do this, but the idea is that someone may be able to extend the functionality of our server without rebuilding the project. We thought of something like a jar file with a implementation of some abstract classes. It should at least only be necessary to redeploy the project into the web container. The problem is; how do we let the plugins extend our web interface? One solution we thought of was to let each plugin have it's own service and dynamicly link to the plugin services from the main service that we provide as standard in our server. This way we may have some kind of plugin support on the clients as well, making the client side plugins know what kind of service it needs on the server side and thus extending the functionality all together.
Hope that explains our scenario. Feel free to comment and add new ideas :)
Regarding session management, its not advisable to manage the session in web services since that way it will become non interoperable.The documentation we found regarding sessions and jax-ws was all doing sessions with HTTPSessions, and to let the web container handle that.
On the server side
    @Resource
    private WebServiceContext wsContext;
    private HttpSession getSession() {
        MessageContext mc = wsContext.getMessageContext();
        return ((javax.servlet.http.HttpServletRequest)mc.get(MessageContext.SERVLET_REQUEST)).getSession();
    HttpSession session = getSession();
    session.setAttribute("User", user);On the client side
((BindingProvider)port).getRequestContext().put(BindingProvider.SESSION_MAINTAIN_PROPERTY,true);Do you have other standard options for us on how to do session management? All ideas are more than welcome

Oracle Service Bus - WS Policy

Hello everybody
I have the following problem:
I have a Proxy Service of OSB and I call from JDeveloper withouth problem. Also I can execute the proxy
When I add the policie Auth.xml I can't execute proxy service and I get the following problem: BEA-380001
and When I call the proxy service from jdeveloper 11, I can't because the policies of OSB is WL9.x and JAX-WS don't support
What am I doing?
I hope your help
Thanks
Jose Luis

Thanks jvanacht, it indeed does work!
After simply enabling SSL in weblogic our SOAPUI request which was replying with the following is now correctly responding:
<faultstring>weblogic.wsee.server.ServerURLNotFoundException: Cannot resolve URL for protocol http/https</faultsting>
We have a SunOne (iPlanet) Web Server proxying requests on HTTPS via the wls plugin to the WLS server.
Thanks Again,
Sham

CodeGenException. Invalid element: "group"

Hi all!
I trying to do simple thing, namely import an existing WSDL into a project and call it from a business process. While trying to build the project I get a com.stc.codegen.framework.model.CodeGenException. In ide.log there appears the following
SEVERE: error: modeler error: model error: invalid element: "group"
com.stc.wsclient.design.codegen.impl.JaxRpcException: Compilation failed, please check ide.log for JAX-RPC output.
       at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.jaxrpc(JaxRpcCodelet.java:338)
       at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.generateBeans(JaxRpcCodelet.java:997)
       at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.generateFiles(JaxRpcCodelet.java:467)
       at com.stc.wsclient.design.codegen.impl.WSClientCodelet.generateFiles(WSClientCodelet.java:451)
<...skipped...>
Caused by: com.stc.wsclient.design.codegen.impl.JaxRpcException: Compilation failed, please check ide.log for JAX-RPC output.
       at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.jaxrpc(JaxRpcCodelet.java:335)
<...blah...blah...blah...>Nothing informative at all but the first string, which still means nothing to me. The WSDL and referenced XSDs are pretty complex, but they pass validation from the EDesigner. The Java CAPS version is 5.1.
Did anybody see such behavior? I can send the project if that can help.
Thanks in advance,
Victor

Hi Luca,
Java CAPS uses JAX-RPC for web-services communication. JAX-RPC does not support <xsd:group> tag. In future versions of Java CAPS they will use JAX-WS instead, which does not (hopefully) have this problem. The only workaround I can think of is not to use groups, encapsulate the repeating elements in type or just copy-paste the group content everywhere instead of references to groups.
Hope that helps.
Victor

WSDL / SOAP http get binding

Hello,
i am looking for information regarding HTTP Get binding for SOAP. I have looked at the wsdl 1.1 specification which provides some information concerning that binding (http://www.w3.org/TR/wsdl#_http) and also in SOAP 1.2 (http://www.w3.org/TR/soap12-part0/#L26854). However all this is not precise enough.
In particular, i am wondering whether the serialization of SOAP request (from its definition in a wsdl) using http get is clearly formalized somewhere (in a specification). If any, what are the limitations and constraints, for instance, does it support complex types defined in the WSDL. Are there implementations currently available?
Thanks,
Cyrille

Hello,
Which kind of Web Services are you building in JDeveloper?
- JAX-RPC (J2EE 1.4)
- Oracle Web Service stack (J2EE 1.3)
What is your targetted environment?
Oracle does not support Document style Web Services in Oracle Web Service stack (J2EE 1.3), it has to be done programmatically.
However the JAX-RPC stack does support, and it is the default, Document style Web Services and you can right click on the Web Service node to edit the service.
Regards
Tugdual Grall

Wsdl soap style get RPC need document/literal

Hi,
Using jdev10.1.3/jre1.3 to generate webservice wrappers
How do you change style which defaults to RPC and I need document/literal ?
Can't really find any properties in the IDE to do it, can anyone point me in to the relevant sections?
Thanks
Pete

Hello,
Which kind of Web Services are you building in JDeveloper?
- JAX-RPC (J2EE 1.4)
- Oracle Web Service stack (J2EE 1.3)
What is your targetted environment?
Oracle does not support Document style Web Services in Oracle Web Service stack (J2EE 1.3), it has to be done programmatically.
However the JAX-RPC stack does support, and it is the default, Document style Web Services and you can right click on the Web Service node to edit the service.
Regards
Tugdual Grall

JAX-WS 2.0 support

Similar Messages

Maybe you are looking for