So much of HiveMind is defined in itself, this is likely to be a problem for tools. For example, the list of valid prefixes is a configuration point (hivemind.ObjectProviders) and Tapestry adds a couple to the default list (infrastructure:, engine-service:). It's wheels within wheels and was not designed for tooling, alas.
On Tue, 29 Mar 2005 14:27:38 -0500, Geoff Longman <[EMAIL PROTECTED]> wrote: > That would be cool! > > I'd like to be able to confirm that a given service id exists: > > <inject property="service-ref" object="service:myModuleId.MyService"/> > > To be complete I would need to confirm the validity user strings > against prefixes contributed to hivemind.ObjectProviders > > and I guess to be really complete if the prefix is "engine-service" > would need to lookup the valid service names registered with > apestry.services.ApplicationServices (is that right?) > > Same kinda stuff would be needed for the <inject-state> ,<set> and > <binding> tags no? > > Geoff > > > On Tue, 29 Mar 2005 13:30:24 -0500, Howard Lewis Ship <[EMAIL PROTECTED]> > wrote: > > Perhaps we could change HiveMind's RegistryBuilder class to have an > > additional method that returns some intermediate object that can be > > queried for this kind of information. > > > > > > On Tue, 29 Mar 2005 13:15:10 -0500, Geoff Longman <[EMAIL PROTECTED]> wrote: > > > > Guess I missed the prior message. Kinda busy! > > > > > > Thanks for answering. Anything you (or anyone) can add will help speed > > > things along! > > > > > > > > > > > > > 1. add Hivemind binding prefix? > > > > > > > > > > What is this? > > > > > > > > There's a whole suite of new prefixes for binding, in addition to > > > > "ognl:" and "message:". And its extensible! > > > > > > > > hivemind: refers to an object defined within HiveMind, for example: > > > > > > > > hivemind:service:tapestry.Infrastructure > > > > > > > > This saves you the trouble of injecting a HiveMind object into a > > > > property and then accessing that property via OGNL. > > > > > > ok, that's what I thought. Whew it takes a lot of drilling around the > > > code to figure out how this all works! > > > > > > I think that bringing Spindle up to date will be a bigger job than > > > usual ;-). Any chance that it is possible now to build a meta hivemind > > > registry? ie. one that doesn't try and instantiate services etc? i.e > > > lightweight. > > > > > > Things that this would be useful for: > > > > > > ask HM does this service id exist? > > > ask HM, for service X, what is expected iface > > > ask HM, what are contributions to point X? > > > > > > The ideal solution would be to model HM as completely as Spindle does > > > now. Would like to do that at some point (opens doors to design time > > > validation and editors for HM!) but I think it would delay my current > > > task too much. > > > > > > > > > > > > > > > > > > > > > 2. add lookup to determine page class from page name. > > > > > > > > > > Am I correct to assume that this feature comes into play only for > > > > > specless pages? > > > > > > > > And for pages that omit the class attribute. > > > > > > ahh I didn't notice that the class attribute was now optional. > > > > > > > -- > > Howard M. Lewis Ship > > Independent J2EE / Open-Source Java Consultant > > Creator, Jakarta Tapestry > > Creator, Jakarta HiveMind > > > > Professional Tapestry training, mentoring, support > > and project work. http://howardlewisship.com > > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
