Yep thats what I ended up doing. The code
(Locale)ExpressionEvaluatorManager.evaluate("locale",
expr,Locale.class, this, pageContext)
was working against standard.jar (1.0).So just not sure why this is breaking
all of a sudden.
Thanks,
Mujahid
Frank W. Zammetti wrote:
I'm not sure
I have a custom tag in which I am evaluating an attribute as follow:
(Locale)ExpressionEvaluatorManager.evaluate("locale", expr,
Locale.class, this, pageContext)
But I get an error:
javax.servlet.jsp.JspException: An error occurred while evaluating
custom action attribute "locale" with value
Weblogic has an option where you can force it load classes from the
WEB-INF directory. I did that to eliminate any potential class loading
conflicts...
Still the same issue. I found a known issue
http://edocs.bea.com/wls/docs91/issues/known_resolved.html#1056681
[CR210907] :
Netui databind
When you say Weblogic is provdinig JSTL 1.1 version, you are reffering
to standard.jar ?
I don't have anything deployed except the example war. So I am not sure
about the conflicts.
Thanks,
Mujahid
Wendy Smoak wrote:
On 3/14/06, Mujahid Ali <[EMAIL PROTECTED]> wrote:
9
rvletRequestImpl.java:1310)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
If you need any more info, please let me know. I really want to find a
way to resolve this...
Thanks,
Mujahid
Wendy Smoak wrote:
On 3/14/06,
Hey Guys,
I am using some tags from the struts-el package and they used to work
fine under weblogic 8.1; After switching over to weblogic 9.1, it seems
that the BeanInfo class for a given tan is never called, so the jstl
expression ${...} is never evaluated. Has anyone seen similar problems?
6 matches
Mail list logo