Nobody else has the problem ?
Somebody could reply to me ?
I came across the same issue, it seems to be an old bug, since a Jira has been openned on it 2 years ago.
I could work around the problem by putting an absolute file name in the persistence.xml <jar-file> subelement. Just a temporary solution of course.
I read the source of the interpretation of the <jar-file> tag and I found a tip which works with JBoss 4.2.1 :
to put a relative path, put "../" only in the beginning of the path and next put "..\" as many as you need, so for me, it is :
But I think that it will not work anymore with JBoss 5.0 but no problem with that, when it will be available, we will change the persistence.xml only for JBoss 5.0 and normally <jar-file>../../entities.jar</jar-file> will work with JBoss 5.0.
Hello, I am with the same problem in JBOSS 5. Just worked putting the the path absolute (C:JBOSS_HOME/server/default/deploy)
is or bug?