PRO is production. yes, what i say is exactly as you assumed: same JSPs work
on our production and fail locally.
anyway, the issue is resolved, it was unrelated to jstl or standard taglib,
but to do with classloading.
--
View this message in context:
http://www.nabble.com/java.lang.ClassCastExc
What version of the Standard taglib are you using?
What's a PRO? Are you saying that the same code works in one
environment and not another?
Does your application make use of:
Config.set(..., Config.FMT_LOCALIZATION_CONTEXT, ...)
On Tue, Dec 16, 2008 at 4:57 AM, konkere wrote:
>
> yesterday i
nope. we use fmt only for localized messages, so
--
View this message in context:
http://www.nabble.com/java.lang.ClassCastException-%40-org.apache.taglibs.standard.tag.common.fmt.BundleSupport-tp21030184p21031282.html
Sent from the Taglibs - User mailing list archive at Nabble.com.
-
Are you using "fmt" tag to format values?
konkere
16/12/2008 08:10
Please respond to
"Tag Libraries Users List"
To
taglibs-user@jakarta.apache.org
cc
Subject
java.lang.ClassCastException @
org.apache.taglibs.standard.tag.common.fmt.BundleSupport
yester
yesterday i got this fancy exception:
java.lang.ClassCastException: javax.servlet.jsp.jstl.fmt.LocalizationContext
at
org.apache.taglibs.standard.tag.common.fmt.BundleSupport.getLocalizationContext(Ljavax.servlet.jsp.PageContext;)Ljavax.servlet.jsp.jstl.fmt.LocalizationContext;(BundleSupp
