An OSS/J Session Facade Artifact models an integration point for a Service Contract. Through this facade, operations on Managed Entities are exposed, Queries and UpdateProcedure are accessible. Also, this is the logical source of emitted notifications. Defining Session Facades is typically the final step in assembling a Service Contract, where information model and the capabilities of the Service Contract are selected.
Standard Modeling Details
- Package: a valid package name.
- Name: a unique name for this Session Facade within the scope defined by the package.
- Super-Artifact (optional): the fully qualified name of the Session Facade being extended by this Session Facade definition. This is optional.
Artifact Specific Modeling Details
- Session Facade Methods: Session Facade methods represent additional methods (ie. on top of all methods exposed as a result of Managed Entity operations, queries and update procedures) available for ad'hoc functionalities.
Standard Generation Details
- Interface Package: the name of the package where the corresponding Java Interfaces shall be generated. If a default interface package has been set for the project, this value will be used by default.
Artifact Specific Generation details
- Managed Entities: the list of Managed Entity Artifacts that are specifically managed through this session facade. By selecting these entities to be managed, one implicitly define the stewardship of this entities. Operations defined on the selected entities will be exposed through the facade.
- Named Queries: the list of named queries that are offered through this Session Facade. The result of all these queries needs to be within the set of Managed Entities as managed by this facade.
- Update Procedures: the list of Update Procedures offered through this Session Facade.
- Emitted Notifications: the list of notifications that may be emitted through this facade (acting as the logical integration point).
As a result of defining a Session Facade in a Tigerstripe Model, the following is generated:
- J2EE Integration Profile: the Java interfaces corresponding to a Session Bean for that facade. All methods on the facade will appear on the session bean.
- JMS/XML Integration Profile: all messages (request, response and exception) required to implement all the methods of the session facade as well as access to queries and update procedures.
- Web Service Integration Profile: a Web Service definition corresponding to the Session Facade. For every Session Facade definition, a WSDL file is created.
© copyright 2005, 2006, 2007 Cisco Systems, Inc. - All rights reserved