How to generate JAX-RPC web services instead of JAX-WS webservices withOEPE

How to generate JAX-RPC web services instead of JAX-WS webservices withOEPE? I am asking this because I need to pass xmlbeans generated objects as arguments in the web method. For JAX-WS there has to be a no argument constructor for it to be able to pass in theweb method. The workshop 10.3 was able to pass the xmlbeans generated object as the web service was implemented as a JAX-RPC web service....

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

Similar Messages

How to run a JAX-RPC web service

I wrote the essential interface and classes to build a JAX-RPC web service, and I installed the J2SE 1.4.2 and Java Web Services Developer Pack 1.2 in Windows XP.
I have read the Java Web Services Tutorial, but is so confusing for me.
Anyone can provide the steps about the environment config, compile, package, and run the web service in Tomcat? thx

I wrote these interface and class to create a simple web service:
package test;
import java.rmi.*;
public interface HelloIF extends Remote {
String sayHello(String s) throws RemoteException;
package test;
public class HelloImpl implements HelloIF {
public String sayHello(String s) {
return message + " " + s;
I compiled these 2 and the *.class files exist in D:\backup\JAVA\fyp\test
and then I wrote the config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service name="MyHelloService" targetNamespace="urn:Foo" typeNamespace="urn:Foo" packageName="test">
<interface name="test.HelloIF" />
</service>
</configuration>
I placed the config.xml in D:\backup\JAVA\fyp, then I type the following command:
D:\backup\JAVA\fyp>wscompile -define config.xml -model model.gz
the system response is:
error: RmiModeler error: java.lang.ClassNotFoundException: test$HelloIF
what's wrong?

Calling One Jax RPC Web Service from another in Oracle AS 10.1.3

We have a number of services residing in the same Oracle 10.1.3 app server container. These are deployed as Jax RPC Web Services
I am trying to figure out what are the different options to have once web service invoke an operation on another (without directly linking to the Java code). The reason we want to keep separation as far as possible is that these services may later migrate to different app servers and in the spirit of SOA all we want to change when a service migrates is address and would like everything else to remain the same.
So for example, if Web Service A needs to invoke an operation X in web service B,
One way to do this seems to be to generate a proxy for web service B, include the proxy in Web Service A and then simply do B.X() from Web Service A.
Is this is the best way to do it ?
Are there other alternative approaches available ? Such as using the built in ESB features of Oracle App Server 10.1.3?
Any pointers will be greatly appreciated.
Thanks
RR

Found document of 10.1.3.1.0 how to Creating a Custom Identity Service Plug-in
Oracle® BPEL Process Manager Administrator's Guide
10g (10.1.3.1.0)
Part Number B28982-03
http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28982/plugin.htm
But may be no help.

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

Cannot attach a WS-Policy to Jax-RPC Web Service

I am having trouble trying to associate a WS-Security Policy with a BEA Jax-RPC Web Service?
I am following the following procedure to try to associate a the policy:
http://edocs.bea.com/wls/docs100/ConsoleHelp/taskhelp/webservices/ConfigureWSPolicyFile.html
The problem is that when I navigate on the Administration Console to
Deployments
=> AdapterAdminService (this is the name of my application)
=> com.gateway.admin.wsdl.v10.AdminImpl (this is the name of my Web Service)
=> Configuration
=> WS-Policy
The Web console displays a stacktrace mentioning an "IndexOutOfBoundsException" :
Error opening /jsp/webservice/WebServiceConfigurationWebServicePoliciesForm.jsp.
The source of this error is java.lang.IllegalArgumentException: The property you provided 'contents' of form 'deploymentPlanForm' must not be set to null. at com.bea.console.taglib.html.TableTag.registerDataSet(TableTag.java:1588) at com.bea.console.taglib.html.TreeTableTag.doRegisterDataSet(TreeTableTag.java:49) at com.bea.console.taglib.html.TableTag.doStartTag(TableTag.java:1360) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag9(__webserviceconfigurationwebservicepoliciesform.java:498) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag8(__webserviceconfigurationwebservicepoliciesform.java:459) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag7(__webserviceconfigurationwebservicepoliciesform.java:416) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jspService(__webserviceconfigurationwebservicepoliciesform.java:265) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119) at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:551) at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:363) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:483) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306) at com.bea.netuix.nf.UIControl.render(UIControl.java:578) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at
I have this issue with both IE7 and Firefox 2. My domain is a WLS 10.0MP1 domain and is deployed on my Windows XP laptop.
I am generating the WS from WSDL with the following ant command:
 <wsdlc srcWsdl="${wsdl.location.path}/AdapterAdministration.wsdl"
 destJwsDir="${gen.compiled.wsdl.dir}"
 packagename="com.gateway.admin.wsdl.v10.server"
 destImplDir="server_impl_example" />
then
 <jwsc srcdir="${src.dir}" destdir="${dist.dir}" classpathref="project.class.path" debug="true">
 <jws file="com/gateway/admin/wsdl/v10/AdminImpl.java"
 compiledWsdl="${gen.compiled.wsdl.dir}/AdapterAdministration_wsdl.jar" />
 </jwsc>
and finally, I deploy it with:
 <wldeploy action="deploy"
 name="AdapterAdminService"
 source="${dist.dir}/AdminImpl.war"
 user="${wls.domain.user}"
 password="${wls.domain.pwd}"
 verbose="true"
 stage="no"
 upload="true"
 adminurl="t3://${wls.domain.host}:${wls.domain.port}"
 targets="${wls.domain.servername}" />
Do you have any idea what might be wrong here?
Thanks in advance,
Svend

Hi all,
Some more information: I have created another very simple Jax-RPC Web Service, now using the @Policy annotation. The policy I specify is then correctly taken into account, but I still have the same symptom when I navigate to the Configuration => WS-Policy page on the Web Console (i.e., I cannot associate a WS-Policy to my WS with the Web Console)
Beginning of the JWS file:
@WebService(...)
@WLHttpTransport(serviceUri = "", portName = "AdapterAdmin")
@Binding(Binding.Type.SOAP12)
@Policy(uri="Wssp1.2-Http-UsernameToken-Digest.xml")
public class AdminImpl implements Admin {
Ant task I use to build and deploy the service:
<target name="build-service" depends="prepare">
 <mkdir dir="package"/>
 <mkdir dir="package/WEB-INF"/>
 <mkdir dir="package/WEB-INF/lib"/>
 <jwsc
 srcdir="${src.dir}"
 destdir="package"
 classpathref="project.class.path"
 debug="true">
 <jws
 file="com/gateway/admin/wsdl/v10/AdminImpl.java"
 contextpath="/AdminImpl2"
 explode="true"
 />
 </jwsc>
 <move todir="package/WEB-INF">
 <fileset dir="package/com/gateway/admin/wsdl/v10/AdminImpl/WEB-INF"></fileset>
 </move>
 <move todir="package/META-INF">
 <fileset dir="package/xsize/gateway/admin/wsdl/v10/AdminImpl/META-INF"></fileset>
 </move>
 <copy todir="package/WEB-INF/lib">
 <fileset dir="${lib.dir}"
 includes="client-1.0.jar,
 tools.jar />
 </copy>
 <delete dir="package/com" />
 <jar destfile="${dist.dir}/simpleWS2.war" >
 <fileset dir="package" />
 </jar>
 <wldeploy action="deploy"
 name="AdminService-withPolicyAnnotation"
 source="${dist.dir}/simpleWS2.war"
 user="weblogic"
 password="weblogic"
 verbose="true"
 stage="no"
 upload="true"
 adminurl="t3://localhost:9001"
 targets="AdminServer" />
 </target>
"

Calling One Jax/rpc web service from another.

We have a number of services residing in the same Oracle 10.1.3 app server container. These are deployed as Jax RPC Web Services
I am trying to figure out what are the different options to have once web service invoke an operation on another (without directly linking to the Java code). The reason we want to keep separation as far as possible is that these services may later migrate to different app servers and in the spirit of SOA all we want to change when a service migrates is address and would like everything else to remain the same.
So for example, if Web Service A needs to invoke an operation X in web service B,
One way to do this seems to be to generate a proxy for web service B, include the proxy in Web Service A and then simply do B.X() from Web Service A.
Is this is the best way to do it ?
Are there other alternative approaches available ? Such as using the built in ESB features of Oracle App Server 10.1.3?
Any pointers will be greatly appreciated.
Thanks
RR

Hi all,
I've managed to get this working by using the following property settings:
System.getProperties().setProperty("http.proxyHost", "Proxy_Hostname");
System.getProperties().setProperty("http.proxyPort", "8080");
System.getProperties().setProperty("http.nonProxyHosts", "localhost,hostbox09");
And solving the authentication problem using this property setting on the java cmd line:
-Dweblogic.net.proxyAuthenticatorClassName=com.mycompany.MyProxyAuthenticator
This class is an impl class of weblogic.common.ProxyAuthenticator interface.
The other thing to note is that MyProxyAuthenticator needs to be in the server pre_classpath.
Then I just call JAX-RPC or JAX-WS web service client calls as normal.
Regards,
Paul

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

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

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

OC4j and JAX-RPC Web service.

Hello every one,
this is actually coming from :
OC4j 9.0.3 CMP/CMR and MVCSoft.
Is it possible to develope JAX-RPC webservice using sun jdk with OC4J ?
How can I do it ?
Thanks.
Giuseppe.

Hi,
I should have said that:
I'm stuck with 9.0.3 as the 10.0.3 is a preview
and the final release is not available until
next summer.
I guess 10.0.3 should be better as it is compliant with J2EE 1.4 which should include JAXRPC support.
The problem with 9.0.3 is that being compliant with J2EE 1.3 it does not directly support JAX-RPC.
So I was wondering How to develop Jax-RPC web service using OC4J 9.0.3.
Sorry for to having specified the version.
Thanks.
Giuseppe.

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

How to use user-defined packages in JAX-RPC web service

I am trying to use Object of my class located in my package in jax-rpc webservice,the code is
package supercomputer;
import Hello.*;
public class SuperImpl implements SuperIF
public String sendParam(String data)
Temp ob=new Temp();
int i=ob.get1(10000);
return data+"returned by supercomputer";
Temp is located in Hello package,I have jar the Hello package as Hello.jar and has set its classpath in targets.xml of Ant tool.
The code compiles well and service is deployed successfully,but when i try to call the service from the client its gives me following error.
[echo] Running the supercomputer.SuperClient program....
[java] java.rmi.ServerException: Missing port information
[java] at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:357)
[java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:228)
[java] at supercomputer.SuperIF_Stub.sendParam(SuperIF_Stub.java:60)
[java] at supercomputer.SuperClient.main(Unknown Source)
I dont know if it deploys why it gives error on client side.
Please tell how to use user-defined packages and class in jax-rpc service code ,i am not talking about passing user-defined parameters i am just talking about making objects of user defined classes in jax-rpc service.I think there is some problem in classpath.
Please guide me in doing that.
Thanks,
Farrukh

Farrukh,
I don't know if your error is about a missing class from your custom package, ... what track did you followed to say that?
To use your package in the implementation of you web service, you should only follow the rules of making a web application: put your package jar in your \lib directory inside WEB-INF/ or your package classes unjared in classes (also in WEB-INF/).
As I already said, I have doubts that your error should be originated from a missing class from your package, but:
-try to see the logs (errors?) when you deploy your web service that could give a hint about the problem.
-try to see if you can access your endpoint through your browser to see if there is a online status
-display your config/WSDL file, and the steps you did to build your web service.
regards,
Pedro Salazar.

How to pass SOAP Attachments with JAX-RPC Web Service

I'm confused...
This sample shows how to send/receive SOAP attachments by using the JAX-RPC Handler mechanism. Can somebody confirm if this is the preferred way to do this. I've seen an example wich does something like:
public interface AttachmentService extends Remote {
public String storeDocumentService(javax.activation.DataHandler dh, String filename) throws RemoteException;
}and then uses JAX-RPC utilities to create wsdl, stubs and stuff. Does this have the same result, as what the OTN example shows (from an architecture perspective?
Thx,
Jan.

Well, how an attachment is processed depends on your application logic...if your application logic requires to processing attachments and verify it before processing the SOAP message, handlers could be better option.
If you need to process the attachment while processing the SOAP message, you can do it in the service implementation class.
In both the cases you need to get access to SOAPMessage object and from there get the attachments with getAttachments method.

How to pass XMLNode to JAX-RPc web service

I am new to web services using JAX-RPC.
Here is my problem. I need to pass Node object from org.w2c.dom.Node to webservice (using JAX-RPC) and return canonicalBytes back to client.
I know I cannot pass Node directly as a parameter to the method (checked Java Language Typed supported by JAX-RPC).
So to cheat the system, I put in this Node object into a vector and then passed this vector to web service.
Here is the exception:-
java.rmi.RemoteException: serialization error: no serializer is registered for (class oracle.xml.parser.v2.XMLElement, null); nested exception is:
     serialization error: no serializer is registered for (class oracle.xml.parser.v2.XMLElement, null)
     at com.peppercoin.webservice.security.ISignatureVerification_Stub.getCanonicalBytes(ISignatureVerification_Stub.java:77)
     at HelloClient.main(HelloClient.java:29)
Caused by: serialization error: no serializer is registered for (class oracle.xml.parser.v2.XMLElement, null)
     at com.sun.xml.rpc.encoding.DynamicSerializer.getSerializerForObject(DynamicSerializer.java:69)
     at com.sun.xml.rpc.encoding.DynamicSerializer.serialize(DynamicSerializer.java:52)
     at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.serialize(ReferenceableSerializerImpl.java:59)
     at com.sun.xml.rpc.encoding.soap.CollectionSerializer.serializeArrayElements(CollectionSerializer.java:72)
     at com.sun.xml.rpc.encoding.soap.CollectionSerializer.serializeArrayInstance(CollectionSerializer.java:55)
     at com.sun.xml.rpc.encoding.soap.CollectionSerializerBase.serialize(CollectionSerializerBase.java:98)
     at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.serialize(ReferenceableSerializerImpl.java:59)
     at com.peppercoin.webservice.security.ISignatureVerification_getCanonicalBytes_RequestStruct_SOAPSerializer.doSerializeInstance(ISignatureVerification_getCanonicalBytes_RequestStruct_SOAPSerializer.java:62)
     at com.sun.xml.rpc.encoding.ObjectSerializerBase.serialize(ObjectSerializerBase.java:100)
     at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.serialize(ReferenceableSerializerImpl.java:59)
     at com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:441)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:63)
     at com.peppercoin.webservice.security.ISignatureVerification_Stub.getCanonicalBytes(ISignatureVerification_Stub.java:60)
     ... 1 more
Every works great as long as i put in strings in Vector.
Is there a work around or did i miss anything, Please help
I am using Oracle Parser
Thanks
Sagar Malisetti

You can't "cheat the system" this way. The serializer for Vector is trying to find a serializer for the elements in the Vector instance that it received. So, it is trying to find a serializer for whatever is the the runtime type of your org.w3c.dom.Node. When it can't find such a serializer in the TypeMappingRegistry, it throws the exception.

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

Weblogic 10.3 - Arrays and JAX-RPC Web Services

We are currently looking at migrating from WL 8.1 to WL 10.3, and have an issue with some of our web services (JAX-RPC) with regards to returning String arrays.
We have a web service method that returns a response object. This response object has many properties that includes a property that is a String array. So the code looks something like this (this is a simplified version):
public class OurService
@RemoteMethod
@WebMethod
@WebResult(name = "result")
public ResponseObject lookup(String someParam)
// build the object and its properties here...
return responseObject;
}
This is what the response object looks like:
public class ResponseObject
private String[] someProperty;
public String[] getSomeProperty()
return this.someProperty;
public void setSomeProperty(String[] someProperty)
this.someProperty= someProperty;
}
So the issue is this. In WL 8.1, the web service generator would recognise the fact that the response object had a property that was a String array and would declare as such in the WSDL file, for example:
 <xsd:element xmlns:tp="java:language_builtins.lang" type="tp:ArrayOfString" name="someProperty" minOccurs="1" nillable="true" maxOccurs="1">
</xsd:element>

As a result, when the service is called, the property is returned in the SOAP response like this:
.

<div class="e">
<div class="c" style="margin-left: 1em; text-indent: -2em">
 <someProperty soapenc:arrayType="xsd:string[2]">
</div>
<div>
<div class="e">
<div>
 <string
xsi:type="xsd:string">string1</string>
<string xsi:type="xsd:string">string2</string>
</someProperty>
</div>
</div>
</div>
</div>
.

But, in WL 10.3, the WSDL entry is:
 <xs:element maxOccurs="unbounded" minOccurs="0" name="InstepCodes" nillable="true" type="xs:string">

As a result the property is returned in the SOAP response like this:
 .
 <java:InstepCodes
xmlns:java="java:com.myservice">string1</java:InstepCodes>
 <java:InstepCodes
xmlns:java="java:com.myservice">string2</java:InstepCodes>
The difference here is that WL 10.3 does not return the array of strings as a complex array type, just as a set of repeated elements.
We need to return the array as we do for WL 8 in WL 10.3, because we have external clients that are parsing the response and looking for the XML in this format. We are not currently in a position to ask them to change.
Is this a limitation of the JAX-RPC spec, or WL's implementation of it?
If the service was to return a String array directly from a service method, then it is declared in the WSDL file.
However, if a service returns an object that within itself has a property that is an array, it does not recognise it like it did with WL 8.1.


<div class="e">
</div>

Thank you for the reply.
We are using WL Server 8.1 (not Workshop), and moving to WL Server 10g R3.
We are using the JWSC task to generate the service, which is:
bq. weblogic.wsee.tools.anttasks.JwscTask+
Here is an extract from the Ant build file the calls the task.
<jwsc
srcdir="src/com/ourservice"
sourcepath="src"
destdir="${ear.dir}"
verbose="false"
debug="true"
keepGenerated="true"
classpathref="ws.class.path">
+<module name="${service.name}" explode="true">+
+<jws file="OurService.java" type="JAXRPC"/>+
+</module>+
+</jwsc>+
As stated in my first post, the service method returns an reponse object and its this that contains the array property. The service method itself does not return an array type. This seems to be the root of the problem, i.e. the declaration of array types is not being propagated down through the object graph the service method returns. Below is the code for the service and the response object.
@FileGeneration(remoteClass = Constants.Bool.TRUE, remoteClassName = "OurService", localHome = Constants.Bool.TRUE, localHomeName = "OurServiceLocalHome", remoteHome = Constants.Bool.TRUE, remoteHomeName = "++OurService++Home", localClass = Constants.Bool.TRUE, localClassName = "++OurService++Local")+
@JndiName(remote = "com.ourservice.++OurService++", local = "com.ourservice.++OurService++Local")+
@Session(ejbName = "++OurService++", type = Session.SessionType.STATELESS, transactionType = Session.SessionTransactionType.CONTAINER, maxBeansInFreePool = "100", initialBeansInFreePool = "20", enableCallByReference = Constants.Bool.TRUE, homeIsClusterable = Constants.Bool.TRUE, homeLoadAlgorithm = Constants.HomeLoadAlgorithm.ROUND_ROBIN, isClusterable = Constants.Bool.TRUE, beanLoadAlgorithm = "RoundRobin", defaultTransaction = Constants.TransactionAttribute.SUPPORTS)+
+@RoleMappings( { @RoleMapping(roleName = "Admin", externallyDefined = Constants.Bool.TRUE),+
+@RoleMapping(roleName = "Monitor", externallyDefined = Constants.Bool.TRUE),+
+@RoleMapping(roleName = "JMS", externallyDefined = Constants.Bool.TRUE) })+
@WebService(name = "OurServicePort", serviceName = "OurService", targetNamespace = "http://www.ourservice.com/SOA/OurService+_service")+
+@SOAPBinding(style = SOAPBinding.Style.RPC, use = SOAPBinding.Use.LITERAL)+
@WLHttpTransport(contextPath = "OurService", serviceUri = "OurService", portName = "
*OurService+Port")+
public class OurService
+{+
@RemoteMethod
@WebMethod
@WebResult(name = "result")
{color:#ff0000}public ResponseObject lookup(String someParam){color}
// build the response object...
return {color:#ff0000}responseObject{color};
+}+
This is what the response object looks like:
public class ResponseObject
+{+
private String[] someProperty;
+public {color:#ff0000}String[] getSomeProperty(){color}+
+{+
return this.someProperty;
+}+
public void setSomeProperty(String[] someProperty)
+{+
this.someProperty = someProperty;
+}+
+}+
From all of this I cant tell how we get the WSDL file to delcare it as an array type, as shown in the JAX-RPC 1.1 spec you mentioned, based on the code we have and the JWSC build task we are using.
(I appologise for the formatting of this message. It seems to want to insert + everywhere in the code examples, despite me removing them!)
Edited by: user8013492 on 11-Dec-2008 02:09
Edited by: user8013492 on 11-Dec-2008 02:11

Need HELP passing raw SOAP to JAX-RPC Web Service

Ive recently downloaded the web services development kit from the SUN site and have got all the examples to work fine.
What I am now trying to do is pass RAW SOAP to the HelloWorld JAX-RPC example,
Ive managed to get the service to call the sayHello function with no params which returns 'Hello NULL'.
I can't however get any parameters to be passed to the sayHello function,
Below is the existing SOAP ive got calling the function with no params.
<?xml version="1.0"?>
<soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><sayHello xmlns="http://hello.org/wsdl">????????????</sayHello></soap:Body></soap:Envelope>
If anybody could tell me what I need to replace ???????????? with then I would be more than gratefull.
P.s If I changed the webservice to accept multiple arguments what would I need to put in my SOAP?
Yours,
Cris.

Thanks for your help on this one. However there is still one thing I don`t understand.
In the example SOAP I posted on the orignal message I have added the namespace ns1 pointing to
http://hello.org/wsdl
The example you posted goes to http://caller.org/wsdl
below is SOAP you posted for me.
<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="http://caller.org/wsdl"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<env:Body>
<ns0:sayHello>
<String_1 xsi:type="xsd:string">some text</String_1>
</ns0:sayHello>
</env:Body>
</env:Envelope>
This returns me an error! However If I change ns0 to point to http://hello.org/wsdl it all works perfectly.....
If you open a browser and go to http://hello.org/wsdl OR http://caller.org/wsdl neither URL points to anything!!!!!!! All the other namespaces used point to valid XML Schemas, which makes sense.
So how can this SOAP message work if the namespace ns0 is nothing???????????
Yours,
Cris.

How to generate JAX-RPC web services instead of JAX-WS webservices withOEPE

Similar Messages

Maybe you are looking for