Me to. There is another strange thing in this:
The service causing the problems returns the Subscription.class object. In it all fields BUT ONE are set to null when returned from the client proxy!!! This field is another complex domain object of mine that is also loaded via hibernate spring aop (Customer.class foreign key). That is so strange, I also have no clue where to go but I think that this is scrambled up somewhere deep down in the reflection call to the WS method done by the client proxy. -----Ursprüngliche Nachricht----- Von: Brad Harper [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 27. Juli 2007 17:17 An: cxf-user@incubator.apache.org Betreff: Re: Complex Types contain all null values... That's exactly the same issue I'm seeing. It's just for complex types... Strings, Longs both return successfully. Sorry for the duplicate topic... I'm pretty much standing still at this point. On 7/27/07, Holger Stolzenberg <[EMAIL PROTECTED]> wrote: > > I am not sure if this helps but: > > How do you get the object, are using a debugging breakpoint at the > return statement of the service method or at the object returned by your > client? > > I also have an WS returning a business object (gets loaded through > Spring AOP transaction demarcation and hibernate). The problem is that > the object returned by the service itself has all fields filled (set a > breakpoint at the return statement of the service), but when calling > the service from a CXF client proxy all the fields in the object are null. > > Just thought that could be the same problem posted for it to the list > with the subject 'WS client returning uninitialized objects' but got > no answer yet. > > > -----Ursprüngliche Nachricht----- > Von: Brad Harper [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 27. Juli 2007 17:01 > An: cxf-user@incubator.apache.org > Betreff: Complex Types contain all null values... > > Simple types are returning correctly. I have four methods on the > service below... methods returning Strings are working... other > methods return business objects. I can step through the service on > the server and those methods are returning the correct values. No > exceptions are thrown and the object contains all null values in the client. > > Spring Wiring: > <!-- Local --> > <bean id="PricingServiceImpl" class=" > com.gdservices.service.thirdparty.PricingServiceImpl"> > <property name="daoFactory"> > <ref bean="hibernateDAOFactory"/> > </property> > </bean> > <!-- Web --> > <jaxws:endpoint > id="pricingService" > implementor="#PricingServiceImpl" > address="/pricingService" /> > > > I'm currently only using the @Webservice annotation and no method level > annotations. Anyone else seen this? >
