[prev in list] [next in list] [prev in thread] [next in thread]
List: tuscany-dev
Subject: Re: AW: [DISCUSS] How to build your own Tuscany SCA Java distribution
From: "haleh mahbod" <hmahbod () gmail ! com>
Date: 2008-09-26 22:53:49
Message-ID: 2516867c0809261553u7e6f3cc6xa2a15d4a128b13d2 () mail ! gmail ! com
[Download RAW message or body]
Hi,
Link[1] now includes information about modules, categories of modules,
dependencies and some use cases. Please review and help fix it if you see
issues. I would like to link to this page from user and developer
documentation in a week.
[1]:
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Build+Your+SCA+Light+Distribution
Thank you,
Haleh
On Thu, Sep 18, 2008 at 12:51 AM, Simon Nash <nash@apache.org> wrote:
> 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 <enjoyjava@gmail.com<mailto:
>> enjoyjava@gmail.com>> 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: Daniel.Stucky@empolis.com <mailto:Daniel.Stucky@empolis.com>
>> Sent: Wednesday, September 17, 2008 1:23 AM
>> To: user@tuscany.apache.org <mailto:user@tuscany.apache.org>
>> 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:hmahbod@gmail.com <mailto:hmahbod@gmail.com>]
>>
>> Gesendet: Mittwoch, 17. September 2008 03:09
>> An: tuscany-dev@ws.apache.org <mailto:tuscany-dev@ws.apache.org>
>> 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
>>
>>
>>
>>
>
>
[Attachment #3 (text/html)]
<div dir="ltr"><div>Hi, </div>
<div> </div>
<div>Link[1] now includes information about modules, categories of modules, \
dependencies and some use cases. Please review and help fix it if you see \
issues. I would like to link to this page from user and developer \
documentation in a week. </div>
<div> </div>
<div>[1]: <a \
href="http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Build+Your+SCA+Light+Dist \
ribution">http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Build+Your+SCA+Light+Distribution</a></div>
<div> </div>
<div>Thank you, </div>
<div>Haleh<br><br></div>
<div class="gmail_quote">On Thu, Sep 18, 2008 at 12:51 AM, Simon Nash <span \
dir="ltr"><<a href="mailto:nash@apache.org">nash@apache.org</a>></span> \
wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px \
0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div class="Ih2E3d">haleh mahbod wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; \
BORDER-LEFT: #ccc 1px solid"><br>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.<br> 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?<br> <br></blockquote></div>I think we should look at the work \
Graham has done with manyeyes to<br>explore the right relationship between modules \
and bundles.<br><br>The 1 to 1 mapping where every bundle is a module produces a \
very<br> tangled dependency graph that is unlike the dependency graphs of<br>other \
open source projects. Aggregating some maven modules together<br>into the same \
bundle (where this makes sense) can simplify the<br>dependency graph and make it \
easier for users to understand.<br> Also, by reducing the total number of bundles, \
Tuscany will become<br>more consumable for users who need to do repackaging and \
subsetting.<br><br>We can use Graham's tooling to model different combinations \
of<br>modules and bundles without having to make changes in the codebase.<br> When we \
have agreed a suitable relationship between modules and<br>bundles and seen what \
dependency graph this produces, we can change<br>the codebase to reflect this \
structure.<br><br> Simon<br><br> <blockquote class="gmail_quote" \
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> \
<div class="Ih2E3d">Give me a couple of hours to move the table and categorize it \
before you look for an example :)<br> Haleh<br></div> <div class="Ih2E3d">On \
Wed, Sep 17, 2008 at 8:20 AM, Raymond Feng <<a href="mailto:enjoyjava@gmail.com" \
target="_blank">enjoyjava@gmail.com</a> <mailto:<a \
href="mailto:enjoyjava@gmail.com" target="_blank">enjoyjava@gmail.com</a>>> \
wrote:<br> <br> Hi,<br><br> I started to build a table at [1] \
to describe the list of tuscany<br> modules. The purpose is to capture \
the following information:<br><br> 1. Describe the function provided by a \
tuscany module<br> 2. Group tuscany modules by functional \
areas<br> 3. Show dependencies between categories<br> 4. Map \
the SCA programming constructs to the required tuscany modules<br><br> \
Hopefully we can help the users and developers figure out what<br> \
tuscany modules are required whether they start from the SCA PM or<br> \
from the user experience of the Tuscany (develop, manage, deploy,<br> \
and run).<br><br> Back to the module dependencies, there are a few \
tools in maven can<br> help:<br> 1. mvn dependency:tree will \
create a text report for the dependency tree<br> 2. mvn site will \
generate dependenecies.html which list all the<br> dependencies for a \
given module.<br><br> Maybe we should produce these maven reports for \
each of the SCA<br> releases so that the modules can be better \
understood.<br><br> [1]<br> <a \
href="http://cwiki.apache.org/confluence/display/TUSCANYWIKI/What+is+what+for+Tuscany+modules" \
target="_blank">http://cwiki.apache.org/confluence/display/TUSCANYWIKI/What+is+what+for+Tuscany+modules</a><br>
<br> Thanks,<br> Raymond<br><br></div> From: <a \
href="mailto:Daniel.Stucky@empolis.com" target="_blank">Daniel.Stucky@empolis.com</a> \
<mailto:<a href="mailto:Daniel.Stucky@empolis.com" \
target="_blank">Daniel.Stucky@empolis.com</a>> <div class="Ih2E3d"><br> \
Sent: Wednesday, September 17, 2008 1:23 AM<br></div> To: <a \
href="mailto:user@tuscany.apache.org" target="_blank">user@tuscany.apache.org</a> \
<mailto:<a href="mailto:user@tuscany.apache.org" \
target="_blank">user@tuscany.apache.org</a>> <div class="Ih2E3d"><br> \
Subject: AW: [DISCUSS] How to build your own Tuscany SCA Java<br> \
distribution<br><br><br><br> Hi Haleh,<br><br> I'm \
doing something similar for the SMILA project. I want to figure<br> out \
which bundles we need for a basic setup, mostly to minimize 3rd<br> party \
dependencies. See<br> <a \
href="http://wiki.eclipse.org/SMILA/Development_Guidelines/Tuscany_Integration" \
target="_blank">http://wiki.eclipse.org/SMILA/Development_Guidelines/Tuscany_Integration</a>.<br>
As a basis I used the information on<br> <a \
href="http://services.alphaworks.ibm.com/manyeyes/browse/data?q=tuscany" \
target="_blank">http://services.alphaworks.ibm.com/manyeyes/browse/data?q=tuscany</a><br> \
provided by Graham. But this contains only the import dependencies<br> \
between bundles. They don't show dependencies between bundles<br> \
regarding "features". I tried to figure this out manually on a \
try<br> and error basis, so my list of bundles may contain unneeded \
bundles<br> or it might even miss bundles. It would be great if you \
could take a<br> look on this or if I could compare my results with \
yours.<br> Nevertheless, my current setup runs fine and my next goals are \
to<br> provide bundle lists to extend the basic setup with remote \
bindings<br> (rmi and ws).<br><br> Perhaps we can share our \
experiences.<br><br> Bye,<br> Daniel<br><br><br></div> \
Von: haleh mahbod [mailto:<a href="mailto:hmahbod@gmail.com" \
target="_blank">hmahbod@gmail.com</a> <mailto:<a href="mailto:hmahbod@gmail.com" \
target="_blank">hmahbod@gmail.com</a>>] <div class="Ih2E3d"><br> \
Gesendet: Mittwoch, 17. September 2008 03:09<br></div> An: <a \
href="mailto:tuscany-dev@ws.apache.org" target="_blank">tuscany-dev@ws.apache.org</a> \
<mailto:<a href="mailto:tuscany-dev@ws.apache.org" \
target="_blank">tuscany-dev@ws.apache.org</a>> <div class="Ih2E3d"><br> \
Cc: Tuscany Users<br> Betreff: [DISCUSS] How to build your own \
Tuscany SCA Java distribution<br><br> Hi,<br><br> I have seen \
different requests from users wanting to know about<br> Tuscany module \
dependencies so that they can build their own<br> distribution that \
address their requirements. I have started a wiki<br> page[1] to capture \
this information. Once this is complete, I'll<br> move it to \
the website. Please help build this page or contribute<br> by \
asking questions to make sure it answers your questions.<br><br> To start \
with, I'd like to make it clear that this effort is not<br> about how \
Tuscany will build smaller distributions for the next<br> release (s). It \
is only focused on capturing dependencies and<br> helping users \
understand how to build their own tailored distribution.<br><br> Thank \
you for your help,<br> Haleh<br><br> [1]:<br> <a \
href="http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Build+Your+SCA+Light+Distribution" \
target="_blank">http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Build+Your+SCA+Light+Distribution</a><br>
<br><br><br></div></blockquote><br><br></blockquote></div><br></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic