[
https://issues.apache.org/jira/browse/MYFACES-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996947#comment-12996947
]
David Jencks commented on MYFACES-2995:
---------------------------------------
Since it's been about 2 1/2 months before this issue was really responded to
I'd appreciate a few days to review your patch before you commit it. At the
moment I don't understand how a per-ear object could possibly be of any use.
IMO depending on the app server either a classloader based strategy as is used
at present will work fine or the app server will need to use something else for
every ear. There is little chance that one app server will use different
classloading strategies for different ears and want to therefore use different
code to distinguish jsf contexts for different ears.
However I may have misunderstood your comments as I have not yet had a chance
to look at your patch.
> Make method of determinine app context in FactoryFinder pluggable
> -----------------------------------------------------------------
>
> Key: MYFACES-2995
> URL: https://issues.apache.org/jira/browse/MYFACES-2995
> Project: MyFaces Core
> Issue Type: Improvement
> Components: SPI
> Affects Versions: 2.0.3-SNAPSHOT
> Reporter: David Jencks
> Attachments: MYFACES-2995-FactoryFinderProvider-1.patch,
> MYFACES-2995.patch
>
>
> As discussed on dev list.... geronimo would like to explicitly mark component
> boundaries rather than relying on the TCCL changing.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
