Re: Using JSTL 1.1.2 with Tomcat 5.5 J2SE 5.0

2005-06-06 Thread Dino Klein

I have two jspx files (pasted below), where one includes the other.
When I remove the xmlns:c declaration/importation - it works; similarly,  
when I do not include the other file, it also works fine.


Thanks.


(1) main.jspx
==
?xml version=1.0 encoding=UTF-8?
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0
maintag xmlns:c=http://java.sun.com/jsp/jstl/core;
jsp:directive.include file=one.jspx/
/maintag
/jsp:root
=

(2) one.jspx
=
?xml version=1.0 encoding=UTF-8?
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0
tagahello/taga
/jsp:root
=


On Sun, 05 Jun 2005 23:26:07 -0400, Rahul P Akolkar [EMAIL PROTECTED]  
wrote:



Dino Klein [EMAIL PROTECTED] wrote on 06/05/2005 10:43:13 PM:
snip/

org.apache.jasper.JasperException: h3Validation error messages from
TagLibraryValidator for c/h3pnull: org.xml.sax.SAXParseException:
Attribute jsp bound to namespace http://www.w3.org/2000/xmlns/; was
already specified for element jsp:root./p

snap/

Can you post the jsp(x)?
-Rahul


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [OT] Using JSTL 1.1.2 with Tomcat 5.5 J2SE 5.0

2005-06-06 Thread Rahul P Akolkar
Dino Klein [EMAIL PROTECTED] wrote on 06/06/2005 09:16:07 AM:

 I have two jspx files (pasted below), where one includes the other.
 When I remove the xmlns:c declaration/importation - it works; similarly, 
 
 when I do not include the other file, it also works fine.
snip/
 (1) main.jspx
 ==
 ?xml version=1.0 encoding=UTF-8?
 jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0
 maintag xmlns:c=http://java.sun.com/jsp/jstl/core;
jsp:directive.include file=one.jspx/
 /maintag
 /jsp:root
 =
 
 (2) one.jspx
 =
 ?xml version=1.0 encoding=UTF-8?
 jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0
tagahello/taga
 /jsp:root
 =

This is not a JSTL issue, marked OT. In XML views of JSPs, the included 
file is expanded in place. And jasper2 isn't happy because there are more 
than one jsp:root elements in the XML view of main.jspx. In your case, I 
don't see any need for either of the two jsp:root elements (unless you 
simplified before posting, and you have a legitimate need). Remove either, 
or both, and you should be fine.

I think you've raised an interesting question. It seems jasper2 will not 
allow includes in the scenarios that result in more than one jsp:root 
elements in the expanded view. Please check if the spec says anything 
about this. If not, I would:
1) Ask for clarification on jsp spec public (unless Mark or Pierre listen 
to this list, and answer)
2) Post on tomcat-user, wait for feedback (follow with a bug report, 
depending on feedback)

-Rahul


simple question on deltamanger - understanding

2005-06-06 Thread John MccLain
 My understanding is that the rclustering replication DeltaManager it is
called via a setAttribute if UseDirtyFlag is set to true. So does this mean
that it only checks for a  delta on the attribute that was set, or does it
check the deltas in the entire session?

Also, does anyone know where I can get commercial Tomcat support - we are
having trouble with clustering

John McClain
Senior Software Engineer
TCS Healthcare
[EMAIL PROTECTED]
(530)886-1700x235
Skepticism is the first step toward truth


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Using JSTL 1.1.2 with Tomcat 5.5 J2SE 5.0

2005-06-06 Thread Rahul P Akolkar
Dino Klein [EMAIL PROTECTED] wrote on 06/06/2005 03:44:38 PM:
snip/
 I did some primitive debugging, and all I could find out is that if I 
use 
 xmlns:fn=http://java.sun.com/jsp/jstl/functions;, then I have no 
 problems; I checked the TLDs, and I noticed that it does not include a 
 validator like the rest (c, sql, fmt, x - all do, and cause problems).

I tried this, you are right. It turns out the bit in my earlier email that 
talked about multiple jsp:root's in the expanded view was FUD, my sincere 
apologies. I've removed the OT marker. Unless someone else has an 
explanation, you can:
1) Dig into the JSTL TLV impls
2) File a bug report (if you're sufficiently convinced)
The two options are not mutually exclusive ;-)

-Rahul