When we talk about dependent SUs.
Is it possible in servicemix to analyze what services a SU uses? I would
like to create a dependency graph for the SOA governance.
So we can analyze what would happen if we undeploy or change a service.
This should also be extended to pure clients. It would be nice if a client
could publish what services it needs to run properly. Are there already
any standard ways to do this in servicemix or even in JBI in general?
Christian
Guillaume Nodet schrieb:
On 11/15/06, Matthias von Arx <[EMAIL PROTECTED]> wrote:
Yes, a service schould be more stable than a bpel process -- if you
want to
invoke for example a new service from an existing pbel process you
have to
undeploy all services if all are included in one SA.
Or for example there are some SA's with included jsr181 and ode SU's
and you
want to deploy a new ode SU using some of the existent services, what
will
you do then?
In theory, if you (re)deploy a SU which has the exact same content
than a previously deployed SU, the JBI container should not modify it.
Unfortunately, this is not implemented in ServiceMix.
While I agree with your use case, I think this should be handled by
the JBI container and components somehow. In the mean time ...
For some cases a separate SA makes really sense.
Now my question to you: What is the order ServiceMix is deploying
SA's on
startup? What is the implemented behaviour now? Randomly?
The files in the directory are listed and processed sequentially, but
the order is not defined. Even when the container is restarted, the
order
between SA, or components is not really defined. So at deployment
time, you could use ant tasks and order the deployment, but it may fail
upon restart :(
Regards, Matthias
gnodet wrote:
>
> There's no way to do that. A Service Aseembly should work
> as a standalone application whenever possible.
> Any specific reason why you do not use a single SA with
> multiple SUs for ode and jsr181 ?
>
> On 11/14/06, Matthias von Arx <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> How can I configure the deploy order of service assemblies?
>>
>> We are using the latest ODE-JBI service engine (and the latest
ServiceMix
>> 3.0 Release) and the JSR181 service engine. Say we have two service
>> assemblies called sa-criminalregister.zip (containing the BPEL
process)
>> and
>> sa-federalcriminalregister.zip (containing the JSR181 service
assembly).
>> If
>> both SA are located in the deploy directory before ServiceMix runs an
>> exception was thrown at startup because the first deployed
>> sa-criminalregister.zip requires the (not yet available) endpoints
of the
>> sa-federalcriminalregister.zip.
>>
>> It's possible to configure something like deployment dependencies
or an
>> order for the SA's (like the SU order)?
>>
>> Regards, Matthias
>>
>> --
>> View this message in context:
>> http://www.nabble.com/SA-Order-tf2631883s12049.html#a7345321
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context:
http://www.nabble.com/SA-Order-tf2631883s12049.html#a7354386
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Christian Schneider
---
http://www.liquid-reality.de
