When rendering 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?
alloyer wrote:
Hi
Could you create a JIRA ticket about the ExpressionDefinition problem we have?
On Sun, Jun 28, 2009 at 6:49 AM, alloyerallo...@gmail.com wrote:
Now I got it now through expressionNode.getExpression().toString(), which
return a string {delayTime}. Then I can get the subString in it. Are
Now I got it now through expressionNode.getExpression().toString(), which
return a string {delayTime}. Then I can get the subString in it. Are there
some better methods?
alloyer wrote:
Thanks, I found lots of test cases there.
When I construct the groovy route definition from a
Now groovy renderer has been implemented, but only tested by using some rotue
with basic processorDefinitions now.
For test all the processorDefinitions, I wonder where can I get some complex
route definition test cases?
Thanks
JIRA j...@apache.org wrote:
[
On Fri, Jun 26, 2009 at 6:22 PM, alloyerallo...@gmail.com wrote:
Now groovy renderer has been implemented, but only tested by using some rotue
with basic processorDefinitions now.
For test all the processorDefinitions, I wonder where can I get some complex
route definition test cases?
We got
