pom.xml - spring maven repo is amazon s3
Key: CAMEL-635
URL: https://issues.apache.org/activemq/browse/CAMEL-635
Project: Apache Camel
Issue Type: Improvement
Components: camel-core
Affe
[
https://issues.apache.org/activemq/browse/CAMEL-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-627.
---
Resolution: Fixed
> JMX Instrumentation - PerformanceCounter - last processed timestamp when
> fa
Hi
Okay the ".646039348" part is the hashcode if the endpoint is not a singleton.
Wouldn't it be better to use @ as prefix instead of dot?
So its:
[EMAIL PROTECTED]
Instead of
[jms]queue%3anumbers.646039348
Any thoughts?
Med venlig hilsen
Claus Ibsen
.
Hi
Ah it was a char based replace method - it does replace all. If the inputs was
String objects then you needed to use the replaceAll.
I tried with jconsole from JDK6 and it also displayes the names "strangely".
I am curious where the why the name is translated into:
[jms]queue%3anumbers.64603
[
https://issues.apache.org/activemq/browse/CAMEL-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43696#action_43696
]
Claus Ibsen commented on CAMEL-494:
---
Hi Dean
Any updates? I am sorry but I can not reproduc
[
https://issues.apache.org/activemq/browse/CAMEL-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-553.
---
Resolution: Fixed
Fixed with CAMEL-606. See updated wiki documentation as well:
http://activemq.ap
[
https://issues.apache.org/activemq/browse/CAMEL-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marat Bedretdinov updated CAMEL-634:
Attachment: tx.fix.2008-06-24-16-54.patch
> DeadLetterChannel default redelivery policy
DeadLetterChannel default redelivery policy eclipsed expected transactional
behaviour in a transacted route
---
Key: CAMEL-634
URL: https://issues.apache.org/a
[
https://issues.apache.org/activemq/browse/CAMEL-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marat Bedretdinov updated CAMEL-634:
Attachment: (was: tx.fix.2008-06-24-16-54.patch)
> DeadLetterChannel default redeliv
[
https://issues.apache.org/activemq/browse/CAMEL-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clayton Clark updated CAMEL-630:
Attachment: IBatisQueue.txt
Added unit test.
Using ObjectHelper for class loading.
> Logical Qu
[
https://issues.apache.org/activemq/browse/CAMEL-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clayton Clark updated CAMEL-630:
Attachment: (was: IBatisQueue.txt)
> Logical Queue Support
> -
>
>
We disable by default, but ship every example with the DLQ explicitly
configured to be amq.. so that way when folks copy examples they get
the dlq behavior, but at least it's explicit and in their face.
On Mon, Jun 23, 2008 at 6:52 AM, James Strachan
<[EMAIL PROTECTED]> wrote:
> 2008/6/23 Gert Van
>
> Another option I guess is to reserve message headers only for protocol
> related stuff; and use Exchange properties for anything else?
>
We could be setting headers in any of the three (in, out, fault)
messages. Using Exchange properties may lose the info regarding which
message the property
>
> I just checked that CXF also puts the protocol header as a Object with the
> key Message.PROTOCOL_HEADERS in the CXF message[1]. If you want to get the
> protocol headers of the CXF message, you can retrieve it from CxfMessage's
> getHeader with the Message.PROTOCOL_HEADERS.
Yes, I aware of t
> I guess the tricky thing is - what is a 'protocol header'?
>
> e.g. take HTTP and JMS as examples; you can specify your own headers
> which a receiver may or may not understand. You can do the same with
> SOAP. What constitutes a 'protocol header' in the general sense?
>
> Since its such a grey a
[
https://issues.apache.org/activemq/browse/CAMEL-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea resolved CAMEL-606.
---
Resolution: Fixed
> JMX enabled as default
> --
>
> Ke
Maybe the useJMX should be marked as @deperacted.
Med venlig hilsen
Claus Ibsen
..
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 24
[
https://issues.apache.org/activemq/browse/CAMEL-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43686#action_43686
]
Claus Ibsen commented on CAMEL-633:
---
The workaround above doens't work.
> SpringTestSuppor
[
https://issues.apache.org/activemq/browse/CAMEL-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-625.
Resolution: Fixed
http://svn.apache.org/viewvc?rev=670439&view=rev
> Add mvn profiles to start
Hi William,
I just checked that CXF also puts the protocol header as a Object with
the key Message.PROTOCOL_HEADERS in the CXF message[1]. If you want to
get the protocol headers of the CXF message, you can retrieve it from
CxfMessage's getHeader with the Message.PROTOCOL_HEADERS.
There is a
[
https://issues.apache.org/activemq/browse/CAMEL-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-633:
--
Priority: Minor (was: Major)
> SpringTestSupport - should support spring xml files loaded from file
[
https://issues.apache.org/activemq/browse/CAMEL-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43684#action_43684
]
Claus Ibsen commented on CAMEL-633:
---
You can do
{code}
protected ClassPathXmlApplication
[
https://issues.apache.org/activemq/browse/CAMEL-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43683#action_43683
]
Claus Ibsen commented on CAMEL-630:
---
Clayton, thanks for the info. Is now clear to me.
The
SpringTestSupport - should support spring xml files loaded from file system
---
Key: CAMEL-633
URL: https://issues.apache.org/activemq/browse/CAMEL-633
Project: Apache Camel
2008/6/23 William Tam <[EMAIL PROTECTED]>:
> Hi all,
>
> I may be totally off but, it seems that Camel Message headers are
> being used too liberally. Some headers are added by components for
> doing their jobs with no intention to send them as protocol headers.
> Some headers are objects/non-str
[
https://issues.apache.org/activemq/browse/CAMEL-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43682#action_43682
]
Clayton Clark commented on CAMEL-630:
-
This update allows you to treat a database table as
[
https://issues.apache.org/activemq/browse/CAMEL-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-613.
Resolution: Fixed
> Change the JMX default connetor's URL to avoid the confilict with the
> Act
[
https://issues.apache.org/activemq/browse/CAMEL-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43679#action_43679
]
Willem Jiang commented on CAMEL-613:
Done, I changed the default connector address to
se
Hi
Okay. Maybe if the name is only for display we could replace all invalid tokens
with _ so they are looking okay in the jconsole.
Jconsole can not escape %3a or whatever they have been replaced with to
anything nice in the display.
Have you tried with jconsole from jdk6, maybe its working be
Hi Claus,
I changed the code to use replaceAll but I got the same result.
String.replace() and String.replaceAll() are using the regex for
replacing, so they will replace all the token that find.
Willem
Claus Ibsen wrote:
Hi
Ah it need to use replaceAll and not just replace since there can b
Sure, I will take care of it.
Willem
Claus Ibsen wrote:
Hi
Ah it need to use replaceAll and not just replace since there can be more tokens in the name.
Willem can you try with the replaceAll and see if it works? I am at work.
Med venlig hilsen
Claus Ibsen
.
Hi
Ah it need to use replaceAll and not just replace since there can be more
tokens in the name.
Willem can you try with the replaceAll and see if it works? I am at work.
Med venlig hilsen
Claus Ibsen
..
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf.
Hi Claus,
I got the same result with you. After digging the code , I found it is
caused by the ObjectName can't contain one of :",=*?
You can find more information in here[1]
[1]
https://svn.apache.org/repos/asf/activemq/camel/trunk/camel-core/src/main/java/org/apache/camel/management/Object
hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is
included in the generated XSD as documentation
-
Key: CAMEL-632
URL:
Hi
I have enabled the JMX connector on the spring-jms example in the trunk.
Could you try to see from jconsole if your computer also reports the jms queue
route with a strange name
How-to
==
svn up
cd examples/camel-example-spring-jms
mvn compile exec:java -PCamelServer
start jconsole
conne
[
https://issues.apache.org/activemq/browse/CAMEL-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated CAMEL-382:
---
Fix Version/s: 1.5.0
(was: 1.4.0)
> support the JAXWS Dispatch API in camel
36 matches
Mail list logo
