[JBoss JIRA] Created: (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7
4:59 p.m.
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
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
4:59 p.m.
New subject: [JBoss JIRA] Assigned: (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7
[
https://issues.jboss.org/browse/SEAMREMOTING-44?page=com.atlassian.jira.p...
]
Marek Schmidt reassigned SEAMREMOTING-44:
-----------------------------------------
Assignee: Shane Bryzak
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
4:40 p.m.
New subject: [JBoss JIRA] Commented: (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7
[
https://issues.jboss.org/browse/SEAMREMOTING-44?page=com.atlassian.jira.p...
]
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: http://www.atlassian.com/software/jira
6:02 a.m.
New subject: [JBoss JIRA] Commented: (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7
[
https://issues.jboss.org/browse/SEAMREMOTING-44?page=com.atlassian.jira.p...
]
Shane Bryzak commented on SEAMREMOTING-44:
------------------------------------------
I'm guessing that the issue is because of the following block of code in BagWrapper:
try {
Class<?> cls =
Class.forName("org.hibernate.collection.PersistentCollection");
// Fix to prevent uninitialized lazy loading in Hibernate
if (cls.isInstance(value) && !loadLazy) {
try {
Method m = cls.getMethod("wasInitialized");
if (((Boolean) m.invoke(value)).booleanValue() == false) {
out.write(UNDEFINED_TAG);
return;
}
} catch (NoSuchMethodException ex) {
} catch (InvocationTargetException ex) {
} catch (IllegalAccessException ex) {
}
}
} catch (ClassNotFoundException ex) {
}
I'm going to need some assistance with this - specifically, the equivalent code that
works in Glassfish which will determine whether the field is a persistent collection and
whether it has been initialized or not.
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
6:02 a.m.
New subject: [JBoss JIRA] Commented: (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7
[
https://issues.jboss.org/browse/SEAMREMOTING-44?page=com.atlassian.jira.p...
]
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
1:03 p.m.
New subject: [JBoss JIRA] (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7
[
https://issues.jboss.org/browse/SEAMREMOTING-44?page=com.atlassian.jira.p...
]
Tomas Remes updated SEAMREMOTING-44:
------------------------------------
Fix Version/s: 3.1.0.Final
Affects Version/s: 3.1.0.CR1
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
12:36 p.m.
New subject: [JBoss JIRA] (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7
[
https://issues.jboss.org/browse/SEAMREMOTING-44?page=com.atlassian.jira.p...
]
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
6:14 a.m.
New subject: [JBoss JIRA] (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7
[
https://issues.jboss.org/browse/SEAMREMOTING-44?page=com.atlassian.jira.p...
]
Jason Porter resolved SEAMREMOTING-44.
--------------------------------------
Resolution: Done
Fixed the glassfish side
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
4581
days inactive
4706
days old
7 comments
6 participants
participants (6)
-
Jason Porter (Resolved) (JIRA) -
Marek Schmidt (JIRA)
-
Shane Bryzak (Commented) (JIRA)
-
Shane Bryzak (JIRA)
-
Tomas Remes (Updated) (JIRA)
-
Tomáš Remeš (JIRA)