I have developed an Struts 1.1 app under Tomcat. I did not have any problems to migrate it to Websphere 5.0, and it worked with no changes. Fine!!!
However, when trying to deploy in an iPlanet Application Server 6.5, it did not work. It complaints in many points. For example, I was able to fix the ClassLoaders differences, patching Struts as suggested in the following message:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg74045.html
using Class.forName() in turn. I made this in 3 or 4 places and I was able to make Struts start.
However, it is still complaining in too many places with the custom tags and so on.
- Does anyone knows a detailed migration guide on how to patch Struts 1.1 for iPlanet Application Server 6.5?
I have looked for long but not success, even the install guides from Jakarta.
We have this problem before with Websphere 3.5, and after the right patchs all worked properly for us, for 2 years. With Websphere 5.0+ we did not need path. So probably it was really worthy.
- Could future Struts implementations include some "hole classes", for saving container differences, (despite I have read that Struts is made according to specs and not implementations). Being closer to real world (i.e. iPlanet, Websphere, Weblogic.....) is remove obstacles for Struts assumption.
I really like Struts, but I would not like to quit using it since some containers are not compatibles and finding or working out patches is a long time consuming task, loosing one of the advantages of using struts.
As usually, the worst side, managers get unconfident when they see something fail, they are not able to evaluate why, and I got troubles in this ocassion making explanations.
Any help would be appreciated,
Adolfo Rodriguez.
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
