I think we should keep the scope of the JIRA. If you want to create a new
sample, with more advanced features (e.g OCC, etc), then I think we should
go with a new and more cool application using REST/AJAX sample app... (btw
there was couple discussions around this before, so I started something,
Hi Luciano,
Please see details below and let me know if we can scope for this, or
it is better to keep the current scope and just add the auto creation of
db.
In current sample we showcase only CRUD and that for only DEBRY.
We can have hooks using JIRA-863 to expand this. i.e. showcase
more
Hi Amita
What I had in mind for Tuscany-863, was more around having a module
responsible for creating the physical databases, populating the tables with
default values and also being able to refresh these values to a original
state. Then the sample applications would check the existence of
Hi All,
Below is the link for the JIRA-
https://issues.apache.org/jira/browse/TUSCANY-863
Using servlet init params, we can expand the current sample (companyweb) to
use
different DAS config xmls for demonstrating different DAS features.
Any thoughts?
Regards,
Amita
