Joerg Heinicke wrote:
> Jon Bedworth wrote:
> >
> > Please can someone help ...
> > 
> > I have been developing an application on my own server using Cocoon 2.1 
> > and Tomcat. Things work fine.
> > 
> > Yet when I transfer this to a server that is also using Tomcat but a 
> > newer version of Cocoon (version 2.1.2), I get the following error when 
> > I try to access certain pages:
> > 
> > org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
> > org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
> > java.net.MalformedURLException: no protocol: XML_entities\ISOnum.ent
> > 
> > which seems to relate to a problem with an entity definition file I have 
> > in a sub-directory (XML_entities).
> > 
> > Has something happened in the newer release to cause this? This entity 
> > file is a standard file, and there is nothing 'malformed' about it that 
> > i can see.
> 
> As far as I know only the Xerces version has changed related to this 
> problem. Maybe you can try to switch back.
> 
> (cc-ing David Crossley, who seems not to be on this list)

(I am a digest subscriber, but only look occasionally.)

Apart from the suggestion from Joerg, i cannot think of anything
changed in Cocoon that might cause this.

Jon, here are a few more comments:

Is the Java version the same on both machines?

The error message is not saying that the file or its contents
are malformed. It is saying that the URL to the file is malformed.

I presume that you are aware that these entity sets are already
provided by the Cocoon core:
http://cocoon.apache.org/2.1/userdocs/concepts/catalog.html

What are you trying to do with ISOnum.ent that you would need
to use a hard-coded URL?

To help further, we would need to know more information:
what you are trying to achieve, the sitemap snippet that
invokes this pipeline, the xml instance that is being processed,
more context from the logfile, etc.

--David





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to