You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Ford, Mark" <ma...@ll.mit.edu> on 2009/08/12 21:49:30 UTC
Question on compiler messages
I noticed that XQuery10ExpressionCompilerImpl.doJaxpCompile does not throw a CompilationException if a XQException is caught during compilation. Does anyone recall why?
The result is that compile errors will appear on the console output which is great for command line users but there's nothing reported to a CompileListener if the compilation was triggered through BpelC.
--
Mark Ford
MIT Lincoln Laboratory
244 Wood Street
Lexington MA 02420
(781) 981-1843
Re: Question on compiler messages
Posted by Karthick Sankarachary <sa...@intalio.com>.
Just FYI, the patch has been checked in at SVN revision 803698.
On 8/12/09, Karthick Sankarachary <sa...@intalio.com> wrote:
>
> That was probably just an oversight. I'll make it throw a compilation
> exception, as that is the expected behavior.
>
> On 8/12/09, Ford, Mark <ma...@ll.mit.edu> wrote:
>>
>> I noticed that XQuery10ExpressionCompilerImpl.doJaxpCompile does not throw
>> a CompilationException if a XQException is caught during compilation. Does
>> anyone recall why?
>>
>> The result is that compile errors will appear on the console output which
>> is great for command line users but there's nothing reported to a
>> CompileListener if the compilation was triggered through BpelC.
>>
>>
>>
>> --
>> Mark Ford
>> MIT Lincoln Laboratory
>> 244 Wood Street
>> Lexington MA 02420
>> (781) 981-1843
>>
>
>
>
> --
> Best Regards,
> Karthick Sankarachary
--
Best Regards,
Karthick Sankarachary
Re: Question on compiler messages
Posted by Karthick Sankarachary <sa...@intalio.com>.
That was probably just an oversight. I'll make it throw a compilation
exception, as that is the expected behavior.
On 8/12/09, Ford, Mark <ma...@ll.mit.edu> wrote:
>
> I noticed that XQuery10ExpressionCompilerImpl.doJaxpCompile does not throw
> a CompilationException if a XQException is caught during compilation. Does
> anyone recall why?
>
> The result is that compile errors will appear on the console output which
> is great for command line users but there's nothing reported to a
> CompileListener if the compilation was triggered through BpelC.
>
>
>
> --
> Mark Ford
> MIT Lincoln Laboratory
> 244 Wood Street
> Lexington MA 02420
> (781) 981-1843
>
--
Best Regards,
Karthick Sankarachary