Geek Answers Handbook

Pros and Cons of Apache Tiles Structure

Greetings for this day, I was just trying to figure out the pros and cons of using Apache Tiles . Please let me know your valuable suggestions, comments, materials regarding the same.

+6
source share
3 answers

(similar to this )

With Tiles, it seems that when I have 100 actions, I need to create 100 jsp files and create 100 definitions in tiles.xml - true, unfortunately

This is not true. And a common lingering misconception about tiles.

This pattern configuration is tile dependent - 1 day. This is not really necessary for tiles-2 when wildcards were introduced, and especially with tiles-3 along with OptionRenderer.

Here is a tutorial to help you with

  • spring for plate integration,
  • with wildcards,
  • implementing a fallback template using OptionsRenderer and
  • .
+7
source

I use Apache Tiles for a nonprofit project, and I become less enthusiastic with it every week. But this can be caused by very simple documentation, too few examples (and examples on advanced topics), and a rather small community.

In addition, I would recommend you look at these resources:

To summarize - the benefits :

  • ability to create composite representations from basic representations, reuse of UI
  • this has been around for some time, and it has been supported in some major environments such as Spring (easy to start with)

limitations

  • small community, not very active IMHO
  • basic documents, a few examples, it is difficult to find valuable modern resources on the Internet - you will be forced to dive deep into Java interfaces and classes to find which apache tiles provide
  • composite view instead of decorator - in my personal opinion, the decorator template is more flexible - you can define variables, slots, attributes, etc. at the very end of query processing, while in a composite view you need to focus on when you define an attribute (all attributes of a subtask must be defined before it is visualized - redefining attributes is more difficult).
+5
source

I have been working with tiles for a long time, and I must say, as soon as you enter it, and you know all the features that you will like. At first it looked so complicated and cumbersome, and you spend a lot of time searching the Internet. But after that you will use a lot of great features that you won’t find in other frameworks or concepts, such as template inheritance, redefinition, flexible composition, wildcard matching, presentation compilers, etc. .... And it works very well with Spring On the other hand, the only function that I have missed so far is the impossibility of directly defining the parent template (which actually violates the concept of Tiles).

+1
source

More articles:


All Articles