Vinay Chandran wrote:
>>tres cool. Does seem like it could use a little
>>polishing =)
>>
>>
>>
>Sure it does .
>
>
>>I definately have a need for stuff like this. I've
>>been thinking about
>>using merlin's Lifecycle Extensions for integration
>>with Axis...this is
>>somewhat similar...
>>
>>
>>
>I too do have similar needs.
>
I'm been thinking about this but not in terms of the extension
mechanisms. In Merlin there is this thing called Resource. A Resource
is basically a utility class that encapsulates a component profile and
lifestyle. It provides access to the component meta model (but that
could change in the future to be just the services it represents). I've
been playing around with plug-in Resource factories that let you delcare
how a service is published. This allows for the potential to publish
the defintion AND service access point without actually activating the
component. With something liker Axis, a valuable feature would be to be
able to build a SOAP definition of a service based on the resource,
then, a client reading the SOAP deifntion would actually invoke a
service against the resource - which would then handle the service
activation (if not already activated). I have something along these
linked already working over CORBA - ability to publish service
descriptions but delaying object activation until a client actually
needs to use the service in question.
Cheers, Steve.
>
>Vinay .
>
>
>
>
>__________________________________________________
>Do you Yahoo!?
>New DSL Internet Access from SBC & Yahoo!
>http://sbc.yahoo.com
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
>
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
