On 2/14/11 1:38 PM, Darran Lofthouse wrote:
On 02/14/2011 07:27 PM, Jason T. Greene wrote:
> Requirement "It will be possible to determine the dependencies between
> services."
>
> Comments: "This will allow tooling to prevent invalid combinations. The
> domain and tooling will error, or attempt to prevent broken
> dependencies."
For this requirement what is a 'service'?
We have subsystems and we have deployments but the dependencies of the
subsystems can be very much affected by the deployments e.g. does the
EJB3 subsystem depend on JCA if it has no deployments that use a JCA
resource? Same goes for a web deployment, you could want to just deploy
some simple servlets or you could want to deploy an app that uses EJBs
and has some database access.
The requirement is just in relation to altering the domain
configuration, and preventing bad profiles. Deployments could be a
problem but those can have failures at deploy time (which would be
resolved by adding the missing subsystem).
I think the rule should be that we only prevent non-working
configurations. E.g if there is a way to make EJB work without JCA there
should be no reason to disallow that.
--
Jason T. Greene
JBoss, a division of Red Hat