> On Tue, 2003-03-18 at 16:25, Unico Hommes wrote:
> [...]
> > For
> > instance the method setContentHandler seems to have been removed
> > completely.
>
> re-added in CVS (both 2.0 and 2.1).
Thanks, that does help.
> Thanks for reporting, and don't hesitate to report any
> further problems
>
On Tue, 2003-03-18 at 16:25, Unico Hommes wrote:
[...]
> For
> instance the method setContentHandler seems to have been removed
> completely.
re-added in CVS (both 2.0 and 2.1).
Thanks for reporting, and don't hesitate to report any further problems
you may have.
--
Bruno Dumon
Hi,
There have been a lot of changes made to DOMStreamer lately and I'm grieved to see
without consideration of backwards compatibity. For instance the method
setContentHandler seems to have been removed completely. I use this class quite
heavily throughout my code and I'm getting e
te
> start/endPefixMapping events, and no xmlns attributes. So it seems only
> logical that the DOMStreamer also shouldn't generate xmlns attributes.
I agree; that is the default SAX2 behaviour. DOMStreamer is currently
emulating namespace-prefixes=true, and as the JaxpPa
tributes is in fact something that
every SAX-generating component in the pipeline should be aware of and
honor. And AFAIK most/all transformers only generate
start/endPefixMapping events, and no xmlns attributes. So it seems only
logical that the DOMStreamer also shouldn't generate xmlns
Hi,
Currently, DOMStreamer.setNormalizeNamespaces() is hardcoded to true.
This fixes the xmlns problem with Xalan, but breaks it with Saxon.
Shouldn't we be doing the
AbstractTextSerializer.needsNamespacesAttributes() check in DOMSerializer
too?
--Jeff
NamespaceNormalizingDOMStreamer doesn't support DOM 1 nodes, which
means that any code using, say, 'setAttribute' instead of
'setAttributeNS' causes cryptic errors like:
...
The DOMStreamer should now also work with elements or attributes created
with crea
r Bruno..
> > > >
> > > > The NamespaceNormalizingDOMStreamer doesn't support DOM 1 nodes, which
> > > > means that any code using, say, 'setAttribute' instead of
> > > > 'setAttributeNS' causes cryptic errors like:
...
> The
alName also when using setAttribute (or createElement for
> > that matter).
> >
> > Since this is not the case, I'll need to improve the DOMStreamer. I'll
> > look into it and let you know more later on.
>
> Thanks. I've put a sample subsitemap that DOMi
, say, 'setAttribute' instead of
> > 'setAttributeNS' causes cryptic errors like:
>
> Ah, didn't know that. I thought that it would automatically assign a
> value to localName also when using setAttribute (or createElement for
> that matter).
>
> Since this i
s like:
Ah, didn't know that. I thought that it would automatically assign a
value to localName also when using setAttribute (or createElement for
that matter).
Since this is not the case, I'll need to improve the DOMStreamer. I'll
look into it and let you know more later on.
>
Probably a question for Bruno..
The NamespaceNormalizingDOMStreamer doesn't support DOM 1 nodes, which
means that any code using, say, 'setAttribute' instead of
'setAttributeNS' causes cryptic errors like:
Failed to execute pipeline.: org.xml.sax.SAXException:
[NamespaceNormalizingDOMStreamer
> I got a strange exception from the DOMStreamer.
>
I have got a similar error. I get this when using the HTMLGenerator.
Upayavira
==
Exception in thread "main" java.lang.reflect.InvocationTargetException:
java.lang.NoSuchMethod
Hi,
I got a strange exception from the DOMStreamer.
10:36:16.501 WARN!! Error for /cocoon/samples/slide/login
java.lang.NoSuchMethodError
at
org.apache.cocoon.xml.dom.DOMStreamer$NamespaceNormalizingDOMStreamer.stream(DOMStreamer.java:218)
at
Unico Hommes wrote:
>
> > > I think that DOMStreamer should only output such a declaration if
> > > the Node to stream is of type Document. Reasonable?
> > >
> > Yes, this is right, so actually you found a bug. Can you enter this
> > as a bug
> > I think that DOMStreamer should only output such a declaration if
> > the Node to stream is of type Document. Reasonable?
> >
> Yes, this is right, so actually you found a bug. Can you enter this
> as a bug in bugzilla, please.
Done.
> > Anyway,
Unico Hommes wrote:
>
> The latest changes to DOMStreamer broke my code in several places
> due to the fact that the NamespaceNormalizingDOMStreamer is
> outputting xml declarations during each stream( Node ) call,
> resulting in xml declarations all over the place in my out
Hi,
The latest changes to DOMStreamer broke my code in several places due to the fact that
the NamespaceNormalizingDOMStreamer is outputting xml declarations during each stream(
Node ) call, resulting in xml declarations all over the place in my output. I think
that DOMStreamer should only
On Saturday 23 November 2002 12:15, Bernhard Huber wrote:
> hi,
> as I have experienced all DOMStreamer usages
> do not invoke enableLogging() for the DOMStreamer object created,
>
> The list of files concerened:
> SourceWritingTransformer.java
> XMLFormTransformer.j
Bernhard Huber wrote:
hi,
as I have experienced all DOMStreamer usages
do not invoke enableLogging() for the DOMStreamer object created,
The list of files concerened:
SourceWritingTransformer.java XMLFormTransformer.java
SourceUtil.java XIncludeTransformer.java
hi,
as I have experienced all DOMStreamer usages
do not invoke enableLogging() for the DOMStreamer object created,
The list of files concerened:
SourceWritingTransformer.java
XMLFormTransformer.java
SourceUtil.java
XIncludeTransformer.java
XMLUtils.java
; wrote:
> I have a DocumentFragment supposebly looking
> like this:
>
>
>
>
>
> Now I try to create SAX events from it:
>
> DOMStreamer streamer = new DOMStreamer(handler);
> streamer.stream(fragment);
>
> Unfortunately this is also fireing the fo
XMLPipe in the CVS.
I also patched DOMStreamer so that it automatically uses EmbeddedXMLPipe
if the streamed node isn't a Document, so it's not necessary to pipe
it's output to EmbeddedXMLPipe.
This is in fact a regression in DOMStreamer since it was rewritten using
JAXP, and that
Ovidiu,
What does this file have? What format is it in?
Thanks,
dims
--- Ovidiu Predescu <[EMAIL PROTECTED]> wrote:
> ATTACHMENT part 1 application/octet-stream
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additiona
> > I have a DocumentFragment supposebly looking
> > like this:
> >
> >
> >
> >
> >
> > Now I try to create SAX events from it:
> >
> > DOMStreamer streamer = new DOMStreamer(handler);
> > streamer.stream(fragment);
&g
Binary data
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
I have a DocumentFragment supposebly looking
like this:
Now I try to create SAX events from it:
DOMStreamer streamer = new DOMStreamer(handler);
streamer.stream(fragment);
Unfortunately this is also fireing the following
events:
[setDocumentLocator]
[startDocument]
[endDocument
27 matches
Mail list logo
