You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Saurabh Dravid (JIRA)" <ji...@apache.org> on 2007/05/30 18:07:16 UTC
[jira] Created: (MUSE-234) Resource Inspector "getOperations()" API
returns the operations not available in processed wsdl
Resource Inspector "getOperations()" API returns the operations not available in processed wsdl
-----------------------------------------------------------------------------------------------
Key: MUSE-234
URL: https://issues.apache.org/jira/browse/MUSE-234
Project: Muse
Issue Type: Bug
Components: Tooling - Code Generation
Affects Versions: 2.2.0
Reporter: Saurabh Dravid
Assignee: Dan Jemiolo
Priority: Minor
Fix For: 2.3.0
I have a WSDL file that has a few operations other than destroy, setTerminationTime and notify. When I run this WSDL file through a Resource Inspector, and try to get the operations using getOperations() method, I get these operations (destroy, setTerminationTime and notify) as extra operations, these operations are not defined in my wsdl file.
This is happening because the Resource Inspector adds certain operations as basic operations irrespective of the capabilities implemented by the resource type. The code snippet that populates the basic methods set is given below.
_BASIC_RESOURCE_METHODS.add(WsrpConstants.GET_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.GET_MULTIPLE_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.QUERY_QNAE);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.SET_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrlConstants.DESTROY_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrlConstants.SET_TERMINATION_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.NOTIFY_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.SUBSCRIBE_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.GET_CURRENT_QNAME);
and in most of the cases the getBaseProxyClass() returns an instance of WSResourceClient class which has these methods. So these are getting added to the operations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Updated: (MUSE-234) Resource Inspector "getOperations()" API
returns the operations not available in processed wsdl
Posted by "Saurabh Dravid (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MUSE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saurabh Dravid updated MUSE-234:
--------------------------------
Description:
I have a WSDL file that has a few operations other than destroy, setTerminationTime and notify. When I run this WSDL file through Resource Inspector, and try to get the operations using getOperations() method, I get these operations (destroy, setTerminationTime and notify) as extra operations, these operations are not defined in my wsdl file.
This is happening because Resource Inspector adds certain operations as basic operations irrespective of the capabilities implemented by the resource type. The code snippet that populates the basic methods set is given below.
_BASIC_RESOURCE_METHODS.add(WsrpConstants.GET_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.GET_MULTIPLE_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.QUERY_QNAE);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.SET_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrlConstants.DESTROY_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrlConstants.SET_TERMINATION_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.NOTIFY_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.SUBSCRIBE_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.GET_CURRENT_QNAME);
and in most of the cases the getBaseProxyClass() returns an instance of WSResourceClient class which has these methods. So these are getting added to the operations.
was:
I have a WSDL file that has a few operations other than destroy, setTerminationTime and notify. When I run this WSDL file through a Resource Inspector, and try to get the operations using getOperations() method, I get these operations (destroy, setTerminationTime and notify) as extra operations, these operations are not defined in my wsdl file.
This is happening because the Resource Inspector adds certain operations as basic operations irrespective of the capabilities implemented by the resource type. The code snippet that populates the basic methods set is given below.
_BASIC_RESOURCE_METHODS.add(WsrpConstants.GET_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.GET_MULTIPLE_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.QUERY_QNAE);
_BASIC_RESOURCE_METHODS.add(WsrpConstants.SET_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrlConstants.DESTROY_QNAME);
_BASIC_RESOURCE_METHODS.add(WsrlConstants.SET_TERMINATION_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.NOTIFY_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.SUBSCRIBE_QNAME);
_BASIC_RESOURCE_METHODS.add(WsnConstants.GET_CURRENT_QNAME);
and in most of the cases the getBaseProxyClass() returns an instance of WSResourceClient class which has these methods. So these are getting added to the operations.
> Resource Inspector "getOperations()" API returns the operations not available in processed wsdl
> -----------------------------------------------------------------------------------------------
>
> Key: MUSE-234
> URL: https://issues.apache.org/jira/browse/MUSE-234
> Project: Muse
> Issue Type: Bug
> Components: Tooling - Code Generation
> Affects Versions: 2.2.0
> Reporter: Saurabh Dravid
> Assignee: Dan Jemiolo
> Priority: Minor
> Fix For: 2.3.0
>
>
> I have a WSDL file that has a few operations other than destroy, setTerminationTime and notify. When I run this WSDL file through Resource Inspector, and try to get the operations using getOperations() method, I get these operations (destroy, setTerminationTime and notify) as extra operations, these operations are not defined in my wsdl file.
> This is happening because Resource Inspector adds certain operations as basic operations irrespective of the capabilities implemented by the resource type. The code snippet that populates the basic methods set is given below.
> _BASIC_RESOURCE_METHODS.add(WsrpConstants.GET_QNAME);
> _BASIC_RESOURCE_METHODS.add(WsrpConstants.GET_MULTIPLE_QNAME);
> _BASIC_RESOURCE_METHODS.add(WsrpConstants.QUERY_QNAE);
> _BASIC_RESOURCE_METHODS.add(WsrpConstants.SET_QNAME);
> _BASIC_RESOURCE_METHODS.add(WsrlConstants.DESTROY_QNAME);
> _BASIC_RESOURCE_METHODS.add(WsrlConstants.SET_TERMINATION_QNAME);
> _BASIC_RESOURCE_METHODS.add(WsnConstants.NOTIFY_QNAME);
> _BASIC_RESOURCE_METHODS.add(WsnConstants.SUBSCRIBE_QNAME);
> _BASIC_RESOURCE_METHODS.add(WsnConstants.GET_CURRENT_QNAME);
> and in most of the cases the getBaseProxyClass() returns an instance of WSResourceClient class which has these methods. So these are getting added to the operations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org