Hi Eric
I wished for JDBC as a transport to the effect of being able to write/read
from a database, and poll the database
for a change in some table and provide some notification .If the 2 mediators
you mentioned are capable of doing that
then that would be great.
Currently you cannot 'poll' a table with the mediators.. the problem or
difficulty in writing JDBC as a "transport" is that how you would
convert a row (or the result of a query which may be a join for example)
into a "message". If we are to write this as a generic transport I
believe different users may want to transform a row via multiple ways.
It is too late to incorporate this into 1.1 as a transport anyway, but
if you require this functionality, I could point you to Data Services -
these are services that essentially transform JDBC queries into a
service you can then invoke (see http://wso2.org/library/2617,
http://wso2.org/library/2631) Couple this with the new "Job" support
that Synapse now offers for scheduling tasks, and I believe you will be
able to build this same functionality for your requirements!
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
