RE: WDSC 6.0 WebSphere Test Environment

I think that serve servlets by class name has to be enabled to allow the 
execution of servlets by their class name.  If you think about it this is 
a security question, if you let someone run any servlet they like they may 
be able to do bad things.   Allowing only named servlets to run lets you 
define what can be invoked and masks the class (and allows you to change 
the jsp or servlet that is run by that name I would think).

The deployment descriptor only references the named servlets that you (or 
some tooling) define I believe.

Mike

Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 
voice 905 413 3199




"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
2005-09-21 10:01
Please respond to
Websphere Development Studio Client for iSeries 


To
"'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
RE: [WDSCI-L] WDSC 6.0 WebSphere Test Environment






> From: Joe Pluta
> 
> You can only run the servlet if it has been defined to the deployment
> descriptor.  For servlets that are simply run by class name, you can't
> do it (they don't even show up under the "Servlets" category of the
> Deployment Descriptor).  What's the rationale behind that?

Don, did you see this?  Is there a reason why we can't run servlets that
aren't specifically defined to the Deployment Descriptor?

Joe