The application (your WAR archive) is one thing. The application server
configuration (database connections for instance) is another. Creator
(and NetBeans) create the resources for you in the default target server.
Now you don't have to use the asupgrade tool but rather recreate the
datasource using the GlassFish console of CLI (asadmin). See:
http://docs.sun.com/app/docs/doc/819-3671/ablih?a=view
thanks,
-Alexis
glassfish_at_javadesktop.org wrote:
> If you have Java Studio Creator with application server 8.x, you may use the migration tool, that's fine, it make sense.
>
> But the individual needs are unique. In my case I completed my project few months ago, archived the project and backed up the .war file. Now in my complter Java Studio Creator uninstalled and what I have is the .war file and Glassfish. Will it make sence if I have to reinstall the IDE to use the migration tool?
>
> If Glassfish is based on standards, it must make the .war file work properly. If Java technology is independent of platform, it should be independent of a migration utility.
>
> Thank you.
> [Message sent by forum member 'sariga' (sariga)]
>
> http://forums.java.net/jive/thread.jspa?messageID=246062
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>