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 55376 - can't add 'localhost' j2ee server if user has no write permissions on local instance
Summary: can't add 'localhost' j2ee server if user has no write permissions on local i...
Status: RESOLVED DUPLICATE of bug 55377
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-22 21:46 UTC by athompson
Modified: 2005-07-21 08:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description athompson 2005-02-22 21:46:39 UTC
linux (gentoo)
jdk-1.5
daily 20050221

1. on linux, install the Sun app server as root
2. become  a regular user
3. start netbeans with a clean install
4. Tools-->Server Manager
5. Add Server
6. select "Sun Java System Application Server 8",
hit Next
7. specify the location of the app server and hit Next
  (because the user does not have write
permission, the 'Domain Folder' and 'Domain'
fields are disabled. the domain field is blank.
this should be OK since i have the server admin
password)
8! try to use 'localhost' as the server location.
i guess the IDE assumes that you want to access
the server directly, so it won't allow you hit
'Finish' until the domain is filled in. but the
Domain field is disabled because the user doesn't
have write permission on the install directory.

the workaround is to specify an alias for the
computer, and use that instead of 'localhost'. it
would probably be better and less confusing to
have the user explicitly select whether he wants
to use the local instance directly or the remote
interface instead of trying to guess this by
devining what the user meant when she specified
'localhost'.

err...that's about as clear as i cant make it.
Comment 1 Petr Jiricka 2005-02-23 10:22:17 UTC
Looks like a duplicate of 53482.

Comment 2 athompson 2005-02-23 19:24:25 UTC
not quite. i'm trying to use the server as you would a remote server
that happens to be on the localhost.
Comment 3 Vince Kraemer 2005-02-24 06:06:35 UTC
I am marking this as a dup of 55377.  The priority is higher and the
steps to reproduce are "close enough".

I also don't want to have to add the same data to two "diffferent"
defects, when the fix for 55377 should cover both.

*** This issue has been marked as a duplicate of 55377 ***
Comment 4 athompson 2005-02-24 14:37:38 UTC
yup. just keep in mind that the reason i filed these as separate
issues is that i consider this to be more of a UI problem--there is
currently no way to specify how you want to access the app server
(directly or through the remote interface) if you specify 'localhost'.
it automatically assumes you want to access things directly.
Comment 5 Vince Kraemer 2005-02-24 16:06:08 UTC
The ui is not going to change substantially.  It is on the radar for a
rewrite in promo f.
Comment 6 Vince Kraemer 2005-02-24 16:13:35 UTC
I entered 55505 to track the UI spec revision.