Plugin non-HTTP transports in JAX-RPC

Is it possible to plugin a non-HTTP transports in JAX-RPC?
I know that Apache SOAP provides a way of plugin non-HTTP transports for it,
Is there any document that can teach me to write a non-HTTP transport and plug it into JAX-RPC?

You cannot plug in non-HTTP transports into the JAX-RPC reference implementation.

Similar Messages

RDS 2012 Disable HTTP transport - Enable only RPC over HTTP for both pre 8 and 8 RDP clients

Hi,
Is it possible to enable only RPC over HTTP for both pre 8 and 8 RDP clients?
Thank you

I would like to know this as well.

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

JAX-RPC and non-primitive data types

Hello all!
I am using JWSDP v1.3 and i have a problem using non-primitive data types as return types for my operations.
Consider the helloservice example of the JWSDP1.3 tutorial. Now suppose that instead of having the simple operation sayHello() that returns a String, we execute a query on a database, get some ResultSetMetaData and we want these Metadata to be the return type of our operation. I.e. have the operation
public ResultSetMetaData sayHello()
instead of the
public String sayHello()
of the tutorial.
When trying to build the service i get the following error which is normal, because ResultSetMetaData is not a supported JAX-RPC type.
run-wscompile: [echo] Running wscompile: [echo] C:\jwsdp\apache-ant\../jaxrpc/bin/wscompile.bat -define -d build - nd build -classpath build config-interface.xml -model build/model. gz [exec] error: invalid type for JAX-RPC structure: java.sql.ResultSetMetaData [exec] Result: 1
Is there any way to define an operation like this? Can i specify somehow ResultSetMetaData as a supported-type?
I hope someone can give me some advice on it, because i have lost one evening trying to figure it out myself :)
Regards,
Kostas

Courtesy links to crossposts so people don't waste their time answering a question which has already been answered
http://forum.java.sun.com/thread.jsp?thread=482875&forum=59&message=2253704
http://forum.java.sun.com/thread.jsp?thread=482873&forum=331&message=2253699

JAX-RPC - dynamic wsdl - non-built-in data types

I thought my recent exp with developing a JAX-RPC client using a dynamic wsdl to communicate to a non-weblogic Web Service might help somebody out there. :-)
JAX-RPC Mechanism in Weblogic for dynamic_wsdl seems to work only with built-in data types. Weblogic also supports non-built-in data types, but you need to do some extra work! For the user-defined objects, you need to generate their types and register them.
Note: The samples given in Weblogic 8.1 do not use non-built-in data types!
Make sure you use the ant task "autotype" in your build.xml to generate the appropriate types (objects to support java-xml and xml-java converstion), types.xml from the wsdl. Register the types.xml file in your calling client code.
If you do not use register the types for the user-defined classes used in the web services method signatures, then you are likely to get the foll. exception.
javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementw
eblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml
.soap.SOAPElement class context=TypedClassContext{schemaType=['http://svcVodafonePooled.wsdlgen.jipi
lot.vodafone.com']:getStock}
C:\Tutorial\WS\dynamic_wsdl>ant run
Buildfile: build.xml
run:
[java] Creating the service...
[java] Creating the call...
[java] invoking the call....
[java] javax.xml.rpc.JAXRPCException: failed to invoke operation 'getStock' due to an error in
the soap layer (SAAJ); nested exception is: Message[ failed to serialize interface javax.xml.soap.SO
APElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface
javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://svcVodafonePooled.ws
dlgen.jipilot.vodafone.com']:getStock}]StackTrace[
[java] javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementw
eblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml
.soap.SOAPElement class context=TypedClassContext{schemaType=['http://svcVodafonePooled.wsdlgen.jipi
lot.vodafone.com']:getStock}
[java] at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:328)
[java] at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:297)
[java] at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:645)
[java] at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:206)
[java] at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
[java] at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
[java] at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
[java] at Main.main(Main.java:61)
[java] Caused by: weblogic.xml.schema.binding.SerializationException: mapping lookup failure. c
lass=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://svcVod
afonePooled.wsdlgen.jipilot.vodafone.com']:getStock}
[java] at weblogic.xml.schema.binding.RuntimeUtils.lookup_serializer(RuntimeUtils.java:151)
[java] at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:187)
[java] at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:174)
[java] at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:324)
[java] ... 9 more
[java] ]
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:578)
[java] at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
[java] at Main.main(Main.java:61)
[java] Exception in thread "main"
[java] Java Result: 1

The foll. code worked fine for me in Weblogic 8.1 SP3, on Windows 2000.
Note: the 2 important lines of code:
TypeMappingRegistry registry service.getTypeMappingRegistry();
registry.registerDefault(new DefaultTypeMapping("types.xml"));
package auth;
import java.net.URL;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Service;
import javax.xml.rpc.Call;
import javax.xml.rpc.ParameterMode;
import javax.xml.namespace.QName;
import javax.xml.rpc.encoding.TypeMapping;
import javax.xml.rpc.encoding.TypeMappingRegistry;
import weblogic.webservice.core.encoding.stream.SOAPElementCodec;
import javax.xml.rpc.encoding.*;
import weblogic.webservice.encoding.DefaultTypeMapping;
public class DClient1 {
static private void print(String msg) {
     System.out.println("DClient1: " + msg);
public static void main(String[] argv) throws Exception {
System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
ServiceFactory factory = ServiceFactory.newInstance();
String targetNamespace = "http://www.vishwa.com/amazingworld";
QName serviceName = new QName(targetNamespace, "GeminiPasswordService");
QName portName = new QName(targetNamespace, "GeminiPasswordServicePort");
QName operationName = new QName("", "checkPassword");
URL wsdlLocation = new URL("http://localhost:7001/GeminiPasswordService/GeminiPasswordService?WSDL");
     print("Creating the service...");
Service service = factory.createService(wsdlLocation, serviceName);
     print("Creating the call...");
Call call = service.createCall(portName, operationName);
     TypeMappingRegistry registry = service.getTypeMappingRegistry();
     registry.registerDefault(new DefaultTypeMapping("types.xml"));
     print("invoking the call....");
Object[] inParams = new Object[2];
inParams[0] = "clark1";
inParams[1] = "kent1";
Object result = call.invoke(inParams);
print("Client return value: = " + result.toString());
QName operationName1 = new QName("", "getBook");
print("Creating the call...");
Call call1 = service.createCall(portName, operationName1);
print("invoking the call....");
Name n = new Name();
     n.setFirstname("Walker");
     n.setAge(50);
     Object[] inParams1 = new Object[1];
     inParams1[0] = n;
Book b = (Book) call1.invoke(inParams1);
print("author: " + b.getAuthor());
print("money: " + b.getMoney());
}

Calling a webservice(JAX-RPC) from non java client ?

Hi,
I read JAX-RPC is used for accessing webservices by calling the webservice methods from a java-based client.
Is it possible to call the Webservice methods(writeen using jax-rpc) from a non-java client,who sends his request in the form of SOAP based calls?
If JAX-RPC is not the correct one to call a RPC from a non-java client,In what way i can do this?
Can anyone please clarify my doubt..,
Thanks in Advance
Rao.,

Hi Arun,
Can i write a my client program using cgi scripts?
In the JAX-RPC docs it was said that i can invoke my Webservices through my Service endpoints or using WSDL location?
If iam using a Non-java Client,it will be easier(I think) to use the WSDL file to call the Web-Service(deployed using JAX-RPC).But,the Client should be aware of that WSDL file.
I have to develop a small Application using webServices(must use XML,SOAP technologies).The user will pass some Parameters as request and the Response should be an XML(SOAP message) message.User should be able to request via browser.(http://localhost:8080/)
Can you please suggest me which technology is correct to use,so that i can use the XML,SOAP in it.
Please let me know...,
thank you once again..,
Regards
Rao.,

Https transport support for JAX-WS WebServices

Hi All ,
I am trying to implement JAX-WS WebServices that support https transport .To do so I added the following annotation *@Policy(uri = "policy:Wssp1.2-2007-Https-BasicAuth.xml)* in my Jws Implementation file for the JAX-WS WebServices but I got parsing error.Can anyone please confirm that JAX-WS supports the policy annotation in Impl file.If it is supported can a link/pointer/example could be given to implement https enabled JAX-WS WebService and the required configuration in wsdl file.
Thanks and Regards

It does but you've specified a policy that uses both HTTPS and basic HTTP authentication. If you require just HTTPS use "Wssp1.2-Https.xml". In turn you must enable the SSL port on the WLS server. See this blog post: http://one-size-doesnt-fit-all.blogspot.com/2009/02/enabling-ssl-and-disabling-non-ssl_17.html
If you use JDev to generate the JAX-WS web services, given the policy annotation JDev willl put the policy in the WSDL file appropriately.
CM.

Plugging Own Transport Protocol Implementation in JAX-RPC

Hi,
JAX-RPC provides by Default HTTP as transport implementation. And it also provides interfaces and factory patterns to provide own Implementation of TransportFactory etc. But I can not find a way how can I specify it to instantiate my Implementation of transport factory instead of default HTTPClientTransportFactory.
I was assuming that there must be a way through system property etc to do it. But I did not find it.
It will be great if anybody can give me any insight about it.

Please help me or inform me to whom or where I can contact.....

HTTP Session caching possible using WL7 JAX-RPC ?

We're using WL7, and using the JAX-RPC API to access external webservices.
Basically, we create the appropriate 'stubs' from the target WSDL using
clientgen. Then we invoke the target method. Code looks something like this:
Client_Impl client = new Client_Impl; // implementation of target
ClientPort_Stub stub = client.getClientPort();
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, url)
stub.invoke(args);
Now, when is the actual endpoint URL being created ? Is it when the invoke()
method is called ?
It cannot be during the constructor since I pass the target URL after that ...
My problem is that I have to call the 'invoke' method quite frequently, and hence
would like the HTTP session to be reused, rather than recreated each time. Right
now,
I construct the stub each time I have to call the target method, and I'm wondering
if
I just cache the stub and keep calling the target method each time, will the underlying
HTTP session be reused ? Any ideas ?
Currently, if I do netstat on my Sun Solaris box (where this runs), I see the
TCP
connection being recreated during each invocation ...
-john

Hi John,
You can do multiple invokes on the same stub. There is no
need to create a new one for each invoke.
WLS 7.0 use HTTP 1.0 with keep alive. If the server respects
HTTP keep alive, then WLS will not create a new connection.
HTHs,
-manoj
"john" <[email protected]> wrote in message news:[email protected]..
>
We're using WL7, and using the JAX-RPC API to access external webservices.
Basically, we create the appropriate 'stubs' from the target WSDL using
clientgen. Then we invoke the target method. Code looks something likethis:
>
Client_Impl client = new Client_Impl; // implementation of target
ClientPort_Stub stub = client.getClientPort();
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, url)
stub.invoke(args);
Now, when is the actual endpoint URL being created ? Is it when theinvoke()
method is called ?
It cannot be during the constructor since I pass the target URL after that...
My problem is that I have to call the 'invoke' method quite frequently,and hence
would like the HTTP session to be reused, rather than recreated each time.Right
now,
I construct the stub each time I have to call the target method, and I'mwondering
if
I just cache the stub and keep calling the target method each time, willthe underlying
HTTP session be reused ? Any ideas ?
Currently, if I do netstat on my Sun Solaris box (where this runs), I seethe
TCP
connection being recreated during each invocation ...
-john

Jax-rpc and https and multiple keystores - a limitation?

hi,
When using the JAX-RPC libraries for a web services client application in my app server I want to make use of a different keystore then the one set by using the default system properties.
reason being I have multiple ssl enabled apps runing in the app server and I want to use different client keys in the apps (I use client certificate authentication)
from what I see now I expect this to be not possible - since creating the http(s) connection is completely hidden from a development point of view.
any ideas on the possibilities/impossibilities?
regards Joost ([email protected])

Can you not use command line switches to specify the truststore, e.g.
-Djavax.net.ssl.trustStorePassword=changeit -Djavax.net.ssl.trustStore=truststore_1-4

JWSDP 1.4, JAX-RPC, wscompile, http proxies

I have a JAX-RPC client that works properly. However, I'm trying to modify the client so that RPC calls can go through an http proxy prior to reaching the web service.
Here are some of the problems I'm experiencing:
There are posts on this site, and elsewhere on the net, stating that the wscompile -httpproxy:host:port option can be used to provide this solution. However, wscompile generates the same exact code - whether the httpproxy option is used or not. Is this a problem in JWSDP 1.4?
There are also posts that state to use properties, such as http.proxyHost or proxyHost. I've used several versions of this solution (while using a sniffer to verify network activity), but all that happens is that the code continues to call directly to the web service - not the http proxy. Makes me think these properties are only useful when using http directly. Many of the posts I've seen regarding this are two years old, and I've seen at least three different opinions on how the property strings should be named. Anybody know the real solution?

For me these system properties do work:
proxyHost, proxyPort (maybe also http.proxyHost, http.proxyPort) for Http
https.proxyHost, https.proxyPort for Https
The nice thing is that from a WebStart application or the plug-in these properties are set automatically from the browser configuration if not reconfigured manually.

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.

HTTP Transport Error in Net BEans 6.5

Hello,
I am consuming a web service using JAX-RPC. I am trying to log onto a web interface through my program but I am getting the following error:
Feb 6, 2009 1:10:54 PM ttsample.Engine Login
SEVERE: null
java.rmi.RemoteException: HTTP transport error: java.net.UnknownHostException: http; nested exception is:
Logged in...
HTTP transport error: java.net.UnknownHostException: http
at ttsample.TtsoapcgiPortType_Stub.databaseLogon(TtsoapcgiPortType_Stub.java:819)
at ttsample.Engine.Login(Engine.java:77)
at ttsample.Main.main(Main.java:30)
Caused by: HTTP transport error: java.net.UnknownHostException: http
at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:140)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:96)
at ttsample.TtsoapcgiPortType_Stub.databaseLogon(TtsoapcgiPortType_Stub.java:802)
... 2 more
I searched the web and found that this is a proxy setting proble.
I configured apache earlier to use the local host that run the web client.
When I change the http port host and port number and try to login into the web client its giving me page not found error.So I changed the proxy settings to default and then restarted the system and then tried to log into the web client and it worked.
I dont know where i am going wrong.I want to consume the WSDL and log into the web client but i am gettingthe above error.
Anyone's help will be greatly appreciated.
Thank You,
Sravanthi.

Where did you get the address: http://sal006.salnetwork.com:82/bin/lccountrycodes.cgi (shouldn't the 82 be 83 instead?)

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

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?

Plugin non-HTTP transports in JAX-RPC

Similar Messages

Maybe you are looking for