There are *many* ways to skin this particular cat. Naturally, Spring provides everything you'll need to build it any number of ways. It's easiest to break down the requirements in isolation and pick a strategy from there.
Most likely, you'll need to store data in a database. You'll need to manipulate the state of the database from
Java. If you're deploying to the web, then you'll also need to build a client or web application.
To store data in a database, you can use Spring's numerous options for data persistence. Spring provides super clean, easy to use options for data persistence with any number of technologies, be it straight
JDBC, Hibernate 2 and 3, JPA, iBatis, etc. For more on building a domain driven database application, see
http://blog.springsource.com/2011/01/07/green-beans-getting-started-with-spring-in-your-service-tier/.
The next step is building your web application. For that, you can use Spring MVC to build a web application with HTML. You could also use Flex and the Spring BlazeDS support to build a Flex-based application that works with Adobe AIR. You might use Spring Android to build a shopping cart that works on Android devices, etc. So, clearly, you've got lots of choices and there's no clear way to tell you whether you'd need JavaScript or not without details.
If you're new to Spring, there are a lot of options. To make it dead simple to get a good result, quickly, you might look at Spring Roo. Spring Roo provides a domain driven development model. You learn how to build a Spring Roo application and it'll build the database code, Java services and web application for you, which you can then fine tune once it's all working. I'm not sure what information you'd like to brush up, but you might start at
http://blog.springsource.com/category/green-beans/, where we have numerous blog posts on numerous topics, all geared towards beginners.