Camel CXF SOAP Service
I have configured camel cxf soap service as mentioned in below example https://github.com/apache/camel/tree/master/examples/camel-example-cxf-tomcat I have ran the application in Jetty server. I am able to consume the service using java client as per example and able to see the WSDl file in broswer. I am not able to generate the SOAPUI project using my WSDL url ( http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl) and even If I use another project and used the given soap request in SOAPUI project, I am not getting any request in server and no response in client. my Apache Camel Jar -2.14.1 CXFJar - 3.0.3 Spring Jar - 3.2.4.RELEASE Broswer URL = http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl kindly help me why SOAPUI project & request is not working Regards, Gnana -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-SOAP-Service-tp5761359.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Mail - copyTo not working and MailBoxPostProcessAction not found
Hi Claus,
thanks for the info! But it looks like the problem is somewhere else.
I tried to:
- create a class that implements
org.apache.camel.component.mail.MailBoxPostProcessAction but that interface
is not existent, so the compiler says
"org.apache.camel.component.mail.MailBoxPostProcessAction cannot be resolved
to a type";
- tried to enable the post process on an object that doesn't implement that
interface, called emailPostProcess, by adding the
postProcessAction=#emailPostProcess parameter but the compiler says:
org.apache.camel.RuntimeCamelException:
org.apache.camel.FailedToCreateRouteException: Failed to create route
test-mail: Route(test-mail)[[From[{{as-props.in-protocol}}:/... because of
Failed to resolve endpoint:
imap://mailserver?mapMailMessage=false&password={{pwd}}&postProcessAction=%23emailPostProcess&username={{usr}}
due to: Failed to resolve endpoint:
imap://mailserver?mapMailMessage=false&password={{pwd}}&postProcessAction=%23emailPostProcess&username={{usr}}
due to: There are 1 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown parameters=[{postProcessAction=#emailPostProcess}]
Is this due to the missing interface implementation on my "emailPostProcess"
class or there is something else missing somewhere?
Thank you for your help!
A.
--
View this message in context:
http://camel.465427.n5.nabble.com/Mail-copyTo-not-working-and-MailBoxPostProcessAction-not-found-tp5759776p5761363.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Custom Codec for TCP IP
I am using netty component to send message over TCP I/P to 3rd party server and also hosting TCP IP serverfor message exchange initiated from 3rd party system. Sample Inbound (REQUEST) message: 1|SMMDDN|EMPID|EMPNAME|DESIGNATION|DEPARTMENT Sample outbound (REPLY) message: 1|ACK - All messages are composed entirely of seven bit ASCII characters. - Start of the message represented by (hex 02 control character) - End of the message delimited by (hex 03 control character) - Each message should be acknowledged by ACK or NAK as shown in above reply message format. - All messages are composed entirely of seven bit ASCII characters. I am new to Camel, will appreciate if someone helps me answering my questions 1. Both MINA and NETTY componnets supports TCP IP communication, which one should be used? 2. Whether these components supports delimeter, if so how to enable it? Thanks, Rav -- View this message in context: http://camel.465427.n5.nabble.com/Custom-Codec-for-TCP-IP-tp5761366.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel CXF SOAP Service
It look like a issue of SOAPUI instead of CXF or Camel. Did you try to use different version of SOAPUI to generate the quest for the example? Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, Jan 6, 2015 at 5:24 PM, Gnana wrote: > I have configured camel cxf soap service as mentioned in below example > > https://github.com/apache/camel/tree/master/examples/camel-example-cxf-tomcat > > I have ran the application in Jetty server. > > I am able to consume the service using java client as per example and able > to see the WSDl file in broswer. > I am not able to generate the SOAPUI project using my WSDL url ( > http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl) > and even If I use another project and used the given soap request in SOAPUI > project, I am not getting any request in server and no response in client. > > my Apache Camel Jar -2.14.1 > CXFJar - 3.0.3 >Spring Jar - 3.2.4.RELEASE > > Broswer URL = > http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl > > kindly help me why SOAPUI project & request is not working > > Regards, > Gnana > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-CXF-SOAP-Service-tp5761359.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
elasticsearch component config issues
We have been using the camel-elasticsearch component in transport client configuration for some time, however we were seeing NodeClosedExceptions when the node with which it was communicating was restarted so switched to the node client to take advantage of the automatic failover. We configured the client with data=false as we didn't want it to store data and things worked quite nicely. However we also use Marvel to collect cluster stats and after a cluster restart we found that the node client in our Camel application had become the master node and no stats were being collected by Marvel on the other nodes in the cluster. When our application restarted one of the regular nodes became master and Marvel started working again. This leads me to question whether an application node client should be eligible to be a master node or not. I have also seen some plugins that only run on the master node in a cluster, and if the master node is a node client that would stop them working, wouldn't it? Perhaps this could be configurable. I'd much rather use the transport client as it feels a better fit for our application's purpose, however the lack of failover support in the component is unacceptable. I'd like to be able to specify a list of hosts for the component to use (maybe in the ActiveMQ style of failover(host1:9200,host2:9200,host3:9200)) or enable sniffing so that the transport client could discover the rest of the cluster if it can connect once. All things considered, it would be cumbersome to specify all these things in the URI on a route, and I wonder if it would be better to have a more flexible way of configuring the component in code or XML (again, like ActiveMQ :-)) Apologies if that is a bit rambling. I think Camel and elasticsearch are fantastic and have been spoiled so far with how easy it is integrating things that maybe I expect things to be too simple now! Regards, Alex. -- View this message in context: http://camel.465427.n5.nabble.com/elasticsearch-component-config-issues-tp5761369.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Mail - copyTo not working and MailBoxPostProcessAction not found
Hi
See this unit test
https://github.com/apache/camel/blob/master/components/camel-mail/src/test/java/org/apache/camel/component/mail/MailPostProcessActionTest.java
On Tue, Jan 6, 2015 at 10:40 AM, A-Light wrote:
> Hi Claus,
> thanks for the info! But it looks like the problem is somewhere else.
>
> I tried to:
> - create a class that implements
> org.apache.camel.component.mail.MailBoxPostProcessAction but that interface
> is not existent, so the compiler says
> "org.apache.camel.component.mail.MailBoxPostProcessAction cannot be resolved
> to a type";
> - tried to enable the post process on an object that doesn't implement that
> interface, called emailPostProcess, by adding the
> postProcessAction=#emailPostProcess parameter but the compiler says:
>
> org.apache.camel.RuntimeCamelException:
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> test-mail: Route(test-mail)[[From[{{as-props.in-protocol}}:/... because of
> Failed to resolve endpoint:
> imap://mailserver?mapMailMessage=false&password={{pwd}}&postProcessAction=%23emailPostProcess&username={{usr}}
> due to: Failed to resolve endpoint:
> imap://mailserver?mapMailMessage=false&password={{pwd}}&postProcessAction=%23emailPostProcess&username={{usr}}
> due to: There are 1 parameters that couldn't be set on the endpoint. Check
> the uri if the parameters are spelt correctly and that they are properties
> of the endpoint. Unknown parameters=[{postProcessAction=#emailPostProcess}]
>
> Is this due to the missing interface implementation on my "emailPostProcess"
> class or there is something else missing somewhere?
>
> Thank you for your help!
> A.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Mail-copyTo-not-working-and-MailBoxPostProcessAction-not-found-tp5759776p5761363.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: Mail - copyTo not working and MailBoxPostProcessAction not found
Hi
Ah also always check the documentation
http://camel.apache.org/mail
That options is a new option in Camel 2.15 onwards. So you cannot use
it with an older Camel release.
On Tue, Jan 6, 2015 at 2:37 PM, Claus Ibsen wrote:
> Hi
>
> See this unit test
> https://github.com/apache/camel/blob/master/components/camel-mail/src/test/java/org/apache/camel/component/mail/MailPostProcessActionTest.java
>
> On Tue, Jan 6, 2015 at 10:40 AM, A-Light wrote:
>> Hi Claus,
>> thanks for the info! But it looks like the problem is somewhere else.
>>
>> I tried to:
>> - create a class that implements
>> org.apache.camel.component.mail.MailBoxPostProcessAction but that interface
>> is not existent, so the compiler says
>> "org.apache.camel.component.mail.MailBoxPostProcessAction cannot be resolved
>> to a type";
>> - tried to enable the post process on an object that doesn't implement that
>> interface, called emailPostProcess, by adding the
>> postProcessAction=#emailPostProcess parameter but the compiler says:
>>
>> org.apache.camel.RuntimeCamelException:
>> org.apache.camel.FailedToCreateRouteException: Failed to create route
>> test-mail: Route(test-mail)[[From[{{as-props.in-protocol}}:/... because of
>> Failed to resolve endpoint:
>> imap://mailserver?mapMailMessage=false&password={{pwd}}&postProcessAction=%23emailPostProcess&username={{usr}}
>> due to: Failed to resolve endpoint:
>> imap://mailserver?mapMailMessage=false&password={{pwd}}&postProcessAction=%23emailPostProcess&username={{usr}}
>> due to: There are 1 parameters that couldn't be set on the endpoint. Check
>> the uri if the parameters are spelt correctly and that they are properties
>> of the endpoint. Unknown parameters=[{postProcessAction=#emailPostProcess}]
>>
>> Is this due to the missing interface implementation on my "emailPostProcess"
>> class or there is something else missing somewhere?
>>
>> Thank you for your help!
>> A.
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Mail-copyTo-not-working-and-MailBoxPostProcessAction-not-found-tp5759776p5761363.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -
> Red Hat, Inc.
> Email: cib...@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: Custom Codec for TCP IP
Netty is more popular then Mina, so I suggest to take a look at camel-netty or camel-netty4 component. You can setup you own delimiters by applying the custom DelimiterBasedFrameDecoder to the netty endpoint with the option of decoder or decoders. Please checkout the camel-netty[1] or camel-netty4[2] document for more information. [1]https://camel.apache.org/netty [2]https://camel.apache.org/netty4 -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 6, 2015 at 8:20:40 PM, ravindran (ravindra...@tcs.com) wrote: > > Netty is more popular then Mina, so I suggest to take a look at > camel-netty or camel-netty4 component. > Netty delimeter
Recording events
We're about to build a number of jars which will use Camel to route messages from sources to destinations via business logic processors. One of things we're looking for is the ability to record business events as they happen. Sounds a bit like Wire Tap? We're unsure. Ultimately the events will form an activity stream for our customers and billing systems. The input data and the event itself will likely differ. We don't want to invent the wheel here. Ideas? James
RE: Recording events
Hello James, Yes , this seems like a Wiretap . Maybe you should also copy your exchange if needed. http://camel.apache.org/wire-tap.html -Original Message- From: James Green [mailto:james.mk.gr...@gmail.com] Sent: dinsdag 6 januari 2015 14:55 To: users Subject: Recording events We're about to build a number of jars which will use Camel to route messages from sources to destinations via business logic processors. One of things we're looking for is the ability to record business events as they happen. Sounds a bit like Wire Tap? We're unsure. Ultimately the events will form an activity stream for our customers and billing systems. The input data and the event itself will likely differ. We don't want to invent the wheel here. Ideas? James
Re: elasticsearch component config issues
It doesn’t make sense that camel-elasticsearch endpoint became a master node. In camel we just setup the Client parameter here[1], please feel free to add more option on it if you need. I think we can also introduce addresses option to add other host address for the transport client to use, please feel free to add a JIRA for it. [1]https://github.com/apache/camel/blob/master/components/camel-elasticsearch/src/main/java/org/apache/camel/component/elasticsearch/ElasticsearchEndpoint.java#L82-L86 -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 6, 2015 at 8:40:56 PM, batwad (a...@oh.is.it) wrote: > We have been using the camel-elasticsearch component in transport client > configuration for some time, however we were seeing NodeClosedExceptions > when the node with which it was communicating was restarted so switched to > the node client to take advantage of the automatic failover. We configured > the client with data=false as we didn't want it to store data and things > worked quite nicely. > > However we also use Marvel to collect cluster stats and after a cluster > restart we found that the node client in our Camel application had become > the master node and no stats were being collected by Marvel on the other > nodes in the cluster. When our application restarted one of the regular > nodes became master and Marvel started working again. > > This leads me to question whether an application node client should be > eligible to be a master node or not. I have also seen some plugins that > only run on the master node in a cluster, and if the master node is a node > client that would stop them working, wouldn't it? Perhaps this could be > configurable. > > I'd much rather use the transport client as it feels a better fit for our > application's purpose, however the lack of failover support in the component > is unacceptable. I'd like to be able to specify a list of hosts for the > component to use (maybe in the ActiveMQ style of > failover(host1:9200,host2:9200,host3:9200)) or enable sniffing so that the > transport client could discover the rest of the cluster if it can connect > once. > > All things considered, it would be cumbersome to specify all these things in > the URI on a route, and I wonder if it would be better to have a more > flexible way of configuring the component in code or XML (again, like > ActiveMQ :-)) > > Apologies if that is a bit rambling. I think Camel and elasticsearch are > fantastic and have been spoiled so far with how easy it is integrating > things that maybe I expect things to be too simple now! > > Regards, > Alex. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/elasticsearch-component-config-issues-tp5761369.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
Re: Mail - copyTo not working and MailBoxPostProcessAction not found
Oh Claus, I see!!! I'm very sorry I didn't notice the release is different!!! Ok, so never mind about the postProcessAction issue, when the 2.15 camel release will be available on maven I'll consider upgrading. What remains open is why the copyTo parameter doesn't work in my route. Thanks a lot, A. -- View this message in context: http://camel.465427.n5.nabble.com/Mail-copyTo-not-working-and-MailBoxPostProcessAction-not-found-tp5759776p5761385.html Sent from the Camel - Users mailing list archive at Nabble.com.
activemq jms topic route with durable subscriber
Hi, I have following route which reads the messages from topic and processes it. And configuration for connectionFactory is as follows: The idea is that as soon as a message is published on the topic, the route will process it using the durable subscriber. But we are facing a problem in this configuration: >From 2nd message onwards, since the durable consumer is already created, while attempting to read the message, the route tries to create a new durable consumer with same name and id and hence it fails for durable consumer already in use: 2015-01-06 18:03:25,090 | WARN | .RefreshTopic] | faultJmsMessageListenerContainer | 180 - org.apache.servicemix.bundles.spring-jms - 3.2.11.RELEASE_1 | Setup of JMS message listener invoker failed for destination 'com.mycompany.RefreshTopic' - trying to recover. Cause: Durable consumer is in use for client: consumerOneId and subscriptionName: ConsumerOneName. After this it gives error regarding Consumer is closed for a while: Setup of JMS message listener invoker failed for destination 'com.mycompany.RefreshTopic' - trying to recover. Cause: The Consumer is closed. At this stage, the route is still able to process the message successfully to repositoryRefreshProcessor. This error happens a few times (5 or 6) and then we start getting session is closed error: Setup of JMS message listener invoker failed for destination 'com.mycompany.RefreshTopic' - trying to recover. Cause: The Session is closed. After this, the route stops processing the message and they are not picked up by the durable consumer at all till the system is restarted. Please advice as what is the correct approach to handle/implement such route. I took reference of this example from camel: http://camel.apache.org/durable-subscriber.html Thanks. Yogesh -- View this message in context: http://camel.465427.n5.nabble.com/activemq-jms-topic-route-with-durable-subscriber-tp5761386.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Recording events
Hi James We record business events like the ones you describe, but are not using the wiretab eip since this is recording the event even if the exchange ultimately fails. Sending a message to a wiretab endpoint will be a fire and forget operation that runs in a separate thread. Correct me if I'm wrong here. Instead we always use a direct endpoint to record business events within a transaction if possible. Of course you can also design your route to minimize possible false positives. I wrote a blog about it here http://preben-asmussen.blogspot.dk/ /Preben -- View this message in context: http://camel.465427.n5.nabble.com/Recording-events-tp5761382p5761392.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Does Camel REST DSL work with a Restlet Servlet?
I've found sort of a workaround for this…not sure if it is the best solution. I created a new class that implements the RestConsumerFactory and in the createConsumer method I have it create a restlet endpoint without the host or port. Basically a route with This is the same endpoint uri structure I was using before with my servlet container. -- View this message in context: http://camel.465427.n5.nabble.com/Does-Camel-REST-DSL-work-with-a-Restlet-Servlet-tp5761346p5761393.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: elasticsearch component config issues
Hi Willem, Thanks for your reply. I should have added that we are using Camel 2.12 and I see the code you've highlighted is tagged as 2.14, so it's possible you've fixed a bug already. I notice the 2.14 code does enable sniffing, which the 2.12 code does not. However it looks like node.client is only set when using the transport client (i.e.: when you specify an IP address). When using the node client (i.e.: cluster name only, no IP) no settings are given so it doesn't look like the node will be started in client mode. Maybe that could be why our application node became master. Regards, Alex. -- View this message in context: http://camel.465427.n5.nabble.com/elasticsearch-component-config-issues-tp5761369p5761396.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Recording events
Hi There is also the event notifier which can be useful to capture this. Or route policy as well. Depends a bit how generic vs special case it has to be. On Tue, Jan 6, 2015 at 2:55 PM, James Green wrote: > We're about to build a number of jars which will use Camel to route > messages from sources to destinations via business logic processors. > > One of things we're looking for is the ability to record business events as > they happen. Sounds a bit like Wire Tap? > > We're unsure. Ultimately the events will form an activity stream for our > customers and billing systems. The input data and the event itself will > likely differ. > > We don't want to invent the wheel here. Ideas? > > James -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: Camel CXF SOAP Service
I have tried with version 4 & 5. but no response. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-SOAP-Service-tp5761359p5761410.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel-boot autowiring issue
Hello,
Thanks for the sample project. I adapted it to experiment with
@EndpointInject and @Produces -- they appear to be broken with spring-boot?
The shouldInjectCamelContext() test fails with null for resultEndpoint --
and template is null too.
(Using recently updated camel-spring-boot SNAPSHOT.)
@BootstrapWith(CamelTestContextBootstrapper.class)
@Configuration
@ComponentScan
@EnableAutoConfiguration
@SpringApplicationConfiguration(classes = {CamelConfigurationTest.class,
MyCamelConfiguration.class})
@RunWith(CamelSpringJUnit4ClassRunner.class)
public class CamelConfigurationTest extends Assert {
@Autowired
CamelContext camelContext;
@Value("${name}")
String name;
@Autowired
private CamelConfigurationProperties configurationProperties;
@Autowired
private Environment env;
@EndpointInject(uri = "mock:result")
private MockEndpoint resultEndpoint;
@Produce(uri = "direct:RoomSyncRouteTest")
private ProducerTemplate template;
@Test
public void shouldInjectCamelContext() {
assertNotNull("camelContext", camelContext);
assertNotNull("configurationProperties", configurationProperties);
assertNotNull("env", env);
assertNotNull("name", name);
assertNotNull("resultEndpoint", resultEndpoint);
assertNotNull("template", template);
}
@Test
public void shouldLoadRoute() {
assertEquals(1, camelContext.getRoutes().size());
}
}
Camel + spring boot looks like a great combo...
TIA!
Steven
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-boot-autowiring-issue-tp5758543p5761414.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Mail - copyTo not working and MailBoxPostProcessAction not found
Hi I added an unit test of the copyTo function https://github.com/apache/camel/commit/5a4d715a1b065a3598ad0ef85b98da81f438c0b5 Not sure why it fails for you. Maybe its some permission issue or the copyTo folder does not exists, and cannot be created or something. Your best chance is to run with debug and then step through the code in camel-mail and see what happens in the MailConsumer class. On Tue, Jan 6, 2015 at 3:26 PM, A-Light wrote: > Oh Claus, > I see!!! I'm very sorry I didn't notice the release is different!!! > > Ok, so never mind about the postProcessAction issue, when the 2.15 camel > release will be available on maven I'll consider upgrading. > > What remains open is why the copyTo parameter doesn't work in my route. > > Thanks a lot, > A. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Mail-copyTo-not-working-and-MailBoxPostProcessAction-not-found-tp5759776p5761385.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
