old javadocs on website?

2016-10-22 Thread Tim Dudgeon 
This page on the website: https://camel.apache.org/javadoc.html links to 
here http://camel.apache.org/maven/current/camel-core/apidocs/index.html 
for the core javadocs.


But that page is for the 2.15.0 version, so it a bit out of date. Are 
the current versions available, and can web site be updated?


Tim

Re: Spring Boot autoconfiguration

2016-10-22 Thread Claus Ibsen 
You can configure camel.springboot.auto-startup=false which wont start
routes etc.

For Camel itself to not start totally, then that would require a new
option to be introduced into camel-spring-boot.

We love contributions so a PR and JIRA is welcome
http://camel.apache.org/contributing.html

On Sat, Oct 22, 2016 at 12:53 PM, Minh Tran  wrote:
> Hi
>
> There are times when running certain unit tests without Camel  is a good 
> thing. For example, testing POJOs. There’s no need to startup all the routes 
> as they’re not being used. Moving them into a different project isn’t very 
> practical.
>
>> On 21 Oct 2016, at 11:39 PM, Mark Nuttall  wrote:
>>
>> It might be easier and better to move that code to a different project. It
>> sounds like you have non camel specific code you want to test.
>>
>> On Oct 20, 2016 11:15 PM, "Minh Tran"  wrote:
>>
>>> Hi
>>>
>>> I’m using Camel 2.18.0 and Spring Boot. I’m trying to write a unit test
>>> that excludes any Camel from starting up.
>>>
>>> Prior to 2.18.0, I could do this by simply excluding
>>> CamelAutoConfiguration. But now in 2.18.0, it looks like a whole bunch of
>>> other AutoConfiguration for Camel has been added. So far I’ve added about
>>> 20 extra classes to exclude before I gave up. Here is what I have so far
>>>
>>> @RunWith(SpringJUnit4ClassRunner.class)
>>> @SpringBootTest
>>> public class PlainTest {
>>>
>>>@Configuration
>>>@EnableAutoConfiguration(exclude = {
>>> CamelAutoConfiguration.class, DirectComponentAutoConfiguration.class,
>>> DirectVmComponentAutoConfiguration.class,
>>>LogComponentAutoConfiguration.class,
>>> PropertiesComponentAutoConfiguration.class, RestComponentAutoConfiguration
>>> .class,
>>>SchedulerComponentAutoConfiguration.class,
>>> SedaComponentAutoConfiguration.class, StubComponentAutoConfiguration
>>> .class,
>>>ValidatorComponentAutoConfiguration.class,
>>> VmComponentAutoConfiguration.class, XsltComponentAutoConfiguration.class,
>>>GzipDataFormatAutoConfiguration.class,
>>> SerializationDataFormatAutoConfiguration.class,
>>> StringDataFormatAutoConfiguration.class,
>>>ZipDataFormatAutoConfiguration.class,
>>> BeanLanguageAutoConfiguration.class, ConstantLanguageAutoConfigurat
>>> ion.class,
>>>HeaderLanguageAutoConfiguration.class })
>>>public static class Config {
>>>
>>>}
>>>
>>>@Test
>>>public void test() {
>>>// do something
>>>}
>>> }
>>>
>>>
>>> Could someone tell me the proper way of excluding Camel in my unit tests?
>>> Thanks.
>>>
>>>
>>>
>



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Spring Boot autoconfiguration

2016-10-22 Thread Minh Tran 
Hi

There are times when running certain unit tests without Camel  is a good thing. 
For example, testing POJOs. There’s no need to startup all the routes as 
they’re not being used. Moving them into a different project isn’t very 
practical.

> On 21 Oct 2016, at 11:39 PM, Mark Nuttall  wrote:
> 
> It might be easier and better to move that code to a different project. It
> sounds like you have non camel specific code you want to test.
> 
> On Oct 20, 2016 11:15 PM, "Minh Tran"  wrote:
> 
>> Hi
>> 
>> I’m using Camel 2.18.0 and Spring Boot. I’m trying to write a unit test
>> that excludes any Camel from starting up.
>> 
>> Prior to 2.18.0, I could do this by simply excluding
>> CamelAutoConfiguration. But now in 2.18.0, it looks like a whole bunch of
>> other AutoConfiguration for Camel has been added. So far I’ve added about
>> 20 extra classes to exclude before I gave up. Here is what I have so far
>> 
>> @RunWith(SpringJUnit4ClassRunner.class)
>> @SpringBootTest
>> public class PlainTest {
>> 
>>@Configuration
>>@EnableAutoConfiguration(exclude = {
>> CamelAutoConfiguration.class, DirectComponentAutoConfiguration.class,
>> DirectVmComponentAutoConfiguration.class,
>>LogComponentAutoConfiguration.class,
>> PropertiesComponentAutoConfiguration.class, RestComponentAutoConfiguration
>> .class,
>>SchedulerComponentAutoConfiguration.class,
>> SedaComponentAutoConfiguration.class, StubComponentAutoConfiguration
>> .class,
>>ValidatorComponentAutoConfiguration.class,
>> VmComponentAutoConfiguration.class, XsltComponentAutoConfiguration.class,
>>GzipDataFormatAutoConfiguration.class,
>> SerializationDataFormatAutoConfiguration.class,
>> StringDataFormatAutoConfiguration.class,
>>ZipDataFormatAutoConfiguration.class,
>> BeanLanguageAutoConfiguration.class, ConstantLanguageAutoConfigurat
>> ion.class,
>>HeaderLanguageAutoConfiguration.class })
>>public static class Config {
>> 
>>}
>> 
>>@Test
>>public void test() {
>>// do something
>>}
>> }
>> 
>> 
>> Could someone tell me the proper way of excluding Camel in my unit tests?
>> Thanks.
>> 
>> 
>>

Re: 2.18.0 SimpleLanguage

2016-10-22 Thread souciance 
But it seems you only got that exception when running in Karaf with an
older Camel. So best thing is to test in a clean Karaf then.

On Sat, Oct 22, 2016 at 2:25 AM, Allan C. [via Camel] <
ml-node+s465427n5789112...@n5.nabble.com> wrote:

> I think what I suspected caused the Exception thrown. It is running as
> usual after I stopped the 2.16.3 bundles, I didn't remove/uninstall them.
>
> The more intriguing thing is that I then uninstalled the 2.16.3
> components,
> and reinstalled them. Now it is a different expected exception. The
> original exception related to SimpleLanguage is not thrown anymore. And I
> also did restart Karaf once. But I think the 2.18.0 SimpleLanguage is not
> an issue - I can't reproduce the exception anymore.
>
> Regards,
> Allan C.
>
> On Fri, Oct 21, 2016 at 9:05 PM, Allan C. <[hidden email]
> > wrote:
>
> > This is the route related to the exception thrown:
> >
> > 
> > XMPP entry point
> > 
> > />
> >
> > 
> > 
> > 
> > ${exchangeProperty.operation} == "ack"
> > 
> > 
> > 
> > ${exchangeProperty.operation} == "nack"
> > 
> > 
> > 
> > ${exchangeProperty.operation} == "control"
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > For what it's worth, the container has both 2.18.0 and 2.16.3 installed.
> > Not sure if this is cause for the conflict. I'll uninstall the 2.16.3
> > components and try again maybe tomorrow.
> >
> > Regards,
> > Allan C.
> >
> > On Fri, Oct 21, 2016 at 6:51 PM, souciance  > com> wrote:
> >
> >> Sorry, but can you post the route as well?
> >>
> >> On Fri, Oct 21, 2016 at 12:07 PM, Allan C. [via Camel] <
> >> [hidden email] >
> wrote:
> >>
> >> > This is my pom.
> >> >
> >> > 
> >> > http://maven.apache.org/POM/4.0.0;
> >> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> >> > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> >> > http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> >> >
> >> > 4.0.0
> >> >
> >> > com.test.server
> >> > test-server
> >> > 1.0.0
> >> > bundle
> >> > test Server
> >> > test Server
> >> >
> >> > 
> >> > 
> >> > central
> >> > Maven Repository Switchboard
> >> > default
> >> > http://repo1.maven.org/maven2
> >> > 
> >> > false
> >> > 
> >> > 
> >> > 
> >> >
> >> > 
> >> > 
> >> > central
> >> > Maven Plugin Repository
> >> > http://repo1.maven.org/maven2
> >> > default
> >> > 
> >> > false
> >> > 
> >> > 
> >> > never
> >> > 
> >> > 
> >> > 
> >> >
> >> > 
> >> > UTF-8
> >> > 1.8
> >> > 1.8
> >> > 2.15
> >> > 2.3.7
> >> > true
> >> >
> >> > 2.18.0
> >> > 4.0.7
> >> > 3.2.2
> >> > 4.4.1
> >> > 1.1.4c
> >> > 1.1.4c_7
> >> > 
> >> >
> >> > 
> >> > 
> >> > 
> >> >org.apache.felix
> >> >org.apache.felix.framework
> >> > ${felix.version}
> >> > 
> >> >
> >> > 
> >> >org.apache.camel
> >> >camel-core
> >> > ${camel.version}
> >> > 
> >> > 
> >> > org.apache.camel
> >> > camel-mongodb
> >> > ${camel.version}
> >> > 
> >> > 
> >> > org.apache.camel
> >> > camel-http4
> >> > ${camel.version}
> >> > 
> >> > 
> >> > org.apache.camel
> >> > camel-blueprint
> >> > ${camel.version}
> >> > 
> >> > 
> >> >org.apache.camel
> >> >camel-xmpp
> >> > ${camel.version}
> >> > 
> >> >
> >> >
> >> > org.igniterealtime.smack
> >> > smack-core
> >> > ${smack.version}
> >> > 
> >> > 
> >> > org.igniterealtime.smack
> >> > smack-tcp
> >> > ${smack.version}
> >> > 
> >> > 
> >> > org.igniterealtime.smack
> >> > smack-extensions
> >> > ${smack.version}
> >> > 
> >> > 
> >> > org.igniterealtime.smack
> >> > smack-java7
> >> > ${smack.version}
> >> > 
> >> > 
> >> >xpp3
> >> >xpp3
> >> > ${xpp3.version}
> >> > 
> >> >
> >> > org.apache.servicemix.bundles
> >> > org.apache.servicemix.bundles.xpp3
> >> > ${xpp3.servicemix.version}
> >> >
> >> >
> >> > 
> >> > org.mongodb
> >> > mongo-java-driver
> >> > ${mongodb.version}
> >> > 
>

Re: Is the PDF of the manual going to be updated?

2016-10-22 Thread Claus Ibsen 
On Fri, Oct 21, 2016 at 11:23 PM, KARR, DAVID  wrote:
>> -Original Message-
>> From: Claus Ibsen [mailto:claus.ib...@gmail.com]
>> Sent: Friday, October 21, 2016 2:09 PM
>> To: users@camel.apache.org
>> Subject: Re: Is the PDF of the manual going to be updated?
>>
>> No we dont generate pdf anymore - its to problematic and requires
>> special tooling to be installed.
>>
>> A new website and documentation is in the works, which allows us to
>> generate document in more formats.
>
> Ah.  I was considering creating some small PRs to fix some small issues with 
> the doc.  I'm guessing then that the latest released documentation has little 
> similarity to what's now on the HEAD of master?
>

If you refer to the PDF document then yeah its very old. The latest
doc you can see on the website. And the docs are now in .adoc files in
the source code which we will use to generate a new website in the
upcoming release (if all goes well).

See details on how to improve docs at
http://camel.apache.org/contributing.html


>> On Fri, Oct 21, 2016 at 10:08 PM, KARR, DAVID  wrote:
>> > I noticed that the documentation set includes a PDF of the manual up
>> to version 2.11, and after that only the HTML version is being produced.
>> Is the PDF not going to be produced anymore?
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2