3 Replies Latest reply on Mar 10, 2008 9:23 AM by kconner

    Dynamic configuration of fs-message-filter

    lucdew

      Hi,

      I would like to avoid using hard-coded values in the jboss-esb.xml
      Especially for the fs-message-filter i don't want to hardcode the input directories and want the values to be resolved at runtime.

      For my personal actions i did the following, every property value is resolved at initialization time:

      <property name="test" value="${config.key}"/>
      


      and when the value is placed between ${ } i load it in an external repository (DB, FS or whatever).

      Would there be a way to hook up the jboss-esb.xml loading to replace values or extend the fs-message-filter with my own version to load values ?
      Example:
      <fs-message-filter
       directory="${input.dir}"
      ...
      


      Thanks in advance,
      Luc

        • 1. Re: Dynamic configuration of fs-message-filter
          kconner

          Which version are you using?

          The current trunk/CP branch have supported property substitution since December, certainly for system properties. We do not yet provide the ability to retrieve these from DB etc. but it should be a (relatively) straight forward task to add.

          • 2. Re: Dynamic configuration of fs-message-filter
            lucdew

             

            "Kevin.Conner@jboss.com" wrote:
            Which version are you using?


            4.2.1 GA.

            I have seen property substitution in quickstart examples but it is performed at build time with Ant.

            I do not intend to use a version built from the trunk.

            Would there be a way to provide my own fs-message-filter implementation which would basically be an extension of the existing one that would load the input directory and other parameters with our own application configuration management ?

            If not, we'll stick to the build time substitution.

            Thanks,
            Luc

            • 3. Re: Dynamic configuration of fs-message-filter
              kconner

              The trunk/CP now support property substitution at deploy time using the System properties.

              The only choices you have at the moment are to stick with build time or use the version in trunk.

              The schedule for our next project release is mentioned in the Development Forum