You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Antonio Gallardo <ag...@agsoftware.dnsalias.com> on 2003/12/31 04:18:40 UTC
Re: cvs commit:
cocoon-2.1/src/blocks/woody/java/org/apache/cocoon/woody/utilDomHelper
.java
Vadim Gritsenko dijo:
> antonio@apache.org wrote:
>
>> +import org.apache.xerces.dom.NodeImpl;
>> +import org.apache.xerces.parsers.DOMParser;
>> +import org.apache.xerces.xni.Augmentations;
>> +import org.apache.xerces.xni.NamespaceContext;
>> +import org.apache.xerces.xni.QName;
>> +import org.apache.xerces.xni.XMLAttributes;
>> +import org.apache.xerces.xni.XMLLocator;
>> +import org.apache.xerces.xni.XNIException;
>>
>>
>
> Can somebody clarify - does it mean that woody works only with xerces? I
> have not seen this limitation mentioned on the prominent place, may be
> I've just missed it...
Don't know. I just expanded this import:
import org.apache.xerces.xni.*;
See:
http://marc.theaimsgroup.com/?l=xml-cocoon-cvs&m=107283798425627&w=2
Best Regards,
Antonio Gallardo
Re: cvs commit: cocoon-2.1/src/blocks/woody/java/org/apache/cocoon/woody/utilDomHelper
.java
Posted by Marc Portier <mp...@outerthought.org>.
Marc Portier wrote:
> hm, this comes from the DOMHelper, right?
> (a yes, the subjectline says so)
>
> I remember a discussion in the office, way back when Bruno was working
> up to a first commit-worthy version of Woody...
>
> The decission was between using SAX or DOM for the building of the
> form-model... the arguments at the time were basically:
>
> - pro SAX: location information in the API to allow pointing out errors
> in config files in error-messages
>
> - contra SAX: no streaming required and more difficult then needed for
> this type of thing...
>
> he decided to use DOM, and get the location info from the xerces
> specific implementation of DOM (there should be a line in there that
> does that)
>
Well, I just checked, there is a complete DOMParserer subclass that does
that in fact...
> He's on holiday until monday and can verify then, but I'm pretty sure
> memory serves correctly...
>
so
the answer is: 'yes, depends on xerces'
the reason is: 'providing location information'
the remaining issue: 'where should it be mentioned? gump.xml? docos?'
regards,
-marc=
> regards,
> -marc=
>
>
> Vadim Gritsenko wrote:
>
>> Antonio Gallardo wrote:
>>
>>> Vadim Gritsenko dijo:
>>>
>>>
>>>> antonio@apache.org wrote:
>>>>
>>>>
>>>>
>>>>> +import org.apache.xerces.dom.NodeImpl;
>>>>> +import org.apache.xerces.parsers.DOMParser;
>>>>> +import org.apache.xerces.xni.Augmentations;
>>>>> +import org.apache.xerces.xni.NamespaceContext;
>>>>> +import org.apache.xerces.xni.QName;
>>>>> +import org.apache.xerces.xni.XMLAttributes;
>>>>> +import org.apache.xerces.xni.XMLLocator;
>>>>> +import org.apache.xerces.xni.XNIException;
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> Can somebody clarify - does it mean that woody works only with
>>>> xerces? I
>>>> have not seen this limitation mentioned on the prominent place, may be
>>>> I've just missed it...
>>>>
>>>
>>>
>>>
>>> Don't know. I just expanded this import:
>>>
>>> import org.apache.xerces.xni.*;
>>>
>>>
>>
>> I know; I had noticed this issue when you expanded the import. The
>> question was to those who are in the know :-)
>>
>> Vadim
>>
>>
>
--
Marc Portier http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/mpo/
mpo@outerthought.org mpo@apache.org
Re: cvs commit: cocoon-2.1/src/blocks/woody/java/org/apache/cocoon/woody/utilDomHelper
.java
Posted by Marc Portier <mp...@outerthought.org>.
hm, this comes from the DOMHelper, right?
(a yes, the subjectline says so)
I remember a discussion in the office, way back when Bruno was working
up to a first commit-worthy version of Woody...
The decission was between using SAX or DOM for the building of the
form-model... the arguments at the time were basically:
- pro SAX: location information in the API to allow pointing out errors
in config files in error-messages
- contra SAX: no streaming required and more difficult then needed for
this type of thing...
he decided to use DOM, and get the location info from the xerces
specific implementation of DOM (there should be a line in there that
does that)
He's on holiday until monday and can verify then, but I'm pretty sure
memory serves correctly...
regards,
-marc=
Vadim Gritsenko wrote:
> Antonio Gallardo wrote:
>
>> Vadim Gritsenko dijo:
>>
>>
>>> antonio@apache.org wrote:
>>>
>>>
>>>
>>>> +import org.apache.xerces.dom.NodeImpl;
>>>> +import org.apache.xerces.parsers.DOMParser;
>>>> +import org.apache.xerces.xni.Augmentations;
>>>> +import org.apache.xerces.xni.NamespaceContext;
>>>> +import org.apache.xerces.xni.QName;
>>>> +import org.apache.xerces.xni.XMLAttributes;
>>>> +import org.apache.xerces.xni.XMLLocator;
>>>> +import org.apache.xerces.xni.XNIException;
>>>>
>>>>
>>>>
>>>
>>> Can somebody clarify - does it mean that woody works only with xerces? I
>>> have not seen this limitation mentioned on the prominent place, may be
>>> I've just missed it...
>>>
>>
>>
>> Don't know. I just expanded this import:
>>
>> import org.apache.xerces.xni.*;
>>
>>
>
> I know; I had noticed this issue when you expanded the import. The
> question was to those who are in the know :-)
>
> Vadim
>
>
--
Marc Portier http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/mpo/
mpo@outerthought.org mpo@apache.org
Re: cvs commit: cocoon-2.1/src/blocks/woody/java/org/apache/cocoon/woody/utilDomHelper
.java
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Antonio Gallardo wrote:
>Vadim Gritsenko dijo:
>
>
>>antonio@apache.org wrote:
>>
>>
>>
>>> +import org.apache.xerces.dom.NodeImpl;
>>> +import org.apache.xerces.parsers.DOMParser;
>>> +import org.apache.xerces.xni.Augmentations;
>>> +import org.apache.xerces.xni.NamespaceContext;
>>> +import org.apache.xerces.xni.QName;
>>> +import org.apache.xerces.xni.XMLAttributes;
>>> +import org.apache.xerces.xni.XMLLocator;
>>> +import org.apache.xerces.xni.XNIException;
>>>
>>>
>>>
>>>
>>Can somebody clarify - does it mean that woody works only with xerces? I
>>have not seen this limitation mentioned on the prominent place, may be
>>I've just missed it...
>>
>>
>
>Don't know. I just expanded this import:
>
>import org.apache.xerces.xni.*;
>
>
I know; I had noticed this issue when you expanded the import. The
question was to those who are in the know :-)
Vadim