Isn't this essentially why the "bundle" attribute was added to the
<bean:message> tag? That would seem to solve the problem, although I guess
it means you'd have to add that attribute to all your <bean:message> instances.
--
Martin Cooper
Tumbleweed Communications
At 09:41 AM 2/16/01 -0600, Craig Tataryn wrote:
>But technically couldn't the application developer do this already? They
>could just add another init-param to the Servlet which specified a
>Resources class other than the default. The servlet writter would simply
>use this resource bundle instead, getting it's messages from there.
>
>You could have something like UIResource and ServletResource classes. The
>UIResource class would be the one you set in the ActionServlet's
>application init-param, and the ServletResource class can be loaded
>programatically by the servlet writter based on some custom init-param
>which specified the class name.
>
>Craig T.
>
>Rob Leland wrote:
>
> > Roland Huss wrote:
> > >
> > > Hi,
> > >
> > > for some reasons I would like to separate messages put into JSP-pages
> > > with <bean:message> from messages generated within java
> > > code.
> > +1
> > This sounds like a good Idea. I would vote for this change.
> > Maybe you could post it to the bug/feature request so it
> > ends up one the list for version 1.1.
> >
> > -Rob
>
>--
>I've been trying to change the world for years, but they just won't give me
>the source code....
>
>
