Re: [xmlc] DocumentLoaderImpl Cache Keys

At 12:54 AM 1/23/2007, you wrote:
> Because I store some XHTML in my database that I later insert into 
> my pages.  So I have to convert it into DOM first and then 
> appendChild it into my XMLC page.  I found the DOMParser you were 
> providing in the xerces jar and used that.

I recommend you either use JAXP or DOM3 LS instead of DOMParser to 
create a DOM.  XMLC itself gets very down and dirty with the DOM 
implementation.  It provides lots of extra power, but ties the code 
very closely to the implementation.  Your application code shouldn't 
follow this pattern unless you have very particular needs that can't 
be met by the standard API's.

Jake

> Erik
>
> On Jan 23, 2007, at 4:56 AM, Jacob Kjome wrote:
>
> > I'm curious, why do you need to use DOMParser?  That should be 
> > transparent to you.
>
>
> --
> You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx 
> mailing list.
> To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws



--
You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing list.
To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws