PicoContainer
  1. PicoContainer
  2. PICO-317

Have Behavior Names in Properties equal the Behavior classname as convention.

    Details

    • Type: Wish Wish
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      As we develop more behaviors, there is a chance (however remote) that somebody's characteristic's name would collide with an existing implementation. This could easily be solved if the we changed org.picocontainer.Characteristics constants for the "_*" attributes to be classnames.

      Example:

      Current:
      _CACHE = "cache";

      Proposed:
      _CACHE= "org.picocontainer.behaviors.Caching"

      I was going to suggest _CACHE=Caching.class.getName(), but that method wouldn't scale to Gems where Java would try to link optional classes that didn't have everything available on the classpath. For example, Slf4jComponentMonitor.class would throw a NoClassDefFoundError if Slf4j wasn't on the classpath.

        People

        • Assignee:
          Unassigned
          Reporter:
          Michael Rimov
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated: