Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#221 closed task (fixed)

Configure GenePattern server

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: critical Milestone: ZZ GenePattern integration v1.0
Component: net.sf.basedb.genepattern Keywords:
Cc:

Description

Each user must be able to configure which GenePattern? server to use and the login/password required to access it.

It would be nice for a user to specify several servers and then be able to select which one to use for a certain calculation. One of the servers could be marked as default.

I think this can go into the Extensions menu in a similar fashion as for the MeV launcher.

Change History (5)

comment:1 Changed 10 years ago by Nicklas Nordborg

Resolution: fixed
Status: newclosed

(In [1102]) Fixes #221: Configure GenePattern? server

comment:2 Changed 10 years ago by Nicklas Nordborg

Resolution: fixed
Status: closedreopened

It will not work to store the GenePattern? options with SessionControl.setUserClientSetting() since those settings are only available in the web client and not available when executing the a plug-in. In principle it should work to use SessionControl.setUserDefaultSetting() instead, but there is a problem that the settings are not written to the database until the user logs out which means that new and modified GenePattern? server settings are not visible to the plug-in unless the user first logs out and then log in again.

comment:3 Changed 10 years ago by Nicklas Nordborg

Resolution: fixed
Status: reopenedclosed

(In [1108]) Fixes #221: Configure GenePattern? server

The settings are now saved to the databas as user default settings.

comment:4 Changed 10 years ago by Nicklas Nordborg

(In [1117]) References #221: Configure GenePattern? server

Changed the AJAX calls to a new servlet. Now requires BASE 2.13 since that depends on new functionality in BASE.

comment:5 Changed 10 years ago by Nicklas Nordborg

(In [1126]) References #221: Configure GenePattern? server

Added field for URL to BASE. This seems to be the easiest way to let the plug-in know about the BASE web server. Also moved the "test" button back to it's previous location.

Note: See TracTickets for help on using tickets.