Re: XmlBeans and Camel - Documentation

Actually Robert, would you mind filing for the Apache right to add license? If you apply for that license we can grant you right to the Wiki. I've noticed your work on both ActiveMQ and CXF - If you see errors, I'd love to see you help fixing up the wiki, having a second set of eyes and someon

Re: XmlBeans and Camel - Documentation

Ah... okay, thanks for the response Johan, that makes sense. -- Robert On Sun, 31 Jul 2011 22:34:50 -0600, Johan Edstrom wrote: > Well, it really just unmarshals using XMLBeans, so the education on how to > use xmlbeans is left with that project, that actually will go for > quite a few compone

Re: XmlBeans and Camel - Documentation

Well, it really just unmarshals using XMLBeans, so the education on how to use xmlbeans is left with that project, that actually will go for quite a few components. Since camel is an integration library, there is a lot of code invoked that from a Camel perspective might seem "un-documented" I

Build failed in Jenkins: Camel » Camel :: JMX #1290

See -- [INFO] [INFO] Building Camel :: JMX [INFO]task-segment: [clean, install] [INFO] ---

Build failed in Jenkins: Camel #1290

See Changes: [cmueller] CAMEL-4239: Improve the VM component tests [davsclaus] CAMEL-4250: Removed depdendency of commons-management. [davsclaus] CAMEL-4247: Introduced ManagementMBeanAssembler as SPI to be able to move spring JMX logic from c

XmlBeans and Camel - Documentation

This appears to be the primary documentation on XmlBeans and Camel: http://camel.apache.org/xmlbeans.html There's not much there. As I'm just getting started with this space, does anyone have anything more to add or can point me to a more extensive tutorial or documentation on the matter? T

[jira] [Commented] (CAMEL-4279) Add support for the new TLS for spring-ws if possible

[ https://issues.apache.org/jira/browse/CAMEL-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073401#comment-13073401 ] David Valeri commented on CAMEL-4279: - Added reply to mailing list thread about initia

[jira] [Work started] (CAMEL-4279) Add support for the new TLS for spring-ws if possible

[ https://issues.apache.org/jira/browse/CAMEL-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4279 started by David Valeri. > Add support for the new TLS for spring-ws if possible > - > >

[jira] [Resolved] (CAMEL-4060) camel-ahc - Upgrade to AHC 1.6.4 and support the new java bean style config bean

[ https://issues.apache.org/jira/browse/CAMEL-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Valeri resolved CAMEL-4060. - Resolution: Fixed Added support to component and documented changes in the wiki. > camel-ahc - U

Re: Missing feature to handle errors in a route which reads from an activemq destination

Thanks for your detailed answer Claus. But that's what I mean with "may it works as a work around". Because for each different ActiveMQComponent we create a new ActiveMQConnectionFactory. Does this sound right for you? Should we do not support a more elegant and resource friendly solution? Somethin

[jira] [Closed] (CAMEL-4239) Improve the VM component tests

[ https://issues.apache.org/jira/browse/CAMEL-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller closed CAMEL-4239. --- > Improve the VM component tests > -- > > Key: CAMEL-

[jira] [Resolved] (CAMEL-4239) Improve the VM component tests

[ https://issues.apache.org/jira/browse/CAMEL-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-4239. - Resolution: Fixed > Improve the VM component tests > -- > >

[jira] [Work started] (CAMEL-4060) camel-ahc - Upgrade to AHC 1.6.4 and support the new java bean style config bean

[ https://issues.apache.org/jira/browse/CAMEL-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4060 started by David Valeri. > camel-ahc - Upgrade to AHC 1.6.4 and support the new java bean style config > bean > --

[jira] [Commented] (CAMEL-4239) Improve the VM component tests

[ https://issues.apache.org/jira/browse/CAMEL-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073382#comment-13073382 ] Christian Müller commented on CAMEL-4239: - Committed r1152623 > Improve the VM co

[jira] [Resolved] (CAMEL-4250) Moved logic from commons-management to camel-core

[ https://issues.apache.org/jira/browse/CAMEL-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4250. Resolution: Fixed Fix Version/s: (was: 3.0.0) > Moved logic from commons-management to c

[jira] [Assigned] (CAMEL-4250) Moved logic from commons-management to camel-core

[ https://issues.apache.org/jira/browse/CAMEL-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4250: -- Assignee: Claus Ibsen > Moved logic from commons-management to camel-core > ---

Re: Missing feature to handle errors in a route which reads from an activemq destination

On Sun, Jul 31, 2011 at 7:42 PM, Christian Müller wrote: > Hello Claus! > > As you know, the redelivery logic is part of Apache ActiveMQ, but we cannot > use it in Camel in the way I would like it. To only have one redelivery > policy in place is not sufficient for us (if you configure the redeliv

[jira] [Resolved] (CAMEL-4247) Add API for pluggable JmxMBeanAssembler

[ https://issues.apache.org/jira/browse/CAMEL-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4247. Resolution: Fixed > Add API for pluggable JmxMBeanAssembler > -

Re: Missing feature to handle errors in a route which reads from an activemq destination

For clarification: We have multiple services/bundles running inside one ServiceMix instance and sharing the same ActiveMQConnectionFactory which is exported as OSGI service by the activemq-broker.xml configuration. We could use a separate ActiveMQConnectionFactory for each service/bundle, but this

Re: Missing feature to handle errors in a route which reads from an activemq destination

Hello Claus! As you know, the redelivery logic is part of Apache ActiveMQ, but we cannot use it in Camel in the way I would like it. To only have one redelivery policy in place is not sufficient for us (if you configure the redelivery policy in your ActiveMQConnectionFactory). We have multiple app

[jira] [Assigned] (CAMEL-4247) Add API for pluggable JmxMBeanAssembler

[ https://issues.apache.org/jira/browse/CAMEL-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4247: -- Assignee: Claus Ibsen > Add API for pluggable JmxMBeanAssembler > -

[jira] [Commented] (CAMEL-4028) Simple language - Allow to configure prefix and suffix tokens

[ https://issues.apache.org/jira/browse/CAMEL-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073349#comment-13073349 ] Claus Ibsen commented on CAMEL-4028: In XML DSL we may want to add a nice namespace fo

[jira] [Commented] (CAMEL-4028) Simple language - Allow to configure prefix and suffix tokens

[ https://issues.apache.org/jira/browse/CAMEL-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073348#comment-13073348 ] Claus Ibsen commented on CAMEL-4028: Taariq that is a good start. It would be great i

Re: Missing feature to handle errors in a route which reads from an activemq destination

Frankly I thing the redelivery logic should be part of Apache ActiveMQ. Your solution is brittle in the fact that you consume the message, and then send it back to the broker. What happens if you cannot send the message back to the broker? It would be better if the broker handled all this out of t

[jira] [Updated] (CAMEL-4028) Simple language - Allow to configure prefix and suffix tokens

[ https://issues.apache.org/jira/browse/CAMEL-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taariq Levack updated CAMEL-4028: - Attachment: (was: CAMEL-4028_Simple_language_-_Allow_to_configure_prefix_and_suffix_tokens2.p

[jira] [Updated] (CAMEL-4028) Simple language - Allow to configure prefix and suffix tokens

[ https://issues.apache.org/jira/browse/CAMEL-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taariq Levack updated CAMEL-4028: - Attachment: CAMEL-4028_Simple_language_-_Allow_to_configure_prefix_and_suffix_tokens1.patch The

[jira] [Resolved] (CAMEL-4285) Imported Xquery modules will not resolve using classpath

[ https://issues.apache.org/jira/browse/CAMEL-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4285. Resolution: Fixed Thanks for the patch. > Imported Xquery modules will not resolve using classpath

[jira] [Updated] (CAMEL-4285) Imported Xquery modules will not resolve using classpath

[ https://issues.apache.org/jira/browse/CAMEL-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4285: --- Priority: Minor (was: Major) Fix Version/s: 2.9.0 Issue Type: Improvement (was: Bug)

[jira] [Resolved] (CAMEL-4275) Don't ignore java.io.File.delete() returned boolean value

[ https://issues.apache.org/jira/browse/CAMEL-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4275. Resolution: Fixed Fix Version/s: 2.9.0 Thanks for the patch. I added it to the camel-testng

[jira] [Assigned] (CAMEL-4285) Imported Xquery modules will not resolve using classpath

[ https://issues.apache.org/jira/browse/CAMEL-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4285: -- Assignee: Claus Ibsen > Imported Xquery modules will not resolve using classpath >

[jira] [Closed] (CAMEL-4284) missing documentation in binary distribution tarballs

[ https://issues.apache.org/jira/browse/CAMEL-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Szott closed CAMEL-4284. --- Indeed! > missing documentation in binary distribution tarballs > --

[jira] [Assigned] (CAMEL-4275) Don't ignore java.io.File.delete() returned boolean value

[ https://issues.apache.org/jira/browse/CAMEL-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4275: -- Assignee: Claus Ibsen > Don't ignore java.io.File.delete() returned boolean value > ---

[jira] [Resolved] (CAMEL-4284) missing documentation in binary distribution tarballs

[ https://issues.apache.org/jira/browse/CAMEL-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4284. Resolution: Duplicate Fix Version/s: 2.9.0 Assignee: Claus Ibsen Duplicate of CAMEL

[jira] [Commented] (CAMEL-4226) add Expressions support on to(), bean() and beanRef() to allow for dynamic endpints (similar to recipientList)

[ https://issues.apache.org/jira/browse/CAMEL-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073340#comment-13073340 ] Claus Ibsen commented on CAMEL-4226: See discussion at http://camel.465427.n5.nabble.c

Re: Why Exchange is not serializable!?

Hi The @user mailing list is the best place to ask questions about Camel. There are many more subscribers who can help and follow the discussions. The @dev is about the development of the Apache Camel project. Exchange is not serializable because Camel cannot guarantee that content in the exchan

Jenkins build is back to normal : Camel #1289

See

Jenkins build is back to normal : Camel » Camel :: JMS #1289

See