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 45410 - [Study] More info about context path
Summary: [Study] More info about context path
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Freeform (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Konecny
URL: http://beetle.czech.sun.com/modules/w...
Keywords: UI
Depends on:
Blocks:
 
Reported: 2004-06-23 09:17 UTC by Petr Blaha
Modified: 2016-07-07 08:56 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Blaha 2004-06-23 09:17:24 UTC
Most of the participants didn't understand the
meaning of the 'Context path' field. Add a brief
help in the bottom of the panel explaining what is
the purpose of the Context path field (the purpose
is that the debugger needs it to be able to debug
webmodules).
Comment 1 Petr Jiricka 2005-02-22 12:49:35 UTC
Still not very clear in 4.1. Jano, any concrete suggestion, please?
Comment 2 Jiri Kopsa 2005-03-18 18:45:42 UTC
I have several (crucial) questions about this field:
- Why isn't the value read from the deployment descriptors?
- Why does the IDE need it, if the deployment is driven by the user provided
deployment descriptor and Ant task?
Comment 3 Radko Najman 2005-03-18 19:10:31 UTC
Q: Why isn't the value read from the deployment descriptors?
A: There is no way how to get (and also set) the context path from the
deployment descriptor in freeform project. That's why we need to ask the user
for it.

Q: Why does the IDE need it, if the deployment is driven by the user provided
deployment descriptor and Ant task?
A: The purpose is written in the first comment. It is necessary to set the
context path to be able to debug the web application - the debugger needs to
know the application to attach and for this it needs to know the context path.
Comment 4 Jiri Kopsa 2005-03-18 19:41:56 UTC
Re: Q1: I believe there is theoretically a way to do that, since we are doing it
in classic projects - but unfortunatel not in the "New Web App With Existing
Sources" wizard. 

The only difference is that we don't know the location of server specific
deployment descriptor. But could the file be found in the project folder (in
promo xyz)?

For 4.1. we might fix this with a label (which is problematic because we are out
of screen estate - due to Tiger vs J2EE 1.4 issue) or fix in promo F in some
smart way.

Re: Q2: Ok, I though that the debugger is just attaching to the server (to the
JVM), not to the application.

Comment 5 Pavel Buzek 2005-03-19 01:16:25 UTC
Re "can the server specific DD be found". Well, probably in some cases. One
issue is you do not even know what type of server the user is using and thus
what is the file name of server specific DD. Then you do not know how to read
it. If it is one of the server types that we support (and this is questionable,
as I would expect one motivation to use freeform would be that you can deploy
from Ant to other servers) and if there is a server specific file only for that
one type of server (this would be typical) the we can in theory ask the plugin
to read the file and give us context path.
Comment 6 Jiri Kopsa 2005-04-01 12:42:52 UTC
So far we have not concluded on the purpose/affect of this field in the wizards
"New Web Application with Existing Sources" and "New Web Application with
Existing Ant Script.
Comment 7 Jaroslav Pospisil 2006-03-13 13:43:35 UTC
TM 5.0->TBD
Comment 8 Petr Jiricka 2006-07-26 12:31:36 UTC
Old issue, not clear how to solve, changing to TASK.
Comment 9 Martin Balin 2016-07-07 08:56:19 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss