> JAXR comes in more in the service discovery scenario
This is a very, very cool idea. However, I see it a more of "nice to have" then a "needed to work" option. A formal proposal on something like this would be nice to have, so it doesn't get lost in the shuffle.
> 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.
I'll try to mold it into a formal proposal once we have it fully implemented (next quarter? in Jetspeed 1.4).
Turns out it is pretty close to a must have sort of thing for our large enterprise. We have ~30+ dev groups doing portal development against a web services tiered model. :0 (I personally prefer local, commonly shared libraries and skipping the whole SOAP overhead but what do I know...)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
