Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Help needed for the design of the authorization request

Subject: perfsonar development work

List archive

Re: [pS-dev] Help needed for the design of the authorization request


Chronological Thread 
  • From: Cándido Rodríguez Montes <>
  • To: Jeff W.Boote <>
  • Cc: " List" <>, Zurawski Jason <>
  • Subject: Re: [pS-dev] Help needed for the design of the authorization request
  • Date: Wed, 4 Jun 2008 17:09:25 +0200

Hi Jason and Jeff,

El 03/06/2008, a las 18:35, Jeff W. Boote escribió:


On Jun 3, 2008, at 9:23 AM, Jason Zurawski wrote:


Cándido;



I think the request should be XML and not 'string' data. This would allow services/clients to use the full set of XML api's to look at requests/responses. (Otherwise, why are we messing with this bloated XML stuff anyway?)


Yes, I agree with you but I don't know how to do it. I can have the Document or the String of the <Request> element but how I integrate it in a nmwg message? I guess I should use the org.ggf.ns.nmwg.base.v2_0.Element class but it wasn't work.

So, any help for adding the <Request> element inside an <aa:subject> element? :-)


To do this you would need to add the necessary objects and handlers to the nmwg object structure.



Or stop using the object marshaling model and just use dom directly or perhaps a push-pull model... Not sure where that is on the Java developers plans, but the marshaling model has obviously shown itself to be a pain in more ways than one and I don't think we should be crafting message formats due to this implementation limitation. (Especially given the fact that the main Java developers have already expressed the wish to remove it.)


I think you can use dom directly when you're generating a nmwg message for sending to a perfSONAR service. But, when a pS service receives it, it will launch an exception because it doesn't know how to model the message with nmwg objects. Please, fix me if I'm wrong...


Probably the short-term solution in the Java implementation is as Jason says: Add the needed objects into the nmwg library.


But, in this case, I prefer to use 'string' data. Why? Because I don't want to model all the XACML objects into the nmwg library. Too many objects!
I agree with you that the request should be XML and not 'string' data, but so far, I don't see the way of doing it.

Regards


jeff



--
Cándido Rodríguez Montes E-mail: 
Middleware warrior Tel:+34 955 05 66 13
Red.ES/RedIRIS
Edificio CICA
Avenida Reina Mercedes, s/n
41012 Sevilla
SPAIN







Archive powered by MHonArc 2.6.16.

Top of Page