A location where logging information is sent.
1.appender
2.logger
3.all of the mentioned
4. none of the mentioned
An appender that logs to a JDBC connection.
1.jdbc
2. console
3. file
4.rollingFile
Library which helps Spring Roo in using of the command line shell.
1. JTag
2.JLine
3.JHib
4.None of the mentioned
Log4J configuration parameters are specified inside:-
1.Config.groovy
2.Conf.groovy
3.Log.groovy
4.None of the mentioned
Spring Roo supports tab completion.
1.True
2.False
3.none
4.all the mentoined
To confirm Roo version.
1. roo.sh
2.roo
3.roo quit
4. roo.sh quit
A database and some sort of persistence mechanism using command:-
1.persistence setup –database HYPERSONIC_IN_MEMORY –provider HIBERNATE
2. persistence setup –database HYPERSONIC_IN_MEMORY –provider
3. persistence setup –database HYPERSONIC_IN_MEMORY
4.persistence –database HYPERSONIC_IN_MEMORY –provider HIBERNATE
A Grails view can contain:-
1.HTML Tags
2.GSP or JSTL Tags
3.Groovy or Java code
4.All of the mentioned
A location where logging information is generated.
1.appender
2. logger
3.all of the mentioned
4. none of the mentioned
A view can require a unique combination of display elements and business logic.
1.True
2.False
3.none
4.all the mentoined
A view’s body content is inside the:-
1.g:javascript library=â€applicationâ€
2.g:layoutHead
3.g:layoutBody
4.g:layoutMeta
Any logging operation occurring at any of the cited packages will be logged.
1.True
2.False
3.none
4.all the mentoined
By default, all logging message are sent to the stacktrace.groovy file.
1.True
2.False
3.none
4.all the mentoined
By default, Grails applies a global layout to display an application’s content.
1.True
2.False
3.none
4.all the mentoined
By default, Grails assigns custom tags to:-
1. g: namespace
2. f: namespace
3. j: namespace
4.All of the mentioned
Command for running tests in Grails.
1.grails test-app
2.grails test
3.grails test-app domain class
4. none of the mentioned
Custom tags can also rely on input parameters.
1. True
2. False
3.none
4.all the mentoined
GORM dynamic finder comparators:-
1.InList
2.LessThan
3.LessThanEquals
4.All of the mentioned
Grails application logging can be configured using:-
1.creating custom appenders
2.logging levels
3.console output
4.All of the mentioned
grails create-tag-lib tag-lib-name command creates a custom tag library under:-
1. /grails-app/tag/
2./grails-app/
3. /grails-app/tag-lib/
4.none of the mentioned
Grails doesn’t supports the concept of templates.
1.True
2.False
3.none
4.all the mentoined
In Log4J parlance, each package is known as:-
1.parlance
2.logger
3.all of the mentioned
4.None of the mentioned
In order for this custom tag to function properly in JSP, it’s necessary to add it to the corresponding Tag Library Definition (TLD) grails.tld.
1. True
2.False
3.none
4.all the mentoined
Log4J also has the following logging level:-
1.fatal
2.error
3. warning
4. all of the mentioned
Maven Directory to hold the non–unit-test Java files for your application.
1.src/main/java
2.src/main/resources
3.src/main/webapp
4.src/test/java
Maven Directory which holds classpath resources that aren’t Java class files.
1.src/main/java
2.src/main/resources
3.src/main/webapp
4.src/test/java
Maven Directory which is used to hold the rest of a web application’s structure.
1.src/main/java
2. src/main/resources
3. src/main/webapp
4.src/test/java
Method creates a mock object from a domain class.
1.mockForConstraintsTests
2.mockForConstraints
3.all of the mentioned
4.None of the mentioned
persistence setup –database HYPERSONIC_IN_MEMORY –provider HIBERNATE command creates files:-
1.src/main/resources/META-INF/persistence.xml
2.src/main/resources/META-INF/spring/database.properties
3.all of the mentioned
4.None of the mentioned
Spring Roo file extension is:-
1. .xml
2..xhtml
3. .roo
4..groovy
Spring Roo provides very powerful support to bootstrap most solutions.
1.True
2.False
3.none
4.all the mentoined
Tag allows any view inheriting this layout automatic access to JavaScript libraries.
1.g:javascript library=â€applicationâ€
2.g:javascript library=â€applicationâ€
3. g:layoutBody
4.g:layoutMeta
Tag is used to define the contents of a layout’s head section.
1.g:layoutTitle
2.g:layoutHead
3.g:layoutBody
4.g:layoutMeta
Tag is used to define the contents of a layout’s title section.
1.g:layoutTitle
2. g:layoutHead
3.g:layoutBody
4.g:layoutMeta
The default Log4J logger can be customized in a Grails application.
1. True
2.False
3.none
4.all the mentoined
The file which contains useful configuration for Hypersonic in-memory database.
1.src/main/resources/META-INF/spring/database.properties
2.src/main/resources/META-INF/persistence.xml
3. src/main/resources/META-INF/pom.xml
4.None of the mentioned
The main mission of Spring Roo is fundamentally and sustainably improve Java developer productivity without compromising engineering integrity or flexibility.
1.True
2.False
3.none
4.all the mentoined
The plugin, which provides Maven support to Eclipse
1.m2eclipse
2.m2plugin
3.plugin
4.None of the mentioned
The Spring Roo shell is a blank slate. It represents the ultimate user interface for Spring Roo to facilitate development.
1. True
2. False
3.none
4.all the mentoined
This directory holds artifacts intended to test the Java classes under the src/main/java folder.
1.src/test/java
2.src/main/resources
3.src/main/webapp
4.src/test/java
This directory holds resources needed by your test classes at test time.
1.src/test/java
2.src/test/resources
3. src/main/webapp
4.src/test/java
To check version of Maven.
1.mvn –v
2.mvn -v
3.mvn –version
4.All of the mentioned
To create custom tags.
1. grails create tag
2.grails create-tag-lib tag-lib-name
3. all of the mentioned
4.None of the mentioned
To offer versatile logging functionality:-
1.loggers
2.appenders
3.all of the mentioned
4. none of the mentioned
To package the project using the Roo shell.
1. perform package
2.roo.sh
3.all of the mentioned
4.none of the mentioned
To perform its logging operations.
1. Log4J
2.LogingJ
3.JLog
4.None of the mentioned
To run the script:-
1.roo.sh script –file ~/Desktop/myapp.roo
2.roo.sh –file ~/Desktop/myapp.roo
3.all of the mentioned
4.None of the mentioned
Unit tests are designed to validate the logic contained in a single domain class.
1.True
2.False
3.none
4.all the mentoined
Where is subdirectory called layouts located, containing the layouts available to an application?
1./grails-app/view/
2. /grails-app/
3. /grails-app/view/WEB-INF
4.None of the mentioned
You can ask Roo questions using:-
1.tab
2.hint
3.all of the mentioned
4.none of the mentioned