Hello,
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
Isn't this essentially why the "bundle" attribute was added to the
tag? That would seem to solve the problem, although I guess
it means you'd have to add that attribute to all your instances.
--
Martin Cooper
Tumbleweed Communications
At 09:41 AM 2/16/01 -0600, Craig Tataryn wrote:
>But tec
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
Roland Huss wrote:
>
> Hi,
>
> for some reasons I would like to separate messages put into JSP-pages
> with 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
Hi,
for some reasons I would like to separate messages put into JSP-pages
with from messages generated within java
code. I.e. packaging your application as jar file and still give
designers a change to customize messages (without touching the jars)
seems to be a good idea (at least for me ;-)
