myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Wessendorf" <mat...@apache.org>
Subject Re: [Trinidad] Make ExternalContextUtils a public API
Date Thu, 30 Aug 2007 06:56:56 GMT
I am fine w/ it.

On 8/29/07, Scott O'Bryan <darkarena@gmail.com> wrote:
> 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
>


-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org

Mime
View raw message