perfsonar development work

[Jason Zurawski <>]

Stijn;




> > > As a workaround, I now create a nmwg:subject element (package 
> > > org.ggf.ns.nmwg.base.v2_0) and then use String operations afterwards 
> > > to change it to perfsonar:subject. 
> >
> > This does not sound very efficient, we can talk about adding what you 
> > need to the element instead of trying to work around the problem in 
> > this manner.
>
> I only need a perfsonar:subject element that can contain a 
> nmwgt:endPointPair.


Because you are trying to accomplish something that our classes won't 
allow, but the BWCTL MP expects, I would suggest not using the java 
classes to generate requests.  I talked with some of the BWCTL 
developers so they know of this problem now.


> > > Likewise for the EndPointPair, I use the EndPointPair from the 
> > > package org.ggf.ns.nmwg.topology.v2_0 and that doesn't result in 
> > > nmwgt:endPointPair, but generates nmwgtopo:endPointPair instead. 
> > > Again I use String operations afterwards to convert that to 
> > > nmwgt:endPointPair.
> >
> > The prefix (nmwgt or nmwgtopo) is really just a shortcut that maps to 
> > a namespace.  The actual prefix doesnt matter, as long as it maps to 
> > the same namespace.  So we could have:
> >
> > xmlns:foo="http://ggf.org/ns/nmwg/topology/2.0/";
> > xmlns:bar="http://ggf.org/ns/nmwg/topology/2.0/";
> > xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/";
> >
> > In the same document, and all prefixes would really mean the same 
> > thing.  Again, using string operations to coerce what you want is 
> > unecessary here.   So you are using the proper classes.
>
> Ok, so if I understand correctly, I can use nmwgtopo:endPointPair 
> instead of nmwgt:endPointPair, if I also change the corresponding 
> namespace at the top?

Right, as long as the namespace above is specified, the prefix does not 
matter.

-jason