org.apache.tomcat.security.file.FileRealmTool in the "j2ee" tree

["Craig R. McClanahan" <Cr...@eng.sun.com>]

This tool was part of an experimental approach to building XML files for
storing authentication information, and is incompatible with the
solution currently implemented in 3.1beta1.  To avoid user confusion, I
propose to remove this source file (and the others in the
org.package.tomcat.security.file package) from the source code
repository.  What do you think?

Craig McClanahan

Re: org.apache.tomcat.security.file.FileRealmTool in the "j2ee" tree

[Hans Bergsten <ha...@gefionsoftware.com>]

"Craig R. McClanahan" wrote:
> 
> This tool was part of an experimental approach to building XML files for
> storing authentication information, and is incompatible with the
> solution currently implemented in 3.1beta1.  To avoid user confusion, I
> propose to remove this source file (and the others in the
> org.package.tomcat.security.file package) from the source code
> repository.  What do you think?

+1, or if there's a chance it will be used eventually, add a very clear
comment in the source and README (as if anyone does ;-) that it's not
currently used.

Hans
-- 
Hans Bergsten		hans@gefionsoftware.com
Gefion Software		http://www.gefionsoftware.com

Re: org.apache.tomcat.security.file.FileRealmTool in the "j2ee" tree

[Costin Manolache <co...@eng.sun.com>]

"Craig R. McClanahan" wrote:

> This tool was part of an experimental approach to building XML files for
> storing authentication information, and is incompatible with the
> solution currently implemented in 3.1beta1.  To avoid user confusion, I
> propose to remove this source file (and the others in the
> org.package.tomcat.security.file package) from the source code
> repository.  What do you think?

After 3.1 is released ?

I would rather add a README - the j2ee directory is not used, but we keep it
because it contains many interesting ideas. We can remove it if it creates
confusion, but I don't think we should do fast moves before release.

Costin