if you are using a xml_parser_utility go to command line and type
bash>which xml_parser_utility

if not there is a build.xml and or pom.xml which will need to reference the 
xml-parser:

--in buildl.xml usually identified as a property to one of the constructed 
CLASSPATH
bash>vi build.xml
search for xml ( press / and type xml at bottom)
search for xerces (press / and type xerces at bottom)
quit vi (:q!)

--in pom.xml usually identified as a dependency
bash>vi  pom.xml 
search for xml ( press / and type xml at bottom)
search for xerces (press / and type xerces at bottom)
quit vi (:q!)

report back the exact version of the xml or xerces parser you see in either 
build.xml or pom.xml

thanks,
Martin 
______________________________________________ 
Jogi és Bizalmassági kinyilatkoztatás
 Ez az
üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük, hogy
jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
készítése nem megengedett.  Ez az üzenet csak ismeret cserét szolgál és
semmiféle jogi alkalmazhatósága sincs.  Mivel az electronikus üzenetek
könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet
ezen üzenet tartalma miatt.





> Date: Sat, 30 Apr 2011 15:40:53 +0200
> Subject: Re: [Jelly] XML ForEach tag hangs
> From: csab...@gmail.com
> To: user@commons.apache.org
> 
> Hi,
> 
> thank you very much for your responses. I'm already trying to
> determine the version of xml parser without much success yet.
> 
> Csaba
> 
> 2011/4/30 Martin Gainty <mgai...@hotmail.com>:
> >
> > trying not to point fingers (at least until we have ALL the facts)
> > a similar incident happened on another apache project and an older version 
> > of xml-parser was at fault
> > trying to determine the implemented xml-parser and the version in this case 
> > would *at least* isolate the problem to that parser
> >
> > thanks paul!
> > Martin
> > ______________________________________________
> > Jogi és Bizalmassági kinyilatkoztatás
> >  Ez az
> > üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük, hogy
> > jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
> > készítése nem megengedett.  Ez az üzenet csak ismeret cserét szolgál és
> > semmiféle jogi alkalmazhatósága sincs.  Mivel az electronikus üzenetek
> > könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet
> > ezen üzenet tartalma miatt.
> >
> >
> >
> >
> >
> >> Subject: Re: [Jelly] XML ForEach tag hangs
> >> From: p...@hoplahup.net
> >> Date: Sat, 30 Apr 2011 09:44:27 +0200
> >> To: user@commons.apache.org
> >>
> >> Csaba,
> >>
> >> As Martin has suggested, the underlying XML parser could be guilty.
> >> I would rather suspect an overly old dom4j or jaxen (that would be in the 
> >> container's classpath hence overriding the webapp's).
> >>
> >> Are you able to find their version?
> >> Otherwise I can dig out a form of jwhich in jelly.
> >>
> >> paul
> >>
> >>
> >> Le 30 avr. 2011 à 03:02, Csaba Győrffy a écrit :
> >>
> >> > Hello there!
> >> >
> >> > I'm trying to use the ForEach tag in Jelly's XML tag library. The
> >> > following script works fine in a standard Java console application:
> >> >
> >> > <x:parse var="doc">
> >> >  <a>
> >> >    <b v="1"/>
> >> >    <b v="2"/>
> >> >    <b v="3"/>
> >> >  </a>
> >> > </x:parse>
> >> >
> >> > <x:forEach select="$doc/a/b" var="x">
> >> >  ...
> >> > </x:forEach>
> >> >
> >> > However, if using Jelly on an application server, from inside an EJB
> >> > container (session bean), running the script above hangs, and 100% CPU
> >> > utilisation comes. I realized while debugging that NodeComparator
> >> > class' getDepth method gets into an infinite loop and never returns.
> >> >
> >> > If I remove two "b" elements from the xml fragment above (so only one
> >> > remains), it works fine. It also works if I change the second part of
> >> > the above script to the following:
> >> >
> >> > <x:forEach select="$doc/a">
> >> >  <x:forEach select="b">
> >> >    ...
> >> >  </x:forEach>
> >> > </x:forEach>
> >> >
> >> > Does anyone have any idea why is that happening? Any help is much 
> >> > appreciated.
> >> >
> >> > Thank you:
> >> > Csaba
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> >> > For additional commands, e-mail: user-h...@commons.apache.org
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: user-h...@commons.apache.org
> >>
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
> 
                                          

Reply via email to