[jira] [Commented] (CAMEL-4256) Adding a EndpointConfiguration interface

[ https://issues.apache.org/jira/browse/CAMEL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114592#comment-13114592 ] james strachan commented on CAMEL-4256: --- Endpoints are already beans you can config

[jira] [Updated] (CAMEL-4417) Move base classes used by components from impl to support

[ https://issues.apache.org/jira/browse/CAMEL-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated CAMEL-4417: -- Fix Version/s: (was: 2.9.0) 3.0.0 > Move base classes used by components

[jira] [Commented] (CAMEL-4417) Move base classes used by components from impl to support

[ https://issues.apache.org/jira/browse/CAMEL-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097145#comment-13097145 ] james strachan commented on CAMEL-4417: --- Since this code change will break pretty mu

[jira] [Created] (CAMEL-4281) would be good for FileEndpoint to implement BrowsableEndpoint (ditto any other components we can find that are easy to do)...

would be good for FileEndpoint to implement BrowsableEndpoint (ditto any other components we can find that are easy to do)... - Key: CAMEL-4281

[jira] [Created] (CAMEL-4233) avoid runtime package scanning to discover TypeConverters

avoid runtime package scanning to discover TypeConverters - Key: CAMEL-4233 URL: https://issues.apache.org/jira/browse/CAMEL-4233 Project: Camel Issue Type: Improvement Repo

[jira] [Commented] (CAMEL-4122) JMX API to create/delete endpoint

[ https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052047#comment-13052047 ] james strachan commented on CAMEL-4122: --- BTW you can create endpoints via the Java A

[jira] [Commented] (CAMEL-4122) JMX API to create/delete endpoint

[ https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052046#comment-13052046 ] james strachan commented on CAMEL-4122: --- In ActiveMQ and ServiceMix you can view/cre

[jira] [Created] (CAMEL-4122) JMX API to create/delete endpoint

JMX API to create/delete endpoint - Key: CAMEL-4122 URL: https://issues.apache.org/jira/browse/CAMEL-4122 Project: Camel Issue Type: Improvement Reporter: james strachan Fix For: 2.8.0

[jira] [Created] (CAMEL-4100) camel JMS endpoints should accept messages with JMSDeliveryMode as a non-numeric String such as values "PERSISTENT" or "NON_PERSISTENT"

camel JMS endpoints should accept messages with JMSDeliveryMode as a non-numeric String such as values "PERSISTENT" or "NON_PERSISTENT" --- Key: CAM

[jira] Created: (CAMEL-3747) create a camel bundle archetype

create a camel bundle archetype --- Key: CAMEL-3747 URL: https://issues.apache.org/jira/browse/CAMEL-3747 Project: Camel Issue Type: Improvement Reporter: james strachan Fix For: 2.7.0 w

[jira] Commented: (CAMEL-3737) ResequenceDefinition in XML allows 2 configurations to be specified, and which is not ideal.

[ https://issues.apache.org/jira/browse/CAMEL-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000878#comment-13000878 ] james strachan commented on CAMEL-3737: --- LoadBalancerDefinition is fine in trunk :)

[jira] Commented: (CAMEL-3737) ResequenceDefinition in XML allows 2 configurations to be specified, and which is not ideal.

[ https://issues.apache.org/jira/browse/CAMEL-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000872#comment-13000872 ] james strachan commented on CAMEL-3737: --- Looks like the LoadBalancerDefinition needs

[jira] Created: (CAMEL-3737) ResequenceDefinition in XML allows 2 configurations to be specified, and which is not ideal.

ResequenceDefinition in XML allows 2 configurations to be specified, and which is not ideal. - Key: CAMEL-3737 URL: https://issues.apache.org

[jira] Created: (CAMEL-3736) BeanDefinition.beanType should be of type String rather than Class so that the XML can be parsed without necessarily having the full class loader available at XML parse ti

BeanDefinition.beanType should be of type String rather than Class so that the XML can be parsed without necessarily having the full class loader available at XML parse time. does using Class even work? --

[jira] Resolved: (CAMEL-3726) Context component - Startup ordering issue when using Spring XML

[ https://issues.apache.org/jira/browse/CAMEL-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved CAMEL-3726. --- Resolution: Fixed Fix Version/s: (was: 2.8.0) 2.7.0 Ass

[jira] Commented: (CAMEL-3693) have a way to validate the model is correct according to JAXB and bean introspection rules

[ https://issues.apache.org/jira/browse/CAMEL-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997898#comment-12997898 ] james strachan commented on CAMEL-3693: --- another one I spotted is OnExceptionDefinit

[jira] Commented: (CAMEL-3693) have a way to validate the model is correct according to JAXB and bean introspection rules

[ https://issues.apache.org/jira/browse/CAMEL-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997879#comment-12997879 ] james strachan commented on CAMEL-3693: --- another validation rule to watch. Patterns

[jira] Updated: (CAMEL-3696) ResequenceDefinition probably should not take a List for easier operation among the various DSLs (Java + XML etc) since expressions in most languages

[ https://issues.apache.org/jira/browse/CAMEL-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated CAMEL-3696: -- Fix Version/s: 2.7.0 > ResequenceDefinition probably should not take a List > for easier opera

[jira] Created: (CAMEL-3696) ResequenceDefinition probably should not take a List for easier operation among the various DSLs (Java + XML etc) since expressions in most languages

ResequenceDefinition probably should not take a List for easier operation among the various DSLs (Java + XML etc) since expressions in most languages can easily do composites --

[jira] Created: (CAMEL-3693) have a way to validate the model is correct according to JAXB and bean introspection rules

have a way to validate the model is correct according to JAXB and bean introspection rules -- Key: CAMEL-3693 URL: https://issues.apache.org/jira/browse/CAMEL-3693

[jira] Created: (CAMEL-3692) badly named getter methods for type "Boolean"

badly named getter methods for type "Boolean" - Key: CAMEL-3692 URL: https://issues.apache.org/jira/browse/CAMEL-3692 Project: Camel Issue Type: New Feature Reporter: james strachan

[jira] Commented: (CAMEL-3651) create a simple way to expose a CamelContext as a black box component that can be easily reused in other CamelContext instances

[ https://issues.apache.org/jira/browse/CAMEL-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993426#comment-12993426 ] james strachan commented on CAMEL-3651: --- Code complete and tested though we could do

[jira] Commented: (CAMEL-3563) CamelContext should act like a Component (i.e. a TypeConverter of CamelContext -> CamelContextComponent)

[ https://issues.apache.org/jira/browse/CAMEL-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993425#comment-12993425 ] james strachan commented on CAMEL-3563: --- See the documentation: https://cwiki.apache

[jira] Commented: (CAMEL-3651) create a simple way to expose a CamelContext as a black box component that can be easily reused in other CamelContext instances

[ https://issues.apache.org/jira/browse/CAMEL-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993117#comment-12993117 ] james strachan commented on CAMEL-3651: --- further background and discussions here: h

[jira] Commented: (CAMEL-3651) create a simple way to expose a CamelContext as a black box component that can be easily reused in other CamelContext instances

[ https://issues.apache.org/jira/browse/CAMEL-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993116#comment-12993116 ] james strachan commented on CAMEL-3651: --- Here's some documentation around the curren

[jira] Created: (CAMEL-3651) create a simple way to expose a CamelContext as a black box component that can be easily reused in other CamelContext instances

create a simple way to expose a CamelContext as a black box component that can be easily reused in other CamelContext instances --- Key: CAMEL-3651

[jira] Commented: (CAMEL-3563) CamelContext should act like a Component (i.e. a TypeConverter of CamelContext -> CamelContextComponent)

[ https://issues.apache.org/jira/browse/CAMEL-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984710#action_12984710 ] james strachan commented on CAMEL-3563: --- @Hadrian Right now any bean in the Spring c

[jira] Commented: (CAMEL-3566) camel-jms - Add option logWarnWhenReplyToIsDiscarded to disable WARN log if JMSReplyTo is being discarded

[ https://issues.apache.org/jira/browse/CAMEL-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984248#action_12984248 ] james strachan commented on CAMEL-3566: --- Whether a user wants a WARN about this or no

[jira] Commented: (CAMEL-3563) CamelContext should act like a Component (i.e. a TypeConverter of CamelContext -> CamelContextComponent)

[ https://issues.apache.org/jira/browse/CAMEL-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984102#action_12984102 ] james strachan commented on CAMEL-3563: --- in pure Spring / web app worlds, we can rely

[jira] Created: (CAMEL-3563) CamelContext should act like a Component (i.e. a TypeConverter of CamelContext -> CamelContextComponent)

CamelContext should act like a Component (i.e. a TypeConverter of CamelContext -> CamelContextComponent) Key: CAMEL-3563 URL: https://issues.apache.org/jira/b

[jira] Created: (CAMEL-3561) camel archetypes generate warnings in mvn 3.0.2

camel archetypes generate warnings in mvn 3.0.2 --- Key: CAMEL-3561 URL: https://issues.apache.org/jira/browse/CAMEL-3561 Project: Camel Issue Type: Improvement Components: tooling

[jira] Created: (CAMEL-3501) missing @Required annotation from setter methods on a few model definitions...

missing @Required annotation from setter methods on a few model definitions... -- Key: CAMEL-3501 URL: https://issues.apache.org/jira/browse/CAMEL-3501 Project: Camel

[jira] Created: (CAMEL-3046) split the camel-groovy and camel-ruby support code into camel-web-groovy and camel-web-ruby jars that a use can add if they wish but can keep the WAR size down if not requ

split the camel-groovy and camel-ruby support code into camel-web-groovy and camel-web-ruby jars that a use can add if they wish but can keep the WAR size down if not required -

[jira] Commented: (CAMEL-3046) split the camel-groovy and camel-ruby support code into camel-web-groovy and camel-web-ruby jars that a use can add if they wish but can keep the WAR size down if not re

[ https://issues.apache.org/activemq/browse/CAMEL-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61159#action_61159 ] James Strachan commented on CAMEL-3046: --- we can create an integration test with both de

[jira] Resolved: (CAMEL-3036) camel-web seems a bit borked viewing an endpoint in tomcat

[ https://issues.apache.org/activemq/browse/CAMEL-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-3036. --- Resolution: Fixed > camel-web seems a bit borked viewing an endpoint in tomcat >

[jira] Resolved: (CAMEL-3035) provide an optional interface Endpoints can provide to generate a simple String ID which can be used within the class loader to make JMX / REST APIs simpler to avoid havi

[ https://issues.apache.org/activemq/browse/CAMEL-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-3035. --- Resolution: Fixed > provide an optional interface Endpoints can provide to generate a sim

[jira] Assigned: (CAMEL-3035) provide an optional interface Endpoints can provide to generate a simple String ID which can be used within the class loader to make JMX / REST APIs simpler to avoid havi

[ https://issues.apache.org/activemq/browse/CAMEL-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan reassigned CAMEL-3035: - Assignee: James Strachan > provide an optional interface Endpoints can provide to gen

[jira] Created: (CAMEL-3036) camel-web seems a bit borked viewing an endpoint in tomcat

camel-web seems a bit borked viewing an endpoint in tomcat -- Key: CAMEL-3036 URL: https://issues.apache.org/activemq/browse/CAMEL-3036 Project: Apache Camel Issue Type: Bug Affects

[jira] Created: (CAMEL-3035) provide an optional interface Endpoints can provide to generate a simple String ID which can be used within the class loader to make JMX / REST APIs simpler to avoid havin

provide an optional interface Endpoints can provide to generate a simple String ID which can be used within the class loader to make JMX / REST APIs simpler to avoid having to encode large URIs ---

[jira] Commented: (CAMEL-3028) migrate the web console away from JSP + JSTL + JSP EL + SiteMesh + other stuff -> Scalate for a simpler, smaller & more DRY template engine

[ https://issues.apache.org/activemq/browse/CAMEL-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61077#action_61077 ] James Strachan commented on CAMEL-3028: --- BTW it looks like recent Jersey libraries are

[jira] Resolved: (CAMEL-3028) migrate the web console away from JSP + JSTL + JSP EL + SiteMesh + other stuff -> Scalate for a simpler, smaller & more DRY template engine

[ https://issues.apache.org/activemq/browse/CAMEL-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-3028. --- Resolution: Fixed > migrate the web console away from JSP + JSTL + JSP EL + SiteMesh + ot

[jira] Created: (CAMEL-3028) migrate the web console away from JSP + JSTL + JSP EL + SiteMesh + other stuff -> Scalate for a simpler, smaller & more DRY template engine

migrate the web console away from JSP + JSTL + JSP EL + SiteMesh + other stuff -> Scalate for a simpler, smaller & more DRY template engine ---

[jira] Created: (CAMEL-2989) provider an API to query available endpoints on a component

provider an API to query available endpoints on a component --- Key: CAMEL-2989 URL: https://issues.apache.org/activemq/browse/CAMEL-2989 Project: Apache Camel Issue Type: Improvement

[jira] Created: (CAMEL-2976) we should have a way to save updated routes to an XML directory somewhere so if folks update routes at runtime they can save them on disk & move them into source control

we should have a way to save updated routes to an XML directory somewhere so if folks update routes at runtime they can save them on disk & move them into source control ---

[jira] Commented: (CAMEL-2920) more eager validation of routes

[ https://issues.apache.org/activemq/browse/CAMEL-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60538#action_60538 ] James Strachan commented on CAMEL-2920: --- great stuff! :) > more eager validation of ro

[jira] Created: (CAMEL-2920) more eager validation of routes

more eager validation of routes Key: CAMEL-2920 URL: https://issues.apache.org/activemq/browse/CAMEL-2920 Project: Apache Camel Issue Type: Improvement Components: camel-core Affects Versions:

[jira] Resolved: (CAMEL-2913) mark required properties in the EIP model so they can be introspected by tooling

[ https://issues.apache.org/activemq/browse/CAMEL-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-2913. --- Resolution: Fixed added a @Required annotation on setter methods to mark things that a UI

[jira] Created: (CAMEL-2913) mark required properties in the EIP model so they can be introspected by tooling

mark required properties in the EIP model so they can be introspected by tooling Key: CAMEL-2913 URL: https://issues.apache.org/activemq/browse/CAMEL-2913 Project: Apache

[jira] Created: (CAMEL-2910) make it easy to store layout x,y and width,height values on each EIP node for visualisation and editing tooling

make it easy to store layout x,y and width,height values on each EIP node for visualisation and editing tooling --- Key: CAMEL-2910 URL: https://issues.apa

[jira] Resolved: (CAMEL-2910) make it easy to store layout x,y and width,height values on each EIP node for visualisation and editing tooling

[ https://issues.apache.org/activemq/browse/CAMEL-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-2910. --- Resolution: Fixed DescriptionDefintion now has optional XML attribute properties for lay

[jira] Commented: (CAMEL-1398) send message from web console adds http headers

[ https://issues.apache.org/activemq/browse/CAMEL-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60402#action_60402 ] James Strachan commented on CAMEL-1398: --- I actually think including the http headers is

[jira] Resolved: (CAMEL-2893) (FromDefintion|ToDefinition).getUriOrRef tend to return null when they should return a URI

[ https://issues.apache.org/activemq/browse/CAMEL-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-2893. --- Resolution: Fixed > (FromDefintion|ToDefinition).getUriOrRef tend to return null when the

[jira] Commented: (CAMEL-2893) (FromDefintion|ToDefinition).getUriOrRef tend to return null when they should return a URI

[ https://issues.apache.org/activemq/browse/CAMEL-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60392#action_60392 ] James Strachan commented on CAMEL-2893: --- this only tends to affect graph drawing tools

[jira] Created: (CAMEL-2893) (FromDefintion|ToDefinition).getUriOrRef tend to return null when they should return a URI

(FromDefintion|ToDefinition).getUriOrRef tend to return null when they should return a URI -- Key: CAMEL-2893 URL: https://issues.apache.org/activemq/browse/CAMEL-2893

[jira] Resolved: (CAMEL-2891) URIs for viewing a route as a language clashes with any other possible sub resource for routes (such as status)

[ https://issues.apache.org/activemq/browse/CAMEL-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-2891. --- Fix Version/s: 2.4.0 (was: 2.5.0) Resolution: Fixed we now

[jira] Created: (CAMEL-2892) remove ugly warnings running tests since upgrading to jetty 7

remove ugly warnings running tests since upgrading to jetty 7 - Key: CAMEL-2892 URL: https://issues.apache.org/activemq/browse/CAMEL-2892 Project: Apache Camel Issue Type: Improveme

[jira] Resolved: (CAMEL-2892) remove ugly warnings running tests since upgrading to jetty 7

[ https://issues.apache.org/activemq/browse/CAMEL-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-2892. --- Resolution: Fixed > remove ugly warnings running tests since upgrading to jetty 7 > -

[jira] Created: (CAMEL-2891) URIs for viewing a route as a language clashes with any other possible sub resource for routes (such as status)

URIs for viewing a route as a language clashes with any other possible sub resource for routes (such as status) --- Key: CAMEL-2891 URL: https://issues.apa

[jira] Resolved: (CAMEL-2883) current use of generics on the model package seems to cause issues in Scala-land when trying to use the model objects to build up routes

[ https://issues.apache.org/activemq/browse/CAMEL-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-2883. --- Resolution: Fixed committed in rev: 959563. > current use of generics on the model packa

[jira] Created: (CAMEL-2883) current use of generics on the model package seems to cause issues in Scala-land when trying to use the model objects to build up routes

current use of generics on the model package seems to cause issues in Scala-land when trying to use the model objects to build up routes Key: C

[jira] Created: (CAMEL-2874) review the ActiveMQ and JMS wiki pages to check they are correct for pooling configuration documentation

review the ActiveMQ and JMS wiki pages to check they are correct for pooling configuration documentation Key: CAMEL-2874 URL: https://issues.apache.org/active

[jira] Created: (CAMEL-2801) add @Tooltip and/or @Description to NodeDefintion classes in org.apache.camel.model

add @Tooltip and/or @Description to NodeDefintion classes in org.apache.camel.model Key: CAMEL-2801 URL: https://issues.apache.org/activemq/browse/CAMEL-2801 Projec

[jira] Commented: (CAMEL-2613) CamelProxy - Add option to treat void methods as InOnly for fire and forget style messaging

[ https://issues.apache.org/activemq/browse/CAMEL-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58676#action_58676 ] James Strachan commented on CAMEL-2613: --- my worry is really folks losing exceptions wit

[jira] Created: (CAMEL-2406) a jmx version of the bean endpoint, where beans are looked up using their JMX ObjectName instead...

a jmx version of the bean endpoint, where beans are looked up using their JMX ObjectName instead... --- Key: CAMEL-2406 URL: https://issues.apache.org/activemq/browse/

[jira] Created: (CAMEL-2405) JMX notification listener to route JMX events to camel

JMX notification listener to route JMX events to camel -- Key: CAMEL-2405 URL: https://issues.apache.org/activemq/browse/CAMEL-2405 Project: Apache Camel Issue Type: Improvement

[jira] Created: (CAMEL-2347) create a Nagios endpoint to allow the sending of alerts to the Nagios monitoring system

create a Nagios endpoint to allow the sending of alerts to the Nagios monitoring system --- Key: CAMEL-2347 URL: https://issues.apache.org/activemq/browse/CAMEL-2347

[jira] Resolved: (CAMEL-2301) switch to jackson for cleaner JSON marshalling of data

[ https://issues.apache.org/activemq/browse/CAMEL-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-2301. --- Resolution: Fixed > switch to jackson for cleaner JSON marshalling of data >

[jira] Created: (CAMEL-2301) switch to jackson for cleaner JSON marshalling of data

switch to jackson for cleaner JSON marshalling of data -- Key: CAMEL-2301 URL: https://issues.apache.org/activemq/browse/CAMEL-2301 Project: Apache Camel Issue Type: Improvement C

[jira] Assigned: (CAMEL-2301) switch to jackson for cleaner JSON marshalling of data

[ https://issues.apache.org/activemq/browse/CAMEL-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan reassigned CAMEL-2301: - Assignee: James Strachan > switch to jackson for cleaner JSON marshalling of data > -

[jira] Resolved: (CAMEL-2280) xml returned by camel-web should avoid using a namespace prefix

[ https://issues.apache.org/activemq/browse/CAMEL-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-2280. --- Resolution: Fixed patch applied; now using no namespace prefix for routes as XML; though

[jira] Commented: (CAMEL-2280) xml returned by camel-web should avoid using a namespace prefix

[ https://issues.apache.org/activemq/browse/CAMEL-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56495#action_56495 ] James Strachan commented on CAMEL-2280: --- FWIW my main aim was to ditch the ugly "ns2" s

[jira] Commented: (CAMEL-2280) xml returned by camel-web should avoid using a namespace prefix

[ https://issues.apache.org/activemq/browse/CAMEL-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56494#action_56494 ] James Strachan commented on CAMEL-2280: --- I've a fix i'm about to apply shortly. One of

[jira] Commented: (CAMEL-2298) create an index of the SOA Patterns from http://www.soapatterns.org/ along with how to implement them in Camel

[ https://issues.apache.org/activemq/browse/CAMEL-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56483#action_56483 ] James Strachan commented on CAMEL-2298: --- I've started a wiki page here... http://cwiki

[jira] Created: (CAMEL-2298) create an index of the SOA Patterns from http://www.soapatterns.org/ along with how to implement them in Camel

create an index of the SOA Patterns from http://www.soapatterns.org/ along with how to implement them in Camel -- Key: CAMEL-2298 URL: https://issues.apach

[jira] Created: (CAMEL-2280) xml returned by camel-web should avoid using a namespace prefix

xml returned by camel-web should avoid using a namespace prefix --- Key: CAMEL-2280 URL: https://issues.apache.org/activemq/browse/CAMEL-2280 Project: Apache Camel Issue Type: Impro

[jira] Created: (CAMEL-2279) create a camel-web demo to show folks how they can create their own WARs with camel-web integrated along with whatever routes & components they want

create a camel-web demo to show folks how they can create their own WARs with camel-web integrated along with whatever routes & components they want

[jira] Created: (CAMEL-2229) switch to slf4j / logback by default as we'll get accurate version information in stack traces, plus MDC support (and neater ways to avoid the "if (LOG.isDebugEnabled())"

switch to slf4j / logback by default as we'll get accurate version information in stack traces, plus MDC support (and neater ways to avoid the "if (LOG.isDebugEnabled())" stuff

[jira] Created: (CAMEL-2130) add a Visitor API to the org.apache.camel.model package so you can visit a RouteDefinition, a set of RouteDefinitions or a subset of a route to determine things like langu

add a Visitor API to the org.apache.camel.model package so you can visit a RouteDefinition, a set of RouteDefinitions or a subset of a route to determine things like languages & endpoints used etc

[jira] Commented: (CAMEL-1619) nightly CI build doesn't deploy the website - the online javadoc is ancient

[ https://issues.apache.org/activemq/browse/CAMEL-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55145#action_55145 ] James Strachan commented on CAMEL-1619: --- still broken :) > nightly CI build doesn't de

[jira] Created: (CAMEL-2003) use enhanced log4j configuration

use enhanced log4j configuration Key: CAMEL-2003 URL: https://issues.apache.org/activemq/browse/CAMEL-2003 Project: Apache Camel Issue Type: Improvement Reporter: James Strachan With a minor twe

[jira] Commented: (CAMEL-1900) Need to allow adding of model definitions and processors in camel components without involving the camel-core

[ https://issues.apache.org/activemq/browse/CAMEL-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53593#action_53593 ] James Strachan commented on CAMEL-1900: --- Just a general idea on the cache endpoint. If

[jira] Created: (CAMEL-1843) improve the CSS so that code looks better on the site

improve the CSS so that code looks better on the site - Key: CAMEL-1843 URL: https://issues.apache.org/activemq/browse/CAMEL-1843 Project: Apache Camel Issue Type: Improvement Com

[jira] Created: (CAMEL-1802) provide XML/JSON representation of RouteStatusResource.getStatus

provide XML/JSON representation of RouteStatusResource.getStatus Key: CAMEL-1802 URL: https://issues.apache.org/activemq/browse/CAMEL-1802 Project: Apache Camel Issue Type: Imp

[jira] Resolved: (CAMEL-1734) Progress OpenEdge Component

[ https://issues.apache.org/activemq/browse/CAMEL-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-1734. --- Resolution: Fixed Fix Version/s: (was: 2.1.0) I've spun up a little Forge proj

[jira] Commented: (CAMEL-1734) Progress OpenEdge Component

[ https://issues.apache.org/activemq/browse/CAMEL-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52543#action_52543 ] James Strachan commented on CAMEL-1734: --- Since folks at Apache won't be able to even co

[jira] Commented: (CAMEL-1631) create a properties component so that endpoints can be created where the URI is looked up in a properties file at runtime

[ https://issues.apache.org/activemq/browse/CAMEL-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51780#action_51780 ] James Strachan commented on CAMEL-1631: --- similar versions of this could be done to use

[jira] Created: (CAMEL-1631) create a properties component so that endpoints can be created where the URI is looked up in a properties file at runtime

create a properties component so that endpoints can be created where the URI is looked up in a properties file at runtime - Key: CAMEL-1631 URL

[jira] Created: (CAMEL-1619) nightly CI build doesn't deploy the website - the online javadoc is ancient

nightly CI build doesn't deploy the website - the online javadoc is ancient --- Key: CAMEL-1619 URL: https://issues.apache.org/activemq/browse/CAMEL-1619 Project: Apache Camel

[jira] Commented: (CAMEL-1536) add an integration test for Camel in OSGi containers like Felix and Equinox

[ https://issues.apache.org/activemq/browse/CAMEL-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51232#action_51232 ] James Strachan commented on CAMEL-1536: --- btw the test case is here.. http://svn.apache

[jira] Resolved: (CAMEL-1536) add an integration test for Camel in OSGi containers like Felix and Equinox

[ https://issues.apache.org/activemq/browse/CAMEL-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-1536. --- Resolution: Fixed added a test case OSGiIntegrationTest using [Pax Exam|http://wiki.ops4

[jira] Created: (CAMEL-1536) add an integration test for Camel in OSGi containers like Felix and Equinox

add an integration test for Camel in OSGi containers like Felix and Equinox --- Key: CAMEL-1536 URL: https://issues.apache.org/activemq/browse/CAMEL-1536 Project: Apache Camel

[jira] Resolved: (CAMEL-1531) upgrade the guice module to GuiceyFruit 2.0-beta-6

[ https://issues.apache.org/activemq/browse/CAMEL-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-1531. --- Resolution: Fixed trunk now uses 2.0-beta-6 > upgrade the guice module to GuiceyFruit 2.

[jira] Created: (CAMEL-1531) upgrade the guice module to GuiceyFruit 2.0-beta-6

upgrade the guice module to GuiceyFruit 2.0-beta-6 -- Key: CAMEL-1531 URL: https://issues.apache.org/activemq/browse/CAMEL-1531 Project: Apache Camel Issue Type: Improvement Component

[jira] Assigned: (CAMEL-1531) upgrade the guice module to GuiceyFruit 2.0-beta-6

[ https://issues.apache.org/activemq/browse/CAMEL-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan reassigned CAMEL-1531: - Assignee: James Strachan > upgrade the guice module to GuiceyFruit 2.0-beta-6 > -

[jira] Commented: (CAMEL-234) support the auto-reloading of Camel routing rules from XML

[ https://issues.apache.org/activemq/browse/CAMEL-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50936#action_50936 ] James Strachan commented on CAMEL-234: -- So using OSGi (e.g. the ServiceMix Kernel) this w

[jira] Commented: (CAMEL-838) add support for common transaction for files

[ https://issues.apache.org/activemq/browse/CAMEL-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50763#action_50763 ] James Strachan commented on CAMEL-838: -- Wonder if there's an OSS project out there doing

[jira] Commented: (CAMEL-1142) FailoverLoadBalancer

[ https://issues.apache.org/activemq/browse/CAMEL-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50699#action_50699 ] James Strachan commented on CAMEL-1142: --- Being able to set a [Redelivery Policy|http:/

[jira] Commented: (CAMEL-1142) FailoverLoadBalancer

[ https://issues.apache.org/activemq/browse/CAMEL-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50698#action_50698 ] James Strachan commented on CAMEL-1142: --- be nice to use this in the DSL something like

[jira] Commented: (CAMEL-1005) should we have an annotation - maybe @Handler or something which can mark a method as being the default method invoked by the Bean Binding if no other Camel annotations

[ https://issues.apache.org/activemq/browse/CAMEL-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50532#action_50532 ] James Strachan commented on CAMEL-1005: --- I think I'd rather a new annotation than requi

[jira] Commented: (CAMEL-1005) should we have an annotation - maybe @Handler or something which can mark a method as being the default method invoked by the Bean Binding if no other Camel annotations

[ https://issues.apache.org/activemq/browse/CAMEL-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50528#action_50528 ] James Strachan commented on CAMEL-1005: --- If there are multiple possible methods then th

  1   2   >