Re: camel-sjms support for JMS 2 in OSGI

[yogu13]

Generated a pull request -> https://github.com/apache/camel/pull/768



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-sjms-support-for-JMS-2-in-OSGI-tp5776164p5776223.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Issue with maximumPoolSize & Netty4-http component

[Willem Jiang]

Hi Charles,

I just created a JIRA[1] for it and will back port the patch CAMEL-8031 to 
camel-netty4 shortly.

[1]https://issues.apache.org/jira/browse/CAMEL-9514 

--  
Willem Jiang


Blog: http://willemjiang.blogspot.com (English)  
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On January 14, 2016 at 3:43:27 PM, Charles Moulliard (ch0...@gmail.com) wrote:
> The workaround only work for the netty4-http but not when we use it with
> the Rest DSL
>  
> This syntax
>  
> @Override
> public void configure() throws Exception {
> // configure to use netty4-http on localhost with the given
> port
> restConfiguration()
> .component("netty4-http")
> .host("localhost").port(getPort())
> .endpointProperty("nettyHttpBinding", "#mybinding")
> .componentProperty("maximumPoolSize","2");
>  
> // use the rest DSL to define the rest services
> rest("/users/")
> .get("{id}/basic")
> .route()
> .log(">> Thread name : ${threadName}")
>  
> will continue to use 16 Threads when we send concurrently 20 messages
>  
> On Thu, Jan 14, 2016 at 8:26 AM, Charles Moulliard wrote:
>  
> > Hi Willem,
> >
> > Thx for your input. I have fixed my problem by setting the parameter on
> > the component itself
> >
> > public void configure() throws Exception {
> >
> > NettyHttpConfiguration nettyConfig = new
> > NettyHttpConfiguration();
> > nettyConfig.setMaximumPoolSize(2);
> > NettyHttpComponent nettyHttp = new NettyHttpComponent();
> > nettyHttp.setConfiguration(nettyConfig);
> >
> > getContext().addComponent("netty4-http", nettyHttp);
> > nettyHttp.start();
> >
> > // expose a echo service
> > from("netty4-http:http://localhost:{{port}}/echo";)
> > .log(">> Thread name : ${threadName}")
> >
> > .transform(body().append(body())).to("mock:result");
> > }
> >
> > Only 2 threads are created now
> >
> > Regards,
> >
> > Charles
> >
> > On Thu, Jan 14, 2016 at 2:33 AM, Willem Jiang  
> > wrote:
> >
> >> Hi Charles,
> >>
> >> You should be able to setup the maximumPoolSize on the Netty4-http
> >> component level due to CAMEL-8031[1].
> >> And the maximumPoolSize only works for consumer side.
> >>
> >> [1]https://issues.apache.org/jira/browse/CAMEL-8031
> >>
> >> --
> >> Willem Jiang
> >>
> >>
> >> Blog: http://willemjiang.blogspot.com (English)
> >> http://jnn.iteye.com (Chinese)
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >>
> >>
> >> On January 14, 2016 at 1:09:04 AM, Charles Moulliard (ch0...@gmail.com)
> >> wrote:
> >> > Hi,
> >> >
> >> > When I debug this unit test
> >> > https://gist.github.com/cmoulliard/123261f7ac2a9d5c719c, the Camel
> >> Netty4
> >> > HTTP Endpoint is well created with the param "maximumPoolSize=2"
> >> >
> >> > main TRACE [org.apache.camel.impl.DefaultComponent] - Creating endpoint
> >> > uri=[netty4-http://http://localhost:26025/echo?maximumPoolSize=2],
> >> path=[
> >> > http://localhost:26025/echo], parameters=[{maximumPoolSize=2}]
> >> >
> >> > but the number of threads reported by Netty is still bigger than 2
> >> >
> >> > Camel (camel-1) thread #4 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #4 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #3 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #3 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #2 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #2 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #1 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #1 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #0 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #0 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #4 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #4 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #3 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #3 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #4 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #4 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #0 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #0 - NettyEventExecutorGroup
> >> > Camel (camel-1) thread #2 - NettyEventExecutorGroup INFO [route1] - >>
> >> > Thread name : Camel (camel-1) thread #2 - NettyEventExecutorGroup
> >> >
> >> > Do I have to use another param to set the ThreadPool used by
> >> Netty4-http ?
> >> >
> >> >
> >> > Regards,
> >> >
> >> > --
> >> > Charles Moulliard
> >> > Apache Committer & PMC / Architect @RedHat
> >> > Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
> >> >
> >>
> >>
> >
> >
> > --
> > Charles Moulliard
> > Apache Committer & PMC / Architect @RedHat
> > Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
> >
> >
>  
>  
> --
> Charles Moulliard

Re: A silly idea?

[Henryk Konsek]

Hi Kay,

Those extra functionalities are outside the scope of the Camel. This is
usually where higher level runtime frameworks/servers like Spring Boot,
Karaf, etc. kicks in. So just choose the right runtime  for your purposes
(I personally prefer Spring Boot) and use Camel integration module
dedicated for this runtime (like camel-spring-boot).

Cheers!

czw., 14.01.2016 o 07:37 użytkownik Kay  napisał:

> Hello, I'm new to this forum, but I've used camel for a long time. ( as a
> matter of fact, I can't imagine the thing that I am able to do my java
> project without camel ). Anyway, a question teased me whenever I use Camel.
> The question was "why is there no base framework for only camel?" In the
> other word, I believe it would be better if there was a certain
> light-weighted environment supporing camel with some better functionalities
> like concurrency, extensibility, hot deploy. So, when I told my colleague
> about this idea, he replied, "Use zookeeper for failure tolerance, use OSGI
> for hot deploy, use Storm or Spark for data distribution. You don't need to
> build another similar thing for your own purpose." But I can't make certain
> with his words because I can't understand the reason why I should control
> so
> many applications for my project. I just want a light-weighted all-in-one
> package. Is building such an all-in-one package for camel a silly idea? How
> do you think about that?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/A-silly-idea-tp5776224.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
-- 
Henryk Konsek
http://about.me/hekonsek

Bundle is waiting for namespace handlers blueprint

[Bruno Jiménez]

I'm create an new simple project, just for test, with the blueprint code
founded on:
- http://camel.apache.org/using-osgi-blueprint-with-camel.html

When deploy it over a new uncompresed folder of servicemix (5.5.1) and the
log say:
INFO  | x-5.5.1/deploy | BlueprintContainerImpl   | 19 -
org.apache.aries.blueprint.core - 1.4.3 | Bundle pad-camel-cxf-stackoverflow
is waiting for namespace handlers [http://camel.apache.org/schema/blueprint]

My old projects are not working when I re-deploy it too.

Something are changing?

Thanks!




--
View this message in context: 
http://camel.465427.n5.nabble.com/Bundle-is-waiting-for-namespace-handlers-blueprint-tp5776232.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Bundle is waiting for namespace handlers blueprint

[Marco Westermann]

Hi,

can you confirm that the broker bundle stays in grace period? Then that 
is an old issue. It has something to do with the order the bundles get 
startet. And that has to do with the server performance.. I had servers 
where I faced that issue at every start. On some servers I have that 
issue sometimes at server start, and on other servers I don't have that 
issue. Anyway I could solve that issue by adding


org.apache.aries.blueprint.synchronous=true

to etc/system.properties.

regards, Marco

Am 14.01.2016 um 14:03 schrieb Bruno Jiménez:

I'm create an new simple project, just for test, with the blueprint code
founded on:
- http://camel.apache.org/using-osgi-blueprint-with-camel.html

When deploy it over a new uncompresed folder of servicemix (5.5.1) and the
log say:
INFO  | x-5.5.1/deploy | BlueprintContainerImpl   | 19 -
org.apache.aries.blueprint.core - 1.4.3 | Bundle pad-camel-cxf-stackoverflow
is waiting for namespace handlers [http://camel.apache.org/schema/blueprint]

My old projects are not working when I re-deploy it too.

Something are changing?

Thanks!




--
View this message in context: 
http://camel.465427.n5.nabble.com/Bundle-is-waiting-for-namespace-handlers-blueprint-tp5776232.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Bundle is waiting for namespace handlers blueprint

[Grzegorz Grzybek]

Hello Bruno

There's https://issues.apache.org/jira/browse/ARIES-1350 fixed in
aries.blueprint.core-1.4.4. Please use this version.

regards
Grzegorz Grzybek

2016-01-14 14:07 GMT+01:00 Marco Westermann :
> Hi,
>
> can you confirm that the broker bundle stays in grace period? Then that is
> an old issue. It has something to do with the order the bundles get startet.
> And that has to do with the server performance.. I had servers where I faced
> that issue at every start. On some servers I have that issue sometimes at
> server start, and on other servers I don't have that issue. Anyway I could
> solve that issue by adding
>
> org.apache.aries.blueprint.synchronous=true
>
> to etc/system.properties.
>
> regards, Marco
>
>
> Am 14.01.2016 um 14:03 schrieb Bruno Jiménez:
>>
>> I'm create an new simple project, just for test, with the blueprint code
>> founded on:
>> - http://camel.apache.org/using-osgi-blueprint-with-camel.html
>>
>> When deploy it over a new uncompresed folder of servicemix (5.5.1) and the
>> log say:
>> INFO  | x-5.5.1/deploy | BlueprintContainerImpl   | 19 -
>> org.apache.aries.blueprint.core - 1.4.3 | Bundle
>> pad-camel-cxf-stackoverflow
>> is waiting for namespace handlers
>> [http://camel.apache.org/schema/blueprint]
>>
>> My old projects are not working when I re-deploy it too.
>>
>> Something are changing?
>>
>> Thanks!
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Bundle-is-waiting-for-namespace-handlers-blueprint-tp5776232.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Re: camel-http-common 2.16.1 includes Servlet API 3.0

[nascha]

Aren't same versions of different camel artifacts supposed to be used
together?
Why is camel-jetty 2.16.1 using 3.1 but it's ok for camel-http4 2.16.1 to be
using 3.0? Is that not incompatible within the same versions?

If it was not the intention to move to 3.1 but stay in 3.0 for Camel 2.16,
then maybe camel-jetty should use 3.0 instead of 3.1?



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-http-common-2-16-1-includes-Servlet-API-3-0-tp5776203p5776235.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Thrown error ignored in processor

[Tingenek]

Hi,

I'm writing my first component. It's reading files and sending them to a
NoSql database.
The problem is that I can't get it to raise an error if something goes
wrong. All that happens is the processor completes and tries again after a
short delay. I tried try-catch, and I can log the error, but I can't
re-throw it either (I've tried several error types). Any ideas?

Here's my code:

@Override
public void process(Exchange exchange) throws Exception {
Message message = exchange.getIn();
String docId = message.getHeader("ml_docId", String.class);
if (docId == null) docId = message.getMessageId();

LOG.info( "Processing.. " + docId);
try {
GenericDocumentManager docMgr =
endpoint.getClient().newDocumentManager();
InputStreamHandle handle = new
InputStreamHandle(message.getBody(InputStream.class));
docMgr.write(docId,handle);
} catch (Exception e) {
LOG.error(e.getMessage());
throw new CamelRuntimeException(e.getMessage());
} 
   
}

And here's my console output:

[el-1) thread #0 - file://inbox] MLProducer INFO 
Processing.. flipper.json
[el-1) thread #0 - file://inbox] MLProducer ERROR
java.net.UnknownHostException: test: unknown error
[el-1) thread #0 - file://inbox] MLProducer INFO 
Processing.. flipper.json
[el-1) thread #0 - file://inbox] MLProducer ERROR
java.net.UnknownHostException: test

Rgds,

Mark



--
View this message in context: 
http://camel.465427.n5.nabble.com/Thrown-error-ignored-in-processor-tp5776250.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Thrown error ignored in processor

[Claus Ibsen]

Hi

This is intended. What do you want to happen when the exception is thrown?
Should the file component stop totally ? move the file somewhere else
/ or somerhing else.

You can configure much in the Camel error handler. And on the file
component to move files that fails to an error directory etc.

Error handling in Camel is a big concept and it takes a bit to grasp
and learn piece by piece what you need.

The website docs has some bits
http://camel.apache.org/error-handling-in-camel.html

Though its not as elaborate and throuugh as covered in some of the Camel books
http://camel.apache.org/books

On Thu, Jan 14, 2016 at 4:51 PM, Tingenek  wrote:
> Hi,
>
> I'm writing my first component. It's reading files and sending them to a
> NoSql database.
> The problem is that I can't get it to raise an error if something goes
> wrong. All that happens is the processor completes and tries again after a
> short delay. I tried try-catch, and I can log the error, but I can't
> re-throw it either (I've tried several error types). Any ideas?
>
> Here's my code:
>
> @Override
> public void process(Exchange exchange) throws Exception {
> Message message = exchange.getIn();
> String docId = message.getHeader("ml_docId", String.class);
> if (docId == null) docId = message.getMessageId();
>
> LOG.info( "Processing.. " + docId);
> try {
> GenericDocumentManager docMgr =
> endpoint.getClient().newDocumentManager();
> InputStreamHandle handle = new
> InputStreamHandle(message.getBody(InputStream.class));
> docMgr.write(docId,handle);
> } catch (Exception e) {
> LOG.error(e.getMessage());
> throw new CamelRuntimeException(e.getMessage());
> }
>
> }
>
> And here's my console output:
>
> [el-1) thread #0 - file://inbox] MLProducer INFO
> Processing.. flipper.json
> [el-1) thread #0 - file://inbox] MLProducer ERROR
> java.net.UnknownHostException: test: unknown error
> [el-1) thread #0 - file://inbox] MLProducer INFO
> Processing.. flipper.json
> [el-1) thread #0 - file://inbox] MLProducer ERROR
> java.net.UnknownHostException: test
>
> Rgds,
>
> Mark
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Thrown-error-ignored-in-processor-tp5776250.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



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

Re: Thrown error ignored in processor

[Tingenek]

Claus,

Thanks for the prompt reply. My test case was that my endpoint couldn't get
a connection to the server via the api so this error should be fatal (at
least to this route) since I can't process any of the files. My problem is
how do I signal this to Camel from the code in my component?

Rgds,

Mark



--
View this message in context: 
http://camel.465427.n5.nabble.com/Thrown-error-ignored-in-processor-tp5776250p5776258.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: A silly idea?

[Christian Schneider]

The problem is that people have different requirements for the runtime.
For example the hot deployment is a reason to choose OSGi but not everyone
needs that.

You should have a look at Apache Karaf. It might provide just the
environment you search for.

I got a tutorial that shows how to deploy your camel integrations to Apache
Karaf. It is quite simple and straight forward.
http://www.liquid-reality.de/display/liquid/2012/01/03/Karaf+Tutorial+Part+5+-+Running+Apache+Camel+integrations+in+OSGi

Btw. I just noticed that my tutorial covers a quite ancient version of
karaf. I will update it for the new karaf 4 command syntax.

There are also some offerings from companies that build on Apache Karaf and
provide some add on functionality like
Talend ESB or Jboss Fuse. You can do most things with just the open source
version though.

Christian

2016-01-14 7:37 GMT+01:00 Kay :

> Hello, I'm new to this forum, but I've used camel for a long time. ( as a
> matter of fact, I can't imagine the thing that I am able to do my java
> project without camel ). Anyway, a question teased me whenever I use Camel.
> The question was "why is there no base framework for only camel?" In the
> other word, I believe it would be better if there was a certain
> light-weighted environment supporing camel with some better functionalities
> like concurrency, extensibility, hot deploy. So, when I told my colleague
> about this idea, he replied, "Use zookeeper for failure tolerance, use OSGI
> for hot deploy, use Storm or Spark for data distribution. You don't need to
> build another similar thing for your own purpose." But I can't make certain
> with his words because I can't understand the reason why I should control
> so
> many applications for my project. I just want a light-weighted all-in-one
> package. Is building such an all-in-one package for camel a silly idea? How
> do you think about that?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/A-silly-idea-tp5776224.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
-- 
Christian Schneider
http://www.liquid-reality.de


Open Source Architect
http://www.talend.com

Re: A silly idea?

[Khai Nguyen]

I have been using Camel at work for sometimes and I love Camel.

Here, we think about Camel having 2 pieces: *component* (I use this term
loosely to mean non-route) which is written only in code and *route* which
could be written in any particular DSL (groovy, java, xml,...).

The component is fixed in term of deployment. The route becomes the hot
deploy unit. You can do

   1. OSGI if your route is in java DSL or any JVM language, because it is
   a jar now.
   2. A simple route deployer if your route is in XML or Groovy.
   3. ...

Our application is just a simple java application with /lib and /route
directories and a shell script to run the main method.

We wrote a maven archetype to generate our standard minimal (cuz we don't
want to ship 1GB of useless jar) camel project. Then you add more
components depend on what your application have to do. Then we ship the
application.

Camel, at core, is just a integration library allows you to send
datas/commands/requests from a endpoint to a endpoint(s).


On Thu, Jan 14, 2016 at 10:40 AM Christian Schneider <
ch...@die-schneider.net> wrote:

> The problem is that people have different requirements for the runtime.
> For example the hot deployment is a reason to choose OSGi but not everyone
> needs that.
>
> You should have a look at Apache Karaf. It might provide just the
> environment you search for.
>
> I got a tutorial that shows how to deploy your camel integrations to Apache
> Karaf. It is quite simple and straight forward.
>
> http://www.liquid-reality.de/display/liquid/2012/01/03/Karaf+Tutorial+Part+5+-+Running+Apache+Camel+integrations+in+OSGi
>
> Btw. I just noticed that my tutorial covers a quite ancient version of
> karaf. I will update it for the new karaf 4 command syntax.
>
> There are also some offerings from companies that build on Apache Karaf and
> provide some add on functionality like
> Talend ESB or Jboss Fuse. You can do most things with just the open source
> version though.
>
> Christian
>
> 2016-01-14 7:37 GMT+01:00 Kay :
>
> > Hello, I'm new to this forum, but I've used camel for a long time. ( as a
> > matter of fact, I can't imagine the thing that I am able to do my java
> > project without camel ). Anyway, a question teased me whenever I use
> Camel.
> > The question was "why is there no base framework for only camel?" In the
> > other word, I believe it would be better if there was a certain
> > light-weighted environment supporing camel with some better
> functionalities
> > like concurrency, extensibility, hot deploy. So, when I told my colleague
> > about this idea, he replied, "Use zookeeper for failure tolerance, use
> OSGI
> > for hot deploy, use Storm or Spark for data distribution. You don't need
> to
> > build another similar thing for your own purpose." But I can't make
> certain
> > with his words because I can't understand the reason why I should control
> > so
> > many applications for my project. I just want a light-weighted all-in-one
> > package. Is building such an all-in-one package for camel a silly idea?
> How
> > do you think about that?
> >
> >
> >
> > --
> > View this message in context:
> > http://camel.465427.n5.nabble.com/A-silly-idea-tp5776224.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >
>
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
> <
> https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de
> >
>
> Open Source Architect
> http://www.talend.com
> <
> https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com
> >
>

RestConfiguration with multiple ports

[dfullarton]

I know that via netty4-http I'm able to create multiple HTTP listeners on
multiple ports.

 from("netty4-http:http://localhost:8088";).to(...)
 from("netty4-http:http://localhost:8087";).to(...)

but when using rest configuration it seems I'm limited to the one listener

restConfiguration().component("netty4-http")...

Is there a way (within one context) that I can bring up multiple http
listeners and route them through to routes create by rest(PATH)?



--
View this message in context: 
http://camel.465427.n5.nabble.com/RestConfiguration-with-multiple-ports-tp5776265.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: A silly idea?

[Kay]

Thanks for all of your comments, and I've read them carefully. Yes, I agree
Karaf is an awesome framework to use hot deployment, and Spring is nice too,
and even all the things that I've written on my first thread were extra
functionalities, camel don't need to support. The first reason why I've
looked into this problem is needs to reduce risks in real project. If I use
tons of open sources for project's needs, and no matter how I've kept using
them correctly. it may cause another learn problem to unskilled
engineers(most ones whom I have to meet normally in a project), and make a
new maintenance problem too, and these problems always have led to the
result which costs much more money, and efforts as I've expected. The second
reason is the thing that I don't want to make my application becomes heavy
with many additional libs. The last reason is the thing that I want a simple
and light-weighted application architecture which satisfy general
requirements of current like failure tolerance, distributed processing, hot
deployment, and etc. I believe it'll be the most beautiful one if I can
control all of services on a simple and tiny clustered environment. In this
kind of view, I'm a little surprised with Khai's comment, your application
is very similar to what I've imagined. Is it public open source or not?
Could I see them?



--
View this message in context: 
http://camel.465427.n5.nabble.com/A-silly-idea-tp5776224p5776267.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Exchange has SOAPMessage want to Send to JMS Topic

[sanjay.gautam]

I am new to the Camel world and what I am trying to do is as follows. 

1. There is a route which is Servlet Component  which is called by external
System. 
2. MyServlet CamelComponent Reads the incoming exchange and creates the
SOAPMessage.
3. In Next Step I want to send the SOAP message to JMS Topic. 

 



  

 
   
   



   


JMS ROUTE 
At this point I Have a Exchange with SOAPMessage into it and as per the SOAP
documentation I should be able to send SOAP message via JMS , but as per
document  JMS can take only few types ?
I was expecting that CAMEL might have some internal Converter like  
MessageTransformer.SOAPMessageIntoJMSMessage(soapMessage, session);
which help in converting the message . I tried Spring Converter but it
doesnt not convert actually. 








OK


  
 

java.lang.Exception






Please suggest me any option , I can surely unmarshel and get the details
form the SOAP message but i dont want to do that as that is not our
requirement. we dont need to looking into the message 

thanks
Sanjay G 






--
View this message in context: 
http://camel.465427.n5.nabble.com/Exchange-has-SOAPMessage-want-to-Send-to-JMS-Topic-tp5776268.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Thrown error ignored in processor

[Claus Ibsen]

You can stop the route from your component, though mind stopping a
route from a route isn't super easy
http://camel.apache.org/how-can-i-stop-a-route-from-a-route.html

Or you can maybe better add a custom route policy to this route, that
detects the exception and validates whether its fatal or not. And if
so it stops the route. Then you have a generic route policy that can
do that.
http://camel.apache.org/routepolicy.html

On Thu, Jan 14, 2016 at 7:32 PM, Tingenek  wrote:
> Claus,
>
> Thanks for the prompt reply. My test case was that my endpoint couldn't get
> a connection to the server via the api so this error should be fatal (at
> least to this route) since I can't process any of the files. My problem is
> how do I signal this to Camel from the code in my component?
>
> Rgds,
>
> Mark
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Thrown-error-ignored-in-processor-tp5776250p5776258.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



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

Re: RestConfiguration with multiple ports

[Claus Ibsen]

Hi

Do you want to have different rest services for different ports? Or do
some of the rest services share the ports?

Either way its not currently baked in too well in the rest-dsl to
allow to pick which rest configuration to user per service.
The design was to keep it simple, 1 rest component for all the services.




On Fri, Jan 15, 2016 at 12:00 AM, dfullarton  wrote:
> I know that via netty4-http I'm able to create multiple HTTP listeners on
> multiple ports.
>
>  from("netty4-http:http://localhost:8088";).to(...)
>  from("netty4-http:http://localhost:8087";).to(...)
>
> but when using rest configuration it seems I'm limited to the one listener
>
> restConfiguration().component("netty4-http")...
>
> Is there a way (within one context) that I can bring up multiple http
> listeners and route them through to routes create by rest(PATH)?
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/RestConfiguration-with-multiple-ports-tp5776265.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



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