I think Vadim fixed a problem in the XMLFormTransformer, stating that
AttributesImpl has a deadlock problem when the constructor argument is null
or empty.
The fix was:
AttributesImpl atts;
if (attributes == null || attributes.getLength() == 0) {
atts = new AttributesImpl();
} else {
atts = new AttributesImpl(attributes);
}
atts.addAttribute( null, NS_PREFIX, XMLNS_PREFIX + ":" + NS_PREFIX,
"CDATA", NS);
attributes = atts;
}
----- Original Message -----
From: "Torsten Curdt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 25, 2002 6:10 AM
Subject: AttributesImpl
> guys, I need a hand... I'm kinda lost. I am trying to add an attribute in
> a transformer:
>
> startElement(..)
>
> ....
> AttributesImpl newAttributes = null;
> try {
> getLogger().error("creating an attributes copy");
> newAttributes = new AttributesImpl(attributes);
> getLogger().error("adding an attribute");
> newAttributes.addAttribute("","id","id","CDATA", id);
> getLogger().error("added an attribute");
> }
> catch(Throwable e) {
> e.printStackTrace(System.out);
> }
> getLogger().error("passing start");
> super.startElement(uri, name, raw, newAttributes);
> ....
>
>
> But I only see the "added an attribute" once. After the next "adding an
> attriubute" I see nothing more at all. No stacktrace, log message -
> nothing. The browser just waits forever and I don't see anything in the
> logs...
>
> Seems like there is no way back from the "addAttribute" sometimes :(
>
>
> Anyone an idea? I always copied the attributes by hand up to now but AFAIK
> the above is the proposed way of doing it...
>
> Any ideas?
> --
> Torsten
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
