Jean-Baptiste Quenot wrote:
* David Crossley:
I think that it is a core facility that is often needed. Why do
you want to be rid of it? There is not really any overhead, is
there.
Nonono, don't worry I don't want to get rid of the catalog
resolving facility. Just greatly
Jean-Baptiste Quenot wrote:
* David Crossley:
Jean-Baptiste Quenot wrote:
I would like to know what purpose serves the existing
resources in webapp/WEB-INF/entities? I know that one can
setup a catalog for resolving entities, but I'm talking about
all the stuff
* David Crossley:
I think that it is a core facility that is often needed. Why do
you want to be rid of it? There is not really any overhead, is
there.
Nonono, don't worry I don't want to get rid of the catalog
resolving facility. Just greatly reduce the amount of mess in
this
Hello,
I would like to know what purpose serves the existing resources in
webapp/WEB-INF/entities? I know that one can setup a catalog for
resolving entities, but I'm talking about all the stuff: DTDs,
schemas, etc. Is it really useful for a mean web application?
In the README
Jorg Heymans wrote:
Would it make sense to package up the entities stuff and include it in
cocoon-core.jar or perhaps in cocoon-entities.jar ? Is this possible at
all ?
I know a bit about the entity resolver [1] but i don't
know about this.
The WEB-INF/entities/catalog reference
Hi,
Would it make sense to package up the entities stuff and include it in
cocoon-core.jar or perhaps in cocoon-entities.jar ? Is this possible at
all ?
It would make it easier to manage them from a maven point of view, as
the more we can put in jars the less we have to manage ourselves during
crossley2003/07/08 01:41:14
Modified:src/webapp/WEB-INF/entities catalog.xcat
Log:
Tweaks to the experimental XML Catalog:
- Removed old sitemap DTD
- Added missing book DTD
- Added document type declaration for catalog DTD, but commented-out because
many tools cannot cope
