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
When rendering the some expression, like the MethodCallExpression of
ExpressionClause in web console, I have to use the expressionType property
of ExpressionClause, so a getExpressionType() method is required.
Can I fix this bug or create a bug issue?
JIRA j...@apache.org wrote:
>
> groovy ren
On Thu, Jul 2, 2009 at 6:36 AM, alloyer wrote:
>
> When rendering the some expression, like the MethodCallExpression of
> ExpressionClause in web console, I have to use the expressionType property
> of ExpressionClause, so a getExpressionType() method is required.
> Can I fix this bug or create a b
When renderring
loadBalance().failover(IOException.class)
resequence(body())
,need a getExceptions() for FailOverLoadBalancer and a getExceptionList()
for ResequenceDefinition.
JIRA j...@apache.org wrote:
>
> groovy renderer
> ---
>
> Key: CAMEL-1392
>
Load balancer is not a top priority DSL to get working 100% in groovy
DSL at this time.
If you have other DSL to port then please take a look at them instead.
For instance the Content Based Router (choice) is top priority.
On Mon, Jul 6, 2009 at 1:05 PM, alloyer wrote:
>
> When renderring
>
all right. I am going to create a page to list which DSL have been supported
these days.
Now the main problem I encountered is to deal with the invoking of a
registered bean or creating object (such as a MyAggregationStrategy
instance) when editing route in Groovy.
Do you think it is a top priorit
After some discuss with Janstey, I know the web editor is working for
changing the existing route, not for router development. The duty of
creating bean may be dropped on groovy editor.
alloyer wrote:
>
> all right. I am going to create a page to list which DSL have been
> supported these days.
Have the endpoint URIs been changed to "direct://start" from "direct:start" ?
I haven't updated my camel-core source for several days. Maybe I have to
update it now.
JIRA j...@apache.org wrote:
>
> groovy renderer
> ---
>
> Key: CAMEL-1392
> URL:
On Thu, Jul 9, 2009 at 7:47 AM, alloyer wrote:
>
> Have the endpoint URIs been changed to "direct://start" from "direct:start" ?
> I haven't updated my camel-core source for several days. Maybe I have to
> update it now.
Yes the endpoint registry in Camel will enforce a // after the scheme.
This al
all right. I saw the deadLetter DSL have used "direct://start".
Will this enforcemnt be applied before long?
Claus Ibsen-2 wrote:
>
> On Thu, Jul 9, 2009 at 7:47 AM, alloyer wrote:
>>
>> Have the endpoint URIs been changed to "direct://start" from
>> "direct:start" ?
>> I haven't updated my c
On Thu, Jul 9, 2009 at 8:43 AM, alloyer wrote:
>
>
> all right. I saw the deadLetter DSL have used "direct://start".
> Will this enforcemnt be applied before long?
Its in there now. So yes it will be standard in Camel 2.0.
This is the ticket about it
http://issues.apache.org/activemq/browse/CAMEL-
Hi,
You'd better run svn update at lest once a day.
Since we are using SVN, you need to get use to the bunch of small
changes everyday :)
Willem
alloyer wrote:
Have the endpoint URIs been changed to "direct://start" from "direct:start" ?
I haven't updated my camel-core source for several day
1. When rendering a resequence DSL:
from("direct:start").resequencer(body()).to("mock:result")"
a getExpressionList method is required to obtain the expressions in
ResequenceDefinition.
2. the AOPDefinition should provides some get methods for its beforeUri,
afterUri and afterFinallyUri fields.
If you don't want to hack the class with JAXB, you can add the get set
method on the Definition class yourself :)
Willem
xueqiang.mi wrote:
1. When rendering a resequence DSL:
from("direct:start").resequencer(body()).to("mock:result")"
a getExpressionList method is required to obtain the ex
all right, thanks.
I am gonna go on a vacation from Jul 23 to Aug 1. After it I will do that.
:-)
willem.jiang wrote:
>
> If you don't want to hack the class with JAXB, you can add the get set
> method on the Definition class yourself :)
>
> Willem
>
> xueqiang.mi wrote:
>> 1. When rendering
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()
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 spri
All right, it seems we have no way to support the "bean" and "process" DSL
rendering now.
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.
>
>
On Wed, Aug 12, 2009 at 10:35 AM, xueqiang.mi 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 t
Hi,
When I tested the intercept DSL, I encountered a problem.
I found sometimes the route maintains the intercept definition as a output
processor in outputs list, but sometimes, it hold the intercept
configuration in its interceptStrategies list. I don't what causes the
difference and how to diff
I found that the addRouteDefinitions method of camel context caused this
problem. It seems that this method transform the interceptDefinition into a
interceptStrategy.
Before updating a route, I use a temporary camel context to generate the
route definition from a route builder, so I can obtain th
I don't think you should be taking route definitions from one camel context
and loading them into another... I'm surprised this actually works! Also,
I'm not really following why you need a 2nd context to set the id... did you
try just using one?
On Thu, Aug 13, 2009 at 10:19 AM, xueqiang.mi wrot
On Thu, Aug 13, 2009 at 3:10 PM, Jon Anstey wrote:
> I don't think you should be taking route definitions from one camel context
> and loading them into another... I'm surprised this actually works! Also,
> I'm not really following why you need a 2nd context to set the id... did you
> try just usin
After trying to grok the intercept code a bit, I'm gonna +1 Claus'
suggestion :)
As a side note for any Camel users listening in, the intercept stuff in 2.0
is *much* easier to use than 1.x from a users standpoint - its just complex
under the hood.
On Thu, Aug 13, 2009 at 10:50 AM, Claus Ibsen w
>From the groovyRouteBuilder, we can only get a routeBuild, which may have
several routes in it and doesn't support to setId.
janstey wrote:
>
> I don't think you should be taking route definitions from one camel
> context
> and loading them into another... I'm surprised this actually works! Al
okay, I am now reviewing the test case. A document, presenting which DSLs are
supported and which are not, will be commited tomorrow or the day after
tomorrow.
cheers
janstey wrote:
>
> After trying to grok the intercept code a bit, I'm gonna +1 Claus'
> suggestion :)
>
> As a side note for an
I got a jersey problem:
To change the status of a route on the following page by send:
http://localhost:9998/routes/route1/status
http://www.nabble.com/file/p25039325/ss.jpg ss.jpg
It is expected to be delivered into the following method of RouteResource
{code}
@Path("status")
public Rout
I can't shed any light into why this stopped working... but I did put in a
fix (or workaround?) in revision 805780.
On Wed, Aug 19, 2009 at 5:13 AM, xueqiang.mi wrote:
>
> I got a jersey problem:
> To change the status of a route on the following page by send:
> http://localhost:9998/routes/rout
28 matches
Mail list logo
