Weblogic 10.3: web service client enable HTTP/HTTPS connection reuse?

hi all,
i am writing an client app to call a web service, through a client proxy generated by jdeveloper/weblogic.
My question is:
for the weblogic web service client proxy, is it possible to enable HTTP/HTTPS connection reuse/pooling?
i see there is many connection created when calling the web service (by command netstat)?
thank you.
lsp

anybody can help?
thanks

Similar Messages

Web Service client authorization error: HTTP status 401

.NETters,
My .NET client program is invoking a simple "Hello World" Web Service written in ABAP. Here is the code:
Z_HWWSDServiceWse svc = new Z_HWWSDServiceWse();
try {
    string msg = svc.ZHelloworld();
    Console.WriteLine(msg);
}catch(Exception e) {
    Console.WriteLine(e.Message);
The code uses WSE 2.0 framework.
This code works if I edit the properties on WSD service using transaction SICF and specify anonymous login options. However, I would like to pass the user token from the client program itself.
So I removed anonymous login options and supplied the required information programmatically.
UsernameToken ut = new UsernameToken("pradeep", "password", PasswordOption.SendPlainText);
svc.RequestSoapContext.Security.Tokens.Add(ut);
However, when I run this code, I get an error: "The request failed with HTTP status 401: Unauthorized"
I then tried supplementing this code with network credentials logic:
System.Net.CredentialCache cc = new System.Net.CredentialCache();
cc.Add(new Uri("http://servermachname"), "Basic", new System.Net.NetworkCredential("pradeep", "password", null));
svc.Credentials = cc;
The problem still doesn't go away :-(.
Does anyone have any idea on what is it that I am missing in my code?
Thank you in advance for your help.
Pradeep

In my tests with normal .NET WS client something like the following allways worked:
WSProxy proxy = new WSProxy();
proxy.Credentials = new System.Net.NetworkCredential("user", "password");
proxy.PreAuthenticate = true;
proxy.CallMethod();
As your code is very similar, it may be a compatibility problem between WSE and WAS. I would recommend that you use a network snippen and look what really goes over the wire.
I have also seen an issue where the settings in SICF where somehow corrupted (e.g. the fixed credentials checkbock was on, but no credentials where specified). The solution was just to "reset" the settings in SICF.

Unable to create web service client

I am using NetBeans to build the the first-cup example but I have failed in all my attempts to create the web service client for first-cup web module.
The reported error is: "
init:
wsimport-init:
wsimport-client-check-DukesAgeService:
wsimport-client-DukesAgeService:
error: Connection timed out: connect
unknown location
error: java.net.ConnectException: Connection timed out: connect
I have tried to start the sun server application but that doesn't solve the problem.
I have strictly followed the following instructions taken from the first-cup tutorial, found at http://java.sun.com/javaee/5/docs/firstcup/doc/p8.html.
Creating a Web Service Client for the firstcup-war Web Module
The firstcup-war web module must consume the firstcup-dukes-age web service in order to get Duke's current age. For this to happen, you need to create a web service client for the firstcup-war web module.
Creating a Web Service Client for the firstcup-war Web Module
Select firstcup-war from the Project pane.
Select File -> New File.
Select Web Services from the Categories pane.
Select Web Service client from the File Types pane.
Click Next.
Select WSDL URL.
Into the WSDL URL field, enter the following location of the WSDL file of the web service that the web service client will consume.
http://localhost:8080/DukesAgeService/DukesAgeService?WSDL
Into the Package field, enter the following package where the client files will be generated.
com.sun.firstcup.webservice
Click Finish.
Thank you and look forward to hearing from you all.

Hi there.
I don't know what the problem is with NetBeans, but if you see the local copy of the WSDL in the firstcup-war project, you will find that the name of your computer should be there as part of the URL. Change it to 'localhost' or to '127.0.0.1' and it should work.
Example:
<xsd:schema>
<xsd:import namespace="http://webservice.firstcup.sun.com/" schemaLocation="http://localhost:8080/DukesAgeService/DukesAgeService/__container$publishing$subctx/WEB-INF/wsdl/DukesAgeService_schema1.xsd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
</xsd:schema>And...
<port name="DukesAgePort" binding="tns:DukesAgePortBinding">
<soap:address location="http://localhost:8080/DukesAgeService/DukesAgeService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
</port>

How to prevent downloading wsdl in weblogic web service client

Hi,
I get a problem regarding weblogic web service client. My working environment:
weblogic server 8.1
Windows XP SP2
JDK 1.4
I use the weblogic tool to generate the client jar file from the wsdl file.
     <target name="generate-client">
          <clientgen wsdl="ACCESS.wsdl"
               packageName="xxxxxx.client"
               clientJar="${client}/${AccessClient_jar_file}"
               keepGenerated="true"
               saveWSDL="true"
          />
          <javac srcdir="${source}"
          destdir="${client}"
          includes="**/AccessClient.java">
          <classpath>
          <pathelement path="${client}/${AccessClient_jar_file}"/>
          </classpath>
          </javac>
     </target>
After that, I create a client java file to invoke the service deploy in the server.
public static void main(String[] argv)
throws Exception
     int transactionId = 100;
     int id = 1000;
// Setup the global JAXM message factory
System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
// Setup the global JAX-RPC service factory
System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
AccessServicePorts ws = new AccessServicePorts_Impl(argv[0]);
AccessService port = ws.getAccessService();
// Resource - create
Resource resource = new Resource();
resource.setRES_CD("Create ResCo");
resource.setCODE_CODE("code_cod");
resource.setRES_TYPE("Resource typ");
resource.setCOMMON_FIELD(common);
AccessDefaultResult resultItems = port.createResource(resource);
System.out.println("createResource : " + resultItems);
I find that this web service client always issue 2 http requests to invoke an web service method deployed in server.
1st http reqeust:
GET /AccessEpol/EpolServiceSoap?WSDL HTTP/1.1
User-Agent: Java/1.4.2_08
Host: 127.0.0.1:8001
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
the return result is the wsdl downloaded from the server.
2nd http request is the real web service request.
The question is how could I eliminate the 1st http request because it's really unnecessary. I use other web service client like Axis 1.x, Axis client never has the http request to download the wsdl from the server.
I read through weblogic web service document. It do mentions that put saveWSDL="true" in the clientgen ant task. the default value for saveWSDL is true already. I did try saveWSDL="false" also. None of them can eliminate the 1st http request.
appreciate for any answer my question?

Hi David,
thanks for the reply.
More or less I agree some points you mentioned above.
I did use Axis 1.x to test the inter-operability. The web service was developed in Weblogic 8.1 and is a part of an existing web application. It will be merged to existing application deployed in weblogic 8.1.
I also program the web service client to test the web service.
The implementation of the server and client will be handed over the project team and training for supporting or continuous development have to be conducted by me. So I don't like to use two types of technologies which will make thing complex.
I found this issue when I tried to protected the web service endpoint, eg http://localhost:7001/epol/service, using the web application Basic mechanism. The wsdl URL http://localhost:7001/epol/service?WSDL is also protected in this case. Unfortunately the username/password pair is not sent to the server when the weblogic client download the WSDL from the server. In this case, the client failed and throw exception.

Web service client ignores http proxy settings

I have a web service client using Weblogic's web service client library. I'm trying to instruct it to use a http proxy. I've set all the following system properties:
-Dhttp.proxyHost=127.0.0.1
-Dhttp.proxyPort=8080 -Dweblogic.webservice.transport.http.proxy.host=127.0.0.1 -Dweblogic.webservice.transport.http.proxy.port=8080
No traffic is passing through the proxy.
When the proxy is down, the application works fine too. I suspect that the proxy settings are completely ignored for some reason.
I'm using Weblogic 8.1 SP4 on a Windows XP box and JDK 1.4.2 (Sun's bundled JDK with Weblogic).

Sorry about the delay,
You just need to use the standard java http proxy properties, take a look at:
http://download-west.oracle.com/docs/cd/A97329_03/web.902/a95453/useservices.htm
Does this help?
Gerard

HTTP Analyzer help for web service client in 11g

I am using jDev 11.1.1.3.0 to build a web service client (proxy) to a potential vendor's web service. I've used the Http Analyzer before but I'm having trouble configuring it for a WS proxy. I just want to see the SOAP stream between my client and the web service. I used the Web Service Proxy wizard to create the Java code, but the web service provider has kept some of the contract in the WSDL private so that I had to manually generate the meat and potatoes of the Java code. I need to be able to see the SOAP my Java code is sending.
I have tried to configure the Http Analyzer to listen on it's own localhost and port with a forward rule to forward the request to the real WS, but I cannot figure out how to get the client to send it's requests to localhost instead of the actual WS.
Actually, I did figure it out, but then the request fails as it apparently tries to connect to the real WSDL before actually sending the request and cannot find a WSDL at the localhost URL. Here's the error:
Exception in thread "main" javax.xml.ws.WebServiceException: {http://localhost:8099}CatalogRequest is not a valid service. Valid services are: {http://[actual URL here]}CatalogRequest
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:249)
I have also tried to configure the Http Analyzer to somehow 'sniff' the actual URL by listening on the actual URL and port, but either I cannot get the Analyzer to see the request or it fails because the Analyzer is using the same port the request is trying to use.
Can someone explain how to configure the Http Analyzer to see the SOAP stream for a Web Client Proxy?

Hi, I'm just using the default setup for HTTP Analyzer and having no problem using it.
Just make sure to run the HTTP Analyzer first before running or starting your app server (Integrated weblogic Server).

CAPS Web Service client fails in Weblogic 9.2

Hi.
I'm trying to run a web service client, created in CAPS to run in Weblogic 9.2
The web service client runs fine in Sun AS but fails in Weblogic with the message:
javax.ejb.CreateException: Exception occurred during creation of message ...
Are there any specific steps I need to take before deploying my web service client to weblogic?
Any documentation on the subject?
Kind regards
G

Version?
Sincerely,
Ted Ueda

Problems - WLS 10.0 web service client

I'm having a few issues with WLS 10.0 web service client.
          I generated a service control from the WSDL. The service is provided by a 3rd party (non-WLS) at another company. I generated the control within my web project and it's deployed as part of the web application. I experience the following problems with the service control API:
          1) The methods setKeyStore(), setTrustStore(), setClientCert() all seem to be ignored - the server always uses the values set in the server's environment definition. Note - the setEndpointAddress() seems to work.
          2) The client request does not set the 'Content-Type' HTTP header correctly (it's set to text/html) - I have no way to override this via the service control API (that I can see).
          3) I don't see any way/place to turn on more detailed tracing of what's going on internally with the service control invocation - is there a way to enable a detailed trace log of what is happening within the service control?
          Note: I'm able to call the web service via the test client (after importing the 3rd party server cert into my local cacerts).
          Thanks,
          [email protected]

Thank you for the reply..
But im still geting the same error. I have tried to include all the libraries in JWSDP pack but still.. I have managed to narrow down the place where the error occures.. It actually happens when I try to get the WebService Client Servant which is located in the package LSC:
---> LSC.LWServiceGenClient.LWS_Impl service = new LSC.LWServiceGenClient.LWS_Impl();
LSC.LWServiceGenClient.LWSServantInterface lagerServiceServant = LSC.LWServiceGenClient.LWSServantInterface_Stub)service.getLWSServantInterfacePort();
return lagerServiceServant;
Could something be wrong with the way I package the Jar? I'm using Sun One Studio and have tried including the 5 packages the application consists of; I have tried including just the files; moving the main class to <root>.. Still same problem..
Or could there be some different fundemental thingy I have forgotten ??
thanks
Aqoi

Web service client timeout

Hi,
I'm trying to set a timeout on my web service client. But its not working. Your tutorials do not seem to address this.
I am using weblogic 10.3.2, with Java 1.6.
============
Properties propSys = System.getProperties();
propSys.put( "weblogic.webservice.UseWebLogicURLStreamHandler", "true" );
Stub stub = (Stub)portObject;
BindingInfo bindingInfo = (weblogic.webservice.binding.BindingInfo)stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(1);
Iterator itr = stub._getPropertyNames();
while (itr.hasNext()){
Object element = itr.next();
log("\n properties that can be set: "+element);
stub._setProperty("weblogic.webservice.rpc.timeoutsecs","1");
===========
I've also tried setting the transaction-timeout and the remove-client-timeout in the weblogic-ear-jar.xml.
===========
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ExternalEntryEJB</ejb-name>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>ExternalEntry</jndi-name>
<remote-client-timeout>1</remote-client-timeout>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>InternalEJB</ejb-name>
<local-jndi-name>Internal</local-jndi-name>
<enable-call-by-reference>True</enable-call-by-reference>
<remote-client-timeout>1</remote-client-timeout>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
===========
in case it matters, I am using weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask as the clientgen task in my build.xml
============
<clientgen autotype="False" ear="${dist}/${app.earname}" warName="${servlet.warname}" packageName="MyPackage.webservices.client"
keepgenerated="False" useServerTypes="True" clientJar="${dist}/MyAppClient.jar">
<classpath refid="build.classpath.builddir"/>
</clientgen>
============
I am testing by putting a Thread.sleep(75000) in the method which is called in the internal EJB. But the method runs to completion and returns the reply object after 90 seconds or so (it normally takes about 12 seconds), but does not timeout.
I've been told that because it is a web services client, the remote-client-timeout will be ineffective. I've also been told that because the EJBs run in the same JVM, the transaction-timeout will be ineffective. Is this so?
Thanks,
Walter

Can you change the clientgen task to weblogic.wsee.tools.anttasks.ClientGenTask this is for jax-rpc 1.1.
<taskdef name="clientgen"
classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
Hope that helps.

Problem creating web service client using WSM Policies

Hello everyone,
I'm trying to make a simple java client to a Web Service secured using a WSM 11gR1 policy (from Soa Suite 11.1.1.2.0). The policy on the server side is oracle/wss11_x509_token_with_message_protection_service_policy which I attached via the Weblogic Admin Console. To implement the client I'm trying to follow the instructions from this documentation: http://download.oracle.com/docs/cd/E15523_01/web.1111/e13713/owsm_appendix.htm#WSSOV386 section "Policy Configuration Overrides for the Web Service Client" and also I'm using OEPE 11.1.1.3.0 (Eclipse 3.5.0) to develop the client. The only weblogic jar I've added to the build path is the weblogic.jar . Unfortunately, the oracle.wsm.security.util.SecurityConstants.ClientConstants interface (used in the example A-6) is not included in this jar and I have no idea what other libraries should I include in order to follow the example. I tried manualy adding other jars but without success. In fact I found one jar which includes this interface, the wsm-secpol.jar but it does not have the properties described in the documentation, so I guess it's not the right jar, and also I don't think this is the right procedure since there might be another dependent jars. So I would like to know what libraries exactly I should add to the build path (or some other procedure if you noticed I'm doing anything wrong)
Thank you !

Hi
I am having the same problem almost where i wrote a client to comsume a JWS server in https. Where the server is setup to require a certificate to connect to.
My code:
public static void main(String[] args) {
try {
DataBaseSyncServerImpl port = new DataBaseSyncServerImplService().getDataBaseSyncServerImplPort();
int number1 = 20;
int number2 = 10;
System.out.printf("Invoking divide method(%d, %d)\n", number1, number2);
double result = port.divide(number1, number2);
System.out.printf("The result of dividing %d and %d is %f.\n\n", number1, number2, result);
when run this code throw
run:
[java] Invoking divide method(20, 10)
[java] Exception in thread "main" javax.xml.ws.WebServiceException: HTTP transport error: javax.net.ssl.SSLHandshak
eException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCert
PathBuilderException: unable to find valid certification path to requested target
Does any one know how can I solve this problem or how can I make the client be able to use self signed certificates. Any help is greatly apprecited. Thanks

Jax-ws web service client

Hi, I am confused by the web service document http://docs.oracle.com/cd/E17904_01/web.1111/e13758/use_cases.htm#i244846 section 2.4. The Note states:
You can invoke a Web service from any Java SE or Java EE application running on WebLogic Server (with access to the WebLogic Server classpath). Invoking a Web service from stand-alone Java applications that are running in an environment where WebLogic Server libraries are not available is not supported in this release for JAX-WS Web services.If I understand it correctly, it says jax-ws only can be consumed by the clients that have access to wls libraries. My web service client will be 3rd party business parnter. Not sure if they are on wls or not. Does it mean I can't use jax-ws?

When you just use the JAX-WS standard you do not need any WebLogic related classes to create a client for your web service.
When the web service is deployed the WSDL can be accessed. By using this WSDL you can create your client by using tools
such as wsimport (which comes with a JDK distribution and is located in the JDK_HOME/bin directory)
wsimport -keep -d C:\YOUR_PROJECT\src http://hostname:port/context/SomeWebService?wsdlthe 'keep' option make sure the generated .java files are not thrown away.

NPE when working with connections.xml for Web Service client

Our ADF Web Service clients needs to read the WSDL and End point URL from connections.xml. But this is giving an Error.
Here are the details:
jdevloper 11.1.1.6.0
Weblogic 10.3.5
OWSM 11.1.1.6
From my ADF based Application I need to call out a web service.
For this I have built a Web Service Proxy and coded to call it from the application.
Since the app needs to run through the development testing deployment lifecycle and hence be deployed on different environments, we need the ability allow configuration of wsdl and end point URL for the web service call without the need to recompile the app.
We want to leverage the connections.xml for this purpose.
http://docs.oracle.com/cd/E23943_01/web.1111/b31974/web_services.htm#autoId6
My connection.xml looks like:
   <Reference name="MyService" className="oracle.adf.model.connection.webservice.impl.WebServiceConnectionImpl" xmlns="">
      <Factory className="oracle.adf.model.connection.webservice.api.WebServiceConnectionFactory"/>
      <RefAddresses>
         <XmlRefAddr addrType="WebServiceConnection">
            <Contents>
               <wsconnection description="file:/C:/JDeveloper/mywork/jdev116/DeployTstCnnxtnLov/LovProxy/src/abc/lov/proxy/MyService.wsdl" service="{http://xmlns.oracle.com/Enterprise/HCM/services/MyService.1}MyService">
                  <model name="{http://xmlns.oracle.com/Enterprise/HCM/services/MyService.1}MyService" xmlns="http://oracle.com/ws/model">
                     <service name="{http://xmlns.oracle.com/Enterprise/HCM/services/MyService.1}MyService">
                        <port name="MyService_Port" binding="{http://xmlns.oracle.com/Enterprise/HCM/services/MyService.1}MyService_Binding">
                           <soap addressUrl="http://<machine:port>/PSIGW/PeopleSoftServiceListeningConnector" xmlns="http://schemas.xmlsoap.org/wsdl/soap/"/>
                           <operation name="MyServiceOperation">
                              <soap soapAction="MyServiceOperation.v1" xmlns="http://schemas.xmlsoap.org/wsdl/soap/"/>
                              <output name="MyService_RESP.V1"/>
                              <input name="MyService_REQ.V1"/>
                           </operation>
                        </port>
                     </service>
                  </model>
               </wsconnection>
            </Contents>
         </XmlRefAddr>
      </RefAddresses>
   </Reference>
My code in the Service Client Looks like:
@WebServiceRef
private static MyService myservice;
            Context ctx = ADFContext.getCurrent().getConnectionsContext();
            WebServiceConnection wsc =
                (WebServiceConnection)ctx.lookup("MyService");
            String urlString = wsc.getWsdlUrlStr();
            System.out.println("WSDL URL: "+urlString);
            myservice = wsc.getJaxWSPort(MyService.class);
            MyService_PortType port = myservice.getMyService_Port();
ServiceRequest request = new ServiceRequest();
ServiceResponse response = port.MyServiceOeration(request);
The WSDL URL is being read correctly.
Error:
This error appears to be triggered by the code:
    myservice = wsc.getJaxWSPort(MyService.class);
java.lang.NullPointerException
        at java.lang.Class.isAssignableFrom(Native Method)
        at oracle.j2ee.ws.common.jaxws.runtime.GenericJavaType.create(GenericJavaType.java:97)
        at oracle.j2ee.ws.common.jaxws.runtime.GenericJavaType.create(GenericJavaType.java:118)
        at oracle.j2ee.ws.common.jaxws.runtime.OperationMappingModeler.processParameters(OperationMappingModeler.java:268)
        at oracle.j2ee.ws.common.jaxws.runtime.OperationMappingModeler.processMethod(OperationMappingModeler.java:155)
        at oracle.j2ee.ws.common.jaxws.runtime.ServiceEndpointRuntimeModeler.buildRuntimeModel(ServiceEndpointRuntimeModeler.java:114)
        at oracle.j2ee.ws.client.jaxws.WsClientProxyFactory.getRuntimeMetadata(WsClientProxyFactory.java:69)
        at oracle.j2ee.ws.client.jaxws.WsClientProxyFactory.createProxy(WsClientProxyFactory.java:126)
        at oracle.j2ee.ws.client.jaxws.WsClientProxyFactory.createProxy(WsClientProxyFactory.java:106)
        at oracle.j2ee.ws.common.jaxws.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:219)
        at oracle.j2ee.ws.common.jaxws.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:249)
        at oracle.adf.model.connection.webservice.impl.WebServiceConnectionImpl.getJaxWSPort(WebServiceConnectionImpl.java:385)
        at abc.lov.proxy.MyService_PortClient.fetchDesc(MyService_PortClient.java:84)
        at abc.lov.ServiceManager.fetchEmplID(ServiceManager.java:13)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

Hi Frank,
I got the following two lines of code just to check if WebServiceConnection was able to read the connections file alright.
            String urlString = wsc.getWsdlUrlStr();
            System.out.println("WSDL URL: "+urlString);
I am not using urlString for further processing.
The output is
WSDL URL: http://<host>/PSIGW/PeopleSoftServiceListeningConnector/MyService.1.wsdl
java.lang.NullPointerException
        at java.lang.Class.isAssignableFrom(Native Method)
        at oracle.j2ee.ws.common.jaxws.runtime.GenericJavaType.create(GenericJavaType.java:97)
        at oracle.j2ee.ws.common.jaxws.runtime.GenericJavaType.create(GenericJavaType.java:118)
The WSDL Url pointed to is the one that I configure in the connection while deploying the App.
Ran a test and WSDL Url is accessible by the app.

JAX-WS web service client and Windows integrated Security authentication

I am currently developing a JAX-WS web service client running on WebLogic 10.3.2.0. The client is connecting to exchange web service running on IIS.
Everything works well when EWS is configured with Http basic authentication.
The problems started when I changed the autentication method on EWS from Http basic authentication to Windows integrated Security authentication.
The client is then unable to authenticate to the web service. Every request made to EWS returns with the message : Invalid HTTP server response [401] - Unauthorized.
I tried using an authenticator like this one:
static class RetrieveWSDLAuthenticator extends Authenticator
private String username, password;
public RetrieveWSDLAuthenticator(String user, String pass)
username = user;
password = pass;
@Override
protected PasswordAuthentication getPasswordAuthentication()
return new PasswordAuthentication(username, password.toCharArray());
and setting it as the default authenticator :
Authenticator.setDefault(new MyAuthenticator("username", "password"));
but the method getPasswordAuthentication() was not even called.
Is there a way to make a JAX-WS client works with Windows integrated Security ?

WIS is not suppported on WLS JAX-WS. You'll need to use other authentication mechanisms such as http basic (which you tried already), or message-level security such as UNT, or SAML.
Regards,
Pyounguk

Standalone Web Service clients in NetBeans with Reliable Messaging

Following the WSIT tutorial (http://java.sun.com/webservices/reference/tutorials/wsit/doc/index.html) it's possible to create a Web Service with Reliable Messaging and a servlet client which run perfectly, great, but try and create a standalone client in NetBeans and it immediatly fails.
Basically I created a standard Java application, did New->Web Service Client exactly like I had done in the servlet example and then used the Web Service Client Resources -> Call Web Service Operation context menu to add a Web Service call to my java application.
The relevant code:
try { // Call Web Service Operation
            uk.ac.ox.sddag.glassfish.server.NonSecureWSService service = new uk.ac.ox.sddag.glassfish.server.NonSecureWSService();
            uk.ac.ox.sddag.glassfish.server.NonSecureWS port = service.getNonSecureWSPort();
            int x = 0;
            int y = 10;
            int result = port.add(x, y);
            System.out.println("Result = "+result);
            ((Closeable)port).close();
        } catch (Exception ex) {
            System.out.println("Exception:");
            ex.printStackTrace();
        }Result:
Exception:
javax.xml.ws.soap.SOAPFaultException: com.sun.xml.ws.rm.RMException: WSRM3018: Non RM Request or Missing wsa:Action header
        at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
        at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
        at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
        at $Proxy29.add(Unknown Source)
        at nonsecurestandaloneclient.Main.main(Main.java:29)
Caused by: javax.xml.ws.WebServiceException: com.sun.xml.ws.rm.RMException: WSRM3018: Non RM Request or Missing wsa:Action header
        at com.sun.xml.ws.rm.jaxws.runtime.server.RMServerTube.processRequest(RMServerTube.java:343)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
        at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
        at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
        at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:218)
        at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
        at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
        at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
        at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
        at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
        at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
        at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
        at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:176)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
        at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
Caused by: com.sun.xml.ws.rm.RMException: WSRM3018: Non RM Request or Missing wsa:Action header
        at com.sun.xml.ws.rm.jaxws.runtime.server.RMServerTube.handleProtocolMessage(RMServerTube.java:469)
        at com.sun.xml.ws.rm.jaxws.runtime.server.RMServerTube.processRequest(RMServerTube.java:145)
        ... 45 more
BUILD SUCCESSFUL (total time: 1 second)By removing the Reliable Messaging from the Web Service this error goes away. Initially I thought this error might be being caused by not specifying the WebMethod annotations 'action' parameter, but it's definitely set.
package uk.ac.ox.sddag.glassfish.server;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebService;
@WebService()
public class NonSecureWS {
    @WebMethod(action = "add")
    public int add(@WebParam(name = "x") int x, @WebParam(name = "y") int y) {
        return x+y;
}Interestingly, I found that this error also goes away if I add the library webservices-rt.jar from my glassfish libs to the project. Perhaps this is an oversight of NetBeans and should have been added automatically if reliable messaging is enabled, although by default it does have JAX-WS 2.1 jaxws-tools which I'm guessing is for some reason not adequate. JAX-WS version mismatch?

This bug still isn't fixed.
Thank you, adding Glassfish's webservices-rt.jar does fix it.

Web Services Client Library - Options

From what I understand there are multiple options to invoke web services (using a client library). From a performance perspective, has anyone done any tests or have recommendations on which client library is better?
For instance,
- Web Services Client Library with Apache Axis 1.2.1
- JAXRPC based Client Library bundled with BEA Weblogic Server (using 8.1SP3 here)
- JAXRPC Client Library with Sun JWSDP (Java Web Services Developer Pack)
- XMLBeans?
- others...
We are using Doc/Literal (un-wrapped style) Web Services.
Thanks
Hitesh

If this is a DI Real Time Job, you need to Enable Session Security to call the Login/Logout Method. Session Security is enabled on the DI Web Admin Console.

Weblogic 10.3: web service client enable HTTP/HTTPS connection reuse?

Similar Messages

Maybe you are looking for