[jboss-jira] [JBoss JIRA] (WFLY-7521) JPA subsystem does not expose a proper capability contract

[Scott Marlow (JIRA)]

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

Scott Marlow commented on WFLY-7521:
------------------------------------

I wonder if the Weld subsystem can depend on this capability contract or if we need to wait for [https://github.com/wildfly/wildfly/pull/9324] [https://issues.jboss.org/browse/WFLY-6941] to split the Weld subsystem into separate modules.  I don't recall if the Weld subsystem exposes a proper capability contract, so we might need a separate jira for that.  

We also might need a jira [https://issues.jboss.org/projects/CAPEDWARF] for Capedwarf, [~alesj] you might want to follow this.  I'm not sure if Capedwarf exposes capability contracts, which I assume it would need to.  



> JPA subsystem does not expose a proper capability contract
> ----------------------------------------------------------
>
>                 Key: WFLY-7521
>                 URL: https://issues.jboss.org/browse/WFLY-7521
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>            Reporter: Brian Stansberry
>            Assignee: Scott Marlow
>
> Capabilities provided to other subsystems by JPA should be via a contract, and it's uses of other subsystems should be via a contract.
> The latter depends on the other subsystems resolving an issue equivalent to this one, if they haven't already.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)