Bug 110496 - Implement stopServer() and refreshServer() methods
Implement stopServer() and refreshServer() methods
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9
6.x
All All
: P4 (vote)
: TBD
Assigned To: Nitya Doraisamy
issues@serverplugins
:
Depends on: 95234 182772
Blocks: 92713 92714
  Show dependency treegraph
 
Reported: 2007-07-21 17:17 UTC by Alexander Kouznetsov
Modified: 2010-03-25 13:13 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-07-21 17:17:55 UTC
Profiler needs following methods to be implemented to be able to manipulate server status in Services dialog:
- stopServer()
- refreshServer()

See also issue 92713 and issue 92714.
Comment 1 Vince Kraemer 2008-04-26 03:31:05 UTC
this looks like it fell through the cracks, since it wasn't assigned to a human...
Comment 2 Vince Kraemer 2008-09-04 00:00:24 UTC
where are the methods stopSserver and refreshServer defined?  What interface are they part of?

Or is this some kind of dead issue?
Comment 3 Alexander Kouznetsov 2008-09-08 12:39:54 UTC
AFAIK, the issue is still valid. Jiri, could you please comment on this issue?
Comment 4 Jiri Sedlacek 2008-09-09 17:20:33 UTC
This RFE is to address Issue 92713 and Issue 92714 - there needs to be some public API to refresh profiled server status
and stop it when finishing profiling session. I don't think the RFE is assigned correctly - it's a general serverplugins
API not related to just GlassFish - change the Subcomponent?

Note that more investigation is needed on both profiler and serverplugins side, definitely not for 6.5 and likely not in
 nearest future => changing Target milestone to future. Profiler team will refresh this issue/invoke the discussion when
more data is available.
Comment 5 Vince Kraemer 2008-10-18 03:26:19 UTC
bug scrub... any update on this?

Comment 6 Alexander Kouznetsov 2008-10-29 07:20:13 UTC
Please provide justification for priority change.
Comment 7 Vince Kraemer 2008-10-29 16:04:27 UTC
it is dependent on issues that are not getting any traction in a plugin which is in maintenance mode... (no new features)

P4... 
Comment 8 Alexander Kouznetsov 2008-10-30 19:33:57 UTC
Could you please specify dependent issues?
Comment 9 Alexander Kouznetsov 2008-10-30 19:36:17 UTC
I. e. issues that blocks this issue. There are some if I understood you correctly.
Comment 10 Vince Kraemer 2008-10-30 20:40:47 UTC
the api that you want the plugin to use doesn't appear to be defined yet...
Comment 11 Vince Kraemer 2009-12-10 12:55:04 UTC
no bug should be assigned to issues. distributing the load.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo