DB Adapter Polling

Question

Most times our bpel processes cannot update a database table (logically or otherwise) immediately after it is polled,rather it may have to deferred after until a few business
validations are done and depending on whether these were successful or not we would like to carry out a logical delete accordingly..
During setup of an adapter once the polling frequency is chosen,we are forced
to choose one of the following operations:
1.delete the rows that were read
2.update a field in the <polled> table(logical delete)
3.update a sequencing table.
Given my scenario I would'nt want to carry out any of these until later after all my business validations have been executed successfully.
Is there a way out ?
thanks

Answer 1

Hi -
Did a "NoAfterReadPollingStrategy" ever get implemented? I am doing DB polling and I don't want to do anything after the DB read.
I am running BPEL 10.1.2.0.2, and didn't see any options when creating a database partner link to do nothing after reading from the DB.
Also, I tried to write my own polling strategy, but kept getting an error because Jdev can't find the oracle.tip.adapter.db.inbound.DeletePollingStrategy to extend. I know I am probably just missing a JAR file somewhere...Does anyone have any ideas?
Thanks in advance.
Hi there,
for the next release we implemented a
ed a NoAfterReadPollingStrategy.
The polling strategies are pluggable though, so
, so until then you could write your own.
Try compiling this java class and putting it in
integration/orabpel/system/classes
package mycustompollingstrategy;
public class NoAfterReadPollingStrategy extends
oracle.tip.adapter.db.inbound.DeletePollingStrategy
public void destroy(Object object,
, oracle.toplink.sessions.Session topLinkSession) {
return;
In your wsdl change PollingStrategyName from
PollingStrategyName="DeletePollingStrategy"
to
PollingStrategyName="mycustompollingstrategy.NoAfterR
eadPollingStrategy
That should work.
Another way is to use the sequencing polling
strategy, which does not effect the source rows, and
then invoke a stored procedure later to clean up the
source rows based on the last_read_id in the
sequencing helper table.
Thanks
Steve