Package jmri.managers

Class ProxySensorManager

    • Method Detail

      • makeBean

        @Nonnull
        protected Sensor makeBean​(Manager<Sensor> manager,
                                  java.lang.String systemName,
                                  java.lang.String userName)
                           throws java.lang.IllegalArgumentException
        Defer creation of the proper type to the subclass.
        Specified by:
        makeBean in class AbstractProvidingProxyManager<Sensor>
        Parameters:
        manager - the manager to invoke
        systemName - the system name
        userName - the user name
        Returns:
        a bean
        Throws:
        java.lang.IllegalArgumentException - if unable to make.
      • provideSensor

        @Nonnull
        public Sensor provideSensor​(@Nonnull
                                    java.lang.String sName)
                             throws java.lang.IllegalArgumentException
        Description copied from interface: SensorManager
        Get the Sensor with the user name, then system name if needed; if that fails, create a new Sensor. If the name is a valid system name, it will be used for the new Sensor. Otherwise, the Manager.makeSystemName(java.lang.String) method will attempt to turn it into a valid system name.

        This provides the same function as ProvidingManager.provide(java.lang.String) which has a more generic form.

        Specified by:
        provideSensor in interface SensorManager
        Parameters:
        sName - User name, system name, or address which can be promoted to system name
        Returns:
        Never null
        Throws:
        java.lang.IllegalArgumentException - if Sensor doesn't already exist and the manager cannot create the Sensor due to an illegal name or name that can't be parsed.
      • provide

        @Nonnull
        public Sensor provide​(@Nonnull
                              java.lang.String name)
                       throws java.lang.IllegalArgumentException
        Get an existing instance via user name, then system name; if no matching instance is found, create a new NameBean from the system name.

        If the name is a valid system name, it will be used for the new NamedBean. Otherwise, the Manager.makeSystemName(java.lang.String) method will attempt to turn it into a valid system name which the manager will attempt to use. If that fails, an exception is thrown.

        This is similar to the specific methods found in certain type-specific managers: TurnoutManager.provideTurnout(java.lang.String), SensorManager.provideSensor(java.lang.String), et al. Those might be more mnemonic; this one is more generic. Neither is preferred nor deprecated; use your choice.

        Specified by:
        provide in interface ProvidingManager<Sensor>
        Specified by:
        provide in interface SensorManager
        Parameters:
        name - User name, system name, or address which can be promoted to system name
        Returns:
        Never null
        Throws:
        java.lang.IllegalArgumentException - if NamedBean doesn't already exist and the manager cannot create it due to an illegal name or name that can't be parsed.
      • newSensor

        @Nonnull
        public Sensor newSensor​(@Nonnull
                                java.lang.String systemName,
                                java.lang.String userName)
                         throws java.lang.IllegalArgumentException
        Return a Sensor with the specified user or system name. Return Sensor by UserName else provide by SystemName.

        Note that two calls with the same arguments will get the same instance; there is only one Sensor object representing a given physical turnout and therefore only one with a specific system or user name.

        This will always return a valid object reference; a new object will be created if necessary. In that case:

        • If a null reference is given for user name, no user name will be associated with the Sensor object created; a valid system name must be provided
        • If both names are provided, the system name defines the hardware access of the desired sensor, and the user address is associated with it. The system name must be valid.
        Note that it is possible to make an inconsistent request if both addresses are provided, but the given values are associated with different objects. This is a problem, and we don't have a good solution except to issue warnings. This will mostly happen if you're creating Turnouts when you should be looking them up.
        Specified by:
        newSensor in interface SensorManager
        Parameters:
        systemName - the desired system name
        userName - the desired user name
        Returns:
        requested Sensor object
        Throws:
        java.lang.IllegalArgumentException - if cannot create the Sensor due to e.g. an illegal name or name that can't be parsed.
      • allowMultipleAdditions

        public boolean allowMultipleAdditions​(@Nonnull
                                              java.lang.String systemName)
        Description copied from interface: NameIncrementingManager
        Determines if it is possible to add a range of NamedBeans in numerical order for a particular system implementation.

        Default is not providing this service. Systems should override this method if they do provide the service.

        Specified by:
        allowMultipleAdditions in interface NameIncrementingManager
        Parameters:
        systemName - the system name to check against; appears to be ignored in all implementations
        Returns:
        true if possible; false otherwise
      • getXMLOrder

        public int getXMLOrder()
        Description copied from interface: Manager
        Determine the order that types should be written when storing panel files. Uses one of the constants defined in this class.

        Yes, that's an overly-centralized methodology, but it works for now.

        Specified by:
        getXMLOrder in interface Manager<Sensor>
        Returns:
        write order for this Manager; larger is later.
      • getBeanTypeHandled

        @Nonnull
        public java.lang.String getBeanTypeHandled​(boolean plural)
        Description copied from interface: Manager
        Get the user-readable name of the type of NamedBean handled by this manager.

        For instance, in the code where we are dealing with just a bean and a message that needs to be passed to the user or in a log.

        Specified by:
        getBeanTypeHandled in interface Manager<Sensor>
        Parameters:
        plural - true to return plural form of the type; false to return singular form
        Returns:
        a string of the bean type that the manager handles, eg Turnout, Sensor etc
      • getNamedBeanClass

        public java.lang.Class<SensorgetNamedBeanClass()
        Get the class of NamedBean supported by this Manager. This should be the generic class used in the Manager's class declaration.
        Specified by:
        getNamedBeanClass in interface Manager<Sensor>
        Returns:
        the class supported by this Manager.
      • isPullResistanceConfigurable

        public boolean isPullResistanceConfigurable()
        Do the sensor objects provided by this manager support configuring an internal pull up or pull down resistor?
        Specified by:
        isPullResistanceConfigurable in interface SensorManager
        Returns:
        true if pull up/pull down configuration is supported, default to false to satisfy the SensorManager interface