You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jeremy Hughes (JIRA)" <ji...@apache.org> on 2011/02/04 17:44:29 UTC
[jira] Updated: (ARIES-523) Misleading message from
PersistenceBundleHelper
[ https://issues.apache.org/jira/browse/ARIES-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes updated ARIES-523:
--------------------------------
Fix Version/s: (was: 0.3)
This wasn't fixed in 0.3 so I've removed the fixVersion 0.3
> Misleading message from PersistenceBundleHelper
> -----------------------------------------------
>
> Key: ARIES-523
> URL: https://issues.apache.org/jira/browse/ARIES-523
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: 0.3
> Reporter: Holly Cummins
> Priority: Trivial
>
> I regularly see messages like the following:
> [12/21/10 14:53:44:559 GMT] 00000017 container I org.apache.aries.jpa.container.impl.PersistenceBundleHelper findPersistenceXmlFiles The bundle [...] specifies both the Web-ContextPath header, but it does not specify the Meta-Persistence header. This bundle will be scanned for persistence descriptors in any locations defined by the JPA specificationthat are on the Classpath.
> [12/21/10 14:53:44:561 GMT] 00000017 container W org.apache.aries.jpa.container.impl.PersistenceBundleHelper findPersistenceXmlFiles The bundle [...]_1.0.0 specified the Meta-Persistence header. However, no persistence descriptors could be located. The following locations were searched: [WEB-INF/classes/META-INF/persistence.xml]
> This has a few problems:
> Is it telling me the Meta-Persistence header is present, or not? The first message says it's missing, the second says it's present. (In fact, there's Web-ContextPath: header but not a Meta-Persistence: header, so the second message is just wrong.)
> "specifies both the Web-ContextPath header, but it does not specify the" isn't grammatical. The "both" should be dropped.
> "specificationthat" needs a space in it.
> It took me a while to work out that it didn't *really* mean I needed to put the JPA specification on the classpath.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira