A question about JAX-RPC

I got a response message from the server side as follows:
<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope soap-env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Header/><soap-env:Body><addResponse><return ns1:type="ns2:int" xmlns:ns1="http://www.w3.org/1999/XMLSchema-instance" xmlns:ns2="http://www.w3.org/2001/XMLSchema">4</return></addResponse></soap-env:Body></soap-env:Envelope>
but at the same time ,jax-rpc can't parse the soap message,and report error as follows:
XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/P-024 version
if the version="1.0" cause the problem or something else?Who can give me an answer?Thank you very much!

Hello
You didn't get any answer yet since July?
I am having almmost the same problem

Similar Messages

Observations/questions on JAX-RPC

I started developing Web Services on Oracle 9iAS (9.0.2.x). What impressed me is how easy it is to turn any old class into a Web Service; you can focus on and develop the API you want, in relative ignorance that the class is being exposed through SOAP. The whole SOAP layer, including [de]serializing parameters and return values, making the HTTP connection, etc. is provided by the container and the auto-generated client stubs.
Oracle 9iAS, and earlier versions of WebLogic (6.x) seem to pre-date JAX-RPC and don't have a standard API for client stubs. WebLogic 7 seems to have adopted JAX-RPC, though, and hopefully other vendors will follow suit; it will nice for all client stubs to have the same methods for setting the URL or a username/password.
I did notice some important differences between Oracle Web Services and JAX-RPC, though:
- Oracle and WebLogic both provide for the direct exposure of stateless session EJBs as SOAP services. The JAX-RPC reference impl (JWSDK) seems to only provide for the exposure of regular Java classes, and exposing an EJB requires an intermediary Java class to find and call the EJB in question. Is it the intent of the JAX-RPC standard to allow for vendors to directly expose EJBs, while just omitting this as a feature for the reference implementation?
- Oracle also does not require an explicit step to generate client stubs and WSDL. It can generate these dynamically at runtime inside the servlet engine, and makes these available for download from the service itself. Can this style of auto-generation play nicely with JAX-RPC?
I also have some questions about JAX-RPC:
- if java.util.Calendar objects are serialized and deserialized by JWSDK, does that imply that java.util.TimeZone objects are as well?
- can someone point me at where the standard for exception handling and transport is documented (what exception do services throw, and how are they translated to client-side exceptions)?
- when the client stub is generated, does that also create client-side skeletons for each user-defined datatype (bean) used as an argument/return type for the service? Can these skeletons be made to implement a particular interface? One of the annoying things about Oracle 9iAS Web Services is that you can't use a client skeleton and the actual (server) bean object interchangeably even if the same get/set method exists on both objects, because the skeleton objects don't implement any interfaces.
Thanks!
-- Bill

Hi,
I will share with you... what I understand and know ...
- Oracle and WebLogic both provide for the direct exposure of stateless session EJBs as SOAP services. The JAX-RPC reference impl (JWSDK) seems to only provide for the exposure of regular Java classes, and exposing an EJB requires an intermediary Java class to find and call the EJB in question. Is it the intent of the JAX-RPC standard to allow for vendors to directly expose EJBs, while just omitting this as a feature for the reference implementation?
Well jsr 109 opens up the possibility of having stateless
session beans as end points. Naturally to stay aligned with
this jsr 109, lot of application server vendors have started
to support this.
The JAX-RPC ri that you are looking at was releazed befor JSR
109 spec was solidified and the ri gets released.
- Oracle also does not require an explicit step to generate client stubs and WSDL. It can generate these dynamically at runtime inside
the servlet engine, and makes these available for download from the service itself. Can this style of auto-generation play nicely with
JAX-RPC?
You should check out the next version of j2ee ri.
Some of your questions might get address there,
- if java.util.Calendar objects are serialized and deserialized by JWSDK, does that imply that java.util.TimeZone objects are as well?
Have check out the jsr 101 Chapter 19 ? That should answer
your question. You can get it from www.jcp.org
- can someone point me at where the standard for exception handling and transport is documented (what exception do services throw, and how are they translated to client-side exceptions)?
http://java.sun.com/webservices/docs/1.0/api/index.html
Check out the javadocs at the above location of service specific exceptions.
Also check out 8.2.6 from the spec it might help a little.
asengup

Very basic questions on JAX-RPC and wscompile

Hello,
well, I have this tool that generates java packages. The thing is that this tool needs now to generate JAX-RPC compliant java packages. To verify its compilance, I am using wscompile 1.1.3 build R1 and Sun AS Edition 8.2.
My questions are:
- In the generated packages, there might some classes with no attributes at all :P(remember that I am handling automatically generated classes). When running wscompile to generate the corresponding WSDL, I am getting "invalid type for JAX-RPC structure", even if it has a default empty constructor. I know it looks stupid, but I could not find anywhere in the JAX-RPC specification saying that for a class to be jaxrpc compliant, it must have at least one attribute. Any idea?
- It might be the case that I have same class name in different packages:
mypackage.structures.messages.A
mypackage.structures.segments.AWhen generating the server stub, I am getting:
Duplicate type name "{urn:mynamespace}A" for java type "mypackage.structures.segments.A" found.
Is there a way to tell wscompile to keep the class package name for every class when generating the wsdl? Or is it always building all the classes together in the package specified in the service/packageName within the configuration xml file?
Thanks a lot in advance for any help.

1. Does predictive text only work in the SMS app, or does it work in the apps for email, writing notes, etc?
It works with Safari, the Mail client, the Notes app, and with the SMS app.
2. Can you turn the predictive text off? (I find it wildly irritating, because I know far better what words I want to write than a pesky phone does!)
Yes.
3. Having email sent to a mobile is a whole new world for me! Do I need to subscribe to MobileMe at £££ per month, or is there another way of having email from my three accounts forwarded to my mobile?
You can access any IMAP or POP account with the iPhone's Mail client, and access multiple email accounts. I currently access to email accounts with the iPhone's mail client - my MobileMe account, and a business POP account. You can access all 3 of your email accounts with the iPhone's Mail client.

Question about JAX-WS together with EJB 3.0 on WLS 10.3

Hi all,
I am developing a application that it is running on WebLogic 10.3. The application expose EJB 3.0 methods as web services by @WebService & @WebMethod annotation. And my question is,
1. Is there any way to specify the context path/root for those exposed EJB? Currently the contextpath is same as the EJB's name
2. And is there a method to disable the "scanning" of JAX-WS annotation on startup/deployment? The reason behind is that, some of the EJB jar files are coming from other team. I need to deploy it as EJB but not as a web service.
Thanks
Regards,
Rock

Hi guys,
Here is what Eduardo is talking about:
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=407022.1
(Doc ID: Note:407022.1)
Rgds,
Fábio.

Problems and Questions about JAX-WS!

Hello guys ,
Haven't come here for a long time , feeling so good backing here.
so guys ,when i using the netbean6 to develop the web service ,i across the folling problems ,can somebody tell me ...thx!
1 when i trying to build the web service client by the way os ,
* ***static drag and pull the xxport to my code area(netbean6) ,here i haven't problems .
** static proxy @WebserviceRef (wsdlLocation="....?wsdl") xxxService it always notice me that can't find the class.
**** dynamic proxy ,when i coding the web service ,using the
@Webservice(Name="",targetNamespace="", wsdlLocation="http://localhost:8080/xx/xxService?wsdl") here i met the wsdlLocation errer,throws the finenofind exception .......
2.questions :
when do i need to use the JAXB ? and when i want to send the image or files do i need to using the SAAJ ?
3 BTW, any URL to learn more about the WS?
Many thx!

Thx, nikos2008, i watch the link you recommanded , it really help ,
but the point is i am using netbean6 to build the web service ,so i dont'
need the wsimport or wsgen , isn't it ?
ok ,so i will describe it more clearly ...example "SOA using Java web service "
@WebService(name = "RequestOrderPort",
41 targetNamespace = "http://www.example.com/req",
42 __wsdlLocation = "http://localhost:8080/oms/RequestOrderService?wsdl")__*
*"-----if i code the wsdlLocation ,i will throws the nullpointException "*
43 public interface RequestOrderPort {
44
45 @WebMethod
46 @WebResult(name = "Order", targetNamespace = "http://www.example.com/oms")
47 @RequestWrapper(localName = "requestOrder",
48 targetNamespace = "http://www.example.com/req",
49 className = "com.example.req.RequestOrder")
50 @ResponseWrapper(localName = "requestOrderResponse",
51 targetNamespace = "http://www.example.com/req",
52 className = "com.example.req.RequestOrderResponse")
53 public OrderType requestOrder(
54 @WebParam(name = "CUST_NO",
55 targetNamespace = "http://www.example.com/req")
56 String custNO,
57 @WebParam(name = "PURCH_ORD_NO",
58 targetNamespace = "http://www.example.com/req")
59 String purchORDNO,
60 @WebParam(name = "ccard", targetNamespace = "http://www.example.com/req")
61 BUSOBJCCARD ccard,
62 @WebParam(name = "item", targetNamespace = "http://www.example.com/req")
63 List<BUSOBJITEM> item)
64 throws InputFault
65 ;
67 }
by "deploy and undeploy the web service " in netbean6 to deploy the web service to GlassFish.
web service client
1:
If you are not running inside a container, you cannot use the @WebServiceRef
for injection, but you can still make use of the generated service
class RequestOrderService,
RequestOrderService service = new RequestOrderService();
64 RequestOrderPort port = service.getRequestOrderPort();
65 (new Tester()).runTests(port);
----- what does it mean of "not inside a container " but if i use this method ,i can success in using the WS
2: You can use several methods to get a proxy instance. In this section, we
look at three of them. The most elegant approach involves dependency
injection specified by an annotation
31 @WebServiceRef(RequestOrderService.class)
32 public static RequestOrderPort port;
it notice me can't find the RequestOrderPort
3.you can construct a proxy instance for the SEI dynamically by
configuring an instance of the javax.xml.ws.Service class at runtime.
Creating a Proxy Instance Using a Dynamically Configured Service
77 URL wsdlURL = new URL("http://"+hostName+":"+portVal+"/chap06-endpointendpoint-
1.0/requestOrder?wsdl");
78 QName serviceQName =
79 new QName("http://www.example.com/req", "RequestOrderService");
80 QName portQName =
81 new QName("http://www.example.com/req", "RequestOrderPort");
82 Service service = Service.create(wsdlURL, serviceQName);
83 RequestOrderPort port =
84 (RequestOrderPort) service.getPort(portQName, RequestOrderPort.class);
85 (new Tester()).runTests(port);
BTW,Is this the 3 ways to use the web service ?
Thx, hope this time i make you understood it...

About JAX-RPC Client

Hi, I am read the JWSDP tutorial but I don�t understand about the kinds of client: (static stub, dynamic proxy, DDI). I would like know:
1)What I need to develop each client? (including files)
2)How works each one?
3)What the structure generated before I develop and compile the client? (file structure)
Thanks.
ps: If someone know any site, that discuss about this for a newbie, I will be very thanks too.

...ahhhh, and what of this clients listed above use the WSDL of the Web Service?!?!
Please help. Thanks;

Jax-rpc and rmi confusion

I'm new to the jax-rpc, and I'm very confused about jax-rpc, if it is using RPC (remote precedure call), why we have to import java.rmi.Remote ? is it somewhere still using RMI?
Thank you in advance for you answer!

Found some answer from the following link
http://forum.java.sun.com/thread.jsp?forum=331&thread=465860

JAX-RPC client with JDeveloper 12c

Hello,
It's the first time I use jax-rpc (I'm used to jax-ws) and looking for help.
I need to create a client for a JAX-RPC web service using JDeveloper 12c.
The customer provided to me a WSDL file (I don't have access to the webservice yet). In JDeveloper I created as usual a "Web Service Client and Proxy" providing that wsdl file, but I think the generated code is for a JAX-WS (since there are @WebMethod, @WebServiceClient and @WebService notations that I understood should not be present in JAX-RPC clients.
Can anyone point me to some documentation about JAX-RPC client developing in JDeveloper 12?
Thank you,
Marco

To make things a little more clearer, this is a post of the error gotten at runtime...
        java.lang.NoSuchMethodError: java.util.Collections.emptyList()Ljava/util/List;
        at com.sun.xml.messaging.saaj.soap.MessageImpl.<clinit>(MessageImpl.java:755)
        at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.createMessage(SOAPMessageFactory1_1Impl.java:47)
        at com.sun.xml.rpc.soap.message.SOAPMessageContext.createMessage(SOAPMessageContext.java:137)
        at com.sun.xml.rpc.client.StreamingSenderState.<init>(StreamingSenderState.java:30)
        at com.sun.xml.rpc.client.StubBase._start(StubBase.java:92)
        at mck.practise.oracle.plsql.PlsqlService_Stub.sayHello(PlsqlService_Stub.java:54)
        at mck.practise.oracle.plsql.HelloWorld.sayRPCHello(HelloWorld.java:34)
        at mck.practise.oracle.plsql.HelloWorld.main(HelloWorld.java:22)The suprising thing is that if I change the application's java platform from JDK 1.4 to Java 5 using the netbeans projects property window, everything works fine.
Can anyone still suggest on this.
Regards,

JDeveloper JAX-RPC vs AXIS

Hi everybody,
I find that working with Axis and it's tools (wsdl2java) is easier than working with Oracle's SOAP implementation(webservicesassembler.jar).
One advantadge of using oracle's solution is that ws that
returns an Element type does not need a custom deserializer and Axis needs.
Which more advantages do you think oracle's solution has?
Why should we use jDev10's JAX/RPC web services?
Thank you.

Hello
The first thing is you should really say "JAX-RPC vs AXIS", since both of them are Web Services Runtime/Development APIs. And Jdeveloper is just a tools that simnplifies the development and developmen of Web Services using JAX-RPC.
So what about JAX-RPC vs Axis?
I would say that Axis is/was a de-facto standard fro developing WS, since it is running in most of the application servers - OracleAS 10g included-. Where JAX-RPC is the standard defines by the Java Community Process (JCP) and is a mandatory features of J2EE 1.4 specifications. So by using JAX-RPC you will be able to use a set of API that are really standard based. Also as part of your decision you should take a look in more details about the services provided by JAX-RPC: http://java.sun.com/xml/jaxrpc/index.jsp and the different standards involved.
Also I think that one important thing to take in consideration when you will make your decision is the future of Axis as we know it today release 1.0 If you see the Axis 2.0 Web site, it says that:
"Axis2 is an effort to re-design and totally re-implement both Axis/Java and (eventually) Axis/C++ on a new architecture."
Other considerations:
Some of the important things to watch when you select your framework are also related to:
- how you can interop with other framework (consuming or providing a service that is created with another stack)
- how to handle attachement (size, types, performances, ..)
When you will start to use Web Services in your system you may need to add different quality of services for example adding security (authentication, encryption, ...) or reliability (how I can be sure that my response has been received by my client application)
All the Web Service Management (security, reliability, etc etc) is not currently well integrated in the Axis stack, so you will have to use a third party solution to have this type of features. (you can for example use Oracle Web Services Manager for that purpose)
All these, and more, are more than just the 'SOAP' stack.
Oracle, JAX-RPC, and more:
First of all OC4J 10.1.3 support JAX-RPC as any J2EE 1.4, in addition we support WS-Security, WS-Reliability to integrate them to your enterprise, and a full integration with Oracle Web Services Manager.
Oracle JAX-RPC implementation has also specific focus to ensure interoperability firs WS-Interoperability compliant -[url=http://www.ws-i.org/]WS-I is an open organization that defines the interoperability around WS.- services, but also based on 'real life validation scenarios' -especially with .Net- where we use our customer applications to validate our platform interoperability.
Also, on the tooling side, our Web Services stack is fully integrated to Oracle JDevelope that allow you to develop easily JAX-RPC base Web Services (client or provider), based on several type of object/business logic (simple Java class, EJB, PL/SQL, SQL, ...); and deploy them very quickly to your application server
Regards
Tugdual Grall

Question related to the JAX-RPC.

Hi ,
I have a question related to the JAX-RPC API.
Please clear me following points whether I am right or not?
1. If my two end points are in Java then and only we use the JAX-RPC API. Is it right?
2. If my two end points are in .Net then we use the some other API in .NET. Is it right?
Please give me links or associate info. regarding this.
Thanks,
Rahul

With JAX-RPC API, you are writing or consuming web services. If you are building web services, then that web service should be interoperable to .NET as well as Java. You do not have to use JAX-RPC, because, JAX-WS can serve the same purpose but is much easier to program. More about web services may be found at [http://soalib.com|http://soalib.com]

JAX-RPC Dynamic Proxy Client Question

I have a very simple web service successfully deployed using Tomcat 5 and Apache Axis. It simply takes a string and returns a String. Regardless, it's working.
Now I'm wanting to create a JAX-RPC dynamic proxy client as described on the following page:
http://java.sun.com/webservices/docs/1.3/tutorial/doc/JAXRPC5.html
There are numerous other articles out there describing the same method.
My problem is that I'm getting a ServiceException on the following line every time I try to run my client:
ServiceFactory factory = ServiceFactory.newInstance();
Would anyone have any ideas why this might be or what I might be missing? All the articles make it seem like this is just a trivial line and never mention much about it.
Any help would be appreciated. Thanks.

Hello,
You are getting a service Exception on ServiceFactory.newInstance() method?
Actually, I have never seen this problem before. Is it possible that there are
classpath issues? That is, are you using just the jars from the jwsdp?
Regards,
Kathy

Jax RPC and security

Hello
i have a little question about the jax rpc and security stuff
i have a webservice running
once over http://localhost:8080/appl/service
and over ssl too http://localhost:8443/appl/service
i am starting the server and then the client is generating static stubs over the ...8080/appl/ws/service?WSDL
is it possible to let the client application generate the stubs over the https port?
or do i have to secure the files on port 8080 via authentication then let the ClientDeveloper download the wsdl-files and let him then create the stubs with a local copy of the wsdls?
Any sugestions?
Thx for any Ideas
Michael / Adraw

Michael / Adraw,
Sorry for piggybacking on your request but I see you have your web service running on over SSL. When I tried that with the jwsdp 1.3 I am unable to browse pages over SSL with netscape and I can not connect with a client web services application (written in java).
Are you able to do this with jwsdp 1.3??
Brian Mason
[email protected]

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 Client side: How to use multiple X509 client certs ?

hi, (excuse me for my english)
i'm looking for an answer to this question:
I'm using the JAX-RPC libraries (JWSDP 2.0) for a web services client application in my app server (tomcat 4 under 1.4 Sun JVM) with HTTPS connection. All works fine when i'm using system.Setproperties for keystore and trustore.
Buk now, I want to use different client SSL keys for the same app to consume the web service (one SSL client key for a group of users).
Is it possible ?
i've tried using custom SSLSocketFactory and custom KeyManager but it won't works: when the SSL connection is well established once, i can connect to the app with an invalide client cert ! (it seems SSL connection is in cache and i dont't know how to disable this cache).
I have read some threads on this problem without answers ! (http://forum.java.sun.com/thread.jspa?forumID=331&threadID=333010 and http://forum.java.sun.com/thread.jspa?forumID=331&threadID=600372)
Thanks
Edited by: Buck007 on May 26, 2008 9:14 AM

I have the same problem. If you find the solution please post it here :)
thanks

A question about JAX-RPC

Similar Messages

Maybe you are looking for