Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Sequence diagram question

 
Shogo Ito
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Which is correct message interaction in a sequence diagram when a user fills a form and submits?

Customer ---> Controller ---> ....
Customer ---> JSP ---> Contoroller ---> ...

Thanks!
Shogo
 
Josep Andreas
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Shogo,
In Cade's Guide they start with Customer->JSP.
This should be safest. But I have seen other examples where they start with Customer->Controller.
regards,
J
 
Bil Bob
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would recommend you research/think about why they would be in either order

Think about how can you access controller without JSP. and v/versa
 
Josep Andreas
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bil,
I assume that you mean:
A) Start with a jsp if you are using model1 architecture for your web-tier
B) Start with a controller if you are using model2 for your web-tier
C) Start with a JSP if you are using Model2 with 'JSP Front Strategy'

But isn't it always a JSP post/get that triggers the controller?
Isn't it a mather of abstraction whether you show or don't show the initial JSP.
In Cade's Guide 8-12/8-13 in the sequence diagram they start with the JSP and in the Collaboration diagram they start with the controller.
what do you think?

Another post on this subject:
http://www.coderanch.com/t/152845/java-Architect-SCEA/certification/Omit-JSP-sequence-diagram

Thanks for your response.
regards,J
[ January 25, 2005: Message edited by: Josep Andreas ]
 
Shogo Ito
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for providing your thoughts.
Shogo
 
Deepak Pant
Ranch Hand
Posts: 446
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Josep,

I am also following JSP-->Controller.

The way I have depicted is that I am showing JSP as a stereotype and actual object is a screen.

So Screen SearchXXX (of stereotype JSP) posts a request, which gets routed via FrontController ....

regards,
Deepak
 
John Alden
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is confusing to me. It isn't the JSP that calls the controller but rather the browser. I was thinking of the following:

Browser makes HTTP request to controller; Controller does it's work and forwards the request to JSP; JSP produces HTML and sends HTTP response back to browser.

Browser ---> Controller
Controller ---> JSP
JSP ---> Browser

I know Cade did this differently but he doesn't show forwarding to a JSP to produce the output for the browser.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic