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 "Steve Jerman (JIRA)" <ji...@apache.org> on 2006/09/15 20:10:22 UTC
[jira] Created: (MUSE-108) Implementation forces WSDL Operation
name choice
Implementation forces WSDL Operation name choice
------------------------------------------------
Key: MUSE-108
URL: http://issues.apache.org/jira/browse/MUSE-108
Project: Muse
Issue Type: Bug
Components: WSDM MUWS Core ManageabilityCapability API
Affects Versions: 2.0.0
Reporter: Steve Jerman
Assigned To: Dan Jemiolo
My test model contains an operation 'shutdown'. The generated code:
public class SystemOperationsImplImpl extends AbstractCapability implements SystemOperationsImpl
{
public Element shutdown() throws Exception {
//TODO implement
throw new RuntimeException("Unimplemented Method");
Doesn't compile since AbstractCapabilty contains a 'shutdown'.
The documentation needs to explain what operation names are legal. Better still put a _ in front of the operation names to avoid clashes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Commented: (MUSE-108) Implementation forces WSDL Operation
name choice
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-108?page=comments#action_12435271 ]
Dan Jemiolo commented on MUSE-108:
----------------------------------
I disagree with "fixing" this - the capability lifecycle operations are equivalent to the Object methods - you can override them, but you shouldn't be changing their semantics. These operations are called by Muse at startup and shutdown to give users the opportunity to perform internal init./shutdown tasks.
If you want to have a "shutdown"-like method that can be invoked by remote clients, use WSRL Destroy (in the ImmediateTermination capability).
The /docs/overview-core.html file in the RC build contains the four lifecycle methods now, but it is better explained in the docs we have in SVN for /site (available in the release).
> Implementation forces WSDL Operation name choice
> ------------------------------------------------
>
> Key: MUSE-108
> URL: http://issues.apache.org/jira/browse/MUSE-108
> Project: Muse
> Issue Type: Bug
> Components: WSDM MUWS Core ManageabilityCapability API
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
>
> My test model contains an operation 'shutdown'. The generated code:
> public class SystemOperationsImplImpl extends AbstractCapability implements SystemOperationsImpl
> {
> public Element shutdown() throws Exception {
> //TODO implement
> throw new RuntimeException("Unimplemented Method");
>
> Doesn't compile since AbstractCapabilty contains a 'shutdown'.
> The documentation needs to explain what operation names are legal. Better still put a _ in front of the operation names to avoid clashes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Closed: (MUSE-108) Add better error handling and warning for
tooling
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-108?page=all ]
Dan Jemiolo closed MUSE-108.
----------------------------
Fix Version/s: 2.0.0
(was: 2.1.0)
Resolution: Fixed
> Add better error handling and warning for tooling
> -------------------------------------------------
>
> Key: MUSE-108
> URL: http://issues.apache.org/jira/browse/MUSE-108
> Project: Muse
> Issue Type: Bug
> Components: WSDM MUWS Core ManageabilityCapability API
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
> Fix For: 2.0.0
>
>
> My test model contains an operation 'shutdown'. The generated code:
> public class SystemOperationsImplImpl extends AbstractCapability implements SystemOperationsImpl
> {
> public Element shutdown() throws Exception {
> //TODO implement
> throw new RuntimeException("Unimplemented Method");
>
> Doesn't compile since AbstractCapabilty contains a 'shutdown'.
> The documentation needs to explain what operation names are legal. Better still put a _ in front of the operation names to avoid clashes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Commented: (MUSE-108) Implementation forces WSDL Operation
name choice
Posted by "Steve Jerman (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-108?page=comments#action_12435955 ]
Steve Jerman commented on MUSE-108:
-----------------------------------
Feel free to close this.... (I would but can't)
> Implementation forces WSDL Operation name choice
> ------------------------------------------------
>
> Key: MUSE-108
> URL: http://issues.apache.org/jira/browse/MUSE-108
> Project: Muse
> Issue Type: Bug
> Components: WSDM MUWS Core ManageabilityCapability API
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
>
> My test model contains an operation 'shutdown'. The generated code:
> public class SystemOperationsImplImpl extends AbstractCapability implements SystemOperationsImpl
> {
> public Element shutdown() throws Exception {
> //TODO implement
> throw new RuntimeException("Unimplemented Method");
>
> Doesn't compile since AbstractCapabilty contains a 'shutdown'.
> The documentation needs to explain what operation names are legal. Better still put a _ in front of the operation names to avoid clashes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Assigned: (MUSE-108) Implementation forces WSDL Operation
name choice
Posted by "Andrew Eberbach (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-108?page=all ]
Andrew Eberbach reassigned MUSE-108:
------------------------------------
Assignee: Andrew Eberbach (was: Dan Jemiolo)
> Implementation forces WSDL Operation name choice
> ------------------------------------------------
>
> Key: MUSE-108
> URL: http://issues.apache.org/jira/browse/MUSE-108
> Project: Muse
> Issue Type: Bug
> Components: WSDM MUWS Core ManageabilityCapability API
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
>
> My test model contains an operation 'shutdown'. The generated code:
> public class SystemOperationsImplImpl extends AbstractCapability implements SystemOperationsImpl
> {
> public Element shutdown() throws Exception {
> //TODO implement
> throw new RuntimeException("Unimplemented Method");
>
> Doesn't compile since AbstractCapabilty contains a 'shutdown'.
> The documentation needs to explain what operation names are legal. Better still put a _ in front of the operation names to avoid clashes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Commented: (MUSE-108) Implementation forces WSDL Operation
name choice
Posted by "Andrew Eberbach (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-108?page=comments#action_12435257 ]
Andrew Eberbach commented on MUSE-108:
--------------------------------------
I'd like to do this for the next point release. The thing I want to introduce is a pluggable error handler so that the interface can decide what to do with these kinds of errors.
On the command line this would just be printing a warning message (or an error message).
In eclipse tooling this could be decorating the offending operation.
> Implementation forces WSDL Operation name choice
> ------------------------------------------------
>
> Key: MUSE-108
> URL: http://issues.apache.org/jira/browse/MUSE-108
> Project: Muse
> Issue Type: Bug
> Components: WSDM MUWS Core ManageabilityCapability API
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Dan Jemiolo
>
> My test model contains an operation 'shutdown'. The generated code:
> public class SystemOperationsImplImpl extends AbstractCapability implements SystemOperationsImpl
> {
> public Element shutdown() throws Exception {
> //TODO implement
> throw new RuntimeException("Unimplemented Method");
>
> Doesn't compile since AbstractCapabilty contains a 'shutdown'.
> The documentation needs to explain what operation names are legal. Better still put a _ in front of the operation names to avoid clashes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Commented: (MUSE-108) Implementation forces WSDL Operation
name choice
Posted by "Steve Jerman (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-108?page=comments#action_12435276 ]
Steve Jerman commented on MUSE-108:
-----------------------------------
After perusing the code , I am happy with this...
> Implementation forces WSDL Operation name choice
> ------------------------------------------------
>
> Key: MUSE-108
> URL: http://issues.apache.org/jira/browse/MUSE-108
> Project: Muse
> Issue Type: Bug
> Components: WSDM MUWS Core ManageabilityCapability API
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
>
> My test model contains an operation 'shutdown'. The generated code:
> public class SystemOperationsImplImpl extends AbstractCapability implements SystemOperationsImpl
> {
> public Element shutdown() throws Exception {
> //TODO implement
> throw new RuntimeException("Unimplemented Method");
>
> Doesn't compile since AbstractCapabilty contains a 'shutdown'.
> The documentation needs to explain what operation names are legal. Better still put a _ in front of the operation names to avoid clashes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Updated: (MUSE-108) Add better error handling and warning
for tooling
Posted by "Andrew Eberbach (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-108?page=all ]
Andrew Eberbach updated MUSE-108:
---------------------------------
Summary: Add better error handling and warning for tooling (was: Implementation forces WSDL Operation name choice)
Fix Version/s: 2.1.0
> Add better error handling and warning for tooling
> -------------------------------------------------
>
> Key: MUSE-108
> URL: http://issues.apache.org/jira/browse/MUSE-108
> Project: Muse
> Issue Type: Bug
> Components: WSDM MUWS Core ManageabilityCapability API
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
> Fix For: 2.1.0
>
>
> My test model contains an operation 'shutdown'. The generated code:
> public class SystemOperationsImplImpl extends AbstractCapability implements SystemOperationsImpl
> {
> public Element shutdown() throws Exception {
> //TODO implement
> throw new RuntimeException("Unimplemented Method");
>
> Doesn't compile since AbstractCapabilty contains a 'shutdown'.
> The documentation needs to explain what operation names are legal. Better still put a _ in front of the operation names to avoid clashes.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org