You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Erik Hatcher <er...@ehatchersolutions.com> on 2005/03/24 01:20:54 UTC

EngineMessages scope

Is the 3.1 EngineMessages class intentionally packaged scoped?  For 
custom services, it'd be handy to have its utility methods available.

Mind if I make it public?

Thanks,
	Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Re: EngineMessages scope

Posted by Howard Lewis Ship <hl...@gmail.com>.
It is intentionally package private, but it is not a problem to make
it more visible. However, the point of the XXXMessages classes, as
wrappers around .properties files, it to manage acess to the messages
in the .properties files, so that we can see if each message is used,
and by who ... basically, so that we can refactor localilzed messages.

If the class becomes public, just make all the individual methods
package private, except for the ones you need to expose more widely.


On Wed, 23 Mar 2005 19:20:54 -0500, Erik Hatcher
<er...@ehatchersolutions.com> wrote:
> Is the 3.1 EngineMessages class intentionally packaged scoped?  For
> custom services, it'd be handy to have its utility methods available.
> 
> Mind if I make it public?
> 
> Thanks,
>         Erik
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> 
> 


-- 
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org