3 Replies Latest reply on Apr 13, 2004 6:56 PM by adrian.brock

    Complete jdbc state manager

      As of jboss-3.2.3 there is the jdbc state manager which replaces jbossmq-state.xml
      with a db store for users/roles and durable subscriptions.

      This needs completing:
      1) Add jmx operations to modify users/roles like file version.
      2) Add a mechanism to initialize the configuration for the testsuite,
      e.g. read the state from jbossmq-state.xml and write it to the db.

      Additionally, it would also be nice if the state manager allowed durable subscriptions
      to be modified using JMX. The hard part is what happens when a subscription
      is active.

      Regards,
      Adrian

        • 1. Re: Complete jdbc state manager
          ivelin.ivanov


          If someone takes this one, let me know.

          Related to this job, I'm working on the user/password set when the JMS manager is deployed. The mechanism that works for the XML state manager is not ported yet.
          Additionally, Since 2.3.4 will ship with the Hibernate SAR I am considering using that as the persistence abstraction for the JMS persistence manager, so that there is no need to maintain a JMS-DS SAR for each database.

          Ivelin

          • 2. Re: Complete jdbc state manager

            I created a separate topic for the hibernate persistence manager and state manager.

            Regards,
            Adrian

            • 3. Re: Complete jdbc state manager

              Part (2) of this requirement has been implemented.
              It is possible to run sql statements when creating queues to populate the database.
              This is really intended for the testsuite and configuring the default guest.
              In practice you would not want to store passwords in plain text.

              Regards,
              Adrian