Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring 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 ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Component Diagram question

Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do we need to show any depedency between Queue/Topic and Message driven bean. If yes what kind of link is used between two components
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In my diagrams queues/topics are artifacts. MDB, and message senders depends from this artifact. But I'm not sure if this is the proper way
author and cow tipper
Posts: 5000
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's important to know why you are using a queue or a topic in an application.

Microsoft probably has the best message queues out there. Here's a little description of why they suggest you use them.

Microsoft Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. MSMQ provides guaranteed message delivery, efficient routing, security, and priority-based messaging. It can be used to implement solutions for both asynchronous and synchronous messaging scenarios.

So, if an assignment has those types of requirements, where you're communicating across heterogeneious networks and systems that might be temporarily offline, well, then message queues are an ideal resource.

Queues are also great for delayed, yet transactionally reliable, messaging. IMHO, many architectures could benefit from having a queue, and delaying transactional processing until more clock cycles are available.

The Service Activator uses JMS as an example. There is a great class diagram, along with a sequence diagram that shows you the pattern. That might be enough to get you kick started if you're confident that a message queue that delays processing and connects heterogeneous environments is the right solution for your problem domain. SuD

Design Patterns - Service Activator - Using JMS in a Class & Sequence Diagram

Good luck!

-Cameron McKenzie
Remember to always leap before you look. But always take the time to smell the tiny ads:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic