Guillaume,
thanks for your quick answer !
Have you got any any idea for my last 2 questions concerning :
* The way used to do the mapping logical/physical endpoint ?
* And where this map is stored ?
Regards,
Charles
Guillaume Nodet wrote:
The new BC will behave as you say.
So this is true for
* servicemix-http
* servicemix-jms
Note that these components are not finished yet, but i am currently
working on it.
When you will deploy a service unit, it contains informations about
the endpoints to create,
either consumer endpoint or provider endpoint.
Depending on the deployment model you will use (wsdl or xml), the
information is extracted
and use to create endpoints.
Cheers,
Guillaume Nodet
Charles Souillard wrote:
Hi all,
I just want to be sure of something about BCs.
My understanding is that BCs are "generic". It means the JMS BC is
deployed into SM only once and then if we want to configure different
endpoints (each partner has its own queue/topic for example) we only
have to deploy (JBI deploy) new service assemblies containing some
artifacts...
Can you just confirm this understanding or tell me if I am wrong...
This question comes to me by thinking about JCA which is a special
case as each partner will have its own JCA connector I think, isn't it ?
I have another question concerning endpoints. I just want to know how
the mapping is done between logical endpoints and physical endpoints.
On the web site, I can read that UDDI is not yet supported so where
are stored these informations ?
Thanks,
Regards,
Charles
