The orm.xml looks like this,
PROPERTY
Entity class is define
Hello Kevin,
I think that the problem comes from the fact I use OpenJPA with Spring and
Spring DM within an OSGi environment. That's the reason for the bundleresource
protocol...
I'd pleased to help you to address this problem! I'll have a look...
Thierry
> Thierry,
> My guess here is that we'
Moving the mysql driver from 5.0.7 to 5.1.8 resolved this issue. Thanks!
But now I have hit the next and more serious hurdle but I will post that as
a new question.
--
View this message in context:
http://n2.nabble.com/MySQLSyntaxErrorException%3A-FUNCTION-XYZ%2C-does-not-exist-tp3356221p33631
Thierry,
My guess here is that we're having a problem with the classloader accessing
the root URL... The type on this URL (bundlesource:) is not what we're
expecting. We're only expecting "file:" or "jar:" for the Root URL type.
But, I know from past postings on our forum, that the use of Spring
Thanks very much Kevin and Jeremy for hints!
I investigate further this aspect and it appears that OpenJPA tries to use
first load time weaver. I see the message in log if the feature isn't available:
openjpa.Runtime - An error occurred while registering a ClassTransformer with
PersistenceUnit
Thanks for the hint, Kevin!
Thierry
> Just a heads up... Do not rely on the default value for unlisted-classes/>. In JPA 1.0, this element was defined incorrectly.
> The default value was set to "false". Thus, the classes/> element, if typed just like this, would indicate "not to
> exclu
On Fri, Jul 31, 2009 at 4:54 AM, Thierry Templier wrote:
>
> Hello,
>
> I fixed my problem by adding the parameter in
> my persistent.xml file to desactivate auto detecting.
Just a heads up... Do not rely on the default value
for . In JPA 1.0, this element was defined
incorrectly. The defau
Hi Thierry,
I did not see this in the blog post that Kevin referred to, but it may be
helpful as well. You can explicitly turn off
OpenJPA's subclassing-based enhancement by specifying this option in your
persistence.xml:
If your app is configured properly, classes (which are not pre
Thierry,
I would first reference this blog posting [1] on our Enhancement processing
(load time weaving) and see if that helps answer your questions. Or, at
least it should help narrow the scope of the question...
Thanks,
Kevin
[1]
http://webspherepersistence.blogspot.com/2009/02/openjpa-enhance
Hello,
I fixed my problem by adding the parameter in my
persistent.xml file to desactivate auto detecting.
Thierry
> Hello,
>
> I'm trying to use OpenJPA 1.1.0 with the Spring JPA support
> within an OSGi environment.
>
> Here is my Spring configuration:
>
> class="org.springframework.orm
Hello,
I'm using OpenJPA 1.1.0 and I wonder if it's possible to explicitly specify
that we want to load time weaving.
Thanks for your help,
Thierry
Hello,
I'm trying to use OpenJPA 1.1.0 with the Spring JPA support within an OSGi
environment.
Here is my Spring configuration:
I have a strange problem when trying to use the entity manager:
Could not open JPA
12 matches
Mail list logo