Hello David,
You are right. I just found the
org.apache.taglibs.standard.tag.el.core.ExpressionUtil class when
looking on the c:out tag source code.
I am invoking it from my tag lib and it is working very well.
But this use of the ExpressionUtil class is ok ? Can I expect his
interface to be
The Jakarta JSTL implementation provides a public API that you can use
in your own tag libraries. You can browse the javadoc for the
"ExpressionEvaluatorManager" class. You could also browse the source
code for the "Struts-EL" contributed library in the Struts distribution.
If you inspect the "Ev
Hello,
In JSTL we can use a expression language in parameters expressions,
like :
Thanks for logging in, .
The ${name} is evaluated and this value is send to the c:out tag.
I want the user of my tags can use ${} expressions on the parameters
of my taglib.
It possible use this expression
Here is the code in one of my JSP file:
When the person ID is Chinese characters, the ID displayed right, but not on the query
string. I guess that the url
parameter string is not encoded in utf-8 to take Chinese charact
While working with a struts application, I wanted to use the i18n taglibs to format
dates, times, currencies etc. However, I don't want to use scriptlets in my JSP.
for example:
" />
or perhaps: (struts-style)
Is there a plan to provide this functionality? ... or like the struts style
Jeff,
My bad, that description is incorrect. It probably is an older text that I had
written while developing the tag. There currently is no way to avoid stripping the
html because there were numerous issues that came up with closing tags, much less
intelligently closing tags, so I made a
>From string taglibs doc's: "A more intelligent substring. It attempts to
cut off a string after a space, following predefined or user-supplied
lower and upper limits, useful for making short descriptions from long
text. Can also strip HTML, or if not, intelligently close any tags that
were lef
Missing setters dont cause a problem and missing getters dont either (it
just wont get that variable ;)
Java Introspection is based on what it finds for getters and setters and not
the actual variable.
But even though that's how ji works it is still considered "standard" to
define all getters and s
