No, I dont think so. If it had something to do with TopLink, it would not
work as a session neither.
Using the same code, but as a session bean, I can find the object and print
the relation with no problems.
This only occurs when I'm moving the object as a web service.
glassfish wrote:
>
> Can it be that that side of the relationship is not set when you create
> the entities? If you use TopLink Essentials (which is the default in
> GlassFish), it caches entities states as-is, i.e. not doing any
> relationship mamangement in the background.
>
> thanks,
> -marina
> [Message sent by forum member 'mvatkina' (mvatkina)]
>
> http://forums.java.net/jive/thread.jspa?messageID=234770
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>
--
View this message in context: http://www.nabble.com/OneToMany-Web-Service-END_ELEMENT-vs-START_ELEMENT-tf4409709.html#a12608522
Sent from the java.net - glassfish users mailing list archive at Nabble.com.