On 12-04-29 04:21 PM, Mick Semb Wever wrote:
- moved the ViewPreparer interface into tiles-api (needed there) and
renamed the old package to avoid conflicts
Why did ViewPreparer need to be moved to api?
( maybe i missed or forgot a previous discussion? )
~mck
No, I don't think we discussed it. My understanding is the following:
When a user needs to write Java code, he should only depend on
tiles-api, not tiles-core. It's more stable, and by doing so, he has
less of our code to understand.
So when does a user needs Java code?
- writing a servlet/portlet/... to call TilesContainer: the package
org.apache.tiles.*
- locating the TilesContainer in tiles official modules:
org.apache.tiles.access.*
- registering dynamic definitions:
org.apache.tiles.mgmt.MutableTilesContainer
- and most importantly, writing definitions, including ViewPreparers.
IMHO you should not have to depend on the whole tiles-core if you just
want to write a library of preparers.
I've also considered deprecating ViewPreparer, but we need an
alternative before we can do that. Possibly some kind of per-definition
RendererWrapper... but implementing this means a lot of changes in
tiles' internal structure.
Nick.
