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
When I started to learn a Spring Faramework I focused my attention on specific details but not on clue and global concepts. Actually I can't grasp some of Spring framework goals.
May be this question too wide, but I don't see any sense to divide it into few separate questions. I don't expect that you answer all my question, but at least one of them.
Spring framework goals:
Make J2EE easier to use
Address end-to-end requirements rather than one tier
Eliminate need for middle tier “glue”
Provide the best Inversion of Control solution
Provide a pure Java AOP implementation, focused on solving common problems in J2EE
Fully portable across application servers
“Non-invasive” framework
Facilitate unit testing
Facilitate OO best practice
Provide a good alternative to EJB for many applications
Enhance productivity compared to “traditional” J2EE approaches
Questions:
1). Easier to use? By mean of what? And comparing with whom? It seems for me that comparing with pure J2EE each framework provide ease of use. Please more details and examples.
2). Don't understand this point. What is end-to-end requirements?
3). Don't understand this point.
6). Does it mean that another Spring alternatives isn't portable via app servers? Isn't EJB portable?
9). Isn't it the same as 4th point.
11). Please some examples of that non-productive J2EE approaches.
You can go through below links to know more :
spring forum
spring-3-0-vs-java-ee-6-0
Spring vs Java EE
Why Java EE Lost and Spring Won
Related
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 6 years ago.
Improve this question
About 3 month ago, I was charged to do a presentation and a demo explaining what is SOA composition.it wasn't easy to do it because latest eclipse version (neon) doesn't support BPEL projects any more, Eclipse Luna and an extension helped me in this situation.
From that time there's some questions that roam around in my mind :
why there's no new tutoriel about SOA composition ?
Are these architectures are deprecated ? if yes why are they ?
I do think (and this is an opinion) that SOAP/SOA/ESB/BPEL is obsolete and taken over by RESTful Architectures. By RESTful I don't mean things that have a primitive JSON+HTTP API, but real distributed applications, where endpoints are not dumb, but define the part of the workflow that belongs to them.
So, the two conceptual things colliding are: Do I want a central "smart" component (like ESB, and pure BPEL services) and dumb (for example SOAP) endpoints. Or do I rather have no central components and smart "endpoints" (like REST resources).
I think conceptually the latter is the clear winner in many cases (not all arguably). There are practical problems however. Companies always like to centralize. Centralization looks "neat" and "tidy", especially for an Enterprise Architect. Until the central components grow out of proportions that is.
One of my clients introduced an ESB just last year, so it's definitely not over. But I do think (again, this is just my opinion), that we already tried centralized architectures and monoliths. They always end in the "legacy system" bin, that can not be replaced because it does everything. So we know where they lead, we need to try something different. :)
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 am going to develop a (relatively) simple game for the Android platform.
It's gonna be 2D-Game (no heavy stuff, maybe simple animations)
I am considering using a framework (like AndEngine)
What are the advantages/disadvantages of using a framework? (rather than developing from scratch)
Thanks!
Well this can be a broad subject, nonetheless I'll toss in my 2 cents.
There are plenty of advantages using a framework and this applies to many other scenarios. Just think of a framework as a bridge to shorten the path and not have to reinvent the wheel.
A framework will pretty much handle the boring plumbing you would have to do otherwise.
Using a framework will, in most cases, make you code faster and some will probably «force» you to code in a cleaner and more organized fashion. Although this has much more to do with the programmer itself...but there are opinionated frameworks out there that will at least lead you the way.
The biggest disadvantage is not using a framework in itself, but picking the right framework. I think you have to make a few questions before deciding to pick Framework A, B or C such as : Is it sufficientlly mature for my needs? Does it have a good community or vendor support? Is it here to stay? What happens if the framework loses pace or support? Will I be in trouble?
There are other disadvantages of course. You may be putting yourself open to the risk of learning the Framework and neglecting the language behind it. For example, you may know jQuery but it's not liquid that you know javascript. See where I'm going?
Also, you can find yourself shackled by the framework limits. You may not be able to have full control of the code you write or at least not be able to express your code better because the framework it self has tight bounds. In other words, you are forced to respect its limits and work the way it is required. Again, pick the right framework for your needs.
I hope this helped.
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
what is the Advantage/disadvantage of use java ee 6 vs spring framework in enterprise application?
Which one is better for large scale projects(why)?
comparing to java ee 6, what is spring disadvantages ?
i dont have any experience in spring but i want to know difference between them.
Java EE s main advantage is that it is an official framework. It has all the same features as Spring except for the fact, that it always goes in one box - container (even if you do not need some components, they will be present). Of course, it is possible to hook some components of Java EE (like Weld) separately into your java SE app, but it is not common.
Spring on the other hand is more configurable in terms of the components you want. You can decide yourself what you need in your application (usually DI). Spring can also use Java EE features (such as JSP).
If you need only some small subset of Java EE (like Dependency Injection), it is better to use Spring for it. If you need multiple features of Java EE (ie. JTA + JMS + DI + etc), I would go for Glassfish.
The main difference is that with spring framework you do not need a full JavaEE container. Otherwise, they are more or less two different solutions for the same problem. I will not comment on the advantage/disadvantage part of the question since this is opinion based.
JavaEE 6 is much more similar to Spring 2/3 than before. The main Spring features / projects has its JavaEE equivalents and you don't need a full JavaEE server to run. You just need the areas you use.
One advantage of Java EE is to code just having the small JavaEE API as a dependency and leave the implementation as responsibility of the server. You don't need a certified server. You can run it in a Tomcat with just the implementations you need. They already did it for you with the TomEE project.
So that's it. If you want to use just java and javax packages instead of org.springframework in your classes you choose JavaEE.
If you don't mind to use non java or javax packages (why would you?), so you can use Spring and any other non Java library.
Both offers solutions for many problems and all the answers in Stackoverflow will be biased. It's not useful to ask that generic question. It depends. What are you goals. Your syntax and usage preferences. Performance requirements. Security requirements… each component can be better, depending on the usage, and you have the option to use both and choose from each one, what helps you best.
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 have worked on struts 1.2 and DWR as front end MVC framework.Now i have two projects to develop one is simple web application and another is complex.Which one i should select from most prevalent MVC Framework Spring mvc, Struts 2, DWR,JSF and brief reason to select any of the MVC . Most of the team knows all the frameworks. What are the factors i should consider to select any Framework.
I would consider what is the scope of my project, if I am anticipating complex system with lots and lots of various implementations, then I would go for Spring, for moderately complex system I would go for JSF.
One also need to consider if the primary designer leaves the team would other team members or a new comer will be able to pick particular MVC framework with ease or not (consider using well known MVC vs not-so-well-known-personal-favourite-picked-out-of-google). How mature the particular MVC framework is, are there good books written about it etc. These are just from top of my head.
Also keep in mind when there is too much of Spring (or any other ioC container) involved, there comes a time (after 8-12 months) when you are unable to debug code correctly because there are so many classes involved that you just keep tracking which class goes to which spring context files etc.
Finally, as one of my mentors used to say, don't solve the world problems (by using lots of design patterns), solve the problem at hand. :-)
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
I know this question is subjective but I would really want to know what are the best j2ee web application auto code generators.
I googled and found out the Appfuse is one of them.
Spring ROO is another but it depends on spring i think.
Are there any other better tools?
Basically lot of time is spent on creating regular CRUD screens with the same mundane things for each screen.
So, I would want to reduce the time spent on such simple CRUD screens so that I can focus more on the core application logic.
We use Telosys (http://www.telosys.org/) to generate repetitive code like CRUD screens.
A set of templates are available for Spring MVC, JPA, AngularJS, etc.
We have customized some of them. It saves of lot of time.
The best solution I have seen so far is Grails. It generates groovy code, not java but you can interface painlessly with any java library/class. The convention over configuration features are amazing and one can put up a functioning web app in minutes. I suggest you see for yourself - just try the grails screencasts. They will get you up to speed in 15 minutes.The technologies used under the hood are best-of-breed : spring, hibernate, lucene, quartz, sitemesh etc.