Hi
I'm not sure if returning hibernate objects directly is a good idea (
personally i don't like this :). I prefer using DTO which give you
more control over data sending over the wire.
You can also try using aegis mappings files to control which
properties are serialized or use dynamic proxy on object which
contains not initialized collections ( someone mentioned this in
context of returning hibernate objects )
On 11/8/06, Andrew Kerr <[EMAIL PROTECTED]> wrote:
Hi there,
I am currently porting an application from Axis 1.4 to XFire 1.2.2.
In Axis, we added a custom BeanSerializer implementation that prevented
uninitialized Hibernate collections from being serialized. This allowed
us to control which "pieces" of an object were returned from specific
web services.
For example, one web service might return a shallow version on an
object, while another would return a deep version of the object will all
its subcollection initialized.
I'd like to implement something similar for XFire. I'd appreciate it if
someone could point me in the right direction.
Thanks,
Andrew
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
