Weblogic-webservices-policy.xml

hi,
iam getting the following error in weblogic-webservices-policy.xml
Referenced file (weblogic-webservices-policy.xml) contains errors (http://www.bea.com/ns/weblogic/webservice-policy-ref/1.0/webservice-policy-ref.xsd).
weblogic-webservices-policy.xml containts the following lines of code:
<?xml version='1.0' encoding='UTF-8'?>
<webservice-policy-ref xmlns="http://www.bea.com/ns/weblogic/webservice-policy-ref" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/webservice-policy-ref http://www.bea.com/ns/weblogic/webservice-policy-ref/1.0/webservice-policy-ref.xsd"></webservice-policy-ref>
can anybody suggest how to fix this error?
thanks
john

Hi!
I was looking for some information regarding the weblogic-webservices-policy.xml file and founf your post. Did you success to solve the problem with it?
Greatly appreciate any inputs
Sincerely
J.

Similar Messages

Weblogic Webservices Malfunction

Hi to all. I'm developing WebServices with Java on Weblogic 12.1.2 server and I found two problems:
1) The "beaInvoke" method appears in my webservice. This method isn't in my wsdl file, and I don't know why Weblogic is creating it. I don't want this method in my service,because this can be a possible security problem.
2) In this java annotation
@javax.jws.WebService( serviceName = "ConversorSeguro",
                      portName = "ConversorSeguroSOAP",
                      targetNamespace = "urn:atica:cursosoa:services:conversorseguro",
                      wsdlLocation = "C:/Workspace/projects/prototipo/ConversorSeguro?wsdl",
                      endpointInterface = "org.umu.atica.secure.wservices.ConversorSeguro")
If I want to use in wsdlLocation parameter with relative path, like wsdlLocation = "prototipo/ConversorSeguro?wsdl" as I used to in OC4J, doesn't work. Weblogic needs a absolute path for do it. I need a relative path to use my webservice in develop and company servers.
How can I solve this problems?
Thanks.

Hi!
I was looking for some information regarding the weblogic-webservices-policy.xml file and founf your post. Did you success to solve the problem with it?
Greatly appreciate any inputs
Sincerely
J.

Wls 10.3 weblogic-webservices.xml transaction-timeout attribute not working

Hi, need some urgent need.
I have a stateless ejb webservice and I'm trying to set the transaction timeout for some of the methods. Right now my webservice transaction is timing out to the default of 30 secs. I've tried setting in the admin console the JTA transaction timeout option, didn't work (file a case with bea support #81233). And after days of researching and searching I came across that you can setup the weblogic webservice transaction-timeout thru the weblogic-webservices.xml deployment descriptor. Tried setting the transaction-timeout attribute to 120 secs. and that didn't work. Here is the snippet of the xml file.
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/weblogic-webservices" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-webservices http://www.bea.com/ns/weblogic/weblogic-webservices/1.0/weblogic-webservices.xsd">
<webservice-description>
<webservice-description-name>com.starcomsoft.pp.system.jws.SystemWSImpl</webservice-description-name>
<webservice-type>JAXRPC</webservice-type>
<port-component>
<port-component-name>SystemWSSoapPort</port-component-name>
<service-endpoint-address>
<webservice-contextpath>starcomsoft_ws</webservice-contextpath>
<webservice-serviceuri>/SystemWSImpl</webservice-serviceuri>
</service-endpoint-address>
     <transaction-timeout>120</transaction-timeout>
     <reliability-config>
          <inactivity-timeout>P0DT600S</inactivity-timeout>
     </reliability-config>
</port-component>
</webservice-description>
</weblogic-webservice>
Does anybody have any clue to solve my urgent need.
Thanks in advance for your help or suggestion.

Unhandled exception
Type=Segmentation error vmState=0x00040000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
Handler1=F144C588 Handler2=F1446A9C
Module=/app/oracle/product/Middleware/wlserver_10.3/server/native/aix/ppc/libmuxer.so
Module_base_address=D8457000
Target=2_40_20091214_049398 (AIX 5.3)
CPU=ppc (4 logical CPUs) (0x600000000 RAM)
----------- Stack Backtrace -----------
(0xD696E748 [libj9vm24.so+0x48748])
(0xD8383EDC [libjclscar_24.so+0x10edc])
(0xD8384514 [libjclscar_24.so+0x11514])
(0xD6967718 [libj9vm24.so+0x41718])
(0xD6967158 [libj9vm24.so+0x41158])
(0xD69640D0 [libj9vm24.so+0x3e0d0])
(0xD6932C9C [libj9vm24.so+0xcc9c])
(0xD69BBA18 [libj9prt24.so+0x3a18])
(0xD6932BB8 [libj9vm24.so+0xcbb8])
(0xD69A77CC [libj9thr24.so+0x27cc])
pthreadbody+0x118 (0xD010D784 [libpthreads.a+0x3784])

Setting dispatch-policy in weblogic-ejb-jar.xml

We are using Weblogic 8.1 sp2.
What are we trying to do-
Use the dispatch policy feature to allocate a new execute queue to a stateless session bean. This is to throttle the usage of this bean.
Problem(s) definition-
1. When I deploy the application with compiled EJBs (i.e. after running ejbc) IT WORKS.
If we deploy without compiling the EJBs IT DOES NOT WORK.
To be very sure I have already tried removing the EJBCompilerCache every time I restart the server.
I have made sure that we use the same weblogic.jar that the server uses during the compilation of the EJBs.
2. In both the cases mentioned above the weblogic-ejb-jar.xml when viewwed from the console does not show the dispatch-policy element.
Any help with regards to this would be highly appreciated.
Rgds,
Amresh

We are using Weblogic 8.1 sp2.
What are we trying to do-
Use the dispatch policy feature to allocate a new execute queue to a stateless session bean. This is to throttle the usage of this bean.
Problem(s) definition-
1. When I deploy the application with compiled EJBs (i.e. after running ejbc) IT WORKS.
If we deploy without compiling the EJBs IT DOES NOT WORK.
To be very sure I have already tried removing the EJBCompilerCache every time I restart the server.
I have made sure that we use the same weblogic.jar that the server uses during the compilation of the EJBs.
2. In both the cases mentioned above the weblogic-ejb-jar.xml when viewwed from the console does not show the dispatch-policy element.
Any help with regards to this would be highly appreciated.
Rgds,
Amresh

Validation errors weblogic-webservices.xml during deploy for valid dd

Hi,
I am trying to set the login-config for my JAXWS EJB webservice endpoint, but I weblogic doesn't accept my weblogic-webservices.xml
I validated my weblogic-webservices.xml using several xml validator tools and all say it is valid.
Here is the weblogic-webservices.xml
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices
     xmlns="http://xmlns.oracle.com/weblogic/weblogic-webservices"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
     xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-webservices http://xmlns.oracle.com/weblogic/weblogic-webservices/1.1/weblogic-webservices.xsd http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<webservice-description>
<webservice-description-name>AppManager</webservice-description-name>
<port-component>
<port-component-name>AppManager</port-component-name>
<service-endpoint-address>
<webservice-contextpath>/AppManagerService</webservice-contextpath>
<webservice-serviceuri>/AppManager</webservice-serviceuri>
</service-endpoint-address>
<login-config>
<j2ee:auth-method>BASIC</j2ee:auth-method>
<j2ee:realm-name>myrealm</j2ee:realm-name>
</login-config>
</port-component>
</webservice-description>
</weblogic-webservices>
Here are the validation errors I get during deployment:
VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a: Expected elements 'auth-method@http://java.sun.com/xml/ns/j2ee realm-name@http://java.sun.com/xml/ns/j2ee form-login-config@http://java.sun.com/xml/ns/j2ee' instead of 'auth-method@http://xmlns.oracle.com/weblogic/weblogic-webservices' here in element login-config@http://xmlns.oracle.com/weblogic/weblogic-webservices:<null> problem: cvc-complex-type.2.4a: Expected elements 'auth-method@http://java.sun.com/xml/ns/j2ee realm-name@http://java.sun.com/xml/ns/j2ee form-login-config@http://java.sun.com/xml/ns/j2ee' instead of 'realm-name@http://xmlns.oracle.com/weblogic/weblogic-webservices' here in element login-config@http://xmlns.oracle.com/weblogic/weblogic-webservices:<null>
Error VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a: Expected elements 'auth-method@http://java.sun.com/xml/ns/j2ee realm-name@http://java.sun.com/xml/ns/j2ee form-login-config@http://java.sun.com/xml/ns/j2ee' instead of 'auth-method@http://xmlns.oracle.com/weblogic/weblogic-webservices' here in element login-config@http://xmlns.oracle.com/weblogic/weblogic-webservices:<null> problem: cvc-complex-type.2.4a: Expected elements 'auth-method@http://java.sun.com/xml/ns/j2ee realm-name@http://java.sun.com/xml/ns/j2ee form-login-config@http://java.sun.com/xml/ns/j2ee' instead of 'realm-name@http://xmlns.oracle.com/weblogic/weblogic-webservices' here in element login-config@http://xmlns.oracle.com/weblogic/weblogic-webservices:<null>
If I remove the namespace indicator 'j2ee' it complains about the same. So it would seem that weblogic ignores the 'j2ee' resulting indeed in a invalid xml.
Can someone please help me to a weblogic-webservices.xml (example with login-config) that was accepted by weblogic?
Thanks a lot,
Eltjo.

Hi,
Please try the following: ( Looks like you are mixing the Tag contents of web.xml as well as weblogic-webservice.xml   together.... )
weblogic-webservice.xml
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/weblogic-webservices" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-webservices http://www.bea.com/ns/weblogic/weblogic-webservices/1.0/weblogic-webservices.xsd">
      <webservice-description>
          <webservice-description-name>AppManager</webservice-description-name>
          <port-component>
          <port-component-name>AppManager</port-component-name>
                 <service-endpoint-address>
                    <webservice-contextpath>/AppManagerService</webservice-contextpath>
                    <webservice-serviceuri>/AppManager</webservice-serviceuri>
                 </service-endpoint-address>
          </port-component>
      </webservice-description>
</weblogic-webservices>And Now provide the <login-config> information separately inside *"web.xml"* file
<login-config>
     <auth-method>BASIC</j2ee:auth-method>
     <realm-name>myrealm</j2ee:realm-name>
</login-config>.
Thanks
Jay SenSharma

Call Weblogic WebService in Delphi

Hi, I'm a newbie in WebService. I use Weblogic servicegen ant task wrap a stateless
EJB to webservice. The bean has a method with a string input parameter as follow:
String Test(String inputParam);
The WSDL generated by Weblogic WebService is like follow:
- <message name="Test">
<part name="string" xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:string"
/>
I use Delphi as Webservice client. When I use Delphi's WSDL Import Wizard, it
renamed parameter "string" to "string_" because of "string" is a reserved word
in Delphi. So when I invoked the Webservice, an exception was thrown:
Found SOAPElement [<string_ xsi:type="xsd:string>test</string_>]. But was not
able to find Part that is registered with this Message which corresponds to this
SOAPElement
How can I solve this problem? On the another word, Can I control the parmater
name generate by Weblogic Webservice ant task?
thanks very much!

Please post web services issues in the webservices newsgroup.
Vimala wrote:
You can define the parameter name to the method and return parameter name with
a web-services.xml.
The link below should give a good start:
http://e-docs.bea.com/wls/docs70/webserv/dd.html#1057960
Vimala
"Dumack Wu" <[email protected]> wrote:
Hi, I'm a newbie in WebService. I use Weblogic servicegen ant task wrap
a stateless
EJB to webservice. The bean has a method with a string input parameter
as follow:
String Test(String inputParam);
The WSDL generated by Weblogic WebService is like follow:
- <message name="Test">
<part name="string" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string"
/>
I use Delphi as Webservice client. When I use Delphi's WSDL Import Wizard,
it
renamed parameter "string" to "string_" because of "string" is a reserved
word
in Delphi. So when I invoked the Webservice, an exception was thrown:
Found SOAPElement [<string_ xsi:type="xsd:string>test</string_>]. But
was not
able to find Part that is registered with this Message which corresponds
to this
SOAPElement
How can I solve this problem? On the another word, Can I control the
parmater
name generate by Weblogic Webservice ant task?
thanks very much!
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Error in Weblogic Webservice

I was using SAAJ 1.3 initially in WEBINF/lib and my code erred with
java.lang.NoSuchMethodError: newInstance at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection
Error Location:
SOAPConnectionFactory factory = SOAPConnectionFactory.newInstance();
SOAPConnection connection = factory.createConnection();
It erred on the above highlighted line. After some searching, I found that it could be because of Weblogic Server 9.2 not compatible with SAAJ 1.3. So I used SAAJ 1.2 and this error got solved. Now I am stuck up with the following error.
java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1
at weblogic.webservice.core.soap.SOAPMessageImpl.getSOAPBody(SOAPMessageImpl.java:634)
Error Location:
SOAPElement attachmentElement = (SOAPElement)message.getSOAPBody().getElementsByTagNameNS(ws, "Attachment").item(0);
I am using SAAJ 1.2 but it says the class does not support SAAJ 1.1.
Again after some googling, I found that the error is due to some bug in Weblogic 9.2 when it is used with SAAJ 1.2. It was mentioned that following steps can be used to overcome this error.
1. Set classpath to latest saaj-impl.jar in startweblogic.cmd
2. Set the below 2 system properties in code.
System.setProperty("javax.xml.soap.MessageFactory","com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl");
System.setProperty("javax.xml.soap.SOAPConnectionFactory","weblogic.wsee.saaj.SOAPConnectionFactoryImpl");
I tried this too but it didnt work.
How can i get rid of this error? Also if i m going to set the classpath to SAAJ 1.3 in startweblogic.cmd, will it not result in the first error i got i.e java.lang.NoSuchMethodError: newInstance at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.
If my question is not very clear, please bear with me. I am pretty new to Webservice.
Can someone tell me how can i overcome this problem.

Have you included the IP addresses of the managed servers into the cluster address like for eg 192.127.1.2,192.127.1.2 in the cluster address field in the administration console? include it if not included that will fix the issue.
Regards,
Dinesh

Sample weblogic-ejb-jar.xml for Resource-ref EJB 3.0

I am trying to create an MDB that can be re-used under different names.
@MessageDriven(description = "An MDB that transfers messages from one Queue to another", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class TransferMdb implements MessageListener {
private static final Logger LOG = Logger.getLogger(TransferMdb.class);
@Resource(name = "jms/connfactory")
private ConnectionFactory connectionFactory;
@Resource(name = "jms/targetDestination")
private Queue targetDestination;
<ejb-jar version="3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_3_0.xsd">
<enterprise-beans>
<message-driven>
<ejb-name>TransferMdb</ejb-name>
<ejb-class>TransferMdb</ejb-class>
</message-driven>
</enterprise-beans>
</ejb-jar>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>TransferMdb</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>200</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>test_queue</destination-jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>20</trans-timeout-seconds>
</transaction-descriptor>
</message-driven-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jms/connectionfactory</res-ref-name>
<jndi-name>connectionfactory</jndi-name>
</resource-description>
<resource-description>
<res-ref-name>jms/targetDestination</res-ref-name>
<jndi-name>reply_queue</jndi-name>
</resource-description>
</reference-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
However when I deploy the above, I get exceptions such as:
problem: cvc-complex-type.2.4a: Expected elements 'initial-context-factory@http://www.bea.com/ns/weblogic/weblogic-ejb-jar provider-url@http://www.bea.com/ns/weblogic/weblogic-ejb-jar connection-factory-jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jms-polling-interval-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jms-client-id@http://www.bea.com/ns/weblogic/weblogic-ejb-jar generate-unique-jms-client-id@http://www.bea.com/ns/weblogic/weblogic-ejb-jar durable-subscription-deletion@http://www.bea.com/ns/weblogic/weblogic-ejb-jar max-messages-in-transaction@http://www.bea.com/ns/weblogic/weblogic-ejb-jar distributed-destination-connection@http://www.bea.com/ns/weblogic/weblogic-ejb-jar use81-style-polling@http://www.bea.com/ns/weblogic/weblogic-ejb-jar init-suspend-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar max-suspend-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar security-plugin@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' instead of 'transaction-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' here in element message-driven-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar:<null>
problem: cvc-complex-type.2.4a: Expected elements 'transaction-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar iiop-security-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar resource-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar resource-env-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar ejb-reference-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar service-reference-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar enable-call-by-reference@http://www.bea.com/ns/weblogic/weblogic-ejb-jar network-access-point@http://www.bea.com/ns/weblogic/weblogic-ejb-jar clients-on-same-server@http://www.bea.com/ns/weblogic/weblogic-ejb-jar run-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar create-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar remove-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar passivate-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar local-jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar dispatch-policy@http://www.bea.com/ns/weblogic/weblogic-ejb-jar remote-client-timeout@http://www.bea.com/ns/weblogic/weblogic-ejb-jar stick-to-first-server@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' instead of 'reference-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' here in element weblogic-enterprise-bean@http://www.bea.com/ns/weblogic/weblogic-ejb-jar:<null>
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
Truncated. see log file for complete stacktrace
I am clearly missing items in the weblogic-ejb-jar.xml. If anyone has a sample or tips, that would be awesome as a starting point.

Those tags just declare that you are using our CMP provider and that
your descriptor is in META-INF/weblogic-cmp-rdbms-jar.xml.
FWIW, you might also want to check out EJBGen. It tends to keep more up
to date with WLS than xdoclet.
-- Rob
Gen wrote:
I am using xdoclets to generate descriptor file weblogic-ejb-jar.xml
for a BMP entity bean. Xdoclet is generating the descriptor file
alright, but is putting the following extra tags. This happens even
for samples which come with the download, so my tags in java file are
not wrong.
My question is, are the extra tags below harmless, or should I
manually go to each desciptor file and remove them?
Thanks.
----------- EXTRA TAGS GENERATED START ---------
persistence> <persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
----------- EXTRA TAGS GENERATED END ---------
----------- TAGS I PUT IN JAVA CLASS START --------
* @ejb:bean name="com.ejb.entity.Customer"
* jndi-name="com.ejb.entity.CustomerHome"
* view-type="remote"
* type="BMP"
* primkey-field="com.ejb.entity.CustomerPK"
* reentrant="false"
* @weblogic:cache
* max-beans-in-cache="1000"
* read-timeout-seconds="900"
* concurrency-strategy="ReadOnly"
----------- TAGS I PUT IN JAVA CLASS END --------

Eclipse:package weblogic.webservice.tools.wsdlp does not exist

Hi, everyone! I got an error While I was Compiling the Entire MedRec Project application on Eclipse3.1 with ant. However, when I used setEnv.cmd and ant command(), it's all Ok! The error message shows as below:
banner:
[echo] #### S T A R T C O M M O N W E B A P P ####
[mkdir] Created dir: C:\medrec_tutorial\build\tmp
build:
[javac] Compiling 23 source files to C:\medrec_tutorial\build\tmp
[javac] C:\medrec_tutorial\src\common\web\com\bea\medrec\utils\MedRecWebAppUtils.java:319: package weblogic.webservice.tools.wsdlp does not exist
[javac] if (th instanceof weblogic.webservice.tools.wsdlp.WSDLParseException) {
[javac] ^
[javac] 1 error
BUILD FAILED
file:C:/medrec_tutorial/src/common/web/build.xml:29: Compile failed; see the compiler error output for details.

Bruce Stephens <[email protected]> wrote:
Hello,
This looks like a bug that has already been reported and resolved. If
you could provide your test case to our super support group [1], and
reference CR127344, they should be able to sort out this issue.
Thanks,Hi ,
I also got the same error.If u find the solution please email me
isuru [email protected]
Thanx
Bruce
[1]
http://support.bea.com
[email protected]
Franck wrote:
Hello,
when I try to build my webservice with a stateless bean and a complexdata type (byte[]), by using ANT and SERVICEGEN.
I have the following exception (with WL 8.1, but it works witout problemwith WL 7.0.4).
*** ERROR:
-package weblogic.xml.schema.binding does not exist
[servicegen] extends weblogic.xml.schema.binding.BeanCodecBase
What has changed between the both version.
can somebody help me
Tank you
Regards

Java.lang.ClassCastException: weblogic.webservice.core.soap.SOAPMessageImpl

Hello Gurus,
Can you please help me with following issue--
I have created a secured web service's client from netbeans 6.8.Then I made a jar file of it.Then I have integrated that jar in my ADF application's viewcontroller project .I have used the jar from backing bean of a jspx page.
If I create a main method in the bean and call the service from inside main method then everything works fine but if i remove the main method and call the service from a button click of the jspx page then i get the following error.
<Jan 7, 2012 11:01:34 AM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<ActionListenerImpl><processAction> java.lang.ClassCastException: weblogic.webservice.core.soap.SOAPMessageImpl cannot be cast to com.sun.xml.messaging.saaj.soap.MessageImpl
javax.faces.el.EvaluationException: java.lang.ClassCastException: weblogic.webservice.core.soap.SOAPMessageImpl cannot be cast to com.sun.xml.messaging.saaj.soap.MessageImpl
     at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:51)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
     at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:698)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:285)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:62)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassCastException: weblogic.webservice.core.soap.SOAPMessageImpl cannot be cast to com.sun.xml.messaging.saaj.soap.MessageImpl
     at com.sun.xml.rpc.client.StubBase._postSendingHook(StubBase.java:231)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:324)
     at com.sahaj.billDetails.NotifySREIBilling_OB_Stub.notifySREIBilling_OB(NotifySREIBilling_OB_Stub.java:67)
     at com.sahaj.tester.Tester.getBillDetails(Tester.java:94)
     at Test.cb1_action(Test.java:19)
     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 com.sun.el.parser.AstValue.invoke(AstValue.java:157)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:46)
     ... 36 more
My bean class looks as follows--
public class Test {
public Test() {
*public String cb1_action() {//does not work*
HashMap billDetails = new Tester().getBillDetails("212078438");
System.out.println(billDetails.size());
return null;
*public static void main(String[] args) {//works*
HashMap billDetails = new Tester().getBillDetails("212078438");
System.out.println(billDetails.size());
}

Hi Mike,
Support for SAAJ was added in WLS 8.1, see:
http://edocs.bea.com/wls/docs81/webserv/interceptors.html#1058444
Can you try your code on the latest release?
Thanks,
Bruce
Mike Reiche wrote:
>
What do I need to fix this?
WLS 7.0 sp2
- Mike
java.lang.Error: NYI
at
weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessageImpl.j
ava:360)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnec
tion.java:228)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run
(HttpSOAPConnection.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnec
tion.java:126)

SEVERE: caught throwable java.lang.AbstractMethodError: weblogic.webservice

Hi,
I am getting the following error while calling the webservice deployed in Weblogic 8.1sp5 version: Please help:
SEVERE: caught throwable
java.lang.AbstractMethodError: weblogic.webservice.core.soap.SOAPEnvelopeImpl.normalize()V
at com.sun.xml.rpc.streaming.XmlTreeReader.parse(XmlTreeReader.java:133)
at com.sun.xml.rpc.streaming.XmlTreeReader.next(XmlTreeReader.java:103)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.java:23)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderBase.java:41)
at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:154)
at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:443)
at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Where you ever able to get this working on WLS? I am dealing with the same problem on WLS 8.1 sp2

Java.lang.Error: NYI at weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessageImpl.java:360)

What do I need to fix this?
WLS 7.0 sp2
- Mike
java.lang.Error: NYI
at
weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessageImpl.j
ava:360)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnec
tion.java:228)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run
(HttpSOAPConnection.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnec
tion.java:126)

Hi Mike,
Support for SAAJ was added in WLS 8.1, see:
http://edocs.bea.com/wls/docs81/webserv/interceptors.html#1058444
Can you try your code on the latest release?
Thanks,
Bruce
Mike Reiche wrote:
>
What do I need to fix this?
WLS 7.0 sp2
- Mike
java.lang.Error: NYI
at
weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessageImpl.j
ava:360)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnec
tion.java:228)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run
(HttpSOAPConnection.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnec
tion.java:126)

Reliable SOAP messaging problems - weblogic.webservice.saf.StoreForwardException

Hi Guys,
I'm playing with the new SOAP reliable message transport in WL 8.1 SP 1.
I have configured a simple web service, with void return, configured for
reliable messaging. I deploy the client to the same server as the server
hosting the webservice, and it uses the async invocation etc.
It wasn't obvious how to throw the exception in the backend implementation.
I simply grab the usertransaction
and call ut.setRollbackOnly(). Hope that's correct..
Whenever I invoke the operation, I get this:
weblogic.webservice.saf.StoreForwardException: Could not find MessageData
header in aknowledgement
I have a JMS file store setup, and I have it assigned to the server via the
services/webservice tab, and I do see some activity in the file store.
My client looks like this:
AsyncInfo asyncInfo = new AsyncInfo();
asyncInfo.setReliableDelivery(true);
FutureResult fr = port.startReliableOperation("hello World", asyncInfo);
System.err.println("Client: Made invocation, invoking async end now");
port.endReliableOperation(fr);
Any ideas?
Regards,
Jon
PS. [As an aside, aknowledgement needs a 'c']
Client: port.StartReliableOperation()
--S:In reliable TX operation
--S:Going to roll back
--S: Set setRolbackOnly()
--S: Finished Reliable operation
Client: Made invocation, invoking async end now
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220025> <Handler
web
logic.webservice.saf.SAFHandler threw an exception from its handleResponse
metho
d. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.>
myserver:Info:Handler weblogic.webservice.saf.SAFHandler threw an exception
from
its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220047> <A
exception
was thrown from callReceive in the Client Dispatcher.>
myserver:Info:A exception was thrown from callReceive in the Client
Dispatcher.
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220034> <A stack
tra
ce associated with message 220047 follows:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing:
weblogic.web
service.saf.StoreForwardException: Could not find MessageData header in
aknowled
gement. (see Fault Detail for stacktrace)
at
weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.ja
va:285)
at
weblogic.webservice.core.ClientDispatcher.callReceive(ClientDispatche
r.java:119)
at
weblogic.webservice.saf.ConversationAssembler.getResponse(Conversatio
nAssembler.java:302)
at
weblogic.webservice.saf.ConversationAssembler.execute(ConversationAss
embler.java:536)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Hi Jon,
I've asked our WS RM guru to comment on your question, but I believe the
answer is going to be that you can explicitly roll back the transaction,
however only from the EJB application method, using the
EJBContext.setRollbackOnly() method.
Regards,
Bruce
Jon Mountjoy wrote:
>
Hi Bruce,
I looked at the example you pointed to, and it does what it says it does.
However, it doesn't attempt to rollback a transaction, which is what I am
doing.
The docs for reliable messaging say:
" If you want to roll back the transaction from the Java method, use the
Java Transaction API (JTA) to get the transaction object and then explicitly
roll back the transaction. "
They also indicate that the receiver executes in the context of a
transaction, which you may rollback.
For example, when the server is down, the transaction doesn't commit. This
behaviour is tested by your example, and it works.
However, when I modify your example to roll back the transaction in the web
service operation backend implementation,
then it doesn't. It yields the same exception that mine does.
For example, I modified your MarketService.java as indicated below to grab
the initial context and then during the operation grab the usertransaction
and call setRollbackOnly(). This causes WebLogic to throw a
weblogic.webservice.saf.StoreForwardException.
Any ideas?
Regards,
Jon
public final class MarketService {
private static boolean mustThrow = true;
InitialContext ctx = null;
public MarketService() {
try {
ctx = new InitialContext();
System.err.println("---InitialContext is set");
} catch (Exception e) {
System.err.println("---InitialContext is not set: " + e);
public void placeOrder(OrderInfo o) {
System.out.println("[MarketService] placing order: " + o);
mustThrow = !mustThrow;
if (mustThrow) {
System.out.println("--S:Going to roll back");
UserTransaction ut = null;
try {
ut = (UserTransaction) ctx.lookup(
"javax.transaction.UserTransaction");
System.out.println("--S: Set setRolbackOnly()");
ut.setRollbackOnly();
// <------------------------------------------
} catch (Exception e) {
System.err.println("--S: UT transaction error:" + e);
} else {
System.out.println("--S: -Not rolling back");
--S:In reliable TX operation
--S:Going to roll back
--S: Set setRolbackOnly()
--S: Finished Reliable operation
<29-Aug-2003 15:48:24 o'clock BST> <Info> <WebService> <BEA-220025> <Handler
weblogic.webservice.saf.SAFHandler threw an
exception from its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.>
myserver:Info:Handler weblogic.webservice.saf.SAFHandler threw an exception
from its handleResponse method. The exceptio
n was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.
<29-Aug-2003 15:48:25 o'clock BST> <Info> <WebService> <BEA-220047> <A
exception was thrown from callReceive in the Clie
nt Dispatcher.>
myserver:Info:A exception was thrown from callReceive in the Client
Dispatcher.
<29-Aug-2003 15:48:25 o'clock BST> <Info> <WebService> <BEA-220034> <A stack
trace associated with message 220047 follow
s:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing:
weblogic.webservice.saf.StoreForwardException: Could
not find MessageData header in aknowledgement. (see Fault Detail for
stacktrace)
at
weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:285)
at
weblogic.webservice.core.ClientDispatcher.callReceive(ClientDispatcher.java:
119)
at
weblogic.webservice.saf.ConversationAssembler.getResponse(ConversationAssemb
ler.java:302)
at
weblogic.webservice.saf.ConversationAssembler.execute(ConversationAssembler.
java:536)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
myserver:Info:A stack trace associated with message 220047 follows:

Weblogic-ejb-jar.xml tags

can anybody tell me if the jndi name tag can come before the ejbtype-descriptor tag
like instead of the usual
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>MyTestSessionBean</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<jndi-name>MyTestSessionBean</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
can it be like
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>MyTestSessionBean</ejb-name>
<jndi-name>MyTestSessionBean</jndi-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<jndi-name>MyTestSessionBean</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
i think it should not be a problem as long as its within the <weblogic-enterprise-bean>: i am generating DDs for weblogic and ejbs and its a big applictaion i dont know if it will work or not. thanks in advance
Message was edited by sarmahdi at Sep 3, 2004 7:45 AM

it seems that unfortunately i cannot but i really appreciate your answer:
ejbname should follow descriptor then jndi name i gues as i am having errors
<!ELEMENT weblogic-enterprise-bean (
ejb-name,
(entity-descriptor|
stateless-session-descriptor|
stateful-session-descriptor|
message-driven-descriptor
transaction-descriptor?,
iiop-security-descriptor?,
reference-descriptor?,
enable-call-by-reference?,
clients-on-same-server?,
(run-as-identity-principal|
run-as-principal-name
create-as-principal-name?,
remove-as-principal-name?,
passivate-as-principal-name?,
jndi-name?,
local-jndi-name?,
dispatch-policy?)
>
i am having this error: Module: core_ejb_sb.jar Error: [EJB:011024]The XML parser encountered an error in your deployment descriptor.
Please ensure that your deployment descriptor corresponds to the format in the DTD. The error was:
Error parsing file 'META-INF/weblogic-ejb-jar.xml' at line: 9 column: 29. The content of element
type "weblogic-enterprise-bean" must match "
(ejb-name,
(entity-descriptor|stateless-session-descriptor|stateful-session-descriptor|message-driven-descriptor)?,
transaction-descriptor?,iiop-security-descriptor?,reference-descriptor?,enable-call-by-reference?,clients-on-same-server?,(run-as-identity-principal|
run-as-principal-name)?,create-as-principal-name?,remove-as-principal-name?,passivate-as-principal-name?,jndi-name?,local-jndi-name?,dispatch-policy?)"
i guess i have to change the format now.

How to resolve setPrefix() in SOAP(saaj API) with weblogic/webservices jar?

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Weblogic-webservices-policy.xml

Similar Messages

Maybe you are looking for