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 29818 - "Execute" action for JSP should be modified for resources in WEB-INF
Summary: "Execute" action for JSP should be modified for resources in WEB-INF
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Pisl
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2003-01-06 19:44 UTC by Ana.von Klopp
Modified: 2016-07-07 08:55 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ana.von Klopp 2003-01-06 19:44:50 UTC 
If the developer keeps JSPs in WEB-INF/lib, the
execute action currently works but causes the
browser to send a request to
http://hostname:port/context/WEB-INF/... which
obviously doesn't work. 

We should either not provide an execute action on
such JSPs, or we should ask the user to specify a
URL such that it will cause the request dispatcher
to execute the JSP in question. (HIE action). 

We should also explain what the valid locations
for JSPs are, and what the consequences are of
placing a JSP in the module docroot or under
WEB-INF in the new JSP wizard.
Comment 1 _ rkubacki 2003-02-17 14:20:37 UTC 
While anything begining with /WEB-INF is invalid we can use web module
URI. This is not optimal but can be done without extra dialog or a new
property or similar. Thoughts?
Comment 2 Ana.von Klopp 2003-02-19 20:09:53 UTC 
If Ann is OK with this, we can go with the web module root 
for now. 




For projects we need to discuss whether to keep execution 
of individual JSPs at all. In a front controller 
application, such execution usually doesn't work. If a 
developer needs a shortcut to execute a specific resource 
they'd be better of using the HTTP Monitor, or bookmarks in 
the browser.
Comment 3 Ana.von Klopp 2003-12-02 21:42:53 UTC 
My preferred solution is to ask the user for a URL in that case (as
opposed to just executing the web module root), since that will send a
clear signal that those JSPs are special.
Comment 4 Ann Sunhachawee 2003-12-03 01:33:10 UTC 
I'd propose that we actually remove the "execute" context menuitems on
jsps in WEB-INF. 

Here's the reasoning:
Long term, I think that with a projects or build system concept it
should be that the user runs a web module and perhaps files that make
sense to run. I understand that it could be "educational" to show a
info dialog, but I'd draw the line of allowing them to enter a URL to
run - since it prob is not the user's intention to run the web module
when they are choosing the "Run/Execute" context menu off a particular
JSP. 

Competitors Notes:
It looks like Websphere AD brings up some warning (*"Couldn't find
anything to deploy") whereas JBuilder 8 does not offer the option to
run jsps within the WEB-INF.
Comment 5 Petr Jiricka 2003-12-03 09:15:07 UTC 
I think the usability motivation of the execute action on JSPs in
WEB-INF is that when the user is editing a page (any page) in the
editor, she should be able to deploy the web module and test the page
(whatever that means) using a single keyboard shortcut associated with
the "execute" action. She should not be forced to go to the main menu
or the popup menu and select "Run Project" or anything.
Comment 6 Martin Balin 2016-07-07 08:55:41 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