Community
Participate
Working Groups
Build ID: i5 Steps To Reproduce: 1. Open Log Import dialog. Click Add... 2. Type a string into the Filters text box. Users in testing expected to be able to type WebSphere and get all the WebSphere adapters, but WebSphere did not show up because the adapter name was "IBM WebSphere". Given that we cannot control the naming, it makes more sense to search the entire string. This is an important function given the number of adapters, but the issue above makes it significantly less useful.
IBM Adapters are not shipped in TPTP product. Please track defect with product that packages IBM Adapters.
I misunderstood the problem.
I tested this on the I5 RCP and typed in "Web". All the WebSphere adapters appeared in the list. It does search the whole string.
(In reply to comment #3) > I tested this on the I5 RCP and typed in "Web". All the WebSphere adapters > appeared in the list. It does search the whole string. > Verified with Malcom that the filter works as expected.
We are both right. The test does work, but only when "Show categories" is not selected. When "Show categories" is selected, "web" does not bring up "WebSphere, it only brings up "BEA". This says that it is not searching same fields in both cases, which was the expected behavior. I am not sure what it is searching in this case, since BEA does not have web in the title. The expected behavior would be to get the same results whether or not the user has "Show Categories" selected or not (Obviously, they should be organized in categories, if it is selected though). This would mean that the filter should search two things: 1. The category text 2. The Adapter name text. Maybe there are some other fields that are relevant to search as well.
Show categories is not working in my driver so I'm not able to test it myself. However, if what Jeff is describing is true, I agree with him that it should be fixed.
Thanks Malcom for verifying the problem. Target to be fixed in i3. Alex, is there any existing defect for the show category bug?
This function was working in TPTP4.2, so this seems to be a regression introduced recently. I have the feeling that it is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=153758. Will investigate.
Changed name since the original title no longer reflects the issue.
Increasing priority as this should be fixed in 4.4.
Fixed.
Verified with LTA-RCP build from 5-11