The problem with this approach is that it doesn't address any other page packages that may have been added via other modules (in the same manner that additional component packages can be added). The idea of copying what ComponentClassResolverImpl does would be the 'correct' method, and an extension to the API was request some time ago to expose this as a legitimate feature. See: https://issues.apache.org/jira/browse/TAPESTRY-1923. There's a patch included that extends the interface as well as implements it. Hopefully this will make it in...
chris Marcus wrote: > Hi Angelo, > > - get ContextClassLoader from current Thread > - get path of your pages package (org.exemplo.teste.pages) from ClassLoader > - get files on this path that ends with ".class", skiping inner classes. > > I think this topic already has been discussed here. > > Marcus. > > -- http://thegodcode.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
