peru cheppanu wrote:
Thanks for replying me.
The basic idea is knowing the need for tag libraries.. for which the
explanation was given as reusability.
In my opinion, the purpose of tags, besides reusability (after all,
plain objects and methods are reusable and easier to implement), is
Thanks for replying me.
The basic idea is knowing the need for tag libraries.. for which the
explanation was given as reusability.
Now, coming to specific example I have given:
I agree that it should not be a part of logic: library. But, I think one such
tag (substring) is useful in
On 8/30/05, peru cheppanu [EMAIL PROTECTED] wrote:
Thanks for replying me.
The basic idea is knowing the need for tag libraries.. for which the
explanation was given as reusability.
Now, coming to specific example I have given:
I agree that it should not be a part of logic: library.
Thanks a lot Craig. That cleared up a lot.
For the rest of 1%, I better put my question straight to the case.
I want to display two properties on 40*10 cell table. I have these options.
1. use a hashmap that contains 400 values. Or have four with 100 each so that I
can have identical keys.
On Tue, 2005-08-30 at 13:06 -0700, peru cheppanu wrote:
Thanks a lot Craig. That cleared up a lot.
For the rest of 1%, I better put my question straight to the case.
I want to display two properties on 40*10 cell table. I have these options.
1. use a hashmap that contains 400 values. Or
Thanks
[EMAIL PROTECTED] wrote:
On Tue, 2005-08-30 at 13:06 -0700, peru cheppanu wrote:
Thanks a lot Craig. That cleared up a lot.
For the rest of 1%, I better put my question straight to the case.
I want to display two properties on 40*10 cell table. I have these options.
1. use a
The tag library allows reuse whereas scriptlets lead to copy/paste
oriented programming ;-). Separation of concerns is one of the main
principles of OOAD. It allows you to change the logic and presentation
layer objects independent of each other. It is easier to develop,
maintain and extend a
For the most part you are correct. However, it is a little more straight forward than that.
Logic should be wrappered in a logic object. The Tag Library can bridge the presentation to this generic logic. This is so that the generic logic can be used universally from either a presentation
Although the previous two answers are basically correct, I don't think
they really contain the response to Peru's initial question. I hope that
the elders of this list will clarify things a bit for him. :-)
I considered that I'd better avoid responding myself to this, as one
that sometime ago
9 matches
Mail list logo
