openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florent BENOIT (JIRA)" <>
Subject [jira] Created: (OPENJPA-148) Parsing exception while using an "exploded" archive
Date Wed, 14 Feb 2007 21:46:05 GMT
Parsing exception while using an "exploded" archive

                 Key: OPENJPA-148
             Project: OpenJPA
          Issue Type: Bug
          Components: jpa
         Environment: Sun JDK 5.0 / EasyBeans / OpenJPA snapshot 0.9.7
            Reporter: Florent BENOIT

This happens when using OpenJPA as persistence provider for the EasyBeans ObjectWeb container.
The error is happening with "exploded" archive.
Exploded means that there is a directory, named "entitybean.jar" with a folder META-INF which
contains a file named persistence.xml, and other directories/files for the classes.

It seems that when using this mode, OpenJPA is trying to parse the directory inputstream (which
is failing).
This exception is not occuring if a jar file is used instead of the "exploded" mode, but the
exploded mode is the default mode for EasyBeans.
Note also that this exception don't occur by using Hibernate Entity Manager or Oracle TopLink
Essentials as persistence provider.

I will attach to this issue a stack trace (with the exploded directory) which fails and at
the end with a jar file (which work)
And 4 steps used to reproduce this problem

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message