What might be the cause of this problem?

You are the architect of a web application that uses javaServer Faces (JSF) as a presentation tier

for business processes coded as stateless session beans. When you add new code to the
stateless session beans to address new accounting requirements, without changing the interface,
you discover that the new business processes are being ignored by some of the JSF components.
What might be the cause of this problem?

You are the architect of a web application that uses javaServer Faces (JSF) as a presentation tier

for business processes coded as stateless session beans. When you add new code to the
stateless session beans to address new accounting requirements, without changing the interface,
you discover that the new business processes are being ignored by some of the JSF components.
What might be the cause of this problem?

A.
The presentation tier is relying on validation logic in the business tier.

B.
The browser is caching out-of-date versions of the JSF components.

C.
The business processes are not rigorously encapsulated in the session beans.

D.
The new session beans have been deployed incorrectly, and proper deployment will resolve the
problem.



Leave a Reply 3

Your email address will not be published. Required fields are marked *


Reviewer

Reviewer

So what is it exactly meant by “The business processes are not rigorously encapsulated in the session beans”?

Juaan The One

Juaan The One

C is Right … If you have the bussiness logic in the presentation tier and the bussiness tier, for example, thats could explain why some JSF Components are working well with nthe new code but other is not because(“The business processes are not rigorously encapsulated in the session beans”)

A –> False … Thats the theory, but this is not causing the problem
B –> ?¿?¿ … False
D –> False … If its not well deployed they should not work in all cases, not in some