|
||||||||
|
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 |
||||||||
Yes, I was using the PicketLink installer 1.3.0 to install the subsystem JARs. One of them was missing – pickelink-as-extension-1.2.2.Final.jar – so EAP failed to startup with that extension declared. I was able to add that module and startup progressed with no problem.
This is a pretty big issue for us, as we're using PicketLink for all of our security functionality in our app, and are using the subsystem in all of our appservers. We'd begun developing our newest code against the 2.6.x branch, so this will affect us in a pretty big way.
Any date on EAP 6.3's release?