1. Which of the following may be performed when a packaged enterprise application (EAR file) is deployed or installed in WebSphere Application Server, V5.0?
A. Generate the deploy code for enterprise beans in EJB modules.
B. Define the custom tag libraries used by the JSPs in the web module deployment descriptor.
C. Specify "Context Root" for each web module.
D. Generate Access beans for any enterprise beans.
E. Map entity beans to relational database schema.
Originally posted by Tony Chen:
My answers would be: A and E
"C" is not correct 'cause you can only specify "Context Root" while installing an individual WAR file.
What do they mean by diverse client profile? Does it mean that the state for different clients can contain little or much data?
How the phrase "Application data involves only small amounts of primitive data, which are not sensitive" influence the answer?
Originally posted by Zach Lee:
Diverse client profile - It means you've got to design your application with possibly non-HTTP clients in mind.
The second quote - Cookies would be Ok to handle low-security, small amounts of primitive data. But cookies are only good for HTTP clients.
B and C also limit you to HTTP clients.
So I would select D - stateful session beans.
Just my 2 cents. I would like to hear from Howard on this.
Howard Kushner wrote:
Think about it a little and then if you're stil not sure why, I'll provide a few more clues.
Originally posted by Peter Reinhardt:
B and ?
Surely option A makes an application more robust (failover to a second server). But options C & D do not really sound right.
whats wrong with answer A, implementing Business logic in the MDB?
Originally posted by Nikhil Pendharkar:
27. A developer has created a Java Project in IBM WebSphere Studio, which is used by an EJB Project. When the server is started for testing, the following messages appear in the console. ... addEjbModule failed for LibraryEJBProject.jar [class com.ibm.ws.runtime.component.DeployedModuleImpl] java.lang.Error: Unresolved compilation problems: ... Which of the following should the developer suspect?
Looking at the above question I feel that correct answer would be
C. The Java Project is not added to 'Project Utility JARs' in the Application Deployment Descriptor
Because Java Project in IBM WebSphere Studio, which is used by an EJB Project would nothing but the utility jar which should be added in the application deployment descripitor. If that is not added then any references made to the classes in that utility jar would definitely result in compilation errors for the EJB Project. If user tries to run the EJB project with these errors its possible that the error specified in the question above would be thrown back.
Still I am not sure, just a logical guess from my side
Originally posted by Edy Yu:
3. Which of the following MUST be provided in a tag library descriptor XML file?
A. The version of JSP custom tags being used.
B. The version of J2EE for the custom tag library.
C. The definition of at least one custom tag.
D. The short name of the web application in which the library is used.
E. The prefix for the custom tags defined in the library.
I think the answer is A, C.