+1 for security reasons
Filip
Mark Thomas wrote:
All,
I'd like to remove the invoker servlet entirely from trunk (and hence TC7.x
onwards) and deprecate it in 6.0.x.
Any objections?
Mark
-
To unsubscribe, e-mail: [EMAIL PR
Costin Manolache wrote:
> +0
>
> I kind of liked the functionality ( i.e. write a servlet and have it 'just
> work', without web.xml ).
> And the annotations have their own problems ( scanning all the classes ).
V3 of the servlet spec should include the ability to add servlet and filter
mappings
+0
I kind of liked the functionality ( i.e. write a servlet and have it 'just
work', without web.xml ).
And the annotations have their own problems ( scanning all the classes ).
But to turn this around to my favorite subject - wouldn't be better to
exclude it from the
release ? Maybe this and the
On Tue, Oct 28, 2008 at 6:56 AM, Mark Thomas <[EMAIL PROTECTED]> wrote:
> I'd like to remove the invoker servlet entirely from trunk (and hence TC7.x
> onwards) and deprecate it in 6.0.x.
+0. We should document it boldly and let people know before the release.
Yoav
-
+1 - its an evil security hole
-Tim
Mark Thomas wrote:
All,
I'd like to remove the invoker servlet entirely from trunk (and hence TC7.x
onwards) and deprecate it in 6.0.x.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a
All,
I'd like to remove the invoker servlet entirely from trunk (and hence TC7.x
onwards) and deprecate it in 6.0.x.
Any objections?
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROT
