Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 33099 invoked from network); 17 Feb 2001 20:04:45 -0000 Received: from fw.infoplanning.net (HELO infoplanning.com) (@209.8.58.131) by h31.sny.collab.net with SMTP; 17 Feb 2001 20:04:45 -0000 Received: (qmail 2162 invoked from network); 17 Feb 2001 20:06:19 -0000 Received: from ip85.leesburg4.va.pub-ip.psi.net (HELO apache.org) (38.30.171.85) by inet with SMTP; 17 Feb 2001 20:06:19 -0000 Message-ID: <3A8EDC98.E913FA7B@apache.org> Date: Sat, 17 Feb 2001 15:18:32 -0500 From: Berin Loritsch X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [C2] FIXED Fault with current CVS? Missing sitemap.ComponentHolder.java References: <3A8ED085.B4CDB449@apache.org> <3A8EDB3E.6A16F197@apache.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Berin Loritsch wrote: > > OK. Finally, I got it fixed. ComponentHolder is no longer necessary. I am not > finished with my optimizations of the XSP system, however, you can rest in the > fact that I will be concentrating on creating a usable system at this point. > > It should be safe to update from CVS again. The end goal: Sitemap Components are accessed the _same_ way as regular components. In other words, for each main role (Generator, Transformer, etc.) you grab a ComponentSelector. That ComponentSelector will grab the specific instance. This will protect us from the current abuses of the ComponentManager that the Sitemap puts us through. It will be sooner than later, but exact timing is unknown. > > Berin Loritsch wrote: > > > > Stuart Roebuck wrote: > > > > > > I decided it was about time I updated my copy of C2 to a newer CVS version and have been running into some problems. > > > > > > Currently when I try to run the Cocoon examples I get a sitemap compile error. Basically, the sitemap is compiled into code containing the java import statement: > > > > > > import org.apache.cocoon.sitemap.ComponentHolder; > > > > > > But this Class no longer exists in the repository, so I get the following bit of log: > > > > > > > ERROR 12041 [cocoon ] (Thread-9): Error compiling sitemap > > > > org.apache.cocoon.components.language.LanguageException: Error compiling > > > > _sitemap_xmap: > > > > Line 40, column 7: Class org.apache.cocoon.sitemap.ComponentHolder not found in > > > > import. > > > > at > > > > org.apache.cocoon.components.language.programming.java.JavaLanguage.compile(JavaLanguage.java:206) > > > > at > > > > org.apache.cocoon.components.language.programming.CompiledProgrammingLanguage.load(CompiledProgrammingLanguage.java:132) > > > > at > > > > org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(ProgramGeneratorImpl.java:200) > > > > at org.apache.cocoon.sitemap.Handler.run(Handler.java:170) > > > > at java.lang.Thread.run(Thread.java:479) > > > > > > > > > > Have I just chosen a bad time to update, or this some oversight? > > > > Deleting the work directory works. Right now, everything except XSP is working, and I am > > tracking down why. Part of the reason is that the SitemapComponentManager and the regular > > ComponentManager aren't talking to each other correctly. I almost have it down though. > > Hopefully it will be fully fixed RSN. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > > For additional commands, email: cocoon-dev-help@xml.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org