perfsonar development work

[Guilherme Fernandes <>]

Michael Bischoff wrote:
> Hello Guilherme,
>
> Afaik I could tell your right, I like to stray away from the nmwg classes, so 
> I haven't
> traced it down completely.
> However as far as using parameters goes; according to the page that approach 
> is deprecated?
>
>   
Yes, it has been deprecated for the new gLS summarization process. I 
don't think this has received any attention for the current base, Maciej 
was dealing with it in the new base, but this doesn't helps things as 
the new base is only scheduled for September (if I recall correctly from 
the psdev meeting).

Added Roman and Maciej to the discussion. This can be quickly fixed in 
the nmwg classes, but I'm still not sure if it hasn't been addressed 
already in some way.

regards,
Guilherme

> regards,
> Michael.
>
>   
> > Michael Bischoff wrote:
> >
> >     
> > > Hello all,
> > >
> > >
> > >
> > >       
> > Hi,
> >
> >     
> > > We have issues with registering to the LS.
> > >
> > >
> > > We use a InformationContextServiceContent and
> > > InformationContextServiceContent#getServiceContent returns an array with one 
> > > element: a
> > > String containing
> > >
> > >
> > > <nmwg:metadata ...>
> > > <..:subject>
> > > ...
> > > </..:subject>
> > > <eventType> .. </eventType>
> > > <eventType> .. </eventType>
> > > <eventType> .. </eventType>
> > > </nmwg:metadata>
> > >
> > >
> > > I checked it in the debugger that it returns the right string.
> > >
> > >
> > > the arrays gets passed around and is called by
> > > LSRegisterRequestGenerator#generateRequestMessage() where it is pushed into 
> > > nmwg classes
> > > in some awkward way and the information is lost. Looking at the metadata nmwg 
> > > class it
> > > seems it can only hold one eventType. (but not one shows up unless I put it 
> > > in a speparate
> > > metadata block.)
> > >
> > > Or format is similar(minus parameters) to example one here:
> > > http://wiki.perfsonar.net/jra1-wiki/index.php/LS_Registration_messages
> > > (Which is the current spec right now, right?)
> > >
> > >
> > > Since I hardly think we are the only with a service that supports more then 
> > > one eventype
> > > and I wonder how other services got this to work, anyone who can elaborate on 
> > > this?
> > >
> > >
> > >
> > >       
> > Multiple eventTypes are not supported in the current base.AFAIK, MA's,
> > which I think that right now are the only one's registering multiple 
> > eventTypes, use the
> > supportedEventType parameter to register multiple eventType.
> >
> > regards, Guilherme
> >
> >     
> > > regards,
> > >
> > > Michael
> > >
> > >
> > >
> > >       
> >     
>
>
>