I would suggest:
<ul>
<li>create a war file on JBoss
<li> run the war file through GlassFish verifier tool. You can find the verifier tool in the GlassFish distribution. <gf-install>/bin. The verifier has proven to be a useful tool in migration and catches issues related to URL patterns, packing issues for e.g.
<li> Migrate the JBoss specific deployment descriptors and configuration files to GlassFish deployement descriptors. The GlassFish specific deployment descriptors are documented in
http://docs.sun.com/app/docs/doc/819-3673/beaqi?a=view .
<li>Check the
http://wiki.glassfish.java.net/Wiki.jsp?page=M2GMigrationGuide for known JBoss -> GlassFish migration issues. I update and maintain this guide as more issues become known. So, if you encounter a migration issue not yet documented, please consider adding to the migration guide or at least post to this forum, so I can link to the migration guide. This would benefit the GlassFish community.
<li>Instead of a war file, you can use an exploded directory (i.e. in a format you would get for e.g. by unjarring a war/ear file).
<li> The Java EE AVK
http://java.sun.com/j2ee/avk/ is useful for testing portability of you application to J2EE/Java EE APIs. At least for some of the examples I have been migrating and blogging about, I have not found the need to use the AVK.
</ul>
Please post any questions you have to this forum.
Thanks,
Sekhar
[Message sent by forum member 'sekhar' (sekhar)]
http://forums.java.net/jive/thread.jspa?messageID=289438