So what should the JIRA say? At this point I think whats needed is a configuration service. That service gets passed a Mapped configuration that consists of a class and a configuration. It would need one method Map<Class,Object> getConfigurations() where the object would be list, map etc depending on the configuration type. From that I think you could figure out most of what's needed. If would also be nice if ComponentClassResolver would return a list of mixins/components.
On Wed, Oct 2, 2013 at 6:27 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Wed, 02 Oct 2013 04:28:51 -0300, Alessio Gambi <alessioga...@gmail.com> > wrote: > > Some time ago I tried a similar thing but without no luck (see [1]), but >> I think still think that some effort should be invested to fill the >> "Distributed Documentation" gap. >> > > I agree. JIRA please? :) > > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
