Hello everyone,
Trinidad has an internal class
(org.apache.myfaces.trinidadinternal.util.ExternalContextUtils) which
contains some convenience methods used throughout Trinidad in order to
handle ExternalContext objects which may be backed by a portal. It is
used especially inside Trinidad's own Configurator framework which is a
public API.
When making my own configurators for the upcoming RichClient incubator
project, and indeed throughout the Richclient code itself, I have found
myself using this internal API because it handles a number of usecases
that are not EASILY handled including working even when the Portal API
is not in the classpath.
As a result, I'm wondering what people would think about promoting this
internal class to our public API?
Scott
- [Trinidad] Make ExternalContextUtils a public API Scott O'Bryan
-