Sorry, this is my fault.
Current Java annotation doesn't support the extension.
But we could use reflection to get the namespaces from your customer
annotation. I just did a quick fix for this[1], please check it out.
[1]https://issues.apache.org/activemq/browse/CAMEL-1602
Willem
millej wrote:
Hi Claus,
Thanks so much for the quick response! This helps me very much! Yes,
basically, if the sending the email fails, I just want to log the error and
end the route. I want the File consumer to complete and move/delete the
file, since a new file will be created and processed at a later time w
Hi
Error handling is hard, especially for non transactional transports
such as File / FTP and the likes.
>From what I understand from your description is that you want to poll
files and upload them to SFTP.
And in case this fails an email should be sent. And if this email
fails then it should ???
I am new to Camel and am having a tough time getting my route to work
properly. That being said, it is entirely possible that I am being a moron
and have missed something simple However, I have searched the mailing
list and have not found the answer I am looking for. Any help would be
apprecia
How would one go about extending the XPath annotation? After searching
around the web it looks as if annotations can't extend another annotation;
in fact, annotations can't use the extends keyword at all.
If you make the custom "annotation" a regular interface that extends the
XPath annotation
On Mon, May 11, 2009 at 2:02 PM, rohitbrai wrote:
>
> Hey guys,
>
> Thanks a lot for this quick implmentation... I was working to make my own
> splitter, but I don't think that is required any more :D
>
> Would like to know, any idea on when will 1.6.1/2.0 release??? Currently I
> am checking out
Hi Claus,
I have created a JIRA ticket for this issue and attached a MVN project that
demonstrates the issue. The JIR reference is CAMEL-1601.
Regards,
Tristan
Claus Ibsen-2 wrote:
>
> On Mon, May 11, 2009 at 7:46 AM, triswork wrote:
>>
>> I have made some progress with this issue, but I
Hey guys,
Thanks a lot for this quick implmentation... I was working to make my own
splitter, but I don't think that is required any more :D
Would like to know, any idea on when will 1.6.1/2.0 release??? Currently I
am checking out the new splitter file, renaming it and adding it to my code
base
Hi Claus,
I have double-checked and the spring XML config seems to be correct. It just
seems that two different transaction contexts are being used when I use
annotations.
I don't know if it makes a huge difference, but I set the
JTATransactionManager as a property of my component (from the Spr
On Mon, May 11, 2009 at 11:10 AM, Guillaume Renault
wrote:
> Hi users,
>
> I saw on the dev list that you voted for a M2 of Camel 2. I'm actually
> working on the SNAPSHOT version as i need the improvement i suggested in
> camel-osgi to use the DefaultCamelContext factory, and it works fine, thx :
gt; >> >
> >>> >> >
> >>> >> > >>> uri="quickfix-client:META-INF/examples/client.cfg"/>
> >>> >> >
> >>> >> >
> >>> &
t;>> >> >
>>>> >> >
>>>> >> >
>>>> >> > >>> uri="quickfix-client:META-INF/examples/client.cfg"/>
>>>> >> >
>>>> >> &
Hi users,
I saw on the dev list that you voted for a M2 of Camel 2. I'm actually
working on the SNAPSHOT version as i need the improvement i suggested in
camel-osgi to use the DefaultCamelContext factory, and it works fine, thx :)
Do you have a date for this future version ? (or the 1.6.1 ver
On Mon, May 11, 2009 at 10:15 AM, jpcook wrote:
>
> Thanks for the advice. I created a new ticket (CAMEL-1599) and hope to submit
> a patch today or tomorrow :)
Fantastic. Submitting patches open a door. That is how I got started
with Camel :)
>
> Claus Ibsen-2 wrote:
>>
>> On Fri, May 8, 2009 a
lient.cfg"/>
>>> >> >
>>> >> >
>>> >> > When the messages are read from the queue and converted, the
>>> following
>>> >> error
>>> >> > is reported.
>>> >> >
>
Thanks for the advice. I created a new ticket (CAMEL-1599) and hope to submit
a patch today or tomorrow :)
Claus Ibsen-2 wrote:
>
> On Fri, May 8, 2009 at 5:53 PM, Claus Ibsen wrote:
>> On Fri, May 8, 2009 at 5:49 PM, jpcook
>> wrote:
>>>
>>> Yes I can do it a bit later. I might even submit a
>> |
>> >> > rg.apache.camel.processor.Logger 127 |
>> >> > ID-dell-charles-1611-1242019089609-2-5 >>>
>> >> > to(quickfix-client:META-INF/examples/client.cfg) -->
>> >> > to(quickfix-client:META-INF/examples/client.
attern:InOut,
> >> >
> >>
> Properties:{JMSReplyTo=temp-queue://ID:dell-charles-1607-1242019074921-2:2:1},
> >> > Headers:{JMSXGroupID=null,
> >> > JMSCorrelationID=ID-dell-charles-1611-1242019089609-3-0, JMSType=null,
> >> > JMSExpiration
t; > to(quickfix-client:META-INF/examples/client.cfg), Pattern:InOut,
>> >
>> Properties:{JMSReplyTo=temp-queue://ID:dell-charles-1607-1242019074921-2:2:1},
>> > Headers:{JMSXGroupID=null,
>> > JMSCorrelationID=ID-dell-charles-1611-1242019089609-3-0, JMSType=null,
>&g
2019074921-2:2:1},
> > Headers:{JMSXGroupID=null,
> > JMSCorrelationID=ID-dell-charles-1611-1242019089609-3-0, JMSType=null,
> > JMSExpiration=1242024716484,
> > JMSMessageID=ID:dell-charles-1607-1242019074921-2:2:3:1:1,
> > JMSRedelivered=false, JMSDeliveryMode=2, JMSPri
:1,
> JMSTimestamp=1242024696484, JMSDestination=queue://fix}, BodyType:String,
> Body:8=FIX.4.1 9=102 35=D 34=82 49=BANZAI 52=20090511-06:51:32 56=FIXGW
> 11=1242024692768 21=1 38=150 40=1 54=1 55=SUN 59=0 10=051
> 08:51:36,515 | ERROR | enerContainer-23 | DeadLetterChannel
ivered=false, JMSDeliveryMode=2, JMSPriority=4,
JMSReplyTo=temp-queue://ID:dell-charles-1607-1242019074921-2:2:1,
JMSTimestamp=1242024696484, JMSDestination=queue://fix}, BodyType:String,
Body:8=FIX.4.19=10235=D34=8249=BANZAI52=20090511-06:51:3256=FIXGW11=124202469276821=138=15040=154=155=SUN59=
On Mon, May 11, 2009 at 8:58 AM, Willem Jiang wrote:
> Yeah, I added a new POJO method splitMessage() to return a List of
> Message, and the original "split" method is renamed to be "splitBody"
> method.
>
> You can find the change here[1].
> [1]
> http://svn.apache.org/viewvc/camel/trunk/camel-co
23 matches
Mail list logo
