[PATCH] Exporting servlet-mappings to Apache/mod_jk TC3.3-M4

2001-07-02 Thread William Barker

   I don't really expect this to be approved for inclusion, since it relies
on ApacheConfig having too much knowledge about Context internals.  I'm
submitting it primarily to demonstrate to the ajp14/warp crowd that it is
possible to auto-generate mappings short of JkMount /my-app/* ajp13.

 ApacheConfig.diff


Re: [PATCH] Exporting servlet-mappings to Apache/mod_jk TC3.3-M4

2001-07-02 Thread cmanolache

Hi William,

I'm not sure I understand your position :-)

Are you interested to help fixing ( or improving ) the ApacheConfig
problems ? The only reason for going back to JkMount
/my-app/* ajp13 is that the apache config generation is incomplete, and
there's little hope to have it finished in a reasonable amount of time.

Any improvement in ApacheConfig is great - it'll simplify the life of
those doing manual configurations ( and want apache serving static files,
etc). When the generated config will be equivalent with web.xml, we can
revert to make it the default.

The big missing parts so far:
- authentication ( form login is the hardest )
- welcome files

( BTW, could you send the diff as cvs diff  ? )

On Sun, 1 Jul 2001, William Barker wrote:

I don't really expect this to be approved for inclusion, since it relies
 on ApacheConfig having too much knowledge about Context internals.  I'm
 submitting it primarily to demonstrate to the ajp14/warp crowd that it is
 possible to auto-generate mappings short of JkMount /my-app/* ajp13.


Costin