OK, that works nicely to auto-load the default catalog.
I will send a patch for the properties file to set a dummy
catalog path, now that we do not rely on their build process.
Yes, the next thing is to decide what default entities should
be shipped. The ISO entity sets and Apache DTDs for a start.
many thanks, David
Dims wrote:
> David,
> Added some code in ResolverImpl to load the default catalog
> programatically using the parseCatalog function that you
> rightly pointed out. Please take a look and see in what
> direction you want this to go next.
> Thanks,
> dims
>
> --- David Crossley <[EMAIL PROTECTED]> wrote:
> > Hi Dims, it seems that there is too much variability
> > in the build process. It appears that we may not be
> > able to rely on them using the build option
> > -Dinstall.war=$TOMCAT_HOME/webapps
> >
> > I am sure that there would be a way to load the
> > default catalog via our Cocoon classes at
> > org/apache/cocoon/components/resolver
> > thereby leaving the CatalogManager.properties entirely
> > free for local use.
> >
> > If you can give me a starting point, then i will try
> > to add it (i am only a Java hacker :-). I can see a
> > parseCatalog() method in the resolver API javadocs,
> > but i am not sure where to call it from.
> > cheers, David
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
>
>
> =====
> Davanum Srinivas, JNI-FAQ Manager
> http://www.jGuru.com/faq/JNI
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.yahoo.com
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
