You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/06/19 09:21:47 UTC
[jira] [Created] (OODT-251) Remove generation of (and dependency
on) module constants in the core library
Remove generation of (and dependency on) module constants in the core library
-----------------------------------------------------------------------------
Key: OODT-251
URL: https://issues.apache.org/jira/browse/OODT-251
Project: OODT
Issue Type: Improvement
Components: balance
Reporter: Andrew Hart
Fix For: 0.4
Since Balance 0.2 (internal JPL release), it has been possible to include content from multiple modules in a single response. This means that the old method of referring to module paths via the constant values (MODULE, MODULE_ROOT, and MODULE_STATIC) no longer work predictably. Since constants can not (by definition) be redefined during the lifetime of a request, a more flexible method is needed to represent module context.
The Application::loadModule() function was introduced some time back to address this, however, the constants were never removed, and there are places where the old and new methods are still used side by side. We need to remove the constants from the core, and update modules to use only the loadModule() syntax.
This issue addresses the problem for the core library. Others will follow for individual modules.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-251) Remove generation of (and dependency
on) module constants in the core library
Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-251:
-----------------------------------
- push out to 0.5
> Remove generation of (and dependency on) module constants in the core library
> -----------------------------------------------------------------------------
>
> Key: OODT-251
> URL: https://issues.apache.org/jira/browse/OODT-251
> Project: OODT
> Issue Type: Improvement
> Components: balance
> Reporter: Andrew Hart
> Fix For: 0.5
>
>
> Since Balance 0.2 (internal JPL release), it has been possible to include content from multiple modules in a single response. This means that the old method of referring to module paths via the constant values (MODULE, MODULE_ROOT, and MODULE_STATIC) no longer work predictably. Since constants can not (by definition) be redefined during the lifetime of a request, a more flexible method is needed to represent module context.
> The Application::loadModule() function was introduced some time back to address this, however, the constants were never removed, and there are places where the old and new methods are still used side by side. We need to remove the constants from the core, and update modules to use only the loadModule() syntax.
> This issue addresses the problem for the core library. Others will follow for individual modules.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-251) Remove generation of (and dependency
on) module constants in the core library
Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-251:
-----------------------------------
Fix Version/s: (was: 0.4)
0.5
- push to 0.5
> Remove generation of (and dependency on) module constants in the core library
> -----------------------------------------------------------------------------
>
> Key: OODT-251
> URL: https://issues.apache.org/jira/browse/OODT-251
> Project: OODT
> Issue Type: Improvement
> Components: balance
> Reporter: Andrew Hart
> Fix For: 0.5
>
>
> Since Balance 0.2 (internal JPL release), it has been possible to include content from multiple modules in a single response. This means that the old method of referring to module paths via the constant values (MODULE, MODULE_ROOT, and MODULE_STATIC) no longer work predictably. Since constants can not (by definition) be redefined during the lifetime of a request, a more flexible method is needed to represent module context.
> The Application::loadModule() function was introduced some time back to address this, however, the constants were never removed, and there are places where the old and new methods are still used side by side. We need to remove the constants from the core, and update modules to use only the loadModule() syntax.
> This issue addresses the problem for the core library. Others will follow for individual modules.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira