xwss
  1. xwss
  2. XWSS-49

XWSSTubelineAssemblerFactory strange behavior

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: www
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      49

      Description

      Tried to plug in the XWSS framework to the client side application via the tube
      line. I created the file com.sun.xml.ws.api.pipe.TubelineAssemblerFactory in
      META-INF/services. So I expected outgoing messages tobe processed after setting
      the security configuration as a request property
      (((BindingProvider)port).getRequestContext().put(XWSSecurityConfiguration.MESSAGE_SECURITY_CONFIGURATION,
      config).
      But no messages were affected. I discovered that XWSSTubelineAssemblerFactory
      initialized the client in an appropriate way when the method
      XWSSTubelineAssembler.isSecurityConfigPresent(ClientTubeAssemblerContext)
      returns true.
      But according to the code it won't return the true value if there is no file
      client_security_config.xml in META-INF.
      In such case it returns
      Boolean.getBoolean("USE_XWSS_SECURITY") - it's always false.
      Rather strange... I had to create my own factory to fix it.

        Activity

        Hide
        kumarjayanti added a comment -

        Hi,

        The XWSS stuff is really old and we have no real customers so there was a
        thought of disabling the supporting for it by default and having it enabled by
        the client setting the System Property. The main reason is that the policy
        configuration can be specified programmatically and the runtime is forced to
        always create the client side Security Tube (costing a little bit of
        performance) in anticipation of there being a runtime configuration of policy.

        But it turned out that our Performance team has recently revived some old ghosts
        which use the same old stuff. So we had to remove the Boolean.getBoolean() and
        instead always return true as it used to earlier.

        If you pick the latest Metro bits you should see the right behavior.

        Show
        kumarjayanti added a comment - Hi, The XWSS stuff is really old and we have no real customers so there was a thought of disabling the supporting for it by default and having it enabled by the client setting the System Property. The main reason is that the policy configuration can be specified programmatically and the runtime is forced to always create the client side Security Tube (costing a little bit of performance) in anticipation of there being a runtime configuration of policy. But it turned out that our Performance team has recently revived some old ghosts which use the same old stuff. So we had to remove the Boolean.getBoolean() and instead always return true as it used to earlier. If you pick the latest Metro bits you should see the right behavior.

          People

          • Assignee:
            xwss-issues
            Reporter:
            mazur_roman
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: