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

Shane Bryzak (Commented) (JIRA) jira-events at lists.jboss.org
Mon Dec 12 06:36:10 EST 2011

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

Shane Bryzak commented on SEAMREMOTING-44:

This now works correctly in AS7, but I still need the equivalent code for Glassfish.
> 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, 3.1.0.CR1
>         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
>             Fix For: 3.1.0.Final
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list