RE: Threading issues Xerces 2.3?

yes, it is not thread-safe.

> -----Original Message-----
> From: Campana Jr., Salvatore J [mailto:sal.campana@xxxxxx]
> Sent: 10 February 2004 14:52
> To: Campana Jr., Salvatore J; xerces-j-user@xxxxxxxxxxxxxx
> Subject: Threading issues Xerces 2.3?
> 
> 
> Has anyone had threading issues with Xerces 2.3? 
> 
> -----Original Message-----
> From: Campana Jr., Salvatore J 
> Sent: Friday, February 06, 2004 3:15 PM
> To: 'xerces-j-user@xxxxxxxxxxxxxx'
> Subject: RE: Help: Xerces 2.3 DeferredElementNSImpl.synchronizeData()
> throws NullPointer
> 
> Yes, I understand that and I check for a null return.
> 
> The problem is that DeferredElementNSImpl.synchronizeData() throws a
> NullPointer because it does not check for null....
> 
> So either there is a bug which has existed for sometime, and still
> exists...or there is some other reason why this occurs....
> 
> Is there even a way to determine if a Node is a Level 1 DOM node at
> runtime?
> 
> Thx! 
> 
> -----Original Message-----
> From: Joseph Kesselman [mailto:keshlam@xxxxxxxxxx]
> Sent: Friday, February 06, 2004 3:10 PM
> To: xerces-j-user@xxxxxxxxxxxxxx
> Subject: RE: Help: Xerces 2.3 DeferredElementNSImpl.synchronizeData()
> throws NullPointer
> 
> 
> 
> 
> 
> localName will be null if the node is a Level 1 DOM node -- ie, was
> produced by a non-namespace-aware DOM builder, or by calling the
> semi-deprecated createElement/createAttribute/setAttribute methods
> rather than the new ...NS versions of those methods.
> 
> ______________________________________
> Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL 
> and more.
> "The world changed profoundly and unpredictably the day Tim 
> Berners Lee
> got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xxxxxxxxxxxxxx
> For additional commands, e-mail: xerces-j-user-help@xxxxxxxxxxxxxx
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@xxxxxxxxxxxxxx
> For additional commands, e-mail: xerces-j-user-help@xxxxxxxxxxxxxx
>