Hi all,
This is the scenario.
I created a WSDL and the generated the server side and client side code
using the WSDL2Java tool. After that i published the Web service in Jetty,,
as done by the generated server code.
The web service is working fine when i tested it using a standalone client.
I am
Hi,
It seems error from your web app code, since it says:
java.lang.UnsupportedOperationException: s
etProperty must be overridden by all subclasses of SOAPMessage
can you show more codes...
Thanks
Jeff
shaminda perera wrote:
Hi all,
This is the scenario.
I created a WSDL and the
Hi,
This looks to me as if it is a library problem. If you have bundled up
the CXF classes in a war file then this will probably be what is happening.
Explanation as follows:
The JBoss implementation of SOAPMessage is an abstract class which
provides default implementations of
Thanks Andrew and Jeff for the quick reply..
See below for some a more detailed stacktrace,,, if that helps..
12:18:05,101 FATAL [application] javax.ejb.EJBTransactionRolledbackException:
java.lang.UnsupportedOperationException: s
etProperty must be overridden by all subclasses of
Oops, one more slip of the pasting finger! Here is the correct version
of those last three mappings
META-INF/services/javax.xml.soap.MetaFactory
META-INF/services/javax.xml.soap.SOAPFactory
META-INF/services/javax.xml.ws.spi.Provider
should each contain a single line, respectively,
Hi shaminda,
Actually, I believe I have misled you slightly. The required mapping is
for MessageFactory, not SOAPMessage. The mapping is provided by jboss in
file jboss-saaj.jar which provides a file called
META-INF/services/javax.xml.soap.MessageFactory
You need to remap this by
Thanks Andrew,,
But i didnt bundle any of the CXF jars in my WAR file to start with
comments?
On 10/17/07, Andrew Dinn [EMAIL PROTECTED] wrote:
Oops, one more slip of the pasting finger! Here is the correct version
of those last three mappings
shaminda perera wrote:
Thanks Andrew,,
But i didnt bundle any of the CXF jars in my WAR file to start with
Ok, we'll come back to that in a second. Irrespective of this when using
CXF within a JBoss server you are still going to face problems with the
fact that CXF and JBoss employ
Thanks andrew for the detailed mail.
This is what i am doing currently:
I created a Web service client side related classes using the WSDL2Java tool
provided by CXF, and then put just put these classes in a suitable package
in the main web application. I didnt put any of the CXF provided
