Antonio Petrelli wrote:
Hi all! I noticed that there are two files named "TilesDecorationFilter", one in tiles-core and another in tiles-api. Since the one used in tiles-test is the tiles-api's, I suppose I can remove tiles-core's file (or not?).
Yes, that seems right (not in front of the code right now). THe correct one is org.apache.tiles.web.TilesDecorationFilter which I think is in api. At one point I was grappling with where to put it so I must have not removed an old version. One should look more robust than the other.
Either way, we need to remove the old one.
Supposing that we stick with tiles-api's TilesDecorationFilter, why is it in tiles-api? Isn't it a core class and not an API class? I am asking this because I don't want to remove by mistake any file.
Good question. I'm not convinced I have a handle on what we expect in our API. Are these JUST the for formal api's or does it also include anything that's not implementation specific. If it's the former, than they are not very usefull standalone since there are no entry points. . .I was thinking that the api is the public interface which our typical user will interact with. As such, I would think that we need to eventually find a way to move our bootstrap listeners, filters, etc. . to the api module.
Thanks Antonio
