BEA webservice client has problem in talking to secured microsoft webservic

Hi,
I am developing a BEA client (standalone java client using BEA 10 MP1 install) to invoke a microsoft secured webservice which requires a X509 token in the request. I am able to invoke the service successfully but can not validate the response which is signed by server.
Here is the client code, I am using -
import javax.xml.rpc.ServiceException;
import javax.xml.rpc.Stub;
import weblogic.security.SSL.TrustManager;
import weblogic.xml.crypto.wss.provider.CredentialProvider;
import weblogic.xml.crypto.wss.WSSecurityContext;
import weblogic.wsee.security.bst.ClientBSTCredentialProvider;
import weblogic.wsee.security.unt.ClientUNTCredentialProvider;
import weblogic.wsee.security.util.CertUtils;
import java.util.List;
import java.util.ArrayList;
import java.security.cert.X509Certificate;
import com.accenture.tarpon.*;
public class Test {
public static void main(String[] args) throws Exception {
String username = args[2];
String password = args[3];
String wsdl = args[4];
String clientKeyStore=args[0];
String clientKeyStorePass=args[1];
String clientKeyAlias = args[5];
String clientKeyPass = args[6];
String serverCertFile = args[7];
X509Certificate serverCert = (X509Certificate) CertUtils.getCertificate(serverCertFile);
GetAddress service = new GetAddress_Impl(wsdl);
Microsoft_X0020_GetAddress port = service.getBasicHttpBinding_Microsoft_X0020_GetAddress();
List credProviders = new ArrayList();
//client side BinarySecurityToken credential provider -- x509
credProviders.add(new ClientBSTCredentialProvider(clientKeyStore, clientKeyStorePass,
clientKeyAlias, clientKeyPass, "JKS", serverCert));
credProviders.add(new ClientUNTCredentialProvider(username.getBytes(), password.getBytes()));
Stub stub = (Stub)port;
stub._setProperty(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credProviders);
stub._setProperty(WSSecurityContext.TRUST_MANAGER,
new TrustManager(){
public boolean certificateCallback(X509Certificate[] chain, int validateErr){
//need to validate if the server cert can be trusted
for (int i = 0; i < chain.length; i++) {
System.out.println("Server cert chain: " + chain);
return true;
System.out.println("\n\n *** before forming getAddressRequest \n\n");
GetAddressRequest getAddressRequest = new GetAddressRequest();
getAddressRequest.setTaxPayerID("MicrosoftGetAddressX509Sign_123");
GetAddressResponse getAddressResponse = port.getTaxPayerAddress(getAddressRequest);
System.out.println("\n\n *** after invocation getAddressRequest \n\n");
printGetAddressResponse(getAddressResponse);
private static void printGetAddressResponse(GetAddressResponse getAddressResponse){
System.out.println("\n\n ***** Response from MicrosoftGetAddressService : ***** ");
System.out.println("\nAddress Line 1 - "+getAddressResponse.getAddressLine1());
System.out.println("\nAddress Line 2 - "+getAddressResponse.getAddressLine2());
System.out.println("\nCity - "+getAddressResponse.getCity());
System.out.println("\nCompany - "+getAddressResponse.getCompany());
System.out.println("\nState - "+getAddressResponse.getState());
System.out.println("\nTaxPayerID - "+getAddressResponse.getTaxPayerID());
System.out.println("\nZip - "+getAddressResponse.getZip());
System.out.println("\nFirst Name - "+getAddressResponse.getTaxpayerFirstName());
System.out.println("\nMiddle Name - "+getAddressResponse.getTaxpayerMiddleInitial());
System.out.println("\nLast Name - "+getAddressResponse.getTaxpayerLastName());
When I run this, I get this message -
[java] Exception in thread "main" java.rmi.RemoteException: SOAPFaultException - Faul
tCode [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}
InvalidSecurity] FaultString [weblogic.xml.dom.marshal.MarshalException: weblogic.xml.cryp
to.wss.WSSecurityException: Failed to validate signature.] FaultActor [null]No Detail; nes
ted exception is:
[java] javax.xml.rpc.soap.SOAPFaultException: weblogic.xml.dom.marshal.MarshalExc
eption: weblogic.xml.crypto.wss.WSSecurityException: Failed to validate signature.
[java] at com.accenture.tarpon.Microsoft_X0020_GetAddress_Stub.getTaxPayerAddress
(Unknown Source)
[java] at Test.main(Unknown Source)
[java] Caused by: javax.xml.rpc.soap.SOAPFaultException: weblogic.xml.dom.marshal.Mar
shalException: weblogic.xml.crypto.wss.WSSecurityException: Failed to validate signature.
[java] at weblogic.wsee.codec.soap11.SoapCodec.decodeFault(SoapCodec.java:311)
[java] at weblogic.wsee.ws.dispatch.client.CodecHandler.decodeFault(CodecHandler.
java:114)
[java] at weblogic.wsee.ws.dispatch.client.CodecHandler.decode(CodecHandler.java:
99)
[java] at weblogic.wsee.ws.dispatch.client.CodecHandler.handleFault(CodecHandler.
java:87)
[java] at weblogic.wsee.handler.HandlerIterator.handleFault(HandlerIterator.java:
304)
[java] at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.ja
va:264)
[java] at weblogic.wsee.ws.dispatch.client.ClientDispatcher.handleResponse(Client
Dispatcher.java:193)
[java] at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispat
cher.java:148)
[java] at weblogic.wsee.ws.WsStub.invoke(WsStub.java:89)
[java] at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:332)
[java] ... 2 more
[java] Caused by: weblogic.xml.crypto.wss.WSSecurityException: weblogic.xml.dom.marsh
al.MarshalException: weblogic.xml.crypto.wss.WSSecurityException: Failed to validate signa
ture.
[java] at weblogic.wsee.security.wssp.handlers.WssClientHandler.processInbound(Ws
sClientHandler.java:144)
[java] at weblogic.wsee.security.wssp.handlers.WssClientHandler.processResponse(W
ssClientHandler.java:130)
[java] at weblogic.wsee.security.wssp.handlers.WssHandler.handleResponse(WssHandl
er.java:128)
[java] at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.ja
va:282)
[java] at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.ja
va:266)
[java] ... 6 more
[java] Caused by: weblogic.xml.dom.marshal.MarshalException: weblogic.xml.crypto.wss.
WSSecurityException: Failed to validate signature.
[java] at weblogic.xml.crypto.wss.SecurityImpl.unmarshalInternal(SecurityImpl.jav
a:411)
[java] at weblogic.xml.crypto.wss.SecurityImpl.unmarshal(SecurityImpl.java:375)
[java] at weblogic.xml.crypto.wss11.internal.WSS11Factory.unmarshalAndProcessSecu
rity(WSS11Factory.java:33)
[java] at weblogic.wsee.security.wssp.handlers.WssClientHandler.processInbound(Ws
sClientHandler.java:141)
[java] ... 10 more
[java] Caused by: weblogic.xml.crypto.wss.WSSecurityException: Failed to validate sig
nature.
[java] at weblogic.xml.crypto.wss.SecurityImpl.unmarshalAndProcessSignature(Secur
ityImpl.java:576)
[java] at weblogic.xml.crypto.wss.SecurityImpl.unmarshalChildren(SecurityImpl.jav
a:435)
[java] at weblogic.xml.crypto.wss.SecurityImpl.unmarshalInternal(SecurityImpl.jav
a:399)
[java] ... 13 more
[java] Caused by: weblogic.xml.crypto.dsig.api.XMLSignatureException
[java] at weblogic.xml.crypto.dsig.SignedInfoImpl.validateSignature(SignedInfoImp
l.java:112)
[java] at weblogic.xml.crypto.dsig.XMLSignatureImpl.validate(XMLSignatureImpl.jav
a:233)
[java] at weblogic.xml.crypto.wss.SecurityImpl.unmarshalAndProcessSignature(Secur
ityImpl.java:568)
[java] ... 15 more
[java] Caused by: weblogic.xml.crypto.api.KeySelectorException: weblogic.xml.crypto.w
ss.WSSecurityException: Failed to resolve security token for issuer serial weblogic.xml.cr
ypto.dsig.keyinfo.X509IssuerSerialImpl@df9095
[java] at weblogic.xml.crypto.common.keyinfo.KeyResolver.setupKeyProviderFromCont
ext(KeyResolver.java:312)
[java] at weblogic.xml.crypto.common.keyinfo.KeyResolver.getKeyFromSTR(KeyResolve
r.java:269)
[java] at weblogic.xml.crypto.common.keyinfo.KeyResolver.select(KeyResolver.java:
124)
[java] at weblogic.xml.crypto.dsig.SignedInfoImpl.getVerifyKey(SignedInfoImpl.jav
a:223)
[java] at weblogic.xml.crypto.dsig.SignedInfoImpl.validateSignature(SignedInfoImp
l.java:110)
[java] ... 17 more
[java] Caused by: weblogic.xml.crypto.wss.WSSecurityException: Failed to resolve secu
rity token for issuer serial weblogic.xml.crypto.dsig.keyinfo.X509IssuerSerialImpl@df9095
[java] at weblogic.xml.crypto.wss.BinarySecurityTokenHandler.getTokenByIssuerSeri
al(BinarySecurityTokenHandler.java:147)
[java] at weblogic.xml.crypto.wss.BinarySecurityTokenHandler.getSecurityToken(Bin
arySecurityTokenHandler.java:81)
[java] at weblogic.xml.crypto.common.keyinfo.KeyResolver.setupKeyProviderFromCont
ext(KeyResolver.java:304)
[java] ... 21 more
At the server side, Microsoft has imported client cert and also on the client side, I have imported server cert in jdk's cacerts file.
Please help.
Thanks in advance,
Manoj

Hello experts,
Do you know is there a way to avoid "SSL handshake failure." error without importing a public key to the default keystore?
When I access WebLogic WebServices over SSL from Service Control which is generated by WL WorkSpaces 10.2,
it used default key and there is no additional key manipulation required.
Is there any way to configure a flag to the service control or WL server to automatically trust the end point host.
As far as I know at this point is that I need to have public key in PEM format and use keytool to import that into client skystore file. Is this the only way it can solve this handshake issue?
Any pointers are appreciated. _J

Similar Messages

Webservice Client deserialization problem with Vectors!

Hello!
I'm generating a Java Proxy Client with Eclipse WTP.
The Client works fine with normal datatypes and own Beans. But whe the return type is a Collection with own beans an exception is thrown:
exception: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
So whats wrong?
In teh Webservice Explorer everything seems to be fine, my vector is serialized in item-tags:
- <getAktionenResponse xmlns="http://commonservice">
- <getAktionenReturn>
- <item xmlns="">
<aktn_nr>a12345</aktn_nr>
<claim>222</claim>
<geschaeftsjahr>2005</geschaeftsjahr>
<son>333</son>
<special_operation_code>soc12345</special_operation_code>
<status>ready</status>
<vin>t123</vin>
</item>
- <item xmlns="">
<aktn_nr>a6789</aktn_nr>
<claim>567</claim>
<geschaeftsjahr>2006</geschaeftsjahr>
<son>555</son>
<special_operation_code>soc6789</special_operation_code>
<status>false</status>
<vin>t123</vin>
</item>
</getAktionenReturn>
</getAktionenResponse>
how can i solve this problem?
the background is that I return a vector with Java Objects. I thought apache axis deserielizes automatically the vector and the bean inside??
I'm pretty new to webservices...
Pleas help!
Thanks!

As per the below link, I assumed its better to avoid collections and go with plain array of objects.
Please let us know if I am wrong.
http://www-128.ibm.com/developerworks/webservices/library/ws-tip-coding.html
Regards,
Venkat S

Firefox 5 or 6 served over NFS to UNIX clients has problem finding shared object libraries.

With versions of firefox 3 and below, I was able to serve the application from a NFS share to all client workstations. Now I can not find a version above 3 that will run from just the NFS share. They all need shared libraries local (instead of just using the shared libraries in the NFS share)

It is just on Solaris we have the issue and even with local installed libraries it still crashes alot. On Redhat it works fine with the libraries in the NFS share.

J2ME webservice client problem

hi,
i am trying to use the webservice client using J2ME on Nokia 6630 device, the problem comes as follow:
i am using webservice client at netBeans IDE 5.0. started the project and create the webservice client, compiled the project, worked on the emulator properly.
transfered it on the device, but unfortunatily does not do anything, when i select the application and nothing happen!
please advice, because i have several trials with no use, and i searched whole the internet, no one talked about this problem.
thanks in advance.

please be more specific...
is the installation is OK?
if it's OK, can you see the first screen of your application and when your application is freezing? do you try to connect it to the web?
...

Problem running ClientGen generated webservice client

I'm using Workshop for Weblogic 10.3 and I'm trying to generate a webservice client. When I generate it with ClientGen and I try to use it I get the following error:
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/j2ee/descriptor/ServiceRefHandlerBean
at weblogic.wsee.jaxrpc.HandlerRegistryImpl.<init>(HandlerRegistryImpl.java:32)
at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:88)
at com_service_osadia_interface.wovenware.SERVICE_OSADIA_Impl.<init>(Unknown Source)
at com_service_osadia_interface.wovenware.SERVICE_OSADIA_Impl.<init>(Unknown Source)
at testClient.main(testClient.java:18)
If I add the com.bea.core.descriptor.j2ee_1.1.0.0.jar to the libraries then I get the following error:
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: com/sun/xml/ws/util/JAXWSUtils
at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:44)
at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:403)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:389)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)
at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:476)
at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)
at com_service_osadia_interface.wovenware.SERVICE_OSADIA_Impl.<init>(Unknown Source)
at com_service_osadia_interface.wovenware.SERVICE_OSADIA_Impl.<init>(Unknown Source)
at testClient.main(testClient.java:18)
How can I fix it?

I didn't see a mistake, but my sample works fine. Are you trying to execute the client from Workshop / Eclipse? If that is the case, then I believe it's a matter of just using the appropriate client libraries, which I believe is your issue even though the error is misleading. You should definitely try using a Java Project for a stand-alone web service invocation. According to this link: http://edocs.bea.com/wls/docs103/webserv_rpc/client.html#wp229351 you simply need 1 jar file named wseeclient.jar on your path, which is archived inside <WL_INSTALL>\wlserver_10.3\server\lib\wseeclient.zip
Once I set up a new Java Project with wseeclient.jar on my path and my clientgen generated classes, I could invoke the sample.
Also, here is what the successful invocation from the command line using (ant build, ant deploy, ant run):
C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\src\examples\webservices\jws_basic\simple>ant build
Buildfile: build.xml
clean:
[delete] Deleting directory C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar
[delete] Deleting directory C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\clientclasses\webservicesJwsSimple_client
server:
[mkdir] Created dir: C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar
[jwsc] JWS: processing module /SimpleImpl
[jwsc] Parsing source files
[jwsc] Parsing source files
[jwsc] 1 JWS files being processed for module /SimpleImpl
[jwsc] JWS: C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\src\examples\webservices\jws_basic\simple\SimpleImpl.java Validated.
[jwsc] Since compiler setting isn't classic or modern,ignoring fork setting.
[jwsc] Compiling 2 source files to C:\temp\_x58sqp
[jwsc] Since compiler setting isn't classic or modern,ignoring fork setting.
[jwsc] Copying 1 file to C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar\SimpleImpl\WEB-INF
[jwsc] Copying 22 files to C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar\SimpleImpl\WEB-INF
[jwsc] Copying 2 files to C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar\SimpleImpl\WEB-INF\classes
[jwsc] Copying 1 file to C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar\SimpleImpl
[jwsc] [EarFile] Application File : C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar\META-INF\application.xml
[AntUtil.deleteDir] Deleting directory C:\temp\_x58sqp
client:
[mkdir] Created dir: C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\clientclasses\webservicesJwsSimple_client
[clientgen] Ignoring JAX-WS options - building a JAX-RPC client
[clientgen]
[clientgen] *********** jax-rpc clientgen attribute settings ***************
[clientgen]
[clientgen] wsdlURI: file:/C:/Oracle/wls10.3/wlserver_10.3/samples/server/examples/build/webservicesJwsSimpleEar/SimpleImpl/WEB-INF/SimpleImplService.wsdl
[clientgen] serviceName : null
[clientgen] packageName : examples.webservices.jws_basic.simple.client
[clientgen] destDir : C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\clientclasses\webservicesJwsSimple_client
[clientgen] handlerChainFile : null
[clientgen] generatePolicyMethods : false
[clientgen] autoDetectWrapped : true
[clientgen] jaxRPCWrappedArrayStyle : true
[clientgen] generateAsyncMethods : true
[clientgen]
[clientgen] *********** jax-rpc clientgen attribute settings end ***************
[clientgen] Package name is examples.webservices.jws_basic.simple.client
[clientgen] DestDir is C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\clientclasses\webservicesJwsSimple_client
[clientgen] class name is Simple_Stub
[clientgen] service class name is SimpleImplService
[clientgen] Porttype name is Simple
[clientgen] service impl name is SimpleImplService_Impl
[javac] Compiling 4 source files
[javac] Note: C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\clientclasses\webservicesJwsSimple_client\examples\webservices\jws_basic\simple\client\Simple_Stub.java uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] Compiling 1 source file to C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\clientclasses\webservicesJwsSimple_client
[jar] Updating jar: C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\examplesWebApp\WEB-INF\lib\jws_basic_simple.jar
[copy] Copying 1 file to C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\examplesWebApp
build:
BUILD SUCCESSFUL
Total time: 22 seconds
C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\src\examples\webservices\jws_basic\simple>ant deploy
Buildfile: build.xml
deploy:
[wldeploy] weblogic.Deployer -verbose -noexit -source C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar -targets examplesServer -adminurl t3://localhost:7001 -user weblogic -password ******** -deploy
[wldeploy] weblogic.Deployer invoked with options: -verbose -noexit -source C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJwsSimpleEar -targets examplesServer -adminurl t3://localhost:7001 -user weblogic -deploy
[wldeploy] <Dec 23, 2008 2:48:19 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, webservicesJwsSimpleEar [archive: C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\build\webservicesJws
SimpleEar], to examplesServer .>
[wldeploy] Task 0 initiated: [Deployer:149026]deploy application webservicesJwsSimpleEar on examplesServer.
[wldeploy] Task 0 completed: [Deployer:149026]deploy application webservicesJwsSimpleEar on examplesServer.
[wldeploy] Target state: deploy completed on Server examplesServer
[wldeploy]
[wldeploy] Target Assignments:
[wldeploy] + webservicesJwsSimpleEar examplesServer
BUILD SUCCESSFUL
Total time: 9 seconds
C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\src\examples\webservices\jws_basic\simple>ant run
Buildfile: build.xml
run:
[java] Got result: Here is the message: 'Hi there!'
BUILD SUCCESSFUL
Total time: 7 seconds
C:\Oracle\wls10.3\wlserver_10.3\samples\server\examples\src\examples\webservices\jws_basic\simple>

Problem invoking from a BPEL process webservice client

I have a BPEL Synchronous process that invokes a webservice deployed on Tomcat. The process executes without any exception when I run it from the BPEL Console. Since I want to execute the BPEL process as a command line operation, I created a BPEL Process Webservice client from scratch using Axis as described in Tutorial7 - InvokingBPELProcesses.pdf. However when I try to execute the client, I get the following error:
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.generalException
faultSubcode:
faultString: Dispatcher send error.
An error occurred while sending a batch message to the dispatch queue. The exception is: Failed to create "java:comp/env/ejb/local/DispatcherLocalBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/local/DispatcherLocalBean not found in startup_war
     at com.oracle.naming.J2EEContext.getSubContext(J2EEContext.java:93)
     at com.oracle.naming.J2EEContext.lookup(J2EEContext.java:76)
     at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:177)
     at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:119)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.collaxa.cube.engine.util.CubeEngineBeanRegistry.lookupDispatcherLocalBean(CubeEngineBeanRegistry.java:165)
     at com.collaxa.cube.engine.util.CubeEngineBeanCache.getDispatcherLocalBean(CubeEngineBeanCache.java:91)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendLocal(DispatchHelper.java:229)
     at com.collaxa.cube.engine.dispatch.Dispatcher.receive(Dispatcher.java:430)
     at com.collaxa.cube.engine.dispatch.Dispatcher.receive(Dispatcher.java:357)
     at com.collaxa.cube.engine.dispatch.Dispatcher.update(Dispatcher.java:253)
     at com.collaxa.cube.engine.core.event.DomainObserverRegistry.notify(DomainObserverRegistry.java:124)
     at com.collaxa.cube.engine.core.event.DomainObserverRegistry.notify(DomainObserverRegistry.java:66)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.notify(CubeProcessHolder.java:727)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.addProcess(CubeProcessHolder.java:697)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:632)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:605)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:592)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:494)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:429)
     at com.collaxa.cube.engine.CubeEngine.lookupProcess(CubeEngine.java:840)
     at com.collaxa.cube.ws.wsdl.WSDLManager.getProcess(WSDLManager.java:437)
     at com.collaxa.cube.ws.wsdl.WSDLManager.getPartnerWSDL(WSDLManager.java:300)
     at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.processBPELMessage(CXSOAPProvider.java:175)
     at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.invoke(CXSOAPProvider.java:111)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
     at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:437)
     at org.apache.axis.server.AxisServer.invoke(AxisServer.java:316)
     at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:701)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
     at com.collaxa.cube.fe.CollaxaServlet.service(CollaxaServlet.java:117)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
".
Can someone please tell me what is it I am doing wrong?

I was using
Oracle BPEL Server version 2.0
Build: 2004.06.17.14.40
Build time: Thu Jun 17 14:40:58 PDT 2004
However, I downloaded the latest version of the Process Manager and did not face the same problem.

A client has sent me an indesign file I cannot open. She says she has updated to Indesign CC 2014. I am a CC member and fully updated my own software but cannot open the file she has sent me, not even if she saves as an IDML, how do I resolve the problem?

A client has sent me an indesign file I cannot open. She says she has updated to Indesign CC 2014. I am a CC member and fully updated my own software but cannot open the file she has sent me, not even if she saves as an IDML, how do I resolve the problem?

There are a few things to try.
First, if this file came to you vial email attachment, it could have been corrupted. Ask her to zip the file and send it again. That sometimes helps.
I suppose there's a chance that the file is already zipped, so see if that's the case and unzip it if so.
If the file name doesn't end with .indd, add it and see if that helps.
If you are double-clicking, try File>Open from within InDesign.
Last (and I know this sounds like a joke, but I've seen it many times), sometimes people attach a Mac Alias or Windows Shortcut instead of the actual file. What is the file size? If it's really small, that might be the reason.
Also, no offense intended if some of this sounds like stuff you have already tried. I don't know what you know, so I'm just spit-balling.

Problem deploying webservice client app

I have a JAX-RPC webservice client application which works flawlessly from within JDeveloper 10.1.3 EA1. However, after deploying the application and running it, I get the following error which I have been unable to trace to a missing library:
Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: javax/xml /rpc/ServiceFactory
at com.brunata.ptd.proxy.TempmonSoapHttpPortClient.<init>(TempmonSoapHtt pPortClient.java:17)
at com.brunata.ptd.proxy.PTDProxy.<init>(PTDProxy.java:24)
at com.brunata.ptd.proxy.PTDProxy.sharedInstance(PTDProxy.java:35)
at com.brunata.ptd.views.PTDAppView.<init>(PTDAppView.java:71)
at com.brunata.ptd.PTDApp.createGUI(PTDApp.java:93)
I made sure to include all libraries I can see JDeveloper is referencing, yet obviously I must be missing something. I include the following:
\j2ee\home\lib
\webservices\lib
\jlib
\lib\xmlparserv2.jar
\xdk\lib\xml.jar
\j2ee\home
\rdbms\jlib\xdb.jar
\diagnostics\lib\ojdl2.jar
\jakarta-taglibs\commons-logging-1.0.3\commons-logging.jar
\jakarta-taglibs\commons-logging-1.0.3\commons-logging-api.jar
I must admit, I am a bit shocked that/if I will have to deploy all these files into a some 40MB jar, not exactly fitting for the Java Web Start appliation I am working on.
Any help greaty appreciated,
Casper Bang

Hi Eric,
Thanks for the single-jar solution tip. Unfortunately I still get the same error (javax.xml.rpc.ServiceFactory) even with the use of that file. If I try to run manually from a commandline and include jaxrpc-api.jar, I get a little further though:
java -classpath J:\jdevstudiobase1013\jdev\mywork\PTD\PTD\classes;J:\jdevj2eebase1013\webservices\lib\jaxrpc-ap
i.jar;J:\jdevstudiobase1013\jdev\mywork\PTD\PTD\deploy\jcommon-1.0.0-rc1.jar com
.brunata.ptd.PTDApp
javax.xml.rpc.ServiceException: Provider oracle.j2ee.ws.client.ServiceFactoryImp
l not found
at javax.xml.rpc.FactoryFinder.newInstance(FactoryFinder.java:44)
at javax.xml.rpc.FactoryFinder.find(FactoryFinder.java:137)
at javax.xml.rpc.ServiceFactory.newInstance(ServiceFactory.java:69)
at com.brunata.ptd.proxy.TempmonSoapHttpPortClient.<init>(TempmonSoapHtt
pPortClient.java:17)
at com.brunata.ptd.proxy.PTDProxy.<init>(PTDProxy.java:24)
Which lib is this? (Any documentation somewhere for where packages are stored?)
Thanks a lot,
Casper

Dynamic Webservices Client

Hey ,
I have an application which requires to talk to 2 different published webservices
from 2 different systems. Now instead od designing static webservice clients for
each of these systems(which would involve having separate proxy jars etc),
I am planning to design a dynamic webservice locator and invoker....
I know that we can have webservice clients which are dynamic to the extent that
we can create proxy objects at runtime once we know the endpoint WSDL..
eg:
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName =new QName targetNamespace,"net.xmethods.services.stockquote.StockQuoteService");
QName portName = new QName(targetNamespace,"net.xmethods.services.stockquote.StockQuotePort");
QName operationName = new QName("urn:xmethods-delayed-quotes","getQuote");
URL wsdlLocation = new URL("http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl");
// create service
Service service = factory.createService(wsdlLocation, serviceName);
// create call Call call = service.createCall(portName, operationName);
My question on this...if I have a dynamic approach like the above what are the
pros and cons..I guess it would surely have more overhead compared to a static
client...?
Secondly ,is it even feasible to design a dynamic client in such a way that the
endpoint WSDL could also be an unknown and my generic client would also locate
the end-point dynamically and then invoke dynamic calls as above...
If anybody can share their insights on a dynamic webservice client , I would really
appreciate it...
Thanx,
Krish
KRISH.VENKATARAMAN
Senior Technology Analyst
Bank of America Corp.
Email:[email protected]

Hi Krish,
In WSDL, the data types passed between applications are described in schema
and
this is key for interop. I dont know of any standard/natural mapping for
values types,
object reference, etc in a binary protocol (like JRMP, IIOP) to schema. For
eg:
say there is serializable object Foo, which is the argument to a remote
method in RMI.
Object Foo can have data + behavior. It may be possible (not always, i
think) to
describe the data in Foo as schema, but how can one describe the behavior?
So, if WSDL is the only contract between the server and client (key
requirement
for interop), then IMHO RMI can not be described by WSDL.
Also, WSDL was designed for future extensions and does not map well to a
programming API. WSIF trys to expose all the gory WSDL details and its apis
are very clumsy.
These were the two main reason to vote it down at JAX-RPC EC.
I am attaching an example that shows, how to introspect WSDL and invoke
a method using JAX-RPC (with little extension to the std api). Also, it
shows
how to handle complex type without data binding. Will this solve your
problem?
I am very interested to get your feedback on this.
BTW, This example will only work with WLS 8.1.
regards,
-manoj
"Krish Venkataraman" <[email protected]> wrote in message
news:[email protected]...
>
>
Mike...thanx for the inputs...
As per ur suggestion...I have taken this offline and mailed u [email protected]
also....lemme know if thatz cool...
there are my observations..lemme know what am i missing..
1) The main difference I see between JAX-RPC and WSIF, is that with WSIFclient
it is easier to port to services talking
via other ports like RMI,IIOP etc...where as JAX-RPC is understandsonly SOAP(atleast
for now).
2) Lets assume for the time-being that I would be interested only to talkto services
talking SOAP.
Then why do I need WSIF ?
3) I can have a JX-RPC client , I can have a similar generic(reflection)code
for built-in/primitive datatypes and for
complex datatypes I anywayz would be doing the same thing(requiringthe java
representation of the datatype unless I use
something like JROM or something which I do not want to) in JAX-RPC orWSIF.
>
4) As far as syncronous or asyncronous invocation is concerned , myunderstanding
is that my client call is going to remain the
same ..the service provider is going to either use message-oriented orRPC
on his side...
Again assuming that I am interested only with services talking SOAP, thiscould
be my generic client invocation design
Background is that my client is going to run from within a WLS70sp1
Actors:
a) webSevice1ClientSessionBean : This will be a stateless session beanwhich might
have knowledge about webSevice1's end-point ,
complex dataTypes if any.
(There would be other session beans like this which would haveknowledge about
other specific webservice)
b) GenericWebServiceInvoker : This will have knowledge about everythingwithin
the webservice-standards/protocols.
eg:
//set weblogic ServiceFactory
System.setProperty( "javax.xml.rpc.ServiceFactory",
"weblogic.webservice.core.rpc.ServiceFactoryImpl" );
//create service factory
ServiceFactory factory = ServiceFactory.newInstance();
//define qnames
String targetNamespace = "http://soapinterop.org/";
QName serviceName = new QName( targetNamespace, "SimpleTest" );
QName portName = new QName( targetNamespace, "SimpleTestSoap" );
QName operationName = new QName( "http://soapinterop.org/",
"echoStruct" );
//create service
Service service = factory.createService( serviceName );
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(
SOAPConstants.URI_NS_SOAP_ENCODING );
mapping.register( SOAPElement.class,
new QName( "http://soapinterop.org/xsd", "SOAPStruct" ),
new SOAPElementCodec(),
new SOAPElementCodec() );
//create call
Call call = service.createCall();
//set port and operation name
call.setPortTypeName( portName );
call.setOperationName( operationName );
call.addParameter( "inputStruct",
new QName( "http://soapinterop.org/xsd", "SOAPStruct" ),
ParameterMode.IN);
All parameter values specific to a particular webservice likeQName,targetNameSpace
etc will be sent to this invoker by
webSevice1ClientSessionBean. The GenericWebServiceInvoker will invokethe
service
(using reflection for primitive/builtin types) and alwayz accept anobject
from the service operation and just return
that "object" back the webSevice1ClientSessionBean.ThewebSevice1ClientSessionBean
will know how to interpret the
complexdataType or builtInDatatype whichever is returned.TheGenericWebServiceInvoker
will not have any application
specific knowledge...it will just have knowledge about how todiscover, invoke
any SOAP webservice...
Somewhere in the beginning of GenericWebServiceInvoker I will use JAXRto
discover services from UDDI if needed.
This way I will have a generic webservice client invocation frameworkwhich
can invoke any service which talks SOAP.
Now lemme know how the above picture looks and what is missing...
I have some questions :
1) Incase of complex dataTypes, I will have itz XML representation inthe
publisher's WSDL and the publisher will give
me the java representation of the complex dataType.But how does myclient
JAX-RPC know how to map the XML
to the java representation unless I specify the mapping somewhere?Does
the TypeMapping/TypeMappingRegistry do this ?
Thanx,
Krish
"Michael Wooten" <[email protected]> wrote:
You know, it's really cool to hear guys thinking things through, before
they "jump
on a bandwagon" :-)
Anyway, I suspect that the performance overhead of doing reflection,
and heavy
server-side code intrusion, is what has made a lot of developers balk
at using
WSIF. I would check out the IBM newsgroups, to see what the general
developer
sentiment is on WSIF.
To achieve any sort of decent performance with JAX-RPC based webservices,
you
need to do a fair amount of optimization/tuning on both the client and
server
side. I recommend setting up your own "lab environment" for doing these,
so you
can see exactly what's making things improve/degrade. If you are really
interested
in this topic, we should talk about it "off-line".
In general, the more "dynamic" things are on the client side, the slower
things
will be, the more you really need to question if you really need them
to be dynamic
:-) Does making it "dynamic" really offer something that you can't get
from a
"static" version? If not, who's really benefiting here. I mean, com'n.
All you
really want to do is invoke an operation, right? By the time you get
all the information
it takes to do a dynamic invocation (i.e. port, target namespace, data
type for
input argument, serializer/deserializer for each non-built-in data type,
etc.),
your client looks like you are trying to boot a PDP-11! LOL! For those
of you
who don't know what a PDP-11 is, it's an early computer (from the'60-'70),
that
you actually had to use switches to create the "binary instructions"
to boot it
up!
From a PM's (product manager's) perpective, I wouldn't even let thedevelopers
modify "working" EJBs to expose them as a web service. Alarm bells should
go off
in your head, if you have to modify existing server-side code to expose
a company
asset as a web service.
Response to OT comment: WebLogic Server 7.0 uses its own implementation
of JAX-RPC
1.0. This implementation, I've been told by one of the BEA engineering
that worked
on it, has been certified to be JAX-RPC compliant by Sun. Don't know
about Apache
Axis, in this regard. I use both Apache Axis and the JWSDP with WLS 6.1,
but I
haven't really spent a lot of time looking for differences between our
(BEA's)
implementation, and theirs.
Regards,
Mike Wooten
"Krish Venkataraman" <[email protected]> wrote:
Hey Mike ...
I hear ya..and I see the significance of WSIF...but that IBM started
it a year
back and itz not yet stabilized is what is holding me back...
U mite have a better hold of what WSIF can do...whatever I could grasp
from yesterday
is this...
a)It reads meta data from the wsdl and using a reflection mechanismcalls
the
service operations...
I see examples with primitive datatypes..but what happens when
complex/custom
datatypes come into play...
Would the client code differ between synchronous invocation toasynchronous
invocation...
And aleast in the samples for the WSIF distribution for connectors like
EJB/JMS
etc, the code does not look generic anymore..there are specific calls
to operations
and parameters...
Also Mike , what is the trade-off on performance between having adynamic
client(lets
say based on WSIF)or having a static client...the extent of reflection
a dynamic
client will have to do and create SAAJ objects at runtime will beenormous..
Also I know that there is a relevant API...but can u give an examleshowing
me
how I could discover services from UDDI ..?
Out of this current topic...does BEA use itz own implementation of SOAP
in itz
webservice implementation...and how does it compare with AXIS ?
Thanx,
Krish
"Michael Wooten" <[email protected]> wrote:
Hi Krish,
Well, I guess that's how things are when "needed functionality exceeds
the current
state of a technology" :-)
I (not necessarily BEA) look at it like way:
1. IBM co-authored the "Big 3" XML grammars for the current web
services
stack.
2. IBM always appears to be "there, somewhere" in the new crop ofproposed
additional
XML grammars for "partially agreed upon extension layers", for theweb
services
stack.
3. IBM donated it's original SOAP implementation to the open-sourcecommunity.
4. IBM came up with WSIF over a year ago.
5. IBM's WSTK uses the Apache Axis stuff.
6. A lot of the JAX-RPC/JAXM API is based on the Apache SOAP and Apache
Axis implementations.
7. It looks like IBM may have donated WSIF to Axis.
8. You appear to need something like WSIF :-)
So, there's probably at least a 60/40 chance that some WSIF-like thing
will make
it into the JWSDP, right? If you want "higher odds", you should talk
to the folks
working on the JWSDP, as they are somewhat "in charge" here :-)
Regards,
Mike Wooten
"Krish Venkataraman" <[email protected]> wrote:
Yes...I am surely lookin at something similar...but that framework
not
being standardized
scares me as I have seen many good ideas not seeing the light of the
day...and
I do not want to design something using a framework which might remain
un-standardized..
what are ur thots..
Thanx,
Krish
"Michael Wooten" <[email protected]> wrote:
Hi Krish,
It sounds like you want WSIF :-)
"WSIF allows stubless or completely dynamic invocation of a Web
service,
>>>>>>
based upon examination of the meta-data about the service at runtime.
It
also allows updated implementations of a binding to be plugged intoWSIF
at
runtime, and it allows the calling service to defer choosing a
binding
until
runtime."
Correct?
This is a relatively new "unofficial" addition to the Web ServicesStack,
so it
is not in WLS 7.0 (or Sun's JWSDP) yet. See the following link formore
details:
http://xml.apache.org/axis/wsif
Regards,
Mike Wooten
"Krish Venkataraman" <[email protected]> wrote:
Hey ,
I have an application which requires to talk to 2 different
published
webservices
from 2 different systems. Now instead od designing static webservice
clients for
each of these systems(which would involve having separate proxyjars
etc),
I am planning to design a dynamic webservice locator and invoker....
I know that we can have webservice clients which are dynamic tothe
extent
that
we can create proxy objects at runtime once we know the endpoint
WSDL..
eg:
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName =new QName
targetNamespace,"net.xmethods.services.stockquote.StockQuoteService");
>>>>>>>
QName portName = newQName(targetNamespace,"net.xmethods.services.stockquote.StockQuotePort");
>>>>>>>
QName operationName = newQName("urn:xmethods-delayed-quotes","getQuote");
>>>>>>>
URL wsdlLocation = newURL("http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl");
>>>>>>>
// create service
Service service = factory.createService(wsdlLocation, serviceName);
// create call Call call = service.createCall(portName,
operationName);
>>>>>>>
>>>>>>>
My question on this...if I have a dynamic approach like the abovewhat
are the
pros and cons..I guess it would surely have more overhead comparedto
a static
client...?
Secondly ,is it even feasible to design a dynamic client in such
a
way
that the
endpoint WSDL could also be an unknown and my generic client wouldalso
locate
the end-point dynamically and then invoke dynamic calls as above...
If anybody can share their insights on a dynamic webservice client
I would really
appreciate it...
Thanx,
Krish
KRISH.VENKATARAMAN
Senior Technology Analyst
Bank of America Corp.
Email:[email protected]
[BrowserClient.java]
[DynamicClient.java]

Webservices client exception

Our application has servlets talking to webservices. To communicate we place webservices client in WEB-INF directory in war files. The problem we are facing is that when we try to access one of our webservices , It throws following exception
java.lang.VerifyError: Cannot inherit from final class
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLo
ader.java:476)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.
java:181)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClas
sLoader.java:62)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.
java:223)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClas
sLoader.java:41)
at weblogic.xml.schema.binding.ClassLoadingUtils.loadNonArrayClass(ClassLoading
Utils.java:68)
at weblogic.xml.schema.binding.ClassLoadingUtils.loadClass(ClassLoadingUtils.ja
va:43)
at weblogic.xml.schema.binding.internal.TypeMappingBase.loadClass(TypeMappingBa
se.java:627)
at weblogic.xml.schema.binding.internal.TypeMappingBase.newInstance(TypeMapping
Base.java:611)
at weblogic.xml.schema.binding.internal.TypeMappingBase.addTypeMapping(TypeMapp
ingBase.java:587)
at weblogic.xml.schema.binding.internal.TypeMappingBase.readXML(TypeMappingBase
.java:771)
at weblogic.xml.schema.binding.internal.TypeMappingBase.readXML(TypeMappingBase
.java:550)
at weblogic.webservice.core.encoding.DefaultRegistry.<init>(DefaultRegistry.jav
a:73)
at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:78)
at com.telverse.soap.admin.user.provisioning.process.Provisioning_Impl.<init>(Provisioning_Impl.java:22)
at com.telverse.manager.ProvisioningManager.findFaceplateButtonsByUID(Provision
ingManager.java:109)
at com.telverse.actions.PhoneAction.displayPage(PhoneAction.java:434)
The code which tries to access is as following:
1. Provisioning_Impl prov = new Provisioning_Impl(url+"/provisioning/provisioning?WSDL");
2. ProvisioningPort provPort = prov.getprovisioningPort();
3. provPort.CALLFUNCTION();
The above exception is thrown at Line no1.
Does anybody know the solution of this error?

I am not sure what is causing this error. Are you able to run this client outside the web app as a standalone client?
http://manojc.com

Webservices Client, Exceptions and Log4J

Hi all.
Let me explain the setup of our project before asking for a solution on my problem!
We are implementing a project with 2 teams. One team handles everything that has to deal with the front-end and uses a wsdl to generate a webservices client side that is trigger for most of the requests.
Another team creates the complete backend including the webservices server side.
Thus, we (as team one) do not interfere nor guide team two in how they implement things.
Now here's the problem.
Our side uses Log4J to log all the exceptions. There side probably doesn't (we don't know). If however an exception is triggered from within a WebService call, it is not send to Log4J but to the standard System.out !
Is there any way to change this? Because the only thing we do is generate a client from the WSDL and nothing else! We do however catch any exception and store a message in our log files, but before the catch happens, our System.out has already added the WSexcpetion :(
Is this clear in any way?
Anyone?
Thanks in advance,
Kind Regards,
Les.

A web service client written on WLS [1], should work with
service hosted by any vendor, including .Net, AXIS, Sun RI,
etc.
The client code you write in WLS which is based on JAX-RPC [1]
should compile as is on other vendor JAX-RPC implementation.
So, if you are looking for client code portability then JAX-RPC
is your best bet.
Regards,
-manoj
[1] http://edocs.bea.com/wls/docs81/webserv/client.html#1069703
[2] http://java.sun.com/xml/jaxrpc/
"hanks" <[email protected]> wrote in message
news:3ea3392d$[email protected]..
>
I have tried webservices with apache and weblogic7.0 but i realised thatboth was
to be done very specific to servers.I may be wrong. I am trying tounderstand
how can i write a sercive for one server and access using another server.
When i write webservice in java tomcat server, I create a service andregister
as urn name. For a client to access this service, code kind of looks ejbcode
where we lookup the service and call its method. Instead of looking upJNDI name
we lookup urn and access method. Mind you this client uses ORG packagesspecific
to tomcat.
Now when we write a websercice with weblogic we have to create a ear whichhas
webserverice and write a client to access that service, which lookscompletely
diffrent from one that we wrote for tomcat. I am wondering how can i usethe same
client to access both the services. It rarely happens that both side wouldbe
using same servers.
I am sure that there is some mistake i m doing cos webservices is supposeto be
even language independent.
Can you guys help me in resolving this, more questions later ;-)

Weblogic 8.1 Webservice Client Proxy Authentication not working

We have a desktop console based Weblogic webservices client application that uses client stubs to establish the connection and communicate with the server where the WSDL was hosted.
We are facing a problem in authenticating the Proxy user with valid credentials.
We are using the following code to set the system properties and Authenticator class to authenticate the proxy user.
//Code Segment #1
Code:
System.setProperty("http.proxyHost", proxyHost);System.setProperty("https.proxyHost", proxyHost);
System.setProperty("weblogic.webservice.transport.http.proxy.host",proxyHost);
System.setProperty("weblogic.webservice.transport.https.proxy.host",proxyHost);
System.setProperty("http.proxyPort", proxyPort);
System.setProperty("https.proxyPort", proxyPort);
System.setProperty("weblogic.webservice.transport.http.proxy.port",proxyPort);
System.setProperty("weblogic.webservice.transport.https.proxy.port",proxyPort);
//System.setProperty("http.proxyType", "basic");
//System.setProperty("https.proxyType", "basic");
//System.setProperty("http.proxy.auth.type" ,"ntlm"); //This is not showing any impact
System.setProperty("http.proxyUser", "bsil\\ashok.kumar");
System.setProperty("https.proxyUser", "bsil\\ashok.kumar");
System.setProperty("http.proxyPassword", " xyzddd");
System.setProperty("https.proxyPassword", "xyzddd");
Authenticator.setDefault(new MyAuthenticator());
//Inner class
public static class MyAuthenticator extends Authenticator {
protected PasswordAuthentication getPasswordAuthentication() {
String username = System.getProperty("http.proxyUser");
     String password = System.getProperty("http.proxyPassword");
     return new PasswordAuthentication(username, password.toCharArray());
We are using following code initialize the stubs (Which internally opens a connection to the given endpoint base URL)
//Code Segment #2
Code:
SessionService_Impl sessionService = new SessionService_Impl(getEndPointURL(SessionServicePort.class));
port = sessionService.getSessionServicePort();
return port;
Using above code it always throws the following exception:
Code:
weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from https://apiclienttest.intralinks.com:443/webservices51/SessionService?WSDL. Please check the URL and make sure that it is a valid XML file [java.io.IOException: Proxy authenticator failed: java.lang.ClassNotFoundException: ]
if i replace the above code (Code Segment #2) to as bellow with Code Segment #3 then its working as expected. But we have been told that the Code Segment #2 is required as shwon above for the Weblogic ClientTimeout seconds feature so we cant replace the Code Segment #2 with Code Segment #3 since we don?t want to miss the ClientTimeout seconds feature for the application.
//Code Segment #3
Code:
SessionService_Impl sessionService = new SessionService_Impl();
          SessionServicePort sessionServicePort = sessionService.getSessionServicePort();
          ((SessionServicePort_Stub) sessionServicePort)._setProperty("javax.xml.rpc.service.endpoint.address", endPointBaseURL+"SessionService");
return sessionServicePort ;
why the Proxy authentication is failing with the Code Segment #2 and why it is passing in case of Code Segment #3
The endpoint base URL we are hitting is hosted on Weblogic server 9.0 (which is hosted at client side in US so it is behind our firewall).
Is some thing more do we need to do in Authenticator class???
Please help me if any one has worked on proxy server authenticator in java.

We have a desktop console based Weblogic webservices client application that uses client stubs to establish the connection and communicate with the server where the WSDL was hosted.
We are facing a problem in authenticating the Proxy user with valid credentials.
We are using the following code to set the system properties and Authenticator class to authenticate the proxy user.
//Code Segment #1
Code:
System.setProperty("http.proxyHost", proxyHost);System.setProperty("https.proxyHost", proxyHost);
System.setProperty("weblogic.webservice.transport.http.proxy.host",proxyHost);
System.setProperty("weblogic.webservice.transport.https.proxy.host",proxyHost);
System.setProperty("http.proxyPort", proxyPort);
System.setProperty("https.proxyPort", proxyPort);
System.setProperty("weblogic.webservice.transport.http.proxy.port",proxyPort);
System.setProperty("weblogic.webservice.transport.https.proxy.port",proxyPort);
//System.setProperty("http.proxyType", "basic");
//System.setProperty("https.proxyType", "basic");
//System.setProperty("http.proxy.auth.type" ,"ntlm"); //This is not showing any impact
System.setProperty("http.proxyUser", "bsil\\ashok.kumar");
System.setProperty("https.proxyUser", "bsil\\ashok.kumar");
System.setProperty("http.proxyPassword", " xyzddd");
System.setProperty("https.proxyPassword", "xyzddd");
Authenticator.setDefault(new MyAuthenticator());
//Inner class
public static class MyAuthenticator extends Authenticator {
protected PasswordAuthentication getPasswordAuthentication() {
String username = System.getProperty("http.proxyUser");
     String password = System.getProperty("http.proxyPassword");
     return new PasswordAuthentication(username, password.toCharArray());
We are using following code initialize the stubs (Which internally opens a connection to the given endpoint base URL)
//Code Segment #2
Code:
SessionService_Impl sessionService = new SessionService_Impl(getEndPointURL(SessionServicePort.class));
port = sessionService.getSessionServicePort();
return port;
Using above code it always throws the following exception:
Code:
weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from https://apiclienttest.intralinks.com:443/webservices51/SessionService?WSDL. Please check the URL and make sure that it is a valid XML file [java.io.IOException: Proxy authenticator failed: java.lang.ClassNotFoundException: ]
if i replace the above code (Code Segment #2) to as bellow with Code Segment #3 then its working as expected. But we have been told that the Code Segment #2 is required as shwon above for the Weblogic ClientTimeout seconds feature so we cant replace the Code Segment #2 with Code Segment #3 since we don?t want to miss the ClientTimeout seconds feature for the application.
//Code Segment #3
Code:
SessionService_Impl sessionService = new SessionService_Impl();
          SessionServicePort sessionServicePort = sessionService.getSessionServicePort();
          ((SessionServicePort_Stub) sessionServicePort)._setProperty("javax.xml.rpc.service.endpoint.address", endPointBaseURL+"SessionService");
return sessionServicePort ;
why the Proxy authentication is failing with the Code Segment #2 and why it is passing in case of Code Segment #3
The endpoint base URL we are hitting is hosted on Weblogic server 9.0 (which is hosted at client side in US so it is behind our firewall).
Is some thing more do we need to do in Authenticator class???
Please help me if any one has worked on proxy server authenticator in java.

Non Java Webservice client Authentication

I see in the Weblogic docs many examples of Java webservice clients. Including
one that passes a user id and password through the getXXXPort(userid, password)
call for authenticating the user at runtime. My question is, can a non Java webservice
client authenticate itself in somewhat the same manor? A non Java client wouldn't
have the client jar file available containing the stubs and all.
If someone has a code snippet they could send me it would be most appreciated.
Thanks,
Craig Lindley

Hi Craig,
An partial example using .NET is attached; in this environment you need
to use their NetworkCredential class.
Hope this helps,
Bruce
craig lindley wrote:
>
I see in the Weblogic docs many examples of Java webservice clients. Including
one that passes a user id and password through the getXXXPort(userid, password)
call for authenticating the user at runtime. My question is, can a non Java webservice
client authenticate itself in somewhat the same manor? A non Java client wouldn't
have the client jar file available containing the stubs and all.
If someone has a code snippet they could send me it would be most appreciated.
Thanks,
Craig Lindleyusing System;
using System.Net;
namespace SecurityBasicClient
class AuthClient
[STAThread]
static void Main(string[] args)
SoapInteropBaseService ws = new SoapInteropBaseService();
ws.Url = "http://webservice.bea.com:7001/base/SoapInteropBaseService";
Console.Write("User:");
string strUser = Console.ReadLine();
Console.Write("Password:");
string strPassword = Console.ReadLine();
ICredentials credentials = new NetworkCredential(strUser,strPassword);
try
ws.Credentials = credentials;
Console.WriteLine(ws.echoString("Hello World"));
catch (Exception err)
Console.WriteLine(err.Message);
finally
Console.ReadLine();

Deployable webservice client - ClassCastException

Hi,
We are trying to implement a WebService Client for the secure Webservice. I have created a deployable proxy client and deployed it on the server, our basis has attached the X509 certificate to the proxy in VA. Test Destination is successful. I have exposed the client as public part in the ws client dc project.I have created a used dc relationship to the webservice client project in my EP Component project. I'm trying to use this client in a AbstractPortal component with following code
SECQANDA seq = (SECQANDA) ctx.lookup("<JNDI location");
I get a ClassCastException on this line
java.lang.ClassCastException: <package>.SECQANDAImpl incompatible with <package>.SECQANDA
Have anyone faced this problem? How do I resolve this error?
Appreciate any help.
Thanks,
Giri.

Hi Anand,
Thanks for your response. I have already checked that object for null - it is not. The problem is I dont have this SECQANDAImpl class that implements the SECQANDA interface in my DC. This implementation class gets generated when I deploy the deployable proxy object. Though I should be able to cast to the interface, it is throwing this error. Any other ideas?
Giri.

NPE with WebService client with JDeveloper 10.1.3

Hi folks,
I am having weird NullPointerException with a WebService client I generated with the WEB Service Proxy wizard in JDeveloper 10.1.3.
The thing is, the client runs fine as long as there are NO NULL FIELDs in the "double" type returned objects. I don't know about other types, but I am sure it fails with doubles.
If there is a NULL value in the returned Bean, then marshaling fails with a NullPointerException.
I guess it is not a Server problem since clients in .NET and AXIS works just fine.
I don't think it has anything to do with it, but, server is in JBoss-4.0.4.GA with JBossWS-1.0.3.
May be a bug in JDEV's WebService client code?
The first line is the deserializer returning a null value. The second is the line with the NPE:
member = myns2__double__double_Double_Serializer.deserialize(ns4_r1_IA_C1_QNAME, reader, context);
instance.setR1_IA_C1(((Double)member).doubleValue());
Any help will be appreciated.
Best regards.

This is not an elegant solution.
I’ve the same problem you have, so the only thing that I thought to solve this problem was to change the sentences one by one replacing with if(member != null) between both sentences.
I use an editor that can change regular expressions.
This works fine, but I think there might be a better solution.
I hope this can help.
Regards.

BEA webservice client has problem in talking to secured microsoft webservic

Similar Messages

Maybe you are looking for