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.
Summary: | Support for deployment to any single target instance | ||
---|---|---|---|
Product: | serverplugins | Reporter: | Nam Nguyen <nnguyen> |
Component: | Infrastructure | Assignee: | Petr Hejl <phejl> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | marcow, pjiricka, pzavadsky |
Priority: | P1 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 55325 |
Description
Nam Nguyen
2005-04-01 23:07:56 UTC
One solution is following chnages: 1. Deployment.getTargetInstanceIDs to return (instanceID + target name) for use by project customizers. 2. Add J2eeModuleProvider.getTargetInstanceID to be use instead of getServerInstanceID whereever appropriate. 3. Facility to convert target-instance-id into ServerString for use by DeploymentTargetImpl. *** Issue 57699 has been marked as a duplicate of this issue. *** Increasing to p1 because of the p1 duplicate of this issue. My preference would be we had something better than those `ID-strings'. I would prefer some `bean??' type of thing which would encapsulate the ServerString etc. and could also be used to generate a good display string for menus/dialogs etc. Right now, we use the ID string, which is `ugly' in UI's. Thanks, -- Marco Ok, my solution for now is to make a combined ServerInstanceID out of the instanceURL (as NB original code) plus possibly '[[' + targetName + ']]' and then split it up into pieces again where I need it. As I said before, I don't like those String based ID's but this looked like the closed I could get to the original code. Thanks, -- Marco I guess this is not p1 anymore... There was no user request about such support. |