Now that's interesting. Once you've done that does all of the WTE work?
Have you tested EJB's as well as servlets?
Kyle
Arjun Bhattacharya <[EMAIL PROTECTED]> on 05/02/2001
05:27:40 PM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: Struts and VisualAge 3.5.3 with WTE
Kyle,
FYI, I found a *dirty* way to import Xerces into VAJ. Import it into the
XML4J project and select yes to overwrite everything. That will work.
Regards,
Arjun
-----Original Message-----
From: Kyle Brown [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 02, 2001 1:09 PM
To: [EMAIL PROTECTED]
Subject: RE: Struts and VisualAge 3.5.3 with WTE
Jon,
There is no easy way to convert. You could possibly write a program
to do it (maybe with Xalan) but the problem is that VAJ spreads over two
files what it takes web.xml only one to do....
Interesting -- I couldn't get Xerces to import into 3.5.3 without
conflicting with IBM XML4J. I even tried deleting the duplicate classes
from XML4J, but that screwed it up... Sun's Jaxp seemed to work well
enough for me...
Kyle
"Jon.Ridgway" <[EMAIL PROTECTED]> on 05/02/2001 12:09:29 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: RE: Struts and VisualAge 3.5.3 with WTE
Hi Kyle,
Sorry to bother you again. I take it from your reply that VisualAge 3.5.3
does not support web.xml files, is there an easy way to convert both ways ?
Also I found that importing the latest version of xerces worked for me.
Struts seems to use some of its classes as well as jaxp stuff (doesn't seem
to bother Websphere test env. Not sure about EJB env yet, I'll let you know
tomorrow). Off to catch the last of the sun.....
Jon.
-----Original Message-----
From: Kyle Brown [mailto:[EMAIL PROTECTED]]
Sent: 02 May 2001 15:26
To: [EMAIL PROTECTED]
Subject: RE: Struts and VisualAge 3.5.3 with WTE
Ahh -- good catch Jon. I actually meant the default.servlet_engine file in
step 3. That contains the document root and classpath. You also have to
create a .webapp file (of course) to actually load the ActionServlet
appropriately...
Kyle
"Jon.Ridgway" <[EMAIL PROTECTED]> on 05/02/2001 09:45:01 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: Kyle Brown/Raleigh/IBM@IBMUS
Subject: RE: Struts and VisualAge 3.5.3 with WTE
Hi Kyle,
If you have time, could you elaborate on step three. The <app
group>/servlets/<app group>.webapps file that I am familiar with in VAJ
makes no mention of doc roots and servlet paths. Could you provide an
example file and/or point me to the docs.
Everything else is very clear and has been a great help. Many thanks
Jon Ridgway.
-----Original Message-----
From: Kyle Brown [mailto:[EMAIL PROTECTED]]
Sent: 02 May 2001 13:57
To: [EMAIL PROTECTED]
Subject: Re: Struts and VisualAge 3.5.3 with WTE
One more modification to this set of instructions:
I didn't like my own solution about modifying the Digester and looked
around to see if I couldn't solve the problem in a way that didn't require
you to modify code. It turns out this isn't too hard. What you have to do
is import only those parts of JAXP that are required to meet the
requirements of Struts. So, if you download the JAXP 1.01 from Sun's
website and import the entire contents of the jaxp.jar file and all of the
classes in parser.jar file EXCEPT those classes that start with org.w3c
into VisualAge for Java, then you will have an additional parser that will
correspond to the JAXP API and will work with Struts, but will not conflict
with the IBM XML4Java parser that the WTE requires.
By the way, this removes the need to modify the struts-config.dtd file.
Kyle Brown
---------------------- Forwarded by Kyle Brown/Raleigh/IBM on 05/02/2001
08:58 AM ---------------------------
Kyle Brown
05/01/2001 07:25 AM
To: [EMAIL PROTECTED]
cc:
From: Kyle Brown/Raleigh/IBM@IBMUS
Subject: Re: Struts and VisualAge 3.5.3 with WTE (Document link: Kyle
Brown)
Yes, I've managed to do it. Getting Struts to work under VAJ 3.5.3 was a
bit of a challenge to say the least.
You have to be sure that you change the default.servlet_engine file to
point to your new web app and that you create a new directory under the
"default_host" subdirectory and put your new .webapp file there. This is
what the documentation is trying to tell you to do.
Other things you have to do to make this work:
(1) You have to change the Digester to work with the older (pre JAXP)
SAXParser classes. This turns out to amount to changing only four or five
methods in the class in fairly simple ways. You have to do this because
you can't replace the IBM parser classes with Xerces since the WTE servlet
engine depends on the IBM parser API.
(2) You have to add your Struts project to the Servlet Engine
classpath (from the WTE Control panel).
(3) Your .webapp file has to have the document root and servlet path
point to the same directory to match the directory structure for Struts
(e.g. the standard J2EE webapp structure).
(4) (I don't know why this is true -- can anyone help here?) You have
to edit the struts-config.dtd file and host it locally to remove the last
couple of lines that define the large icon and small icon elements. There
is something in the way that they are configured that will screw up the IBM
parser. Simply commenting out those lines from the DTD makes it work.
BTW -- does anyone know of someone actually using the icon definitions in
Struts?
I'm still working on that article for the IBM VisualAge Developer's
Domain on how to make Struts work in VAJ 3.5.2 and VAJ 3.5.3....
Kyle Brown
[EMAIL PROTECTED] on 04/30/2001 05:12:46 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Struts and VisualAge 3.5.3 with WTE
Has anybody configured the struts example application
with VisualAge 3.5.3 and the included WTE?
Any problems?
I found the documetation for WTE within VisualAge to be
less than robust. I can access the default app created by
WTE, but no luck creating a new one.
- Darren.
