You have given the link for Receiver JDBC adapter,not for sender JDBC,do you mind telling us how will the select and update query look like in case of dynamic sender JDBC
The poster did not specify whether this was sender or receiver channel, but it would only make sense that a "dynamic query" must be on the receiver communication channel since if it was on the sender channel, the channel would have to intelligently determine how to do dynamic queries.
Also, the poster asked if there was a way to "send a dynamic query" to the channel. This seems to imply that the channel is receiving information from somewhere to determine the query, which could only mean it is a receiver channel.
If you would like more information on the JDBC sender communication channel, please open a new thread.
"<i>The poster did not specify whether this was sender or receiver channel, but it would only make sense that a "dynamic query" must be on the receiver communication channel since if it was on the sender channel, the channel would have to intelligently determine how to do dynamic queries.</i>"
Please have a look at the tope of the page.Moreover Aamir didn't asked for JDBC sender comm.channel information, we all are interested to know how we can use Dynamic query from sender side, thats it!!!
infact he did specify ,please have a look at his second response
<i>Lets say I want to pull data from a database for a particular month every 15th of month. then everything in my JDBC adapter will remain the same but only month will change in the select statement?</i>
This definitely is sender JDBC coz he is puling from Database
Lets say I want to pull data from a database for a particular month every 15th of month. then everything in my JDBC adapter will remain the same but only month will change in the select statement?
This can be done in a synchronous receiver JDBC communication channel where the request message will have the query (in an XML format) and the response will contain the result of the query.
Have a look at the link below which details the structure of the request message. Specifically look at the comments at the end "action=select"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.