ader if we can't find the class on the property's
classloader.
[1]
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ejbfep.multiplatform.doc/info/ae/ae/tejb_jpa3rdparty.html
Regards
-mike
On Thu, Oct 30, 2008 at 10:53 AM, Jan Dockx <[EMAI
d.
Kevin
On Thu, Oct 30, 2008 at 6:17 PM, Jan Dockx <[EMAIL PROTECTED]> wrote:
Hello mike. Thanks for the response.
Your suggestion sounds like a path to investigate. Quick question
though:
how will WebSphere know to inject an EntityManager of the "third
party
persistence pro
der or
the entity's classloader if we can't find the class on the property's
classloader.
[1]
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ejbfep.multiplatform.doc/info/ae/ae/tejb_jpa3rdparty.html
Regards
-mike
On Thu, Oct 30, 2008 at 10
We are working with ValueHandlers for enterprise applications that
will be deployed on WebSphere, currently 6.1.0.19. We believe that the
current OpenJPA implementation has made a less than stellar choice in
how to load value handlers, and suggest a change. But since this is a
long term sol
We suggest a change in how OpenJPA determines the names to be used for
DB columns when using value handlers that use multiple columns. When a
@Column annotation (or the equivalent in XML) is found for a property
or field that is handled by a value handler, the name passed to the
map() metho
