• Post Reply Bookmark Topic Watch Topic
  • New Topic

JMS on component diagram

 
Dawid Augustynowicz
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm confused how to show JMS messanging on my diagrams. I'm using UML2. First I thought to show queue/topic as artifact and sender and reciever as components dependent on this JMS archetype. Another idea I had is to show Message as interface and reciever of this message as assembly connector, but then it is not visible if it is topic or queue communication. I also had idea to show this topic/queue as separate component with interfaces for example Publish, Subscribe. What is the best way to model JMS communication? Maybe should I show on deployment diagram instead of component diagram?
 
Khaled Mahmoud
Ranch Hand
Posts: 361
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I support the first idea which is using an artifact to represent the
message queue. I think it seems more understandable on the component diagram than the second approach.
[ December 09, 2007: Message edited by: Khaled Mahmoud ]
 
Dawid Augustynowicz
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is this the best way to document JMS messaging in my project? (and it is UML compilant?):

 
Gravity is a harsh mistress. But this tiny ad is pretty easy to deal with:
the new thread boost feature: great for the advertiser and smooth for the coderanch user
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!