XSLTProcessor component missing? (and possible Catalog bug)

[Michael McKibben <mi...@hihat.net>]

I noticed some useful XML components were ported over from Cocoon. Was
there a reason why the XSLProcessor component was left behind? It might
get lonely :) 

Also, I noticed that the CatalogEntityResolver implements the
org.xml.sax.EntityResolver interface and not the
org.apache.avalon.excalibur.xml.EntityResolver interface. Isn't this a
bug? Otherwise, the ExcaliburComponentManager will complain that it
doesn't implement Component and throw an exception.

Regards,

--mike


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: XSLTProcessor component missing? (and possible Catalog bug)

[Carsten Ziegeler <cz...@s-und-n.de>]

Michael McKibben wrote:
> 
> 
> I noticed some useful XML components were ported over from Cocoon. Was
> there a reason why the XSLProcessor component was left behind? It might
> get lonely :) 
> 
Yes, there is a reason: time.
Seriously, the plan was to move first the complex parts of Cocoon to Avalon
like the source resolving and after that is established we wanted to move
all the other components like the XSLTProcessor as well.
I hope to get the source resolving finished in the next two weeks and
will then continue with the other components.

Carsten

> Also, I noticed that the CatalogEntityResolver implements the
> org.xml.sax.EntityResolver interface and not the
> org.apache.avalon.excalibur.xml.EntityResolver interface. Isn't this a
> bug? Otherwise, the ExcaliburComponentManager will complain that it
> doesn't implement Component and throw an exception.
> 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>