Hi,
A couple of weeks ago Marc made a good suggestion on IRC that it would
be nice to have the OpenJPA Maven plugin not to be dependent on any
specific version of OpenJPA library.
I removed the compile time dependency but cannot drop it altogether
since the plugin's unit test (link below),
[
https://issues.apache.org/jira/browse/OPENJPA-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496016
]
Abe White commented on OPENJPA-238:
---
Custom id classes can have either a (Class,String) or just a String
Murali,
This is probably a question for the application server (jboss in your case)
rather than the jpa provider (openjpa). The binding of an
EntityManagerFactory into jndi is an application server (ie. container)
process, not a jpa provider process. (The same thing goes for your
datasource
Folks,
I am exploring the idea of using OpenJPA internal APIs to obtain
meta-data from a persistence unit (e.g. JAR) for use in custom
code generation.
Since I'm a bit of a newbie to OpenJPA, it would be helpful if
someone could give me some starting pointers to save me a little
time.
Suppose I
Probably you should look at the AuxiliaryEnhancer in the PCEnhancer
class -- it gives you some hooks for doing further processing during
the OpenJPA enhancement process.
From there, you should look at ClassMetaData and MetaDataRepository.
That's got references to pretty much everything else
