Btw, do you have the full stack trace of the exception ?
Cheers,
Guillaume Nodet
On 6/9/06, Peter Klotz <[EMAIL PROTECTED]> wrote:
Hi,
when using the static-routing-slip of the servicemix-eip component I have
the
problem that whatever target exchange component I specify, the error
returned is
always:
javax.jbi.messaging.MessagingException: No matching rule found for
exchange
I use other eip-patterns already successfully and now static-routing-slip
for
the first time, so I know how to use eip and lwcontainer components and
I'm 100%
sure that he corresponding service is defined.
<eip:static-routing-slip service="bes:usermgmt-router"
endpoint="endpoint">
<eip:targets>
<eip:exchange-target service="bes:usermgmt-filter"/>
<eip:exchange-target service="bes:dispatcher"/>
</eip:targets>
</eip:static-routing-slip>
The issue is with the usermgmt-filter component, which is definitely
deployed
and started:
INFO - 2006-06-09 10:09:15,313 | JBIContainer.activateComponent(1008) |
Activating component for: [container=ServiceMix,na
me=ID:spetses-56146-1149869277265-0:10] with service:
{http://blue-elephant-systems.com/midas/servicemix/1.0}usermgmt-filt
er component: [EMAIL PROTECTED]
INFO - 2006-06-09 10:09:15,314 | ComponentMBeanImpl.init(184) |
Initializing
component: ID:spetses-56146-1149869277265-0:1
0
INFO - 2006-06-09 10:09:15,485 | ComponentMBeanImpl.start(206) | Starting
component: ID:spetses-56146-1149869277265-0:10
DEBUG - 2006-06-09 10:09:15,488 | BaseServiceUnitManager.start(150) |
Service
unit started
but why can it not be found then?
When I have only the "bes:dispatcher" component in there it seems to work.
here is an extract from the corresponding servicemix-lwcontainer SU:
<sm:serviceunit id="jbi">
<sm:activationSpecs>
...
<sm:activationSpec endpoint="usermgmt-filter"
service="bes:usermgmt-filter">
<sm:component>
<bean class="com.bes.itm.comp.usermgmt.UserMgmtFilter">
<property name="repository">
<ref local="repository"/>
</property>
<property name="capacity" value="500"/>
<property name="timeout" value="360000"/>
<property name="service" value="bes:dispatcher"/>
</bean>
</sm:component>
</sm:activationSpec>
Is there a known problem with exactly this eip pattern?
Thanks, Peter
