** Changed in: zorba
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/988417
Title:
block internal modules
Status in Zorba - The XQuery Processor:
F
** Changed in: zorba
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/988417
Title:
block internal modules
Status in Zorba - The XQuery Processor:
Fi
** Changed in: zorba
Milestone: None => 2.5
** Changed in: zorba
Status: New => In Progress
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/988417
Title:
block internal modules
Statu
I saw the branch merge proposal before I noticed this bug, so I'll copy
my comment from there:
I don't like that this mechanism is so different to the way you block
non-internal modules (using a URIMapper with DENY_ACCESS). While it
would be a bit less efficient, it would be more consistent to cal
** Description changed:
- If on wants to limit the choice of of available modules for a user, this
- is very easy for external modules. One simply registers an URIMapper
- that disallows access to certain modules. However, this does not work
- for Zorba's internal modules as those a not resolved v
5 matches
Mail list logo
