| Summary: | JSPSearchSupport & JSSearchSupport should not consider derived resources | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Source Editing | Reporter: | Patric Rufflar <patric> | ||||
| Component: | jst.jsp | Assignee: | Nick Sandonato <nsand.dev> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Nick Sandonato <nsand.dev> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | itewksbu, thatnitind | ||||
| Version: | unspecified | Flags: | thatnitind:
review+
|
||||
| Target Milestone: | 3.2.4 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Patric Rufflar
Created attachment 191682 [details]
patch
Thanks for opening the defect. However, this doesn't quite fit the definition of "critical" which is used to indicate crashes, data loss and severe memory leaks. Wouldn't IPath.isRoot() be better than path.toString().equals("/")?
(In reply to comment #3) > Wouldn't IPath.isRoot() be better than path.toString().equals("/")? Thats from my original code. And its probably there because I did not know of "isRoot". I wouldnt see any problem with changing it to isRoot assuming it does the same thing. Code released. Nick, I tested your patch - it seems that JSIndexManager is still processing derived resources. (JSPIndexManager is now fine) (In reply to comment #6) > Nick, > > I tested your patch - > it seems that JSIndexManager is still processing derived resources. > (JSPIndexManager is now fine) Patric, Right now, the JSIndexManager is still not based on the AbstractIndexManager, which we were able to apply this fix to. A separate bug would need to be opened against the JSDT as their index implementation is different. Done: bug 340774 |