Will Thompson
> > Verzonden: dinsdag 30 oktober 2012 18:20
> > Aan: MarkLogic Developer Discussion
> > Onderwerp: [MarkLogic Dev General] Extending error handling
> >
> > I want to extend the functionality of the existing HTTP error handler,
> but not
> > necessarily replace it. I thought at the very least I could make a
> > copy
> of the
> > existing error handler, add my extensions, and point the App Server
> there, but I
> > can't seem to find the right XQY module. Is the default error handler
> part of the
> > executable, not XQY?
> >
> > -Will
> > ___
> > General mailing list
> > General@developer.marklogic.com
> > http://developer.marklogic.com/mailman/listinfo/general
> ___
> General mailing list
> General@developer.marklogic.com
> http://developer.marklogic.com/mailman/listinfo/general
>
> Hi Mihir,
>
> Try this:
>
> xdmp:tidy( 'MarkLogic is rocking' ,
> xmlns="xdmp:tidy">
>
> true
> )
>
> Regards
> Amit
>
> -- Forwarded message --
> From: Mihir Das
> To: general@developer.marklogic.com
> Cc:
> Date: Wed, 31 Oct 2012 11:22:44 +0800
> Subject: [MarkLogic Dev General] Preserve space in xdmp:tidy
>
> Hi All,
>
> Can anyone tell me how to preserve space after node closure in xdmp:tidy?
>
> e.g:
>
> xdmp:tidy( "MarkLogic i*s rocking" ,
> xmlns="xdmp:tidy">
>
> true
> )
>
> Output:
>
>
> No warnings or errors were found.
>
>
>
>
>
> MarkLogici*s rocking
>
>
> Expected:
>
>
> MarkLogic i*s rocking
>
>
> Thanks in advance!
> Mihir
>
>
>
> -- Forwarded message --
> From: Mihir Das
> To: general@developer.marklogic.com
> Cc:
> Date: Wed, 31 Oct 2012 11:56:19 +0800
> Subject: Re: [MarkLogic Dev General] Preserve space in xdmp:tidy
> To add on this, if we use the string inside tag and option
>
> then will it still validate the document for well-formed and clean XHTML?
>
> Thanks,
> Mihir
>
> On Wed, Oct 31, 2012 at 11:22 AM, Mihir Das wrote:
>
>>
>> Hi All,
>>
>> Can anyone tell me how to preserve space after node closure in xdmp:tidy?
>>
>> e.g:
>>
>> xdmp:tidy( "MarkLogic i*s rocking" ,
>> > xmlns="xdmp:tidy">
>>
>> true
>> )
>>
>> Output:
>>
>>
>> No warnings or errors were found.
>>
>>
>>
>>
>>
>> MarkLogici*s rocking
>>
>>
>> Expected:
>>
>>
>> MarkLogic i*s rocking
>>
>>
>> Thanks in advance!
>> Mihir
>>
>>
>
>
> -- Forwarded message --
> From: Geert Josten
> To: MarkLogic Developer Discussion
> Cc:
> Date: Wed, 31 Oct 2012 07:54:28 +0100
> Subject: Re: [MarkLogic Dev General] Extending error handling
> Hi Will,
>
> There are some other error-handlers that might be worth looking at. Most
> notably the one from Query Console. It's not an isolated error handlers,
> but the eval.xqy endpoint contains some functions that might interest
> you..
>
> Cheers,
> Geert
>
> > -Oorspronkelijk bericht-
> > Van: general-boun...@developer.marklogic.com [mailto:general-
> > boun...@developer.marklogic.com] Namens Will Thompson
> > Verzonden: dinsdag 30 oktober 2012 22:42
> > Aan: MarkLogic Developer Discussion
> > Onderwerp: Re: [MarkLogic Dev General] Extending error handling
> >
> > Thanks Geert. This is ideally what I'd like to do, but there doesn't
> seem to be a
> > way to pass the context of the current exception back to error(). It is
> possible to
> > get the error code, name, and description and then rethrow. In this case
> it will
> > raise the error from the error handler context.
> >
> > Then it's smart enough to print out "Old Error" followed by a
> pretty-printed
> > xdmp:quote() of the $error:error variable. That's partially useful, but
> it's not
> > clear to me how to wire it so that it rethrows using the context of
> $error:error.
> > As it is, it would be very hard to read the error details through sea of
