Practical use cases of Spring Integration? [closed] - java

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 7 years ago.
Improve this question
I have started learning spring integration. As of now learnt that it provides features like transformers, filters etc
But I am not getting what can be practical use cases of spring integration. Say if I have to just transform java object to xml/json or vice versa.
Should I go ahead with spring integration . I think no as it can be achieved with their 3rd part libraries also . So what can be the use cases of
spring integration ?

Its very much used for enterprise integration.There are many theories and examples that you may have read. I can give you one scenario where we are currently using Spring integration.
We manage a business system in which we have to connect to different telecom operator with different kind service to get some information.Now some telecom operator uses email,soap based web service ,restfull webservice,Sockets ,ftp etc and all these we need to integrate our system. So we have one component which integrates with all the operator just by some simple configuration and very minimal codes.

Related

Design an application with multiple request sources: WS(SOAP\REST), MQ, batch [closed]

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 5 years ago.
Improve this question
I have to design an application which gets requests from multiple sources like Web service (can be SOAP or REST), online system, Message Queue or some batch job. Application needs to interface with 2 more applications for getting results. I understand that this can be done using microservices. This application needs to be built in Java. I am looking for some framework which can help me with accepting input from multiple sources as mentioned above.
If you want to build a lightweight simple layer (single app) to cater all these requirements, I would recommend using Apache Camel. This single app can listen to rest/soap requests, read from file system, JMS store, database etc. You can even embed it into another application and have all sorts of integration with different data source and excellent and easy to configure routing and transformation engine. Plus the documentation and community is awesome.

Web application achitecture [closed]

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 7 years ago.
Improve this question
I've to rebuild a swing based application to move it to a web environment. This application has some functionalities that already exist in another web application. I want them both to maintain the same functionalities, even those that are shared, but I don't want duplicated code.
In terms of architecture/technologies, what is the best approach to reuse as much code as I can? A third service-oriented application that controls all the business logic and have the web applications serve only as front-end? But how to avoid code duplication on the front-end?
Any feedback will be much appreciated.
very broad question so it's hard to give exact solution. think about separating common functionality as a different service. then both application can just redirect to it or use its api.
if that's not an option then try to separate that logic to a library that will be included in other application. good frontend frameworks allow you to do it also with frontend code (directives, plugins, validators etc)
You could work with dependencies transforming the common utilities, access data and business rules in libraries. In first moment you can make a refactor separating tiers and responsibilities and then you can incorporate Maven in you environment to generate and start to work with dependencies.

Java Project to Spring Restful services [closed]

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 7 years ago.
Improve this question
I am very new to Spring and REST. I've practiced few tutorials on Spring from internet and successfully executed few projects.
Now I have a plain Java project (with 5 packages 12 classes). I would like to convert this Java project to Spring framework with REST Services. I have nearly 4 (out of 12) classes (which would be my services). (I don't have any UI).
Can someone please help me out on how to convert this project to Spring-REST? I've been searching all over internet but nothing matches my context.
The fastest way to go IMHO is via Spring Boot Spring Boot makes it easily to bootstrap a fully working Spring-REST-Stack. In combination with Spring Tool Suite, you are up in no time.

Any Spring PHP project? [closed]

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 9 years ago.
Improve this question
I am coming from Java Spring background. I am big fan of various Spring modules like Spring Core, Spring Security, Spring MVC etc.
I would now like to implement a web project in PHP and also I would like to leverage features provided by Spring framework. Is it possible to expose Services (Service Oriented Architecture) on server side using Spring and PHP?
I read about this article http://www.cs.montana.edu/~tosun/phpvsjava.pdf wherein a lot of limitations of PHP mentioned w.r.t. Java. Do you suggest any alternatives for overcoming these limitations?
Any help will be highly appreciated.
Thanks!
You should consider Symfony. You get a lot of nice features like dependency injection that you are used to with Spring.
Hope that helps.

infrastructure software for developing web service [closed]

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 8 years ago.
Improve this question
I'm developing a web service and as being new to the technology, I did a bit of research on the internet on the infrastructure software/technologies needed. Below are my findings and hope to get your precious opinion:
Application Server - Tomcat6
Web service engine - Axis2
Web service implementation - POJO
Accessing Database MySql - JPA (Only 5 simple tables)
Do they look good to you?
I'm thinking of using EJB3 for point3, but there are a lot of people on the internet (and this forum) saying EJB3 is not worth the effort, POJO will do. What's your view?
Thanks,
Sarah
Might be worth trying on programmers.stackexchange.com as its not specifically a coding question. For my 2 cents, I'd seriously consider whether you wanted to go down the SOAP route (Axis is SOAP only) or whether you should use REST.
Tomcat is usually a good choice for a server, as is MySQL for a DB. If you're going to use JPA, you need to choose a JPA implementation; the obvious one is Hibernate. If you do choose to use REST then I can recommend Jersey, which is Sun's reference implementation.

Categories