We are currently in the middle of this migration process from 3.02 to 4.0.

We were impacted mainly because:

- some of our custom tag libraries were buggy but were working in 3.0
because tags were instantiated each time, starting from 3.1 tags can be
re-used so if you tag keep some state variables, it will impact next run.
- we had to completely review our configuration and installation doc due to
JRun switch from properties files to XML.
- some of our configuration have to be moved in other location due to new
war deployment.
- JNDI name space change.

Overall, this migration was more difficult because we skipped 3.1 but it
allowed us to improve our code quality and remove custom code.

Good luck,

Gael



Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to