Should we back out the use of graphviz too? Do you think generating images
for camel routes should be -1'd too?
On 28 November 2013 13:41, James Strachan james.strac...@gmail.com wrote:
On 28 November 2013 13:32, Daniel Kulp dk...@apache.org wrote:
I’m -1 to this commit. I don’t think we
On 28 November 2013 13:32, Daniel Kulp dk...@apache.org wrote:
I’m -1 to this commit. I don’t think we should be adding a bunch of
targets for all the various container/platform integrations.
If that were true I'd maybe -1 it too; but this commit looks to be about
making it easy for Camel
I wonder if we should experiment with a BOM file?
http://stackoverflow.com/questions/14874966/how-to-use-bom-iwith-maven
then the camel project could import the BOM file and other projects
could share it too (without having to go the parent pom.xml route).
On 15 August 2013 12:26, Claus Ibsen
On 29 April 2013 09:01, Babak Vahdat babak.vah...@swissonline.ch wrote:
Am 29.04.13 08:00 schrieb James Strachan unter
james.strac...@gmail.com:
On 28 April 2013 23:46, Babak Vahdat babak.vah...@swissonline.ch wrote:
Hi James,
Another awesome stuff of yours, Thanks!
Though I've got three
On 30 April 2013 08:58, Babak Vahdat babak.vah...@swissonline.ch wrote:
I did the following changes to make the CI build work again on JDK 1.6:
https://github.com/apache/camel/blob/trunk/camel-core/pom.xml#L395
https://github.com/apache/camel/blob/trunk/components/pom.xml#L214
Makes sense?
Endpoint documentation is manually created on the wiki which is quite
error prone; plus the wiki page has to then cope with every version of
Camel we release and is very easy to get stale and incorrect - and
with all the 'since version X' text its confusing for users.
Additionally its hard for
:47, James Strachan james.strac...@gmail.com wrote:
Endpoint documentation is manually created on the wiki which is quite
error prone; plus the wiki page has to then cope with every version of
Camel we release and is very easy to get stale and incorrect - and
with all the 'since version X' text
On 27 March 2013 07:03, Claus Ibsen claus.ib...@gmail.com wrote:
On Tue, Mar 26, 2013 at 5:15 PM, Henryk Konsek hekon...@gmail.com wrote:
Do you guys read the javadoc of the Java DSL? We have java doc on the
DSL where we provide a little information.
I know you aren't referring to me, but I'm
On 27 January 2013 18:25, Christian Müller christian.muel...@gmail.com wrote:
... and to make it precise. By writing fighting for it I mean:
- add missing features to Karaf WebConsole
- provide better documentation (for users and developers)
- make it as easy as possible to install it
- and
On 25 January 2013 22:23, Raul Kripalani r...@evosent.com wrote:
So if the reason for trashing the console out of the Camel code base is the
proven lack of development focus on it, I wonder if it'd make sense to
contact the person behind the camelwatch project to ask if he'd be willing
to
On 25 January 2013 08:07, Charles Moulliard ch0...@gmail.com wrote:
+1 for the project plan and if you are interested I can play the role of
Project Manager to coordinate all the different tasks, actions, define a
plan and
following
manage it
Concerning the webconsole, http://hawt.io
I'd be in favour of moving it to a sandbox so folks can tinker with it
if they want.
On 25 January 2013 16:57, Hadrian Zbarcea hzbar...@gmail.com wrote:
In the context of a few web based consoles available for Camel, including
the Karaf console and the recently announced hawt.io, the question
Thanks for the feedback Raul! More inline...
On 21 October 2012 11:58, Raul Kripalani r...@evosent.com wrote:
Hi James,
The idea looks nice. I'm just a bit concerned about whether the concept
steps on the toes of the interceptSendToEndpoint DSL to some extent?
The interceptSTE DSL only
Inspired by the SwitchYard project and how it uses contracts in SCA, I
thought I'd take a stab at adding something vaguely similar to Camel;
to allow us to add bindings to an endpoint (e.g. ensuring a particular
Data Format is used in or out of the endpoint, to add a validation
step , add
=1400019view=markup
On 19 October 2012 11:13, James Strachan james.strac...@gmail.com wrote:
Inspired by the SwitchYard project and how it uses contracts in SCA, I
thought I'd take a stab at adding something vaguely similar to Camel;
to allow us to add bindings to an endpoint (e.g. ensuring
-1
I see no real reason to break stuff
On 19 June 2012 19:37, Hadrian Zbarcea hzbar...@gmail.com wrote:
Using URIs to identify and configure Endpoints is a notable Apache Camel
innovation. This feature was present in Camel from its first release. The
definition of the URIs syntax in
+1
On 2 December 2011 15:57, Jean-Baptiste Onofré j...@nanthrax.net wrote:
Hi Claus,
fully agree, and in fact, it's in my TODO list.
If all are agree, I will do it :).
I plan to commit Karaf sub-shell (on Karaf trunk) over the week end.
What do you think to update Camel trunk to start to
On 2 December 2011 15:29, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
On the Karaf @dev they are talking about changing the naming of the commands.
http://karaf.922171.n3.nabble.com/PROPOSAL-New-Karaf-commands-norm-td3430815.html
eg
camel:list-routes -- camel:route-list
Or we could even
The manual seems borked - it contains:
Download of http://camel.apache.org/book-in-one-page.html failed
On 2 November 2011 02:30, Hadrian Zbarcea hzbar...@gmail.com wrote:
A new release candidate apache-camel-2.9.0-RC1 is out with approximately 305
issues resolved so far: improvements and bug
did it manually in the past releases.
There is an open jira for it assigned to me that was a moving target for a
while now. With a workaround available, not a high priority for me. James,
contributions highly appreciated :).
Hadrian
On 11/03/2011 07:43 AM, James Strachan wrote:
The manual
On 17 October 2011 10:03, Jean-Baptiste Onofré j...@nanthrax.net wrote:
Hi Claus,
You are right: it depends if the command accepts several bundles or not.
For instance:
- bundles:start 23 34 56
- system:shutdown (no argument)
On trunk, you will see bundle:* or bundles:* commands. It's
[
https://issues.apache.org/jira/browse/CAMEL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114592#comment-13114592
]
james strachan commented on CAMEL-4256:
---
Endpoints are already beans you can
[
https://issues.apache.org/jira/browse/CAMEL-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13097145#comment-13097145
]
james strachan commented on CAMEL-4417:
---
Since this code change will break pretty
[
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
On 5 September 2011 14:04, Christian Schneider ch...@die-schneider.net wrote:
Hi all,
I am currently trying to minimize the use of impl classes in components and
check how to completely hide impl classes for 3.0.
So I will have to move several classes from impl to support as they are used
On 1 September 2011 02:01, Hadrian Zbarcea hzbar...@gmail.com wrote:
Personally, I don't think we need a big jar. My understanding is that
Christian is looking for ways to *improve* modularity and reduce
dependencies.
But he was suggesting making camel-core bigger adding in more
dependencies
Agreed. If the issue is test time, just make the test cases call stop
asynchronously?
On 2 August 2011 07:43, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
The stop operation on the consumer is synchronous to ensure the
operation goes well.
I am not to keen that this is changed just with the
URL: https://issues.apache.org/jira/browse/CAMEL-4281
Project: Camel
Issue Type: Improvement
Reporter: james strachan
then via JMX or code folks can browse the available messages
--
This message is automatically generated by JIRA.
For more information
On 20 July 2011 16:56, Daniel Kulp dk...@apache.org wrote:
I asked Hadrian and he didn't know and James hasn't responded, so I'll ask
here.
Does anyone know who's crontab the rsync of the site from the cwiki staging
area to /www/camel.apache.org is running?
It's not currently preserving
On 22 July 2011 11:32, Guillaume Nodet gno...@gmail.com wrote:
On Fri, Jul 22, 2011 at 10:55, Christian Schneider
ch...@die-schneider.net wrote:
Hi all,
I have taken a look at the current Java DSL. There i especially one thing
that bugs me.
When we configure defintion like threads we do
, James Strachan ja...@fusesource.com
wrote:
I still don't get it - maybe I'm just dumb.
So we need to delete all web pages hosted at apache that even talk
about using, say, JAXB - since its not some source code in an Apache
repo? A web page at Apache can only talk about source code hosted
On 20 July 2011 17:43, Eric Johnson ericjohn...@apache.org wrote:
My understanding of what Dan is saying is that since the Scalate
component is not developed as part of the Apache Camel project it
cannot be documented in a way that makes it look like it is a part of
the Apache Camel project.
Dan could you please explain why you're deleting pages from the wiki which
describe open source camel components without first at least having a
discussion about it?
On 19 July 2011 18:54, conflue...@apache.org wrote:
Scalate Page *removed* by Daniel
+1
On 20 July 2011 12:15, Christian Schneider ch...@die-schneider.net wrote:
+1
Btw. the release builds quite well even on windows. Only got some test
failures in camel-ftp.
Christian
Am 19.07.2011 04:13, schrieb Zbarcea Hadrian:
A new minor release apache-camel-2.8.0 is out with
?
On 20 July 2011 16:43, Daniel Kulp dk...@apache.org wrote:
On Wednesday, July 20, 2011 8:47:19 AM James Strachan wrote:
Dan could you please explain why you're deleting pages from the wiki which
describe open source camel components without first at least having a
discussion about
On 20 July 2011 16:43, Daniel Kulp dk...@apache.org wrote:
On Wednesday, July 20, 2011 8:47:19 AM James Strachan wrote:
Dan could you please explain why you're deleting pages from the wiki which
describe open source camel components without first at least having a
discussion about
Reporter: james strachan
Package scanning to discover classes annotated with @Converter is slow. Plus on
many containers (especially commercial JEE containers) its not even possible;
since ClassLoader.getResource() doesn't often return file system based URIs you
can easily convert
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
[
https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13052046#comment-13052046
]
james strachan commented on CAMEL-4122:
---
In ActiveMQ and ServiceMix you can view
[
https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13052047#comment-13052047
]
james strachan commented on CAMEL-4122:
---
BTW you can create endpoints via the Java
Agreed. I think we need to step back a little and think a little more
about our users first and helping them get started with Apache Camel;
figuring out guidelines on which pages can/can't have a link to an
external document comes second.
On 4 May 2011 14:17, Jon Anstey jans...@gmail.com wrote:
On 4 May 2011 15:24, Hadrian Zbarcea hzbar...@gmail.com wrote:
Mule is also an open source project and that had more of a relevance when
Camel started and was a Mule competitor. That page can go away too.
As James brilliantly stated: let's think of the Camel user's needs and
address them.
Agreed. Folks are always asking how things like Camel compares to X.
On 4 May 2011 15:33, Claus Ibsen claus.ib...@gmail.com wrote:
On Wed, May 4, 2011 at 4:24 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:
Mule is also an open source project and that had more of a relevance when
Camel started
Wouldn't a tool using a combination of introspection javadoc help
make sure the documentation is up to date valid? It'd work on most
endpoints today without much extra work. Adding extra annotations
could help; but I'd rather have better tools so that code can be more
DRY. e.g. it seems silly
Liking C4 plus its not too tall
On 29 March 2011 09:08, Rob Davies rajdav...@gmail.com wrote:
I'll try a jpeg
On 28 Mar 2011, at 18:07, Richard Kettelerij wrote:
No attachment here
On Mon, Mar 28, 2011 at 7:05 PM, Rob Davies rajdav...@gmail.com wrote:
weird - it was a pdf - anybody else
On 29 March 2011 11:23, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
I like C4 as well (from Robs JPEG) but I wonder if we can have a
version without the grey box?
Just to see how that goes as well.
Yeah; though I do like the idea of some kind of box/background around
the text; seems to add a
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
On 19 October 2010 13:19, James Strachan james.strac...@gmail.com wrote:
On 19 October 2010 12:54, Willem Jiang willem.ji...@gmail.com wrote:
On 10/19/10 6:06 PM, James Strachan wrote:
[snip]
Implementing Protocols
=
So the realisation we came to was, we just need to combine
?
--
Key: CAMEL-3736
URL: https://issues.apache.org/jira/browse/CAMEL-3736
Project: Camel
Issue Type: Task
Reporter: james
: https://issues.apache.org/jira/browse/CAMEL-3737
Project: Camel
Issue Type: Task
Reporter: james strachan
Right now its possible in XML to specify both kinds of configuration;
batchConfig and streamConfig. This isn't ideal and the definition is a bit
floored
[
https://issues.apache.org/jira/browse/CAMEL-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13000872#comment-13000872
]
james strachan commented on CAMEL-3737:
---
Looks like the LoadBalancerDefinition needs
[
https://issues.apache.org/jira/browse/CAMEL-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13000878#comment-13000878
]
james strachan commented on CAMEL-3737:
---
LoadBalancerDefinition is fine in trunk
[
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
[
https://issues.apache.org/jira/browse/CAMEL-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12997879#comment-12997879
]
james strachan commented on CAMEL-3693:
---
another validation rule to watch. Patterns
[
https://issues.apache.org/jira/browse/CAMEL-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12997898#comment-12997898
]
james strachan commented on CAMEL-3693:
---
another one I spotted
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
Project: Camel
Issue Type: Improvement
Reporter: james strachan
Its very easy for us to create JAXB objects which can only be used from JAXB
marshalling and not from Java code or introspection. Or that we can introduce
JAXB bugs by inconsistent annotation usage.
We
Key: CAMEL-3696
URL: https://issues.apache.org/jira/browse/CAMEL-3696
Project: Camel
Issue Type: Improvement
Reporter: james strachan
[
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 ListExpressionDefinition
The camel-spring.xsd file
http://camel.apache.org/schema/spring/
was pretty crusty (looking like its from somewhere between 2.3 and 2.4).
-rw-rw-r-- 1 hadriancamel 87245 Jun 3 2010 camel-spring.xsd
It looks like we've not been updating this since about 2.4.0 onwards.
I've just
+1, sooner the better
On 18 February 2011 12:19, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
Now that the major migration efforts for Camel 2.7 is in-house
(JDK1.6,spring3,slf4j, etc.). and the fact that we did this really
fast.
Thanks everyone.
I would like to propose that we consider
On 17 February 2011 08:48, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
DSL in plain Java is somewhat limited how far you can go with Java and
Generics.
A common issue over the times has been the Content Based Router where
users would use other complex patterns inside the when/otherwise
[
https://issues.apache.org/jira/browse/CAMEL-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993425#comment-12993425
]
james strachan commented on CAMEL-3563:
---
See the documentation: https
[
https://issues.apache.org/jira/browse/CAMEL-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993426#comment-12993426
]
james strachan commented on CAMEL-3651:
---
Code complete and tested though we could do
URL: https://issues.apache.org/jira/browse/CAMEL-3651
Project: Camel
Issue Type: New Feature
Reporter: james strachan
Assignee: james strachan
Fix For: 2.7.0
see these discussions for background
http://camel.465427.n5
[
https://issues.apache.org/jira/browse/CAMEL-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993116#comment-12993116
]
james strachan commented on CAMEL-3651:
---
Here's some documentation around
+1
On 25 January 2011 03:14, Hadrian Zbarcea hzbar...@gmail.com wrote:
A new release apache-camel-2.6.0 is out with approximately 297 issues
resolved: new features, improvements and bug fixes.
Please find the staging repo here:
[
https://issues.apache.org/jira/browse/CAMEL-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984710#action_12984710
]
james strachan commented on CAMEL-3563:
---
@Hadrian
Right now any bean in the Spring
/browse/CAMEL-3563
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: james strachan
Fix For: 2.6.0
Imagine you have a camelContext.xml for production use (e.g. you're creating an
OSGi bundle with a camelContext.xml
[
https://issues.apache.org/jira/browse/CAMEL-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984102#action_12984102
]
james strachan commented on CAMEL-3563:
---
in pure Spring / web app worlds, we can rely
[
https://issues.apache.org/jira/browse/CAMEL-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984248#action_12984248
]
james strachan commented on CAMEL-3566:
---
Whether a user wants a WARN about
Reporter: james strachan
Fix For: 2.6.0
We're missing some plugin versions in the generated pom.xml files...
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 61, column 15
--
This message is automatically
Issue Type: Improvement
Components: camel-core
Reporter: james strachan
Fix For: 2.6.0
Here's a list of pattern and property that has missing @Required annotation.
There might be a few others I've missed, but at first look these look likely
candidates
{code
+1
On 13 December 2010 05:25, Hadrian Zbarcea hzbar...@gmail.com wrote:
As announced a few months back, the last maintenance release of camel-1.x,
apache-camel-1.6.4 is out with 7 issues resolved: improvements and bug fixes.
Please find the staging repo here:
On 11 November 2010 13:29, Jon Anstey jans...@gmail.com wrote:
I think this thread is over but I just wanted to agree on a point Johan (and
probably others) made here.
Not to mention if you actually fix a bug and submit a patch you could fix
documentation in one feel swoop.
That is an
FWIW I started an experimental spike to try recreate the Camel website
using wiki files from source control - exported from Confluence -
(rather than the Confluence / AutoExport icky stuff) like Karaf
ServiceMix are doing. More as a test of Scalate than any attempt to
actually change any
On 10 November 2010 13:40, Hadrian Zbarcea hzbar...@gmail.com wrote:
Thanks James,
You have to comment out the dependency on scalate-test in the pom for this to
work (otherwise you get a Failed to resolve artifact).
That aside, one of the important requirements I believe is not to raise the
On 10 November 2010 14:43, Guillaume Nodet gno...@gmail.com wrote:
On Wed, Nov 10, 2010 at 14:40, Hadrian Zbarcea hzbar...@gmail.com wrote:
Thanks James,
You have to comment out the dependency on scalate-test in the pom for this
to work (otherwise you get a Failed to resolve artifact).
On 10 November 2010 14:51, Daniel Kulp dk...@apache.org wrote:
On Wednesday 10 November 2010 9:43:13 am Guillaume Nodet wrote:
On Wed, Nov 10, 2010 at 14:40, Hadrian Zbarcea hzbar...@gmail.com wrote:
Thanks James,
You have to comment out the dependency on scalate-test in the pom for
this
On 10 November 2010 15:00, Hadrian Zbarcea hzbar...@gmail.com wrote:
That is true, but you can see your changes in the wiki right away.
I love the idea of having the docs version controlled, I understand all the
benefits. I am also convinced losing the ability to edit in place is a major
On 10 November 2010 15:15, Daniel Kulp dk...@apache.org wrote:
On Wednesday 10 November 2010 9:59:11 am James Strachan wrote:
On 10 November 2010 14:51, Daniel Kulp dk...@apache.org wrote:
For most of the people on this list, it ISN'T a big deal. We deal with
svn and mvn every day
On 10 November 2010 15:00, Hadrian Zbarcea hzbar...@gmail.com wrote:
That is true, but you can see your changes in the wiki right away.
I love the idea of having the docs version controlled, I understand all the
benefits. I am also convinced losing the ability to edit in place is a major
+1
On 26 October 2010 08:55, Jean-Baptiste Onofré j...@nanthrax.net wrote:
+1
Tested: focus on camel-cxf, camel-blueprint, camel-timer components. All
routes are working well. I begun the integration in ServiceMix.
Regards
JB
On 10/25/2010 11:19 PM, Hadrian Zbarcea wrote:
A new release
On 27 October 2010 14:58, falvarez falva...@ancap.com.uy wrote:
Claus,
I have one more question and not upset them more:
We have windows in our systems platform.
You can give us support for this platform?
Absolutely! :)
Its maybe better if we take this off the Apache lists to the
I've seen quite a few Camel riders doing very similar things over the
years; particularly in cases where teams are sharing routes with other
team or folks want to wrap up 'protocols' as something thats a black
box and easy to cookie-cut. The following is admittedly advanced usage
but seems common
On 19 October 2010 12:54, Willem Jiang willem.ji...@gmail.com wrote:
On 10/19/10 6:06 PM, James Strachan wrote:
[snip]
Implementing Protocols
=
So the realisation we came to was, we just need to combine a protocol
bean RouteBuilder and a Component into a single, simple bean
On 18 October 2010 10:43, Schneider Christian
christian.schnei...@enbw.com wrote:
Hi all,
I will have some free time in december as I am changing my employer. So I am
planning to work a little on some architectural improvements for camel 3.0.0.
As these things are very critical to the
On 18 October 2010 18:28, Hadrian Zbarcea hzbar...@gmail.com wrote:
I changed the thread name to [discuss].
I like that idea and it's something we contemplated in the past. This will
bring back the idea of getting the dsl out of core as well.
What benefits does that have BTW? IMHO more
On 19 October 2010 13:59, Schneider Christian
christian.schnei...@enbw.com wrote:
Hi James,
it is not absolutely necessary to split the jar into three jars. More
important is to have rules that say that a component developer should only
depdend on the API part and to check that the internal
On 19 October 2010 14:51, Hadrian Zbarcea hzbar...@gmail.com wrote:
The benefit if allowing developers to have their dsl that extends the camel
dsl. I get asked this question now and then (last time yesterday).
The only way to do it now is to have a separate dsl on top of the camel dsl.
Huh?
On 19 October 2010 15:06, Hadrian Zbarcea hzbar...@gmail.com wrote:
If you think it's a good idea, and I agree, then 3.0 *is* the right time to
do it. It's some 5-6 months away, there's plenty of time and I expect us to
get a lot of help from the growing community.
Pushing this for 4.0 is
Good idea!
We should make it as easy as possible to set conditional breakpoints
in your debugger using the available context and your IDE. e.g.
* the id of the Definition node in the route (stop at a specific point
in a route). e.g. condition: getDefinition().getId() == AMC
* the kind of node
On 18 October 2010 14:56, Claus Ibsen claus.ib...@gmail.com wrote:
On Mon, Oct 18, 2010 at 1:11 PM, James Strachan
james.strac...@gmail.com wrote:
Good idea!
We should make it as easy as possible to set conditional breakpoints
in your debugger using the available context and your IDE. e.g
On 29 September 2010 09:08, Claus Ibsen claus.ib...@gmail.com wrote:
James will cut the scalate 1.3 release next week.
Don't tell anyone, I'll be updating the site, blogging and announcing
tomorrow, but the 1.3 scalate release is in the FuseSource repo and
will be promoted to the central maven
On 24 September 2010 08:55, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
Okay so Karaf 2.1 is now in its final stages of the vote, so hopefully
that would go well so it can be released and available early next
week.
Then its a matter of having James Strachan do his Scalate 1.3 release
[
https://issues.apache.org/activemq/browse/CAMEL-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61159#action_61159
]
James Strachan commented on CAMEL-3046:
---
we can create an integration test with both
---
Key: CAMEL-3046
URL: https://issues.apache.org/activemq/browse/CAMEL-3046
Project: Apache Camel
Issue Type: Improvement
Components: camel-web
Reporter: James
-web
Affects Versions: 2.4.0
Reporter: James Strachan
Fix For: 2.5.0
rather than taking the URI and encoding it, it would be nice if endpoints could
just generate their own unique ID on construction (then we don't have lifecycle
issues of keeping track of endpoints
Affects Versions: 2.4.0
Reporter: James Strachan
Assignee: James Strachan
Fix For: 2.5.0
e.g. try mvn tomcat:run then try navigate to an endpoint to try send a
message to it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add
[
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
1 - 100 of 239 matches
Mail list logo
