A bit more info supporting my theory that it is a TC bug. I was running
TC 7 pretty much out of the box. The only changed files in the TC 7
tree were the server and web app config files. My doc root with the
actual webapps is on another drive and not under the TC folder tree. I
installed TC
It appears that the problem was truly a bug in that particular version
of Tomcat. I dug through all of the jar files and all possibly custom
config items, and found absolutely nothing amiss. Finally, I moved up to
Tomcat 8 on the server, and everything works fine now.
On 7/21/2015 12:07 PM,
Konstantin, thank you so much for the quick response. My comments below
On 7/21/2015 6:07 AM, Konstantin Kolinko wrote:
2015-07-21 3:13 GMT+03:00 Jerry Malcolm :
I have a large webapp that processes XML data into JSPs using XPath/JSTL
plus some of my own custom tags.
Are you using Apache
2015-07-21 3:13 GMT+03:00 Jerry Malcolm :
> I have a large webapp that processes XML data into JSPs using XPath/JSTL
> plus some of my own custom tags.
Are you using Apache (Jakarta/Tomcat) implementation of JSTL or some
3-rd party one?
http://tomcat.apache.org/taglibs.html
It should not matter.
BTW Everything else in XPath is working fine on the 3rd
environment. I can do
and it outputs the data correctly. It appears the only thing not
working is when I reference an x:set variable using the ${...} syntax.
Jerry
On 7/20/2015 7:13 PM, Jerry Malcolm wrote:
I have a large w
I have a large webapp that processes XML data into JSPs using XPath/JSTL
plus some of my own custom tags. The app is working fine on two
separate Tomcat systems (one is TC7 and one is TC8). I copied the app
to a third system (TC 7.0.57) and I'm having problems with all of the
x:set variables
