Return-Path: 
 <users-return-69277-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: (qmail 93498 invoked from network); 24 Jun 2004 16:11:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 24 Jun 2004 16:11:44 -0000
Received: (qmail 45206 invoked by uid 500); 24 Jun 2004 16:11:22 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 45078 invoked by uid 500); 24 Jun 2004 16:11:20 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
list-post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 44722 invoked by uid 99); 24 Jun 2004 16:11:17 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [62.17.160.115] (HELO dub-msx1.spectelcorp.com) (62.17.160.115)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 24 Jun 2004 09:11:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: XSP Generator not using Cocoon Entity Resolver but defaultxerces
 resolver
Date: Thu, 24 Jun 2004 17:10:55 +0100
Message-ID: 
 <DEF39A0710293E489D45B10E06645CBD02C78BE4@dub-msx1.spectelcorp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: XSP Generator not using Cocoon Entity Resolver but defaultxerces
 resolver
Thread-Index: AcRZ/pHltvqulZ3tTOS0SZ4/8QQL5QABoBgw
From: "Marcial Rosales" <marcial.rosales@spectel.com>
To: <users@cocoon.apache.org>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

	David,

	No matter what mechanism I use to configure the entity resolver it does =
not work.
	If the entity resolver wasn't able to resolve an entity reference, it =
should report it in the output log anyway. However, I am not getting =
anything but the logs captured during the initialization of the =
catalogs.=20
	If my catalog is not properly set up, I should get an entry in the log =
saying something like "it couldn't resolve the entity reference", is =
that right?=20

	It seems Cocoon has not set up the parser yet using =
"XMLReader.setEntityResolver(org.xml.sax.EntityResolver resolver)".

	I am using Cocoon 2.0.4.

-----Original Message-----
From: David Crossley [mailto:crossley@apache.org]
Sent: 24 June 2004 16:18
To: users@cocoon.apache.org
Subject: Re: XSP Generator not using Cocoon Entity Resolver but
defaultxerces resolver


Marcial Rosales wrote:
>         I am trying to use the Cocoon catalog for resolving external
> parsed entities. I have configured Cocoon to use its own entity
> resolver but it seems that it is not configuring the parser used to
> parse the XSP files. I am trying to factor out chuncks of xml into
> external xml files that are included into the XSP using entity
> references.

But you have not configured the entity resolver at all,
just raised the verbosity level.

You need to follow the Cocoon Sample called "catalog-demo".
Run './cocoon.sh servlet' and see the Samples.

Specifically you need to add your own catalog.xcat
and configure it in cocoon.xconf using the "local-catalog"
parameter. Your catalog.xcat would define the mapping
between the filename "book_meeting" and some other local file.

--David

> This is the header of my little xsp file:
>=20
> <?xml version=3D"1.0"?>
>=20
> <!DOCTYPE xsp:page [
>     <!ENTITY book_meeting SYSTEM "book_meeting">
> ]>
>        =20
> This is the configuration I am using in cocoon.xconf:
>=20
> cocoon.xconf :
>   <entity-resolver
> class=3D"org.apache.cocoon.components.resolver.ResolverImpl"
> logger=3D"core.resolver">
>    <parameter name=3D"catalog" value=3D"/resources/entities/catalog"/>
>    <parameter name=3D"verbosity" value=3D"10"/>
>   </entity-resolver>
>=20
> This is the configuration in CatalogManager.properties:
> verbosity=3D10
> catalogs=3D
> prefer=3Dpublic
> allow-oasis-xml-catalog-pi=3Dyes
>=20
> in this is the log obtained within sitemap.log:
>=20
> java.io.FileNotFoundException:
> =
C:\WebPortal\Tomcat\webapps\webportal3\sitemaps\provisioning\docs\book_me=
eting (The system cannot find the file specified)




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


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