This will work, but then I'd have to add a different servlet definition
for each cobrand (and code the views with different references as
well?). There must be a simpler way..?
--- Henner Zeller <[EMAIL PROTECTED]> wrote:
>
> Hi,
> > I know I can treat the servlets as a separate webapp and de
53 -0700 (PDT)
> > From: August Detlefsen <[EMAIL PROTECTED]>
> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]>,
> > [EMAIL PROTECTED]
> > To: Tomcat Users List <[EMAIL PROTECTED]>
> > Subject: Cobranding - Share Controller, Split View
> >
&g
gt;
> Subject: Cobranding - Share Controller, Split View
>
> I am currently developing several cobranded sites that share the same
> functionality. I want to be able to share the same set of servlets
> across multiple cobrands.
>
> I know I can treat the servlets as a separate webapp and
Hi,
> I know I can treat the servlets as a separate webapp and deploy them to
> each separate host, but if I do this, will they be able to access the
> different configuration ( and JNDI resources )
> specified in the each ROOT context's web.xml?
What about having the same servlet referenced m
I am currently developing several cobranded sites that share the same
functionality. I want to be able to share the same set of servlets
across multiple cobrands.
I know I can treat the servlets as a separate webapp and deploy them to
each separate host, but if I do this, will they be able to ac
