#116 Need Servlet API v3 support

Release_3.1
open
None
5
2012-08-27
2012-08-25
No

Currently, JWebUnit depends on v2.5 of the Java servlet-api. With many sites switching to Tomcat 7 (which supports and *provides* Servlet V3), JWU's dependency on the old servlet-api causes both versions to be added to the class path, which causes class conflicts which break the app and tests. Explicitly excluding JWU's dependency on v2.5 in a client POM breaks JWU.

What we really need is a new version of JWebUnit built with the new Servlet API release. I propose changing the servlet API dependency in JWebUnit's POM to this:

<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>3.0.1</version>
</dependency>

(BTW, note that the artifactId has changed.)

Thanks!!!

Discussion

  • Fran Tonello

    Fran Tonello - 2012-08-25
    • priority: 5 --> 8
     
  • Julien HENRY

    Julien HENRY - 2012-08-27
    • milestone: --> Release_3.1
    • labels: 865330 -->
    • status: open --> open-accepted
     
  • Julien HENRY

    Julien HENRY - 2012-08-27

    I'm not sure everybody is ready to update so servlet-api 3.0. It would be better to remove this dependency. This is something I wanted to to for a long time, but I'm not sure it will be easy. I will check asap.

     
  • Fran Tonello

    Fran Tonello - 2012-08-27

    Thanks for your quick response, Julien! I like how you think; I dared not hope that the dependency could be eliminated entirely.

    My company wants us to upgrade to Tomcat 7, since it's been out for over a year and a half. The upgrade to Servlet v3 was trivial - nothing needed to change in our apps, only our JWU integration tests are giving us trouble. So at least the upgrade is probably easy if the dependency can't be eliminated. The trouble is all those existing clients. There'd prolly have to be a new JWU artifact...

     
  • Fran Tonello

    Fran Tonello - 2012-08-27
    • status: open-accepted --> open
     
  • Fran Tonello

    Fran Tonello - 2012-08-27

    I've found a workaround, and lowing the priority of this issue.

    If you leave the old 'provided' dependency on Servlet v2.5 in your POM, JWebUnit will work, and there aren't any class conflicts:

    <dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>servlet-api</artifactId>
    <version>2.5</version>
    <scope>provided</scope>
    </dependency>

     
  • Fran Tonello

    Fran Tonello - 2012-08-27
    • priority: 8 --> 5
     
  • Julien HENRY

    Julien HENRY - 2012-08-28

    Thanks for the feedback. I'll keep the issue open in order to remind to investigate for the complete removal of servlet-api dependency.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks