Forums Register Login

Sequence Diagram and WebService

+Pie Number of slices to send: Send
Hi Friends,
I need to invoke a web service from a DAO i.e. SessionBean -> DAODactory->DAO->?

Can you guide how to represent this invocation in my sequence diagram and how will I represent the web service object in the diagram e.g. Proxy.

Also, as DAO needs the endpoint URL of the webservice, What is the best way to lookup the URL instead of hardcoding it. I reckon I can't use @WSReference annotation here as DAO is not container managed.

Thanks
Amit
+Pie Number of slices to send: Send
 

Kumar Amit wrote:Hi Friends,
I need to invoke a web service from a DAO i.e. SessionBean -> DAODactory->DAO->?

Can you guide how to represent this invocation in my sequence diagram and how will I represent the web service object in the diagram e.g. Proxy.

Also, as DAO needs the endpoint URL of the webservice, What is the best way to lookup the URL instead of hardcoding it. I reckon I can't use @WSReference annotation here as DAO is not container managed.

Thanks
Amit



URL needs to be looked up from JNDI tree.
Proxy is just like DAO or facade so show that just like other objects. You can show some info stereo type.
I have put one simple synchronous call from DAO to XYZ system(external system). Not sure, if that's the most right way of doing it but I have a feeling that we are showing more than required. We are supposed to produce high level sequence diagrams, not method parameter level just my pov...
+Pie Number of slices to send: Send
What about showing service locator pattern here to lookup for endpoint from JNDI?
Also, how are you showing XYZ system(external system) in the sequence diagram? Is like another other class with a name "XYZSystem"
I reckon we should show a class representing stubs generated using WSDL?
Other members can you please comment whats the best way to show this invocation?
+Pie Number of slices to send: Send
You can add UML notes, I did that.
+Pie Number of slices to send: Send
I think you can simply mention DAO are accessed via Factory pattern in your notes. In sequence /class diagram it's not necessary to show how. Lookup or annotation is how - keep that out of class / sequence diagram. My suggestion.
+Pie Number of slices to send: Send
You can use service locator pattern to do a lookup for SEI from JNDI. Otherwise there is no harm reading it from the properties file.
External system you can show as an entity(with some different color) on the sequence diagram and provide UML notes(dog eared boxes) regarding your convention.
You save more money with a clothesline than dozens of light bulb purchases. Tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 2105 times.
Similar Threads
sequence diagram using a Business Delegate
A question about UML - sequence diagrams
UML representation when hiererachy objects are involved
Dependecy injection EJB3
Sequence Diagram in StartUML
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 19, 2024 01:21:58.