The only potential hiccup to this plan is that we don't version properties.
Suppose the lifecycle handler moves this resource from QA to production,
it's basically changing the version. So v3 was QA, v4 is production. I
want the property lifecycle.status=production associated with v4 and
lifecycle.status=qa associated with v3.
Thoughts?
Paul
Paul Fremantle wrote:
We previously discussed doing lifecycle management externally to the
registry via Mashup. However, I think there is a good opportunity to do
something simple built-in via a URL handler.
The idea is that the lifecycle process itself is represented as a
resource (and therefore a URL). So in REST everything is a resource =>
processes are resources too.
In this case I think that the lifecycle resource is something like:
http://foo.com/a/b/c/d.wsdl;lifecycle
Where this is handled by a URL handler.
If you get this then you get the current lifecycle state (which is also
stored in a property).
Then, if you want to change the state you do a PUT with a different
state. If you have permissions to modify lifecycle (maybe just
permission to move from test->production even) for this resource, then
this happens. The URL handler basically implements the simple flow
between states and decides which jumps are allowable. In fact its just a
simple state machine.
Thoughts?
Paul
Chathura C. Ekanayake wrote:
Hi Paul,
Handlers are executed inside the JDBC registry. At this point the
request has passed the SecureRegistry.
So it is up to the handlers to determine the permissions. A realm
instance is passed to handler constructors, which can be used to
access users, roles and permissions.
All registered handlers will be executed one by one for each request,
until a handler responds with a not null result. Request URL is passed
as a parameter when executing the handlers. Then each handler should
examine the URL and find out whether it can process it or not. If it
can process it, it should return a resulting resource object.
Otherwise it should return null.
Thanks,
Chathura
Paul Fremantle wrote:
What is the permissions model for URL handlers? Who can execute one?
Or is it up to the handler to figure it out? If so how can it access
users/roles?
Paul
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
Office: +1 646 290 8050
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
