You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Paul Lindner <pl...@linkedin.com> on 2010/05/12 20:20:42 UTC
upgrade to servlet-api 2.5
I'd like to move us to servlet-api 2.5
pros:
* Allows easier web.xml configuration for various url patterns.
* Allows for use of getContextPath() to ease configuration hassles
cons:
* People can't deploy source builds directly to tomcat 5.5 or older
containers.
To make this easy I'll wrap calls to getContextPath() into it's own class
that can be customized with hard coded or configured value.
Re: upgrade to servlet-api 2.5
Posted by Chirag Shah <ch...@gmail.com>.
+1
On Wed, May 12, 2010 at 12:12 PM, Paul Lindner <pl...@linkedin.com> wrote:
> I'm going ahead with this change
>
> * web.xml has already had servlet-2.5 markup for a long time...
> * I forgot that I raised this issue long ago and no one complained.
>
>
> On Wed, May 12, 2010 at 11:20 AM, Paul Lindner <pl...@linkedin.com>wrote:
>
>> I'd like to move us to servlet-api 2.5
>>
>> pros:
>> * Allows easier web.xml configuration for various url patterns.
>> * Allows for use of getContextPath() to ease configuration hassles
>>
>> cons:
>> * People can't deploy source builds directly to tomcat 5.5 or older
>> containers.
>>
>> To make this easy I'll wrap calls to getContextPath() into it's own class
>> that can be customized with hard coded or configured value.
>>
>>
>
Re: upgrade to servlet-api 2.5
Posted by Paul Lindner <pl...@linkedin.com>.
Hmm,
If you're using maven you can add an <exclusion> for servlet-api-2.5 to your
pom.xml and move on. For 2.0.x we'll insure that we maintain 2.4 ABI
compatibility for deployed artifacts by not using the new methods in 2.5.
You'll still be responsible for supplying your own web.xml, but that's a
given!
And I'm afraid to ask, where are you with respect to Java 5 vs 6 support?
On Thu, May 13, 2010 at 8:47 AM, Han Nguyen <hn...@us.ibm.com> wrote:
> -1 for the proposal as is.
> We certainly understand and in favor of your proposal for web.xml cleanup
> and API ease of use. However, we have requirements to support both 2.4 and
> 2.5.
> Is there a way we can manage this to provide backward compatibility to
> take care of any possible API conflicts/breakages ?
>
> Thanks,
> Han
>
>
>
> From: Paul Lindner <pl...@linkedin.com>
> To: dev@shindig.apache.org
> Date: 05/12/2010 04:38 PM
> Subject: Re: upgrade to servlet-api 2.5
> Sent by: lindner@inuus.com
>
>
>
> You should be fine. This is mostly for the benefit of people developing
> off
> the code base and less about the people consuming the artifacts.
>
> I can revert back to 2.4 if there's a compelling argument.
>
> On Wed, May 12, 2010 at 1:24 PM, Mark D Weitzel <we...@us.ibm.com>
> wrote:
>
> > Paul,
> >
> > Would you be kind enough to let me check with a few of our product teams
> > inside of IBM? I *think* this may give us some heartache b/c we'll need
> to
> > deploy on the current version. So I definitely don't want to vote yes or
> > no without having all the facts.
> >
> > Thanks,
> >
> > -Mark W.
> >
> >
> >
> > From:
> > John Hjelmstad <fa...@google.com>
> > To:
> > dev@shindig.apache.org
> > Date:
> > 05/12/2010 03:53 PM
> > Subject:
> > Re: upgrade to servlet-api 2.5
> >
> >
> >
> > +1 from here.
> >
> > On Wed, May 12, 2010 at 12:12 PM, Paul Lindner
> > <pl...@linkedin.com>wrote:
> >
> > > I'm going ahead with this change
> > >
> > > * web.xml has already had servlet-2.5 markup for a long time...
> > > * I forgot that I raised this issue long ago and no one complained.
> > >
> > >
> > > On Wed, May 12, 2010 at 11:20 AM, Paul Lindner <plindner@linkedin.com
> > > >wrote:
> > >
> > > > I'd like to move us to servlet-api 2.5
> > > >
> > > > pros:
> > > > * Allows easier web.xml configuration for various url patterns.
> > > > * Allows for use of getContextPath() to ease configuration hassles
> > > >
> > > > cons:
> > > > * People can't deploy source builds directly to tomcat 5.5 or older
> > > > containers.
> > > >
> > > > To make this easy I'll wrap calls to getContextPath() into it's own
> > class
> > > > that can be customized with hard coded or configured value.
> > > >
> > > >
> > >
> >
> >
> >
>
>
Re: upgrade to servlet-api 2.5
Posted by Han Nguyen <hn...@us.ibm.com>.
-1 for the proposal as is.
We certainly understand and in favor of your proposal for web.xml cleanup
and API ease of use. However, we have requirements to support both 2.4 and
2.5.
Is there a way we can manage this to provide backward compatibility to
take care of any possible API conflicts/breakages ?
Thanks,
Han
From: Paul Lindner <pl...@linkedin.com>
To: dev@shindig.apache.org
Date: 05/12/2010 04:38 PM
Subject: Re: upgrade to servlet-api 2.5
Sent by: lindner@inuus.com
You should be fine. This is mostly for the benefit of people developing
off
the code base and less about the people consuming the artifacts.
I can revert back to 2.4 if there's a compelling argument.
On Wed, May 12, 2010 at 1:24 PM, Mark D Weitzel <we...@us.ibm.com>
wrote:
> Paul,
>
> Would you be kind enough to let me check with a few of our product teams
> inside of IBM? I *think* this may give us some heartache b/c we'll need
to
> deploy on the current version. So I definitely don't want to vote yes or
> no without having all the facts.
>
> Thanks,
>
> -Mark W.
>
>
>
> From:
> John Hjelmstad <fa...@google.com>
> To:
> dev@shindig.apache.org
> Date:
> 05/12/2010 03:53 PM
> Subject:
> Re: upgrade to servlet-api 2.5
>
>
>
> +1 from here.
>
> On Wed, May 12, 2010 at 12:12 PM, Paul Lindner
> <pl...@linkedin.com>wrote:
>
> > I'm going ahead with this change
> >
> > * web.xml has already had servlet-2.5 markup for a long time...
> > * I forgot that I raised this issue long ago and no one complained.
> >
> >
> > On Wed, May 12, 2010 at 11:20 AM, Paul Lindner <plindner@linkedin.com
> > >wrote:
> >
> > > I'd like to move us to servlet-api 2.5
> > >
> > > pros:
> > > * Allows easier web.xml configuration for various url patterns.
> > > * Allows for use of getContextPath() to ease configuration hassles
> > >
> > > cons:
> > > * People can't deploy source builds directly to tomcat 5.5 or older
> > > containers.
> > >
> > > To make this easy I'll wrap calls to getContextPath() into it's own
> class
> > > that can be customized with hard coded or configured value.
> > >
> > >
> >
>
>
>
Re: upgrade to servlet-api 2.5
Posted by Paul Lindner <pl...@linkedin.com>.
You should be fine. This is mostly for the benefit of people developing off
the code base and less about the people consuming the artifacts.
I can revert back to 2.4 if there's a compelling argument.
On Wed, May 12, 2010 at 1:24 PM, Mark D Weitzel <we...@us.ibm.com> wrote:
> Paul,
>
> Would you be kind enough to let me check with a few of our product teams
> inside of IBM? I *think* this may give us some heartache b/c we'll need to
> deploy on the current version. So I definitely don't want to vote yes or
> no without having all the facts.
>
> Thanks,
>
> -Mark W.
>
>
>
> From:
> John Hjelmstad <fa...@google.com>
> To:
> dev@shindig.apache.org
> Date:
> 05/12/2010 03:53 PM
> Subject:
> Re: upgrade to servlet-api 2.5
>
>
>
> +1 from here.
>
> On Wed, May 12, 2010 at 12:12 PM, Paul Lindner
> <pl...@linkedin.com>wrote:
>
> > I'm going ahead with this change
> >
> > * web.xml has already had servlet-2.5 markup for a long time...
> > * I forgot that I raised this issue long ago and no one complained.
> >
> >
> > On Wed, May 12, 2010 at 11:20 AM, Paul Lindner <plindner@linkedin.com
> > >wrote:
> >
> > > I'd like to move us to servlet-api 2.5
> > >
> > > pros:
> > > * Allows easier web.xml configuration for various url patterns.
> > > * Allows for use of getContextPath() to ease configuration hassles
> > >
> > > cons:
> > > * People can't deploy source builds directly to tomcat 5.5 or older
> > > containers.
> > >
> > > To make this easy I'll wrap calls to getContextPath() into it's own
> class
> > > that can be customized with hard coded or configured value.
> > >
> > >
> >
>
>
>
Re: upgrade to servlet-api 2.5
Posted by Mark D Weitzel <we...@us.ibm.com>.
Paul,
Would you be kind enough to let me check with a few of our product teams
inside of IBM? I *think* this may give us some heartache b/c we'll need to
deploy on the current version. So I definitely don't want to vote yes or
no without having all the facts.
Thanks,
-Mark W.
From:
John Hjelmstad <fa...@google.com>
To:
dev@shindig.apache.org
Date:
05/12/2010 03:53 PM
Subject:
Re: upgrade to servlet-api 2.5
+1 from here.
On Wed, May 12, 2010 at 12:12 PM, Paul Lindner
<pl...@linkedin.com>wrote:
> I'm going ahead with this change
>
> * web.xml has already had servlet-2.5 markup for a long time...
> * I forgot that I raised this issue long ago and no one complained.
>
>
> On Wed, May 12, 2010 at 11:20 AM, Paul Lindner <plindner@linkedin.com
> >wrote:
>
> > I'd like to move us to servlet-api 2.5
> >
> > pros:
> > * Allows easier web.xml configuration for various url patterns.
> > * Allows for use of getContextPath() to ease configuration hassles
> >
> > cons:
> > * People can't deploy source builds directly to tomcat 5.5 or older
> > containers.
> >
> > To make this easy I'll wrap calls to getContextPath() into it's own
class
> > that can be customized with hard coded or configured value.
> >
> >
>
Re: upgrade to servlet-api 2.5
Posted by John Hjelmstad <fa...@google.com>.
+1 from here.
On Wed, May 12, 2010 at 12:12 PM, Paul Lindner <pl...@linkedin.com>wrote:
> I'm going ahead with this change
>
> * web.xml has already had servlet-2.5 markup for a long time...
> * I forgot that I raised this issue long ago and no one complained.
>
>
> On Wed, May 12, 2010 at 11:20 AM, Paul Lindner <plindner@linkedin.com
> >wrote:
>
> > I'd like to move us to servlet-api 2.5
> >
> > pros:
> > * Allows easier web.xml configuration for various url patterns.
> > * Allows for use of getContextPath() to ease configuration hassles
> >
> > cons:
> > * People can't deploy source builds directly to tomcat 5.5 or older
> > containers.
> >
> > To make this easy I'll wrap calls to getContextPath() into it's own class
> > that can be customized with hard coded or configured value.
> >
> >
>
Re: upgrade to servlet-api 2.5
Posted by Paul Lindner <pl...@linkedin.com>.
I'm going ahead with this change
* web.xml has already had servlet-2.5 markup for a long time...
* I forgot that I raised this issue long ago and no one complained.
On Wed, May 12, 2010 at 11:20 AM, Paul Lindner <pl...@linkedin.com>wrote:
> I'd like to move us to servlet-api 2.5
>
> pros:
> * Allows easier web.xml configuration for various url patterns.
> * Allows for use of getContextPath() to ease configuration hassles
>
> cons:
> * People can't deploy source builds directly to tomcat 5.5 or older
> containers.
>
> To make this easy I'll wrap calls to getContextPath() into it's own class
> that can be customized with hard coded or configured value.
>
>