[jira] Commented: (AXIS-1981) Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly

["Prasad A. Chodavarapu (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXIS-1981?page=comments#action_64739 ]
     
Prasad A. Chodavarapu commented on AXIS-1981:
---------------------------------------------

The same happens for handlerInfo parameters as well. For example,   

<service name="example2" provider="java:RPC" style="rpc" use="encoded">
      <handlerInfoChain>  
        <handlerInfo classname="...">
          <parameter name="p1" value="v1"/>
        </handlerInfo>
        <role soapActorName="http://manning.com/xmlns/samples/soasecimpl/cop"/>
      </handlerInfoChain>
</service>

loses its parameters when deployed. The resulting server-config.wsdd doesn't even have a parameter line with empty name/value pair as in the case of axis.handlers.JAXRPCHandler. 

> Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly
> ----------------------------------------------------------------------------------
>
>          Key: AXIS-1981
>          URL: http://issues.apache.org/jira/browse/AXIS-1981
>      Project: Axis
>         Type: Bug
>   Components: Deployment / Registries
>     Versions: 1.2, 1.2RC3
>  Environment: java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
> Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing)
>     Reporter: Prasad A. Chodavarapu
>  Attachments: deploy-example2.wsdd, server-config.wsdd
>
> Any parameters other than className provided with a axis.handlers.JAXRPCHandler configuration are not correctly deployed by the AdminService. Here are some extracts from the example files I'm attaching:
> deploy.wsdd:
> ===========
>   <service name="example2" provider="java:RPC" style="rpc" use="encoded">
>       <requestFlow>  
>         <handler type="java:org.apache.axis.handlers.JAXRPCHandler">
>           <parameter scope="application"/>
>           <parameter name="className" 
>             value="com.manning.samples.soasecimpl.example2.WSSecurityUsernameHandler"/>
>           <paramater name="rolesList" 
>             value="http://manning.com/xmlns/samples/soasecimpl/cop"/>
>         </handler>
>       </requestFlow>
>       ...
>   </service>
> server-config.wsdd after deploying the above:
> =============================================
>   <service name="example2" provider="java:RPC">
>   ...
>   <requestFlow>
>     <handler type="java:org.apache.axis.handlers.JAXRPCHandler">
>       <parameter name="className"   value="com.manning.samples.soasecimpl.example2.WSSecurityUsernameHandler"/>
>       <parameter name="" value=""/>
>     </handler>
>     ...
>   </requestFlow>
> As you can see, the "rolesList" parameter is lost during deployment. So is the "scope" parameter.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira