Invoking JAX-RPC service deployed in SunONE7.0 by jdk1.2/1.3 client

Hi,
Is it possible to invoke a JAX-RPC service deployed in SunONE7.0 by jdk1.2/1.3 client?. If possible what jars should the client have in order to do this?.
warm regards,
Vijay

I used tha JAX-RPC runtime jars that come with JSWDP and was able to sucessfully run the client on JDK1.3 environment. Is there a solution for JDK1.2 client?

Similar Messages

  • Getting SOAPExceptionImpl while invoking JAX-RPC Service

    Hi,
    I am using Static Stub to invoke a service . Both the Client and and Service are deployed on same Tomcat. Service is quite simple that display the Greeting message but when I am calling a service it throws the following exception..
    java.rmi.RemoteException : HTTP Transport Error: com.sun.xml.messaging.saaj.SOAPExceptionImpl;
    Invalid Content-Type "text/html"
    Any idea how to fix this issue ?
    Thanks
    Abdul

    I used tha JAX-RPC runtime jars that come with JSWDP and was able to sucessfully run the client on JDK1.3 environment. Is there a solution for JDK1.2 client?

  • Build soap client to invoke jax-rpc web services

    Hi,
    I would like realize a simple soap java client to invoke a web services starting from wdsl file configuration of my web services.
    Thanks,
    Enrico.

    Hi,
    You can use jax-rpc to invoke the web services by creating stubs classes in your client side using wsdl. If you have ant ,then use wscompile command (in ant) or through dos command passing this wsdl file as parameter to create stubs classes automatically.And then set your classpaths accordingly when calling the web services from your client.
    thanks
    javaonlyjava

  • Exception when running a JAX-WS client against a JAX-RPC service

    I have a JAX-WS client invoking a JAX-RPC web service on Weblogic 10.3. The service was originally built for Weblogic 9.2, it's been rebuilt and runs fine on 10.3.
    Some operations work fine, but invoking one operation results in the following exception:
    at secsvc.client.GetRolesForUserInApplicationResponse$JaxbAccessorF_role.get(Unknown Source)
         at com.sun.xml.internal.bind.v2.runtime.reflect.NullSafeAccessor.get(Unknown Source)
         at com.sun.xml.internal.bind.v2.runtime.reflect.Accessor.getUnadapted(Unknown Source)
         at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl$7.get(Unknown Source)
         at com.sun.xml.internal.ws.client.sei.ResponseBuilder$DocLit$PartBuilder.readResponse(Unknown Source)
         at com.sun.xml.internal.ws.client.sei.ResponseBuilder$DocLit.readResponse(Unknown Source)
         at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
         at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
         at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
         at $Proxy29.getRolesForUserInApplication(Unknown Source)
    This operation works fine if invoked by an RPC client.
    Any idea what's going on?
    Mikey

    Hi Jitu,
    I changed the wsdl. And so I don�t get the warning anymore. My Webservice also runs well, now. Thanks anyway for the reply.
    There is a nice tech article on the sun network, which solved my problem. The basic idea is to split the wsdl into 2 wsdl documents. one containing all the porttypes messages and so on. And the other wsdl contains the binding and service elements.
    If you are interested check out this link:
    http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns/index2.html
    thanks,
    footman

  • How to Invoke a  BPEL service deployed in 10g (10.1.3.5.1) from Spring 2.5

    Hi:
    Can I invoke a BPEL process/service which is deployed on Oracle 10g Release 3 (10.1.3.5.1) using Spring framework 2.5.x?
    Is it the same way we access the webservices using JAX-WS web service proxies provided by Spring?
    Regards
    Sreedhar

    the bpel process is just like any other webservice, so i assume you should be able to invoke it list like a plain other webservice
    http://forum.springsource.org/showthread.php?26088-How-do-you-call-webServices

  • Error while invoking a Web service deployed on OC4J from Oracle BPEL

    Hi,
    I had created a web service from a simple java class using JDeveloper and deployed that on OC4J which had emmited a wsdl for the web service. On the same AS my BPEL processing is deployed in which i had created a partner link by using 1st option (i.e Browse WSDL files from local file system) and invoking the published method of the java class.I am expecting that the method of the class which is deployed as web service will be executed and i will get the return of the method as the response of the invoke activity , but i am getting this error :
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    <part name="summary">
    <summary>when invoking locally the endpoint 'http://localhost:8080/MyIM-JavaCustomerFactory-context-root/JavaCustFactory', ; nested exception is: ORABPEL-02052 Cannot lookup BPEL domain. The BPEL domain "JavaCustFactory" cannot be found; the domain may not have initialized properly. Please verify that the BPEL domain loader has a valid set of initialization properties in the application properties file.</summary>
    </part>
    <part name="detail">
    <detail>ORABPEL-02052 Cannot lookup BPEL domain. The BPEL domain "JavaCustFactory" cannot be found; the domain may not have initialized properly. Please verify that the BPEL domain loader has a valid set of initialization properties in the application properties file.</detail>
    </part>
    </remoteFault>
    It seems that the Invoke activity is not able to get the WebService and it is asking for some settings , if any clue regarding this pls reply.
    I can also give the wsdl also.
    mail me at [email protected]

    Hi,
    Thanx it is working now.
    BTW can you give me some urls with info of this kind of setting which i need to do for other kind of integarions in J2EE platform.Sorry if i am asking too much as i am a starter in this technology.

  • Invoking secured web-service deployed in OC4j

    Hi All
    I have implemented security for web-services(UsernameToken profile) and i have deployed it in the standalone Oc4j
    I am trying to invoke the secured webservice now by passing the below security header in the SOAP message.
    <soap:Header>
    <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
    xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsse:Username>admin</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">admin</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    </soap:Header>
    And i am hitting with the below exception
    WSDoAllReceiver: cannot get SOAP header after security processing; nested exception is:
         org.xml.sax.SAXParseException: &lt;Line 9, Column 48&gt;: XML-20100: (Fatal Error) Expected 'EOF'
    Help me out pls ..
    Thanks in advance
    Kalyan

    (Re: Error: org.xml.sax.SAXParseException: <Line 1, Column 2049>: XML-20100:
    Hi!
    Read this site, maybe the solution is on the bottom of the page:
    http://www.orafaq.com/forum/t/91517/0/
    "3. Verify this file to be a valid xml file. There should be no unwanted extra lines after the last element either."
    "4. Make necessary changes in the file. Save the file."
    "5. Try to deploy the application again."
    Bests!
    Tamas

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

  • Error invoking web service deployed in SOA Suite

    I have implemented a stateful web service in Jdeveloper 10.1.3.2.
    I can test succesfully an operation of the web service from the embedeed oc4j of jdeveloper, but i can not succes when i try do the same from the application server control of soa suite.
    The response of the web service in the second case, is the xml of the request.I can not understand.
    I implemented a web service proxy in jdeveloper that invokes the web service deployed in soa suite.When i run it, it gives me an exception like this:
    unexpected element name: expected={http://orclproject/types/}doLoginResponseElement, actual={http://orclproject/types/}doLoginElement
         at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(LiteralObjectSerializerBase.java:231)
         at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:159)
         at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub._deserialize_doLogin(OrclLoginWSSoapHttp_Stub.java:1022)
         at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub._readFirstBodyElement(OrclLoginWSSoapHttp_Stub.java:891)
         at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:333)
         at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
         at klient7.proxy.runtime.OrclLoginWSSoapHttp_Stub.doLogin(OrclLoginWSSoapHttp_Stub.java:484)
         at orclproject.OrclLoginWSSoapHttpPortClient.doLogin(OrclLoginWSSoapHttpPortClient.java:65)
         at orclproject.OrclLoginWSSoapHttpPortClient.main(OrclLoginWSSoapHttpPortClient.java:28)
    where doLogin is the operation of the web service.
    any idea?
    thanks in advance...

    Hi,
    almost 8 months passed since this post, but if still actual then look at BUG: Request XML returned as response when result too large thread. It may be the same problem with large data sets.
    Regards,
    Patrik

  • 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

  • Invoking a web service via proxy

    Hi,
    I have requirement to invoke a web service protected by basic http authentication.
    I have generated a jax-ws proxy, the proxy makes a local copy of the wsdl.
    And I use the following code to invoke it:
    lDAPUserAdminService = new LDAPUserAdminService();
    LDAPUserAdminServiceSoap lDAPUserAdminServiceSoap = lDAPUserAdminService.getLDAPUserAdminServiceSoap();
    BindingProvider bindingProvider = (BindingProvider) lDAPUserAdminServiceSoap;
    Map<String,Object> rc = (Map<String,Object>)bindingProvider.getRequestContext();
    rc.put(BindingProvider.USERNAME_PROPERTY, "lclient");
    rc.put(BindingProvider.PASSWORD_PROPERTY, "xxxxx");
    lDAPUserAdminServiceSoap.getUser()..
    it works fine for the url that is used to generate the proxy.
    But when I try to invoke the same service deployed on a different server using the following code:
    lDAPUserAdminService = new LDAPUserAdminService(
    new URL("http://10.23.48.132:7003/LDAPAdminServices/user/LDAPUserAdminService.jws?wsdl"),
    new QName("http://www.openuri.org/", "LDAPUserAdminService")); *//gives 401 error*
    LDAPUserAdminServiceSoap lDAPUserAdminServiceSoap = lDAPUserAdminService.getLDAPUserAdminServiceSoap();
    BindingProvider bindingProvider = (BindingProvider) lDAPUserAdminServiceSoap;
    Map<String,Object> rc = (Map<String,Object>)bindingProvider.getRequestContext();
    rc.put(BindingProvider.USERNAME_PROPERTY, "lclient");
    rc.put(BindingProvider.PASSWORD_PROPERTY, "xxxxx");
    lDAPUserAdminServiceSoap.getUser()..
    I get 401 unauthorized error when trying to create the proxy itself trying to access the wsdl.
    Is there any way to pass credentials programatically so that the proxy can access the wsdl.
    Really appreciate any help!!
    Anil

    Hi,
    Have a look at this one...
    http://www.rgagnon.com/javadetails/java-0085.html
    Cheers,
    Vlad

  • Web service deployed to outside of JDeveloper

    Hello, I've created a web service which runs fine within JDeveloper, but I'm running into problems when trying to deploy the WAR to a seperate container, specifically Tomcat. Tomcat throws an ClassCastException because, given the WAR created by JDeveloper, it expects the service endpoint to extend the Servlet API. I see no way to just plug the generated WAR into Tomcat without having to execute additional steps. The only solution I found, being new to both JDeveloper and Web Services, is to manually extract the service classes from the WAR and then use the AXIS client to add the service to Tomcat. I'm wondering if some one has found an easier solution, specifically:
    * is there a way, when creating your web service in JDeveloper, to make the end points more compatible with seperate contianers, i.e. am I using the wrong mapping type or some thing?
    * is there a way, when creating your deployment profiles, to make the generated WARs more compatible with seperate containers? I tried using the Deploy To > Tomcat option but still encountered the same problem.
    Any help would be GREATLY appreciated- we have a small development window (before the Oracle App Server is available) where code developed in JDeveloper will need to be deployed in Tomcat, hence the need. Thanks for your time. Take care.
    Sean

    Hello Sean,
    In Oracle JDevelopeg 10g R3 (10.1.3) the default stack used by Web services is JAX-RPC (the standard J2EE specifications).
    Even if JAX-RPC is a Java EE standard, each vendor (like EJB 1.x and 2.x) has some specific to ave a complete stack. So when you create a JAX-RPC service we have some dependency on some Oracle classes. So you can not directly deploy a WAR build for OracleAS Web Service to anoter container. (it is true the other way, with other vendor implemetation). Currently our Web Service runtime is not portable cross container.
    I think you should be able to use the Sun RI of JAX-RPC on Tomcat but in this case you need to create a specific build/war to be able to generate the correct artifact from your implementation class, SEI and WSDL. The Oracle Web Service team is currently working on a document explaning how you can create JAX-RPC services and deploy them in different container, but it is still an ongoing project and Tomcat is not the first targetted platform.
    Since you look familiar with Apache Axis, it is today the most portable Web Service stack, it has some limitations (support of WS-* for example), but based on your use case it looks using Apache Axis will be the best approach. As you may know Apace Axis is supported on OracleAS 10g R2 and R3.
    Regards
    Tugdual Grall

  • JAX-RPC and JSP

    Hi all,
    I have created a jax-rpc console app which works fine. (its a fairly simple online shop application). I would like to try and implement it via jsp but have never used jsp before.
    I've tried to follow the coffee-bean example, but the jsp has confused the hell out of me. (getting the cb app to run is fine, but separating out the jax-rpc element is a nightmare, what with the taglibs, build files and all). Despite my best efforts, I have failed to get a simple jsp/jax-rpc page to work.
    In so far as I can tell, it requires two builds to install the jax-rpc service, and another build to install the jsp service on the tomcat server. Is this correct?
    It would be much appreciated if anyone could post a simple example of how to get a basic jsp/jax-rpc service to work. A simple hello world would be just fine! :)
    I know I could figure out jsp alone. Thats not really the problem. Its incorporating the jax-rpc service that is killing me! All comments and suggestions are very welcome.
    //Daniel.

    Hi all,
    I have created a jax-rpc console app which works fine.
    (its a fairly simple online shop application). I would
    like to try and implement it via jsp but have never
    used jsp before.I suggest you invest some time in learning how to work with JSP technology. Usually JSP pages call JavaBeans or EJB components to do the work.
    >
    I've tried to follow the coffee-bean example, but the
    jsp has confused the hell out of me. (getting the cb
    app to run is fine, but separating out the jax-rpc
    element is a nightmare, what with the taglibs, build
    files and all). Despite my best efforts, I have failed
    to get a simple jsp/jax-rpc page to work.The Coffee Break application has two JavaBeans components that do the work of calling the JAX-RPC service: RetailPriceList and CheckoutFormBean.
    >
    In so far as I can tell, it requires two builds to
    install the jax-rpc service, and another build to
    install the jsp service on the tomcat server. Is this
    correct?What do you mean by build? To create a JAX-RPC service you have to generate files with tools, compile those files, package into a WAR, and then deploy.
    The web application containing the JSP pages and compiled JavaBeans components is packaged into another WAR and deployed separately.
    >
    It would be much appreciated if anyone could post a
    simple example of how to get a basic jsp/jax-rpc
    service to work. A simple hello world would be just
    fine! :)
    I know I could figure out jsp alone. Thats not really
    the problem. Its incorporating the jax-rpc service
    that is killing me! All comments and suggestions are
    very welcome.We'll take your comments into account for the next version of the Java Web Services Tutorial.

  • JAX-RPC client problems and proxy

    I have deployed a JAX-RPC service in JBoss, but on the client side, I am getting NullPointerException when I attempt to access the service. I believe I'm not creating the proxy in the client properly. Where I need help is:
    1. What should the proper ENDPOINT URI be for the service (my variable "destination" shown below).
    2. What should the code in createProxy() look like?
    WEB Services Shows:
    ===================
    VehicleInfoService ACTIVE
    Address: http://myhost:8080/VehicleInfoService/vehicle
    WSDL: http://myhost:8080/VehicleInfoService/vehicle?WSDL
    Port QName: {http://myhost:8080/wsdl/VehicleInfoService}VehicleInfoServiceIFPort
    Remote interface: testsoap.VehicleInfoServiceIF
    Implementation class: testsoap.VehicleInfoServiceImpl
    Model: http://myhost:8080/VehicleInfoService/vehicle?model
    CLIENT CODE
    ============
    import javax.xml.rpc.*;
    import javax.xml.rpc.Stub;
    import testsoap.*;
    public class TestSOAP
    VehicleInfoServiceIF vehicleInfoServiceInf;
    private String statusMessage = null;
    private static String destination = "http://myhost:8080/VehicleInfoService/v
    ehicle";
    public TestSOAP()
    try
    Stub stub = createProxy();
    // Address of the service
    stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY,
    destination);
    vehicleInfoServiceInf = (VehicleInfoServiceIF)stub;
    catch (Exception ex)
    statusMessage = "Error creating Proxy stub: " + ex.getMessage();
    private static Stub createProxy()
    return(Stub)(new VehicleInfoService_Impl());

    To reply to own posting, I finally discovered that I had a problem with my config.xml file. Once I corrected that, I was able to modify the createProxy entry to:
    private static Stub createProxy()
    return(Stub)(new testacp.VehicleInfoService_Impl().getVehicleInfoServiceIFPo
    rt());
    Corrected config.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <configuration
    xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
    <wsdl location="http://mybox:8080/VehicleInfoService/vehicle?WSDL"
    packageName="testsoap"/>
    </configuration>
    These changes fixed my problem. With the correct entries in config.xml, I no longer got compile errors with "getVehicleInfoServiceIFPort Not Found".

  • Bug/flaw in JAX-RPC xrpcc generated output (JWSDP EA1)

    I believe I have found a bug (or flaw) in how xrpcc (JWSDP EA1) is generating stubs and WSDL code as follows:
    If you use simple parameter types (ints, doubles, Strings et al) then xrpcc generates a name that is based on the type (eg. String_1) rather than the
    parm name (senderID) in the WSDL and stub code. I have noticed, however, that if you are using a JavaBean as an input/output parameter to/from a remote method, it generates an XMLSchema ComplexType with the proper names of subelements, so that situation seems to be OK.
    I think this is a bug/flaw in xrpcc...
    For example, if you try to use a remote method that looks somewhat like:
    public int SendTrajectory( String senderID )
    You get the following fragment generated in the WSDL output from xrpcc:
    <message name="sendTrajectory">
    <part name="String_1" type="xsd:string"/>
    whereas I think it should use the actual parameter name for simple parameters and should look like:
    <message name="sendTrajectory">
    <part name="senderID" type="xsd:string"/>
    I read the JAX-RPC Spec (v 0.7....pdf on the Sun web site) and it seems to allude to the fact that the names SHOULD be based on the parameter name in
    section 5.5.5. where it specifically states:
    "Each Java parameter (in the Java method signature) is mapped to a message part in the wsdl:message. This wsdl:message corresponds to the wsdl:input element for the mapped wsdl:operation. Each message part has a name attribute that is mapped based on the name of the Java parameter and a type attribute (an XML data type)"
    ...and the example the shown further down in that section of the JAX-RPC spec re-inforces this opinion.
    The generated code works with the current version of JAX-RPC and xrpcc, that is not the problem. There is a bigger issue with this situation, since you
    cannot (and should not) assume that a web service (even if generated with JAX-RPC) will be invoked by a client that was generated with JAX-RPC tools.
    The problem is really evident when you don't use JAX-RPC to talk to a JAX-RPC generated service, since you have to use these funny names like String_1, Double_3 which have no application context semantics and thus will invariably lead to some really subtle bugs in remote calls.
    We have used JAX-RPC to generate our server side web service in the normal manner. However, our client is running on an embedded Java (CLDC/MIDP
    level device....on an aJile Java chip in fact) where the JAX-RPC footprint is way too massive for the confines of the MIDP/CLDC platform. So we are using the Enhydra kSoap API and libraries on the client end to invoke the back end JAX-RPC service. This works fine by the way! We have successfully invoked JAX-RPC wrapped services from the embedded Java platform. The
    difficulty stems from the fact that the kSOAP api (and others) require you to bind the values of the parameters for the SOAP invocation by using the WSDL <part> name, and so these funny type-based names become visible in your client application code. Ouch!
    For example, my kSOAP calls to invoke our JAX-RPC service look like this (where request is a SOAP web services request using the kSOAP API's):
    request.addProperty ( "String_1", "SaJe314159" );
    request.addProperty ( "Double_2", pvt.getLatitude() );
    request.addProperty ( "Double_3", pvt.getLongitude() );
    request.addProperty ( "Double_4", pvt.getBearing().floatValue() ) );
    request.addProperty ( "Double_5", pvt.getVelocity() );Whereas it should really look like the following, based on our interface definitions:
    request.addProperty ( "senderID", "SaJe314159" );
    request.addProperty ( "latitude", pvt.getLatitude() );
    request.addProperty ( "longitude, pvt.getLongitude() );
    request.addProperty ( "bearing", pvt.getBearing().floatValue() ) );
    request.addProperty ( "velocity", pvt.getVelocity() );The problem is that xrpcc generates the names as in the first example (String_1, Double_2) instead of using the parameter names (eg. "senderID, latitude).
    We can work around this in two ways for now: 1) use the type-based generated name labels for the moment, or 2) go into the xrpcc generated stub code and WSDL and make manual changes. In the longer term, I'm sure you appreciate why either of these workarounds are not acceptable.
    Based on the above, I think that there is a bug/flaw in this version of xrpcc (it's using a parameter type rather than a parameter name to generate the <message>/<part> element in the WSDL (and of course in the generated stubs and such).
    Thoughts? Fix in EA2 perhaps?
    Thanks!
    ....Andrzej

    I've got the same problem. I edited the WSDL and regenerated both Server and Client classes and it then didn't work. Forget the error but it seemed to have incorrectly capitalised a letter in a class/method name.
    I am trying to define a common WSDL doc that our suppliers must conform to when providing us with a web service. My aim is that the common WSDL will be OK for both Java-based web services and .NET based web services. I have succeeded in this task apart from the method parameter name issue. .NET (of course) does it correctly, and its WSDL correctly names the method parameters. However Java Web Services via xrpcc produce this ridiculous String_1, String_2 etc which bear no relation to the method parameters. I cannot very well go to our suppliers who are using .NET and demand that their method/function parameters are named String_1, String_2 - and wouldn't Bill be pleased with my excuse that I'm trying to get equivalence with the deficiencies of Java ?

Maybe you are looking for