On Wed, Aug 12, 2009 at 10:35 AM, xueqiang.mi<allo...@gmail.com> wrote:
>
> All right, it seems we have no way to support the "bean" and "process" DSL
> rendering now.
>

Yeah that is fine, we cant do 100%. And there are fine solutions for
people to use xxxRef instead.
Maybe in the future we can do some magic under the covers.


>
> Claus Ibsen-2 wrote:
>>
>> Hi
>>
>> This is not possible as a processor instance is inlined directly. It
>> is not registered anywhere.
>> Only processorRef uses a reference to a Processor in the registry.
>>
>> Its only the Java DSL that has this feature (inlined/anonymous
>> processors ) as in Spring DSL you need to use a reference to a spring
>> bean.
>>
>>
>> On Wed, Aug 12, 2009 at 10:04 AM, xueqiang.mi<allo...@gmail.com> wrote:
>>>
>>> Hi,
>>> I want to understand how RouteContext or Registry register and then look
>>> up
>>> a new Processor object when  receive some DSL which contains new
>>> Processor
>>> object, like the following one:
>>> {code}
>>> MyValidator validator = new MyValidator();
>>> from("direct:start")
>>>                    .doTry()
>>>                        .process(validator).to("mock:valid")
>>>                    .doCatch(ValidationException.class)
>>>                        .to("mock:invalid")
>>> {code}
>>> 1. Does the route/processor definition maintain the processor name
>>> "validator" somewhere?
>>> 2. If the processor is registered, how can I get the object and translate
>>> it
>>> into a processor reference when rendering it. I want to render the above
>>> DSL
>>> into:
>>> {code}
>>> from("direct:start")
>>>                    .doTry()
>>>                        .processRef("someName or some
>>> registeredKey").to("mock:valid")
>>>                    .doCatch(ValidationException.class)
>>>                        .to("mock:invalid")
>>> {code}
>>>
>>> Thanks
>>>
>>> JIRA j...@apache.org wrote:
>>>>
>>>> groovy renderer
>>>> ---------------
>>>>
>>>>                  Key: CAMEL-1392
>>>>                  URL:
>>>> https://issues.apache.org/activemq/browse/CAMEL-1392
>>>>              Project: Apache Camel
>>>>           Issue Type: Sub-task
>>>>             Reporter: James Strachan
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> -
>>>> You can reply to this email to add a comment to the issue online.
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/-jira--Created%3A-%28CAMEL-1392%29-groovy-renderer-tp22220288p24931669.html
>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>>
>
> --
> View this message in context: 
> http://www.nabble.com/-jira--Created%3A-%28CAMEL-1392%29-groovy-renderer-tp22220288p24931863.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
>



-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Reply via email to