there is already jdbc pallet , why do we need adb adapter?

Pros and cons of JDBC and ADB Adapter:

1) JDBC activity Supports Transaction (available in GROUPING)
whereas ADB doesn't support it.
2) Using JDBC activities you can invoke a procedure/function,
dynamically construct queries using these activities.
3) Schema should be equal to the table structure in ADB,
otherwise you can’t handle a table.
You need not to define a schema while using JDBC activities.
4) In ADB whenever there is a table structure/field change this
will reflected easily by clicking on
refresh button
5) In ADB you can map to the particular table. Once it is mapped
you have to point to another table by using another ADB
activity, where as in JDBC you can easily point to any database
table (select * from ). Need not to configure prior
to the execution.
6) In ADB you have supporting table so that you can easily get
the status of the message to be published or not.
7) For high load/performance use ADB Adapter.