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 129896 - navigator window goes blank or f:view for JSP
Summary: navigator window goes blank or f:view for JSP
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: issues@javaee
URL:
Keywords:
: 105111 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-03-12 13:40 UTC by soag
Modified: 2016-07-07 08:56 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description soag 2008-03-12 13:40:30 UTC
Windows navigator Issue, that occurs constantly, is as it follows, the components are lost at some point and insted of
them apperars f:view, even more on other ocassions this component list are lost completely, the trace is on the log, and
is as it follows, the olny way to recover form this error is restarting the netbeans.
Comment 1 _ potingwu 2008-03-12 16:54:11 UTC
What do you mean "component lost, ... component list are lost completely, ..."? Assign to Component for further
investigation.
Comment 2 _ krystyna 2008-03-12 19:01:19 UTC
I think the reporter is speaking about the Navigator window, our old 
Outline window, and I see that sometimes it goes blank for the JSP
view, especially if switching from Java -> Jsp view. Is this correct,
reporter? Please confirm. (If so, we should reassign to 
core/navigator )
Comment 3 soag 2008-03-13 15:00:24 UTC
 krystyna, this is correct, the window navigator is the old outline window, and when return to design view it goes blank
or appears f:view. 
Comment 4 _ krystyna 2008-03-13 17:22:39 UTC
I have reproduced this in dev build 0311 as well tab switching from
Design -> Java -> JSP. Reassigning to core navigator.
Comment 5 Lukas Hasik 2008-03-14 11:40:05 UTC
reassigning to owner of navigator component.

Krystyna, do you have reproducible scenario? Haven't a similar issue been fixed for 6.0.1?
Comment 6 David Simonek 2008-03-14 15:39:08 UTC
actually duplicate of 129261. Please write reproducible steps there, thanks.

*** This issue has been marked as a duplicate of 129261 ***
Comment 7 _ krystyna 2008-03-17 20:06:43 UTC
Here are reproducible directions from NetBeans IDE Dev (Build 200803141205):
1. create a VW project - don't drop any components
2. tab click on JSP view
3. tab click on Java view (let all members get populated)
4. tab click on JSP view
>Navigator view is empty for the JSP view

5. return to design view and drag and drop one or two components, tab switch to JSP view
>Navigator view is still empty for the JSP view

6. Close and restart IDE to see the JSP view


Original reporter's scenario is likely different, but this is best way
for me to reproduce. I have seen the Navigator view go blank for JSP 
view before.
Comment 8 David Simonek 2008-03-18 10:34:51 UTC
As I said in 129261, I was wrong - this is different bug and it's not in Navigator infrastructure, but in JSP view
itself probably - it just fails to display JSP structure after steps that krystyna wrote abover.
See further explanation in 129261, thanks.
Comment 9 Peter Zavadsky 2008-03-18 17:08:07 UTC
So this belongs to JSP navigator view (no designer involved). Passing there.
Comment 10 Marek Fukala 2008-03-19 11:36:30 UTC
This is a problem of missing JSP navigator feature. After first opening of a JSP page with custom tags the text is lexed
without the information from jsp parser so the custom tags are lexed as html tags and hence they appear in the navigator
view as html nodes. Then, after some time, the jsp parser finishes and provides the info about custom tags in the page.
The document is relexed and the tags in the editor get colored like jsp tags. The navigator then refreshes its content
and since there are just jsp nodes, no content is provided.

This is quite tricky and more users complained about it.

Please also note issue #130348 - "GSF Source doesn't listenen on TokenHierarchy" which make it even worser.
Comment 11 Marek Fukala 2008-03-19 14:22:07 UTC
We do not have time much time now so I originally thought about a quick workaround - disabling the navigator for visual
web files complely. But I realized that the Visual JSP does have the same mimetype as JSP so it is not easily possible
to distinguish them from the GSF perspective. I can think of more ways of fixing this, but they are mostly workarounds
but, and they seem to be of similar complexity as copy-pasting and adjusting the html navigator code to jsp.

I personally consider this bug as very confusing even the real impact is minimal.

Comment 12 soag 2008-03-20 14:03:19 UTC
mfukala , thanks for the reply, however we disagree, because we are facing a project with the netbeans suite based in
visual web pack (JSF) and EJB 3.0 ,to gain full control and features we must use the navigator panel, which allow us to
edit mainly visual properties on the behaviour of the application.

I.e. on the NB 5.5.1 we use screen with panes which are overposed (invisible) because it helps to give more funcionality
in less navigation pages, and the only way to set this properties to this component is selecting it on the outline
window (navigator window on netbeans 6).
Comment 13 jiai 2008-03-22 16:05:10 UTC
Same problem here like "soag" described. You can't deactivate the Navigator view for VW!!!
Comment 14 Marek Fukala 2008-03-27 20:15:24 UTC
"soag", disabling the JSP navigator panel means disabling the panel, not the navigator itself. If you have any other
impl. of the navigator bound to the JSP mimetype they will remain.
Comment 15 Marek Fukala 2008-04-01 19:16:52 UTC
I would like to hear QE opinion about this issue - do you consider this as showstopper in 6.1? I personally think the
issue is nasty, but I wouldn't say showstopper. Involved people, please speak up and set the priority and milestone if
you  consider this as critical problem from your point of view. For now, I am setting TM to dev (not to fix in 6.1).
Comment 16 _ krystyna 2008-04-01 21:44:34 UTC
I think this is a showstopper and the users are telling us this is essential for 
them: see desc 13, 14. VW has a high dependency on the Navigator as the only place from
which to configure some of the hidden and non-visible components. I would also like to note that there
are similar issue #129261 and it's duplicate issue #130826. Thanks.
Comment 17 Martin Schovanek 2008-04-02 13:05:43 UTC
I would prefer to fix it for 6.1 because it is nasty issue reported by user. Next it breaks lot of WS automated tests.
Comment 18 Marek Fukala 2008-04-02 16:30:23 UTC
Martine, I do not understand how it can break tests. Test of what, navigator? Explain it please. OTOH I am not saying I
am not going to fix it, I just want to be sure what is your problem.

Krys, As I said in my record from Mar 27 the problems described in records #13 and 14 are likely not related to what
this issue is about. OR I do not understand the point. The users haven't replied to my comment yet. Do you know them?
Comment 19 _ krystyna 2008-04-02 18:10:15 UTC
No Marek, I don't know the users. You are correct, I see your point. JSP Navigator view
is of critical use for VW as Design view Navigator that is. I take back my comment
then about it being a showstopper.
Comment 20 _ krystyna 2008-04-02 18:21:05 UTC
Meant to say: it is when VW project is in Design view that Navigator is critical.
This case is JSP view and not critical. Testing in 6.0.1 it looks like there is no
Navigator view for JSP for VW project or regular web project.
Comment 21 Martin Schovanek 2008-04-02 20:50:30 UTC
After discussion with Marek agree that this issue is not stopper.
Comment 22 soag 2008-04-02 21:03:52 UTC
Thanks for the reply, I believe that what Krystyna  says "VW has a high dependency on the Navigator as the only place from
which to configure some of the hidden and non-visible components" is the most accurate description of the use we are
giving .
As well as I believe that if this issues is bein fixed for version 6.1 can give more potenial to the newer addons as
well as the funcionality inherited of the previous versions.

We will be exited witing for the 6.1 release

Kind regards.
Comment 23 Marek Fukala 2008-04-03 17:24:48 UTC
"VW has a high dependency on the Navigator as the only place from
which to configure some of the hidden and non-visible components" 

I guess you mean VW navigator, not the RAW JSP one. Is that right? I personally do not find the RAW view (tree of tag
nodes) of JSP or HTML as much usefull, it is easier to navigate in the code than in the outline IMHO.
Comment 24 _ krystyna 2008-04-03 18:53:36 UTC
Yes, agree: the JSP view of Navigator is not useful to VW proejcts. 
VW Navigator when the Designer page is surfaced is most useful to
VW projects. By the way, Marek, you can bring this down to P3.
Comment 25 soag 2008-04-04 14:41:18 UTC
Yes, I always referred to VW projects, VW window Navigator and Design view
Comment 26 Marek Fukala 2008-09-25 19:07:05 UTC
Summary:
1) the tree like navigator provided by GSF DOESN'T show jsp tag node, but it shows html tag nodes. 
2) after file opening it take some time before jsp parser finishes and provides a list of jsp custom tag prefixes
3) before that all jsp custom tags are in fact html tags (from the lexer point of view) so they ARE visible in the
navigator 
4) once the parser provides the list of prefixes, the whole document is relexed and the custom tags become jsp tags =>
they disappear from the navigator.

There is also issue #130348 (GSF Source doesn't listenen on TokenHierarchy) which may also cause some unpleasant behavior.

From my point of view there is no bug, the navigator doesn't show the jsp nodes once opened except the short time just
before opening.

There is no elegant workaround to this IMHO very minor issue which doesn't influence VW users much since they see the VW
navigator by default. 

Proper fix is to provide the nodes for jsp tag, which is a feature.
Comment 27 Marek Fukala 2008-10-13 11:29:26 UTC
*** Issue 105111 has been marked as a duplicate of this issue. ***
Comment 28 Martin Balin 2016-07-07 08:56:48 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