haleh mahbod wrote:
Thank you both for the information that you provided. I'll move the
table that Raymond has into the wiki page as a starting point. Let's
work from one place.
Daniel, you raised a good point that I was not covering on the wiki page
and that is the mapping to bundles. I am assuming that there is a 1 to 1
relationship between modules and bundles. Therefore, as long as we
categorize the modules into what is needed for service construction,
assembly, deployment and management, we have enough information for
users to build their tailored distribution. Is this what you have in
mind or is it at a lower granularity?
I think we should look at the work Graham has done with manyeyes to
explore the right relationship between modules and bundles.
The 1 to 1 mapping where every bundle is a module produces a very
tangled dependency graph that is unlike the dependency graphs of
other open source projects. Aggregating some maven modules together
into the same bundle (where this makes sense) can simplify the
dependency graph and make it easier for users to understand.
Also, by reducing the total number of bundles, Tuscany will become
more consumable for users who need to do repackaging and subsetting.
We can use Graham's tooling to model different combinations of
modules and bundles without having to make changes in the codebase.
When we have agreed a suitable relationship between modules and
bundles and seen what dependency graph this produces, we can change
the codebase to reflect this structure.
Simon
Give me a couple of hours to move the table and categorize it before you
look for an example :)
Haleh
On Wed, Sep 17, 2008 at 8:20 AM, Raymond Feng <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi,
I started to build a table at [1] to describe the list of tuscany
modules. The purpose is to capture the following information:
1. Describe the function provided by a tuscany module
2. Group tuscany modules by functional areas
3. Show dependencies between categories
4. Map the SCA programming constructs to the required tuscany modules
Hopefully we can help the users and developers figure out what
tuscany modules are required whether they start from the SCA PM or
from the user experience of the Tuscany (develop, manage, deploy,
and run).
Back to the module dependencies, there are a few tools in maven can
help:
1. mvn dependency:tree will create a text report for the dependency tree
2. mvn site will generate dependenecies.html which list all the
dependencies for a given module.
Maybe we should produce these maven reports for each of the SCA
releases so that the modules can be better understood.
[1]
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/What+is+what+for+Tuscany+modules
Thanks,
Raymond
From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2008 1:23 AM
To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Subject: AW: [DISCUSS] How to build your own Tuscany SCA Java
distribution
Hi Haleh,
I'm doing something similar for the SMILA project. I want to figure
out which bundles we need for a basic setup, mostly to minimize 3rd
party dependencies. See
http://wiki.eclipse.org/SMILA/Development_Guidelines/Tuscany_Integration.
As a basis I used the information on
http://services.alphaworks.ibm.com/manyeyes/browse/data?q=tuscany
provided by Graham. But this contains only the import dependencies
between bundles. They don't show dependencies between bundles
regarding "features". I tried to figure this out manually on a try
and error basis, so my list of bundles may contain unneeded bundles
or it might even miss bundles. It would be great if you could take a
look on this or if I could compare my results with yours.
Nevertheless, my current setup runs fine and my next goals are to
provide bundle lists to extend the basic setup with remote bindings
(rmi and ws).
Perhaps we can share our experiences.
Bye,
Daniel
Von: haleh mahbod [mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>]
Gesendet: Mittwoch, 17. September 2008 03:09
An: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Cc: Tuscany Users
Betreff: [DISCUSS] How to build your own Tuscany SCA Java distribution
Hi,
I have seen different requests from users wanting to know about
Tuscany module dependencies so that they can build their own
distribution that address their requirements. I have started a wiki
page[1] to capture this information. Once this is complete, I'll
move it to the website. Please help build this page or contribute
by asking questions to make sure it answers your questions.
To start with, I'd like to make it clear that this effort is not
about how Tuscany will build smaller distributions for the next
release (s). It is only focused on capturing dependencies and
helping users understand how to build their own tailored distribution.
Thank you for your help,
Haleh
[1]:
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Build+Your+SCA+Light+Distribution
