[jboss-jira] [JBoss JIRA] (AS7-4873) Strict location check of persistence.xml deployments

[Scott Marlow (JIRA)]

    [ https://issues.jboss.org/browse/AS7-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695118#comment-12695118 ] 

Scott Marlow commented on AS7-4873:
-----------------------------------

I think its a good idea to tighten down the location check and also include checking for common "wrong" locations also.

I agree that doing this in 7.2.0 is the right version to make this change.
                
> Strict location check of persistence.xml deployments
> ----------------------------------------------------
>
>                 Key: AS7-4873
>                 URL: https://issues.jboss.org/browse/AS7-4873
>             Project: Application Server 7
>          Issue Type: Enhancement
>          Components: JPA / Hibernate
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Bartosz Baranowski
>            Assignee: Scott Marlow
>            Priority: Minor
>             Fix For: 7.2.0.Alpha1
>
>
> As of: https://github.com/jbossas/jboss-as/commit/38815193011fba624170a7d938118ee630b6ccb2 it is possible to deploy persistence.xml from invalid location:
> As per JPA spec(https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide), valid locations are:
>  - an EJB-JAR file
>  - the WEB-INF/classes directory of a WAR file
>  - a jar file in the WEB-INF/lib directory of a WAR file
>  - a jar file in the EAR library directory
>  - an application client jar file

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira