It depends on if you are on an OSGi container or not.
If you are, you could initialise your JmsComponents on a single bundle and
export them as an OSGi Service. Then import them into the route bundles
with an ID that matches the prefix you want to use for the endpoints.
If you're not on OSGi, tak
> Until this is not settled, I don't
> want to change this. MAY BE we cannot use the the official Apache JIRA to
> track issues at Apache extra...
Ok guys, probably I don't get some nuances of the Apache politics.
>From this point of view some issues (like CAMEL-5382[1]) are illegal
and should not
> Everything looks good so far. Do you considering doing a release of Camel
> extra 2.10.0? I think we are in a good shape...
Yeah, this is the next thing I want to do this week.
> I created an issue at Sonatype to get my user account enabled to publish
> artifacts. Feel free to "hijack" to ticke
Hi
Please use the @user mailing list for this kind of questions.
See the blue box on this page about that
http://camel.apache.org/mailing-lists.html
On Mon, Sep 24, 2012 at 8:49 PM, rajivbandaru wrote:
> Hi, we are dealing with this situation and any clue on this would be helpful.
> here is t
Luciano Resende wrote on Mon, Sep 24, 2012 at 14:15:13 -0700:
> On Mon, Sep 24, 2012 at 1:59 PM, Christian Müller <
> christian.muel...@gmail.com> wrote:
>
> > Thanks all for the valuable input.
> > I think there are a few points where we have slightly different
> > interpretations from what is wr
On Mon, Sep 24, 2012 at 10:12 AM, Doug Cutting wrote:
> On Sun, Sep 23, 2012 at 10:19 PM, Greg Stein wrote:
>> Apache communities do a *ton* of things. If the community is helping to
>> manage non-ASF stuff... no biggy.
>>
>> The ASF websites and releases have very clear requirements on vendor-ne
Yes Claus, it works fine when I run it as a unit test.
--
View this message in context:
http://camel.465427.n5.nabble.com/Is-camel-beanio-working-tp5719695p5719867.html
Sent from the Camel Development mailing list archive at Nabble.com.
*jar* beanio-2.0.1.jar
*config file* beanio-2.0.1.jar\org\beanio\internal\config\beanio.properties
(I think the error is while loading this config file)
*blueprint*
http://www.osgi.org/xmlns/blueprint/v1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:camel="ht
Hi,
Current we don't have the Globle Camel Context that you want.
It looks like your routes don't share the same camel context.
If you are using Spring it could be easy to let all the camel contexts share
the same jms endpoint configuration by import the resource like this
If you are using t
Hi, we are dealing with this situation and any clue on this would be helpful.
here is the problem statement:
We route several jms messages to various jms endpoints, and each endpoint
could be a different jms provider, such as tibco, weblogic, activemq etc. in
addition, we have several routes using
-1
Yes it would be nice/convenient. However, camel-extra is an external
project. AFAIK, the ASF is not providing hosting services for external
projects.
Hadrian
On 09/24/2012 05:12 PM, Henryk Konsek wrote:
+1 if we make it simple and easy for our Camel extra users to find the
Apache Camel
I suggest to open a ticket for each task which is not done yet at Google
Code.
@Henryk: Could you do this please!?
In my opinion we should release Camel extra 2.10.0 short term and postpone
the still open tasks to Camel extra 2.10.1 or 2.11.0.
Best,
Christian
On Wed, Sep 5, 2012 at 8:58 AM, Clau
Fixed:
Committing to https://svn.apache.org/repos/asf/camel/trunk ...
M
tests/camel-itest-osgi/src/test/java/org/apache/camel/itest/osgi/aws/AmazonSQSClientMock.java
Committed r1389632
Best,
Christian
On Mon, Sep 24, 2012 at 1:44 PM, Jean-Baptiste Onofré wrote:
> OK, Thanks Christian,
>
> ke
Hi Henryk!
Do you follow the other discussion [1]? Until this is not settled, I don't
want to change this. MAY BE we cannot use the the official Apache JIRA to
track issues at Apache extra...
[1]
http://camel.465427.n5.nabble.com/Re-Apache-Extras-notifications-was-Disable-GitHub-commenting-httpd-
Thanks Henryk!
I added the logging.properties file for camel-jgroups.
Everything looks good so far. Do you considering doing a release of Camel
extra 2.10.0? I think we are in a good shape...
I created an issue at Sonatype to get my user account enabled to publish
artifacts. Feel free to "hijack"
On Mon, Sep 24, 2012 at 1:59 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Thanks all for the valuable input.
> I think there are a few points where we have slightly different
> interpretations from what is written down (or not). I want to clarify this
> on the appropriate mailing l
> +1 if we make it simple and easy for our Camel extra users to find the
> Apache Camel JIRA.
Anybody else wants to express their opinion? If not, can we assume it
is a quiet consensus?
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Thanks all for the valuable input.
I think there are a few points where we have slightly different
interpretations from what is written down (or not). I want to clarify this
on the appropriate mailing list (to make sure our official Apache project
and our Apache extra project follows the guidelines
Hi,
In rev929 I've added some additional tests to Hibernate component to
make it's test coverage better.
[1] http://camel.apache.org/hibernate.html
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hey Charles!
No issues with reverting the change, but:
- the build will fail again (this was the reason of my change).
- James already did some changes.
Could you please have a look at it and change it as it's needed?
Best,
Christian
On Mon, Sep 24, 2012 at 10:30 AM, Charles Moulliard wrote:
>
On Sun, Sep 23, 2012 at 10:19 PM, Greg Stein wrote:
> Apache communities do a *ton* of things. If the community is helping to
> manage non-ASF stuff... no biggy.
>
> The ASF websites and releases have very clear requirements on vendor-neutral
> ALv2 work. If a PMC/community can clearly delineate a
OK, Thanks Christian,
keep me posted if you need any help.
Regards
JB
On 09/24/2012 01:19 PM, Christian Müller wrote:
I will fix this later today. I think I know the reason (not related to the
aws bundle).
Sent from a mobile device
Am 24.09.2012 09:49 schrieb "Jean-Baptiste Onofré" :
Yeah,
I will fix this later today. I think I know the reason (not related to the
aws bundle).
Sent from a mobile device
Am 24.09.2012 09:49 schrieb "Jean-Baptiste Onofré" :
> Yeah, it sounds like this.
>
> Regards
> JB
>
> On 09/24/2012 09:46 AM, Claus Ibsen wrote:
>
>> On Mon, Sep 24, 2012 at 9:36 AM,
Hi Christian,
We should revert the modifications as what you have done does not allow
anymore to package WAR or JAR and during the deploy phase maven download
the file even if it is created during compile phase.
Regards,
Charles
On Mon, Sep 24, 2012 at 8:11 AM, Charles Moulliard wrote:
> Hi C
Yeah, it sounds like this.
Regards
JB
On 09/24/2012 09:46 AM, Claus Ibsen wrote:
On Mon, Sep 24, 2012 at 9:36 AM, Jean-Baptiste Onofré wrote:
Hi Claus,
does it result to an update (for instance update of the ServiceMix AWS
bundle) ?
I don't know as the osgi tests dont run on CI servers as
On Mon, Sep 24, 2012 at 9:36 AM, Jean-Baptiste Onofré wrote:
> Hi Claus,
>
> does it result to an update (for instance update of the ServiceMix AWS
> bundle) ?
>
I don't know as the osgi tests dont run on CI servers as they tend to
cause problems there.
So we run them manually. And I haven't run
Hi Claus,
does it result to an update (for instance update of the ServiceMix AWS
bundle) ?
Regards
JB
On 09/24/2012 09:33 AM, Claus Ibsen wrote:
Hi
Just ran the osgi tests on trunk. The AWS related tests fails with error like:
---
27 matches
Mail list logo
