On 20/05/2015 11:13, Gerhard Petracek wrote:
hi ludovic,inheriting folder names that way would break other use-cases and it's also against the overall concept (+ it can lead to more complex path-configs easily as well as to potential clashes in case of multiple interfaces which contain meta-data for the path-name,...). i just used that annotation for the discussion (to be sure that we are talking about the same). we could extend @ViewConfigRoot to support e.g.: @ViewConfigRoot(virtual = true) public interface Pages extends PagesCommon { //... } for sure that would only work for the root-node. however, all options i've seen so far are more complex than just using @Folder(name="/") (or they would break other use-cases).
You get the idea. I think too that it should be usable for any folder. I will gladly test a new feature if you come to implement it. ;-) Ludovic | | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT. |
