[
https://issues.apache.org/jira/browse/MYFACES-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921809#comment-17921809
]
Volodymyr Siedlecki commented on MYFACES-4705:
----------------------------------------------
I think MYFACES-4495 is safe to add back in. The others no so much.
MYFACES-4524 - TCK fails. I created a challenge, but I don't think a new EE8
TCK release will be out any time.
MYFACES-4559 - Breaking change as we're using a new object.
MYFACES-4500 - Breaking change as it's an new exception.
I agree with Paul about waiting until some one brings them up. I'd prefer to
not add more context parameters. Alternatively, users can upgrade to 4.0 where
these are fixed.
> Handle Breaking Changes
> -----------------------
>
> Key: MYFACES-4705
> URL: https://issues.apache.org/jira/browse/MYFACES-4705
> Project: MyFaces Core
> Issue Type: Bug
> Reporter: Volodymyr Siedlecki
> Assignee: 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)
> - https://issues.apache.org/jira/browse/MYFACES-4524 (resource handling)
> 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)
