AW: Tomcat not working
Carefully check the TLD-Definition-File, sometimes a bug in the TLD-File prevents the tomcat from starting the context -Ursprungliche Nachricht- Von: Ananth R [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 4. Marz 2004 10:39 An: Tag Libraries Users List Betreff: Tomcat not working Hello I was deploying some tag libraries .It worked nicely for some time.Suddenly, Iam not able to enter into the examples( webapps/examples) directory.Whats this problem?? I checked server.xml file.It looks OK( context tag is OK). Please diagnoise the problem. Thanking you regards A N A N T H. R - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XTags: Variable-Tag
Hi, the XTags Variable-Tag doesn't work if I use it this way: xtags:variable id=myNodesList select=item type=List/ I've found out that if a 'List' or 'Node' Type is used, the Variable- Tag performs a case insensitive test on 'list' or 'node'. - That's why the above example can't work correctly. I ask the developers to fix this problem. Thanks a lot! ;-) Regards, Manuel Tromm -- Dipl.-Inf. Manuel Tromm [EMAIL PROTECTED] otris software AGhttp://www.otris.de Landgrafenstr. 153 Fon +49 (0)231 95 80 69 -0 D-44139 Dortmund Fax +49 (0)231 95 80 69 -44 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: XTags: Usage of org.dom4j.Documents?
=foo/bar context=%= mydoc % ... /xtags:forEach You can define a variable for any expression or parse to allow you to evaluate once and keep it around for future reference. e.g. xtags:parse id=mydoc some taghello there/tag /some /xtags:parse then later... xtags:valueOf select=/some/tag context=%= mydoc %/ or you could use the XPath variables. Whenever an attribute is defined in page / request / session / application scope it is available as an XPath variable. So you could rewrite the above as xtags:valueOf select=$mydoc/some/tag/ You can also use the xtags:variable tag to define a variable of an XPath expression, to avoid reevaluation. e.g. xtags:variable id=mytags select=//tag/ Of course you could always define your own scripting variables for documents and pass them in as a context parameter or create your own attributes and use the XPath variable syntax. Hope that helps. James - Original Message - From: Manuel Tromm [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 06, 2001 9:36 AM Subject: XTags: Usage of org.dom4j.Documents? Hi folks, I've got a question about using XTags: The common way to use the XTags, is to parse an XML document from somewhere by using the xtags:parse-Tag. After the XML-Code has been parsed, it can be accessed by the different X-Tags... Sometimes I have to use the XML-Source (that is needed as input for XTags) twice or more or at completely different locations of my web-application. For this reason I've added the XML-Code to a cache. The problem is now, that every time when the XTags-JSP is requested, the XML-Input has to be parsed by the XTags again. That means a lack of performance. Now my question: Because the XTags are built on top of the dom4j, I'd like to know if there is any way to use an (already parsed!) org.dom4j.Document as input for XTags, so that I don't have to parse XML-Sources twice? If yet there is no way, I'd like to ask the developers to provide an appropriate Tag, because I think it would be also quite helpful for other users. Does someone know a solution? Regards, Manuel Tromm test_for_each_context.jsp
XTags: Usage of org.dom4j.Documents?
Hi folks, I've got a question about using XTags: The common way to use the XTags, is to parse an XML document from somewhere by using the xtags:parse-Tag. After the XML-Code has been parsed, it can be accessed by the different X-Tags... Sometimes I have to use the XML-Source (that is needed as input for XTags) twice or more or at completely different locations of my web-application. For this reason I've added the XML-Code to a cache. The problem is now, that every time when the XTags-JSP is requested, the XML-Input has to be parsed by the XTags again. That means a lack of performance. Now my question: Because the XTags are built on top of the dom4j, I'd like to know if there is any way to use an (already parsed!) org.dom4j.Document as input for XTags, so that I don't have to parse XML-Sources twice? If yet there is no way, I'd like to ask the developers to provide an appropriate Tag, because I think it would be also quite helpful for other users. Does someone know a solution? Regards, Manuel Tromm