Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-1210

Transformations are not triggered for aliases

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 2.0.4.Final
    • Fix Version/s: 2.0.5.CR1
    • Component/s: Management
    • Labels:
      None

      Description

      Currently only operations passed in to the controller by the client are passed over to the transformers. So if you have an alias /an=alias mapping to /some=resource, and a transformer mapped for /some=resource:

      /some=resource:add gets transformed
      /an=alias:add does not get transformed.

      Behind the scenes /an=alias:add ends up in AliasStepHandler, which adds the step to invoke the real /some=resource:add. Unfortunately the /some=resource:add does not get passed to the transformers.
      The transformer framework should use the same logic as AliasStepHandler to map the alias to the real address and the transform that.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  kabirkhan Kabir Khan
                  Reporter:
                  rhusar Radoslav Husar
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: