This week's book giveaways are in the Cloud/Virtualization and Go forums.
We're giving away four copies each of Cloud Native Transformation: Practical Patterns for Innovation and The Go Workshop and have the authors on-line!
See this thread and this one for details.
Win a copy of Cloud Native Transformation: Practical Patterns for InnovationE this week in the Cloud/Virtualization forum
or The Go Workshop in the Go forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Knute Snortum
  • Henry Wong
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Frits Walraven
  • Joe Ess
  • salvin francis

component diagrams.

 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi guyz,

just a question about component diagrams. Do you deeply explain the concept of a MVC framework (Front controller + dispatcher + helpers(model) ) or can we just put a component tagged <<Servlet>> just as in Cade's book. I dont know till which level of explanations we re supposed to arrive.

i mean :

first solution is :

Jsp component ---> Servlet Component ---> Business delegate(with service locator) ---> Facade SLSB .....


second solution is :

Jsp component ---> Front controller (with request mapping, request processor, command pattern, dispatcher) ---> Business delegate (with service locator) ---> Facade SLSB ....

I m making a Customer Component Diagram and i m confused about the strategy to use.

any ideas ?

tery
 
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

Sorry to wake this old post up. I have somes almost similar concern.

1. My anwser is also my question:

I am planning to have only one component "Display View" with stereo "JSP" and other "RequestController" with stereo "Servlet". Not much like Mark Cade : "BrowseCatalogForm", "SearchCatalogForm" etc.

For the swing, the same thing : one "UserForm" with stereo "SwingGUI", one "Controller" component , one BD/SL.

Do you think is that OK?

2. By the way, extra question :
- The swing have login component instead of JAAS (JAAS is complicated for me).
- I dont use SFSB, session information will be store in HttpSession for web, in the controller at client side for the swing.

Is that Ok too?

Thanks in advance!
 
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It will depend of what you're trying to do. For architecture pourposes, you should try to define a high level architecture, focusing at layers, dependencies, business components and subsystems. But for some implementation model, you could enter at those low level details about patterns and classes from MVC.

My tip: Keep the things simplier! Create something readable, but not overcluted.

Regards,

Originally posted by tery valencia:
hi guyz,

just a question about component diagrams. Do you deeply explain the concept of a MVC framework (Front controller + dispatcher + helpers(model) ) or can we just put a component tagged <<Servlet>> just as in Cade's book. I dont know till which level of explanations we re supposed to arrive.

i mean :

first solution is :

Jsp component ---> Servlet Component ---> Business delegate(with service locator) ---> Facade SLSB .....


second solution is :

Jsp component ---> Front controller (with request mapping, request processor, command pattern, dispatcher) ---> Business delegate (with service locator) ---> Facade SLSB ....

I m making a Customer Component Diagram and i m confused about the strategy to use.

any ideas ?

tery

 
permaculture is a more symbiotic relationship with nature so I can be even lazier. Read tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!