+1. I'll do the Python extension.
On 9/20/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
That's exactly what I intended when moving the SCARuntimeException to the
CPP extension. I think we need a really good trawl of exception throwing
handling so this is a great time to do it.
I'll take a look at the core runtime and cpp extension.
Cheers,
On 20/09/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> The SCA spec for C++ defines some SCA exceptions for use in an SCA C++
> client or C++ component implementation. These exceptions are currently
> distributed with our CPP extension, but there are a number of places in
> our runtime code (core runtime and other extensions) where we currently
> still use these exceptions (for historical reasons), forcing us to
> duplicate some of the osoa/sca includes into these extensions, or just
> throw "char *" exceptions in some places in lack of a better Tuscany
> exception.
>
> How about we clean this up a little :) and do the following:
> - Declare Tuscany core runtime exceptions (probably similar to the ones
> we now have under osoa/sca).
> - Have extensions use them or extend them.
> - In the CPP extension, catch these exceptions and translate them to the
> SCA for C++ specific ones.
> - Review all places where we throw / catch exceptions and either handle
> them correctly or place a //TODO in the code as a reminder.
>
> I volunteer to do that cleanup work in the Ruby and WS extensions.
> Thoughts? Any other volunteers?
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
