I don't agree with this implementation. It doesn't leave any room
for customization through MappingDefaults, it ties the ClassMapping
to the XMLSchemaParser (?!), and it's totally different than our
mapping of indexes, foreign keys, and primary keys, the other
supported constraint types.
Can you file a JIRA report for the time being? Nothing immediately
suspicious jumps out at me in the stack trace, but I am still fairly
confident that this has something to do with our special blob
handling in Oracle.
On Jan 3, 2007, at 10:14 AM, Kevin Sutter wrote:
Marc,
Dain-
Note that in many cases, we track the thread's context class loader,
but only use it as an auxiliary loader to check when searching for
classes: typically, class loading will go happen via the
Configuration's getClassResolverInstance().
That isn't to say that there aren't potential
Don,
One clarification...
On 1/1/07, Don Brady [EMAIL PROTECTED] wrote:
This is under WebSphere 6.1.
Are you attempting to use OpenJPA with standard WebSphere 6.1 (ala the
DeveloperWorks article that Roland and I wrote --
Hi all,
I've been fighting for some time now with my OpenJPA configuration and just
discovered why. It seems that you *either* consider the persistence.xml file
*or* the map passed as parameter of Persistence.createEntityManagerFactory.
If you look at PersistenceProductDerivation.load(String
I've been fighting for some time now with my OpenJPA configuration
and just
discovered why. It seems that you *either* consider the
persistence.xml file
*or* the map passed as parameter of
Persistence.createEntityManagerFactory.
If you look at PersistenceProductDerivation.load(String rsrc,
Sorry I've jumped too quickly to conclusions. The mistake was mine.
However I'm trying to initialize OpenJPA programmatically using the
following code:
HashMap propMap = new HashMap();
propMap.put(openjpa.ManagedRuntime, new TxMgrProvider(_txMgr));
Matthieu-
Can you send the complete stack trace?
Also, I don't think this is the cause of the problem, but why are you
specifying both ConnectionDriverName and ConnectionFactory? With
ConnectionFactory specified, you shouldn't need to specify the
ConnectionDriverName.
On Jan 3, 2007,
But if I don't provide openjpa.ConnectionDriverName the call to
createEntityManager fails with an exception saying that ConnectionDriverName
should be provided (coming from DataSourceFactory):
4|true|0.9.6-incubating-SNAPSHOT
org.apache.openjpa.persistence.ArgumentException: A JDBC Driver or
Right. Sorry about that. Even though my ConnectionDriverName is still not
properly picked up:
ERROR - ApplicationContext.log(675) | StandardWrapper.Throwable
4|true|0.9.6-incubating-SNAPSHOT
org.apache.openjpa.persistence.ArgumentException: A JDBC Driver or
DataSource class name must be
My ultimate goal is to provide directly an instance of DataSource that
OpenJPA would use instead of trying to lookup or create one. It seems that
it's possible by setting ConnectionFactory to the datasource instance but
OpenJPA fails before that if no ConnectionDriverName is specified.
Abe is
[
https://issues.apache.org/jira/browse/OPENJPA-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462082
]
Kevin Sutter commented on OPENJPA-95:
-
I just attached the three files (Agent, Guid, and ManagedElement) used to
I'm able to reproduce the ConnectionDriverName problem. I'll have
more info in a bit.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and
Cool! I've tried to set openjpa.Log but like all other properties it doesn't
get considered by the entity manager. It's just like my whole Map gets
ignored. I'm also setting the DBDictionary but it also gets ignored as I get
the dictionary auto-detection message...
Something else I can do to
OK, the problem is that we're only paying attention to openjpa.*
property keys with String values when you bootstrap through
Persistence. I have no idea why, and I'll change it momentarily.
But for now, you can work around the problem for your DataSource
using the
OK, the problem is that we're only paying attention to openjpa.*
property keys with String values when you bootstrap through
Persistence. I have no idea why, and I'll change it momentarily.
Actually I now see why, and I might not be able to fix it before I
leave work today. For anyone
I'm still having the same problem (it can't find my ConnectionDriverName
property). Now my code looks like:
HashMap propMap = new HashMap();
propMap.put(openjpa.jdbc.DBDictionary,
org.apache.openjpa.jdbc.sql.DerbyDictionary);
propMap.put(openjpa.ManagedRuntime,
17 matches
Mail list logo
