You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Pontus Ullgren <ul...@gmail.com> on 2016/10/23 19:35:32 UTC
IDE for newer Camel versions using Camel Spring Boot
Hi,
I know about JBoss Tools Camel Tooling and been using it. It works great as
long as we stayed with the RedHat supported versions of Camel and JBoss
Fuse. But lately we have moved away from this and going with Camel Spring
Boot and more up to date versions of Camel.
The main reason for this is to get new features faster.
The problem now is that JBoss Tools does not handle this combination well.
But that is a JBoss specific issue so that is not what I want to discuss
here. There is other forums for this.
Instead my question: What do you use for developing your Camel based
applications ?
I quickly tested Spring Tool Suite which kind of give us most of what we
look for including good support for gradle. But hope to get some more
suggestions.
We mostly use the Spring XML DSL to define the routes but also some Java
DSL.
Code completion and some tooltips in XML editing mode is a requirement.
Graphical visualisation and editing of the routes is a bonus but I assume
that JBoss Tools is the only one that supports this.
Thanks for any insight you can share
Pontus
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by Mark Nuttall <mk...@gmail.com>.
Fyi STS has property autocompletion with docs :).
I recommend Claus's video. I was going to mention it but figured he would.
On Oct 24, 2016 3:18 AM, "Claus Ibsen" <cl...@gmail.com> wrote:
> Hi
>
> There is also the fabric8 Camel forge tooling for Apache Camel
> http://fabric8.io/guide/forge.html
>
> As well the maven plugin to validate your Camel endpoints/expressions
> http://fabric8.io/guide/camelMavenPlugin.html
>
> The forge tooling works in any IDE such as Eclipse, IDEA or NetBeans.
> I recorded a video in the start of the year
> http://www.davsclaus.com/2015/12/video-of-apache-camel-
> tooling-to-edit.html
>
> For graphical drag and drop then there is as you say JBoss Eclipse
> tooling for Camel where a new version was recently released that
> support Camel 2.17.x
> http://lhein.blogspot.se/2016/10/jboss-fuse-tooling-80-for-
> eclipse-mars.html
>
> The real power of Camel is that you do NOT need any tooling, its just
> java, scala, groovy or xml code. The more skilled (Camel) developers I
> hear just uses their IDE of choice/
>
> Though for Spring Boot users I do like the auto completion tooling
> that IDEA has when editing application.properties where you can get
> code assistance to see all the options you can configure, and with
> documentation.
>
>
>
> On Sun, Oct 23, 2016 at 9:35 PM, Pontus Ullgren <ul...@gmail.com> wrote:
> > Hi,
> >
> > I know about JBoss Tools Camel Tooling and been using it. It works great
> as
> > long as we stayed with the RedHat supported versions of Camel and JBoss
> > Fuse. But lately we have moved away from this and going with Camel Spring
> > Boot and more up to date versions of Camel.
> >
> > The main reason for this is to get new features faster.
> >
> > The problem now is that JBoss Tools does not handle this combination
> well.
> > But that is a JBoss specific issue so that is not what I want to discuss
> > here. There is other forums for this.
> >
> > Instead my question: What do you use for developing your Camel based
> > applications ?
> > I quickly tested Spring Tool Suite which kind of give us most of what we
> > look for including good support for gradle. But hope to get some more
> > suggestions.
> >
> > We mostly use the Spring XML DSL to define the routes but also some Java
> > DSL.
> > Code completion and some tooltips in XML editing mode is a requirement.
> > Graphical visualisation and editing of the routes is a bonus but I assume
> > that JBoss Tools is the only one that supports this.
> >
> > Thanks for any insight you can share
> > Pontus
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Oct 26, 2016 at 12:03 PM, James Green <ja...@gmail.com> wrote:
> Just installed the update but ctrl+alt+4 would not show any Camel items
> until I put the cursor between inside a from()...to() route. Putting the
> cursor inside a RouteBuilder was not sufficient, maybe an area for
> improvement...
>
Ah thanks. Yeah the code checks the cursor position and see if there
is any existing endpoint / eip and then uses that. If there is not
then it ought to show a list of all endpoints from the current file.
And if no file then fallback for the entire project.
Apparently there is still a bug somewhere. You are welcome to log a ticket at:
https://github.com/fabric8io/fabric8-forge
>
> On 26 October 2016 at 08:52, Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi
>>
>> Yeah it was a bug in the tooling. Its because you dont have a
>> src/main/webapp folder.
>>
>> Are you using latest release of the camel addon?
>> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22io.
>> fabric8.forge%22%20AND%20a%3A%22camel%22
>>
>> The latest today is 2.3.60
>>
>>
>>
>> On Tue, Oct 25, 2016 at 3:29 PM, James Green <ja...@gmail.com>
>> wrote:
>> > Nice video indeed, however on asking to edit an endpoint in IDEA
>> 2016.2.5 I
>> > get "No Facet of type [interface
>> > org.jboss.forge.addon.projects.facets.WebResourcesFacet] is installed."
>> >
>> > Not sure I know where this needs to be reported as a bug - is it a JBoss
>> > thing, a fabic8 thing, or a Camel thing?
>> >
>> > On 24 October 2016 at 08:17, Claus Ibsen <cl...@gmail.com> wrote:
>> >
>> >> Hi
>> >>
>> >> There is also the fabric8 Camel forge tooling for Apache Camel
>> >> http://fabric8.io/guide/forge.html
>> >>
>> >> As well the maven plugin to validate your Camel endpoints/expressions
>> >> http://fabric8.io/guide/camelMavenPlugin.html
>> >>
>> >> The forge tooling works in any IDE such as Eclipse, IDEA or NetBeans.
>> >> I recorded a video in the start of the year
>> >> http://www.davsclaus.com/2015/12/video-of-apache-camel-
>> >> tooling-to-edit.html
>> >>
>> >> For graphical drag and drop then there is as you say JBoss Eclipse
>> >> tooling for Camel where a new version was recently released that
>> >> support Camel 2.17.x
>> >> http://lhein.blogspot.se/2016/10/jboss-fuse-tooling-80-for-
>> >> eclipse-mars.html
>> >>
>> >> The real power of Camel is that you do NOT need any tooling, its just
>> >> java, scala, groovy or xml code. The more skilled (Camel) developers I
>> >> hear just uses their IDE of choice/
>> >>
>> >> Though for Spring Boot users I do like the auto completion tooling
>> >> that IDEA has when editing application.properties where you can get
>> >> code assistance to see all the options you can configure, and with
>> >> documentation.
>> >>
>> >>
>> >>
>> >> On Sun, Oct 23, 2016 at 9:35 PM, Pontus Ullgren <ul...@gmail.com>
>> wrote:
>> >> > Hi,
>> >> >
>> >> > I know about JBoss Tools Camel Tooling and been using it. It works
>> great
>> >> as
>> >> > long as we stayed with the RedHat supported versions of Camel and
>> JBoss
>> >> > Fuse. But lately we have moved away from this and going with Camel
>> Spring
>> >> > Boot and more up to date versions of Camel.
>> >> >
>> >> > The main reason for this is to get new features faster.
>> >> >
>> >> > The problem now is that JBoss Tools does not handle this combination
>> >> well.
>> >> > But that is a JBoss specific issue so that is not what I want to
>> discuss
>> >> > here. There is other forums for this.
>> >> >
>> >> > Instead my question: What do you use for developing your Camel based
>> >> > applications ?
>> >> > I quickly tested Spring Tool Suite which kind of give us most of what
>> we
>> >> > look for including good support for gradle. But hope to get some more
>> >> > suggestions.
>> >> >
>> >> > We mostly use the Spring XML DSL to define the routes but also some
>> Java
>> >> > DSL.
>> >> > Code completion and some tooltips in XML editing mode is a
>> requirement.
>> >> > Graphical visualisation and editing of the routes is a bonus but I
>> assume
>> >> > that JBoss Tools is the only one that supports this.
>> >> >
>> >> > Thanks for any insight you can share
>> >> > Pontus
>> >>
>> >>
>> >>
>> >> --
>> >> 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
>>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by James Green <ja...@gmail.com>.
Just installed the update but ctrl+alt+4 would not show any Camel items
until I put the cursor between inside a from()...to() route. Putting the
cursor inside a RouteBuilder was not sufficient, maybe an area for
improvement...
On 26 October 2016 at 08:52, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Yeah it was a bug in the tooling. Its because you dont have a
> src/main/webapp folder.
>
> Are you using latest release of the camel addon?
> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22io.
> fabric8.forge%22%20AND%20a%3A%22camel%22
>
> The latest today is 2.3.60
>
>
>
> On Tue, Oct 25, 2016 at 3:29 PM, James Green <ja...@gmail.com>
> wrote:
> > Nice video indeed, however on asking to edit an endpoint in IDEA
> 2016.2.5 I
> > get "No Facet of type [interface
> > org.jboss.forge.addon.projects.facets.WebResourcesFacet] is installed."
> >
> > Not sure I know where this needs to be reported as a bug - is it a JBoss
> > thing, a fabic8 thing, or a Camel thing?
> >
> > On 24 October 2016 at 08:17, Claus Ibsen <cl...@gmail.com> wrote:
> >
> >> Hi
> >>
> >> There is also the fabric8 Camel forge tooling for Apache Camel
> >> http://fabric8.io/guide/forge.html
> >>
> >> As well the maven plugin to validate your Camel endpoints/expressions
> >> http://fabric8.io/guide/camelMavenPlugin.html
> >>
> >> The forge tooling works in any IDE such as Eclipse, IDEA or NetBeans.
> >> I recorded a video in the start of the year
> >> http://www.davsclaus.com/2015/12/video-of-apache-camel-
> >> tooling-to-edit.html
> >>
> >> For graphical drag and drop then there is as you say JBoss Eclipse
> >> tooling for Camel where a new version was recently released that
> >> support Camel 2.17.x
> >> http://lhein.blogspot.se/2016/10/jboss-fuse-tooling-80-for-
> >> eclipse-mars.html
> >>
> >> The real power of Camel is that you do NOT need any tooling, its just
> >> java, scala, groovy or xml code. The more skilled (Camel) developers I
> >> hear just uses their IDE of choice/
> >>
> >> Though for Spring Boot users I do like the auto completion tooling
> >> that IDEA has when editing application.properties where you can get
> >> code assistance to see all the options you can configure, and with
> >> documentation.
> >>
> >>
> >>
> >> On Sun, Oct 23, 2016 at 9:35 PM, Pontus Ullgren <ul...@gmail.com>
> wrote:
> >> > Hi,
> >> >
> >> > I know about JBoss Tools Camel Tooling and been using it. It works
> great
> >> as
> >> > long as we stayed with the RedHat supported versions of Camel and
> JBoss
> >> > Fuse. But lately we have moved away from this and going with Camel
> Spring
> >> > Boot and more up to date versions of Camel.
> >> >
> >> > The main reason for this is to get new features faster.
> >> >
> >> > The problem now is that JBoss Tools does not handle this combination
> >> well.
> >> > But that is a JBoss specific issue so that is not what I want to
> discuss
> >> > here. There is other forums for this.
> >> >
> >> > Instead my question: What do you use for developing your Camel based
> >> > applications ?
> >> > I quickly tested Spring Tool Suite which kind of give us most of what
> we
> >> > look for including good support for gradle. But hope to get some more
> >> > suggestions.
> >> >
> >> > We mostly use the Spring XML DSL to define the routes but also some
> Java
> >> > DSL.
> >> > Code completion and some tooltips in XML editing mode is a
> requirement.
> >> > Graphical visualisation and editing of the routes is a bonus but I
> assume
> >> > that JBoss Tools is the only one that supports this.
> >> >
> >> > Thanks for any insight you can share
> >> > Pontus
> >>
> >>
> >>
> >> --
> >> 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
>
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Yeah it was a bug in the tooling. Its because you dont have a
src/main/webapp folder.
Are you using latest release of the camel addon?
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22io.fabric8.forge%22%20AND%20a%3A%22camel%22
The latest today is 2.3.60
On Tue, Oct 25, 2016 at 3:29 PM, James Green <ja...@gmail.com> wrote:
> Nice video indeed, however on asking to edit an endpoint in IDEA 2016.2.5 I
> get "No Facet of type [interface
> org.jboss.forge.addon.projects.facets.WebResourcesFacet] is installed."
>
> Not sure I know where this needs to be reported as a bug - is it a JBoss
> thing, a fabic8 thing, or a Camel thing?
>
> On 24 October 2016 at 08:17, Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi
>>
>> There is also the fabric8 Camel forge tooling for Apache Camel
>> http://fabric8.io/guide/forge.html
>>
>> As well the maven plugin to validate your Camel endpoints/expressions
>> http://fabric8.io/guide/camelMavenPlugin.html
>>
>> The forge tooling works in any IDE such as Eclipse, IDEA or NetBeans.
>> I recorded a video in the start of the year
>> http://www.davsclaus.com/2015/12/video-of-apache-camel-
>> tooling-to-edit.html
>>
>> For graphical drag and drop then there is as you say JBoss Eclipse
>> tooling for Camel where a new version was recently released that
>> support Camel 2.17.x
>> http://lhein.blogspot.se/2016/10/jboss-fuse-tooling-80-for-
>> eclipse-mars.html
>>
>> The real power of Camel is that you do NOT need any tooling, its just
>> java, scala, groovy or xml code. The more skilled (Camel) developers I
>> hear just uses their IDE of choice/
>>
>> Though for Spring Boot users I do like the auto completion tooling
>> that IDEA has when editing application.properties where you can get
>> code assistance to see all the options you can configure, and with
>> documentation.
>>
>>
>>
>> On Sun, Oct 23, 2016 at 9:35 PM, Pontus Ullgren <ul...@gmail.com> wrote:
>> > Hi,
>> >
>> > I know about JBoss Tools Camel Tooling and been using it. It works great
>> as
>> > long as we stayed with the RedHat supported versions of Camel and JBoss
>> > Fuse. But lately we have moved away from this and going with Camel Spring
>> > Boot and more up to date versions of Camel.
>> >
>> > The main reason for this is to get new features faster.
>> >
>> > The problem now is that JBoss Tools does not handle this combination
>> well.
>> > But that is a JBoss specific issue so that is not what I want to discuss
>> > here. There is other forums for this.
>> >
>> > Instead my question: What do you use for developing your Camel based
>> > applications ?
>> > I quickly tested Spring Tool Suite which kind of give us most of what we
>> > look for including good support for gradle. But hope to get some more
>> > suggestions.
>> >
>> > We mostly use the Spring XML DSL to define the routes but also some Java
>> > DSL.
>> > Code completion and some tooltips in XML editing mode is a requirement.
>> > Graphical visualisation and editing of the routes is a bonus but I assume
>> > that JBoss Tools is the only one that supports this.
>> >
>> > Thanks for any insight you can share
>> > Pontus
>>
>>
>>
>> --
>> 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
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by James Green <ja...@gmail.com>.
Nice video indeed, however on asking to edit an endpoint in IDEA 2016.2.5 I
get "No Facet of type [interface
org.jboss.forge.addon.projects.facets.WebResourcesFacet] is installed."
Not sure I know where this needs to be reported as a bug - is it a JBoss
thing, a fabic8 thing, or a Camel thing?
On 24 October 2016 at 08:17, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> There is also the fabric8 Camel forge tooling for Apache Camel
> http://fabric8.io/guide/forge.html
>
> As well the maven plugin to validate your Camel endpoints/expressions
> http://fabric8.io/guide/camelMavenPlugin.html
>
> The forge tooling works in any IDE such as Eclipse, IDEA or NetBeans.
> I recorded a video in the start of the year
> http://www.davsclaus.com/2015/12/video-of-apache-camel-
> tooling-to-edit.html
>
> For graphical drag and drop then there is as you say JBoss Eclipse
> tooling for Camel where a new version was recently released that
> support Camel 2.17.x
> http://lhein.blogspot.se/2016/10/jboss-fuse-tooling-80-for-
> eclipse-mars.html
>
> The real power of Camel is that you do NOT need any tooling, its just
> java, scala, groovy or xml code. The more skilled (Camel) developers I
> hear just uses their IDE of choice/
>
> Though for Spring Boot users I do like the auto completion tooling
> that IDEA has when editing application.properties where you can get
> code assistance to see all the options you can configure, and with
> documentation.
>
>
>
> On Sun, Oct 23, 2016 at 9:35 PM, Pontus Ullgren <ul...@gmail.com> wrote:
> > Hi,
> >
> > I know about JBoss Tools Camel Tooling and been using it. It works great
> as
> > long as we stayed with the RedHat supported versions of Camel and JBoss
> > Fuse. But lately we have moved away from this and going with Camel Spring
> > Boot and more up to date versions of Camel.
> >
> > The main reason for this is to get new features faster.
> >
> > The problem now is that JBoss Tools does not handle this combination
> well.
> > But that is a JBoss specific issue so that is not what I want to discuss
> > here. There is other forums for this.
> >
> > Instead my question: What do you use for developing your Camel based
> > applications ?
> > I quickly tested Spring Tool Suite which kind of give us most of what we
> > look for including good support for gradle. But hope to get some more
> > suggestions.
> >
> > We mostly use the Spring XML DSL to define the routes but also some Java
> > DSL.
> > Code completion and some tooltips in XML editing mode is a requirement.
> > Graphical visualisation and editing of the routes is a bonus but I assume
> > that JBoss Tools is the only one that supports this.
> >
> > Thanks for any insight you can share
> > Pontus
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
There is also the fabric8 Camel forge tooling for Apache Camel
http://fabric8.io/guide/forge.html
As well the maven plugin to validate your Camel endpoints/expressions
http://fabric8.io/guide/camelMavenPlugin.html
The forge tooling works in any IDE such as Eclipse, IDEA or NetBeans.
I recorded a video in the start of the year
http://www.davsclaus.com/2015/12/video-of-apache-camel-tooling-to-edit.html
For graphical drag and drop then there is as you say JBoss Eclipse
tooling for Camel where a new version was recently released that
support Camel 2.17.x
http://lhein.blogspot.se/2016/10/jboss-fuse-tooling-80-for-eclipse-mars.html
The real power of Camel is that you do NOT need any tooling, its just
java, scala, groovy or xml code. The more skilled (Camel) developers I
hear just uses their IDE of choice/
Though for Spring Boot users I do like the auto completion tooling
that IDEA has when editing application.properties where you can get
code assistance to see all the options you can configure, and with
documentation.
On Sun, Oct 23, 2016 at 9:35 PM, Pontus Ullgren <ul...@gmail.com> wrote:
> Hi,
>
> I know about JBoss Tools Camel Tooling and been using it. It works great as
> long as we stayed with the RedHat supported versions of Camel and JBoss
> Fuse. But lately we have moved away from this and going with Camel Spring
> Boot and more up to date versions of Camel.
>
> The main reason for this is to get new features faster.
>
> The problem now is that JBoss Tools does not handle this combination well.
> But that is a JBoss specific issue so that is not what I want to discuss
> here. There is other forums for this.
>
> Instead my question: What do you use for developing your Camel based
> applications ?
> I quickly tested Spring Tool Suite which kind of give us most of what we
> look for including good support for gradle. But hope to get some more
> suggestions.
>
> We mostly use the Spring XML DSL to define the routes but also some Java
> DSL.
> Code completion and some tooltips in XML editing mode is a requirement.
> Graphical visualisation and editing of the routes is a bonus but I assume
> that JBoss Tools is the only one that supports this.
>
> Thanks for any insight you can share
> Pontus
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by jclarysse <jc...@talend.com>.
Pontus, JBoss Tools is not the only product to support grafical visualisation
of Camel routes. You may take a look at Talend ESB, which also sticks to a
given supported version (Camel 2.16 in Talend 6.2) but allows exports as
Spring Boot Microservices:
https://www.talend.com/download/talend-open-studio#t3
--
View this message in context: http://camel.465427.n5.nabble.com/IDE-for-newer-Camel-versions-using-Camel-Spring-Boot-tp5789147p5789151.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by Mark Nuttall <mk...@gmail.com>.
Pontus, I only do Java DSL with Spring Boot, so I use STS (I could use
Intellij too if I had a license for it). It works very well for me (and my
use cases). The guy i use to work with started with XML but it was painful
because - XML. He has moved exclusively to Groovy. I am not sure what your
use case for XML is, but Groovy might solve it (since it can be run as a
program or as a script)
Mark
On Sun, Oct 23, 2016 at 4:45 PM, souciance <souciance.eqdam.rashti@gmail.com
> wrote:
> Hi Pontus
>
> I use Intellij for the actual coding and I find that Intellj works faster
> and cleaner than Eclipse which I used before. The maven integration is also
> good and the git integration is really nice. I work mainly with the java
> dsl and use blueprint for route configuration and deployment to Karaf as
> the runtime model, with everything running in docker. I did try JBoss Tools
> and the graphical visualisation but I think the release needs a few more
> updates to become more stable. I run into some errors and it was quit slow
> to work with.
>
> Best
> Souciance
>
>
>
> On Sun, Oct 23, 2016 at 9:36 PM, pontus.ullgren [via Camel] <
> ml-node+s465427n5789147h20@n5.nabble.com> wrote:
>
> > Hi,
> >
> > I know about JBoss Tools Camel Tooling and been using it. It works great
> > as
> > long as we stayed with the RedHat supported versions of Camel and JBoss
> > Fuse. But lately we have moved away from this and going with Camel Spring
> > Boot and more up to date versions of Camel.
> >
> > The main reason for this is to get new features faster.
> >
> > The problem now is that JBoss Tools does not handle this combination
> well.
> > But that is a JBoss specific issue so that is not what I want to discuss
> > here. There is other forums for this.
> >
> > Instead my question: What do you use for developing your Camel based
> > applications ?
> > I quickly tested Spring Tool Suite which kind of give us most of what we
> > look for including good support for gradle. But hope to get some more
> > suggestions.
> >
> > We mostly use the Spring XML DSL to define the routes but also some Java
> > DSL.
> > Code completion and some tooltips in XML editing mode is a requirement.
> > Graphical visualisation and editing of the routes is a bonus but I assume
> > that JBoss Tools is the only one that supports this.
> >
> > Thanks for any insight you can share
> > Pontus
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://camel.465427.n5.nabble.com/IDE-for-newer-Camel-
> > versions-using-Camel-Spring-Boot-tp5789147.html
> > To start a new topic under Camel - Users, email
> > ml-node+s465427n465428h31@n5.nabble.com
> > To unsubscribe from Camel - Users, click here
> > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=
> unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aU
> BnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> > .
> > NAML
> > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_
> viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace&breadcrumbs=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/IDE-for-newer-Camel-versions-using-Camel-Spring-
> Boot-tp5789147p5789148.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
Re: IDE for newer Camel versions using Camel Spring Boot
Posted by souciance <so...@gmail.com>.
Hi Pontus
I use Intellij for the actual coding and I find that Intellj works faster
and cleaner than Eclipse which I used before. The maven integration is also
good and the git integration is really nice. I work mainly with the java
dsl and use blueprint for route configuration and deployment to Karaf as
the runtime model, with everything running in docker. I did try JBoss Tools
and the graphical visualisation but I think the release needs a few more
updates to become more stable. I run into some errors and it was quit slow
to work with.
Best
Souciance
On Sun, Oct 23, 2016 at 9:36 PM, pontus.ullgren [via Camel] <
ml-node+s465427n5789147h20@n5.nabble.com> wrote:
> Hi,
>
> I know about JBoss Tools Camel Tooling and been using it. It works great
> as
> long as we stayed with the RedHat supported versions of Camel and JBoss
> Fuse. But lately we have moved away from this and going with Camel Spring
> Boot and more up to date versions of Camel.
>
> The main reason for this is to get new features faster.
>
> The problem now is that JBoss Tools does not handle this combination well.
> But that is a JBoss specific issue so that is not what I want to discuss
> here. There is other forums for this.
>
> Instead my question: What do you use for developing your Camel based
> applications ?
> I quickly tested Spring Tool Suite which kind of give us most of what we
> look for including good support for gradle. But hope to get some more
> suggestions.
>
> We mostly use the Spring XML DSL to define the routes but also some Java
> DSL.
> Code completion and some tooltips in XML editing mode is a requirement.
> Graphical visualisation and editing of the routes is a bonus but I assume
> that JBoss Tools is the only one that supports this.
>
> Thanks for any insight you can share
> Pontus
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/IDE-for-newer-Camel-
> versions-using-Camel-Spring-Boot-tp5789147.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428h31@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://camel.465427.n5.nabble.com/IDE-for-newer-Camel-versions-using-Camel-Spring-Boot-tp5789147p5789148.html
Sent from the Camel - Users mailing list archive at Nabble.com.