Hines, Bill writes:
> "IBM's WebSphere is not a fully Java Servlet 2.2 compliant container."
>
> With the fixpack though, WebSphere 3.5 is brought up to date on servlets 2.2
> and JSP 1.1.
(My apologies if this is off-topic for this list.)
"Brought up to date on servlets 2.2 and JSP 1.1" does not necessarily
mean that WebSphere is a fully compliant servlet container. What you
have indicated is that it is at least partially compliant.
Java Servlets 2.2, as I have read it the specifications, is what
defines war files, their layout, and how they are to be handled by the
container.
Since WebSphere 3.5.2 only has deployment support for war files, it
cannot be fully compliant.
The whole point of a war file (and this has already appeared on the
list) is such that one can drop the war into any given compliant
container and it just work. However, one cannot simply drop a war
file into WebSphere and expect it to work. Utilities must be used to
*convert* the war file into a WebSphere application.
The fact that WebSphere 3.5.2 does not *natively* support war files
speaks for itself in demonstrating that WebSphere is not fully
Servlets 2.2 compliant.
That was my only point: that "support for WAR files" does not equal
fully compliant servlet container.
> -----Original Message-----
> From: Lefty Burgess [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 01, 2000 8:57 AM
> To: [EMAIL PROTECTED]
> Subject: Struts ok with WebSphere AppServer?
>
> Alix Jermyn writes:
> >
> > For our next project we would like to use struts, and our client is
> likely
> > to be committed to using WebSphere for an App Server.
> >
> > Has anyone out there used WebSphere with struts before - any problems we
> > should be aware of before committing ourselves?
> >
> > PS Craig imminent is imminent for the Struts 1.0 milestone release? (1
> > week, 1 month?)
> >
> > ta
> > Alix
>
> Unfortunately, I cannot answer your question *yet*. I am in the same
> situation, however, in that I am developing an application with Struts
> on Apache/Tomcat but need to deploy to IIS/WebSphere.
>
> It *should* be possible, with some extra work of course, because
> IBM's WebSphere is not a fully Java Servlet 2.2 compliant container.
> Big surprise there. The extra work involves running a particular
> version of WebSphere and using utilities to convert a war file into
> something WebSphere can understand. I have not actually gotten this
> far yet, but it *seems* relatively straightforward.
>
> Here are some links substantiating what I am trying to relate:
>
> http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/was/0
> 008.html
>
> http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/was/0
> 00801.html
>
> http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/was/0
> 00802.html
>
> To quote from the last link:
>
> "IBM WebSphere Application Server Version 3.5 Fix Pack 2 (also known
> as Version 3.5.2) introduces support for WAR files. However, Fix Pack
> 2 has been designed to maintain compatibility with existing
> applications. As such, WAR files are only used as a deployment vehicle
> in Version 3.5.2. After a WAR file is installed into the server
> runtime, the WAR file itself is no longer used."
>
> If you try all this before I do and it works or doesn't, please let
> the rest of us know. Thanks!
>
> --
> Lee "Lefty" Burgess <<!>> Manipulate eternity. Power is a symphony:
> Web Application Developer <<!>> elaborate, enormous, essential.
> PiperStudiosInc <<!>> Dream the moment with a fiddle in summer
> [EMAIL PROTECTED] <<!>> and a knife in winter.
--
Lee "Lefty" Burgess <<!>> Manipulate eternity. Power is a symphony:
Web Application Developer <<!>> elaborate, enormous, essential.
PiperStudiosInc <<!>> Dream the moment with a fiddle in summer
[EMAIL PROTECTED] <<!>> and a knife in winter.
