Here is the output from build-time enhancer.
Buildfile: build.xml
enhance:
[openjpac] 463 UserAdminTestCase WARN [main] openjpa.MetaData - No
setter was found for method new in type
com.example.model.impl.UserModelBaseImpl while searching for persistent
properties. This method will be ignor
In the javadoc there are many event and listener.I want to use the event and
the listener in jee enviroment,the emf.add**Listener() method can't not
called because in jee enviroment the entitymanagerfacetory is created by jee
contianer.i only use ejb3 injection in my session bean use
@Persistenc
Kevin Sutter wrote:
>
>
> Claudio Di Vita wrote:
>>
>> I turned on all TRACE messages, but I cannot see any exception. The SQL
>> is
>> generated for all records, but I cannot see them as rows in tables.
>>
>
> Interesting. We don't generate and log the SQL until it's ready to be
> sent
>
Craig L Russell wrote:
Database users are notorious for wanting stability, even if it means
running back-level releases. Somehow they manage to coerce vendors into
supporting them on their running systems.
To get an accurate idea of our users' requirements, perhaps we need to
include users@
On Thu, 06 Aug 2009 10:11:48 -0400
Donald Woods wrote:
> > But it's also clear that OpenJPA 2.0 will require Java 6. So I have
> > no issues with making the switch for 2.0.
>
> Agree. I'd like us to require Java SE 6 for build and runtime.
Agree.
>
> >
> > But is it a problem staying with
+1
Java 5 for 1.0.x and 1.3.x
Java 6 for 2.x
I think this could better for OpenJPA adoption.
Concerning my own usage, I'm no more using Java 5 ... so I would be
pleased with everything Java 6.
On Aug 6, 2009, at 16:11 , Donald Woods wrote:
Craig L Russell wrote:
Database users are notori
I have an entity A with a to-many relation to entity B. If entity A is
retrieved from the database, and entity B is found in the cache, the inverse
field from entity B to entity A is null.
StoreCollectionFieldStrategy.processEagerParallelResult() is setting a
"mapped by" field in the result object
Illhan -
In your application initialization I believe you could do something like
this to get a reference to the EntityManagerFactory
OpenJPAEntityManager oem = OpenJPAPersistence.cast(em);
OpenJPAEntityManagerFactory oemf =
OpenJPAPersistence.cast(oem.getEntit
Yu Wang -
OPENJPA-1089[1] wasn't your exact problem, but I want you to be aware that a
change was made.
Thanks -
Rick
[1] https://issues.apache.org/jira/browse/OPENJPA-1089
--
View this message in context:
http://n2.nabble.com/How-to-encrypt-DB-password-in-persistence.xml-tp2868212p3400811.h
Rick,
Thank you for your information. I have resolved this issue by
modifying dbcp source code.
The bad part is dbcp can be built with jdk 1.4 only which made build
system little bit complicated:-)
If you can deliver encryption feature in next release, I'll be very
pleased to use it.
Regards,
Yu
10 matches
Mail list logo
