Hi
Can you please use the @user mailing list for questions on how to do X
with Camel.
This is a @dev list for talks about development of the *project* itself.
The user list has many more ppl looking at it, and thus more people to help you.
On Mon, Jun 25, 2012 at 8:46 PM, Navengit wrote:
> I h
On Mon, Jun 25, 2012 at 8:22 PM, Daniel Kulp wrote:
> On Monday, June 25, 2012 08:20:12 PM Henryk Konsek wrote:
>> > That said, we should update to JIBX 1.2.4.5 as they made sure all the
>> > deps that they needed are available in central which GREATLY simplifies
>> > things. I updated CXF a while
I have a Java Struts 1.1 based application which has a JSP which is sending
an HTTP request to Jetty endpoint in my Camel application.
I have an object set in request.setAttribute.
How to get this object in my camel processor?
I am able to get the request parameters but not request attributes.
I h
I think that is the issue. JIBX 1.2.3 does not define additional repos and
the required dependencies are not available on central.
I took a look at 1.2.4.5, and there are no repos defined there either, but
all dependencies appear to be available on central.
-Tony
dk...@apache.org wrote
>
> T
The Apache Jenkins build system has built Camel.trunk.notest (build #1579)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1579/
to view the results.
On Monday, June 25, 2012 08:20:12 PM Henryk Konsek wrote:
> > That said, we should update to JIBX 1.2.4.5 as they made sure all the
> > deps that they needed are available in central which GREATLY simplifies
> > things. I updated CXF a while ago, just didn't get a chance to look at
> > Camel.
> Hi
> That said, we should update to JIBX 1.2.4.5 as they made sure all the deps
> that they needed are available in central which GREATLY simplifies things.
> I updated CXF a while ago, just didn't get a chance to look at Camel.
Hi Daniel,
Doesn't it fix this issue [1]?
[1] https://issues.apache.or
The jibx pom's from central should have the right repo defined in it.
That said, we should update to JIBX 1.2.4.5 as they made sure all the deps
that they needed are available in central which GREATLY simplifies things.
I updated CXF a while ago, just didn't get a chance to look at Camel.
D
> Is it possible to build routes dynamically based on a configuration file?
As Claus said, it is possible. However before you create routes
dynamically consider using Dynamic Router [1].
[1] http://camel.apache.org/dynamic-router.html
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Am 25.06.12 12:16 schrieb "Claus Ibsen" unter :
>On Mon, Jun 25, 2012 at 12:09 PM, Babak Vahdat
> wrote:
>> Hi
>>
>> Yes of course, will do so tonight.
>>
>
>Hadrian if you are able to cut the RC sooner than after Babak have fixed
>this,
>then we may want to work on this right now, so the trunk
> I am not sure if we can keep up with all the patch releases, as
> camel-extra ought to be compatible.
I think we should. It should be transparent for user (as transparent
as possible at least) whether she's using camel or camel-extra. This
is licensing stuff, users usually do not care if they in
Hi
Another way that some people do is to build routes using XML and load them.
There is a short example here
http://camel.apache.org/loading-routes-from-xml-files.html
On Mon, Jun 25, 2012 at 2:20 PM, Murari Raghavan
wrote:
> Thanks Claus.
>
> --
> View this message in context:
> http://came
Thanks Claus.
--
View this message in context:
http://camel.465427.n5.nabble.com/Is-it-possible-to-dynamically-build-routes-tp5714971p5715043.html
Sent from the Camel Development mailing list archive at Nabble.com.
Hi
Its better to ask on the @user mailing list about how to do X with Camel.
And yes its possible. The RouteBuilder is just java code, so whatever
you can do in java you can do there.
You can have if .. else .. for loops .. and whatnot.
What people often do in these cases is to build a base clas
Hi
Yeah it would be nice to get camel-extra released as a follow up to
any of the Camel minor releases, eg 2.9.0 2.10.0, 2.11.0.
I am not sure if we can keep up with all the patch releases, as
camel-extra ought to be compatible.
On Mon, Jun 25, 2012 at 12:42 PM, Henryk Konsek wrote:
>> I'm alr
> I'm already delayed with camel-extra 2.9.0 :-( See [1]
> I already tagged a release but didn't uploaded the artifacts and signatures
> until now. I plan to upload it to [2] where the 2.8.0 artifacts already are.
I want to contribute new component to Camel Extra (JGroups [1], which is LGPL).
If
On Mon, Jun 25, 2012 at 12:09 PM, Babak Vahdat
wrote:
> Hi
>
> Yes of course, will do so tonight.
>
Hadrian if you are able to cut the RC sooner than after Babak have fixed this,
then we may want to work on this right now, so the trunk code is ready
for the RC.
> Babak
>
> --
> View this messa
Hi
Yes of course, will do so tonight.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-10-0-tp5714768p5715032.html
Sent from the Camel Development mailing list archive at Nabble.com.
Hi
Yeah can you skip those tests on Java7, and add a TODO etc.
Then when we upgrade to Spring WS 2.1.x (when Spring 3.1 is out out of
the box Spring version) then we can enable them again.
On Mon, Jun 25, 2012 at 11:30 AM, Babak Vahdat
wrote:
>
>
> Am 25.06.12 09:55 schrieb "Claus Ibsen" unter
Am 25.06.12 09:55 schrieb "Claus Ibsen" unter :
>Hi
>
>I have fixed #4 by downgrading to Spring WS 2.0.3 which is the last
>release that supports Spring 3.0.x out of the box.
>https://issues.apache.org/jira/browse/CAMEL-5393
Hi
The only minor side effect of this downgrade is that building on C
+1
Sent from a mobile device
Am 25.06.2012 09:49 schrieb :
> Author: davsclaus
> Date: Mon Jun 25 07:49:12 2012
> New Revision: 1353413
>
> URL: http://svn.apache.org/viewvc?rev=1353413&view=rev
> Log:
> CAMEL-5393: Downgraded to spring ws 2.0.3 to support spring 3.0 out of the
> box.
>
> Modifie
Hi
I have fixed #4 by downgrading to Spring WS 2.0.3 which is the last
release that supports Spring 3.0.x out of the box.
https://issues.apache.org/jira/browse/CAMEL-5393
And there is in fact a new Spring WS 2.1.0 release, which we can
upgrade to when we change use Spring 3.1.x as the default Spr
22 matches
Mail list logo
