This is part of issue b) in Konstantin's comments in TOMCAT-NEXT.txt
Konstantin has accurately summed up the issues with basing the API on
DirContext as:
- Unnecessary objects, e.g. NamingException instead of null.
- Too many methods. Name vs. String. list() vs. listBindings().
- Limited API. As a workaround, there are non-standard methods that
are implemented on BaseDirContext instead, e.g. getRealPath(),
doListBindings(..).
I do not believe that the resources implementation should be based
around DirContext. It adds a lot of unnecessary clutter and complexity
to something that is already fairly complex. A comparison of the
DirContext based implementation objects with the new implementation
demonstrates - in my view - how much simpler this could be.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
