The problem is the fact that we don't have access to specific errors or logs on the application server. Which is websphere 5.0. We submit an ear file with our entire app and the server admin runs scripts, installs the app, and locks down everything. We can't see anything after it is installed either. And this is only on the development server, not the production server.
And even if we only need to make a simple change like to a header file, we have to redeploy the entire application in an ear file, ftp it to the sever and from there the admin runs the scripts, the entire application is deleted, then reinstalled.
At this point, i actually got the application to run, but it really has nothing to do with struts or websphere at this point, it has more to do with whatever the server admin has set up and how it's set up. Unfortunately the developers and designers have no access, no documententatuion and anytime there is a problem, the server admin's simple answer is, "This is the way it's done, deal with it."
That and they plan on putting more security issues do to some new Security CEO or manager or whatever they are called these days.
So we are not sure if we even want to go with this server for our application anymore. For whatever reason, using the action servlet in struts takes forever to load. If it's running complex processes that is one thing, but going from Page A to Page B that takes about 10 seconds is unacceptable.
In Tomcat, it loads rather quickly, but in websphere, for whatever reason, it takes forever. And like I said, we do not have access to change anything in websphere. We don't even have access to our application once it is deployed. And this is on the development box.
If we have to use websphere 5.0 on this project, we might not use struts at all because it is just too slow between simple links at this point.
Joined: Feb 15, 2005
I hear your pain. I agree with you that it's probably a configuration issue and not a Struts issue. WebSphere is a great app server and it can perform very well. However, it's a lot more complicated than Tomcat, and if it's poorly configured, it won't perform well.
I wouldn't be too quick to abandon Struts, though. If the app server performs this poorly for a Struts application, it's not likely to perform that much better for a plain servlet/JSP application.