• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

JMS communication details in Sequence diagram

 
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I need to communicate with an external system using JMS.
Now, since my intention is to use EJB3 and have all the JMS objects (the ConnectionFactory and the Queue) injected via annotations by the EJB container, what level of details should I give to the sequence diagram?

I was thinking just to have a method in my EJB from which to create a self-call to depict the QueueSender creation and then just to call the remote Queue using a send method.
Is this acceptable or it doesn't make any sense? Should I depict QueueSender actual creation by adding the objects to the diagram?

To explain me better I add the diagram removing any other specific information to my case

Any help will be great as I'm stuck for two days on this not being able to decide which way to go.

Claudiu
SequenceDiagram.jpg
[Thumbnail for SequenceDiagram.jpg]
SequenceDiagram for JMS interaction
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am in a similar quandary. I've decided not to show the QCF and QueueSession interfaces in my sequence diagram as it is common knowledge and depicts a standard way of implementing JMS requirements.

What did you go with?

Claudiu Dumitrescu wrote:Hi,

I need to communicate with an external system using JMS.
Now, since my intention is to use EJB3 and have all the JMS objects (the ConnectionFactory and the Queue) injected via annotations by the EJB container, what level of details should I give to the sequence diagram?

I was thinking just to have a method in my EJB from which to create a self-call to depict the QueueSender creation and then just to call the remote Queue using a send method.
Is this acceptable or it doesn't make any sense? Should I depict QueueSender actual creation by adding the objects to the diagram?

To explain me better I add the diagram removing any other specific information to my case

Any help will be great as I'm stuck for two days on this not being able to decide which way to go.

Claudiu

 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I agree with Jesson that JMS connection creation details is unnecessary to be included in the sequence diagram.
 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I fully agree. Step 2 is implementation detail, with does not provide any valuable information from architectural point of view.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic