[jdom-interest] non-deterministic behaviour [eg]

skeens skeens at mobile.rogers.com
Wed Apr 11 14:24:42 PDT 2001

Oops. I didn't think about that one.

Now this may be a dumb question but why are you passing in a List to setMixedContent() rather than a JDOM specific container:
public Element setMixedContent(JDOMList mixedContentC);

I'd like to know the reasoning because  I'm coming from a long history of C++ where containers of generic objects is frowned upon. 
-----Original Message-----
From: Jason Hunter <jhunter at collab.net>
Date: Wed, 11 Apr 2001 14:13:54 -0700
To: "Steven D. Keens" <skeens at planetfred.com>
Subject: Re: [jdom-interest] non-deterministic behaviour [eg]

> Element's content.  You could just replace the Element's
> content with the new mixed content.

That has the unfortunate side effect that then we store an external list
within Element.  We can't then protect against illegal objects being
added and such, because mods to the List can happen ungated.


More information about the jdom-interest mailing list