DO NOT REPLY [Bug 20068] New: - Named handlers during deployment are considered unique at server

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20068>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20068

Named handlers during deployment are considered unique at server

           Summary: Named handlers during deployment are considered unique
                    at server
           Product: Axis
           Version: 1.0-rc2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Deployment / Registries
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: chadsm@mitre.org


PROBLEM:

[SEE: WSDD example 4 in samples/userguide]

When a WSDD contains a top-level named Handler, deployment causes the Handler 
to be recorded on the server WSDD as a top-level Handler with the same name.  
As a result, if two separate WSDD use the same name for a top-level Handler, 
the server only records the most recent published.

EXAMPLE:

WSDD1 contains this XML segment:
<deployment ...>
  <handler name="X" type="java:Y">
    <parameter name="Z" value="WSDD1"/>
  </handler>
...
</deployment>

WSDD2 contains this XML segment:
<deployment ...>
  <handler name="X" type="java:Y">
    <parameter name="Z" value="WSDD2"/>
  </handler>
...
</deployment>

When WSDD1 is deployed, the handler is recorders in the server WSDD.  Then, 
when WSDD2 is deployed, the handler from WSDD1 is removed, and the handler for 
WSDD2 is written.

SOLUTION:

Multiple solutions will work, but the simplest would be to scope top-level 
handler names when transitioned from the deployment WSDD to the server WSDD.  
This still enforces name uniqueness but ensures multiple deployment WSDDs can 
use the same handler name.