irshad gehlot wrote:
Hi All,
Please exclude me from this mailing list.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
^^^
|||
Clues above.
Hi All,
Please exclude me from this mailing list.
Thanks.
Mark Thomas <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> Can you please send a proposal (including diffs) to the JSR-315 EG?
> "Generification" of the Servlet APIs is being considered for Servlet 3.0.
>
> Thanks,
>
[EMAIL PROTECTED] wrote:
Can you please send a proposal (including diffs) to the JSR-315 EG?
"Generification" of the Servlet APIs is being considered for Servlet 3.0.
Thanks,
Jan
Jan,
Patches are available (under the AL2) from:
http://people.apache.org/~markt/patches/
I also fixed a couple
Mark Thomas wrote:
Costin Manolache wrote:
And if the TCK signature tests pass - that's a bug in the tests :-).
We shouldn't touch the method signatures in servlet API.
Having read everyone's comments and having thought some more about
this during today, my current plan is:
- fix any non-
Costin Manolache wrote:
And if the TCK signature tests pass - that's a bug in the tests :-).
We shouldn't touch the method signatures in servlet API.
Having read everyone's comments and having thought some more about this
during today, my current plan is:
- fix any non-generics warnings in th
And if the TCK signature tests pass - that's a bug in the tests :-).
We shouldn't touch the method signatures in servlet API.
Costin
On Tue, May 6, 2008 at 2:03 AM, Remy Maucherat <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-05-06 at 08:27 +0100, Mark Thomas wrote:
> > I am leaning towards 4 on the
On Tue, 2008-05-06 at 08:27 +0100, Mark Thomas wrote:
> I am leaning towards 4 on the basis that
> a) This is trunk, not a release branch
> b) This option generates no warnings
> c) I assume the spec will start using generics at some point (maybe in 3.0?)
> If modifying the spec interfaces seems li
I'm for 3 since I wonder if the option 4 follow the specs.
2008/5/6 Mark Thomas <[EMAIL PROTECTED]>:
> All,
>
> As you have probably noticed I am doing some clean-up of the trunk codebase
> as and when the opportunity arises. So far the clean has identified the odd
> copy/paste error or casting p
