Carsten Ziegeler wrote:

Starting with 2.2 you could use the getSitemapPath() method of
the Request object (you can get the request object using
the ContextHelper).

Does it return sitemap file name? ... Nope. I guess you've not noticed on the bottom of the email I mentioned:


  -    private String getSitemapPath() throws Exception {
  -        Source src = this.sourceresolver.resolveURI(".");
  -        try {
  -            return src.getURI();
  -        } finally {
  -            this.sourceresolver.release(src);
  -        }
       }

That's what we already had and it did not work... Need something uniquely identifying each sitemap file. Sitemap path is not unique.

Vadim


Carsten


-----Original Message-----
From: Vadim Gritsenko [mailto:[EMAIL PROTECTED] Sent: Thursday, September 30, 2004 12:16 AM
To: Cocoon Developers
Subject: Sitemap Reloading & Flow: Crashes


Hi all,

Seems like I found the reason why "touch sitemap" crashes all current flows. Sitemap reloading causes current sitemap to be released, together with flow Interpreter instance, and new sitemap looks up new instance of flow Interpreter. Because Interpreters are SingleThreaded, new instance is created. And after this change [1], each new instance has unique ID which causes scopes of all currently running flows to get lost:

+ // The instance counters, used to produce unique IDs
+ private static int instanceCounter = 0;
+
+ // The instance ID of this interpreter, used to identify user scopes
+ private String instanceID;


Previously scopes where associated with sitemap path (which should be really sitemap path plus file name). Any insight on how to restore lost functionality? Any way to find out full sitemap URI?

Vadim

[1] http://marc.theaimsgroup.com/?l=xml-cocoon-cvs&m=108917975901961



Reply via email to