JAX-RPX vs. SOAP

Hi @all,
I'm working on webservices at the moment and actually reading some stuff about that topic. After reading some articles and papers, I have a question concerning JAX-RPC and SOAP. Is it right, that JAX-RPC doesn't use SOAP, and if it's right, what about the SOAP-packages, which should be used by every webservice???
Hope there is anybody out there, who can help me going on...
Regards
Markus

Hi Markus,
JAX-RPC uses SOAP 1.1 as the XML-based protocol to transfer messages between client and server.
Let me know if you have any specific questions.
Regards,
-Arun

Similar Messages

Jax-rpc and soap

I have implemented a web service using jax-rpc and soap however i am unsure how to go about validating my soap package with my own schema before using the web service. How do i use my own schema to validate this, i think it may be with the wsdl file but i am not sure. At present the wsdl file points to a non existing .xsd file which the soap envelope uses, what i need i to replace this with my own schema, or is there a better way to do this than using jax-rpc and soap?
cheers
Andy

I am in the same situation as you are. Got any solution? please let me know.
Appreciate your valuable reply

JAX-rpx document literal type web services

I was trying to create a Document centric Web service. I followed all the steps in the document "Patterns and Designs for Building Document based Web Services" available at java.sun.com. I created the XSD's and WSDL files (top down approach). i used the following command of wscompile tool to generate the java source code.
wscompile -import -d build/classes -keep -s build/src -model build/model.xml.gz
to publich the web service on a server.
When the tool generates the code, the parameters for the method are the elements of the schema, instead of being an object, specified in the WSDL.
// This class was generated by the JAXRPC SI, do not edit.
// Contents subject to change without notice.
// JAX-RPC Standard Implementation (1.1.2_01, build R29)
// Generated source version: 1.1.2
package com.galaxyplus.tranentry.services;
public interface IPurchaseOrder extends java.rmi.Remote {
    public com.galaxyplus.tranentry.services.PurchaseOrderStatus acceptPO(com.galaxyplus.tranentry.services.Address billTo, java.util.Calendar createDate, com.galaxyplus.tranentry.services.LineItem[] items, java.lang.String poID, com.galaxyplus.tranentry.services.Address shipTo) throws
         java.rmi.RemoteException;
}It was supposed to be
// This class was generated by the JAXRPC SI, do not edit.
// Contents subject to change without notice.
// JAX-RPC Standard Implementation (1.1_03, build R65)
package com.examples.docliteral;
public interface IPurchaseOrder extends java.rmi.Remote {
    public com.examples.docliteral.PurchaseOrderStatus
         acceptPO(com.examples.docliteral.PurchaseOrder parameters) throws
             java.rmi.RemoteException;
}Does any one have any inputs on this. I am using the same example as in the Document.
Thanks

More Information
PurchaseOrder.xsd
<?xml version="1.0" encoding="UTF-8"?>

<schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="uri:X" targetNamespace="uri:X">
     <element name="PurchaseOrderDocument" type="tns:PurchaseOrder"/>
     <complexType name="Address">
          <sequence>
               <element name="street" type="string" nillable="false"/>
               <element name="city" type="string" nillable="false"/>
               <element name="state" type="string" nillable="false"/>
               <element name="zipCode" type="string" nillable="false"/>
          </sequence>
     </complexType>
     <complexType name="LineItem">
          <sequence>
               <element name="itemname" type="string" nillable="false"/>
               <element name="price" type="decimal" nillable="false"/>
               <element name="quantity" type="int" nillable="false"/>
          </sequence>
     </complexType>
     <complexType name="PurchaseOrder">
          <sequence>
               <element name="billTo" type="tns:Address" nillable="false"/>
               <element name="createDate" type="dateTime" nillable="false"/>
               <element name="items" type="tns:LineItem" nillable="false" minOccurs="0" maxOccurs="unbounded"/>
               <element name="poID" type="string" nillable="false"/>
               <element name="shipTo" type="tns:Address" nillable="false"/>
          </sequence>
     </complexType>
</schema>Status.xsd
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="uri:X" targetNamespace="uri:X">
     <element name="Status" type="tns:PurchaseOrderStatus"/>
     <complexType name="PurchaseOrderStatus">
          <sequence>
               <element name="orderid" type="string" nillable="false"/>
               <element name="timestamp" type="string" nillable="true"/>
          </sequence>
     </complexType>
</schema>Abstract.wsdl

<definitions xmlns:tns="urn:poservice" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="uri:X" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
targetNamespace="urn:poservice" name="POService">
     <types>
          <xs:schema>
               <xs:import namespace="uri:X" schemaLocation="PurchaseOrder.xsd"/>
               <xs:import namespace="uri:X" schemaLocation="Status.xsd"/>
          </xs:schema>
     </types>
     <message name="IPurchaseOrder_acceptPO">
          <part name="parameters" element="ns1:PurchaseOrderDocument"/>
     </message>
     <message name="IPurchaseOrder_acceptPOResponse">
          <part name="result" element="ns1:Status"/>
     </message>
     <portType name="IPurchaseOrder">
          <operation name="acceptPO">
               <input message="tns:IPurchaseOrder_acceptPO"/>
               <output message="tns:IPurchaseOrder_acceptPOResponse"/>
          </operation>
     </portType>
</definitions>poservice.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="urn:poservice"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
targetNamespace="urn:poservice" name="POService">
     <import namespace="urn:poservice" location="Abstract.wsdl"/>
     <binding name="IPurchaseOrderBinding" type="tns:IPurchaseOrder">
          <soap:binding style="document"
                         transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="acceptPO">
               <soap:operation/>
               <input>
                    <soap:body use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
          </operation>
     </binding>
     <service name="POService">
        <port name="IPurchaseOrderPort" binding="tns:IPurchaseOrderBinding">
          <soap:address location="http://127.0.0.1:8080/docliteralfromjava/jaxrpc"/>
        </port>
     </service>
</definitions>Thanks

PL/SQL Web Services - JAX-RPC returning in JSON format

Hello all,
I have been searching on the web, inclusively on this forum, for a way of returning data in a JSON format from a PL/SQL web service.
The threads that I have found about this issue are still unanswered.
Does anyone know if it is possible to create a JAX-RPC web service which returns in JSON format ?
Regards,
Pedro

Hi,
JAX-RPX services are SOAP services and thus return XML. You want to use REST instead
Frank

How we can call asynchronous jax-ws web services in OSB 10g r3?

Hello everybody,
We're using the Oracle Service BUS 10.3 here, and we'd like to make some calls from business services to web services in some asynchronous way.
We know Jax-ws provides the callback way and the pooling async way to call it, but as this kind of "operations" are generated in the service consumer stub (and our service consumer rigth now is the OSB itself through the Business Service), we are trying to discover how Oracle Service BUS would use this async feature.
IMHO, the callback approach would be better, since the response pipeline itself should be trigged when the response is ready.
Is the OSB 10.3 ready to use async calls with Jax-WS or we should continue using Jax-Rpc with soap over xml to solve this issue?
Thanks!
Edited by: lucas.teixeira on 26/05/2009 05:05

It is important to remember that in our situation here, we'd like to use the Jax-Ws specification. We could use the Jax-RPC and call our service using the JMS transport and the @WLJmsTransport, we know, but this is out of our plans, since the WL implementation of it will enqueue every requisition in just one consumer for the WS.
Anyone can help us calling async jax-ws services from the OSB ?
Thanks!

J2EE Web services and JAX-RPC

Hello..
While working with J2EE web services using JDeveloper and OC4J, I noticed that it really doesn't confirm to Sun's JAX-RPC standard. The Web Service interface class does not extend the "Remote" and all methods don't throw "RemoteException" as mandated by JAX-RPC standard.
I have few questions:
(1) Are the OC4J J2EE web services completey different from JAX-RPC based web services.??
(2) Does Oracle have any implementation of JAX-RPC??
(3) Is Sun the only one promoting and implementing the JAX-RPC standard? Or are there other players?
thanks...

(1) Are the OC4J J2EE web services completey different from JAX-RPC based web services.??
OC4J J2EE Web Services originate from Oracle/Apache SOAP with several differences:
a. A model where each type of implementation gets a specific servlet (e.g. one for EJB's, one for PL/SQL, one for stateless and stateful Java classes. Architecturally, you can see the picture here:
http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/b10004/orawebservices.htm#1024808
(scroll down a half page for the picture)
b. The packaging of the Web services rather than using the Apache SOAP registration mechanism uses something closer to JSR 109 (also known as Web Services for J2EE, part of J2EE 1.4 with JAX-RPC, SAAJ [SOAP API forAttachments in Java] and JAXP [Java API for XML Parsing]), where the Web service is packaged as an ordinary ear file for deployment.
Oracle built this implementation by extrapolating from the JAX-RPC documentation that was available last year before it was a final specification in an effort to release a production quality Web services implementation that was aligned with JAX-RPC. It has been through two releases - Oracle9iAS 9.02 and Oracle9iAS 9.0.3 and is now being evolved to JAX-RPC as we move to J2EE 1.4.
(2) Does Oracle have any implementation of JAX-RPC??
We are planning to release a JAX-RPC implementation in the new year (I don't have specific dates yet) on OC4J. The production implementation of this will be as seamless a migration as possible from the existing implementation. Oracle9i JDeveloper will also add support for JAX-RPC as a 3rd option in its list of choices available. You can get a sense of how such a migration would work by running the Web services wizard in JDev for Apache SOAP and then, in a separate project, running it for Oracle9iAS J2EE Web Services - imagine there being another option for JAX-RPC. The work to migrate should be as simple as running a wizard or command line utility (known as the Web Services Assembler tool in Oracle9iAS).
(3) Is Sun the only one promoting and implementing the JAX-RPC standard? Or are there other players?
Pretty much every one in the Java side of industry will be implementing JAX-RPC. The important time to note is when J2EE 1.4 is released ... sometime in the new year ... I believe around March but may be mistaken. Part of J2EE 1.4 is required support for JAX-RPC, SAAJ, Web Services for J2EE etc etc. This will standardize the implementation of Web services. Oracle, like others in the industry, supports the standard protocols, (SOAP), interfaces (WSDL) and registries (UDDI) - what J2EE 1.4 does is standardize the packaging, deployment and implementation (the wrappers generated by the tooling).
My guess is that around JavaOne (June 2003) there will be a rash of announcements from J2EE vendors announcing support of JAX-RPC and J2EE 1.4 (or early implementations) as we will be in the same race that happened in 2001/2002 when J2EE 1.3 was the spec to announce implementations around.
Mike.

JAX-RPC and DataHandler

Sorry, I know there has been lots of discussion about sending files with JAX-RPC in this forum, but I haven't found any answers to my problem.
I got the impression that all I needed to do was to write a service having a DataHandler as a method parameter or a return type and JAX-RPC would automatically send it as attachment, but all I got was this error message:
no serializer is registered for (class javax.activation.DataHandler, {http://java.sun.com/jax-rpc-ri/internal}datahandler)
So what else I need to do to get this working? Is there any documentation explaining this, at least the Java Web Services Tutorial doesn't event mention the possibility of sending files.
Heikki

You can use DataHandler classes to add files to your web service messages. You would need to create a client side DataHandler and a server side DataHandler. The Web Service Tutorial doesn't say DataHandler but it is mentioned. Look at the web service tutorial for web service pack 1.3. Chapter 12 --> Advanced JAX-RPC Examples --> SOAP Message Handlers Example.
The basic jist is you manually manipulate the soap message going back and forth.

SOAP over TCP/IP

Hi,
Has anyone implemented SOAP over TCP/IP sockets instead of using a web server? Does JWSDP support this?
Any information and pointers on how to implement this is highly appreciated.
Thanks in advance.
Amogh

WSIT, which is built on top of JAX-WS supports SOAP/TCP. You can get wsit from http://wsit.dev.java.net

RMI-SOAP conversion

Dear techies,
I have an existing RMI Server which I would like to convert to Web Service .
and I found hurdles all the way. Any help in this regard will be much appreciated.
I used JAX-RPC and also tried GLUE from www.themindelectric.com
1) RMI allows me to transport data as well as behaviour , SOAP doesnt.
I have a lot of user defined types for which I have to write Serializers/
Deserializers. To avoid that I have written Java Bean wrappers over
all User Defined types.Am wondering if this will interoperate with
Apache AXIS and other implementations?
By Default JAX-RPC uses 'SOAP section 5 encoding style' can
I plug in some other encoding style such as OMGs XMI ( I dont have
the need , jus curious)
2) Some of the functions that I want to expose as a web service accepts
interfaces. Am stuck on this. I see that XML Schema defines a construct
called abstract in section 4.7 . and I tried a tool named GLUE which
generated WSDL files automatically for my functions that accepts interfaces
and it declared those types as abstract=true . But am not clear on that c
can some one shed some light please. The BIG question is *How Do I expose
a function that accepts interfaces as arguments as a web Service? *
3) My RMI Server allows Notifications to be sent to the client.(sort of
call back). Dunno how to do the same using JAX-RPC?
Or rather can I use JAX-RPC to implements call backs. Or should I use
JAXM to do that? ( I havent used JAXM..dont even know that its used for such
purpose).
Section 2.4.4 of WSDL Specification talks about Notification Operation
How can I realise that thru java ? Or Rather how would I declare My function
such that xrpcc (or that matter any other tool) generates WSDL with a
notification operation .
( Perhaps I can use Multipart MIME to push notifications to the client,
but dunno how to implement them )
The Scenario is as follows
- RMI Client calls a AmInterestedInReceivingUpdates(ClientRef ) function of the server
- The Server Stores the Clients (RemoteReference) in a data structure
- Whenever an update occurs at the server side the server uses the RemoteReference to
invoke the handleUpdate() function of the client
How do I do this using SOAP/JAX-RPC or AXIS or any other?
Thanks and Regards
Sudeep Chandran
The Lesson that I have learnt is if the same species in different planets
communicate they can exchange both data and behaviour . If Different species in
different planets communicate they can exchange only data .

Hi Kevin,
How did WASP help solve your problem?
Am interested in knowing how you have defined the interface in WSDL file.
-Tnx
Sudeep
I guess that answers my question. That is, you can't
get around this problem with JWSDP EA2.
Thanks for the info on GLUE, I am looking into it.
BTW, I have been successful using WASP from Systinet
to make a Jini service available as a Web Service
also.
Thanks,
Kevin Carroll

SOAP Encoding and the real need

I just read the below from the site here-
SOAP encoding has fallen out of favor in the Web services community. It is not supported by the WS-I basic profile. So JAX-WS, as the latest incarnation of Java Web services, has disallowed SOAP encoding. JAX-RPC supports SOAP encoding, so if you really must use SOAP encoded messages, stick with JAX-RPC.
I am new to Web Services and am familiar with DOC/Literal only.
Why will anyone want to create a "new" Web service in Encoded format?
What was the real need SOAPEncoding has served when there is a separate standard named XML Schema?
Just curious to explore-

Hello,
The WS-I work constrains the various web service specification to a
functional subset that exhibit the greatest degree of interoperability;
certainly there are many other features (quality of service, security,
attachments, etc.) that are provided by WebLogic web services; this does
not negate the fact that BP 1.0 compliance can be easily achieved.
Regards,
Bruce
Vasudev Kumarjiguda wrote:
>
Hi,
The Basic Profile 1.0 forbids SOAP encoding, yet Bea WebLogic documentation mentions
that RPC-oriented WebLogic Web Service operations use SOAP encoding.
Am I missing something here (since Bea supports the Basic Profile 1.0) ?
thanks
Vasu

How to consume SOAP over JMS in OESB which is deployeed in Oracle 11g

Oracle 11g Supports only JAX-RPC for SOAP over JMS i.e no response queue configuration.
I have to consume same web service in Oracle ESB ,
Please let me know what configuration required in OESB's business service to consume .

Hi Harshada,
Any good reasons to integrate Share point Jquery mobile application with SMP ?
because Share point web services can be consumed directly in the Jquery mobile applications.
Please look at the below examples to achieve it.
Sample Codes :
Read List Items using Sharepoint Web Services and jQuery | Robert Kuzma on SharePoint, HTML, CSS &amp; JavaScript, …
Pro-Grammar: Calling the SharePoint 2010 GetListItems web services with Jquery
javascript - Getting list data from SharePoint 2010 site using Jquery - Stack Overflow
-Virinchy

How-To: server-based... application policy management

Hi all,
I am at the end of me rope here.
I have a system with an intended client-server architecture - although the server component is not developed/functioning yet.
I have partially integrated JAAS into the system as I need authentication and authorization within my application. It is currently built into the client component for testing purposes, but should be distributed over both at deployemnt time.
And hence my problem: I have developed a database implementation of both the Policy and Configuration classes. These are a part of the server component. I do not want any configuration to be called for on the client -side i.e. preconfiguring of policy files and permissions. I just want an instance of the policy and configuration to be 'downloaded' and installed on the client prior to the security manager being switched on and authentication. This is of course given that runtime authorization occurs on the client.
I would really love to do all this the Java advocated way. I have tried to make sense of Sun Directory Server and Access Manager.... but I am wondering if this is overkill; there is so much talk of what these products can do, but it leaves me with no idea if they are appropriate for the 'little' I want done.
The last thing I want to do is implement my own solution... something I have already researched with a combination of web services, JAX-RPC and SOAP... but it's a big unnecassary headache.
Please advise... anyone.
See also http://forum.java.sun.com/thread.jspa?threadID=576476&tstart=0

Ok,
I solved the problems I described earlier and I have a fully funtional policy implementation. The main features are:
(1) It is distributed to accomodate client-server architectures
(2) Transmitted over the wire with an arbitrary protocol
(3) Is populated from a database
(4) Fully supports JAAS
There are a few glitches with regard to refresh; this maybe due to the fact that my client-server comms is SOAP based.
I can't post code due to contract blah blah... but the least I can do is help troubleshoot; since completing it I can see how stupid my mistakes were and would like to help others avoid the same 'I'M GONNA SCREW YOU PROJECT SCHEDULE' pitfalls that I did ran into.
One word of advice I offer now is to ignore the fact that only getPermissions(CodeSource cs) andrefresh() are abstract - reimplement what ever you need to - it's clear the new PolicyFile implementation has abandoned some/alot of the concepts of the pre 1.4 version and hence the interface is a bit misleading.
Kind regards,
Darren B

Mapping namespace to generated package name (clientgen)

Hello,
We have a need to map the namespace of the generated bean artifacts from clientgen to a different package name. This could be done prior to weblogic 10 with the typePackageName attribute of clientgen but this is no longer supported in weblogic 10. Is there another way to do this? Note we cannot change the namespace of the webservice wsdl we are generating the client for.
Thank you!
Julia Allen

Use the <binding> child element to specify one of the following:
* For JAX-WS, one or more customization files that specify one or more of the following:
o JAX-WS and JAXB custom binding declarations. For more information, see “Customizing XML Schema-to-Java Mapping Using Binding Declarations” in Getting Started With WebLogic Web Services Using JAX-WS.
o SOAP handler files. For more information, see “Creating and Using SOAP Message Handlers” in Programming Advance Features of WebLogic Web Services Using JAX-WS.
* For JAX-RPC, one or more XMLBeans configuration files, which by convention end in .xsdconfig. Use this element if your Web Service uses Apache XMLBeans data types as parameters or return values.
The <binding> element is similar to the standard Ant <Fileset> element and has all the same attributes. See the Apache Ant documentation on the Fileset element for the full list of attributes you can specify.
Note: The <binding> element replaces the <xsdConfig> element, which is deprecated as of version 10.0 of WebLogic Server.
See here for detail.

Webservice invocation question ?

hi,
i had never create nor call a webservice... here the work i have to do :
my environnement is : weblogic 8.1, J2EE 1.3, eclipse.
i am developping a web application, this web applciation has a login form to enable user to connect to the application.
A web service already exits in another weblogicserver (i have the ip, port number, methode name....), this webservice and more specialy its methode checkAuthorization takes two parameters (username,password) and send back 3 result parameteers (res1, res2, res3).
what i have to do, is to create a helper class, let's say "webserviceClient" which invoke thsi webservice and depending on the result, authorize or not the connection.
i began to read the sun tutorial, i understand that there is two ways to do this job, using JAX-RPC or SOAP!!!!
my question is : are this componenet applicationserver dependent, in another way, does weblogic server 8.1 conatins the necessary package to do that ?
my second question is, what is the more easiest way to that ?
i have not a lot of time for doing that :-))),
thanks for your help

Hi Abhi,
Are your Web Service and Enterprise Application which call the web service both are running on the same server?
I think you should check web service processing time of the web service at server side(inside your web service/method) not at the client side. This way you will get better idea about how much time client takes to connect to web service and getting response back.
get elapsed time as Chicon specified at client side, and put similar at server side to get web method processing time like:
// This is you web method
public String webMethod() {
    long webServiceStart = System.currentTimeMillis();
    // Web Service Implementation
    // Web Service Implementation
    long webServiceEnd = System.currentTimeMillis();
    System.out.println("Web Service processing time : " + (webServiceEnd-webServiceStart) + " milliseconds");
}You should get above time almost same in both the case.
Because standalone application needs to connect to server explicitly where as an enterprise application running on same server as your web service is will get it invoked fast compared to standalone application.
Thanks,
Tejas

Using @StreamAttachments

Hi all,
I´m trying to pass a large file in the parameter of my web service. The best way, says Weblogic, is to have the annotation @StreamAttachments and pass the parameter javax.activation.DataHandler that contains a stream.
But when i try to generate the WS files it releases a warning like this:
[WARNING] - The type javax.activation.DataHandler used in parameter zipFile on method integrateDocumentZipData has no default constructor and might not be able to be bound to XML.
I don´t know if this is the problem but when i try to make the client for this WS, it can´t bind the DataHandler type.
I analyze the WSDL and the DataHandler type is mapped to the URL "http://www.bea.com/servers/wls90/wsee/attachment " that dosen´t exist.
Anyone have this kind of problem or uses any other kind of process to pass large content to a WS with high performance??
cheers

Hi,
You can ignore that warning safely. Using DataHandler as parameter of JAX-RPC service method will result in a bea proprietary type. So only WebLogic JAX-RPC client can consume it. You should be able to run [clientgen | http://edocs.bea.com/wls/docs103/webserv_ref/anttasks.html#wp1039270] against that WSDL successfully.
I suggest you take a look at WebLogic JAX-WS [streaming soap attachment | http://edocs.bea.com/wls/docs103/webserv_adv/mtom.html#wp279644] which based on standard MTOM spec.
HTH,
-LJ

JAX-RPX vs. SOAP

Similar Messages

Maybe you are looking for