[
https://issues.apache.org/activemq/browse/CAMEL-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60018#action_60018
]
Max Ullinger commented on CAMEL-2705:
-------------------------------------
Hi
Nice idea there.
One thing that makes Camel hard to use for us right now is the need to have
beans in a registry (we will probably use camel as a "workflow" engine with
lots of calls to many business logic pojos). Currently evaluating.
It would be great to have a class component that instantiates an action for
this call.
It would be even better if the instantiated object could be configured.
e.g. <to uri="class:org.acme.SomeBean?config1=fast"/>
would set the field "config1" to the value "fast" when the class is
instantiated. -> a little like Spring DI
That would definately make Camel much easier to use.
> Add class as component for invoking beans but based on FQN classnames
> ---------------------------------------------------------------------
>
> Key: CAMEL-2705
> URL: https://issues.apache.org/activemq/browse/CAMEL-2705
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.4.0
>
>
> [10:09] <jstrachan> wonder to avoid using a string as a name, then as a
> class, we use a class uri?
> [10:09] <jstrachan> <to uri="class:org.acme.SomeBean"/>
> [10:12] <davsclaus> ah yeah that is clever
> [10:12] <davsclaus> jstrachan i like that one
> [10:13] <jstrachan> might be rare but some folks might use a class name as a
> name and you could get a clash I guess
> [10:14] <davsclaus> yeah and by class it spell out that its resolving a
> class and not looking up a bean name
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
