I think John was suggesting an XQuery try-catch expression, not a Java one.

But you are more likely to get helpful suggestions if you post a full example 
of the exception you are trying to avoid. Corb throws some fatal exceptions of 
its own, when it cannot reasonably continue. It also re-throws various 
MarkLogic and XQuery exceptions. Seeing the exception that you are hitting 
would help.

-- Mike

On 28 Nov 2011, at 07:11 , sachin gill wrote:

> HI John,
>        thanx for the suggestion but I'm using CORB jar (so that if any 
> version version upgrade happen we don;t need to do lot of customisation) 
> rather than its code , so can't handle it inside CORB code .
> 
> Thanks
> Sachin
> 
> On Mon, Nov 28, 2011 at 6:50 PM, John Zhong <[email protected]> wrote:
> First idea is that you can use try/catch. For example:
> 
> try {
>    (: your business code here :)
> } catch($e) {
>    (: your code to handle exception :)
> }
> 
> John
> 
> On Mon, Nov 28, 2011 at 6:41 PM, sachin gill <[email protected]> wrote:
> Hi ,
>    We are  facing bulk processing issue with CORB .We are using it to process 
> a large set of  XML's , it works fine till it doesn't get any issues or 
> exception.Once it finds any exception it stops,And we need to start from 
> scratch again.
> 
> How can i ignore such exception while processing and continue for other xmls .
> 
> Thanks
> Sachin  
> 
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
> 
> 
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
> 
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general

_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to