Q. To run the script:-

View solution

Q. Maven Directory to hold the non–unit-test Java files for your application.

View solution

Q. Maven Directory which holds classpath resources that aren’t Java class files.

View solution

Q. Maven Directory which is used to hold the rest of a web application’s structure.

View solution

Q. This directory holds artifacts intended to test the Java classes under the src/main/java folder.

View solution

Q. This directory holds resources needed by your test classes at test time.

View solution

Q. To package the project using the Roo shell.

View solution

Q. The plugin, which provides Maven support to Eclipse

View solution

Q. Spring Roo provides very powerful support to bootstrap most solutions.

View solution

Q. A database and some sort of persistence mechanism using command:-

View solution

Q. persistence setup –database HYPERSONIC_IN_MEMORY –provider HIBERNATE command creates files:-

View solution

Q. The file which contains useful configuration for Hypersonic in-memory database.

View solution

Q. The file which is the standard JPA configuration file to enable the Hibernate-based JPA implementation.

View solution

Q. Spring application context, src/main/resources/META-INF/spring/applicationContext.xml consists of:-

View solution

Q. Command to create a Spring MVC controller that provides a UI:-

View solution

Q. To deploy the application to a web container:-

View solution

Q. Spring Roo’s root folder (or any of the source packages) is:-

View solution

Q. This encapsulates the context of a test’s execution:-

View solution

Q. This manages a test context for a test and triggers test execution listeners:-

View solution

Q. This defines a listener interface; by implementing this, you can listen to test execution events.

View solution