cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira ...@upaya.co.uk>
Subject Re: Using the standard Jaxp parser in Cocoon.java
Date Tue, 04 Jan 2005 14:31:34 GMT
Sylvain Wallez wrote:

> Upayavira wrote:
>
>> Carsten Ziegeler wrote:
>>
>>> Sylvain Wallez wrote:
>>>
>>>> Hi all,
>>>>
>>>> Doing some cleanup on the component management, I went into 
>>>> o.a.c.Cocoon where a bootstrap service manager is created and setup 
>>>> only to handle the case where the user would like to use parser 
>>>> different from the default system-wide one. This alternate parser 
>>>> is specified using the "org.apache.excalibur.xml.sax.SAXParser" 
>>>> system property.
>>>>
>>>> This looks to me like some old legacy code that was written before 
>>>> JAXP was finalized and before XML parsers were shipped with the JDK.
>>>>
>>>> I'd like to remove this as it seems IMO useless and complicates the 
>>>> startup code.
>>>>
>>>> Thoughts? Is anyone having a good use case for this feature?
>>>>
>>> Believe it or not, I had exactly the same idea today as I looked at
>>> the Cocoon class...so +1 for removing.
>>
>>
>>
>> Will this work on Java 1.3? Or are you just talking about Cocoon 2.2?
>
>
>
> I changed it (just to check -- not committed yet) in 2.2, but I see no 
> reason why it shouldn't work with 1.3 when a JAXP implementation 
> exists in the classpath. And Cocoon does provide one implemenation 
> with Xerces.

+1 then!

Regards, Upayavira

Mime
View raw message