Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] EclipseLink in Glassfish, roundup

This is very odd; I cannot think what could be causing the issue.  Do you get
any errors during deployment?  Try setting logging to finest and see if
anything odd is occurring.

You should not be starting Glassfish with the agent; the weaving should
occur from the EJB 3.0 container contract the same as it did with TopLink
Essentials.  However weaving is not required for lazy collections, so
weaving should not have any effect.  It could have something to do with the
weaving of change tracking, so you could try turning weaving off in your
persistence.xml and see if the issue still occurs.

By the way, does the same application work with TopLink Essentials, or do
you get issues as well?

Could you include the full exception stack trace with the error from M4.

I will try to run our JPA server tests in Glassfish to see if I get the same
issue as you are seeing.

wintermute-3 wrote:
> Hi all,
> ok, so I read some more documentation and gave another try to deploy  
> my Application in Glassfish with EclipseLink.
> With M3, I still have the issue of LAZY collections beeing empty.  
> (They behave normal in TL Essentials, they also return content with  
> FetchType.EAGER set -- only if set to LAZY they return a size of 0,  
> btw. without having been serialized.)
>  From what I understand from the TL documentation, I shouldn't have to  
> care for weaving in an Application Server, so probably I was wrong  
> assuming I had to start the GlassFish VM with a -javaagent parameter.  
> Is this correct?
> Is there anything I could do to find out if the LAZY thing is a  
> Glassfish issue, an EclipseLink problem or some kind of overfitting to  
> TL Essentials from my side? (Only standard JPA involved, but still...)
> With M4, the following Exception happens when deploying the Application:
> Internal Exception: java.lang.UnsupportedOperationException
> 	at  
> org 
> .eclipse 
> .persistence 
> .exceptions 
> .EntityManagerSetupException 
> .predeployFailed(
> 	... 45 more
> Caused by: java.lang.UnsupportedOperationException
> 	at java.util.Collections 
> $UnmodifiableCollection.addAll(
> 	at  
> org 
> .eclipse 
> .persistence 
> .internal 
> .jpa 
> .metadata 
> .MetadataProcessor.initPersistenceUnitClasses( 
> 196)
> What might be going on here?
> rv

--- James Sutherland
 EclipseLink ,
Wiki: Java Persistence , EclipseLink , TopLink 
Forums: TopLink , EclipseLink 
View this message in context:
Sent from the EclipseLink - Users mailing list archive at

Back to the top