I *DON'T* like ExternalContext because in a piece of code that uses
both, you'll have to qualify the class with a package name. Never a
good idea in my book. What about something cheezy like MyFacesContext?
Does MyFaces already have a class like this?
Günther wrote:
Hi!
More interesting are class names like AdfFacesContext.
Naming them TrinidadContext might not a good solution.
Note: This class is *not* extending FacesContext.
ExternalContext might be a good name...
but... as we all know, this is already taken :)
What about TrinidadRealm? ;-)
No, but why would ExternalContext be better then TrinidadContext?
Thanx for your patience if this happens to be a stupid question to ask.
Regards,
Thorsten
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Matthias
Wessendorf
Gesendet: Freitag, 14. Juli 2006 23:49
An: [email protected]
Betreff: [Proposal] (re)naming issue
Hey,
since we closed ADFFACES-4 it is now time to start the renaming of the
packages, since ADF is a no no.
ADF-FACES-API
package
from
org.apache.myfaces.adf.**
to
org.apache.myfaces.trinidad.**
ADF-FACES-IMPL
package
from
org.apache.myfaces.adfinternal.**
to
org.apache.myfaces.trinidad.internal.**
(note trinidad DOT internal)
More interesting are class names like AdfFacesContext.
Naming them TrinidadContext might not a good solution.
Note: This class is *not* extending FacesContext.
ExternalContext might be a good name...
but... as we all know, this is already taken :)
Any ideas?
