You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by ta...@jakarta.apache.org on 2004/03/12 15:23:02 UTC

[Jakarta Tapestry Wiki] Updated: HiveMind

   Date: 2004-03-12T06:23:01
   Editor: 66.11.174.240 <>
   Wiki: Jakarta Tapestry Wiki
   Page: HiveMind
   URL: http://wiki.apache.org/jakarta-tapestry/HiveMind

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -4,3 +4,22 @@
 It will be used as part of ["Tapestry31"] to form the infrastructure of Tapestry. Some aspects of the Tapestry DTD will be deprecated, such as <service> and <extension>. Tapestry will define extension points to accomplish the same thing.
 
 In addition, new elements, such as <service-binding> will be added, to easily connect HiveMind services to component parameters.
+
+----
+
+About the new elements. Is a new binding type needed? I mean, you just need a handle to the service to bind it.
+
+I'm thinking a variation of <property-specification> would be nice..
+
+{{{<service-property name="boo" service-id="my.module.MyService" interface="com.x.y.MyService"/>}}}
+
+Would be cool if the class enhancement worked for this as it does for <property-specification>
+
+i.e.
+{{{
+public abstract MyPage extends BasePage {
+  abstract MyService getBoo();
+}
+}}}
+
+GeoffLongman

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org