You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by SAXESS - Hussayn Dabbous <da...@saxess.com> on 2003/01/15 12:35:09 UTC

Why are CatalogManager.properties in subdir classes ???

Hy;

I wonder, why the Catalog.properties must reside
in the classes directory. For me it would be
more natural to put it either into WEB-INF, or
WEB-INF/conf instead.

any explanations?

This is what makes me troubles:
(Maybe someone knows a workaround for this ...)

i use eclipse for my development.
whenever i rebuild cocoon, the classes directory
is thrown away and repopulated with new classfiles.
unfortunately everytime i have to copy CatalogManager.properties
back to the class dir afterwards...

regards, hussayn

-- 
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax:     +49-221-56011-20
E-Mail:  dabbous@saxess.com


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Re: Why are CatalogManager.properties in subdir classes ???

Posted by David Crossley <cr...@indexgeo.com.au>.
Bernhard Huber wrote:
> SAXESS - Hussayn Dabbous wrote:
> > I wonder, why the Catalog.properties must reside
> > in the classes directory. For me it would be
> > more natural to put it either into WEB-INF, or
> > WEB-INF/conf instead.
> > 
> com.sun.resolver.CatalogManager reads this property file
> from the classpath, so its not any Cocoon component
> responsible for that behaviour,

That is correct the Entity Resolver code expects it to
be there.

Actually, we have not being using the com.sun.resolver
for a while now. Norm now has the code and documentation
at Apache XML Commons http://xml.apache.org/commons/
Cocoon and Forrest use the latest resolver.jar pre-release.

Evidently, there is a change in this version that allows the
entity resolver to ignore missing CatalogManager.properties

The next steps for Cocoon, are to take advantage of the
upgraded resolver and refine our implementation of it.
If you could help, please see the new "resolver-article.html"
via the draft XML Commons website:
http://marc.theaimsgroup.com/?l=xml-commons-dev&m=104037450832414

--David

> for a detailed explanantin, see userdocs/concepts entity catalogs 
> (catalog.html)
> 
> regards bernhard




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Re: Why are CatalogManager.properties in subdir classes ???

Posted by Bernhard Huber <be...@a1.net>.
hi,

SAXESS - Hussayn Dabbous wrote:
> Hy;
> 
> I wonder, why the Catalog.properties must reside
> in the classes directory. For me it would be
> more natural to put it either into WEB-INF, or
> WEB-INF/conf instead.
> 
com.sun.resolver.CatalogManager reads this property file from the 
classpath, so its not any Cocoon component responsible for that behaviour,
for a detailed explanantin, see userdocs/concepts entity catalogs 
(catalog.html)

regards bernhard


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org