G> In my experience, Java Engineers invest too much time in theoretical
G> benefits instead of practical ones which needlessly complicates their
G> design and wastes time that is better used elsewhere. For example,
G> I've seen many people using the same reasoning to separate interface
G> from concrete class even when there was only one implementation and
G> no possibility of 3rd-party implementations.
G> In any case, I don't think you need a MVC framework to do what you're
G> talking about. Here is what I do:
[...]
>>>>> On Thu, 5 Jun 2014 11:28:37 +0200, Miroslav Fuksa <miroslav.fuksa_at_oracle.com> said:
MF> thanks for the explanation. I understand your point with flexibility
MF> of your solution. I only see a problem when your html document would
MF> have too many fields then your html mutator code would be less
MF> readable and maintainable then if you would used any templating
MF> engine. But I do not know all your code, so please do not take this
MF> as criticism. And of course I am not selling" our MVC support now
MF> ... I was just curios :-)
Gili,
In your experience, do you find the absence of a CDI backed EL that you
can put in your HTML pages is not a problem? How do you handle I18N?
These are two areas where a more tightly integrated template system
would be helpful.
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| 17 business days til Santa Clara trip