Sylvain Wallez wrote:
I don't like all those static methods that hardcode more and more logic, and even less when they lookup some components...You mean an extra component and not the Cocoon SourceResolver, right?
Why aren't these methods part of a CocoonResolver component that would extend Excalibur's SourceResolver with some XML-related features ?
Ok, this could work and might be a cleaner solution. Agreed.
I don't know if this should be an independent component, or one that extends the SourceResolver. But it would really be better to avoid too much code in static methods. And even more code that performs some component lookup under the scenes ;-)
Sylvain (having hard time to awake this morning ;-)
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }