Looking for WLS 7.x Web Services interoperability information

Does anyone know of any published reports on compatibility when non-WLS clients
access a WLS web service? I’m completing some tests with clients created using
the Java Web Services Developers Pack but I’m more interested in how it also does
with other vendor implementations (Microsoft, IBM, Apache). I’m also interested
in whether WLS 6.x clients can access WLS 7.x web services. I haven’t seen BEA
referenced very often on the interoperability sites. Has BEA published any information
on their compatibility? Has anyone else published information on this?
Thanks,
Dave

The server seems to be OK (tried intra and internet) ... yes it's normally up.
Please try again and let me know of any further problems.
Thanks,
Bruce
Dave wrote:
Bruce,
Thanks for the link but it looks like the server is down (connection timed out).
Is the server normally up?
Thanks,
Dave
Bruce Stephens <[email protected]> wrote:
Hi Dave,
I think you will find that the round 3 tests build on most of the work
done in 1/2.
Also, there are results listed on our interop server
http://webservice.bea.com:7001/results/summary.html
Thanks,
Bruce
Dave wrote:
manoj,
I looked at test results on Sun’s site and whitemesa. I only noticedBEA in round
3. Can you point me to the other test results?
Thanks,
Dave
"manoj cheenath" <[email protected]> wrote:
BEA participate in the soapbuilder interop testing and WLS 7.0
pass all of the round I, II and III interop tests defined by soap
builders (with most vendors).
Also, we have internal interop tests for .Net and AXIS.
regards,
-manoj
"Dave" <[email protected]> wrote in message
news:[email protected]..
Does anyone know of any published reports on compatibility when
non-WLS
clients
access a WLS web service? I'm completing some tests with clients
created
using
the Java Web Services Developers Pack but I'm more interested in
how
it
also does
with other vendor implementations (Microsoft, IBM, Apache). I'm
also
interested
in whether WLS 6.x clients can access WLS 7.x web services. I haven'tseen BEA
referenced very often on the interoperability sites. Has BEA publishedany information
on their compatibility? Has anyone else published information on
this?
Thanks,
Dave

Similar Messages

Are the WLS 9.1 Web Service Ant Tasks ready for prime time?

I am trying to create a Proof of Concept (POC) for Enterprise and B2B Services at Wendy's Int'l, Inc.
As part of this POC, I created a WSDL for an in-house service and then used the wsdlc and jwsc Ant Tasks to translate this WSDL to Java classes and ultimately (I hoped) a deployable services.
In this document, I describe the issues I encountered setting up what I consider to be a simple POC.
I'll try to attach my WSDL file and build.xml so you can follow along.
I'll also try to attach my CSS file so you can compare how the generated WSDL appears in the Browser to the way I want it to appear.
If attachments are not allowed on these forums, then I will wait and see if there is interest in those documents before I paste them under this topic.
Some preliminary information about my environment.
Environment:
 Windows XP Pro SP2
 WebLogic 9.1
 Java 1.5.0_04
Service Name:
 AppRelease
Note: If I modify my WSDL (perhaps to add a new Operation or to change the definition of an element) and run wsdlc again, the AppReleaseSOAPPortImpl.java file is overwritten For this reason, I implemented my service logic in a class called AppReleaseServiceImple.java.
Now, for the issues.
1. Bug:
In the WSDL generated by wsdlc, the wsdl:part child of the wsdl:message tag is erroneously prefixed with a colon.
This occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
2. Bug:
In the WSDL generated by wsdlc, the wsdl:input and wsdl:output children of the wsdl:operation child of wsdl:portType tag are erroneously prefixed with a colon. Like 1 above, this occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
The error message generated by Bugs 1 and 2 is not helpful in diagnosing the problem:
[jwsc] Error at line:46 col:7 ':' expected [?! -- [CDATA[ ]
3. Bug:
In the WSDL generated by wsdlc, the documentation elements have all of my html elements stripped out, as well as my xhtml and wsdl namespace references. This completely negates one of the best features of the documentation tag, being able to present the WSDL in a browser as a nicely formatted, human friendly document which is also the underlying WSDL that can be viewed when the person views the source document.
I label this as a bug because it greatly reduces the functionality of the resulting WSDL.
4. Annoyance:
The WSDL generated by wsdlc has all of my comments stripped out, except the comments in the xsd:schema section of the wsdl:types element. I would prefer that all my comments be left in the WSDL, but if comments must be stripped out then I think all of the comments should be stripped out.
5. Annoyance:
The WSDL generated by wsdlc has my CSS specification stripped.
Work around: I donâ€™t know if adding the CSS back will do any good because I have not yet created a deployable service (see the last issue below).
6. Annoyance:
The WSDL generated by wsdlc has different namespace prefixes than the ones I specified for my application's namespace and for the http://schemas.xmlsoap.org/wsdl/soap/ namespace.
Work around: Perform a find/replace on namespace prefixes "s0" and "s1" to return them to my prefered values.
Another thing I can do at this point is simply replace the generated WSDL in the jar file with my original WSDL. This would address issues 1 thru 6 above.
7. Annoyance:
The java source files created by wsdlc are put into a jar file. This makes it annoying when working within a traditional IDE like Eclipse because there is no way to reference the source files within the jar as working source.
Work around: Extract the source files from the jar and identify the resulting directory structure as part of the source structure of the project.
8. Bug:
The jwsc task complains if the same parameter name is used in multiple operations. I received the following Errors from jwsc:
[jwsc] C:\IDE\workspace\Acre-WL9.1\AppReleaseSOAPPort.java 0:0
[jwsc] [ERROR] - Parameter element "{http://acre.services.wendys.com/AppRelease/}garRequest" is not unique across document/literal bare WebService.
Since the operation names are unique, I see no reason to also require uniqueness in the parameter names used by those operations.
Work around: Use unique element names for the input parameters of the services operations.
9. Bug:
Once items 1, 2 and 8 above are taken care of, jwsc fails with the following error:
java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.ApplicationBeanImpl
This seems to be due to the weblogic.jar file not being in the System Classpath.
However, I should note that when I set verbose="on" and debug="on" in the jwsc ant task, there was a message from the task which stated "[jwsc] [search path for class files: [big freakinâ€™ jar list]". In the big freakinâ€™ jar list, I did find weblogic.jar and weblogic.jar has the required ApplicationBeanImpl. This indicates to me that the jwsc task does not fully honor either its classpathref attribute, nor an embedded classpath element.
Work around: Make sure the weblogic.jar is in the System Classpath.
10. Bug:
I fixed bug #9 by running a setDomainEnv script and then ran my ant task. This time I received the following output:
ant build-serviceBuildfile: build.xml
build-service:
[jwsc] 1 JWS files will be processed.
[jwsc] Processing JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java
[jwsc] JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java Validated.
[AntUtil.deleteDir] Deleting directory <some temporary directory>
BUILD FAILED
java.lang.ExceptionInInitializerError
At this point, I am completely stymied about how to proceed.
I wonder what new issues await once this 10th issue is addressed.
Really, is this tool set ready for prime time?

Sorry to hear you are having so many issues with using the WLS 9.1 web service Ant tasks, inside of Eclipse.
I generally create a User Library for the couple weblogic jars needed, and use it (the User Library) in my Eclipse projects that I create JWSes in. 
I also have a separate WebLogic Library in Eclipse (actually 2 libraries since I work with WL 8.1 and now WL 9.1). As you may know, one of the long-standing issues with the Ant integration within Eclipse is the fact that Ant, being an External Tool, does not receive the Project-specific Paths/Libraries. However, since most Java-relevant Ant tasks can take classpath and classpathref attributes, this is usually not an issue. In the case of the BEA-supplied wsdlc Ant task, it is apparent from the verbose/debug console output that wsdlc can see the jars in its classpathref, but it ignores those references when resolving class references and instead only uses the system classpath.

I've only needed the weblogic.jar and xbean.jar, not all the ones you mentioned in an earlier thread of this post. 
I have not tried to winnow down exactly which jars are required. I simply included all the jars that exist and were added to the system classpath by the setDomainEnv.bat file created by WebLogic 9.1.

Afterwards, I create an Ant Builder to build the JWS Web Service EAR, as opposed to fiddlin' with Eclipse. 
I too use Ant to build my deployable archives. Eclipse is simply my IDE of choice. I validated that all the issues I listed occurred when running Ant from the command line.

If you are interested in how I do it, send me an e-mail (to [email protected]), and I'll send you a zip of one of these JWS projects. The build.xml script for the project, takes care of a lot of the "annoyances" you mentioned, one of which I think is not accurate. I have never had a situation where the wsdlc Ant task "overwrote" my XXXImpl.java file.. 
Since I'm doing a POC to determine how we want to proceed with developing Web Services and an SOA in general, I tried to perform the same tasks using Axis 2 1.0, the WebLogic 9.1 tools, and XFire 1.1. Overwriting the Impl class is a common failing in the tools which take a WSDL and create Java source files for all three frameworks.

Try my scenario. Add another operation to an existing WSDL, and run the wsdlc Ant Task. The old IMPL class will be over-written.

Because of this, I have a separate Impl class and I make sure that all its methods and annotations match the methods and annotations in the Skeleton Impl class created by wsdlc.

Maybe that's because I use the <exec> Ant task with jar.exe (the xvf options) in my build.xml, to only get what I need out of the .jar/.zip the wsdlc generates. I'm typically only interest in the interface class that my XXXImpl.java file needs to implements, because I use XMLBeans for the input args (and return values) of my web service operations. 
Perhaps. I am not using XMLBeans in any of the three frameworks because the resulting service seems to be lighter-weight in all three frameworks if XMLBeans is not used. I'm sure there will be scenarios where XMLBeans is preferred, but I have not encountered that case in this POC.

Regards,
Mike Wooten
Thanks for the follow-up.
Mike McAngus

Problems - WLS 10.0 web service client

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

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

Chat with Microsoft experts on XML Web Services Interoperability

Chat Title: XML Web Services Interoperability
The promise of XML Web services rests on interoperability and
ubiquity. Open standards and rigorous multi-vendor testing ensure that
a rich community of Web services implementations will proliferate.
Join us in this session with Keith Ballinger and Yann Christensen from
the team that brought you ASP.NET's Web services stack as we discuss
Microsoft's work in XML Web services interoperability.
When: Thursday – February 7th 12:00pm PST (3:00pm ET/8:00pm GMT/5:00am
Tokyo)
Information: http://msdn.microsoft.com/chats/

I'm wondering if it's the "=" and Quote in the parameter that is causing the search to fail to find your record
Try with just the value in the field tag
Wrong?
<ns2:ContactId>='AHMA-VD8RSZ'</ns2:ContactId>
<Id>='AHMA-VD6N8I'</Id>
Correct:
<ns2:ContactId>AHMA-VD8RSZ</ns2:ContactId>
<Id>AHMA-VD6N8I</Id>
Same for Last Name and other parameters
Edited by: Royston Goveia on Dec 6, 2012 1:09 AM

Best practice for simply invoking a web service

Hello,
We have web services deployed and accessible as wsdl documents in the SOA service manager/UDDI product. What is the best practice for simply calling a web service method deployed without regard to whether it is deployed on Tomcat, WebSphere, Oracle, etc.
I'd just like to create a java client to make a web service call and JAXRPC has me confused because you seem to have to have custody of the web service implementation code to call a service. Can someone point me in the right direction?
Thanks,
Sean

Thanks. Here is my wsdl, how would you say this is encoded?
<?xml version="1.0" encoding="UTF-8"?>
<definitions
 name="OracleProcess"
 targetNamespace="http://xmlns.oracle.com/OracleProcess"
 xmlns="http://schemas.xmlsoap.org/wsdl/"
 xmlns:tns="http://xmlns.oracle.com/OracleProcess"
 xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:client="http://xmlns.oracle.com/OracleProcess"
 >
 <types>
 <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/OracleProcess"
 xmlns="http://www.w3.org/2001/XMLSchema">
 <element name="OracleProcessProcessRequest">
 <complexType>
 <sequence>
 <element name="input" type="string"/>
 <element name="input2" type="string"/>
 </sequence>
 </complexType>
 </element>
 <element name="OracleProcessProcessResponse">
 <complexType>
 <sequence>
 <element name="result" type="string"/>
 </sequence>
 </complexType>
 </element>
 </schema>
 </types>
 <message name="OracleProcessRequestMessage">
 <part name="payload" element="tns:OracleProcessProcessRequest"/>
 </message>
 <message name="OracleProcessResponseMessage">
 <part name="payload" element="tns:OracleProcessProcessResponse"/>
 </message>
 <portType name="OracleProcess">
 <operation name="process">
 <input message="tns:OracleProcessRequestMessage"/>
 <output message="tns:OracleProcessResponseMessage"/>
 </operation>
 </portType>
 <binding name="OracleProcessBinding" type="tns:OracleProcess">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <operation name="process">
 <soap:operation style="document" soapAction="process"/>
 <input>
 <soap:body use="literal"/>
 </input>
 <output>
 <soap:body use="literal"/>
 </output>
 </operation>
 </binding>
 <service name="OracleProcess">
 <port name="OracleProcessPort" binding="tns:OracleProcessBinding">
 <soap:address location="http://st4s:9700/orabpel/default/OracleProcess/1.0"/>
 </port>
 </service>
<plnk:partnerLinkType name="OracleProcess">
 <plnk:role name="OracleProcessProvider">
 <plnk:portType name="tns:OracleProcess"/>
 </plnk:role>
</plnk:partnerLinkType>
</definitions>

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

Support for document and documentwrapped web services

List,
Are "document" and "documentwrapped" style web services supported in WSL 8.1 SP1?
The
documentation referenced below [1] [2] indicates that these styles are supported,
but in the
Unsupported Features section of the Web Services overview [3] states the RPC literal
style and
Document encoded style are not supported. It is my understanding that the style
attribute
values of the servicegen ant task map to the SOAP encodings as follows:
RPC -> SOAP RPC
documentwrapped -> SOAP RPC-literal
document -> SOAP document-literal
Is this correct?
Regards,
Kent
[1] http://edocs.bea.com/wls/docs81/webserv/design.html#1038901
[2] http://edocs.bea.com/wls/docs81/webserv/anttasks.html#1063540
[3] http://edocs.bea.com/wls/docs81/webserv/overview.html#1074641

So is it a true statement that if I use the documentwrapped style, I don't have
the restriction
of having only one void method while gaining the scalability and performance benefits
[1] of
SOAP document-literal encoding? Does the documentwrapped style have any restrictions
regarding out and in-out parameters? If so, what is the correct way in Java to
specify a
parameter as "IN" only?
Thanks again,
--Kent
[1] http://dev2dev.bea.com/products/wlworkshop/articles/Cohen.jsp
"manoj cheenath" <[email protected]> wrote:
This is correct. In the doc/lit bare case, a
method with no parameter will have an empty
soap envelope. If you look at the schema for
this operation, it will be an empty complexType.
So in the style, you can only have one void
method. WLS tools (servicegen/source2wsdd) do
not enforce this. Which I think is a bug.
Hope this helps,
-manoj
http://manojc.com
"manoj cheenath" <[email protected]> wrote in message
news:[email protected]...
This is correct. In the doc/lit bare case, a
method with no parameter will have an empty
soap envelope. If you look at the schema for
this operation, it will be an empty complexType.
So in the style, you can only have one void
method. WLS tools (servicegen/source2wsdd) do
not enforce this. Which I think is a bug.
Hope this helps,
-manoj
http://manojc.com
"Kent Kvarfordt" <[email protected]> wrote in message
news:[email protected]...
Bruce,
How do the restrictions apply to methods that do not have any paramters?
>>>
I have attached a copy of the weblogic webservice complex example that I
modified
to use
document style encoding and contains two noarg methods, getVersion
and
getAnotherVersion. I also modified the buy and sell methods to take single arguments.
Following are the results from the test web page for a call to getAnotherVersion.

<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:Header>
<env:Body>
</env:Body>
</env: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:Header>
<env:Body>
<n1:buy
xmlns:n1="http://www.bea.com/examples/Trader">getVersion</n1:buy>
</env:Body>
</env:Envelope>
What am I missing? BTW - I am using Weblogic Server 8.1 SP1.
Also, how does the weblogic documentwrapped style map to the SOAP encodings
SOAP RPC, SOAP RPC-literal, and SOAP document-literal? Are the messages encoded
SOAP doc/lit, but the programming model allows for multiple parameters? Is
the documentwrapped style specific to weblogic webservices?
And finally, given Java is a pass by value language, do I need to
do
anything
special to the webservice method signatures to specify the parameters
as
"IN"
parameters?
Thanks for all the help. From looking at the list traffic, your
keeping
busy.
Regards,
Kent
Bruce Stephens <[email protected]> wrote:
Hi Kent,
There are restrictions on the doc/lit style of encoding, such as
the
methods that implement each operation of the Web Service can have only
one parameter and the methods that implement each operation cannot use
out and in-out parameters. The documentwrapped generates a resulting
Web Service operations that can take any number of parameters, although
the parameter values will be wrapped into one complex data type in the
SOAP messages. Manoj has an example of documentwrapped [1].
We do not support rpc/lit. You might want to review this note by Yasser
Shohoud, it explains this in exquisite detail [2]
Regards,
Bruce
[1]
http://manojc.com/?sample14
[2]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsrv/h
tml/rpc_literal.asp
Kent Kvarfordt wrote:
List,
Are "document" and "documentwrapped" style web services supported
in
WSL 8.1 SP1?
The
documentation referenced below [1] [2] indicates that these styles are supported,
but in the
Unsupported Features section of the Web Services overview [3]
states
the RPC literal
style and
Document encoded style are not supported. It is my understanding
that
the style
attribute
values of the servicegen ant task map to the SOAP encodings as
follows:
RPC -> SOAP RPC
documentwrapped -> SOAP RPC-literal
document -> SOAP document-literal
Is this correct?
Regards,
Kent
[1] http://edocs.bea.com/wls/docs81/webserv/design.html#1038901
[2] http://edocs.bea.com/wls/docs81/webserv/anttasks.html#1063540
[3] http://edocs.bea.com/wls/docs81/webserv/overview.html#1074641

How to configure CA for access to a Web Service from an app deployed in WL

Hi everyone.
I have an app deployed in a WLS (10.3). This app acts like a web service client and works correctly (spring + cxf). The web service is provided by an external company and now they want to switch to https. They are using a self signed certificate. My company's support staff told me that they already configured the domain's trusted key store but the app fails to invoke the WS with the following error:
2010/12/03 13:06:12.314 [ERROR] [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-5] [ar.com.link.gp.services.impl.WebserviceConfirmacionServiceImpl - 55] - Error - informarPagos
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy549.confirmaPago(Unknown Source)
at ar.com.link.gp.services.impl.WebServiceClientServiceImpl.confirmaPago(WebServiceClientServiceImpl.java:103)
at ar.com.link.gp.services.impl.WebServiceClientServiceSinConceptoDecorator.confirmaPago(WebServiceClientServiceSinConceptoDecorator.java:33)
at ar.com.link.gp.services.impl.WebserviceConfirmacionServiceImpl.informarPagos(WebserviceConfirmacionServiceImpl.java:50)
at ar.com.link.gp.services.impl.ConfirmacionServiceImpl.procesarConfirmaciones(ConfirmacionServiceImpl.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at ar.com.link.logging.interceptor.LoggingInterceptor.invoke(LoggingInterceptor.java:74)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy514.procesarConfirmaciones(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.util.MethodInvoker.invoke(MethodInvoker.java:276)
at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:260)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1239)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1251)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:43)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
at weblogic.net.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:238)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1951)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.onFirstWrite(HTTPConduit.java:1903)
at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:42)
at org.apache.cxf.io.AbstractThresholdOutputStream.write(AbstractThresholdOutputStream.java:69)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1969)
at org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:47)
at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:188)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:637)
at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:483)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:309)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:261)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
... 25 more
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1591)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:975)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:123)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.getSession(SSLSocketImpl.java:1830)
at weblogic.net.http.HttpsClient.getSSLSession(HttpsClient.java:537)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:257)
at weblogic.net.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:237)
... 41 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:285)
at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:191)
at sun.security.validator.Validator.validate(Validator.java:218)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:954)
... 51 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:174)
at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:280)
... 57 more
I'm the app's developer and I don't have experience in this subjects. Is the wl misconfigured? Should I do something from the app to reference the keystore?
Thanks un advance.
Sorry for my english.

Hi user10939158, thank you for your response. Maybe I was not precise in my previous post. I know how certificates work and that I should not be using self signed ones. Due to a reason (non technical) we MUST use a self signed certificates. Considering this as a prerequisite let me clarify my situation:
- We added the certificate to the custom trust store connfigured in WL
- We configure the managed server to be more "verbose" about SSL stuff
- When the managed server start it outputs the following lines in the log:
<Dec 13, 2010 5:31:21 PM ARST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the JKS keystore file /wldomains/desa_domain/TrustCTWebservices.jks.>
<Dec 13, 2010 5:31:21 PM ARST> <Debug> <SecuritySSL> <BEA-000000> <SSLContextManager: loaded 1 trusted CAs from /wldomains/desa_domain/TrustCTWebservices.jks>
<Dec 13, 2010 5:31:21 PM ARST> <Debug> <SecuritySSL> <BEA-000000> <Subject: CN=jserver, OU=SWG, O=IBM, C=US; Issuer: CN=jserver, OU=SWG, O=IBM, C=US>
- In this lines we can see the certificate that interests us (jserver)
- When the app do a WS reqeust we see in the log:
<Dec 13, 2010 5:32:43 PM ARST> <Notice> <Stdout> <BEA-000000> <trustStore is: /opt/bea/jrockit_160_05/jre/lib/security/cacerts> (THE VM's DEFAULT KEYSTORE!!!!!!)
- If we add the cert to /opt/bea/jrockit_160_05/jre/lib/security/cacerts everything works ok but I have doubts that this is right.
Why the default keystore is used?
Thank you very much
Regards

Attachment in WLS 7 sp2 Web Service

Hi, I'm trying to send to a Web Service in WLS7 sp2 SOAP message with attachments. My problem: when I don't add any attachment to SOAP message all go OK, but when I add an attachment with the "href" attribute in an element of the message (I need do it because I use the MM7 protocol of 3GPP), WLS7 donÂ´t accept my message and tell me: "The ID referenced by ..... is unknow". The Content-ID of attachment is equal to value of the href attribute.
Please, I need help with this!! If anyone knows any URL or sample code that can help me, please, reply to this post.
Thanks and sorry, my english is not very well.

Currently there is no option to turn off security check.
I think you can use a servlet filter mapped to the URL
of your service, instead of a proxy servlet?
Regards,
-manoj
http://manojc.com
"Toni Nykanen" <[email protected]> wrote in message
news:3ef1577b$[email protected]..
>
Hi!
We need to implement authentication using our own methods, and theauthentication
information is provided to the web service implementation in a basicauthentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
in
wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
Is there any way to circumvent this, because we want to implementauthentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for ourown
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet,which
would
remove the basic authentication header, and put the authentication info incustom
headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
>
But still, I'd like to know if there is any way to tell bea's servlet toignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

Error 504 DNS look up failed while calling web services using XML

Hi, I am trying to call web service from Oracle using XML.
Everything seems to be in place but im getting an error "The webserver for <My End URL> reported that an error occurred while trying to access the website. Please click here to return to the previous page."
If I directly access the end url from my browser its accessible and seems to work fine.
The http response receiveed is mentioned below:
Status code: 403
Reason phrase: Forbidden
<html>
<head>
<title>504 DNS look up failed</title>
</head>
<body>
<table width="100%"><tr><td bgcolor=#3300cc align="center" colspan=2>504 DNS look up failed</td></tr></table> The webserver for 'My End URL' reported that an error occurred while trying to access the website. Please click here to return to the previous page. <hr></body>
</html>
Im using Oracle 9i
Please help
Edited by: 927814 on Apr 15, 2012 11:41 PM
Edited by: 927814 on Apr 15, 2012 11:46 PM

Without far greater details as to what you are doing, what you have installed, and what you have tried, not much can be offered. All that I can gather from the information you provided is that the server name you are trying to contact either is not responding or is invalid. If you have Forms installed on your local machine (for example using Developer Suite), try using localhost rather than the hostname. For example, http://localhost:port/forms/frmservlet?form=yourform
http://www.checkupdown.com/status/E504.html

Suggestions for Chunking Large Outbound Web Service Messages from BPEL

We have a problem today when Oracle EBS sends a large amount of data to BPEL, BPEL processes that data and then attempts to pass that data as a web service via a partner link to the PeopleSoft integration broker. When the message is too large ( > 10,000 records or so) we are hitting some issues on the PeopleSoft web server side being unable to receive that large of a message.
"allocLargeObjectOrArray - Object size: 32768016, Num elements: 8192000"
We are considering adjusting the BPEL program to chunk the outbound data being sent to PeopleSoft. The idea would be to use some type of loop and just break after so many lines, transmit the current message and then start a new message.
The PeopleSoft integration broker has a setting, for outbound type integrations, that can enable an automated chunking feature called ‘Max App Message Size’. I was wondering, does BPEL have a similar configuration setting that might provide this feature? I’m dreaming up that this could be a property of the partner link object that could allow you to specify a certain ‘max size’ and then it would just know to start a new message at that threshold. That might avoid us having to make any additional BPEL code changes at this point.
Currently using version 11.1.1.1.
Any advice, much appreciated.
Regards,
Ken

I have found the following tutorial that implements something similiar to what I am trying to do: http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/10g/10135/odiscenario_bpelcallback/odiscenario_bpelcallback.htm#t3
Because of this, I am now confident that the conversation IDs can be used to achieve correlation. I have implemented the pattern by performing
an invoke activity on the web service, passing the result of ora:getConversationId() as part of the message. The conversation Id returned is of UUID-Form.
After the invoke activity, I have added a pick activity to receive the response message supplied by the web service through IDeliveryService.post(...). I can see that the message is received correctly by loooking at the contents of DLV_MESSAGE. However, the pick activity times out every time (after 10m). Looking at DLV_SUBSCRIPTION reveals that the conversation_id for the pick/receive activity is set to a value of the form bpel://localhost/default/MyBpelProcessName~1.0/7610001-BpInv0-BpSeq2.7-2. As far as I know, this should instead be set to the UUID that ora:getConversationId() returned before performing the invoke activity. What is going wrong here?
Thanks for your help!

WSGEN question on WLS 6.1 / Web Services

I am just starting out with Web Services and I am trying to
build some examples from the WebLogic 6.1 Bible step-by-step
using Ant 1.3.
I get this error when I execute Ant with the -verbose option:
allen @ olc301 [5] ant -verbose rpc.ws
Ant version 1.3 compiled on March 2 2001
Buildfile: build.xml
Detected Java Version: 1.2
Detected OS: SunOS
parsing buildfile /lopt/local/tmp/src/code/webservices/build.xml with URI = file:/lopt/local/tmp/src/code/webservices/build.xml
Project base dir set to: /lopt/local/tmp/src/code/webservices
Build sequence for target `rpc.ws' is [rpc.ws]
Complete build sequence is [rpc.ws, producer.ws, consumer.build, consumer.ws,
ejb.build, help, producer.build, rpc.build]
rpc.ws:
BUILD FAILED
/lopt/local/tmp/src/code/webservices/build.xml:30:
Could not create task of type: wsgen.
Common solutions are to use taskdef to declare your task,
or, if this is an optional task, to put the optional.jar in
the lib directory of your ant installation (ANT_HOME).
Can anybody help me ? I see several similar questions in the
newsgroups but no answers - I am missing something simple I
think !!
Thanks in advance -

Don, thanks for the reply !
I was using a different version of Ant and using the BEA version helped. Maybe
this is something I missed in the documentation ?
Don Ferguson <[email protected]> wrote:
Are you using the version of ant that comes with WLS (which has the
taskdefs in the defaults.properties file) or your own copy of ant?
Ethan Allen wrote:
I am just starting out with Web Services and I am trying to
build some examples from the WebLogic 6.1 Bible step-by-step
using Ant 1.3.
I get this error when I execute Ant with the -verbose option:
allen @ olc301 [5] ant -verbose rpc.ws
Ant version 1.3 compiled on March 2 2001
Buildfile: build.xml
Detected Java Version: 1.2
Detected OS: SunOS
parsing buildfile /lopt/local/tmp/src/code/webservices/build.xml withURI = file:/lopt/local/tmp/src/code/webservices/build.xml
Project base dir set to: /lopt/local/tmp/src/code/webservices
Build sequence for target `rpc.ws' is [rpc.ws]
Complete build sequence is [rpc.ws, producer.ws, consumer.build, consumer.ws,
ejb.build, help, producer.build, rpc.build]
rpc.ws:
BUILD FAILED
/lopt/local/tmp/src/code/webservices/build.xml:30:
Could not create task of type: wsgen.
Common solutions are to use taskdef to declare your task,
or, if this is an optional task, to put the optional.jar in
the lib directory of your ant installation (ANT_HOME).
Can anybody help me ? I see several similar questions in the
newsgroups but no answers - I am missing something simple I
think !!
Thanks in advance -

Looking for; WS over Email proxy/service

Anyone seen an example or a jump start for a WebService over an Email service or an Email proxy?
IE a thick client makes WS / SOAP calls to this WS service that proxies the fetch mail / list of msgs from my POP3/IMAP mindspring account?
Any tips would be appreciated.
Thanks, curt

I've found web services over sending an email, which is quite simple.
I'm looking for parts or jump starts for browsing email on another server.
Thanks, curt

Looking for feedback on Photoshop web compatibility tool

We initially build https://www.oss-usa.com/psd-parser?promo=psd-parser as internal tool for validating Photoshop artwork against known web compatibility issues and recently made it available as a free online service. Looking for feedback from folks actively using Photoshop on web design projects.

Hello otechcomputing. is this how you want to setup your network?
If so, Guest Networks cannot be " extended" since it has Website Authentication encryption which the RE1000 does not support. Here are my suggestions:
1. Main Network WiFi password should be WPA2 Personal (more secured)
2. Enable Guest Access (password protected)
3. Reconfigure the RE1000 to connect to the EA6500 (main network) and change the extender's network name and password (still WPA2 Personal). You can name it with "EXT" at the end to designate it as such.

URL for WSDL only shows web service information page

Using tomcat6 and jwsdp 2.0.
After requesting the WSDL, I instead get the Web Service information page which shows this in a table form:
Web Services,
Port Name, Status, Information
etc.
Why doesn't it give me back the WSDL instead?

The information page must contain end point wise information displayed.
Each end point information contains web service address, WSDL address(you are looking for this I hope), Implementation class etc.
Also, try giving *?wsdl* parameter at the end of your web service address, it must lead you to the WSDL file of the web service.
-typurohit (Tejas Purohit)

Looking for WLS 7.x Web Services interoperability information

Similar Messages

Maybe you are looking for