Hi, There is an interesting blog entry that talks right about the component you are trying to develop. Just google for Tapestry vs OSGi and you will find it. BTW I did it something like that few time ago and I used regexp.
On 13-set-2010, at 15:20, Everton Agner <ton.ag...@gmail.com> wrote: > Yes, probably I'll use it if I have to implement it from scratch. I just > wanted to know if there was something like that already implemented > > I'll google it for options, maybe there is some API somewhere. If anyone > knows, please tell me. > > Thanks! > > _______________________ > Everton Agner Ramos > > > 2010/9/13 Thiago H. de Paula Figueiredo <thiag...@gmail.com> > >> On Mon, 13 Sep 2010 09:19:18 -0300, Everton Agner <ton.ag...@gmail.com> >> wrote: >> >> I'm developing an auto menu builder, which retrives all the pages from the >>> ComponentSource service. But since core pages are included on it (like >>> /core/servicestatus or something like that), I've created another service >>> for IgnoredPaths, and I wanna configure paths as Patterns, like "core/*". >>> I should be OK if i had something like what Ant does for paths and >>> wildcard,that could match patterns like "core/*" and some improved paths >>> like >>> "**/users/*". >>> >> >> Tapestry has nothing like that. Have you thought about using regular >> expressions? >> >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, >> and instructor >> Owner, Ars Machina Tecnologia da Informação Ltda. >> http://www.arsmachina.com.br >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
