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

Similar Messages

Apache axis, JAX-RPC, JAXR, JAXM, JAX-WS, JAXB, and Metro

Are all of the following the different APIs for creating web service applicaton?
Apache axis,
JAX-RPC,
JAXR,
JAXM,
JAX-WS,
JAXB, and
Metro
--If so, which one(s) are most widely used?
--If not, what are the differences among them?
Thanks
Scott

I think your are looking for a full web services framework.
Apache axis --> Is a WS framework. implements jax-rpc. Provides some features on its own
JAX-RPC --> Is a WS framework specification. Your application servers/axis implement this.
JAXR --> not an web-service api, rather a web-service registry access api
JAXM --> Is an api for xml messaging. Your framework provider may use this.
JAX-WS --> Is jax-rpc 2.0. Your application server provider will give implementation for this. Otherwise you can use xfire/metro as the implementation. Chose this over jax-rpc.
JAXB, --> Is used for xml-java binding. Jax-ws uses this. But not specific to jax-ws..
Metro --> Reference implementation for jax-ws.
All in all jax-rpc, jax-ws and axis2 are three options. go for jax-ws if you do not have any other constraints.As for selcting implementation of jax-ws, if you are working on an app-server (and not on a simple servlet container or without a server), server vendor will provide that. Otherwise look for xfire or metro.

Java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

We have some web services that run under OC4J 10.1.3.4. We have various JEE 'client' apps (JSF, servlets etc.) that use these web services. These JEE apps also run under OC4J.
We started a migration project from oc4j to weblogic 10.3.2. In phase 1 we want to move these JEE 'client' apps to weblogic. In phase 2 we want to move the web services themselves to weblogic with adjustments to the JEE 'client' apps as needed.
However we ran into an issue during this phase 1. Deploying these JEE 'client' apps to weblogic results in an error like this:
java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions.
We are including Oracle web services client libraries (http://download.oracle.com/otn/java/oc4j/1013/wsclient_extended.zip) in these JEE 'client' apps's war files because weblogic does not have them.
What part of Web Service Migration Guide is the above error message talking about? Do we have to re-generate the client side proxies for all these web services using weblogic's clientgen task in 'JAXRPC' mode? Many of these web services are doc/literal jax-rpc web services. Or does the migration guide recommend we migrate the web services first to weblogic? Any other specific information on working around this error message would be greatly appreciated.

Hi,
I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
Regards,
Sylvain

Jdeveloper 11g - JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

Hi,
I am using Jdeveloper 11g and migrating a web Service Proxy created using jdeveloper 10g.
I imported all the proxy classes and when I try to run web service client In Jdeveloper 11g I get the following error
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions."
Please advise on how to solve this?
which is the offending jar/library file in Jdeveloper 11g which is causing the above error?.
Is the above problem there in the WebLogic Server Runtime also?
Please let me know.
2) I cannot generate web server proxies also with jdev11g because the wsdl has overloaded methods omitting the name property within the input and output message, ie, they have a null name. therefore Jdeveloper 11g is using the library which
when called with an overloaded operation that contains null input/output message names, a duplicate error occurs because it sees other operations with the same name. so it is effectively not allowing to create the web service proxies.
Thanks,
Appreciate your quick response to the above

Have you checked the 'Web Service Migration Guide' mentioned in the error message?
Timo

JAX-RPC with JAXM?

I have already created a synchronous messaging client using JAX-RPC. I now find the need to also have a asychronous messaging client as well. I was not able to find much as far as information or examples of asynchronous messaging. The only information I was able to find just says that I should use JAXM. The question I have is can I combine the JAX-RPC and the JAXM together (I'm using tomcat). Also does anyone know of a good asynchronous messaging example using either JAXM or JAX-RPC?
tyia

The Java Web Services Tutorial case study example uses JAX-RPC and JAXM together:
http://java.sun.com/webservices/docs/1.0/tutorial/doc/CB.html

JAX-RPC 9.0.4 --- Data Types Supported

Hi,
does any body know is java.util.List is a supported Datatype on OC4j 9.0.4.2 for JAX-RPC.
Cheers
Gaurav

Gaurav,
Not sure which version of JAX-RPC you are intended to run on top of 9.0.4.2 ?
In any way, if you want your service to work with the majority of the clients, you need to focus on the XML types; not the java types.
To my knowledge, the List will be mapped to a proprietary type, at best, which make it harder to re-use.
All the best,
Eric

Can we include a JAXM servlet in JAX-RPC web service????????

Can we include a JAXM servlet in JAX-RPC web service?
If yes then how?
If not then why?

Hi,
I found a link to getting handle to Request and response object here: http://edocs.bea.com/wls/docs103/webserv_rpc/jws.html#wp275820
Thanks!

JAX-RPC or JAXM or AXIS/GLUE

Hello,
I am starting with webservices and am confused with all the APIs out there. Should I start with JAX-RPC or JAXM to develop/consume webservices? Do I need SOAP implementations like AXIS or GLUE?
Please Help !!!
-ss

Yes, it's pretty overwhelming when you're first starting out. My suggestion is to start with JAX-RPC because:
1. it's easy to understand
2. most existing web services are RPC-based
3. there are many nice tools to help you create JAX-RPC based services
Now you can decide which JAX-RPC implementation to use. Both JWSDP and Axis have JAX-RPC implementations. JWSDP is nice everything-rolled-into-one installation, so it's a good platform for learning (the tutorial version 1.2 isn't available yet but most of the 1.1 tutorial applies to JWSDP 1.2). Just download the JWSDP 1.2 installation package and the tutorial and you're ready to go (Tomcat is bundled with the JWSDP).
However, I believe that many more commercial web service implementations are based on Axis than JWSDP. If you plan on deploying web services yourself, you may want familiarize yourself with Axis. Just download and install Tomcat, then download and install Axis. The axis-user mailing list at http://ws.apache.org/axis/mail.html is very helpful.
And don't worry too much about which package is better. Any services you develop with either platform can be ported unchanged to the other.
Good luck,
Mike

Diff between JAXM & JAX-RPC

what's the difference between JAXM & JAX-RPC ? How to choose between the two ?

hi,
You can simulate the request-reply type call in JAXM also.
So if I have to ans it again I will say JAX-RPC uses JAXM to execute the rpc call.
Also through JXM alone you can simulate the RPC call Through SoapConnection. I dont know if it can be done through ProviderConnection . I have yet to explore it.
Still I am confused why JAX-RPC is considered as a separate API.
--Ashwani

BIweb service proxy JAX-RPC 1.1 method is not supported in WLS 8.1 clients

Hello
I have an application in oracle Application server and I'm migrating to weblogic 11g .
I have used web service proxy for BIPublisher 10.1.3.4 , careated by jdeveloper web service proxy wizard , when I want using it in weblogic , In corresponding form that uses BI Publisher web service proxy , I encounter following error :
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients , if you attempting to run oc4j 10.1.3 JAX-RPC client in WLS,please see Web service Migration Guide for Instructions"
What should I do?
Regards
Mehdi

Spoke to dev and there was a bug logged, it seems to be down to Weblogic's implementation.
+This is pure WLS issue. The root cause of this problem is that Weblogic's
SAAJ implementation. No codechange on BIP server side
WLS 10 ships with two SAAJ implementations. By default the buggy 9.x
implementation is used (which lives in the package
weblogic.webservice.core.soap), but there is a new implementation, which
supports SAAJ 1.3 (which lives in the package weblogic.xml.saaj). I also
checked in a debugging jsp page, which could help looking at the DEBUG
logging to see which SAAJ implementation is used.
JSP testpage xmlponline/wwwroot/wsclient/soapclient-wls-8270711.jsp
To use this new version, you have to make sure setting the
-Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl
in startWebLogic script. +
Please give the solution a try and let me know if it works.
Regards
tim

XML Comments in SOAP message - jax-rpc

I ran across an issue with comments in my soap messages with regards to the serialization.
My solution was to strip all the comments inbound and outbound.
Are xml comments supported by JAX-RPC? I am currently scouring the internet for more information, but the closest I have come is a reference in the IBM implementation which doesn't really help me out.
Any thoughts are appreciated.

I'm trying to figure this out myself. I am using JAXM to access a web service but it wants the xml version...

Batch operations with JAX-RPC

I have read a number of different tutorials about Web services and JAX-RPC, and have to come the conclusion that JAX-RPC is the correct approach to use for my project. Most of the examples I have seen involve invoking services which perform a 'one-shot' action e.g. get a Stock Quote.
My first question is that I am not sure for such 'one-shot' services, how much support there is in the API for sending/receiving arrays of data items. e.g. sending a user's data to a web service which includes an associated list of phone numbers.
Further if I wanted to send user's data which included an array of nested objects, would I have to implement a serializer/deserialiser plugin?
My main concern really is how best to handle a batch of requests to the service. My current thought is to use JAX-RPC with an xml document attachment - listing of a number of user's data and their parameters. A 'batch service' would return a response immediately then work through the document and invoke the existing 'single shot' service - which will be hosted on the same web server.
Is this approach which brings together a number of different ideas from the various JAX-RPC tutorials viable? Are they any better alternatives?
For example would it be better to implement a JAX-RPC for the single shot service requests and use JAXM for batch service requests? (On the server-side I would still be expecting the batch service to re-use the single-shot service). Can JAXM and JAX-RPC services co-exist on the same web server? I realise that there would be WSDL generated for the JAX-RPC service alone and so for a client developer there will be an inconsistency in terms of how the Web service is accessed.
Thanks in anticipation

Hello, I'll try and go through your questions one at a time:
My first question is that I am not sure for such 'one-shot' services, how much support there is in the API for
sending/receiving arrays of data items. e.g. sending a user's data to a web service which includes an
associated list of phone numbers.JAX-RPC has built in support for List type operations. There is no problem sending Arrays of information over the wire. If you were sending an Object of type User, for instance, there would be no problem with User having a List of PhoneNumber types objects as part of it's structure.
Further if I wanted to send user's data which included an array of nested objects, would I have to implement
a serializer/deserialiser plugin?Condintional No. If the nested objects contained only data structures that JAX-RPC knows how to deal with, your fine (things like java.lang.String or java.lang.Integer). However, if your nested objects contain types that JAX-RPC does not know how to deal with (i.e. java.sql.TimeStamp), you will have to write a custom serializer/deserializer just like you would if you were passing those objects without them being nested.
My main concern really is how best to handle a batch of requests to the service. My current thought is to
use JAX-RPC with an xml document attachment - listing of a number of user's data and their parameters.
A 'batch service' would return a response immediately then work through the document and invoke the
existing 'single shot' service - which will be hosted on the same web server.
Is this approach which brings together a number of different ideas from the various JAX-RPC tutorials
viable? Are they any better alternatives?As per above you shouldn't have to send an xml document attachment, but I guess you could. Also, for batch processing type tasks you probably want to look at the asychronous mode mentioned in the JAX-RPC part of the JWSDP tutorial.
For example would it be better to implement a JAX-RPC for the single shot service requests and use
JAXM for batch service requests? (On the server-side I would still be expecting the batch service to re-use
the single-shot service). Can JAXM and JAX-RPC services co-exist on the same web server? I realise
that there would be WSDL generated for the JAX-RPC service alone and so for a client developer there
will be an inconsistency in terms of how the Web service is accessed.Well, it really is up to you at this point. I assume that you want/need to use web services for access (as opposed to EJBs or any other method). So, I would look at an asychronous web service implementation.

JAX-RPC vs OC4J J2Ee web service

Hi,
Currently we use Oracle10G 10.0.3 developer preview edition. we deployed same web service on both JAX-RPC platfrom and OC4J J2EE web service platfrom (RPC encoding style). We found that old platform seems to perform better than JAx-RPC platfrom with regard to serialization and de-serialzation. We also did the test on Doc/literal style in JAX-RPC platfrom and its performance is not as good as the one deployed on old platform. We understand JAX-RPC is new implementation and Oracle10.0.3 is under developer preview edition and so it may not be optimized. We have following questions
1. Is this a known issue in JAX-RPC platform?
2. Is there anyway to optimize JAX-RPC web service? Like using different XMl parser (instead of Oracle XML parser)
3. When is the final release of 10.0.3 expected?
4. Will Oracle be supporting old web service platfrom (OC4J J2EE web service platform)? If so how long?
Thanks and regards
__Hari

Hi,
Currently we use Oracle10G 10.0.3 developer preview edition. we deployed same web service on both JAX-RPC platfrom and OC4J J2EE web service platfrom (RPC encoding style). We found that old platform seems to perform better than JAx-RPC platfrom with regard to serialization and de-serialzation. We also did the test on Doc/literal style in JAX-RPC platfrom and its performance is not as good as the one deployed on old platform. We understand JAX-RPC is new implementation and Oracle10.0.3 is under developer preview edition and so it may not be optimized. We have following questions
1. Is this a known issue in JAX-RPC platform?
2. Is there anyway to optimize JAX-RPC web service? Like using different XMl parser (instead of Oracle XML parser)
3. When is the final release of 10.0.3 expected?
4. Will Oracle be supporting old web service platfrom (OC4J J2EE web service platform)? If so how long?
Thanks and regards
__Hari

JAX-RPC: Exception

Hello there
I am using currently SUN's Webservice Development Kit 1.4 and try to realise a JAX-RPC "rpc/encoded" webservice.
My applicatio is currently running if I am using a static client (stubs geenerated by wscompile). If am going forward to use a dynamic proxy client, I am getting a strange exception during the deserialization of the xml data on the client: "trailing block elements must have an id attribute". See also stack trace at the end of the messsage.
As far as I understand is that it must somewthing be with the "ArrayList" or arrays which I am using in my JavaBean which I sent from the server to the client. Here my extract from my JavaBean:
public class Article
     long id;
     Date date;
     String category;
     String title="";
     String lead="";
     List texts;
}If I am taking out the member "List texts" then it will work correctly. The list contains only Strings. I tried also to use String[] array, but this didn't help either.
So here, my questions perhaps someone has some ideas what I did wrong.
- Why does it work with the stastic client but not with the dynamic proxy?
- Does anybody know an example on the net where in JavaBeans Lists or Arrays has been used?
- Anybody an idea why this error appears? Did I something wrong?
Thank you in advance
Mark Egloff
trailing block elements must have an id attribute
     at com.sun.xml.rpc.encoding.SOAPDeserializationContext.deserializeMultiRefObjects(SOAPDeserializationContext.java:81)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:226)
     at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:80)
     at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:489)
     at com.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallInvocationHandler.java:122)
     at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallInvocationHandler.java:86)
     at $Proxy0.getArticle(Unknown Source)
     at tagesanzeiger.client.ManagerDynamicClient.main(ManagerDynamicClient.java:43)

Thanks for your answer... regarding the support of "List" Types, you can get a list of supportet types from here http://java.sun.com/webservices/docs/1.3/tutorial/doc/JAXRPC2.html#wp79865 As you see "list" is supported. The problem for me is that I not use directly the list as parameter from the interface, rather than this it is used "internally" in my JavaBean. I found how to declare additional types here:https://jax-rpc.dev.java.net/whitepaper/1.1/index-part1.html#3.5.1 i.e. in your config-interface.xml for the wscompile server:
<typeMappingRegistry>
     <additionalTypes>
          <class name="tagesanzeiger.data.Media"/>
     </additionalTypes>
</typeMappingRegistry>This works for the serialization later on the serverside, but the client then claims that it has no serializer. I have read somewehere that the client also supports declarative serialization of custom types, bt I did not find any example. I tried also prorgrammatically, here a hint:
http://users.skynet.be/pascalbotte/rcx-ws-doc/seiadvanced.htm
But there is no full example of custom serializer, so I tried to use the sun serializer:
com.sun.xml.rpc.encoding.ValueTypeSerializer
com.sun.xml.rpc.encoding.ObjectArraySerializerbut this ended in a NullPointerException.....
- so has anybody out there a working example with complex types in a JavaBean?
- has anyone an example of customserializer.?
Regarding books, I have one from the Sun " Java Web Services Architecture" and one from Wiley "Developing Java Web Services", but both do not show how to use the cutom serializers nor declarive options at the client side....So I hope somenone has somewhere a working example...please...
Thanks
Mark

503 error code when trying to access a weblogic jax-rpc webservice

I'm going crazy on a webservice issue with Weblogic server 10.2.
I have a DocumentRepository webservice deployed and I generated a JAX-RPC library based on its WSDL.
Now I'm trying to access this webservice from Spring in a desktop application with the following bean declaration:
<bean id="documentRepository" class="eu.europa.ec.rdg.efp.services.document.v1_00.DocumentRepository_Impl">
     <constructor-arg value="http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL" />
</bean>
But when the Spring application context initializes, after a few minutes, I get the following exception:
javax.xml.rpc.ServiceException: Failed to parse WSDL http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Server returned HTTP response code: 503 for URL: http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL
+     at weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:174)+
+     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:485)+
+     at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)+
+     at eu.europa.ec.rdg.efp.services.document.v1_00.DocumentRepository_Impl.<init>(Unknown Source)+
+     at eu.europa.ec.rdg.efp.services.document.v1_00.DocumentRepository_Impl.<init>(Unknown Source)+
+     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
+     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
+     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)+
+     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)+
+     at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)+
+     ... 35 more+
Caused by: weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Server returned HTTP response code: 503 for URL: http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL
+     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)+
+     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:403)+
+     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:389)+
+     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)+
+     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)+
+     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:476)+
+     ... 43 more+
Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL
+     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1305)+
+     at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)+
+     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)+
+     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)+
+     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)+
+     ... 48 more+
Yet, I can see the WSDL in my browser when I go to http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL
Now it looks a lot like a proxy issue, which is possible because I'm behind a proxy, and I had to set the following command-line parameters in order to access remote HTTP resources before the spring application context is initialized:
-DproxySet=true -DproxyHost=<my proxy IP> -DproxyPort=8012
And I authenticate to my proxy using the following code, once again before the Spring application context is initialized:
Authenticator.setDefault(new Authenticator() {
                                   protected PasswordAuthentication getPasswordAuthentication() {
                                        return new PasswordAuthentication(<my login>, <my password>);
Yet, those settings seem to have absolutely no effect on how the webservice client is loading the WSDL.
So my question is the following: is it possible to specify a proxy to be used by the webservice client class to load the WSDL? If yes, how?
On the other hand, if it was a proxy issue, then I guess the webservice client couldn't reach the server and I would get a connection timeout or something. But here I get a response, even though it's a 503 error. Any other idea where my exception comes from?
I'm really desperate here. I've tried to ask our corporate weblogic support but they couldn't reproduce my issue. I've been fighting with this for weeks. Please help!

Please, take a look at https://blogs.oracle.com/proactivesupportWCC/entry/clustering_and_high_availability_for (and contact the support group as advised)

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

Similar Messages

Maybe you are looking for