We have discussed UDDI, David brought it up on IRC, and I think it is a good idea.
*===================================* * Scott T Weaver * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] * *===================================* > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 24, 2003 5:26 PM > To: [EMAIL PROTECTED] > Subject: RE: Re[2]: JSR-168 Comments > > > > As for a Jetspeed portal dispatching to a Weblogic container, that is > > something that I don't think is covered by the spec. > > The spec covers the contract between the portlet and the container. > > You may want to look into the WSRP for that kind of interoperability. > > Oracle claims to be using WSRP for just that: > http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/PDK/articles/ > OV > ERVIEW.WSRP.JSR168.HTML > > I haven't looked at it very closely, but it seems to be a good approach. > I > could see a Jetspeed Portal server talking to multiple JSR-168 portlet > provider servers via WSRP. Toss in a UDDI directory to register local and > remote portlets and I think things start to get interesting. (Of course, a > full blown UDDI server is overkill for a local registry, but having > linkage > to a UDDI directory sounds like a good thing.) I could see people > standing > up little local portlet servers for nifty portlet apps - email, calendar, > currency conversion, Star Trek quotes, blog service, etc. > > - Jasen. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
