Ramkumar,
Is this such a wise move??
What is the point of allowing processing to continue if the model is actually
broken in some way?
I would agree that there may be some exceptions that can be removed and replaced by the logging of
messages, but is it really wise to allow the creation of a model that is broken in some important
features?
Yours, Mike.
Ramkumar Ramalingam (JIRA) wrote:
[
https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam reassigned TUSCANY-2347:
--------------------------------------------
Assignee: Ramkumar Ramalingam
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: Ramkumar Ramalingam
Fix For: Java-SCA-Next
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.
