David,
We've been wanting to add a generic exception mechanism in XPL for a long time, but currently, there is no such support. I just added an RFE:
http://sourceforge.net/tracker/index.php?func=detail&aid=1060344&group_id=116683&atid=675663
The solutions I see are:
1. Implement the exception mechanism in XPL (not trivial ;-) 2. Modify the email processor to have a "continue on failure" option 3. Write a processor that manually call your pipeline (using the pipeline API) and catches the exceptions it may throw
Any other ideas?
BTW the XPL exception mechanism would look like:
<p:exception>
<p:try>
<p:processor name="oxf:url-generator">
<p:input name="config">
<config>
<url>http://example.org/feed.rss</url>
</config>
</p:input>
<p:output name="data" id="feed"/>
</p:processor>
</p:try>
<p:catch type="java.lang.Exception">
<p:processor name="oxf:identity">
<p:input name="data">
<error>
An exception was caught!
</error>
</p:input>
<p:output name="data" id="feed"/>
</p:processor>
</p:catch>
<p:catch>
...
</p:catch>
</p:exception>BPEL has a similar faulthandlers / catch / catchAll construct that we could look at as well.
-Erik
David Sinclair wrote:
Our application has a queue of emails to be sent out, with a scheduled pipeline that periodically takes items from the queue and sends them. If one mail fails, we want to continue on and send the remaining messages, leaving the unsent mails in the queue. However, the email processor throws an exception ending the pipeline execution....is there a way to make them fail independently?
FYI, we are using the email processor within an xpl for-each.
David Sinclair.
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
