2012/9/27 Mark Thomas ma...@apache.org:
On 19/09/2012 20:46, Mark Thomas wrote:
On 09/09/2012 19:50, Mark Thomas wrote:
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:
-
On 27/09/2012 10:09, Konstantin Kolinko wrote:
I am sure that DirContext is not the right API to define resources.
At best is could be a [deprecated] view/proxy to the actual implementation.
The only benefit I see in using this API by someone is that the API
itself is defined in javax.*
On Thu, Sep 27, 2012 at 2:14 AM, Mark Thomas ma...@apache.org wrote:
On 27/09/2012 10:09, Konstantin Kolinko wrote:
I am sure that DirContext is not the right API to define resources.
At best is could be a [deprecated] view/proxy to the actual
implementation.
The only benefit I see in
Costin Manolache cos...@gmail.com wrote:
On Thu, Sep 27, 2012 at 2:14 AM, Mark Thomas ma...@apache.org wrote:
On 27/09/2012 10:09, Konstantin Kolinko wrote:
I am sure that DirContext is not the right API to define resources.
At best is could be a [deprecated] view/proxy to the actual
On Thu, 2012-09-27 at 07:34 -0700, Costin Manolache wrote:
One use for a resource API is if it provides different backends - like
Hadoop filesystem abstraction
does. Than you could serve from hdfs/db/etc, and someone could use the same
api in deploy tools
or general programs.
One of the
On Thu, Sep 27, 2012 at 10:54 AM, Remy Maucherat r...@apache.org wrote:
On Thu, 2012-09-27 at 07:34 -0700, Costin Manolache wrote:
One use for a resource API is if it provides different backends - like
Hadoop filesystem abstraction
does. Than you could serve from hdfs/db/etc, and someone
On Thu, Sep 27, 2012 at 10:18 AM, Mark Thomas ma...@apache.org wrote:
Costin Manolache cos...@gmail.com wrote:
On Thu, Sep 27, 2012 at 2:14 AM, Mark Thomas ma...@apache.org wrote:
On 27/09/2012 10:09, Konstantin Kolinko wrote:
I am sure that DirContext is not the right API to define
On 19/09/2012 20:46, Mark Thomas wrote:
On 09/09/2012 19:50, Mark Thomas wrote:
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
On 09/09/2012 19:50, Mark Thomas wrote:
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
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().
-
10 matches
Mail list logo