Feature Requests item #3561726, was opened at 2012-08-25 10:25
Message generated for change (Comment added) made by ftonello
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=497985&aid=3561726&group_id=61302
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Release 3.1
Status: Open
>Priority: 5
>Private: No
Submitted By: Fran Tonello (ftonello)
Assigned to: Julien HENRY (henryju)
Summary: Need Servlet API v3 support
Initial Comment:
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!!!
----------------------------------------------------------------------
>Comment By: Fran Tonello (ftonello)
Date: 2012-08-27 16:37
Message:
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>
----------------------------------------------------------------------
Comment By: Fran Tonello (ftonello)
Date: 2012-08-27 10:34
Message:
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...
----------------------------------------------------------------------
Comment By: Julien HENRY (henryju)
Date: 2012-08-27 06:53
Message:
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.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=497985&aid=3561726&group_id=61302
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
JWebUnit-development mailing list
JWebUnit-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jwebunit-development
