Non-ACC client for WSIT enabled services

Hallo All,
Can anyone tell me how I could develop a non-ACC java client for SSL enabled web service/Reliable Messaging enabled web services.
As of now, I am able to access these services with clients deployed in ACC containers of Glassfish V2UR1.
I read some thing about glassfish connectors, but did not get a clear picture. I don't believe that Glassfish doesn't have support for non-ACC clients.
Thanks a lot in advance.

Similar Messages

Iplanet connect exception when usig non acc client

I am trying to connect a non acc client to my appserver. I have everything set up according to the sample program provided by sun. When i execute the client it "hangs" at the contect initialization line (Context initial = new InitialContext(env).
when I check the log for the appserver it has the following error:
com.iplanet.ias.cis.connection.ConnectException: com.iplanet.ias.cis.channel.tcp.TCPNativeException: -5973:EndPoint.JNI_getValidAddressNative: PR_GetHostByAddr() Failed
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:205)
at com.iplanet.ias.cis.connection.ServerConnection.accept(ServerConnection.java:251)
at com.sun.corba.ee.internal.iiop.ListenerThread.run(ListenerThread.java:77)
Caused by: com.iplanet.ias.cis.channel.tcp.TCPNativeException: -5973:EndPoint.JNI_getValidAddressNative: PR_GetHostByAddr() Failed
at com.iplanet.ias.cis.connection.EndPoint.getValidAddressNative(Native Method)
at com.iplanet.ias.cis.connection.EndPoint.getValidAddress(EndPoint.java:239)
at com.iplanet.ias.cis.connection.EndPoint.<init>(EndPoint.java:101)
at com.iplanet.ias.cis.connection.EndPoint.getEndPoint(EndPoint.java:73)
at com.iplanet.ias.cis.connection.EndPoint.getEndPoint(EndPoint.java:78)
at com.iplanet.ias.cis.channel.tcp.TCPChannel.getLocalEndPoint(TCPChannel.java:68)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:202)
... 2 more
any idea what I am doing wrong?

Were you ever able to resolve this problem? If so, please let me know how at [email protected]
thanks
suneet

Error when uninstalling App-V RDS client: Product: Microsoft Application Virtualization (App-V) Client for Remote Desktop Services 5.0 Service Pack 2 x64 -- Error 1324. The folder path 'C:' contains an invalid character

Issue: experienced when attempting to uninstall the App-V 5.0 SP2 RDS client.
Event Log: Product: Microsoft Application Virtualization (App-V) Client for Remote Desktop Services 5.0 Service Pack 2 x64 -- Error 1324. The folder
path 'C:' contains an invalid character
Symptoms (when in this current state):
Unable to uninstall the SP2 client
You can upgrade the client (via hotfix) and uninstall the hotfix, but you will not be able to remove the SP2 client
AppvVfs filter driver will not create an instance, therefore applications will not be able to read into existing streamed VFS content, or trigger sparse files to stream content. (you can still stream the content via other means, like the UI or powershell)
Because of the AppvVfs filter driver not instantiating, applications that depend on licences that exist in VFS will not be able to be read causing certain applications to react as if the license does not exist or is an incorrect format

Resolution:
Check for the existence of a hidden folder named %appdata% in the C:\Program Files\Microsoft Application Virtualization\Client folder. (You will need to un-check the folder options box in windows explorer for "Hide
protected operating system files" to see it)
If the hidden %appdata% folder exists, delete it.
Proceed to uninstall the App-V client
After a clean uninstall and removal of remnants of the client, reinstall the client again and apply the latest hotfix available (Hotfix 2 for SP2 at a minimum).

How to Non-ACC Client connect Sun App Server 8 with SSL

I have create a Rich Client(Non-ACC) that connect to Sun App Server 8 with IIOP(8001) and is working fine. However, when I try to connect to same server with using SSL (8002) and throw exception during lookup a Bean as below.
Please help!!
Server Configuration
================
IIOP Port(s): 8001, 8002, 8003
All listener ports are enabled
Client Coding
===========
env.put(javax.naming.Context.PROVIDER_URL, "iiop://"+url);
env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,"com.sun.appserv.naming.S1ASCtxFactory");
System.setProperty("javax.net.ssl.keyStoreType", "jks");
System.setProperty("javax.net.ssl.keyStore", "D:\\Sun\\AppServer\\domains\\adsr\\config\\keystore.jks");
System.setProperty("javax.net.ssl.keyStorePassword", "password");
System.setProperty("javax.net.ssl.trustStore", "D:\\Sun\\AppServer\\domains\\adsr\\config\\cacerts.jks");
System.setProperty("javax.net.ssl.trustStorePassword", "password");
System.setProperty("com.sun.CORBA.connection.ORBSocketFactory", "com.sun.enterprise.iiop.IIOPSSLSocketFactory");
ic = new InitialContext(env);
Object objref = ic.lookup("ejb20/statelessSession/EntControllerHome");
Exception
========
[java] Mar 18, 2005 4:43:59 PM com.sun.corba.ee.spi.logging.LogWrapperBasedoLog
[java] INFO: "IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/4645"
[java] Mar 18, 2005 4:44:00 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl readFully
[java] WARNING: "IOP00410215: (COMM_FAILURE) Read of full message failed :
bytes requested = 12 bytes read = 7 max wait time = 300 total time spent waiting = 364"
[java] org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 215 completed: No
[java] at com.sun.corba.ee.impl.logging.ORBUtilSystemException.transportReadTimeoutExceeded(ORBUtilSystemException.java:2629)
[java] at com.sun.corba.ee.impl.logging.ORBUtilSystemException.transportReadTimeoutExceeded(ORBUtilSystemException.java:2655)
[java] at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.readFully(SocketOrChannelConnectionImpl.java:676)
[java] at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.read(SocketOrChannelConnectionImpl.java:545)
[java] at com.sun.corba.ee.impl.protocol.giopmsgheaders.MessageBase.readGIOPHeader(MessageBase.java:119)
[java] at com.sun.corba.ee.impl.transport.CorbaContactInfoBase.createMessageMediator(CorbaContactInfoBase.java:153)
[java] at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.readBits(SocketOrChannelConnectionImpl.java:325)
[java] at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.handleEvent(SocketOrChannelConnectionImpl.java:1175)
[java] at com.sun.corba.ee.impl.transport.SelectorImpl.run(SelectorImpl.java:275)
[java] javax.naming.CommunicationException: Can't find SerialContextProvider [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 208 c
ompleted: Maybe]
[java] at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:133)
[java] at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:290)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:347)
[java] at com.shkco.jaf.test.JAFLogonTest.connect(JAFLogonTest.java:110)
[java] at com.shkco.jaf.test.JAFLogonTest.setUp(JAFLogonTest.java:134)
[java] at junit.framework.TestCase.runBare(TestCase.java:125)
[java] at junit.framework.TestResult$1.protect(TestResult.java:106)
[java] at junit.framework.TestResult.runProtected(TestResult.java:124)

I don't think tomcat supports the ejb-ref portion of web.xml. If you're using ejbs your best bet is to use a web container within a J2EE implementation.
--ken

Web-service client for legacy web service

I currently access a legacy server (Lotus Domino 7) via CORBA. I thought a web service (my second) would be faster, but a whole day's research has uncovered only obsolete or trivial examples.
The WSDL generated by the server is rpc/encoded so wsimport cannot generate the necessary "artifacts" for a web service client.
The web service is simple: it accepts two java.lang.Strings, and returns a java.lang.String of XML. The "dynamic proxy" approach from 1.4.2 seems to have disappeared; I was hoping that approach would let me just hand-code a single "artifact" - an SEI based on the method information in the WSDL.
1) What classes in JAX-WS will let my web service client communicate with rpc?
2) With such a simple signature, do I need any other "artifacts" beyond an SEI?
Thanks for any help!

In case anyone's search leads them here, I've posted the solution at:
*[http://www.pby.com/general.nsf/webarticles/dominowebservice01]*
It is an exhaustive article (not "Hello World"!) that goes through several versions of the web service and client - hopefully explaining all* pieces of the puzzle:
~ web service code,
~ WSDLs
~ schema
~ thoroughly-documented clients that do and do not use JAXB
~ ... that use generated artifacts
~ ... that customize existing POJOs
~ the SOAP messages generated in each direction
~ the necessary JAXB annotations
~ explanations of how the code works
~ explanations of how namespaces affect the code
~ on and on and on...
My constant goal was to write an uncomplicated solution that uses as few artifacts (two) and annotations as possible. The end result is a small, fast JAX-WS 2.0 client that uses JAXB to invoke and consume a secured Domino 7 (1.4.2 JVM + AXIS) web service, using RPC/literal SOAP messages.

Java client for WCF STS service without netbeans etc.?

I want to communicate with a WCF service that uses an STS. I want to know what I am doing, so I don't want to use netbeans. If I have to use netbeans to figure it out for myself, can you help me interpret this part of the documentation for metro:
https://metro.java.net/guide/ch12.html#gghnt
How do I retrieve the certificate from the .NET service to use if I follow the instructions?
Or, other suggestions would be helpful.
Thanks

I'm a bit confused why you're using an Applet to do this as it will require you to serve the Applet from the same server as where the .Net web service lives.
If I was doing it I'd take advantage of the web service capabilities built into Java 6 (the only supported version from Sun). The wsimport tool would be able to reverse engineer the WSDL from the .net web service and generate client side classes for you.

Web Start client for two Web Services

Hello.
I wrote a client application that uses two different web services.
Both web services are created using Basic Authentication. They have different user_names and passwords, but must be deployed on the same application server. I must invoked methods of these web services one after another.The problem occures when I invokes mehods of second web service. No matter which of service would be first or second. The problem occurs on second calling. I got this exception:
EXCEPTION: java.rmi.RemoteException: HTTP Status-Code 403: Access to the requested resource has been denied; nested exception is:
     HTTP Status-Code 403: Access to the requested resource has been denied
     at com.softlets.insurelet.security.InsureletSecurityServiceSEI_Stub.login(InsureletSecurityServiceSEI_Stub.java:89)
     at com.softlets.insurelet.test.TestRefundPolicy.main(TestRefundPolicy.java:61)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
IMPORTANT: Everything worked fine until I started to install this application using Java Web Start.
MY ASSUMPTION: It's likely to me that web start executes my application in some environment where it caches the first web service's username and password and applies it to the second web service. Because, if I run both web services on my local machine and set ENDPOINT_ADDRESS_PROPERTY to different values (first - localhost:8080, second - 192.168.0.21:8080) everything works fine.
CODE FRAGMENT:
public static void main(String[] args) {
try {
String user = "test"; String pass ="test";
String host = "http://192.168.0.21:8080/insurelet-p/insurelet_p";
Stub stub = (Stub)(new Insurelet_policies_Impl().getInsureletPoliciesServiceSEIPort()); stub1._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, host);
stub._setProperty(javax.xml.rpc.Stub.USERNAME_PROPERTY, user);
stub._setProperty(javax.xml.rpc.Stub.PASSWORD_PROPERTY, pass);
InsureletPoliciesServiceSEI ws = (InsureletPoliciesServiceSEI)stub;
String officeid = "test1"; String operatorid = "test2"; String mct = "1";
// FIRST WEB SERVICE CALLING
boolean result = ws.makeRefund(officeid, operatorid, mct);
String suser = "test"; String spass ="test";
String shost = "http://192.168.0.21:8080/insurelet-s/insurelet_s";
Stub stub1 = (Stub)(new Insurelet_security_Impl()).getInsureletSecurityServiceSEIPort();
stub1._setProperty(javax.xml.rpc.Stub.USERNAME_PROPERTY, suser);
stub1._setProperty(javax.xml.rpc.Stub.PASSWORD_PROPERTY, spass);
stub1._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, shost);
InsureletSecurityServiceSEI ws1 = (InsureletSecurityServiceSEI)stub1;
// SECOND WEB SERVICE CALLING
OperatorTO to = ws1.login("softlets", "admin", "admin"); // EXCEPTION
ENVIRONMENT: Both web services are deployed in a single enterprise application on Sun Java System Application Server 8.1.
Java version: 1.5..0_02

In case anyone's search leads them here, I've posted the solution at:
*[http://www.pby.com/general.nsf/webarticles/dominowebservice01]*
It is an exhaustive article (not "Hello World"!) that goes through several versions of the web service and client - hopefully explaining all* pieces of the puzzle:
~ web service code,
~ WSDLs
~ schema
~ thoroughly-documented clients that do and do not use JAXB
~ ... that use generated artifacts
~ ... that customize existing POJOs
~ the SOAP messages generated in each direction
~ the necessary JAXB annotations
~ explanations of how the code works
~ explanations of how namespaces affect the code
~ on and on and on...
My constant goal was to write an uncomplicated solution that uses as few artifacts (two) and annotations as possible. The end result is a small, fast JAX-WS 2.0 client that uses JAXB to invoke and consume a secured Domino 7 (1.4.2 JVM + AXIS) web service, using RPC/literal SOAP messages.

Help me in writing client for this JAX ws Web service

Hi ,
I am unable to write client for my Webservice deployed under glass fish v3 .please help.
package jws;
import javax.jws.WebService;
import javax.jws.WebMethod;
import javax.jws.WebParam;
@WebService(name="CalculatorPortType")
public interface Calculator {
    @WebMethod
    public int add(int value1, int value2);
} package jws;
import javax.jws.WebService;
@WebService(serviceName = "Calculator",
            portName="CalculatorPort",
            endpointInterface = "jws.Calculator")
public class CalculatorService implements Calculator {
    public int add(int value1, int value2)
         System.out.println("Inside web service class ");
        return value1 + value2;
My client which is incomplete :please help
import java.net.URL;
import jws.CalculatorService;
import jws.Calculator;
import javax.xml.ws.Service;
import sun.print.resources.serviceui;
public class Hi {
@WebServiceRef(wsdlLocation=
"http://localhost:8089/Ram/Calculator?wsdl")
CalculatorService service ;
public static void main(String argsp[]) throws Exception
} This is deployed under glassfish v3.

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.

Java client for microsoft passport

hi,
i wonder if it is possible to build a java client for microsoft passport services on mobile phones. do i need any kind of middleware to communicate between a java phone and a server?
thanks in advance
Dirk

Hi,
Yes, by using a servlet you can connect to passport services lets say hotmail by using the HTTP protocol as described in RFC 2518. Only thing you have to do is to communicate with the servlet afterwards..
Cheers,

Official RDP client for all major platforms and certificate issue only on windows

We have been fully embracing RDS and remote apps(working great internally). On the four major platforms OSX iOS Android and Windows we are using the official Microsoft application to connect to "Remote Resources" through VPN. Every platform besides
windows just popped up a certificate error you could accept. The windows client from the windows store was a miserable experience by going to the webpage and installing the certificate into the Trusted Root Certification Authorities. Something no end user
will be able to achieve.
Why is the windows experience worse then the other 3 platforms. I am by no means certificate expert. Is this where we purchase an offical certificate and not have this issue? Still doesn't explain the lack of user friendliness on windows compared to the
other OS'es

Hi,
I understand what you mean. One thing to keep in mind is that making it as easy as it is on the non-windows clients for end users to simply choose to trust the certificate and proceed is a security risk. If the end users would contact their admin
via phone and verify that the thumbprint shown matches the cert thumbprint on the server then it would be okay, but people generally will not do that.
-TP

Problem with DII client for Doc/Literal with non built-in type in WL8.1 Sp2

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Need help writing client for WSE 1.0 Web Service

Hello all,
I am attempting to write Java clients against a .Net service that uses WSE 1.0. I can't seem to get any of toolkits I have tried to work with this service. Unfounately, I do not own the service, so I cannot upgrade it to WSE 2.0. The problem seems to be that the WSE 1.0 expects namespaces from the July 2002 version of WS-Security, while all the libraries I have tried (JWSDP, Oracle Web Service Wizard, etc) use the oasis namepsace from January 2004.
Can he one suggest an alternative? Is there a way to set the namespace sent in XWS-Security? I think this might solve the problem...
Thanks,
KS

Hi,
firstly JWSDP 1.5 is pretty old, the latest release of JWSDP is JWSDP 2.0 that happened late last year.
The problem is most likely happening due to a bug in JWSDP 1.5. If you dump the Message that is going over the wire you will probably see
SOAPAction : ""
SOAPAction : "<the correct action value>"
And this is the reason for the failure. I believe you are using SOAP 1.1 messages right ?
What you will need to do is upgrade to
JWSDP 2.0 and more important also upgrade your SAAJ jars in the JWSDP installation to SAAJ 1.3
https://saaj.dev.java.net/files/documents/52/32730/saaj1.3.zip
Alternatively, you can use Sun's Project Tango (Sun's Next Generation WebServices Interoperability Technology Offering) which has been tested to interoperate with Microsoft WCF.
http://java.sun.com/developer/technicalArticles/glassfish/ProjectTango/
You can download Project Tango by visiting the following page :
https://wsit.dev.java.net/
Look at the Try It section for instructions on how to use it.
Using the Netbeans Plugin you can develop a java client which can securely communicate with the .Net WebService. All you need to do for that is use Netbeans to create a Java WebService Client by pointing it to the WSDL of the .Net Service.
Let us know if this helped.
Thanks...
Message was edited by:
kumar_at_sun

Risk Management & Process controls for non SAP client

Hi Forum Gurus,
I need clarity on the following: Can Risk managment 3.0 and Process controls be implemented for a non-SAP client?
i.e. Our client does not run SAP, but they are interested in RM and PC, so is this possible to implement?
Any advice would be highly appreciated.
Kind regards,
PREVO.

Hi Prevo,
Process control and Risk management 3.0 are delivered within same installation package files so it is same for both the applications .
Also real time agents for Oracle or peoplesoft are avaialble if you want to leverage the automated control functionality of PC 3.0 in non SAP environment.
Remember the automated control functionality is the optional feature of PC3.0.If you wish only to use the manual controls features of PC 3.0 you dont need RTAs(real time agent).
You can find further information about manual controls at http://service.sap.com
use the quicklink '/rkt' then the following menu path: SAP Business Objects for GRC Solutions -> SAP BO Process Control 3.0 -> Technology Consultant
Regards
Debraj

WWW Location of the Novell Client for XP supporting IP Gateway Services

When connecting Windows XP workstations to the SBS 6.0 server through the
Novell Client 4.9SP1a for Windows XP, there are no services within 4.9
for IP Gateway included. As many of you know, by using BorderManager as
the Firewall/NAT/IP/IPX Gateway to access the Internet, all workstations
accessing the Internet need the IP Gateway service installed with the
client. The Novell Client CD-ROM shipped with the Novell SBS 6.0 media
has clients for Windows NT/2000 (outdated) but none are compatible for
Windows XP (it appears that Novell had not updated their Novell SBS 6.0
media since they started shipping it). In addition, the online
documentation included with the media is outdated (e.g. BorderManager 3.6
docs for BorderManager 3.7 being shipped) and do not mention anything
about configuring Windows XP clients for Novell IP Gateway services.
I have thoroughly looked within Novell's Support site the past few weeks
for:
+ The original Novell Client 4.9 (prior to support packs) to see if that
version of the client has IP Gateway services included (file not found or
listed).
+ Previous Novell Clients for Windows XP to see if those versions support
IP Gateway services. (Support Pack versions only are listed, but no
original versions, and do not contain Novell IP Gateway services).
+ Any instructions or tips for configuring the Novell IP Gateway services
within the Novell Client 4.9 or earlier versions for Windows XP(documents
are non-existent).
All of the above leads the following question:
Can someone please direct me to the location to where the proper
Novell Client for Windows XP supporting Novell IP Gateway services?
Since Windows XP has been around for a few years now, one would think
Novell would have developed a client for it that possesses Novell IP
Gateway services by now to be used with BorderManager. Correct? If so,
where is it? In addition, one would think Novell would include the media
supporting the current software they are shipping, not outdated ones.
(Or at least, ensure their outsourced sales services are doing so.) In
addition, one would also think Novell would at least provide the
necessary tools/files necessary to at least to have the ability to
install their products out of the box - instead of forcing their
consumers to purchase unnecessary additional support services for
something they should have included within their media package or website
at the start.
Nevertheless, I appreciate any input where to find the appropriate Novell
Client for Windows XP supporting Novell IP Gateway services.
Thanks,
EricV

In article <cb60c.5596$[email protected]>, wrote:
> As many of you know, by using BorderManager as
> the Firewall/NAT/IP/IPX Gateway to access the Internet, all workstations
> accessing the Internet need the IP Gateway service installed with the
> client.
>
This is simply not correct. Novell has not been providing IP gateway
functionality within Client32 for a long time, because it is not needed,
and it had serious limitations.
I haven't had a client using IP Gateway for many years now, and I have a
*lot* of BorderManager clients.
The alternative to IP Gateways is a combination of proxies and NAT w/filter
exceptions.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Create web service client for javafx project in netbeans 6.8

I here have a javafx project and need to create a web service client for it (in netbeans 6.8).
However when I right click this project -> new -> web service client -> input wsdl location\package -> finish, it seems that the client code is never generated. This is quite different from what happens when creating web service client for a java project.
Anyone knows how is this happening?

Thanks for your reply.
I did write my own ws client code but I need to create a web proxy based on an appointed wsdl path. That requires me to create a web service client from netbeans 6.8, like what I described in my first post. Unfortunately, it's not behaving like what I imagined it should do for a java project, even the javafx file itself doesn't have any error. The error occurs in package definition line.
package fx;For the definition above, it cannot access java.lang.builtins.
The question now is about the possibility to include javafx file in an non-javafx, say, java project. Any comments?
---Regards.

Non-ACC client for WSIT enabled services

Similar Messages

Maybe you are looking for