jmesa tag library or API

[ashish]

Hi,

I'm using JMESA quite extensively in my application and is quite fan
of this API. I have one very quick question.
What should be my choice between using JMESA tag library to using
JMESA java API's.

Can I have the list of features which are supported through api's and
the support is not there in tag library.
something related to performance or anything.

I'm in a discussion wherein I need to have proper arguments for or
against any one of these approaches.

Thanks,
Ashish

[Jeff Johnston]

Glad to hear that JMesa is working out for you!

The tag library is a very thin wrapper over the API, so not only are
they essentially the same...they really are the same. So the only
"feature" that cannot be used with the tag library is using AJAX. If
you want to avoid the whole page refresh then you have to use the API.
This is not a limitation of JMesa, but of using tags in general.

In our applications we use both actually. We use the tags for the
convenience and because a page refresh is fine in one part of the
application, but then use the API directly in a different part in
which using AJAX is a better experience.

As a side note I still plan on working on a builder for the API. I
like the way the API is structured right now, but I think using the
builder (with fluent methods) pattern to create the table would be
real nice and it would make the Tag library and API feel more the same
too. Nothing about the API will change either, and would just be an
optional way to work. I envision that the builder would either accept
the TableFacade, or the builder would get set back on the TableFacade.

-Jeff Johnston