Bug 59180 - Use better server instance identification than jsr-88 uri
Use better server instance identification than jsr-88 uri
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: Infrastructure
5.x
All All
: P3 (vote)
: TBD
Assigned To: Petr Hejl
issues@serverplugins
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-23 15:29 UTC by Sherold Dev
Modified: 2007-08-30 17:38 UTC (History)
0 users

See Also:
Issue Type: TASK
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sherold Dev 2005-05-23 15:29:01 UTC
When adding a new server instance to the server registry it should be assigned a
unique key that would allow to differentiate it from the others. Currently the
jsr-88 deployment URI of the server is used which causes identification
conflicts when there is need to add two different instances of a particular
server type, which are set up to listen on the same port. For example there can
be two absolutely different instances of WebLogic whose URIs will be 
	deployer:WebLogic:http://localhost:7001
JBoss in its default configuration has three instances which are set up to port
8080.
To resolve the conflict, the plugin developer has to introduce an additional
level of abstraction to make all instances URIs look different for j2eeserver,
while supplying a valid URI for the server jsr-88 classes.
Here the suggestion is that a more abstract identification method should be
used, so that these conflicts never occur.
Comment 1 Sherold Dev 2005-05-23 15:29:51 UTC
TM -> 4.2.
Comment 2 Sherold Dev 2005-10-23 21:06:32 UTC
This is not a real DEFECT -> TASK.
Comment 3 Petr Blaha 2006-03-13 13:51:05 UTC
TM 5.0 -> TBD


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