If you read through the archives you will see that information was
posted on using struts with WebSphere a while back. I know because I
posted the information. As I am the developer of the War file converter
tool (I am a contractor working on WebSphere) I can vouch that at least
three struts based apps work with WebSphere 3.5 ptf2. I actually used
the struts example app for quite bit of my testing. I can only vouch for
Struts 0.5 as Struts 1.0 wasn't available at the time. I also converted
two other struts apps using the tool over to WebSphere with no problem.
These were medium complex apps that between them used the majority of
the taglibs.
The only thing that you have to do is provide a jaxp parser. This is
because WebSphere doesn't currently ship with one. The best way to do
this is to put it in your lib directory of your war file.
FYI the converter tool was actually written using ant. An XSL Transform
is performed to convert the web.xml to WebSphere xml format. You can
look at convert.xml to see what it is doing.
The next full version of WebSphere will support War files (and ear +
ejb-jar files) without having to convert them.
If you need any more information then I suggest you go back and read the
archives or go through the normal IBM support channels.
Richard Backhouse
Lefty Burgess wrote:
>
> Craig R. McClanahan writes:
> >
> > I'm not familar with the details of WebSphere, but accepting WARs as a deployment
> > format is all that is all that is required. See Section 9.3 of the 2.2 spec,
>which
> > says:
> >
> > The specification defines a hierarchical structure which can exist
> > in an open file system, an archive file, or some other form for deployment
> > purposes. It is recommended, but not required, that servlet containers
> > support this structure as a runtime representation.
> >
> > As long as the container provides an environment that complies with the
> > programmatic requirements of the servlet API (such as resolving getResource() and
> > getResourceAsStream() calls correctly), it does not matter what internal
> > architecture is used to represent the components of the application.
> >
> > Just as one example of an implication of this: it is not portable to assume that
> > you can use file I/O to talk to "files" within the web application document root.
> > The only portable mechanism is ServletContext.getResource() and
> > ServletContext.getResourceAsStream() -- which is why Struts uses these calls for
> > things like reading the configuration file.
>
> I stand corrected then. I think I'll scamper off and read the spec
> more carefully.
>
> > >
> > > 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.
> > >
> >
> > Some sort of deployment tool is required by pretty much any application server.
> > Even something simple like Tomcat has such a tool (the text editor you use to
>tweak
> > properties in server.xml :-).
>
> Yes, but Tomcat does not require you to run a separate conversion
> utility on a war file to convert that war file into a separate set of
> files that Tomcat recognizes as a web application. This is what
> WebSphere does. :)
>
> Still, WebSphere *is* compliant then, based on your correction that
> the spec only recommends the use of the war file format.
>
> > >
> > > 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.
> > >
> >
> > Are there particular aspects of WebSphere that cause Struts-based applications to
> > still fail, even when you properly deploy a web application using their tools?
>
> Heehee! That's just it. We don't know because no one has actually
> tried it yet. At least, no one here has mentioned doing it, to my
> knowledge.
>
> I will be working this issue Monday, so I will definitely let everyone
> know what my experience is.
>
> > Craig McClanahan
>
> --
> 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.
