Another interesting use case for the SCA domain manager is to deploy SCA
composite applications in the Cloud. Most likely, we are going to create the
"deployable" application out of the SCA contributions and pick a Node from
the Cloud to run it based on the infrastructure capabilities required by the
application.
Thanks,
Raymond
--------------------------------------------------
From: "Raymond Feng" <[email protected]>
Sent: Friday, May 29, 2009 9:02 AM
To: <[email protected]>; <[email protected]>
Subject: Re: Discovery-based SCA Domain for OSGi RFC 119
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Friday, May 29, 2009 5:56 AM
To: <[email protected]>
Subject: Re: Discovery-based SCA Domain for OSGi RFC 119
[[snip]]
I'm not totally thrilled about bringing in the old domain manager code
right now, i wont get in the way but i don't think its helpful. We can
see the code already as its in 1.x and take bits from there if
required so i don't see the need to bring it up in 2.x yet. Why i
don't like this is because it comes with a large amount of baggage and
to get it going would mean taking all that on right away without
getting any sort of common understanding or consensus on what we need
or are trying to support, and as we've seen over and over it can be
real hard to remove or substantially redesign something once its
committed. I was hoping this time we'd take small incremental baby
steps getting consensus and specific testcases working one by one.
As we discussed on the other thread, the SCA domain manager is useful to
provide an administrative view of the
SCA domain. It also provides the capability to assemble contributions into
one or more deployable composite applications
that can be run Nodes. Even though the 1.x SCA domain manager works in a
static manner, the core of the functions
can be reused in the case that some of the metadata are dynamically
discovered or updated. The idea to model related
pieces in the SCA domain as RESTful resources are also very appealing too.
I personally +1 to bring it up to 2.x.
[[snip]]
- The domain is running within a single JVM so it doesn't need any
remote distribution technology which helps keep things simple
Yes or no. SCA domain is naturally distributed. Modeling it after a single
JVM may prevent us seeing the big picture.
I'd like to look at this but it can be done outside of this tomcat
exercise.
Sure i agree and i'd planned on in parallel to the tomcat work
continuing to also using the two-nodes-itest as a very simple JSE
testbed, and we come come up with more simple testcases as the
scenarios are developed.
+1 to decouple the Tomcat work from the SCA domain. I'm leaning to use two
nodes approach.
...ant
