[jira] Updated: (CAMEL-1660) A lite AOP feature in the DSL

[ https://issues.apache.org/activemq/browse/CAMEL-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1660: --- Fix Version/s: (was: 2.1.0) 2.0.0 > A lite AOP feature in the DSL > --

[jira] Commented: (CAMEL-1660) A lite AOP feature in the DSL

[ https://issues.apache.org/activemq/browse/CAMEL-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52834#action_52834 ] Claus Ibsen commented on CAMEL-1660: trunk: 794544. > A lite AOP feature in the DSL > --

[jira] Commented: (CAMEL-1554) Remove InterceptorDefinition

[ https://issues.apache.org/activemq/browse/CAMEL-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52833#action_52833 ] Claus Ibsen commented on CAMEL-1554: And calling before and after can always be done the

[jira] Commented: (CAMEL-1554) Remove InterceptorDefinition

[ https://issues.apache.org/activemq/browse/CAMEL-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52832#action_52832 ] Claus Ibsen commented on CAMEL-1554: It was clashing with the general interceptor in Came

[jira] Commented: (CAMEL-1554) Remove InterceptorDefinition

[ https://issues.apache.org/activemq/browse/CAMEL-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52831#action_52831 ] Ming Fang commented on CAMEL-1554: -- Why was this removed? What is the alternative way to add

Re: svn commit: r794245 - in /camel/trunk/components/camel-bindy/src: main/java/org/apache/camel/dataformat/bindy/ main/java/org/apache/camel/dataformat/bindy/annotation/ main/java/org/apache/camel/da

Hi Charles I think you didn't comment the package of "org.apache.camel.dataformat.bindy.model.simple.oneclassmandatory" So the test of BindySimpleCsvMandatoryFieldsUnmarshallTest is failed. Please using "svn st" to double check the code with ? states before you commit the code :) Willem cm

[jira] Resolved: (CAMEL-1834) Message content sent to exception handler is not re-readable

[ https://issues.apache.org/activemq/browse/CAMEL-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved CAMEL-1834. Resolution: Fixed Fixed for 1.6.2-SNAPSHOT in http://svn.apache.org/viewvc?view=rev&re

[jira] Created: (CAMEL-1834) Message content sent to exception handler is not re-readable

Message content sent to exception handler is not re-readable Key: CAMEL-1834 URL: https://issues.apache.org/activemq/browse/CAMEL-1834 Project: Apache Camel Issue Type: Bug Aff

Re: JMS queue / JNDI instead of physical name

Hi, I try to use the destinationResolver and I was able to use logical name instead of the physical name. Thanks. Here is my configuration: or

Apache Camel Pattern

Hi, Is there a wiki page described in more detail the following exchange pattern and what is supported by Camel (except the known InOnly/InOut) ? *InOnly * *InOptionalOut

Re: Apache camel logger processor / only one line is displayed

Its the TRACER that you have in the displayed log. the LOG component is not the tracer. You have configured it to log at DEBUG level maybe try raising that to INFO/ERROR or whatever. In case DEBUG logging is not enabled. On Wed, Jul 15, 2009 at 3:49 PM, Charles Moulliard wrote: > Nothing change

Re: Apache camel logger processor / only one line is displayed

Nothing change if I use this uri log:x3slog?level=DEBUG&multiline=true&showException=true BTW, in the doc, showException is defined by default to false --> so :no stack trace is show or this log:x3slog?level=DEBUG&multiline=true&showAll=true 15:46:22,406 | INFO | enerContainer-22 | TraceIn

Re: Apache camel logger processor / only one line is displayed

Sorry for my mistake master Claus ;-) Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Wed, Jul 15, 2009 at 3:35 PM, Claus Ibsen wrote: > A good idea is to read the manual / log component :) > http://ca

Apache tryprocessor / only one line is displayed

This is also the case for the tryProcessor : 15:16:36,328 | DEBUG | erContainer-1657 | TryProcessor | che.camel.processor.TryProcessor 115 | The exception is handled: true for the exception: java.lang.NumberFormatException caused by: null I don't see the full stack trace in d

Re: Apache camel logger processor / only one line is displayed

A good idea is to read the manual / log component :) http://camel.apache.org/log.html The option: showException should be set to true BTW: I would like to add an additonal option in the future: showTrackTrace to eg not output exception stacktrace, but still the exception message and exception cla

Apache camel logger processor / only one line is displayed

Hi, In my route, I use the camel logger processor to log some info in a file. I have configured it to display error on multilines

[jira] Resolved: (CAMEL-1831) OSGi integration test to show how to setup the servlet in OSGi plateform

[ https://issues.apache.org/activemq/browse/CAMEL-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-1831. - Resolution: Fixed http://svn.apache.org/viewvc?rev=794238&view=rev > OSGi integration test t

[jira] Resolved: (CAMEL-1832) camel-servlet feature

[ https://issues.apache.org/activemq/browse/CAMEL-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-1832. - Resolution: Fixed Fix Version/s: 2.0.0 http://svn.apache.org/viewvc?rev=794237&view=re

[jira] Created: (CAMEL-1833) camel-servlet wiki page

camel-servlet wiki page --- Key: CAMEL-1833 URL: https://issues.apache.org/activemq/browse/CAMEL-1833 Project: Apache Camel Issue Type: Sub-task Reporter: Willem Jiang Assignee: Willem Jiang --

[jira] Created: (CAMEL-1832) camel-servlet feature

camel-servlet feature - Key: CAMEL-1832 URL: https://issues.apache.org/activemq/browse/CAMEL-1832 Project: Apache Camel Issue Type: Sub-task Reporter: Willem Jiang Assignee: Willem Jiang -- Th

[jira] Created: (CAMEL-1831) OSGi integration test to show how to setup the servlet in OSGi plateform

OSGi integration test to show how to setup the servlet in OSGi plateform Key: CAMEL-1831 URL: https://issues.apache.org/activemq/browse/CAMEL-1831 Project: Apache Camel

[jira] Assigned: (CAMEL-1831) OSGi integration test to show how to setup the servlet in OSGi plateform

[ https://issues.apache.org/activemq/browse/CAMEL-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-1831: --- Assignee: Willem Jiang > OSGi integration test to show how to setup the servlet in OSGi p

Re: File cannot be processed immediately in a camel junit test. Why ?

I found how to solve this. This is related to the fact that the file : csv.txt.camelLock was present in the folder from an old test failure. Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Wed, Jul 15, 2

Re: File cannot be processed immediately in a camel junit test. Why ?

using noop=true does not work So I will try the second approach proposed ;-) On Wed, Jul 15, 2009 at 12:22 PM, Claus Ibsen wrote: > Use ?noop=true if the file it should process is included in your SVN > and thus should not be deleted. > > Otherwise you can write a temporary file the target/xxx

Re: How to test an exception in a camel test

I can't test the exception type : This test fails try { template1.sendBody(record1); fail("Should have thrown an exception"); } catch (CamelExecutionException e) { Assert.isInstanceOf(java.lang.IllegalArgumentException.class, e.getCause());

Re: File cannot be processed immediately in a camel junit test. Why ?

Use ?noop=true if the file it should process is included in your SVN and thus should not be deleted. Otherwise you can write a temporary file the target/xxx folder and let Camel be able to moved/delete it On Wed, Jul 15, 2009 at 12:19 PM, Charles Moulliard wrote: > Hi, > > When I launch the fol

Re: How to test an exception in a camel test

On Wed, Jul 15, 2009 at 12:15 PM, Charles Moulliard wrote: > Thx. > >  It works with this : > >       try { >            template1.sendBody(record1); >        } catch (CamelExecutionException e) { > You actually need to do it like this try { template1.sendBody(record1);

File cannot be processed immediately in a camel junit test. Why ?

Hi, When I launch the following unit test of bindy, @ContextConfiguration(locations = "org.apache.camel.dataformat.bindy.csv.BindySimpleCsvUnmarshallTest$ContextConfig", loader = JavaConfigContextLoader.class) public class BindySimpleCsvUnmarshallTest extends AbstractJUnit4SpringContextTests {

Re: How to test an exception in a camel test

Thx. It works with this : try { template1.sendBody(record1); } catch (CamelExecutionException e) { Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Wed, Jul 15, 2009 at 11:

Re: How to test an exception in a camel test

Some exceptions are wrapped in Camel so catch the wrapper and look for your caused exception. On Wed, Jul 15, 2009 at 11:25 AM, Charles Moulliard wrote: > Hi, > > I try to create a test like this where I check if a specific exception type > is generated but it does not work. > > Is the code corre

How to test an exception in a camel test

Hi, I try to create a test like this where I check if a specific exception type is generated but it does not work. Is the code correct : @ContextConfiguration(locations = "org.apache.camel.dataformat.bindy.csv.BindySimpleCsvMandatoryFieldsUnmarshallTest$ContextConfig", loader = JavaConfigContext