This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 96836 - Cluster UI spec reviewed
Summary: Cluster UI spec reviewed
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Nitya Doraisamy
Depends on:
Blocks: 96835
  Show dependency tree
Reported: 2007-02-28 20:05 UTC by Vince Kraemer
Modified: 2007-05-22 16:23 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Vince Kraemer 2007-02-28 20:05:37 UTC
Comment 1 Nitya Doraisamy 2007-03-14 21:24:43 UTC
UI Spec for Clustering support will be ready for review by Mar16.
Prototype available by : Mar19.
Comment 2 Nitya Doraisamy 2007-03-14 21:25:11 UTC
UI Spec for Clustering support will be ready for review by Mar16.
Prototype available by : Mar19.
Comment 3 Nitya Doraisamy 2007-03-16 17:53:17 UTC
UI Spec available at
Comment 4 Vince Kraemer 2007-03-16 18:43:14 UTC
added link to spec.  Folks may want to comment here...
Comment 5 Petr Pisl 2007-03-28 14:22:58 UTC
PP01: What is the purpose of this feature? It's just for people, who deploy to
the clustered AS? Is there any real usecase, why developer needs to work with
clustered AS? We are trying to minimize time of deployment, redeployment and
debugging. How are influence these times in such case, when the application is
deployed to the clustered environment? Is there any difference during between
development for clustered and non clustered server?

PP02: From  the  spec it looks like that the ide will not deploy the application
to the cluster automatically. User has to do it "by hand".  What happen when the
user redeploy the application? Will be redeployed to the cluster automatically?
Comment 6 Josef Holy 2007-03-28 17:11:29 UTC
I do agree with what Petr Pisl wrote in the previous comment. What I am
generally missing in the spec is the user context. Use cases seem to be a bit
too much tech-oriented - written from the point of view of the server/IDE etc.
Could you please try to explain them from the user's point of view? I mean write
them in the form like 'The user is in the state A and wants to perform
action/task B'? I think that it could help to solve both issues Petr has pointed to.