[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[eclipselink-users] Eclipselink 1.0.1 + Spring on GFV2UR2 - other issues (Toplink Essentials)
|
Apart from the META-INF/orm.xml not being spotted correctly in this (Spring enabled) setup.
I also see something strange happening during deployment, which points to Toplink Essentials
getting in the way of EclipseLink 1.0.1. Somewhere in the log (during deployment) the following
line is written:
[#|2008-10-20T07:56:24.778+0200|WARNING|sun-appserver9.1|oracle.toplink.essentials.session.file:/home/jvissers/Work/containers/glassfish-v2ur2/
glassfish/domains/domain1/applications/j2ee-modules/cumquat-brandportal-services/WEB-INF/classes/-image-bank.ejb_or_metadata|_ThreadID=17;_ThreadName=Thread-35;
_RequestID=7f3d2c87-9073-4486-8bc0-a082f58af64e;|Ignoring LAZY fetch type on element [private byte[] com.cumquatit.brandportal.domain.model.imagebank.ImageData.data]
within entity class [class com.cumquatit.brandportal.domain.model.imagebank.ImageData]. All basic mappings default to use EAGER fetching.|#]
Apparently Toplink Essentials is 'doing something' along with the deployment. I want to use EclipseLink 1.0.1 -
so how do I stop this from happening?
-J
