On Thursday, September 11, 2003, at 01:35 PM, Todd Kuebler wrote:
Cool, happy to hear about J2 registries going to rdbms, although I hope there is some abstract service registry layer on top of the implementation so it isn't so tied directly to a particular technology or schema.
JAXR comes in more in the service discovery scenario, which is actually what I was thinking about, ie discovering local/remote content in portlets/webservices/rss/etc. I really see the portal as both a consumer and producer (individual portlet xml, wsrp,etc) of network services (ok, web services, but I hate that) of all types and was thinking about where JAXR/xml registries/xml repositories fit in that capacity.
I was thinking of an abstract service layer that can deal with all of those service types and map them smoothly in/out of portlets. One of our teams has something like this we are considering for use here at work, once that is more tangible I'll try to communicate it again > here.
Sorry for my vagueness and poor communication skills. :(
Here is something more concrete and less muddled purhaps.
Imagine the following startup scenario for the portion of jetspeed code that currently loads the portlet registries.
1) ask the service registry for all content producers available to this portal (JAXR query).
2) service registry returns 3 nodes
a) local portlets (what is in xreg currently, could still be stored locally...)
b) remote portlets from portal B this portal has permission to use
c) web services that have compatible data types for some generic
web services portlet (similar to the current dbbrowser portlet)
3) these are all merged into the 'service registry' and portlets are created for each entry to produce the content
Have you looked at WSRP? It has a framework for consumer to discover producer capabilities
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] +01 707 773-4646 +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
