Service Locator in Component Diagram

[Lyju Edwinson]

Hi,

I am sorry If I am repeating this question some have.

1)

I have the following design, JSP --> Controller --> Business Deligate --> Session Facades --> SQL Adaptors (JDBC) and Service Locator ( web service clients)

I have put SQL Adaptors in Integration layer, now thinking on where to put the Service locator and web services clients.

is it ok to make a new layer called "Web Service Layer" and put the Service Locator there ?

Basically My Session Facade --> DataAssembler ( calls different web service method and assembles data for the client tier) --> SeviceLocator --> Remote Serbvices.

2) I am caching the data from remote service calls in the client tier ( Cache Interface is provided), where will I include this in Component diagram?

The data is first checked in this client cache and if not found remote call to the session bean is done to get the data.

Please let me know.

[Rishi Shehrawat]

I have the following design, JSP --> Controller --> Business Deligate --> Session Facades --> SQL Adaptors (JDBC) and Service Locator ( web service clients)

I have put SQL Adaptors in Integration layer, now thinking on where to put the Service locator and web services clients.

is it ok to make a new layer called "Web Service Layer" and put the Service Locator there ?

I think that service locator is not required for web services, given that web service referece can be injected by using @WebServiceRef
Using both business delegate & session facade seems like a overkill as there is an overlap between the two.
Are you not using JPA? In my opnion the expectation for this certification is that JPA should be used for persistence, unless you have a good reason for not using JPA.

I am caching the data from remote service calls in the client tier ( Cache Interface is provided), where will I include this in Component diagram?

It can be shown in the component diagram.

[Lyju Edwinson]

Thanks a lot for the reply.
That make sense.

I will use JPA , I think thats better .
Basically JDBC will save my purpose.

Regards
Lyju