I've been looking into
https://issues.apache.org/jira/browse/TUSCANY-2393 and pondering the
requirement for:
"- complete generation of an AtomPub workspace/service document, for a
service, component or a group of related components (potentially in a
composite)"
I see the value of this requirement, but I would like to hear what other
folks might like to see. I can envision this type of document being
useful for publishing information about an SCA composite or group of
composites on a node.
For example with the store.composite of the Tuscany sample-store, I
might expect a service document like this:
<?xml version="1.0" encoding='utf-8'?>
<service xmlns="http://www.w3.org/2007/app";
xmlns:atom="http://www.w3.org/2005/Atom";>
<workspace base="uiservices/store.html" lang="EN">
<atom:title>Store</atom:title>
<collection href="Catalog" >
<atom:title>Fruit Catalog</atom:title>
<accept>application/atom+xml;type=feed</accept>
</collection>
<collection href="ShoppingCart/Cart" >
<atom:title>Shopping Cart</atom:title>
<accept>application/atom+xml;type=feed</accept>
</collection>
<collection href="ShoppingCart/Total" >
<atom:title>Shopping Total</atom:title>
<accept>application/atom+xml;type=entry</accept>
</collection>
</workspace>
</service>
Is this close to what people have in mind? This is useful for workspace
service discoveries. What other sorts of uses do people have in mind for
this requirement?
--
Thanks, Dan Becker
