On 1/24/06, Dave Newton <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Surely they thought about this and decided there was some reason not to
> > make the constants available in the tags. Or was it just too difficult a
> > task for some finite period of development time?
> >
<snip/>
Probably not the right forum to ask.
> Well, I'm not sure how you'd differentiate between a named, scoped bean
> and a fully-specified class name except by checking for a named, scoped
> bean and if that fails looking up a class definition. You could add a
> parameter to tags, but that wouldn't help for JSP 2.0 non-tag EL
> expressions. Maybe by declaring a package name somewhere you could
> finagle a way around it, but still seems warty.
>
<snap/>
package constants;
public class Foo {
public static final String BAR = "bar";
//...
}
elsewhere, in a JSP 2.0 page:
<jsp:useBean id="foo" class="constants.Foo" />
${foo.BAR} <%-- Line of interest --%>
The issue I quoted earlier says the above line should have the *desired* effect.
-Rahul
>
> Dave
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
