Is JAX-RPC compatible with Apache Axis?

We are starting a new project, and our design goal is to develop server-side API that is the exposed via Web Services. The goal is to have them run within the Sun Reference Implementation, and within Apache Axis.
My question is, if we develop to the JAX-RPC Specification, with occasional SAAJ calls for attachment processing, will our Web Services run within Apache Axis? In other words, it Apache Axis JAX-RPC and SAAJ-compatible?

It seems that the way they handle Attachments is different. Apache Axis seems to have its own way of handling Attachments, even though it is possible that they also support the standard JAX-RPC way.
Generally speaking, I am not very happy with how JAX-RPC handles attachments, but this is a different subject.

Similar Messages

  • Web Service JAX-RPC/SOAP with JAXB

    Hello,
    During my research on JAX-RPC/SOAP as web service technology. I found only simple "helloworld" sample type what using simple String as aurgment. For my task, I required a more complex aurgment such as a complete contact info. I then did some sample code for JAXB and found it to be very useful as a XML/JAVA binding tool. It seems logical to use JAXB to parse and bind the complex aurgment. Though I have not seen any reference to this using it with JAX-RPC. Does JAX-RPC have the tool set to accomplish the same thing? JAX-RPC may have such thing, but using this JAXB seem logical, thus would I still "conform" to the JAX-RPC if I go this route. Any info would be much appreciative.
    Thanks in Advance,
    Mike

    The two JAX-RPC tools that I have used, the reference implementation and Apache Axis both have tools for mappiing XML to classes and vice-versa. Having used JAXB also, I have to say that both of these tools are much easier to use than JAXB.
    As far as whether it will conform, you can make a valid SOAP message using any tool you like.

  • 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

  • Web Services with Apache Axis plugin Weblogic

    Hi,
    I am a newbie to Web Services & Apache Axis. I have plugged in Apache Axis with
    Weblogic 6.1. I wanted to know whether an architecture of the following is possible.
    Web Services published on Apache Axis wrapped on SessionBeans on Weblogic 6.1.
    Also can I get some docs, samples that can help me.
    Any help is appreciated.
    Meghna

    Hi Meghna,
    hmmm...if you are going to start off with webservices, why not go with
    the very best available: WLS 8.1 has:
    - much better schema coverage,
    - rpc, doc-literal and doc-literal-wrapped style
    - async client
    - jms transport
    - security and RM
    - many new ant tasks
    See the full list: http://edocs.bea.com/wls/docs81/webservices.html
    All the features...plus outstanding performance and our award winning
    support.
    Bruce
    Meghna Sinha wrote:
    >
    Hi,
    I am a newbie to Web Services & Apache Axis. I have plugged in Apache Axis with
    Weblogic 6.1. I wanted to know whether an architecture of the following is possible.
    Web Services published on Apache Axis wrapped on SessionBeans on Weblogic 6.1.
    Also can I get some docs, samples that can help me.
    Any help is appreciated.
    Meghna

  • JAX-RPC documentliteral with -model option problems in JWSDP 2.0

    Hello,
    I am trying to deploy a service generated with JAX-RPC. Howeverr when I write URL (http://localhost:8080/webservicedeployable/webservice001) in a browser I am getting message: 404 Not Found: Invalid request. Appending ?WSDL shows propers wsdl code, so endpoint URL is allright.. There is my config file delow:
    <?xml version="1.0" encoding="utf-8"?>
    <configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
      <service name="webservice001"
               targetNamespace="http://scdjws/webservices/wsdl"
               typeNamespace="http://scdjws/webservices/types"
               packageName="com.service001">
        <interface name="service.MyServicePort" servantName="service.MyServiceImpl"/>     
      </service> 
    </configuration>I am using command:
    wscompile -gen:server -f:documentliteral -s "C:\Documents and Settings\Michal\jbproject\mojservice\src\" -classpath WEB-INF/classes -d build -model webservice001.xml.gz config.xml -keepmy jaxrpc-ri.xml is:
    <?xml version="1.0" encoding="utf-8"?>
    <webServices xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
                 version="1.0"
                 targetNamespaceBase="http://java.sun.com/xml/ns/jax-rpc/wsi/wsdl"
                 typeNamespaceBase="http://java.sun.com/xml/ns/jax-rpc/wsi/types"
                 urlPatternBase="/ws">
      <endpoint name="service001"
                displayName="Service 001"
                description="This is service001"
                interface="service.MyServicePort"
                implementation="service.MyServiceImpl"
                model="/webservice001.xml.gz"/>
      <endpointMapping endpointName="service001"
                       urlPattern="/webservice001"/>
    </webServices>I am using Tomcat 5.5.16 and JWSDP 2.0.
    Making a call to the service throws exception:
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/webservicedeployable/webservice001
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:791)
    Thank you in advance for all suggestion.
    Michal

    Hi,
    I reselved the problem by just copying the FastInfoset to the jaxrpc\lib directory (I am sure this should work in a different way).
    Well, the next problem I am getting is that the "XMLStreamWriter" class cannot be found. This class is contained in jsr173_api.jar.
    I guess my main question is the following:
    Which projects are necessary to get this simple helloWorld example to work?
    I did set the JWSDP_HOME varible. Is there another setting I have to make to have all necessary jar-files available and to be able to run the samples?
    Could anybody point me to a tutorial that does not only show a few lines of code (as the HelloWorld sample in the JWSDP-Tutorial) but that would instead lead me through a step-by-step sample application that I write by myself and actually runs at the end? The example in the JWSDP-Tutorial uses all kinds of existing config files which are not explained.
    Thanks for your help.

  • JDeveloper 10.1.3.3.0:  Problem with Apache Axis 1.4 response handler

    I have written both a request handler and a response handler for calling a web service using Apache Axis 1.4.
    The request handler is working, but when the web service returns a soap fault, my response handler is not getting called (I have set breakpoints in both the "onFault" and "invoke" methods of the response handler, which extends "org.apache.axis.handlers.BasicHandler").
    Here is what my WSDD looks like:
    <deployment xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
       <transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/>
       <globalConfiguration>
          <requestFlow>
             <handler name="MyRequestHandler" type="java:com.mycompany.MyRequestHandler"/>
          </requestFlow>
          <responseFlow>
             <handler name="MyResponseHandler" type="java:com.mycompany.MyResponseHandler"/>
          </responseFlow>
       </globalConfiguration>
    </deployment>Thanks!
    Jonathan
    Edited by: user1993443 on Mar 6, 2009 9:03 AM

    The OC4J version with comes in jdeveloper has instaled ADF, is a version prepared to test your aplications and well ready for that.
    The OC4J standalone version is this [http://www.oracle.com/technology/tech/java/oc4j/index.html] and is downloaded separately here [http://www.oracle.com/technology/software/products/ias/htdocs/utilsoft.html] .
    The structured folder of the OC4J standAlone is never is contended inside Jdeveloper folder and when you try to install ADF with ADF runtime installer you only need to map to your OC4J folder base.
    Good Luck.

  • Sun's jax-rpc V.S Apache XML-RPC

    Anyone can enlighten me with the differences between these two? which one is better?

    I too am interested in the opinions of this post. After doing the research I see that for ease of implementation, it looks like XML-RPC is easier/faster to implement, however generates overhead through the creation of the servers to run such. On the JAX-RPC side, I find it not quite as easy to implement, and instead of it's own server it generates a full-fledged web service.
    After looking through these it appears to me that if you want to use one of these for standard RPCs than it would be best to stick to the more mature java.rmi implementations; and if you want to create webservices, jax-rpc definitely helps.
    Am I correct in saying this or am I missing another side of things as well?
    I would enjoy seeing other's opinions of such.
    Llama

  • Jinitiator 1.3 (calling webservice on https with apache axis and jre 1.3)

    I would like to run a PJC component which integrate Axis for communication with webservices located on remote server over https protocol..
    I have made a backend classes with wsdl2java (axis or with SOAPUI)..
    If i run a program with JDK > 1.3 all works fine... but if I run the program with JRE 1.3 (Jinitiator 1.3 PJC) I get the error:
    --> javax.xml.rpc.ServiceException: java.net.MalformedURLException: unknown protocol: https
    javax.xml.rpc.ServiceException: java.net.MalformedURLException: unknown protocol: https
         at arhivskiSistem.InDocArchiveWebServiceLocator.getInDocArchiveWebServiceSoap(InDocArchiveWebServiceLocator.java:100)
         at in2.mikrocop.Test.dokumenti(Test.java:93)
         at in2.mikrocop.Test.testiranje(Test.java:73)
         at in2.mikrocop.Test.main(Test.java:87)my source code is like this:
            System.setProperty("java.net.debug", "all");
            System.setProperty("javax.net.ssl.keyStore", direktorij + keyStore);
            System.setProperty("javax.net.ssl.keyStorePassword", this.getPassword());
            System.setProperty("javax.net.ssl.keyStoreType", "pkcs12");
            System.setProperty("javax.net.ssl.trustStore", direktorij + trustStore);
            System.setProperty("javax.net.ssl.trustStorePassword",  this.getPassword());
            System.setProperty("javax.net.ssl.trustStoreType", "jks");
            InDocArchiveWebServiceLocator ws_locator = new InDocArchiveWebServiceLocator();
            InDocArchiveWebServiceSoap_PortType pt = ws_locator.getInDocArchiveWebServiceSoap();Do you have any Idea how to solve this?

    First, I will start by saying that JInitiator was not intended to run on Win7, especially 64bit. So, it may be time to think about moving to the Java Plugin. Preferably one which is certified with your Forms version.
    To your issue, I suspect you need to change the "Region and Language" settings on the client machine. This can be found on the Control Panel. If that doesn't help, take a look at this:
    http://stackoverflow.com/questions/4850557/convert-string-from-codepage-1252-to-1250

  • 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,

  • Web Service security with Apache Axis. 403 forbidden error

    Hello.
    I have to invoke a Web Service method via https. To achieve that, I have correctly added the server certificate to my truststore.
    When I invoke the method, I obtain this error:
    AxisFault
    faultCode: {http://xml.apache.org/axis/}HTTP
    faultSubcode:
    faultString: (403)Forbidden
    This is because the server requests me for a client certificate.
    I have the certificate, but I don't know how to use it in the java client.
    Does anybody know how to do that? Any kind of help will be very useful.
    Thank you very much in advance.
    NOTE: If I write the url of the web service in a web browser, the server requests me for a client cert. When I chose the appropiate certficate, the web browser shows me this message from the web service: "Hello, this is a Web Service"

    Finally my problem has been solved.
    I added the necesary properties to the system and everything went well.
    This is the code:
    String trustStore = System.getProperty("java.home") + "/lib/security/cacerts".replace('/', File.separatorChar);
    String keyStore = System.getProperty("java.home") + "/lib/security/keystorePKCS12".replace('/', File.separatorChar);
    String tspasswd = "myTrustStorePassword";
    String kspasswd = "myKeyStorePassword";
    System.setProperty("javax.net.ssl.trustStore", trustStore);
    System.setProperty("javax.net.ssl.trustStorePassword", tspasswd );
    System.setProperty("javax.net.ssl.keyStore", keyStore);
    System.setProperty("javax.net.ssl.keyStoreType", "PKCS12");
    System.setProperty("javax.net.ssl.keyStorePassword", kspasswd );It's necesary to say that my keystore is PKCS12 type, and it stores only one pkcs certificate.
    Note that is also posible to set these system properties in the Tomcat start script.

  • Web services - JAX-RPC/Axis/OC4J

    Hi,
    We are planning to expose some of J2EE applications as web service. It is based on JAX-RPC 1.0. I have checked it with Apache-Axis without changing any code and it worked. Will it work in OC4J without any code changes?
    1. Does OC4J or Oracle SOAP server supports(or implements) JAX-RPC?
    2. Do we need to change any code?
    rgds
    Bala Murali

    Right now we have a JAX-RPC 1.1 with JSR 109 support preview here on OTN at - this came out at OracleWorld:
    http://otn.oracle.com/tech/java/oc4j/1003/content_preview.html
    The target production date is summer 2004. There are also plans to do another drop of this preview with updated support later this year and possibly again before the production release.
    We have quite a lot of functionality that we are targetting to flesh out our Web services support in the areas of reliability, orchestration, transactions and security.
    Mike.

  • Jax-ws and apache axis

    This is a newbie question. Can you tell me the difference between jax-ws and apache axis. Is it possible to build web services just using jax-ws and not apache axis. What would be advantages and disadvantages.
    Thanks.

    Yeah you can just use jax ws:http://java.sun.com/developer/technicalArticles/J2SE/jax_ws_2/
    I find it more intuitive. Some would tell you that axis is more bloated :http://blogs.msdn.com/b/dotnetinterop/archive/2008/07/30/changing-of-the-guard-axis-out-jaxws-in.aspx
    I would rather decide between jax ws and REST :https://blogs.oracle.com/enterprisetechtips/entry/implementing_restful_web_services_in

  • Jax-rpc and xsd x:any/

    I am using JAX-RPC to build a client for a web service. Some of the operations on the web service include an <x:any/> element in the response. JAX-RPC generates a corresponding javax.xml.soap.SOAPElement for each of the elements defined as <x:any/>.
    The web service operation, that I am building the client for, is truly generic. It takes in a parameter that is a sql query string and so the respones for the web service could and will be many different sizes and shapes. I'm curious if there are any frameworks that will aid in my handling of the SOAPElement objects. I am currently the JAX-RPC that comes with apache AXIS 1.3 for the web service client.
    Does JAX-RPC or AXIS provide functionality for handling the SOAPElements so that I do not have to write code for each custom query that may be invoked on this web service? I would prefer handIe this in a more generic and abstracted manner. I realize that I can traverse the SOAPElement, but this seems very ugly.
    Are there examples of how this is usually done.?

    Thanks. I am using Hibernate as well. Unfortunately, I did not develop the web service itself and are only tasked with invoking it. We have no control over how the web service is defined or developed. So, I am forced to deal with the SOAPEnvelope. Any insight as to frameworks that will help parse the SOAPEnvelope would be appeciated

  • 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

  • Apache Axis RC1

    Any one have any tips for using JDev 9.0.3 with Apache Axis RC1. I am looking at both JDeveloper and JBuilder and it seems like JBuilder has good support for Axis. Cannot find any support with JDeveloper. Can someone confirm, or give some direction to using JDev with Axis.
    Thanks
    Matthew Drooker

    Thanks, but Tomcat is the server, not OC4J. I have success deploying a web service to OC4J and hitting it from a stored procedure, axis and soap, but:
    I am looking for more information on how to install Axis in the database with loadjava. I have it loaded in the local db, thinking it came from a full install. I am unable to load it in a different db with loadjava due to its class resolutions. The DBAs don't have the information needed to loadjava it there either.
    Any information on loading Axis with loadjava? Something along the lines of "How-to load the Axis stack in Oracle with LoadJava".

Maybe you are looking for