[keycloak-dev] JPA issue on AS 7.1.1.Final

[Marek Posolda]

Had a chat with Anil and Pedro about this. Seems to me that beans.xml 
are not needed inside api and simple-schema picketlink modules as those 
are not using cdi or weld stuff. Will propose them PR once I 
successfully run their integration tests with beans.xml removed.

Next PL version is planned to be released in August and among other 
things, it has also some Active Directory fixes, which I needed to 
workaround in keycloak code. Actually have a branch where I am testing 
AD with picketlink master and things look much cleaner in there. Do you 
think we will be able to update to latest picketlink 2.7. alpha version 
once it's released or do we need to stick with 2.6.5.Final ?

Marek

On 22.7.2014 11:17, Stian Thorgersen wrote:
> Currently master doesn't work on AS 7.1.1.Final (works on EAP 6.2/6.3 and WildFly).
>
> The problem is that Weld tries to load the peristence-unit even though jboss.as.jpa.managed is set to false. Weld is processing the WAR as picketlink-idm-api-2.6.0.CR5.jar and picketlink-idm-simple-schema-2.6.0.CR5.jar include beans.xml. This problem was fixed in 7.1.2.Final (EAP 6.2).
>
> On 7.1.1.Final there seems to be no way to prevent CDI from triggering as all mechanism was added later (exclude-subsystem in jboss-deployment-structure.xml or bean-discovery-mode="none" in beans.xml).
>
> Potential solutions I've found are:
>
> * Get rid of beans.xml in PicketLink jars
> * Remove support for AS 7.1.1.Final (isn't this about time any ways?!)
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev