Costin,
This is getting off topic from my original request.
(And I am partly responsible ;-)
My proposal is for adding thr XML policy code to the current
existing Tomcat 4 HEAD branch.
I would like to commit the code to CVS. Building Tomcat with this
support is optional and can be left out of
Costin Manolache wrote:
> Glenn,
>
> As a new feature, you need a majority of votes and at least 3 +1.
> My vote is -1 ( but is not a veto ). Only commits can be vetoed,
> and I'll probably do so if castor is used - all tomcat is using
> digester style for xml processing, and we have a proposal t
Jean-Francois Arcand wrote:
>
>
> Glenn Nielsen wrote:
>
>> The JVM itself anticipated a need for alternative application specific
>> Policy
>> implementations and has the hooks for doing it.
>>
>> Are you aware of anyone working on a new standard? Is there a JSR?
>
>
>
> [FYI]
> JSR 115
; Are you aware of anyone working on a new standard? Is there a JSR?
[FYI]
JSR 115
(http://jcp.org/aboutJava/communityprocess/first/jsr115/index.html) Java
Authorization Contract for Container is in that direction (for
expressing Web Permissions and for moving away from the *.policy file
forma
Remy Maucherat wrote:
> Costin Manolache wrote:
>
>> Glenn Nielsen wrote:
>>
>>
>>>
>>> [ ] commit XML Policy source to jakarta-tomcat-4.0 HEAD
>>> and include it in future release of Tomcat 4.1.x
>>> [X] commit to CVS but don't add to the next release
>>> [ ] create a Tomcat 4.2 dev
Costin Manolache wrote:
> Glenn Nielsen wrote:
>
>
>>
>> [ ] commit XML Policy source to jakarta-tomcat-4.0 HEAD
>> and include it in future release of Tomcat 4.1.x
>> [X] commit to CVS but don't add to the next release
>> [ ] create a Tomcat 4.2 development branch and commit there (
Comments intermixed below.
Costin Manolache wrote:
> Glenn Nielsen wrote:
>
>
>>Tomcat SecurityManager XML Policy configuration
>>---
>>
>>I have finished implementing support within Tomcat for using XML based
>>security policy
>>files. This was prop
