+1 for me
Thanks,
Andrew
Andrew Eberbach
Autonomic Computing
(919) 254-2645
T/L: 444-2645
[EMAIL PROTECTED]
| "Hawkins, Joel"
<[EMAIL PROTECTED]>
09/01/2006 01:30 PM
|
|
Definite +1. It's really great to see this advancing so far ahead of our
expected schedule.
Joel
-----Original Message-----
From: Daniel Jemiolo [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 31, 2006 4:54 PM
To: [email protected]
Subject: Re: WS-ResourceTransfer implementation
Hi Mohammad,
Thanks for contributing this - we probably wouldn't have started this
until next year given all the work we're doing on WSDM 1.1 and the
current
release, so this is very helpful. Given the status of the WSRT spec, I'd
say we should separate this from the other modules in the trunk and
document them as "preview"/"experimental"/"beta"/etc. I'd like the team
to
be able to focus on support for WSRF/WSN/WSDM in 2.x while still making
this stuff available to any early adopters. I think we're a ways off
from
the spec being ratified, so we have a while before we have to figure out
how/when to provide full support for it.
Here's my +1 for accepting the code as an addition to the build. I'd ask
the other committers to please vote and/or send their thoughts.
Dan
Mohammad N Fakhar/Raleigh/[EMAIL PROTECTED] wrote on 08/31/2006 03:49:51 PM:
>
> Hi all,
>
> A few months ago, there was talk on muse-dev of implementing the
> reconcilation specs
> authored by Microsoft, HP, Intel, and IBM, and how to align them with
WSRF
> and WSDM.
> The first reconcilation spec, WS-ResourceTransfer, was published
today;
> as a member
> of the team that worked on this spec, I have been working on a
reference
> implementation
> of it and would like to contribute it to Muse. I'm not sure how/where
it
> should fit but
> I figure the development team can help with that. I've opened a JIRA
item
> with the code:
>
> https://issues.apache.org/jira/browse/MUSE-86
>
> Here's a link to the spec:
>
> http://www.ibm.com/developerworks/library/specification/ws-wsrt/
>
> Since the WS-RP and WS-RT specifications are semantically similar , I
> created an early
> reference implementation of WS-RT, based on Apache Muse. The
> implementation is primarily
> a delegation layer, which serves WS-RT requests by delegating to Muse
> WS-RP capabilities.
> For example, a WS-RT Put request with QName dialect maps to a WS-RP
> SetResourceProperties
> operation with a Property dialect. Some WS-RT operations, however, do
not
> map directly
> to WS-RP operations, for example a WS-RT Put operation with XPath
dialect
> has no equivalent in WS-RP. For such operations, the delegation layer
> pre-processes the WS-RT request and breaks it down into WS-RP
operations
> that can be processed by WS-RP capabilities.
>
> The delegation layer is designed so that Muse WS-RT Web services can
be
> exposed over WS-RT dialects just by adding capabilities to deployment
> descriptors.
> This will allow developers to experiment with WS-RT with minimal
effort
> and can be
> used as a co-existence strategy for those resources that may need to
> support
> both WS-RP and WS-RT clients.
>
> In addition to the server side delegation layer, I wrote a WS-RT
client
> side API that
> is symmetric to the WS-RP client API. It enables WS-RT clients to
> programatically invoke
> WS-RT webservices using WS-RT concepts such as fragments, expressions
and
> metadata.
>
> I've also added a sample project that is similar to the existing
samples
> and a
> command line demo of it.
>
> The sample takes a little bit of manual work to build and deploy right
> now; if you want to see it in action
> via a web app, an alphawork demo is available as well:
> http://wsi.alphaworks.ibm.com/wsrt/
>
>
> thanks,
> Mohammad N. Fakhar
> IBM Software Group Strategy
> Emerging Standards
> Research Triangle Park, NC USA
> [EMAIL PROTECTED]
> Phone: (919) 254-2104
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
