[jboss-jira] [JBoss JIRA] (AS7-1535) More management operations for timers

[Bartosz Baranowski (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749181#comment-12749181 ] 

Bartosz Baranowski edited comment on AS7-1535 at 1/21/13 8:39 AM:
------------------------------------------------------------------

Ive been poking around the code to familiarize myself with it. Initially it seemed a good idea to put those ops under 
{noformat}
/subsystem=ejb3/service=timer-service
{noformat}
, since I assumed thats a proper spot. However this counters look and feel of jboss CLI and model. Im now digging into code to check what changes are required to push this to deployment root in CLI, for instance: 
{noformat}
/deployment=jboss-as-ejb-in-ear.ear/subdeployment=jboss-as-ejb-in-ear.jar/subsystem=ejb3/stateless-session-bean=GreeterEJB/service=timer-service
{noformat}

This would reduce number of parameters and bring some context into invocations and conform to overal design.

So instead of calls like:
{noformat}
cd /subsystem=ejb3/service=timer-service
:list(...) //and choose timer, deployment, etc
:suspend(target="jboss-as-ejb-in-ear.jboss-as-ejb-in-ear.jar.GreeterEJB", service="jboss.deployment.subunit.jboss-as-ejb-in-ear.ear.jboss-as-ejb-in-ear.jar.component.GreeterEJB.ejb3.timerService", id="5816a904-4cc1-489a-a412-14f79ad7e3eb")
{noformat}

We would do:
{noformat}
cd /deployment=jboss-as-ejb-in-ear.ear/subdeployment=jboss-as-ejb-in-ear.jar/subsystem=ejb3/stateless-session-bean=GreeterEJB/service=timer-service
:suspend(id="asdfasfadsgasa")
{noformat}

or
{noformat}
cd /deployment=jboss-as-ejb-in-ear.ear/subdeployment=jboss-as-ejb-in-ear.jar/subsystem=ejb3/stateless-session-bean=GreeterEJB/service=timer-service/timer=512y724yh5472157
:suspend()
{noformat}

Last format would allow to read consistently timers as resource via Model.

                
      was (Author: baranowb):
    Ive been poking around the code to familiarize myself with it. Initially it seemed a good idea to put those ops under /subsystem=ejb3/service=timer-service, since I assumed thats a proper spot. However this counters look and feel of jboss CLI and model. Im now digging into code to check what changes are required to push this to deployment root in CLI, for instance: 
{noformat}
/deployment=jboss-as-ejb-in-ear.ear/subdeployment=jboss-as-ejb-in-ear.jar/subsystem=ejb3/stateless-session-bean=GreeterEJB/service=timer
{noformat}

This would reduce number of parameters and bring some context into invocations and conform to overal design.
                  
> More management operations for timers
> -------------------------------------
>
>                 Key: AS7-1535
>                 URL: https://issues.jboss.org/browse/AS7-1535
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management, EJB
>            Reporter: Stuart Douglas
>            Assignee: Bartosz Baranowski
>             Fix For: 7.3.0.Alpha1
>
>
> Using the management api it should be possible to perform additional operations on timers such as:
> suspending
> cancelling 
> invoking a timeout method

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira