Project:
| View Revisions: Issue #31529 | [ Back to Issue ] | ||
| Summary | 0031529: Extension needed in SessionLogin.java to save new columns values when saving new sessions | ||
| Revision | 2015-11-19 10:24 by AugustoMauch | ||
| Description | There are cases where is necessary to find some sessions (from ad_session) depending on the organization in which was created. Now, all sessions are saved with '*' organization. There are at least two ways to address this problem: - Avoid always using the '*' organization when a session is created, and instead use the organization included in the parameters of the request - Include a new column in the ad_session table, set it to the proper organization when the session is created and then use it to retrieve the session that belong to a certain organization. Probably the second option is less risky. There might be code that is assuming that ad_org_id column of the sessions will always use the '*' organization, so the first option could have unexpected consequences. The second option would require to extend SessionLogin to initialize column defined in other modules, as the development that requires will be part of the posterminal module. |
||
| Revision | 2015-11-19 10:14 by AugustoMauch | ||
| Description | There are cases where is necessary to find some sessions (from ad_session) depending on the organization in which was created. Now, all sessions are saved with '*' organization. To solve this problem, the solution is to create a new column with the store organization value. This development is needed for Posterminal module, so code injection is needed in SessionLogin.java class to save the new organization value. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |