1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
This is a LGPL'ed implementation of sun's java servlet api version 2.0
and version 2.1.
They were originally made by me (Paul Siegmann) and Mark Wielaard has made
them version 2.1 compliant.
Then I added a dirty hack to enable the creation of both 2.0 and 2.1 source
code from a single source tree.
See *How can you implement two api versions with a single source tree?*
Look for updates on: http://www.euronet.nl/~pauls/java/
Status of the classes
=====================
Feature complete and fully functional as a drop-in replacement on _my_ system.
Not yet stress-tested.
I have serious doubts about the thread-safeness and the "weird-input robustness"
of the library.
On the bright side: the documentation covers nearly 100% of the functionality.
I want to use the classes
=========================
Not a good idea, see *Status of the classes*.
I want to test the classes
==========================
Great! that's wat this release is intended for.
Could you tell me whether they work and if so on what kind of system.
If they do not behave as they should then please provide as much detail
as possible.
Patches are very welcome, but see *I want to send a patch*
I want to send a patch
======================
Great idea. But !!!:
Really Important(tm): if you've _ever_ taken a look at the source code of
sun's servlet developement kit, then please _don't_ send me a patch.
If you do then I'd be violating sun's copyright, which could get both me
and this library in big trouble.
How can you implement two api versions with a single source tree?
=================================================================
I added #ifdef VERSION_2_1 ... #endif tags to the code and wrote a class to generate the source code on the basis of these tags.
This is a really dirty hack which I feel really guilty about, but I saw no
other way.
The two api versions are nearly identical, neither of them have been seriously tested so they might change radically and almost equally in the near future.
This would require lots of updates on 2 almost identical source trees.
So I added the tag system, which seems to work OK for now.
When the implementations have stabilized and proven themselves I might split the source tree again.
|
