Juha Lindfors wrote:
Getting the scripts done would be the first step and itself helpful for most current admins, regardless of the language used in the script.
Once those exist, it should not be a huge step to integrate the scripts with a new MigrationSubDeployer that registers to accept any legacy descriptor DTD. It would eliminate the last step (running the script) from the process.
The difference between the two is first one modifies the package to contain new up-to-date descriptors where you can now add new configuration supported by the newer document type. In the latter there's no additional work on the admin but package would not be updated with new document type, something you'd want people to do eventually.
-- ================ Bill Burke Chief Architect JBoss Group LLC. ================
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
