[jdom-interest] First pass at Namespace revision[eg]

Jochen Strunk strunk at signal7.de
Fri Mar 30 02:09:05 PST 2001

What was wrong with the use case in the first part of my mail (web 
framework) ? That's a real life example how we use jdom. It would really 
benefit from set namespace. It would also benefit from having support for 
default namespaces.


At 22:12 29.03.2001 -0800, you wrote:
> > As I understand this happens because in your namespace model a child's
> > namspace should not be affected by its location in the document. So the
> > next step to achieve the wanted result would be traversing all child
> > elements of element and assigning them the foo namespace. Its obvious that
> > I do not want to use getCopy for this task since it would unnecessarily do
> > a deep copy. I would need to implement my own copy method which gives me
> > the same element in the foo namespace.
> >
> > This is not very straightforward any more :-(
>I'm sympathetic that we may want a setName() and setNamespace() pair of
>methods to make it easier to modify all aspects of the doc
>programatically.  I talked with Elliotte at the O'Reilly conference this
>afternoon and he's not convinced yet.  What we need is a compelling
>example where it's appropriate to change the namespace of all elts in a
>document programatically.  If we have that, I think Elliotte our
>strongest naysayer will be convinced.  So...  What's your use case?
>To control your jdom-interest membership:

(-) Jochen Strunk
(-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH
(-) Brüder-Knauß-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665402, Fax: 06151 665373
(-) strunk at signal7.de, www.signal7.de

More information about the jdom-interest mailing list