Hey guys, Thanks for your replies and apologises for the delay getting back to you!
This one is a non-issue, after trying to debug this one for some time, it turned out to be a build issue, whereby the outputted ear was invalid and so the same scenario worked after a rebuild - it's all happy on both weblogic and websphere. Cheers, Dave. -- Dave Sowerby MEng MBCS On Mon, Sep 29, 2008 at 4:54 PM, Raymond Feng <[EMAIL PROTECTED]> wrote: > Hi, > > Can you post the java bean class that you are passing? And the xml for the > marshaled object? > > Thanks, > Raymond > > From: Simon Laws > Sent: Sunday, September 28, 2008 2:12 AM > To: [email protected] > Subject: Re: Issue with JAXBDataBinding > > > > > > On Sun, Sep 28, 2008 at 8:46 AM, Dave Sowerby <[EMAIL PROTECTED]> > wrote: > > Hi guys, > > I'm having some difficulties when attempting to call one of my > services using the default binding on websphere (the client and > service are both on websphere). > > 1) Client fetches reference to service, using default binding. > 2) Client passes a bean with two variables, neither of which are null. > 3) During the data binding, the code executes > JAXBDataBindingExtensionPoint$LazyDataBinding.copy(Object, DataType, > operation) > 4) The argument for marshalling created by the > JAXBContextHelper.java:108 contains the correct original value > containing both non-null variables. > 5) The unmarshalled value object returned on line 111 contains an > instance of the same bean class, but where both variables are null. > > It's worth noting that because of TUSCANY-2531, this bean is marked > with the XmlType annotation, using the namespace element. > > Does anyone know, if the use of the XmlType could be causing this > issue - or if (without changing the service interface) I could pass > these values by reference, as I'm using the default binding I'd > imagine that should function normally? > > Cheers, > > Dave. > > -- > Dave Sowerby MEng MBCS > > > Hi Dave > > Are the client/server contributed to the same node, i.e. are they in the > same webapp? > > If you've got a test case, or failing that the interface you are using, I'll > try and run it up here and see what happens. > > Regards > > Simon >
