2

I need to port a legacy internal Java EE application (JSPs, EJBs/stored procedures, Weblogic) over to a newer Java web framework and revamp the features/UI substantially. I'm somewhat limited because the backend will remain Oracle Stored Procedures (no direct SQL), so that rules out many ORM/JPA technologies.

At this point, I'm leaning towards using Spring JDBC to wrap the stored procedure access and a combination of Spring MVC, REST & perhaps Twitter Bootstrap for the frontend. Overall, I'd like to be better positioned to support iterative/agile feature development, etc.

Any other (Java) web technologies worth looking into?

2 Answers 2

4

This is just my humble opinion, I would recommend looking into Grails. Although it sounds like you won't be able to leverage GORM, Grails still provides an excellent MVC framework approach, and the convention-over-configuration means that you do not need to deal with the XML configuration files and/or annotations that you do with many other frameworks.

Here is another Stackoverflow post regarding Grails without Gorm: https://stackoverflow.com/a/4600991/463196

In Grails, Taglib support is great (writing custom Taglibs has never been easier) and the plugin ecosystem is incredible.

Also, Groovy means not having to write a lot of the boilerplate getter/setters, overloaded constructors of old. The easiest line of code to support is the one that was never written.

Sign up to request clarification or add additional context in comments.

3 Comments

+1 to this. In the past 2 years I've had to write 2 x new front-ends to existing systems (backend - communicating via web services) and I did one in Spring MVC and the other with Grails (no GORM). Would definitely go with Grails if doing it again.
Grails does look interesting, but we already have a lot of domain/dao/utility Java classes that we need to reuse and I don't see how that would fit with Grails easily...
Here is a very good response to integrating existing Java code with Grails. stackoverflow.com/a/896288/463196. I haven't done this myself, but it is a very well-thought out answer that bears looking into, should you choose to go the Grails route.
2

I know this is not really an answer to your question since you've given it already. But from personal experience on similar setups (Java EE/Oracle stored procs/functions) I cannot recommend enough the combo you've suggested with Spring Core/MVC and SimpleJdbcCall to link to your existing Oracle stored procs. I particularly like this setup since it scales very nicely and you can start refactoring bit-by-bit non-intrusively.

2 Comments

what about the templating technology...I've used Freemarker in the past...are there any better options out there?
I've used Freemarker and Velocity in the past but I tend to prefer Velocity because of its syntax simplicity and the addons provided through VelocityTools

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.