aspose file tools*
The moose likes Websphere and the fly likes JAX-WS problem with WAS 8.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "JAX-WS problem with WAS 8.0" Watch "JAX-WS problem with WAS 8.0" New topic
Author

JAX-WS problem with WAS 8.0

Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 266
    
    1
I'm encountering big problems with JAX-WS services on WAS 8.0.0.2.

I've developed following Web Service via EJB 3.1, using only annotations.


The idea behind this web-service is to execute a request on server side, passing a CustomObject
instance serialized as binary stream. CustomObject is a class made available both on Java client
(a simple Java swing app) and EJB module: more precisely, CustomObject is present in a Java project
which is used as "utility jar" in the EAR project which contains WSBusinessDelegate ejb.

The problem is that I cannot deploy this web services, by publishing to WAS 8.0: the only way i can successfully
publish it, is by removing ALL references to CustomObject.
I cannot understand why. As far JAX-WS is concerned, what is exchanged between client and server sides
is a data stream, no matter what it actually is (the content of a file, or other).
I've read that there is a problem with wsgen called by WAS or RAD during deploying stage, when setting classpath,
but i don't know if this may be the case.

Can anybody help me ?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JAX-WS problem with WAS 8.0
 
Similar Threads
Web service development using Axis 2
Code to get SOAP request
When use mtom to transfer one file, server log shows the file is accessed twice.
ResponseWrapper in cxf
problem to send file