Hi Brian,
The ServiceTracker concept was first proposed by Alexandr Smirnov [1] when we were thinking about doing a BridgeFactoryFinder similar to the one found in the JSF API [2]. I recommend that everyone on JSR 344 take a look at Alexander's post.
The JSR-329-NEXT folks (Mike Freedman, Ken Finnigan, and myself) thought that if the ServiceTracker concept were part of JSF 2.2, then we could simply utilize it within JSF 2.2 compatible bridge implementations.
Best Regards,
Neil
[1]
https://issues.apache.org/jira/browse/PORTLETBRIDGE-189?focusedCommentId=13009307&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13009307
[2]
http://javaserverfaces.java.net/nonav/docs/2.0/javadocs/javax/faces/FactoryFinder.html
On Jan 10, 2012, at 4:18 PM, Brian Leathem wrote:
> Hello experts,
>
> I've been approached by Ken Finnigan (Red Hat, Portal bridge lead), Micheal Freedman (Oracle, JSF 344 expert), and Neil Griffin (Liferay, JSR 344 expert) on including the service Tracker code from RichFaces to JSF 2.2. We would very much like to see this contribution take place, however portals are not something I am familiar with, so it's not clear to me how to proceed.
>
> Michael, Neil, could either of you explain to the group why this wold be a good contribution to the JSF specification?
>
> Regards,
> Brian Leathem
> Red Hat (RichFaces Project Lead)