Re: JSTL x:parse problems

2002-04-18 Thread peter lin
I think you're problem is that xmlText expects String. Have you tried xmlURL, isntead of xmlText. here is the way I use parse, which works fine. c:set var=xmlurlsample.xml/c:set x:parse var=dom c:import url=${xmlurl}/ /x:parse peter lin Steve Appling wrote: I am having problems

Re: JSTL x:parse problems

2002-04-18 Thread Steve Appling
In section 11.2 of the JSTL 1.0 public draft specification it says that xmlText can take a String or a Reader. I can't use xmlUrl (or body content of the parse tag) because my xml is in a section of the web application that is in a restricted security domain. I can't provide authentication

Re: JSTL x:parse problems

2002-04-18 Thread peter lin
The code that handles it does perform type checking, so it should work. the code below is taken from the parsesupport. if (xmlUrl != null) d = parseURLWithFilter(xmlUrl, filter); else { if (xmlText instanceof String) d =

Re: JSTL x:parse problems

2002-04-18 Thread Shawn Bayern
Reader is fine... Your problem comes from a simple error that everyone (including me) makes from time to time when testing JSTL with scriptlets. Look at your sample carefully: % InputStream is = application.getResourceAsStream(/test.xml); InputStreamReader reader = new

Extending jsp:useBean tag

2002-04-18 Thread amishra
I am interested in extending jsp:useBean tag. I want to add product specific calls to code within this tag, which are always performed. What is the best way to accomplish this. Should I implement all function done by jsp:useBean in the new tag or is there a way to extend the existing TagHandler

Re: Extending jsp:useBean tag

2002-04-18 Thread Shawn Bayern
On Thu, 18 Apr 2002 [EMAIL PROTECTED] wrote: I am interested in extending jsp:useBean tag. I want to add product specific calls to code within this tag, which are always performed. What is the best way to accomplish this. Should I implement all function done by jsp:useBean in the new tag

Re: JSTL x:parse problems

2002-04-18 Thread Shawn Bayern
On Thu, 18 Apr 2002, Steve Appling wrote: Thank you Shawn! I had hoped I was just doing something stupid. Unfortunately that isn't the only thing I'm doing wrong - this just moved me to my next problem. Here's a simplified example- ignoring the reader code I have: x:parse

Re: JSTL x:parse problems

2002-04-18 Thread Steve Appling
After scrolling down in the exception list I found that the root cause is a NoClassDefFoundError. What is the org.saxpath package? I'll post my simple sample page if needed, but does the following exception report shed any light on the problem? Exception Report: javax.servlet.ServletException:

Re: JSTL x:parse problems

2002-04-18 Thread Shawn Bayern
Oh! That just means you're missing a dependency in your web application. The easiest instructions, for right now, are to make sure all the JARs in the standard-example.war distribution are in your own web application's WEB-INF/lib directory. I'll be clarifying and simplifying the installation

Re: JSTL x:parse problems

2002-04-18 Thread Steve Appling
Thank you - I was under the mistaken impression that jstl.jar and standard.jar contained the entire JSTL implementation (at least what wasn't already in Tomcat's common lib). That definitely needs to make it into the documentation. BTW, in the example you sent you had: x:parse xml=${reader}

Re: JSTL x:parse problems

2002-04-18 Thread Shawn Bayern
On Thu, 18 Apr 2002, Steve Appling wrote: BTW, in the example you sent you had: x:parse xml=${reader} var=doc/ In my version, the attribute for the parse action needs to be xmlText. Was that a typo or are you using a different version than I am? Also I was not aware that I could get a

question about XPath tests

2002-04-18 Thread Steve Morrison
I have a node in an XML doc I'd like to compare against. It's a number, say 1001. x:out select=$dom_ref/path/to/node = 1001/ displays true or false correctly depending on if the the node content is 1001 or not. But this always is true: x:if select=$dom_ref/path/to/node = 1001true/x:if no