[jira] Closed: (TUSCANY-2347) Removing the exception throws from the processors

["Ramkumar Ramalingam (JIRA)" <de...@tuscany.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramkumar Ramalingam closed TUSCANY-2347.
----------------------------------------


> Removing the exception throws from the processors
> -------------------------------------------------
>
>                 Key: TUSCANY-2347
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2347
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-Next
>         Environment: Windows XP,
>            Reporter: Ramkumar Ramalingam
>            Assignee: Simon Laws
>             Fix For: Java-SCA-Next
>
>         Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5-NEW.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6-NEW.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7-NEW.patch, TUSCANY-2347-Part7.patch, TUSCANY-2347-Part8.patch, TUSCANY-2347-Part9.patch
>
>
> After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like
> a) IOException
> b) XMLStreamException
> c) PriviledegedActionException
> d) and ParseConfigurationExceptions
> As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.