Michael Rassmussen wrote:
I looked and maven is pulling servlet 2.2. I would assume that faces
is using that same servlet.jar. I just rebuilt faces against 2.3 and
the problems seem to have gone away. I haven't tried 2.4, but it
seems that it should work fine there. It is my guess after trying to
build struts-faces in eclipse using servlet 2.2 that the problem is
with 2.2 not being supported. (And it shouldn't be right?)
Michael
That's correct ... JSF requires Servlet 2.3.
Note: my nightly build scripts use Ant, not Maven ... and I'm in the process of cleaning that up. Shortly I'll be posting a list of the actual dependencies I'm using for the Struts nightly build, which should correspond to what we actually include in 1.2.1.
Craig
On Mon, 05 Jul 2004 18:56:41 -0700, Craig McClanahan
<[EMAIL PROTECTED]> wrote:
Ted Husted wrote:
I imagine Craig has Struts-Faces compiling against 2.4 to make sure it stays in synch with Tomcat 5.
It is indeed, but that's actually a mistake. It needs to compile against the 2.3 version, since that's what JSF specifies as a minimum platform. I'll fix that in tonight's run.
But, the question is whether we want to mandate that Struts-Faces can only compile against 2.3 (and not 2.4)? Or vice-versa. Or is there a way to write the class so it compiles under either?
I'll take a look at the changes once I catch up a little bit more, and might be able to come up with something clever that makes this possible (still recovering from JavaOne and ~11k backlogged mail messages :-).
I know this is a pain. We went through the same problem with DataSources between 2.2 and 2.3. I'm not sure what the issue here is, but for DataSources, the interface changed and we had to stub the new members so that they threw exceptions if called. Of course, the problem with that approach is it may obviate new functionality or rely on deprecated methods.
-Ted.
Craig
On Mon, 05 Jul 2004 14:14:02 +0200, Matthias Wessendorf wrote:
James,
i also guess it is the result of the commitment. i submitted (first) a wrapper, that builds against 2.4 reason is, the build-porperties had *default* to 2.4
okay ted asks for a 2.3-wrapper, so i created that candidate.
i think the wrapper should compile against 2.3 since jsf is able to run in j2ee1.3-containers
So i am wondering, why struts-faces uses 2.4 for compiling.
btw. the 2.3 wrapper runs on servlet2.4-containers (like tomcat5.0)
Matthias
I think it is happening because of the changes I committed for your fix for MyFaces. If you look at when the builds stopped, it's right after I made the commits on 6/29. It must be an issue of what version of servlet.jar that the HttpServletRequestWrapper class is being compiled against. Is it not possible to make that class compilable against both 2.3 and 2.4?
-James
-----Original Message----- From: Matthias Wessendorf [mailto:[EMAIL PROTECTED] wessendorf.de] Sent: Monday, July 05, 2004 6:29 AM To: [EMAIL PROTECTED] Subject: Struts-faces
see http://cvs.apache.org/builds/jakarta-struts/nightly/struts- faces/
the nightly build is empty again,
so is there a logfile, where i can check, why it is not build successful?
Cheers,
-- Matthias Weßendorf Aechterhoek 18 DE-48282 Emsdetten Germany Email: matthias AT wessendorf DOT net URL: http://www.wessendorf.net
------------------------------------------------------------------ --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------ --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
