tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JimOR <>
Subject Enhancer annoyance
Date Tue, 13 May 2008 18:23:42 GMT

I'm running into a mild annoyance running a junit test suite directly from
within Eclipse.  I have the -javaagent VM arg in my run configuration, and
the problem does goes away if I run an ant task to call the enhancer
directly prior to running my test suite.

The problem is that access to any collection from the first Entity listed as
'subclassed' gives an NPE, which in my configuration is a failure.  The
remaining Entities test fine, and you'll notice that the enhancer happily
processes that Entity after reporting it being subclassed.

As I stated, it's a mild annoyance because when any tests fail, I only have
to launch that ant enhancer task and re-run the test.  Any thoughts?
following is a portion of my test suite output:

InitialTestSetup Started
Apache OpenEJB 3.0    build: 20080408-04:13
656  PortfolioData  INFO   [main] openjpa.Runtime - Starting OpenJPA 1.0.1
1250  PortfolioData  INFO   [main] openjpa.jdbc.JDBC - Using dictionary
class "org.apache.openjpa.jdbc.sql.PostgresDictionary" (PostgreSQL 8.1.4
,PostgreSQL Native Driver PostgreSQL 8.1 JDBC3 with SSL (build 405)).
1625  PortfolioData  INFO   [main] openjpa.Enhance - Creating subclass for
"[class, class, class,
class]". This means that your application will
be less efficient and will consume more memory than it would if you ran the
OpenJPA enhancer. Additionally, lazy loading will not be available for
one-to-one and many-to-one persistent attributes in types using field
access; they will be loaded eagerly instead.
2578  PortfolioData  TRACE  [main] openjpa.Enhance - Enhancing type "class".
2938  PortfolioData  TRACE  [main] openjpa.Enhance - Enhancing type "class".
3328  PortfolioData  TRACE  [main] openjpa.Enhance - Enhancing type "class".
3594  PortfolioData  TRACE  [main] openjpa.Enhance - Enhancing type "class".
 INFO- -
Context is Set, ejb in Context:
 INFO- -
Framework initialization and bean lookup took 8.844
View this message in context:
Sent from the OpenEJB User mailing list archive at

View raw message