Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] web service as source of Subject API

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] web service as source of Subject API


Chronological Thread 
  • From: Chris Hyzer <>
  • To: Ken LAI <>
  • Cc: Grouper Users <>
  • Subject: RE: [grouper-users] web service as source of Subject API
  • Date: Mon, 23 Feb 2009 09:41:31 -0500
  • Accept-language: en-US
  • Acceptlanguage: en-US

For this request it would probably be best if you could make your own custom
one. If you find a way to make it generic and want to contribute it back,
please do. Depending on your usage of the subject API, you might see
performance issues when using web services as a source...

Regards,
Chris

> -----Original Message-----
> From: Ken LAI
> [mailto:]
> Sent: Monday, February 23, 2009 12:55 AM
> To: Chris Hyzer
> Cc: Grouper Users
> Subject: Re: [grouper-users] web service as source of Subject API
>
> Yes, I am asking for a subject source which is a web service client.
> As in my previous mail, it may be a generic DSML client and map the
> seachType in sources.xml to a DSML search request. Better still, it
> will be good if DSML is just a implementation of generic web service
> subject source interface. We can provide our own if we need custom
> web service client as subject source.
>
> Regards,
> -Ken
>
> On Mon, Feb 23, 2009 at 1:33 PM, Chris Hyzer
> <>
> wrote:
> > Can you please give a spec of what the sources.xml part could look
> like, and what the inputs and outputs of the web service would be? And
> to be clear, are you asking for a subject source which is a web service
> client? Or also a web service operation in grouper WS which would host
> subjects? Or both?
> >
> > Thanks,
> > Chris
> >
> >> -----Original Message-----
> >> From: Ken LAI
> >> [mailto:]
> >> Sent: Monday, February 23, 2009 12:18 AM
> >> To: Chris Hyzer
> >> Cc: Grouper Users
> >> Subject: Re: [grouper-users] web service as source of Subject API
> >>
> >> I understand the difficulty to make a generic web service to be
> >> useful. I suppose you can consider DSML
> >>
> >> http://en.wikipedia.org/wiki/Directory_Service_Markup_Language
> >>
> >> which is standard and LDAP-based. My idea is that any generic web
> >> service will serve my needs as I can connect it to a ESB and do the
> >> message transformation. The endpoint can be file, jdbc, jndi or
> >> another web service.
> >>
> >> Regards,
> >> -Ken
> >>
> >> On Mon, Feb 23, 2009 at 11:34 AM, Chris Hyzer
> <>
> >> wrote:
> >> > There is no plan for that. We do have plans to discuss exposing
> some
> >> Grouper web service operations to search and potentially manage
> >> subjects...
> >> >
> >> > Anyways, for having a builtin subject source which uses web
> services,
> >> it sounds like it would be difficult to make that generic. Each web
> >> service subject source might have a much different API. I would
> just
> >> make your own subject source which implements
> >> edu.internet2.middleware.subject.Source and acts as a web service
> >> client. If you need help coding this, let me know. If we find out
> it
> >> is generic and useful to people, we can add it in.
> >> >
> >> > Regards,
> >> > Chris
> >> >
> >> >> -----Original Message-----
> >> >> From: Ken LAI
> >> >> [mailto:]
> >> >> Sent: Sunday, February 22, 2009 10:27 PM
> >> >> To: Grouper Users
> >> >> Subject: [grouper-users] web service as source of Subject API
> >> >>
> >> >> Currently, the source of Subject API only supports Jdbc and Jndi.
> >> Do
> >> >> you have any plan to add web service as one source of Subject
> API?
> >> >> This gives more flexibility of various sources which only
> interfaces
> >> >> with web service.
> >> >>
> >> >> -Ken
> >> >
> >



Archive powered by MHonArc 2.6.16.

Top of Page