[seam-issues] [JBoss JIRA] Commented: (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7

[Shane Bryzak (JIRA)]

    [ https://issues.jboss.org/browse/SEAMREMOTING-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624891#comment-12624891 ] 

Shane Bryzak commented on SEAMREMOTING-44:
------------------------------------------

To clarify, I'll take care of the issue in AS7, but I need someone to do some debugging in Glassfish to determine which internal class they use to represent the collection, and the method to invoke to determine whether it is initialized.

> Remoting Model API lazy fields initialized automatically on Glassfish and AS7
> -----------------------------------------------------------------------------
>
>                 Key: SEAMREMOTING-44
>                 URL: https://issues.jboss.org/browse/SEAMREMOTING-44
>             Project: Seam Remoting
>          Issue Type: Bug
>    Affects Versions: 3.0.0.Final
>         Environment: seam remoting 3.0.1-SNAPSHOT, glassfish 3.1.1.b12 with default persistence provider (eclipselink) || jboss-as-7.1.0.Alpha1-SNAPSHOT with default persistence provider (hibernate 4)
>            Reporter: Marek Schmidt
>            Assignee: Shane Bryzak
>
> Lazy fields, such as
> {noformat}
> @OneToMany(fetch = FetchType.LAZY, mappedBy = "person",
>             cascade = CascadeType.ALL, orphanRemoval = true)
>     public Collection<Address> getAddresses() {
>         return addresses;
>     }
> {noformat}
> are loaded automatically in the model on AS7 and Glassfish. On JBoss AS 6, the field is works correctly and is undefined unless explicitly expanded.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira