Use Cases
Assumptions
  • Catalog system has a web GUI
  • Clean separation between GUI and business logic
  • Other (non GUI) systems need to access the business logic
For simplicity's sake, we have a shallow object hierarchy. We're contriving simplicity and avoiding a terribly complex class hierarchy and object compositions so we can stay focused on the SOAP services.

The latter use case will be fulfilled with our web services interface.

Slide 38 of 58 Contents
  1 |   2 |   3 |   4 |   5 |   6 |   7 |   8 |   9 | 10
11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20
21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30
31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40
41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50
51 | 52 | 53 | 54 | 55 | 56 | 57 | 58
www.arachna.com > Educational Resources > Tutorials > O'Reilly Open Source Conference (2002) > Exchanging Objects and Messages With SOAP

spidaman
© 2002-2009 Ian Kallen | Copyright Notice