Given this list of attributes:

- related to Intercepting Filter

- supports role separation between developers

- adds reusability

Which design pattern is being described?

The design of your web application calls for certain security measures to be taken for every request received. Some of these security checks will be applied, regardless of the type of request.

Which design pattern can be used to achieve this design requirement?

Your company wants to leverage its distributed silos. Your job is to seamlessly integrate your application’s web service endpoints with its DAOs. In addition, your coarse-grained Controller Locators must be enhanced to support J2ME, UDDI registries.

Which design pattern can be used to achieve these design requirements?

This statement describes the potential benefits of a design pattern:

The pattern reduces network roundtrips between a client and an Enterprise Bean, and gives the client a local copy of the data encapsulated by an Enterprise Bean after a single method call, instead of requiring several method calls. Which design pattern is being described?

Your company, Models ’R Us, is creating an advanced inventory maximization component that can be used with all major J2EE container vendors. Your job is to design the piece of this component that will perform JNDI lookups with whatever vendor the client is using.

What design pattern can help you accomplish this task?

While fine tuning your multi-tiered J2EE business application, you’ve discovered that you’d get better performance if you reduced the number of remote requests your app makes, and increased the amount of data collected for each request you make.

What design pattern should you consider to implement this change in your application?

Given this list of attributes:

- related to Service Locator

- reduces coupling

- can add a layer and some complexity

Which design pattern is being described?

Your web application uses a SessionBean component in a distributed application to make a specialized calculation, such as validating credit-card numbers. However, you want to shield your web components from the code involved with looking up the SessionBean component and using its interface. You want to decouple local application classes from the looking up and use of the distributed component, whose interface could change. Which J2EE design pattern can you use in this case?

Given this list of attributes:

- related to Business Delegate

- improves network performance

- can improve client performance through caching

Which design pattern is being described?