Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-16882 Modify description in each module of subsystem to its correct sentence
  3. WFLY-16910

Modify description in transactions of subsystem to its correct sentence

XMLWordPrintable

      Check and update the description to its correct sentance if needed.

      /subsystem=transaction:read-resource-description

       

      FROM:

      "description" => "Used to set the node identifier. Each Xid that the transaction manager creates will have this identifier encoded within it and ensures the transaction manager will only recover branches which match the specified identifier. It is imperative that this identifier is unique between application server instances which share either an object store or access common resource managers.",

       

      "description" => "Denotes a path where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the 'relative-to' attribute. When the 'relative-to' attribute is undefined the value is considered an absolute path. This setting is valid when default or journal store is used. It's not used when the jdbc journal store is used.",

       

      "description" => "Indicates a strategy used for obtaining a unique identifier needed for creation of transaction instances. When true then the transaction manager generates the transaction id based on process id (PID). When set to false then the transaction manager generates the transaction id based on the referenced socket binding, i.e. the attribute 'process-id-socket-binding' is required.",

       

      "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log.It's alternative to jdbc based store.",

       

      TO:

      "description" => "Used to set the node identifier. Each Xid that the transaction manager creates will have this identifier encoded within it and ensures the transaction manager will only recover branches that match the specified identifier. It is imperative that this identifier is unique between application server instances which share either an object store or access common resource managers.",

       

      "description" => "Denotes a path where the transaction manager object store should store data. By default, the value is treated as relative to the path denoted by the 'relative-to' attribute. When the 'relative-to' attribute is undefined the value is considered an absolute path. This setting is valid when default or journal store is used. It's not used when the jdbc journal store is used.",

       

      "description" => "Indicates a strategy used for obtaining a unique identifier needed for the creation of transaction instances. When true, the transaction manager generates the transaction id based on the process id (PID). When set to false then the transaction manager generates the transaction id based on the referenced socket binding, i.e. the attribute 'process-id-socket-binding' is required.",

       

      "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. It's alternative to jdbc based store.",

            rhn-support-gabsanto Gabriel Santos
            mshikalw Moulali Shikalwadi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: