I am approving this message, but I must point out that you are more likely to
motivate a constructive response to your query if you sign it with a name!
Gervas
Moderator
Since services normally provide coarse grained interface, i was
wondering how to design one in following scenario:-
1. A vehicle insurance form. Form 1 collects vehicle info. Form 2 is
generated dynamically based on input from Form 1 and Form 2 collects
customer info. Form 3 is generated dynamically based on input from
Form 1 and Form 2 and collects certain disclosure information. After
Form3 submission, the data collected from user in Form1,2&3 is
persisted as one transaction. The rules to wether information
collected on Form 1 is valid lies within the service. Similarly the
customized information (based on Form 1 response) that needs to be
collected from user in Form2 is again in business component. The
reason lies in the fact that the component act as autonomous
component for collecting and providing insurance information. If the
rules related to insurance changes, this one component can reflect
those changes. Also the component would be reused by different
components within the organization.
My dilema is
How do i organize the interface ?
Since this is interactive application , there is a UI layer which
interacts with "insurance component". Another constraint on the
architecture is that the form data should be validated at each step.
Should the service interface look like
1. Validate Form 1 information
2. Get Form 2 display questions by accepting Form 1 information
3. Validate Form 2 information
4. Get Form 3 display questions by accepting Form 1 and 2 information
5. Validate Form 3 information
6. Save transaction
This interface not only gets tied to UI, but also seems to fine
grained considering all the interactions between UI and component
are going through regular SOAP and XML. Tommorow, lets say i want
to consolidate all 3 forms into one large form and i introduce ajax
into the ui mix where client (browser) dom structure is continously
updated based on choices made by end user, this interface would
change.
How do i design a coarse grained interface which does not depend on
UI?
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
