Differences between revisions 14 and 15
Revision 14 as of 2006-01-21 17:24:13
Size: 1034
Editor: DonBrown
Comment:
Revision 15 as of 2009-09-20 23:12:18
Size: 1042
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
Both the Jericho and Shale proposals mention the need for a Context notion to work (perhaps in combination with a Chain of Responsibility). I would like to point out that the [http://morph.sourceforge.net Morph] framework provides [http://morph.sourceforge.net/apidocs/net/sf/morph/context/Context.html such an abstraction] that is ideal for abstracting out the details of different APIs (HTTP, Porlet, etc). For example, the [http://morph.sourceforge.net/apidocs/net/sf/morph/context/contexts/HttpServletContext.html HttpServletContext] abstracts out the details of interacting with the Servlet API so that you need only depend on either the [http://morph.sourceforge.net/apidocs/net/sf/morph/context/Context.html Context] interface or the java.util.Map interface. Both the Jericho and Shale proposals mention the need for a Context notion to work (perhaps in combination with a Chain of Responsibility). I would like to point out that the [[http://morph.sourceforge.net|Morph]] framework provides [[http://morph.sourceforge.net/apidocs/net/sf/morph/context/Context.html|such an abstraction]] that is ideal for abstracting out the details of different APIs (HTTP, Porlet, etc). For example, the [[http://morph.sourceforge.net/apidocs/net/sf/morph/context/contexts/HttpServletContext.html|HttpServletContext]] abstracts out the details of interacting with the Servlet API so that you need only depend on either the [[http://morph.sourceforge.net/apidocs/net/sf/morph/context/Context.html|Context]] interface or the java.util.Map interface.

Both the Jericho and Shale proposals mention the need for a Context notion to work (perhaps in combination with a Chain of Responsibility). I would like to point out that the Morph framework provides such an abstraction that is ideal for abstracting out the details of different APIs (HTTP, Porlet, etc). For example, the HttpServletContext abstracts out the details of interacting with the Servlet API so that you need only depend on either the Context interface or the java.util.Map interface.

{{{ * StrutsUseCases

StrutsWhiteboard (last edited 2009-09-20 23:12:18 by localhost)