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

Dan Becker resolved TUSCANY-2633.
---------------------------------

       Resolution: Fixed
    Fix Version/s: Java-SCA-1.4

java\sca\modules\assembly\src\main\java\org\apache\tuscany\sca\assembly\impl\CompositeImpl.java
java\sca\modules\policy\src\main\java\org\apache\tuscany\sca\policy\impl\ImplementationTypeImpl.java
java\sca\modules\policy\src\main\java\org\apache\tuscany\sca\policy\impl\PolicySetImpl.java

Resolved At revision: 702995

> *Impl.java to String
> --------------------
>
>                 Key: TUSCANY-2633
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2633
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.3.2, Java-SCA-1.4
>            Reporter: Dan Becker
>            Assignee: Dan Becker
>             Fix For: Java-SCA-1.4
>
>
> Similar to 
> tuscany-policy/src/main/java/org/apache/tuscany/sca/policy/impl/BindingTypeImpl
>  and TUSCANY-2632, a few imple classes have toString() is implemented as 
> getName().toString(). This is unsafe when the getName is null and can return 
> a NullPointerException. Test the name in order to program more defensively.
> For example:
> return (getName() != null) ? getName().toString() : "null";
> (Note, I see this show up when Tracing/Logging with AspectJ, which probably 
> runs the Tuscany code in a slightly different way that the normal 
> Node>Composite>Domain order.)

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

Reply via email to