This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes JSP and the fly likes String literal constants - opinion sought. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » JSP
Bookmark "String literal constants - opinion sought." Watch "String literal constants - opinion sought." New topic
Author

String literal constants - opinion sought.

Jason Pepper
Greenhorn

Joined: Oct 15, 2005
Posts: 9
One of the practices we follow at my workplace is to create a Constants class to store string literals that can be referred to throughout the application.

However, this approach encourages the use of scriptlet code in jsps, instead
of JSTL. For example.

If I have a request parameter foo that is being used all over the app. In the non EL world I would use..

<input type="hidden" name="<%= Constants.PARAM_FOO %>" >

But in JSTL I use

<input type="hidden" name="${param.foo}" >

Notice how the word "foo" is hardcoded in the page now.

We are also encouraging the use of EL and JSTL, but find this in direct
conflict with our old practice of keeping constants in one place.

Is there a way to keep the constants in one place and still use EL?
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61315
    
  66

I addressed an approach to this in an article in the August 2005 JavaRanch Journal.

An article I am currently writing for the December issue of the Journal also will address this topic.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
Jason Pepper
Greenhorn

Joined: Oct 15, 2005
Posts: 9
Thanks. That would work.
 
GeeCON Prague 2014
 
subject: String literal constants - opinion sought.