You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <tu...@ws.apache.org> on 2008/05/19 19:59:56 UTC

[jira] Resolved: (TUSCANY-2277) Standardization of registering msg with monitor

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

Simon Laws resolved TUSCANY-2277.
---------------------------------

    Resolution: Fixed

Checked in at r657881. Thanks Ram


> Standardization of registering msg with monitor
> -----------------------------------------------
>
>                 Key: TUSCANY-2277
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2277
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Assembly Model
>    Affects Versions: Java-SCA-Next
>         Environment: Windows XP
>            Reporter: Ramkumar Ramalingam
>            Assignee: Simon Laws
>             Fix For: Java-SCA-Next
>
>         Attachments: TUSCANY-2277-Part1-New.patch, TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2-New.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3-New.patch, TUSCANY-2277-Part3.patch
>
>
> Lokking at the monitors that are being hooked up with different parts of the code, found  that we have some inconsistency interms of raising warning & errors. In some places we throw exceptions and in other places we raise a warning. 
>  
> Here are some examples for the inconsistency.......
>  
> BaseConfigurationBuilderImpl.java
> Here we raise only a warning for URISyntaxException, should we not throw an exception too?
>  
> BaseWireBuilderImpl.java
> Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor?
> In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here?
>  
> CompositeProcessor.java
> There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input.
> From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed....
> http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html

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