this application without weblogic.xml, is that the application will start just fine, but in a different context-root: the one you typed inside glassfish-web.xml.The reason for this is well documented on Support for GlassFish Deployment Descriptors. Give it a look in case you want to know what else does WebLogic understands from GlassFish's DD.Now, let's try something different. Let's now use pure Apache Maven to compile and run the application on your WebLogic installation! For that, we will first need to configure the plugin.Configuring the WebLogic Development Maven PluginBefore you can use the plugin, you must install it in your local or remote Maven repository. Feel free to follow official instructions for WebLogic 12.1.2. But in case you want to just get it done, here's the short version:Go to your WLS installation. It is probably located here:/opt/wls12120Now change to the following directory:$ cd oracle_common/plugins/maven/com/oracle/maven/oracle-maven-sync/12.1.2 Issue the following command to sync WLS Maven Plugin into your local repository:$ mvn com.oracle.maven:oracle-maven-sync:push -Doracle-maven-sync.oracleHome=/opt/wls12120/oracle_home/.You have now successfully installed WLS Maven Plugin. To validate the installation, type:$ mvn help:describe -DgroupId=com.oracle.weblogic-DartifactId=weblogic-maven-plugin -Dversion=12.1.2-0-0To continue, let's configure the plugin onto our bookmark-javaee6 sample application, and then deploy the package into WebLogicOpen the POM file of bookmark-javaee6 projectUncomment the WebLogic Maven Plugin definitionMake sure to enter the same username and password as your domain when you installed and configured WebLogicMake sure WebLogic is runningMake sure there's no other bookmark-jaavaee6 project deployed on your WebLogic instanceExecute the following command:$ mvn package pre-integration-testCheck your logs and try http://localhost:7001/bookmark-javaee6!ConclusionAs you could see, if you are working with a Java EE 6 project 100% standardized, and perhaps Maven, you will find no problems at migrating this project to WebLogic 12c. In fact, if you are using Maven it will be as simple as adding a new plugin just to facilitate deployment. But even this you won't have to do in case you have a binary only. Just open the Admin Web Console, and fire a deployment from there!And by the way, WebLogic is not that heavyweight and unproductive application server developers thought it still is. For more information about Developer Productivity with WebLogic 12c, read my entry "WebLogic in Comparison: RebelLabs and the Java App Server Debate".Caveats for Java EE projects, road ahead for migrationsIn the next blog posts of this series, I will cover how to work around some common issues when your project is not exactly following, or taking advantage of all standards defined in the Java EE 6 platform, or simply using extra features, customizations of GlassFish.Here's a sneak peek of what's coming next:How to Migrate JDBC DataSources from GlassFish to WebLogicHow to Define, Deploy, and Use JMS resourcesHow to Migrate JMS resources from GlassFish to WebLogicHow to Add and Isolate (classpath of) 3rd-party libraries (for example PrimeFaces)And many more things to come!Applying a GlassFish Domain Topology to a WebLogic Domain (clustering, etc)Migrating Security RealmsMigrating Custom Login ModulesIf there's any other subject you'd like to see, please post a comment!Cheers!