]
Tomáš Remeš commented on SEAMREMOTING-44:
-----------------------------------------
still problem also in seam 3.1.0.Beta2. i've tested it on glassfish3.1.1 and
jboss-as-web-7.0.1.Final
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: