You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Andreas Veithen (JIRA)" <ax...@ws.apache.org> on 2012/09/22 11:54:07 UTC

[jira] [Updated] (AXIS-886) Named handlers during deployment are considered unique at server

     [ https://issues.apache.org/jira/browse/AXIS-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen updated AXIS-886:
---------------------------------

    Priority: Minor
    
> Named handlers during deployment are considered unique at server
> ----------------------------------------------------------------
>
>                 Key: AXIS-886
>                 URL: https://issues.apache.org/jira/browse/AXIS-886
>             Project: Axis
>          Issue Type: Bug
>          Components: Deployment / Registries
>    Affects Versions: 1.1rc2
>         Environment: Operating System: All
> Platform: All
>            Reporter: Chad Smith
>            Priority: Minor
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org