JAX-RPC Asynchronous messaging

I am attempting to create a publish / subscribe service using JAX-RPC (since remote procedure calls are needed through most of the program)... however I have not found any good descriptions / explainations on how to create the remote messaging from the publisher (server) to the consumer (client)... I know this is the JMS forum but there is not a forum dedicated to JAX or SOAP... so I figured this would be the closet one and maybe someone here has experimented with something similar... thanks

There's a brand new forum for Java and Web services, including JAX-RPC.
I'm sure folks there can give you a hand.
http://forum.java.sun.com/forum.jsp?forum=331

Similar Messages

How can I influence the JAX-RPC response message from a void method

Hello,
I used WSDL2Java to create a web service. This service seems to work but the xsi:type="somename" attributes are not included in the response. I want to get them in. Or, otherwise, I want the push webservice just to send an acknowledge message. Because, our client that's pushing the webservice message to us gets error messages.
But, while the webservice is a push service I don't know how to influence the returning soap envelope. This is the webservice method I mean:
public void putDatex2Data(eu.datex2.schema._1_0._1_0.holders.D2LogicalModelHolder body) throws java.rmi.RemoteException {
//the code
Furthermore, has someone good examples of implementations that help to get the real incoming XML message data in a easy way.
Thanks.

No, that's not a feature of the phone.
You can submit feedback to Apple requesting such a feature here:
http://www.apple.com/feedback

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...

Intercepting SOAP XML message in JAX-RPC Handler and calling a diff method

Is it possible to intercept the SOAP XML message in the JAX-RPC handler and avoid the serialization and deserialization (OR avoid XML data binding)
Here is a more detail question
My web service has two methods
1. One Method which accepts Java Object (this object is mapped with a Schema
Complex Type Element in my WSDL file)
2. Second method which accept simple String type.
I want my web service client to send java object (using the first method), so that the Input gets validate in the WSDL itself (before it hits the actual web service) but once the request gets validated i want to pass that converted SOAP XML String (on the Server side using JAX-RPC handler) to the Second method.

The answer to this is that the WSDL had
elementFormDefault="qualified"
in the schema.
Changing to unqualified resulted in the desired output.
Note: The service was changed to handle both cases.

Asynchronous JAX-RPC Web services

In our application we would like to make a non-blocking call
to a single web service ( so we don't need to use BPEL).
Do you have a pointer to the document about creating Asynchronous JAX-RPC Web services and writing client code?
Thanks!
-- Qun

Yes interoperability is the biggest advantage you get with JAX-RPC services.
JAX-RPC spec (JSR 101) defines a standard way in which a web service should be written so that it interoperates between different application servers. It does away with the vendor specific api's and implementation of web services.
Chandar

Store-and-forward SOAP messaging in JAX-RPC ??

JAXM seems dead (although SAAJ lives and is very useful). I want to implement a store-and-forward SOAP messaging system for EAI and give it a Java API. Can I do this in JAX-RPC? Does it make any sense?
Thanks,
Mark

At Java One they were advocating the use of web services over JMS.

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

Using JAX-RPC handlers to proxy web service traffic

Hi,
I want to use JAX-RPC handlers to proxy web service traffic. In some instances the handler should modifiy / verify the message before forwarding the request to the remote web service end-point. Hence, the handler should forward the call by invoking the remote web service. In some cases the result from invoking the remove service should be post-processed by another proxy handler. To ensure that the result from invoking the remote service is available for post-processing I assume that the handler invoking the remote service must add the response message to the message context ( e g setProperty method) in the handler. Is this correctly understood?
I would like to understand that this is a technically feasible and reasonable approach of using JAX-RPC. I'd really appreciate some feedback here.
Many thanks,
Tom

Hi Eric,
Thanks for your response. we are trying to access WSRR( manages end point urls for 7 different environments) and generate the end point dynamically at the design time. As we figured out WSRR is not compatible with OSB we are trying to implement these client side (OSB Proxy service) handlers which would get the dynamic endpoint depending on the environment used. I was able to create the handlers for this and set the jar in the classpath but the client service which should be using these handlers have to have these handlers defined in the deployment descriptor(web.xml) which am unable to see with a OSB project.
Will there be a deployment descriptor(web.xml/webservices.xml) associated with Proxy services on OSB? Or Is there any other way to add custom JAX-RPC Handlers to a proxy service? Or is there any way to connect to WSRR directly?
Thanks,
Swetha

EJB 3.0 and JAX-RPC 1.1 Not Working Together

I've came across a strange behavior when building a JAX-RPC 1.1 service in WebLogic 10 on top of a EJB 3.0 bean:
Business Interface
@Remote
@WebService(targetNamespace="http://coronelado.sf.net")
public interface AuthenticationBO {
boolean login(String email, String password) throws AuthenticationBOException;
Bean
@Stateless(name="AuthenticationBO")
@TransactionManagement(BEAN)
@WLHttpTransport(contextPath="coronelado-service", serviceUri="AuthenticationBOService")
@WebService(endpointInterface="net.sf.coronelado.business.AuthenticationBO")
public class AuthenticationBOBean implements AuthenticationBO {
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0">
<enterprise-beans>
    <session>
      <ejb-name>AuthenticationBO</ejb-name>
      <service-endpoint>net.sf.coronelado.business.AuthenticationBO</service-endpoint>
    </session>
</enterprise-beans>
</ejb-jar>After I deploy the bean, two web services, not one, are listed in the console: AuthenticationBOService and AuthenticationBOBeanService (a duplicate), and the following error message is printed:
[JAM] Warning: failed to resolve class net.sf.coronelado.business.AuthenticationBOBeanAm I missing something here?

http://fernandoribeiro.eti.br/2007/06/27/bug-in-weblogic-10-web-services/

URGENT **** Need help for JAX-RPC Web Service Proxy deploy to OC4J 10.1.3.5

Hi everyone!
I’m really new to web services.
I’m getting a *500 internal server error* while deploying my JAX-RPC web service Proxy to an Oracle AS, in an OC4J, v. 10.1.3.5.0.
Running my client from my development environment (*jdeveloper 10g, 10.1.3.5.0*) everything functions correctly: from jdeveloper I can contact and use the web service defined by the following endpoint: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
I created a "try_ws_client.jsp" file that runs correctly from my local development environment jdeveloper (that uses an embedded oc4j, v. 10.1.3.5.0) but fails when run from the test server (Oracle AS, in an OC4J, v. 10.1.3.5.0), getting, as I mentioned a 500 internal server error, a white page in IE but with FF the message says: The’s an error in the servlet .....
Here's how I created the ws proxy and how I’m using it to consume the ws I mentioned.
1. I used the jdeveloper “Create Web Service Proxy” wizard (File > New > Business Tier > Web Services > Web Service Prox) and in the WSDL document URL I put: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
2. The operation ended without adding nothing to the web.xml file and creating the proxy files. One of them is: FederaMLOLSoapClient.java that have the WS exposed methods (es: public boolean createUser(String) ) + a “main” method with the example how to use this client to consume the WS.
public static void main(String[] args) {
try {
it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
System.out.println("calling " + myPort.getEndpoint());
// Add your own code here
} catch (Exception ex) {
ex.printStackTrace();
3. In FederaMLOLSoapClient.java I’ve create the method "tyIt":
public String tryIt(String username) {
try {
it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
if(myPort.createUser(String username)) {
return “O.K”;
} else {
return “K.O”;
} catch (Exception ex) {
// logs error
4. I created my try_ws_client.jsp file that creates FederaMLOLSoapClient object and calls the tryIt method, printing the “OK” or “KO” message.
<%@ page import="it.reggiocity.provincia.biblioreggiane.*"%>
<%
String message = "";
FederaMLOLSoapClient obj= new FederaMLOLSoapClient( );
message = obj.tryIt(“AAAAAA70R10H226H”);
%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1252"%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"/>
<title>prova</title>
</head>
<body><%=message%></body>
</html>
The situation is:
My try_ws_client.jsp runs correctly from my jdeveloper and the user is created while creating app.ear and deploying it to my Oracle AS/OC4J as mentioned above, I get a 500 Internal Server Error.
Any idea to find a solution to this problem?
Please help.
Take care.
John M.

Hi,
you want to build the Web Service, or you want to consume the Service as a client? If the latter, Web client (ADF?) or Java client?
Frank

JAX-RPC: Web service where both server /and/ client are services?

I'm considering a two-way Web service in an application that I'm designing and would appreciate any insight from prior experience.
This will be a standard client-server application, where the server broadcasts messages and the client, in turn, can request further information about the messages that it receives (think RSS-style updates, but with more interaction). [strong]However[strong], instead of having the client poll the server for new messages, I'd like to have the client register itself with the server as a message listener. The server is currently implemented as a Web service on port X. I'd like the client to register itself with the server, and then receive messages on port Y.
I'm considering a design like the following (note the directions of the inheritance arrows):
( Server class ) --<-- ( RemoteServerImpl class ) -->-- / RemoteServer interface /
|
( Listener class ) --<-- ( RemoteListenerImpl class ) -->-- / RemoteListener interface /Some considerations:
* In both cases, the client and server are broken out into an interface and two classes. The non-Remote classes implement all of the functionality. The RemoteX interfaces declare the methods that will be exposed via RPC, and the RemoteXImpl classes are empty subclasses of the non-Remote classes.
* In order to register itself with the Server, the Listener must be passed in as a method parameter, and thus conform to the JAX-RPC specification for value types. However, value types can't implement java.rmi.Remote.
* Only the Server and Listener know anything about each other.
* This application can be run either remotely or locally, depending on how the Server and Listener are instantiated. For the latter, they're instantiated directly and the listener is registered with the Server. For the latter, the RemoteX interfaces will point to the service stubs.
* I don't see an easy way to allow both the Server and the Listener to have references to each other (at least now without some casting magic), since one of them will have to conform to the value type specification, which requires that all of its fields must be valid JAX-RPC types.
I've got the Server portions implemented and working, and am now going to turn to the Listener stuff. Can anybody see a fundamental problem with this design, or can suggest something better?

Hi There,
Because web services are fundamentally a Services-oriented architecture, and not an Object-oriented one, you are unable to pass objects by reference (only by value) hence the design decision to not allow rmi.Remote objects to be sent across the wire. The best way would be to abstract an object which does itself not represent a server, but a route to a server (lets call it ServerPointer). This must contain address, port, service info, etc.
Now, in your Server class, create a factory method which takes a ServerPointer, and returns a reference to a
remote server, e.g. protected Server createServer( ServerPointer p ) (using the necessary APIs to get such a reference)
Hope this helps...

WLS 8.1 JAX-RPC stubs and SSL

I am part of an industry effort to assess WS interop. We have created a common
WSDL that will be implemented in WAS, .NET and WLS 8.1. As part of this effort,
we are also trying to use two-way SSL authentication. However, I have not found
a way to configure WLS 8.1 JAX-RPC Stubs (generated using clientgen utilities)
to present the client certificates. I have a tried a couple of approaches but
neither of them works with the stubs.
First, I tried using the SSLAdapter (as explained in the "Programming Web Services")
documentation. Unfortunately, the service that I am trying to invoke has only
http binding and trying to invoke it using the SSLAdapter throws an exception
complaining that SSL can't be used on non-https binding.
I tried to try another approach. In this, I tried to invoke https: URL for the
web service instead of using the Adapter. However, in this case, I am getting
a peer certificate not presented exception. Everything that I have checked in
adding a client private key and trusted certificates utilize SSLSocketFactory
(& SSLContext) or HttpsURLConnection objects.
At this point, I have ran out of ideas on how to add SSL to the generated client
stubs to tell the generated StubImpl or ServiceImpl implementations to use a different
SocketFactory or connection. There may be some other global class or property
to set these things up, but I am not aware of those. The server side SSL configuration
seems to working fine, as the requests with SSL configuration of "Request Client
certificate but don't enforce it' seems to work fine.
Any responses and suggestions are greatly appreciated.
Thanks
Raj

Did you check out :
http://webservice.bea.com/
There is a 2 way SSL example here:
http://webservice.bea.com/SSL2way.zip
HTHs.
http://manojc.com
"Seshadri Rajagopal" <[email protected]> wrote in message
news:3ec24d41$[email protected]..
>
I am part of an industry effort to assess WS interop. We have created acommon
WSDL that will be implemented in WAS, .NET and WLS 8.1. As part of thiseffort,
we are also trying to use two-way SSL authentication. However, I have notfound
a way to configure WLS 8.1 JAX-RPC Stubs (generated using clientgenutilities)
to present the client certificates. I have a tried a couple of approachesbut
neither of them works with the stubs.
First, I tried using the SSLAdapter (as explained in the "Programming WebServices")
documentation. Unfortunately, the service that I am trying to invoke hasonly
http binding and trying to invoke it using the SSLAdapter throws anexception
complaining that SSL can't be used on non-https binding.
I tried to try another approach. In this, I tried to invoke https: URL forthe
web service instead of using the Adapter. However, in this case, I amgetting
a peer certificate not presented exception. Everything that I have checkedin
adding a client private key and trusted certificates utilizeSSLSocketFactory
(& SSLContext) or HttpsURLConnection objects.
At this point, I have ran out of ideas on how to add SSL to the generatedclient
stubs to tell the generated StubImpl or ServiceImpl implementations to usea different
SocketFactory or connection. There may be some other global class orproperty
to set these things up, but I am not aware of those. The server side SSLconfiguration
seems to working fine, as the requests with SSL configuration of "RequestClient
certificate but don't enforce it' seems to work fine.
Any responses and suggestions are greatly appreciated.
Thanks
Raj

JAX-RPC And Non-Java Web Service

Hi,
This is a total shot in the dark. I'm attempting to consume an RPC web service developed in Delphi. I've created a JAX-RPC client in NetBeans from the published WSDL, attached below. I've created calls to several of the procedures available. What's bizarre, at least to me, is that half of them work fine and half of them don't. In all cases where they don't I'm getting a returns SOAP envelope indicated an access violation, attached below. There are no errors in any of the server logs and the developer assures me that the procedures do, in fact, work from his client (also developed conveniently enough in Delphi).
I'm willing to take him at face value for the moment and assume that the problem is in my client implementation, although I have no idea where it would lie. The only difference I've been able to gather between the features which work and those that don't is the size of the return package...it would most likely be much larger than the ones that don't work.
The service is an ISAPI dll running under IIS on Windows Server 2003. Any clues or guidance anyone would be willing to provide would be most welcome. On to the files:
There wasn't enough room to post the entire thing so I've included one working (CheckStock) and non-working (GetLibTrace) function.
WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" name="IInnovaServiceservice" targetNamespace="http://tempuri.org/" xmlns:tns="http://tempuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/">
<message name="CheckStock2Request">
    <part name="OPC" type="xs:string"/>
</message>
<message name="CheckStock2Response">
    <part name="QTY" type="xs:int"/>
    <part name="messages" type="xs:string"/>
    <part name="return" type="xs:int"/>
</message>
<message name="GetLibTrace5Request">
    <part name="LibName" type="xs:string"/>
</message>
<message name="GetLibTrace5Response">
    <part name="dimensions" type="xs:string"/>
    <part name="messages" type="xs:string"/>
    <part name="return" type="xs:int"/>
</message>
<portType name="IInnovaService">
    <operation name="CheckStock">
      <input message="tns:CheckStock2Request"/>
      <output message="tns:CheckStock2Response"/>
    </operation>
    <operation name="GetLibTrace">
      <input message="tns:GetLibTrace5Request"/>
      <output message="tns:GetLibTrace5Response"/>
    </operation>
</portType>
<binding name="IInnovaServicebinding" type="tns:IInnovaService">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="CheckStock">
      <soap:operation soapAction="urn:InnovaServiceIntf-IInnovaService#CheckStock" style="rpc"/>
      <input>
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:InnovaServiceIntf-IInnovaService"/>
      </input>
      <output>
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:InnovaServiceIntf-IInnovaService"/>
      </output>
    </operation>
    <operation name="GetLibTrace">
      <soap:operation soapAction="urn:InnovaServiceIntf-IInnovaService#GetLibTrace" style="rpc"/>
      <input>
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:InnovaServiceIntf-IInnovaService"/>
      </input>
      <output>
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:InnovaServiceIntf-IInnovaService"/>
      </output>
    </operation>
</binding>
<service name="IInnovaServiceservice">
    <port name="IInnovaServicePort" binding="tns:IInnovaServicebinding">
      <soap:address location="http://172.20.10.145:8080/innovaservice.dll/soap/IInnovaService"/>
    </port>
</service>
</definitions>My client:
package com.signet.innova.client;
import com.signet.innova.client.interfaces.IInnovaService;
import com.signet.innova.client.interfaces.IInnovaServiceservice_Impl;
import java.net.URL;
import java.rmi.RemoteException;
import java.util.ArrayList;
import javax.xml.namespace.QName;
import javax.xml.rpc.Stub;
import javax.xml.rpc.holders.Holder;
import javax.xml.rpc.holders.IntHolder;
import javax.xml.rpc.holders.StringHolder;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.Dispatch;
import javax.xml.ws.Service;
public class InnovaClient {
    private void testConnection() {
        Stub stub = createProxy();
        IInnovaService service = (IInnovaService) stub;
        StringHolder sh1 = new StringHolder();
        StringHolder sh2 = new StringHolder();
        StringHolder sh3 = new StringHolder();
        IntHolder ih1 = new IntHolder();
        IntHolder ih2 = new IntHolder();
        IntHolder ih3 = new IntHolder();
        try {
            System.out.println("Calling checkStock()");
            service.checkStock("0103877866", ih1, sh1, ih2);
            System.out.println(" service returned => " + ih1.value + ":" + sh1.value + ":" + ih2.value);
        } catch (RemoteException re) {
            System.out.println(" service returned => " + re.toString());
        try {
            System.out.println("Calling getLibTrace()");
            service.getLibTrace("REGULAR", sh1, sh2, ih3);
            System.out.println(" service returned => " + sh1.value + ":" + sh2.value + ":" + ih1.value);
        } catch (RemoteException re) {
            System.out.println(" service returned => " + re.toString());
    private Stub createProxy() {
        return (Stub) (new IInnovaServiceservice_Impl().getIInnovaServicePort());
    public static void main(String[] args) {
        InnovaClient client = new InnovaClient();
        System.out.print("Running testConnection()...");
        client.testConnection();
}The request and response packets are in my reply below. Ran out of characters. :o)
Edited by: Pablo_Vadear on Dec 22, 2009 11:19 PM

Correction from above...".it would most likely be much larger than the ones that don't work" should have been "it would most likely be much larger IN THE ONES THAT DON'T WORK". Sorry.
The request:
POST /innovaservice.dll/soap/IInnovaService HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Content-Length: 484
SOAPAction: "urn:InnovaServiceIntf-IInnovaService#CheckStock"
User-Agent: Java/1.6.0_17
Host: 172.20.10.145:8080
Connection: keep-alive
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="urn:InnovaServiceIntf-IInnovaService" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ns0:CheckStock><OPC xsi:type="xsd:string">0103877866</OPC></ns0:CheckStock></env:Body></env:Envelope>POST /innovaservice.dll/soap/IInnovaService HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Content-Length: 491
SOAPAction: "urn:InnovaServiceIntf-IInnovaService#GetLibTrace"
User-Agent: Java/1.6.0_17
Host: localhost:8080
Connection: keep-alive
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="urn:InnovaServiceIntf-IInnovaService" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ns0:GetLibTrace><LibName xsi:type="xsd:string">REGULAR</LibName></ns0:GetLibTrace></env:Body></env:Envelope>And the response:
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><NS1:CheckStockResponse xmlns:NS1="urn:InnovaServiceIntf-IInnovaService"><return xsi:type="xsd:int">0</return><QTY xsi:type="xsd:int">0</QTY><messages xsi:type="xsd:string">Item 0103877866 retrieved OK.
Right side OPC.
</messages></NS1:CheckStockResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
HTTP/1.1 200 OK
Date: Tue, 22 Dec 2009 23:18:40 GMT
Server: Microsoft-IIS/6.0
Content-Type: text/xml
Content-Length: 486
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultactor/><faultcode>SOAP-ENV:Server</faultcode><faultstring>Access violation at address 00000000. Write of address 00000000</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>Any help appreciated.
Edited by: Pablo_Vadear on Dec 22, 2009 11:23 PM

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

Sending attachments using JAX-RPC

Hi,
can anyone give me an example for sending an attachment using JAX-RPC. I want to create a webservice that will expect an attachment. Also once the client snds the attachment how can i access it in the service?
any help will be apreciated. Thanks.

Did anyone test this?
I am using a DataHandler in the server
public String sendDocument(String name, DataHandler dh)
DataHandler rdh = (DataHandler) dh;
     if (dh == null)
          return message+ "Received null attachment";
     DataSource ds = rdh.getDataSource();
     try
          dh.writeTo(new FileOutputStream("D:\\temp\\" + name));
     catch(java.io.IOException e)
     return message + " Processed attachment " + ":Stream Error: " + e.getMessage();
     return message + " Processed attachment" ;
In the client I use Proxy which works fine:
FileDataSource fs = new FileDataSource(fileName);
if (fs == null)
     System.out.println("Invalid File Source");
DataHandler dhSource = new DataHandler(fs);
     System.out.println(up.sendDocument(dhSource.getName(), dhSource));
THIS WORKS FINE. I see the attachment is saved properly.
When I try using DII:
call.setOperationName(new QName(BODY_NAMESPACE_VALUE,"sendDocument"));
QName QNAME_TYPE_DH = new QName(NS_XSD, "DataHandler");
call.addParameter("String_1", QNAME_TYPE_STRING,ParameterMode.IN);
call.addParameter("DataHandler_1", QNAME_TYPE_DH,ParameterMode.IN);
FileDataSource fs = new FileDataSource(fileName);
if (fs == null)
     System.out.println("Invalid File Source");
else
          DataHandler dhSource = new DataHandler(fs);
          String dhName = dhSource.getName();
     Object[] params = new Object[] {dhName,dhSource};
     String result = (String)call.invoke(params);
     System.out.println(result);
THIS DOES NOT WORK. I get an error.
[java] serialization error: no serializer is registered for (class javax.activation.DataHandler, {http://www.w3.org/2001/XMLSchema}DataHandler)
ANY POINTERS??????
I even tried this:
QName qnameAttachment = new QName(NS_XSD, "DataHandler");
TypeMappingRegistry tr = service.getTypeMappingRegistry();
TypeMapping tm = tr.createTypeMapping();
tm.register(DataHandler.class,
qnameAttachment,
new JAFDataHandlerSerializerFactory(),
new JAFDataHandlerDeserializerFactory());
     tr.registerDefault(tm);
NO SUCCESS!
Appreciate any responses....

JAX-RPC Asynchronous messaging

Similar Messages

Maybe you are looking for