[jira] [Commented] (STREAMS-580) Namespacing with fallbacks in ComponentConfigurator

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STREAMS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349018#comment-16349018 ] 

ASF GitHub Bot commented on STREAMS-580:
----------------------------------------

steveblackmon opened a new pull request #421: STREAMS-580: Namespacing with fallbacks in ComponentConfigurator
URL: https://github.com/apache/streams/pull/421
 
 
   STREAMS-580: Namespacing with fallbacks in ComponentConfigurator (https://issues.apache.org/jira/browse/STREAMS-580)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Namespacing with fallbacks in ComponentConfigurator
> ---------------------------------------------------
>
>                 Key: STREAMS-580
>                 URL: https://issues.apache.org/jira/browse/STREAMS-580
>             Project: Streams
>          Issue Type: Improvement
>            Reporter: Steve Blackmon
>            Assignee: Steve Blackmon
>            Priority: Major
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Add support for class and package based namespacing in ComponentConfigurator:
> - Add a new method to ComponentConfigurator - detectConfiguration() 
> - When the caller does not provide a Config or a path to detectConfiguration, get fancy:
> - Look for the fields declared by the component POJO class on each of the following:
> - the SimpleClassName
> - the CanonicalClassName
> - each ancestor package of the CanonicalClassName, longest to shortest
> - if a field is specified at more than one package/class level, the class or longest package ancestor takes precedence.
> Write sufficient unit tests to demonstrate that this is working as intended.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)