[1]
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00584.html
[2]
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00545.html
Has anyone done anything to these? I could do a patch to
LanguageShuntFactory [2] to have override capability depending on
Session language attribute.
What should we do
+1 from me too, though we might take a vote from the larger community on
this one. A lot of people's code is gonna stop compiling when the package
for ThrowawayBean2 changes...
--jim
- Original Message -
From: Schnitzer, Jeff [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday,
Ok, I did write a patch to LanguageShuntFactory. I attached the files in
this mail.
- LanguageShuntFactory.java is the new patched LanguageShuntFactory
- LanguageShuntFactory.java.old is the old LanguageShuntFactory (in
current CVS)
- LanguageShuntFactory.diff is diff file that can be applied to
-1 I say leave it, what's the point of changing it other than to create
headaches?
Travis
jim moore wrote:
+1 from me too, though we might take a vote from the larger community on
this one. A lot of people's code is gonna stop compiling when the package
for ThrowawayBean2 changes...
--jim
Has anyone compared performance of a 2-step JSP transformation with a
similar 2-step XSLT transformation? Being as JSPs are really servlets
with a bunch of print and tag start/end calls, it would seem to have an
easier task than XSLT transformations. Is it a wash?
I realize this isn't a
#1 has to be addressed by a custom ShuntFactory. You can't have
multiple mode attributes, but the value of a mode attribute can be a
composite:
command name=runQuery
controller class=org.foo.Query/
view name=success mode=content:wap
path=wap/en/queryResults.jsp/
view name=success
From: Dave Hahn [mailto:[EMAIL PROTECTED]
Has anyone compared performance of a 2-step JSP transformation with a
similar 2-step XSLT transformation? Being as JSPs are really servlets
with a bunch of print and tag start/end calls, it would seem to have
an
easier task than XSLT
