Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I am using fuse6.3 on EAP and FIS2.0 on ocp, the rest DSL has the following Camel components integrated with it:
Servlet component (camel-servlet).
Spark-Rest component (camel-spark-rest).
Netty HTTP component (camel-netty-http).
Netty4 HTTP component (camel-netty4-http).
Jetty component (camel-jetty).
Restlet component (camel-restlet).
There is detail description for the above components for reference, but we want to know, from the best practice, is there any high level guide on which could be the best choice?
Best regards
Lan
I use
choice
JBOSS Fuse 6.x,7.x
camel-netty4-http
Apache Camel 3.x
camel-netty-http
servlets
camel-servlet
component
note
camel-servlet
goes well with spring-boot with embedded tomcat
camel-spark
producer only
camel-jetty
consumer only
camel-restlet
deprecated and has been removed in camel 3.x
camel-netty-http
producer and consumer
Why did I choose netty? camel-netty-http is supported in future versions of Camel and it can be used as both producer and consumer.
https://camel.apache.org/components/latest/spark-component.html
https://camel.apache.org/components/latest/jetty-component.html
https://camel.apache.org/components/latest/netty-http-component.html
https://tomd.xyz/camel-rest/
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I am beginner to apache camel, and i need some clarity in it.
Apache camel is an alternative for microservices? Or what is the advantage of this routing integration.
It has separate HTTP component but its configuration method looks like
from("route1").to("route2")
so how it works when one request arrives in camel application.
Kindly guide me to know the basics of it.
apache camel is an integration framework which helps you to connect many endpoints with different protocols together.There are lots of integrations for apache camel ready to use and no it is not an alternative to microservices but you can use it in microservice architecture.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
Is it possible to deploy a react-redux application to the cloud foundry environment of the SAP Cloud Platform and is it a supported way of the new SAP Cloud Application Programming Model ?
I cannot find any official resources on that so far.
Sure you can do it. You can build a CAP backend app (with a HANA db for example), add an HTML5 frontend app with any framework you like (React, Angular, Vue, etc...) and glue it all together with the App Router, for dispatching your calls.
Here explained step-by-step how to do this:
https://blogs.sap.com/2020/09/01/how-to-build-end-to-end-custom-applications-in-cloud-foundry/?update=updated
To answer your first question, Yes It should be possible to deploy a react-redux based JavaScript application on SAP CF. You can use the static buildback for on cloud foundry. You can check the documentation here.
To answer your second question, I am not completely sure about that, But you can use CAP to generate your database and OData services, and consume them in your application. Additionaly you can check SAP fundamental react
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
In a typically web application, where my back end services and client (AngularJS) are deployed in different containers, how should i chose which controller to code in Spring Boot.
Should i use
#Controller with #ResponseBody or
use #RestController or
use spring-boot-starter-jersey?
What are the pros and cons for each design choice.
#RestController is just a replacement for #Controller and #ResponseBody, hence there's no point in using them when the first option is more expressive and concise.
The main difference between other options is that spring-boot-starter-jersey by default uses JAX-RS annotations while #RestController is part of Spring. You can easily create desired REST services for your AngularJS application with both solutions.
Spring REST services are said to be not compliant with the JAX-RS language specification but it is up to you to decide whether it's important for you or not. JAX-RS isn't required to design a RESTful architecture.
In addition, Jersey is just a JAX-RS implementation so it only allows you building REST endpoints while Spring provides you with more features, like for instance, creating dynamic views where a simple JSON output is not enough.
So all in all, it's up to you to decide what really fits your needs.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
We are using Spring Integration to read from a database, transform into XML, and then place messages onto a topic for an external system. Would there be any reasons to favour Camel for this use case? Also, in general, what advantages, if any, does Camel have over Spring Integration?
A related question: for development using Spring projects such as Batch, Data and XD, how seamless would it be to use Camel with these technologies, in comparison to Spring Integration.
Thanks
Here are a few links that discuss Spring Integration vs Camel.
http://java.dzone.com/articles/light-weight-open-source
http://www.javacodebook.com/2013/07/24/spring-integration-vs-apache-camel/
When to use Spring Integration vs. Camel?
Note that Camel uses Spring for configuration and can easily integrate with other Spring projects such as Batch, http://camel.apache.org/springbatch.html, XD and others.
Nothing requires you to go with a pure Spring stack though many choose to do so. I find Camel a much more pleasant choice than SI in my day to day work.
I don't want to start one more holly war regarding Spring Integration vs Apache Camel, but I'd say: it's up to you, which one to choose for development.
As you noticed Batch, Data and XD, and, of course, Integration, all are projects of Spring.
And what is interest XD is written on Spring Integration and the last one is main tool to extend the XD Runtime.
So, I won't mind that you can write some adapter for Camel in the XD, but will it make sense, if you can just concentrate on your business task with existing abilities from XD via Integration and Spring at all?..
Anyway Spring Integration is a part of Spring IO platform. And you should agree with me, that one Camel can't replace entire platform.
You can find some links to what other people have blogged/written about Apache Camel vs competitors at
http://camel.apache.org/articles
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Am a beginner and wants to implement sorl for search with a mvc web application.
Witch web server is the fastest and most secure to use for sorl?
Jetty, tomcat?
Either is fine.
Solr uses Jetty to make the initial setup and configuration process easier and ships with it. But that does not mean that Jetty is a bad choice for production deployment. If your
The organization already has a standard Java web-application platform, then Solr will work
with it - Tomcat, weblogic, JBoss etc. But if you have some choice then use Jetty. It's fast,
stable, mature, and easy to administer and customize. In fact, Google uses Jetty for their
App Engine—see www.infoq.com/news/2009/08/google-chose-jetty/.
If you want to use Tomcat solr has steps to setup , its easy : http://wiki.apache.org/solr/SolrTomcat
So the answer depends, security, what your organization allows. Solr is a war file all it cares is for a Servlet Container.