[ 
https://issues.apache.org/activemq/browse/SM-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42295#action_42295
 ] 

Guillaume Nodet commented on SM-1305:
-------------------------------------

I agree this could be a bit confusing .   However, adding the same interface 
with a different name (wrt to servicemix-eip) may be even more confusing, so 
I'd rather have a @ExchangeTarget along with an <bean:exchange-target/>.  We 
can just copy the ExchangeTarget class from servicemix-eip into servicemix-bean 
(we need to find another name), as we can not share the same class (xbean needs 
the source code for its annotation processing and thus can not be used in 
different projects).

Using a set of properties (endpoint/operation/service/uri) is not the best 
solution imho, because if someone want to implement a router, it will have to 
define several targets, and a single set of properties would not work.

> Provide convenient base classes to simplify servicemix-bean component 
> development (including IN-only MEP Transforms)
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1305
>                 URL: https://issues.apache.org/activemq/browse/SM-1305
>             Project: ServiceMix
>          Issue Type: New Feature
>          Components: servicemix-bean
>    Affects Versions: 3.2.1
>            Reporter: Ron Gavlin
>         Attachments: lw2smbean.zip
>
>
> The deprecated, LightWeight container provided a convenient base class, 
> TransformComponentSupport, that made it easy for non-JBI experts to write 
> simple transforms in Java. In order to accomplish the same task with 
> servicemix-bean, a developer must have have in-depth, JBI knowledge. A helper 
> class or base class should be created to make it easier for developers to 
> write transforms using servicemix-bean. A base class would also be useful to 
> ease the implementation of non-Transform servicemix-beans. 
> I suggest the following class names for the proposed two base classes:
> 1. org.apache.servicemix.bean.support.BeanSupport.java - this class provides 
> servicemix-bean specific functionality currently offered by the combination 
> of "org.apache.servicemix.components.util.PojoSupport.java" and 
> "org.apache.servicemix.components.util.ComponentSupport.java"
> 2. org.apache.servicemix.bean.support.TransformBeanSupport.java - this class 
> extends "org.apache.servicemix.bean.support.BeanSupport.java" (above), 
> implements MessageExchangeListener, and provides servicemix-bean specific 
> functionality currently offered by 
> "org.apache.servicemix.components.util.TransformComponentSupport.java"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to