|
| Re: Deployment in SCA and SCA Tools [message #538282 is a reply to message #537755] |
Mon, 07 June 2010 08:21  |
|
Hello Hugo,
My answers below.
Le 03/06/2010 16:50, Hugo A. Garcia a écrit :
> Hi
>
> I would like to know if the deplyment of domain occurs in one or two or
> multiple phases. What follows are some thoughts from S. Roderick:
>
> <comment>
>
> A one phase deployment works like this:
>
> <code>
> load deployment file
> for all components listed in deployment file
> configure component
> if any component failed to configure then exit
> for all components listed in deployment file
> start component
> ...
> </code>
>
> The problem comes when one of your components is say a file logging
> component attached to the real-time logging, and some other component
> fails to configure. You get no logging output as the logging component
> hasn't had a chance to start yet!
>
> Multiphase:
>
> What you need is to be able to completely configure and start all your
> logging _service components_, and then attempt to configure/start your
> application components
>
> </comment>
>
> ------
>
> How does deployment work in SCA?
Honestly, I am not sure there is a unique way.
IMO, deployment depends on the target platform.
Currently, we try to support 3 different platforms: Apache Tuscany, OW2
FraSCAti and Fabric3. You should see with them directly for this question.
> How does the SCA Tools support deployment?
SCA Tools support a very basic deployment.
We do not support the notion of "domain", since only Tuscany implemented
it and documented it. And we do not really support SCA servers, but SCA
runtime libraries (meaning we expect an SCA application with the runtime
libraries in its class path).
What we provide is simply a convenient way to deploy an SCA application
on a SCA runtime. But it is only intended for development, as it does
not offer many options and interactions with the runtime.
A more advanced solution would go through the definition of servers in
Eclipse, just like Tomcat and JEE servers. This would help in debugging
and following execution. Once again, that would still be intended for
development steps.
In production steps, Eclipse should not be used. People generally prefer
scripts to deploy (ANT, Maven). Given our current priorities, SCA server
support (something similar to what exist for Tomcat) would rather wait
for external contributions. It is not on our own roadmap.
Regards,
Vincent.
|
|
|
| Re: Deployment in SCA and SCA Tools [message #577302 is a reply to message #537755] |
Mon, 07 June 2010 08:21 |
|
Hello Hugo,
My answers below.
Le 03/06/2010 16:50, Hugo A. Garcia a écrit :
> Hi
>
> I would like to know if the deplyment of domain occurs in one or two or
> multiple phases. What follows are some thoughts from S. Roderick:
>
> <comment>
>
> A one phase deployment works like this:
>
> <code>
> load deployment file
> for all components listed in deployment file
> configure component
> if any component failed to configure then exit
> for all components listed in deployment file
> start component
> ...
> </code>
>
> The problem comes when one of your components is say a file logging
> component attached to the real-time logging, and some other component
> fails to configure. You get no logging output as the logging component
> hasn't had a chance to start yet!
>
> Multiphase:
>
> What you need is to be able to completely configure and start all your
> logging _service components_, and then attempt to configure/start your
> application components
>
> </comment>
>
> ------
>
> How does deployment work in SCA?
Honestly, I am not sure there is a unique way.
IMO, deployment depends on the target platform.
Currently, we try to support 3 different platforms: Apache Tuscany, OW2
FraSCAti and Fabric3. You should see with them directly for this question.
> How does the SCA Tools support deployment?
SCA Tools support a very basic deployment.
We do not support the notion of "domain", since only Tuscany implemented
it and documented it. And we do not really support SCA servers, but SCA
runtime libraries (meaning we expect an SCA application with the runtime
libraries in its class path).
What we provide is simply a convenient way to deploy an SCA application
on a SCA runtime. But it is only intended for development, as it does
not offer many options and interactions with the runtime.
A more advanced solution would go through the definition of servers in
Eclipse, just like Tomcat and JEE servers. This would help in debugging
and following execution. Once again, that would still be intended for
development steps.
In production steps, Eclipse should not be used. People generally prefer
scripts to deploy (ANT, Maven). Given our current priorities, SCA server
support (something similar to what exist for Tomcat) would rather wait
for external contributions. It is not on our own roadmap.
Regards,
Vincent.
|
|
|
Powered by
FUDForum. Page generated in 0.02156 seconds
] 
Search
Help
Register
Login
Home
