[
https://issues.apache.org/jira/browse/MYFACES-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909629#comment-17909629
]
Paul Nicolucci commented on MYFACES-4705:
-----------------------------------------
I was the one that back ported a couple of these and I can see the concern in
previous releases. We would want to likely handle some of these changes as
non-default changes using a context parameter to avoid breaking anyone updating
to the latest releases of MyFaces. Alternatively the behaviors have been this
way for awhile and no one has complained so perhaps we wait until someone
requests the change.
> Handle Breaking Changes
> -----------------------
>
> Key: MYFACES-4705
> URL: https://issues.apache.org/jira/browse/MYFACES-4705
> Project: MyFaces Core
> Issue Type: Bug
> Reporter: Volodymyr Siedlecki
> Priority: Major
>
> A number of issues were found when MyFaces was tested against the 4.0 TCK.
> These issues were fixed in MyFace 4.0 and then back-ported to earlier
> releases.
> However, upon looking at these again, they introduce some breaking changes.
> I think they may require some more conversation.
> This list includes:
> - https://issues.apache.org/jira/browse/MYFACES-4559 (ArtifactProducer change)
> - https://issues.apache.org/jira/browse/MYFACES-4500 (new
> IllegalStateException in ajax requests)
> - https://issues.apache.org/jira/browse/MYFACES-4495
> (subscribeToEvent, publishEvent, unsubscibeFromEvent don’t throw NPEs when
> specified by the JavaDoc)
> I've revert these in 2.2, 2.3, and 3.0 for now so we can discuss a proper
> plan forward.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
