• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JAX-WS problem with WAS 8.0

 
Bartender
Posts: 1357
39
IBM DB2 Netbeans IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 ?
 
reply
    Bookmark Topic Watch Topic
  • New Topic