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 "Prasad A. Chodavarapu (JIRA)" <ax...@ws.apache.org> on 2005/05/09 11:41:09 UTC
[jira] Created: (AXIS-1981) Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly
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
[jira] Commented: (AXIS-1981) Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly
Posted by "Prasad A. Chodavarapu (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1981?page=comments#action_64794 ]
Prasad A. Chodavarapu commented on AXIS-1981:
---------------------------------------------
Even if we set up by hand, the parameters for a handlerInfoChain in server-config.wsdd, the paramaters aren't being as mambers of the Map returned by HandlerInfo.getHandlerConfig() in the handler's init method.
> 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
[jira] Commented: (AXIS-1981) Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly
Posted by "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
[jira] Commented: (AXIS-1981) Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly
Posted by "Venkat Reddy (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1981?page=comments#action_65948 ]
Venkat Reddy commented on AXIS-1981:
------------------------------------
Two problems with your WSDD:
1. The <paramater name="rolesList" ..> has a typo in it.
2. <parameter scope="application"/> : A parameter element should be a name value pair.
- Venkat
> 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
[jira] Resolved: (AXIS-1981) Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly
Posted by "Venkat Reddy (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1981?page=all ]
Venkat Reddy resolved AXIS-1981:
--------------------------------
Resolution: Invalid
> 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
[jira] Updated: (AXIS-1981) Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly
Posted by "Prasad A. Chodavarapu (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1981?page=all ]
Prasad A. Chodavarapu updated AXIS-1981:
----------------------------------------
Attachment: deploy-example2.wsdd
Example WSDD
> 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
[jira] Updated: (AXIS-1981) Parameters set in axis.handlers.JAXRPCHandler configuration not deployed correctly
Posted by "Prasad A. Chodavarapu (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1981?page=all ]
Prasad A. Chodavarapu updated AXIS-1981:
----------------------------------------
Attachment: server-config.wsdd
Resultant server-config.wsdd
> 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