Webcast: Migrating from GlassFish to WebLogic

Logo

As previously announced, WebLogic Server is where Oracle is focusing it's commercial support efforts, supporting the increased delivery of bug fixes, new features, and Java EE 7 APIs.  Which is something our customers are keen to experience.

We will continue to invest in GlassFish as the reference implementation for the Java EE platform, which will continue to be a good option for users to deploy their applications using an open source product.  We will continue to develop and release the GlassFish Open Source Edition.

We are seeing that many GlassFish customers and users want to be on (or move to) a supported application server. Customers of Oracle GlassFish Server may now start planning the migration with ease, and users of GlassFish Server Open Source Edition can start studying the when's and how's of such migration.

Which is why for those who are looking forward to experiencing the feature-rich Oracle WebLogic application server, I will give you in this developer webcast an overview of Oracle WebLogic Server and take a sample Java EE application to walk you through the most common migration scenarios to get your applications redeployed on WebLogic. You will hear about:

  • WebLogic Installation Process, Architectural Concepts, and Clustering Setups
  • Migration of Common Java EE Resources (JDBC, JMS)
  • Seamless GlassFish to WebLogic Redeployment
  • Advanced Classloader Analysis and Configuration
  • Shared Libraries
  • Tools to automate massive migrations
Date: Wednesday, April 30, 2014
Time: 10:00am PT / 1:00pm ET
Register for free online event today

Watch the webcast, and if you have questions, send to me over Twitter at @brunoborges and I will be happy to answer them!


Comments:

Hi Bruno,

I am having difficulties migrating an app from GF to WL.
I made a little testproject that shows the problem:
https://github.com/ddijk/WeblogicCdiIssue.git

This app deploys fine to GF but fails on WL when CDI is enabled. If I remove "beans.xml" it deploys fine to WL also.
So somehow, enabling CDI causes the problem.
I did some investigation and it looks like Struts tries to load a factory via reflection and this fails on WL.
Apparently CDI changes the classloading in such a way that the Struts Factory class is not (yet) available to the classloader.

I hoped to workaround this problem using weld:scan to exclude CDI scanning on the Tag class, but this did not help because it seems like CDI tries to load the class anyway.

Do you have a solution for this?

Posted by Dick on April 25, 2014 at 06:36 AM PDT #

Hi there,

Please make sure to check My Oracle Support for any existing fix for this issue, or submit a new Service Request and let our Support team take a look at that.

Thanks!

Posted by Bruno Borges on April 25, 2014 at 11:12 AM PDT #

Post a Comment:
Comments are closed for this entry.