[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009307#comment-13009307
]
Alexandr Smirnov commented on PORTLETBRIDGE-189:
------------------------------------------------
JSF FactoryFinder has been created in JRE 1.4 age, therefore it doesn't
leverage JDK 5+ generics. I propose to use more type safe implementation,
similar to the one used in richfaces library:
https://docs.google.com/document/pub?id=1cCoeesqZYcUU4sth53Xhu7eY3Jycb9VSTJLEY7-k0eg
.
The main difference with JSF FactoryFinger is using Factory/Service classes as
the key, that lets Java compiler decide proper return type for the instance.
Also, because Bridge is JSF extension, we can use system events to initialize
and release bridge in the proper place, instead of the first request, to avoid
synchronization problems.
> Proposal for 3.0 API: javax.portlet.faces.BridgeFactoryFinder
> -------------------------------------------------------------
>
> Key: PORTLETBRIDGE-189
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-189
> Project: MyFaces Portlet Bridge
> Issue Type: New Feature
> Components: General
> Affects Versions: 3.0.0
> Reporter: Neil Griffin
> Assignee: Michael Freedman
>
> Discussion of *which* factories can be done in other issues, but I wanted to
> discuss the idea of having a BridgeFactoryFinder in this issue.
> In order to make the bridge more extensible, I would propose a
> javax.portlet.faces.BridgeFactoryFinder based on the same idea found in Faces:
> http://javaserverfaces.java.net/nonav/docs/2.0/javadocs/javax/faces/FactoryFinder.html
> For a prototype of this idea, please refer to the following class in the
> PortletFaces Bridge trunk:
> http://svn.portletfaces.org/svn/portletfaces/bridge/portletfaces-bridge-api/trunk/src/main/java/org/portletfaces/bridge/BridgeFactoryFinder.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
