I just used the CHECKSTYLE:OFF / CHECKSTYLE:ON to disable the complain and
commit the fix the Apache Camel git repository.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.co
The Apache Jenkins build system has built Camel.2.12.x.notest (build #3)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.12.x.notest/3/ to
view the results.
Pull request https://github.com/apache/camel/pull/42 submitted to fix
salesforce component regression.
Checkstyle might still complain, I do not know how to make it ignore the dto
directory for that.
--
View this message in context:
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-
GitHub user dhirajsb opened a pull request:
https://github.com/apache/camel/pull/42
CAMEL-6428, fixed camel-salesforce regressions
Fixed case sensitive field names in DTOs, rst processors to not throw an
exception for default operation name, test sObjectClass names
You can merge th
Hi,
Yes, I had submitted a pull request https://github.com/apache/camel/pull/41
for a new Facebook component two days ago.
Thanks,
Dhiraj.
--
View this message in context:
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-0-tp5738140p5738339.html
Sent from the Camel Developme
I am working on a fairly simple patch to fix integration test regressions
introduced in the camel-salesforce component due to the checkstyle fixes I
mentioned in CAMEL-6428.
I will submit a pull request on github soon.
Regards,
Dhiraj.
--
View this message in context:
http://camel.465427.n
Adding back in lines 356 & 357 seems to get back to 2.11.1 behavior
https://github.com/apache/camel/blob/camel-2.11.x/components/camel-core-xml/src/main/java/org/apache/camel/core/xml/AbstractCamelContextFactoryBean.java#L357
Camel-6576 seems to have subtlety changed the behavior from 2.11. Not c
Digging into this, it may be a side effect of CAMEL-6576.
DefaultManagementLifecycleStrategy.onContextStart sets the CamelContext
ManagementName
In 2.11.1, the first time I see any lifecycleStrategies is for my unit test
- context name = camel-25 - and it sets the managementName correctly
In 2.1
I logged a ticket about adding a new option to shutdown strategy to
configure it to suppress logging after context is shutdown.
https://issues.apache.org/jira/browse/CAMEL-6688
On Fri, Aug 30, 2013 at 2:16 PM, Claus Ibsen wrote:
> If you do not want the RejectedExcutionException to be logged in
Hi
Ah you are doing it a bit wrong in your createCamelContext.
As you call super.createContext which then creates the Camel and
enlist it in JMX and whatnot. Then after the super you change the JMX
stuff.
What you should do is like we do in
org.apache.camel.management.ManagementTestSupport
from
Claus,
It could be left over state, but the odd bit is everything works fine with
2.11.1... that one test fails when I tried against 2.12.0.
That unit test is then followed by other JMX unit tests that work, so
somehow the Platform mbean server is started for later tests; perhaps a
timing issue..
If you do not want the RejectedExcutionException to be logged in the
logs after the camelcontext has been attempted to shutdown.
Then we could consider adding a new option to shutdown strategy to
allow end users to configure that Camel should suppress logging after
camel context has been attempted
Maybe there is some leftover state from previous test. I assume you do
not for per test, but run all the tests in the same JVM. Otherwise you
can try setting surefire plugin to fork per test. Then the test ought
to pass. if so then its likely some leftover state from previous test
or something that
Hi
As said on the ticket its working as designed. When you shutdown
aggressive (eg set timeout to 1 sec) then there may be messages in
Camel that are not finished.
And if anyhow they are attempted to be continued the routing engine
throws the RejectedExecutionException. So that is why you may see
Hi everyone,
Earlier today I created a new jira issue [1] on something that I consider
is a bug. It was triaged and marked as "Not a problem". I don't agree with
this so I'm starting this discussion either to better understand why it's
not a bug or to reopen it. I thought this mailing list was a b
I should have been clearer that it fails at line 67 of that unit test
against the 2.12.0 release candidate only when you run the full build or
when you build the camel-cookbook-monitoring module.
https://github.com/CamelCookbook/camel-cookbook-examples/blob/master/camel-cookbook-monitoring/src/tes
I have one JMX unit test that runs in 2.11.1, but now fails in 2.12.0. The
CamelContext.getManagementName is returning null, but only when the unit
test is run as part of the larger build -- it works fine standalone.
https://github.com/CamelCookbook/camel-cookbook-examples/blob/master/camel-cookbo
Most tests are covered by the unit tests which can be ran by Jenkins.
Now we need to run some manual test on the release candidate kit.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://
Hi
FYI, I just deployed the camel osgi related examples within Apache Karaf 2.3.2.
Everything looks good.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.
The camel-core-test jar is introduced by camel-disruptor, I will commit a fix
for it shortly.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/)
Couldnt these tests not be automated using Jenkins or Gump?
Jan
> -Ursprüngliche Nachricht-
> Von: Claus Ibsen [mailto:claus.ib...@gmail.com]
> Gesendet: Freitag, 30. August 2013 09:26
> An: dev
> Betreff: Re: [VOTE] Release Apache Camel 2.12.0
>
> Hi
>
> I tested this release with the
Hi
I tested this release with the camel-extra source code and that worked fine.
I also tried some of the examples from the Camel 2.12 distribution.
Though have not (yet) tried any of the OSGi examples in Apache Karaf 2.3.2.
Also noticed that the doc folder holds the html of the manual. The pdf
i
22 matches
Mail list logo
