Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 388868

Summary: Global search: Regular expression search escapes some special chars used as part of the reg ex.
Product: [ECD] Orion Reporter: libing wang <libingw>
Component: ClientAssignee: libing wang <libingw>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: john.arthorne, mamacdon
Version: 0.5   
Target Milestone: 1.0 M2   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description libing wang CLA 2012-09-05 13:56:04 EDT 
By using the new reg ex global search, you can use the crawler to search reg ex in multi-files. But there was a special char escape API only for lucene engine, which  accidentally escaped the reg ex special chars. E.g. b\SettingsContainer\b ==> b\\SettingsContainer\\b. This will prevent the reg ex from performing properly.
Need to revisit this lucene escape API
Comment 1 libing wang CLA 2012-09-06 17:28:29 EDT 
Also, we cant hard code "?depth=1" when fetching children at the start point.
From the search.html hash, we got the search location without "?depth=1". We should always use the meta data on the search location and get .ChildrenLocation from the meta data. 

In the file root case, where meta data is not supported, we should use the search location directly.(I found that orion file service impl does not support file meta data on root but other file systems like html5 does)