Public API of PicketLink 2.5 contained in EAP 6.3.0 has changed since PicketLink 2.1 included in previous EAP 6.x versions. Release Notes needs to document these changes or provide a reference to document describing migration from PicketLink 2.1 to 2.5.
According to , org.picketlink is treated as public API, hence customers are allowed to use this API and full support is provided. The changes in the API can render customer applications uncompilable and defunct after EAP upgrade to 6.3.0. Hence this change needs to be documented in sufficient detail.
_Non-exhaustive_ example of the API changes:
* Classes from org.picketlink.identity.federation.core.config package were moved to org.picketlink.config.federation
* Classes from org.picketlink.identity.federation.core.exceptions package were moved to org.picketlink.common.exceptions
* Classes from org.picketlink.identity.federation.core.handler.package config were moved to org.picketlink.config.federation.handler
* Classes Base64 and PBEUtils from org.picketlink.identity.federation.core.util package were moved to org.picketlink.common.util
There might have been other changes as well. Consult the respective developers to check and document all the changes in API that could have impact on customers.
In this BZ ticket's description, Ondrej notes "_Non-exhaustive_ example of the API changes". Is there an authoritative reference of differences between PL 2.1 and 2.5 which I can include in the EAP 6.3.0 Release Notes? We particularly need to highlight any instances where changes may break compatibility.
Russell - Ondrej is correct.
We need move a bunch of internal classes around. The list of packages that were moved is correct.
You can document the packages moved.
They do not affect user applications.
I was not sure of the meaning of Anil's feedback in comment 3, so I asked for clarification via IRC:
<rdickens> asaldhan: do i understand correctly that the list of modules mentioned by Ondrej is the *complete* list of modules which were moved between PL 2.1 and 2.5?
<rdickens> asaldhan: thank you
I have changed the release notes flag as Anil Saldhana has confirmed that these API changes will not affect customer applications already using PicketLink 2.5.
The changes do affect backwards compatibility. Applications using PL 2.1 API do not even compile with 2.5 and their source (at least the imports, maybe more?) needs to be changed. All of these changes need to be documented as PL API is a part of the EAP public API.
Anil, Russell, please provide full list of changes to the Release Notes or note to Rel Notes and full list into more appropriate guide.
Russell, please change the RN text accordingly. It must be stated that the changes are _not_ backwards compatible.
Topic 35798 has been created to contain the API changes and has been added to the content spec for the 6.3.0 Release Notes.
Moving ticket to MODIFIED pending document rebuild.
Moving to POST pending rebuild of the Release Notes.
Update will be available at the below URL (Info will be in an appendix at the end of the document).
In EAP 6.3 Release Notes section 8. API changes between PicketLink versions 2.1 and 2.5, there is wrong package name in the beggining. Change the first package name from "org.picketlink.identity.federation.core.configliteral>" to "org.picketlink.identity.federation.core.config"
Nice catch Filip. Markup goof. I've fixed it now.
A new build of the 6.3.0 Release Notes is available for review at:
When verifying bugs, please ensure you're viewing the latest version of the document (6.3.0-14 or later).
Verified in Revision 6.3.0-14
Moving back to assigned as a tracker (so I don't forget to add this content in the final GA build).
A new version of the Release Notes is available for review at:
(ensure you're reviewing version 6.3.0-17)
Verified in Revision 6.3.0-17