I'd like to start using the implementation-data extension in the Store
sample, first to have the contents of the sample Catalog in a database,
then maybe extend it to the ShoppingCart as well.
In that context, I'm thinking about evolving the implementation-data
extension a little, along the following lines:
- One component per database so we don't have to repeat the database
connection info in each component.
- One service per table, named like the table, so we don't have to know
a fixed service name and also when you look at the service it's obvious
which table it works with.
- Experiment with using JDBC directly, as we already have
implementation-das to leverage the DAS/SDO runtime.
- Taking and returning an StAX XMLStreamReader, as it'll be sufficient
(and really lightweight) if the Tuscany databinding framework can
convert that XML data to whatever databinding is needed by other
components in the assembly.
Thoughts?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
