Re: Nasty flowscript issue - nailed

2004-07-08 Thread Andrew Savory
Hi, On 7 Jul 2004, at 17:17, Gianugo Rabellino wrote: On Jul 7, 2004, at 8:03 AM, Sylvain Wallez wrote: Giaunugo, I committed the unique ID fix (using an instance counter). Can you please crosscheck? Thanks so much Sylvain! I'm out of the office for the next two days, but I'll get back to you

Re: Nasty flowscript issue - nailed

2004-07-07 Thread Sylvain Wallez
Vadim Gritsenko wrote: Sylvain Wallez wrote: snip/ The interpreter is looked up by the sitemap engine (see FlowNode.java), so in that case SingleThreaded means a different instance for each sitemap, which handles all requests for that sitemap. A bit hacky, but that's how it is since the origin

Re: Nasty flowscript issue - nailed

2004-07-07 Thread Gianugo Rabellino
On Jul 7, 2004, at 8:03 AM, Sylvain Wallez wrote: Giaunugo, I committed the unique ID fix (using an instance counter). Can you please crosscheck? Thanks so much Sylvain! I'm out of the office for the next two days, but I'll get back to you ASAP if Andrew/Jerm don't beat me at it... Ciao, --

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Andrew Savory
Hi, On 5 Jul 2004, at 22:16, Gianugo Rabellino wrote: I changed that to private String getSitemapPath() throws Exception { return ObjectModelHelper.getRequest( EnvironmentHelper.getCurrentEnvironment().getObjectModel()).getSitemapU RI(); } but being a freshman on Cocoon flow

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Jeremy Quinn
On 6 Jul 2004, at 10:04, Andrew Savory wrote: Hi, On 5 Jul 2004, at 22:16, Gianugo Rabellino wrote: I changed that to private String getSitemapPath() throws Exception { return ObjectModelHelper.getRequest( EnvironmentHelper.getCurrentEnvironment().getObjectModel()).getSitemap

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Sylvain Wallez
Gianugo Rabellino wrote: We had an interesting night here, dealing with a really nasty flowscript issue (http://marc.theaimsgroup.com/?t=10879848851r=1w=2). Thanks to the precious help of Jerm, Andrew and Paul Russell, our small hackaton seemed to be successful in at least nailing the

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Gianugo Rabellino
On Jul 6, 2004, at 11:35 AM, Sylvain Wallez wrote: I changed that to private String getSitemapPath() throws Exception { return ObjectModelHelper.getRequest( EnvironmentHelper.getCurrentEnvironment().getObjectModel()).getSitemap UR I(); } Aargh! You should absolutely

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Sylvain Wallez
Gianugo Rabellino wrote: On Jul 6, 2004, at 11:35 AM, Sylvain Wallez wrote: I changed that to private String getSitemapPath() throws Exception { return ObjectModelHelper.getRequest( EnvironmentHelper.getCurrentEnvironment().getObjectModel()).getSitemap UR I(); } Aargh!

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Sylvain Wallez
Gianugo Rabellino wrote: On Jul 6, 2004, at 11:35 AM, Sylvain Wallez wrote: I changed that to private String getSitemapPath() throws Exception { return ObjectModelHelper.getRequest( EnvironmentHelper.getCurrentEnvironment().getObjectModel()).getSitemap UR I(); } Aargh!

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Gianugo Rabellino
On Jul 6, 2004, at 12:26 PM, Sylvain Wallez wrote: There is a solution, though: there's a different FlowIntepreter for each Processor instance (they are SingleThreaded), and so each interpreter instance could produce a unique identifier and use it as the result of getSitemapPath (which

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Sylvain Wallez
Gianugo Rabellino wrote: On Jul 6, 2004, at 12:26 PM, Sylvain Wallez wrote: There is a solution, though: there's a different FlowIntepreter for each Processor instance (they are SingleThreaded), and so each interpreter instance could produce a unique identifier and use it as the result of

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Vadim Gritsenko
Sylvain Wallez wrote: Gianugo Rabellino wrote: On Jul 6, 2004, at 12:26 PM, Sylvain Wallez wrote: There is a solution, though: there's a different FlowIntepreter for each Processor instance (they are SingleThreaded), and so each interpreter instance could produce a unique identifier and use

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Sylvain Wallez
Vadim Gritsenko wrote: Sylvain Wallez wrote: Gianugo Rabellino wrote: On Jul 6, 2004, at 12:26 PM, Sylvain Wallez wrote: There is a solution, though: there's a different FlowIntepreter for each Processor instance (they are SingleThreaded), and so each interpreter instance could produce a

Re: Nasty flowscript issue - nailed

2004-07-06 Thread Vadim Gritsenko
Sylvain Wallez wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: JavaScriptInterpreter should have an id attribute intialized once, whose value is used instead of getSitemapPath(), e.g. private String interpreterID = IDGenerator.getNewID(); System.identityHashCode(this) is much simpler than

Nasty flowscript issue - nailed

2004-07-05 Thread Gianugo Rabellino
We had an interesting night here, dealing with a really nasty flowscript issue (http://marc.theaimsgroup.com/?t=10879848851r=1w=2). Thanks to the precious help of Jerm, Andrew and Paul Russell, our small hackaton seemed to be successful in at least nailing the issue. So, there you go: