[CXF-7586] cxf-rt-rs-security-oauth2 preventing application on JBoss from starting if more than 1 PU defined

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.0, 3.2.1
• Fix Version/s: 3.2.2
• Component/s: JAX-RS Security
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Olivier Paquet
• Created: 12/Dec/17 09:36
• Updated: 07/Feb/18 14:51
• Resolved: 13/Dec/17 14:35

Description

Hi,

We noticed after switchting from cxf 3.1.7 to 3.2.x that our application is not starting anymore.
After some analysis we found out that the cxf module cxf-rt-rs-security-oauth2 contains a class org.apache.cxf.rs.security.oauth2.grants.code.JPACMTCodeDataProvider which injects an EntityManager using @PersistenceContext without defining a unitName. On our JBoss 6.4 EAP (JBoss 7.x) we get the following error message:

java.lang.IllegalArgumentException: JBAS011470: Persistence unitName was not specified and there are x persistence unit definitions in application deployment deployment

With only one persistence unit definition it's working, but we need multiple PU's.

One solution I have in mind is to define a unitName for the PersistenceContext on the org.apache.cxf.rs.security.oauth2.grants.code.JPACMTCodeDataProvider ("CXF_PU") , so that a PU has to be define explicitly in the persistence.xml, I mean it's not nice but for us it would be ok.

Or perhaps there are other macanisms to avoid the persistence context injection if this class is not used?

It currently prevents us from switchting to the newest cxf version.

I attached a sample maven project to reproduce this issue on a JBoss 7.x .

Greetings, Olivier

Issue Links

• links to: GitHub Pull Request #357