Announcement Announcement Module
No announcement yet.
What is the uml pattern in Spring Architecture ? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • What is the uml pattern in Spring Architecture ?

    When we are using Spring Architecture, I want say when we have:
    DAO level + Service level + Spring mvc Level (using interfaces and implementation of the services)

    what elements we can identificate with the rol of "Service Locator" and "Delegates" inside this Architecture ?

    it exists ? it's necesary ? have you any diagram than explain it ?

    Thanks folks.

  • #2
    Using spring you don't tend to use the Service Locator pattern due to the fact that services are injected into your business classes rather than the business classes looking up a service, however if you were to make a call like
    applicationContext.getBean( "myServiceProvider" )
    Then you could say that Spring's applicationContext is a Service Locator but this is not the normal way of doing things within Spring.

    Your service level classes are probably what you would refer to as Business Deligates being the coarse grained interface to your business logic.

    Does this answer your question?

    Other patterns you will find in your Spring applications are...
    • Intercepting Filter - if you use LocaleChangeInterceptor and/or CookieLocaleResolver
      Front Controller - DispatcherServlet
      View Helper - Any classes that extend AbstractController
      Command - Any classes that extend BaseCommandController
      Transfer Object - I'm sure I don't need to point that one out
      Data Access Object - Again, you have already identified these