You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by James Carman <ja...@carmanconsulting.com> on 2003/03/23 06:01:14 UTC

Re: tomcat servlet invoker

You should not use the "invoker" servlet.  You should set up servlet
mappings in your web.xml file for your servlets.

----- Original Message -----
From: "Boon Seong" <nb...@singnet.com.sg>
To: <to...@jakarta.apache.org>
Sent: Sunday, March 23, 2003 6:01 AM
Subject: tomcat servlet invoker


> Hi,
>
>  With reference to the documentation at
>
>
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.21-beta/REL
>  EASE-NOTES ,  on the section Enabling invoker servlet, there is this note
>  -----
>  Using the invoker servlet in a production environment is not recommended
> and
>  is unsupported.
>  -----
>
>  Wonder what we should use for servlet invokation for a production
>  environment ?
>
>
>  Thanks.
>
> nbs
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Re: tomcat servlet invoker

Posted by James Carman <ja...@carmanconsulting.com>.
Yes, you must create a servlet mapping for each servlet.  You could use
XDoclet to generate your web.xml file, which can alleviate some of the
burden and maintenance overhead.

----- Original Message -----
From: "Boon Seong" <nb...@singnet.com.sg>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Sunday, March 23, 2003 6:59 AM
Subject: Re: tomcat servlet invoker


> What will be used to invoke the servlet then ?
>
> The servlet mapping is one to one. What happen if I have a lot of servlets
?
> The 1 to 1 mapping
> may cause some maintainance problem.
>
> Thanks.
>
> NBS
>
>
> ----- Original Message -----
> From: "James Carman" <ja...@carmanconsulting.com>
> To: "Tomcat Users List" <to...@jakarta.apache.org>
> Sent: Sunday, March 23, 2003 7:01 AM
> Subject: Re: tomcat servlet invoker
>
>
> > You should not use the "invoker" servlet.  You should set up servlet
> > mappings in your web.xml file for your servlets.
> >
> > ----- Original Message -----
> > From: "Boon Seong" <nb...@singnet.com.sg>
> > To: <to...@jakarta.apache.org>
> > Sent: Sunday, March 23, 2003 6:01 AM
> > Subject: tomcat servlet invoker
> >
> >
> > > Hi,
> > >
> > >  With reference to the documentation at
> > >
> > >
> >
>
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.21-beta/REL
> > >  EASE-NOTES ,  on the section Enabling invoker servlet, there is this
> note
> > >  -----
> > >  Using the invoker servlet in a production environment is not
> recommended
> > > and
> > >  is unsupported.
> > >  -----
> > >
> > >  Wonder what we should use for servlet invokation for a production
> > >  environment ?
> > >
> > >
> > >  Thanks.
> > >
> > > nbs
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> > >
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Re: tomcat servlet invoker

Posted by Jacob Kjome <ho...@visi.com>.
Which is why you should be using a Model2 framework like Barracuda, Struts, 
Maverick, and other frameworks.

Jake

At 01:59 PM 3/23/2003 +0200, you wrote:
>What will be used to invoke the servlet then ?
>
>The servlet mapping is one to one. What happen if I have a lot of servlets ?
>The 1 to 1 mapping
>may cause some maintainance problem.
>
>Thanks.
>
>NBS
>
>
>----- Original Message -----
>From: "James Carman" <ja...@carmanconsulting.com>
>To: "Tomcat Users List" <to...@jakarta.apache.org>
>Sent: Sunday, March 23, 2003 7:01 AM
>Subject: Re: tomcat servlet invoker
>
>
> > You should not use the "invoker" servlet.  You should set up servlet
> > mappings in your web.xml file for your servlets.
> >
> > ----- Original Message -----
> > From: "Boon Seong" <nb...@singnet.com.sg>
> > To: <to...@jakarta.apache.org>
> > Sent: Sunday, March 23, 2003 6:01 AM
> > Subject: tomcat servlet invoker
> >
> >
> > > Hi,
> > >
> > >  With reference to the documentation at
> > >
> > >
> >
>http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.21-beta/REL
> > >  EASE-NOTES ,  on the section Enabling invoker servlet, there is this
>note
> > >  -----
> > >  Using the invoker servlet in a production environment is not
>recommended
> > > and
> > >  is unsupported.
> > >  -----
> > >
> > >  Wonder what we should use for servlet invokation for a production
> > >  environment ?
> > >
> > >
> > >  Thanks.
> > >
> > > nbs
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> > >
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: tomcat servlet invoker

Posted by Boon Seong <nb...@singnet.com.sg>.
What will be used to invoke the servlet then ?

The servlet mapping is one to one. What happen if I have a lot of servlets ?
The 1 to 1 mapping
may cause some maintainance problem.

Thanks.

NBS


----- Original Message -----
From: "James Carman" <ja...@carmanconsulting.com>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Sunday, March 23, 2003 7:01 AM
Subject: Re: tomcat servlet invoker


> You should not use the "invoker" servlet.  You should set up servlet
> mappings in your web.xml file for your servlets.
>
> ----- Original Message -----
> From: "Boon Seong" <nb...@singnet.com.sg>
> To: <to...@jakarta.apache.org>
> Sent: Sunday, March 23, 2003 6:01 AM
> Subject: tomcat servlet invoker
>
>
> > Hi,
> >
> >  With reference to the documentation at
> >
> >
>
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.21-beta/REL
> >  EASE-NOTES ,  on the section Enabling invoker servlet, there is this
note
> >  -----
> >  Using the invoker servlet in a production environment is not
recommended
> > and
> >  is unsupported.
> >  -----
> >
> >  Wonder what we should use for servlet invokation for a production
> >  environment ?
> >
> >
> >  Thanks.
> >
> > nbs
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org