Thilina Buddhika wrote:
Hi,
I have done some slight modifications to the proposal. I will keep on
improving it in next two days, as I am getting more feedback from the
community and I am digging more into Tuscany and Geronimo.
I submitted it as a proposal for GSoC. I will keep the Apache wiki page [1]
up to date with the modifications I will be doing to the proposal, so that
everyone can review it.
thanks!
/ thilina
[1] -
http://wiki.apache.org/general/ThilinaBuddhika/GSoC2008/Tuscany_SCA_Support_in_the_Geronimo_Admin_Console
Hi Thilina,
The proposal looks really good to me! I just have a few minor comments
and ideas.
An SCA domain contains the following:
- SCA contributions
- a domain composite configuring and assembling top level SCA components
- policy configuration
- an allocation of SCA components to nodes/runtimes
An SCA domain admin application should ideally cover these four aspects.
I'll let you think about how you want to stage them in the project.
A comment on "an SCA domain is hosted on an application server runtime
like Geronimo". Although a "domain admin application" can be hosted on a
single app server like Geronimo, an SCA domain is wider than a single
runtime, as SOA solutions usually involve more than a single central JEE
server :), with components distributed on multiple runtimes in a network
(Geronimo, Tomcat, standalone Tuscany, other app servers etc.).
So for a simple and friendly user experience, the domain administrator
should be able to deploy, validate, start/stop components running on
other runtimes in the domain, directly from your Geronimo-based admin
application, without having to juggle with the other admin applications
of the individual servers. I think that it will really make a big
difference in terms of usability.
Hope this helps.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
