Yes it's ok,
But i need to understand this also for my code generator too:
suppose i've my bean configured as:
<beans xmlns:bean="http://servicemix.apache.org/bean/1.0";>
<bean:endpoint service="test:endpoint" endpoint="endpoint"
bean="#listenerBean"/>
<bean id="listenerBean" class="org.apache.servicemix.bean.beans.ListenerBean"/>
</beans>
It's uri in nmr is "service:test:endpoint" right??? so for example i
could use "test:endpoint" as a destinationService attribute in
another endpoint right???
Is there already a JIRA on the porting or should i open a new one, i'll
attach my BeanTransformComponentSupport
so you can look at it.
Andrea
Guillaume Nodet ha scritto:
This property should be already set. This is done in servicemix-common
AsyncBaseLifeCycle class IIRC, so you should not worry about this one.
On Mon, Apr 7, 2008 at 4:58 PM, Andrea Zoppello <[EMAIL PROTECTED]> wrote:
Hi All,
I'm trying to develop a base smx bean deployable pojos reflecting the
features of the old
TransformComponentSupport class.
It seems to be very easy, but i still have two problems that i do not
understand very well
1) when i'm going to deploy a smx-bean, which value have the service and
the endpoint attributes??
One of the problem i've is on that line of TransformComponentSupport:
outExchange.setProperty(JbiConstants.SENDER_ENDPOINT, getService() + ":" +
getEndpoint());
Any idea??
Obviousvly if i'll sove my problem i'm going to contribute my class to smx
community :-)
Andrea
