[
http://jira.jboss.com/jira/browse/EJBTHREE-560?page=all ]
Gregory Nolle updated EJBTHREE-560:
-----------------------------------
Attachment: PersistenceUnitDeployment.diff
I came up against this problem as well. It's also mentioned in the forum here with
some other symptoms:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=87057.
I've attached a patch that fixes the problem. It seems that the original code tries to
perform relative path resolution manually which seems rather pointless considering that
this functionality is built into java.net.URL itself.
CLONE -Referencing JAR file in persistence.xml - Still a bug and
referenced duplicate issue does not exist
----------------------------------------------------------------------------------------------------------
Key: EJBTHREE-560
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-560
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC1
Reporter: geoffm74
Attachments: PersistenceUnitDeployment.diff
I've installed EJB3.0RC1 and the release notes states that now all persistence.xml
features are implemented. So I went on trying to use the jar file referencing.
Unfortunately I found that during deployment the only place being searched for this jar
file was in JBOSS_HOME/bin. I tried with absolute paths and relative - but it kept hangin
on to the bin folder - probably the working folder for jboss launcher.
My jar is bundled with my ear - where should it really be to get the jar reference
workin? I think the bin folder is not a proper place....
Peter
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira