FWIW,
the SYSTEM DTD issue is a twofold problem:
a) The classloader returns a null for the URL provided
b) Struts doesn't check a null for the inputstream.
One of these days, I'll send a patch in for b)
I'll try a simple app to test the getResource* issues, and file a PMR,
early next week.
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
NetRexx: http://www.multitask.com.au/NetRexx.nsf
----- Forwarded by dIon Gillard/Multitask Consulting/AU on 24/03/2001
07:42 PM -----
RE: WebSphere 3.5.3 problem
> I did our 3.5.3 installation yesterday and it was as per
> 3.5.2. I still
> needed the changed action servlet and also a change of the
> struts-config.xml to use a SYSTEM DTD rather than a PUBLIC one.
>
> It did NOT work out of the box. getResourceAsStream still
> appears to be
> broken in 3.5.3
How odd, because I am 100% sure that the getResourceAsStream works fine
for
us in 3.5.3! We used to have a patch for it when running 3.5.2, but all of
us removed that patch when we upgraded, and it still works. I believe that
we are using a system DTD though, but not because it didn't work
otherwise.
Oh, and we're running the advanced version of WAS.
On the other hand, I'm not too surprised since we are experiencing strange
behaviours with WebSphere every day. I sincerely think that just about any
other application server out there must beat WebSphere in terms of
productivity and ease of development. Is there anyone out there that has
positive experiences from WebShpere?
/Markus
Previous Document
Next Document
Return to View
