Opened 17 years ago
Closed 17 years ago
#657 closed defect (duplicate)
Plug-in wizard may selects wrong plug-in if only one of several plug-ins can be used in a given context
Reported by: | Jari Häkkinen | Owned by: | Martin Svensson |
---|---|---|---|
Priority: | critical | Milestone: | BASE 2.4 |
Component: | web | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
the affymetrix INTENSITY plug-ins are not recognized. When "New root bioassayset" is selected the dialog goes direct into 2-channel mode, that is requests a formula for importing data.
More info avaialble now. When I added another INTENSITY plugin for Affymetrix, the dialog for selecting a plugin pops up. I am allowed to select either Plier of RMAExpress.
Yes, removing Plier makes the dialog going directly to the formula dialog whereas I would like to see RMAExpress.
Change History (7)
comment:1 by , 17 years ago
Description: | modified (diff) |
---|---|
Priority: | blocker → critical |
comment:2 by , 17 years ago
Description: | modified (diff) |
---|
comment:3 by , 17 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 17 years ago
comment:5 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:6 by , 17 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Summary: | Affymetrix experiments cannot create a "New root bioassayset" since ... → Plug-in wizard may selects wrong plug-in if only one of several plug-ins can be used in a given context |
The checked in changes fixes the problem, but it also destroys the fix for #625. The ContextUtil.checkContext() method must return a ContextResult object for each plug-in that is tested.
The problem in this ticket is caused by the web client that (incorrectly) assumes that if only one plug-in can be used then it is the first one returned in the list (www/common/plugins/index.jsp line 180-190).
comment:7 by , 17 years ago
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
Should be fixed as part of #625.
(In [3534]) References #657