[ 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to