Re: [Jelly] XML ForEach tag hangs

Martin, your x namespace prefix is not properly bound. Somewhere up in your script, you should have xmlns:x="jelly:xml" hope it helps. paul Le 3 mai 2011 à 22:59, Martin Gainty a écrit : > > org.apache.commons.jelly.JellyException: > file:/C:/maven-plugin/jelly/commons-jel > ly-1.0-src/te

Re: [Jelly] XML ForEach tag hangs

Hi Martin I had this exception when tried to use select attribute with the core tag library's forEach tag, which doesn't support it. Anyway, I'm using the binaries downloaded from the project Download site: http://commons.apache.org/jelly/download_jelly.cgi and XML tag lib's foreach is working for

RE: [Jelly] XML ForEach tag hangs

org.apache.commons.jelly.JellyException: file:/C:/maven-plugin/jelly/commons-jel ly-1.0-src/test-classes/org/apache/commons/jelly/suite.jelly:29:43: This tag does not understand the 'select' attribute at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:232) at org.apache

Re: [digester] The element type ... must be terminated by the matching end-tag

On Tue, May 3, 2011 at 12:48 PM, Patrick Diviacco wrote: > I get the following error: > > May 3, 2011 6:41:25 PM org.apache.commons.digester.Digester fatalError > SEVERE: Parse Fatal Error at line 2336608 column 3: The element type "user" > must be terminated by the matching end-tag "". > org.xml.

[digester] The element type ... must be terminated by the matching end-tag

I get the following error: May 3, 2011 6:41:25 PM org.apache.commons.digester.Digester fatalError SEVERE: Parse Fatal Error at line 2336608 column 3: The element type "user" must be terminated by the matching end-tag "". org.xml.sax.SAXParseException: The element type "user" must be terminated by

Re: [dbcp] connection events / connection close hook

On 5/3/11 7:07 AM, Daniel Baldes wrote: > Hi, > > I'd like to run some connection-specific clean-up code when a > physical database connection is closed by the connection pool. You mean really closed, as in destroyed, or just returned to the pool? > > I found ConnectionEventListener and > PooledCo

Re: [scxml] Calling go() twice

On Tue, May 3, 2011 at 10:13 AM, Dario D wrote: > Thanks Jocke. How would you suggest to resume the the last state before the > condition was not met? Let's say that the condition was made valid somehow. > How to resume from the last state? > > To continue the previous example: > >        try { >

Re: [scxml] Calling go() twice

You will have to trigger an event I think. 2011/5/3 Dario D : > Thanks Jocke. How would you suggest to resume the the last state before the > condition was not met? Let's say that the condition was made valid somehow. > How to resume from the last state? > > To continue the previous example: > >  

Re: [scxml] Calling go() twice

Thanks Jocke. How would you suggest to resume the the last state before the condition was not met? Let's say that the condition was made valid somehow. How to resume from the last state? To continue the previous example: try { exec.go(); // Execution stops at state

[dbcp] connection events / connection close hook

Hi, I'd like to run some connection-specific clean-up code when a physical database connection is closed by the connection pool. I found ConnectionEventListener and PooledConnection.addConnectionEventListener() in the JDBC API, however I think this is just used internally by JDBC drivers? At

Re: [scxml] Calling go() twice

exec.go(); should only be called once. It will start the state machine and it will go through all steps that meets the criteria (event cond). Regards Jocke. 2011/5/3 Dario D : > Hello all, > > I've just started using SCXML and it's great. However, I've hit a brick wall > and I can't seem to figu

[scxml] Calling go() twice

Hello all, I've just started using SCXML and it's great. However, I've hit a brick wall and I can't seem to figure out something. I have the following XML file: http://www.w3.org/2005/07/scxml"; version="1.0" initialstate="state1">