It just isn't my month...
Well, the fixes are not fixing things. I've been able to confirm with IBM that the specific problem that has cropped up is indemic to WebSphere 3.5 and 4.0.1. WebSphere 5.0 does not have this problem, so we'll be migrating...
August 20, 2003
![Network Computing logo Network Computing logo](https://eu-images.contentstack.com/v3/assets/bltde8121fc52c5c8f3/blt3f3d0318f746b1c2/65a530e4187606040a1d8b8c/placeholder.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
Well, the fixes are not fixing things. I've been able to confirm with IBM that the specific problem that has cropped up is indemic to WebSphere 3.5 and 4.0.1. WebSphere 5.0 does not have this problem, so we'll be migrating as soon as possible to WAS 5.0. I've been playing with WebSphere Studio and running our code base on a test 5.0 server with success, so I don't foresee any huge issues.Stay tuned to see if I'm psychic or not.
You May Also Like
Maximizing cloud potential: Building and operating an effective Cloud Center of Excellence (CCoE)
September 10, 2024Radical Automation of ITSM
September 19, 2024Unleash the power of the browser to secure any device in minutes
September 24, 2024