Task #6893 (closed)
Opened 13 years ago
Closed 12 years ago
changeActiveGroup vs. setGroupForSession
| Reported by: | atarkowska | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | n.a. |
| Component: | OmeroPy | Version: | n.a. |
| Keywords: | n.a. | Cc: | python-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
There is only local implementation of changing active group in webclient_gateway.py. There should be one single method on the omero.gateway to do it.
In stead of pushing changeActiveGroup we could possibly use setGroupForSession. But current implementation does not work as expected. setGroupForSession updates omero session, but BlitzGateway? fields. It cause mismatch between those two objects, while you call BlitzGateway?.getExentContext(), getUser(), etc. again.
Change History (2)
comment:1 Changed 13 years ago by cneves
comment:2 Changed 12 years ago by atarkowska
- Resolution set to duplicate
- Status changed from new to closed
duplicated in 2339
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Ola, please add a unit test that describes what you expect from that method and pass the ticket to me.