IMO this is a design smell of the presentation layer.
My suggestion would be to refactor these items down to the
'business-layer' and then have your actions put the results of that
layer into the form/display bean.
Then the .jsp could just look like <c:out value='${order.smallOrderFeeLimit}'/>
There may be more to this with your particular site, but that's a
first off-the-cuff guess.
hth,
On 2/8/06, Keith Fetterman <[EMAIL PROTECTED]> wrote:
> We are converting old JSP pages to Struts and JSTL and I am running into
> a problem. On the old JSP pages, we have some calls to static methods
> in scriptlets and runtime expressions. On the new JSP pages, we have
> disabled scriptlets and runtime expressions. Here is an example:
>
> The old code will have an expression like:
> <%= OrderRulesBean.getSmallOrderFeeLimit() %>
>
> What is the best way (best practice or easiest to implement) to access
> static methods in the JSP pages without resorting to runtime expressions?
--
Keith Sader
[EMAIL PROTECTED]
http://www.saderfamily.org/roller/page/ksader
http://www.jroller.com/page/certifieddanger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
