When I started to implement the new composite assembly model I felt a
need to adjust a little the folder structure under the Tuscany system
root, did half of it, which triggered some questions :) This is a new
thread to discuss these changes.
Here's what we had in M1:
$TUSCANY_SCAPP_SYSTEM_ROOT/ <-- your Tuscany-system-root
subsystems/
CalculatorSubsystem/
sca.subsystem <-- creates and configures the Calculator
module component
modules/
Calculator <-- the Calculator module and code
sca.module
other artifacts, *.so, *.wsdl, *.xsd etc.
Now that the spec has removed subsystem, module and fragment, and
generalized the use of composites, here's what I'd like to propose:
deploy/ <-- your Tuscany-system-root
configuration/
CalculatorApp.composite <-- creates the Calculator component, we
don't need sub-folders here since we can give meaningful name to
composite files now
packages/
Calculator <-- the Calculator composite and code
Calculator.composite
other artifacts, *.so, *.wsdl, *.xsd etc.
- Configuration contains the composites included in your system creating
and configuring your top level components.
- Packages contains all your other development artifacts (not
necessarily just composites that's why I'm proposing packages/ instead
of modules/ or composites/).
- I think that the samples should use consistent naming convenvions, but
you should also be able to pick the names you want for your folders and
artifacts and have Foo/Bar.composite containing <composite name="Abc"/>
for example.
Any thoughts?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
