|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Hi,
Are you using the subsystem from the installer ?
If so, here is some status about the subsystem. Recently, we got the subsystem in both EAP and WildFly. What means we're not shipping the subsystem as a separated jar anymore. We'll probably get EAP 6.3 and WildFly 9 fully integrated with PL 2.6.0.CR1+. That is the good news.
In your case, I would suggest to keep Beta3 or avoid using the subsystem until the next version for EAP. Sorry for that, but this is an important step to get PL fully integrated into EAP and make life easier for everybody.
The error you're getting is because the subsystem is not considering one of the changes we did to the PicketLink Configuration API to better support the JPA store in EAP and WildFly.
Thanks.