Bug 1064552 - WebLogic: Review email entitled Application Migration: Weblogic libraries used in legacy applications
Summary: WebLogic: Review email entitled Application Migration: Weblogic libraries use...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: EAP 6.3.0
Assignee: sgilda
QA Contact: Russell Dickenson
URL:
Whiteboard:
: 1064553 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-12 20:07 UTC by sgilda
Modified: 2015-06-05 14:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-05 13:55:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description sgilda 2014-02-12 20:07:19 UTC
Description of problem:
Email sent to se-jboss from Kunal Limaye <klimaye> on 2/11/2014

Team,

We are working on an opportunity in Melbourne, Australia where in the prospect is looking at migrating their existing application (which is a SaaS platform) from Weblogic to JBoss.
One of the discussion items was their current use of Weblogic specific libraries (jar files) referenced by the application; and more importantly how that would look like in JBoss world.

I wanted to reach out to the wider team to see if we have any knowledge in terms of which JBoss/JEE libraries would perform equivalent function provided by the the following Weblogic libraries. I am hopeful that we have some knowledge to share especially with activity within our JBoss Cake/Windup project.
Thanks in anticipation.

    Weblogic JMS queue
    Weblogic deployment descriptor (weblogic-application.xml, weblogic.xml)
    au.com.hubbub.weblogic.jms.DelayedQueueSenderPolicy
    org.springframework.transaction.jta.WebLogicJtaTransactionManager
    org.hibernate.transaction.WeblogicTransactionManagerLookup
    com.yarris.weblogic:weblogic-log - Dependencies required to redirect log from Weblogic System logger to Log4j.
    FaxMonitorPoller, FaxProgressPoller - weblogic.management.timer.Timer timerMBean
    Weblogic ejb deployment descriptor (foo-weblogic-ejb-jar.xml) for (63 Stateless Session Beans)
    DelayedQueueSenderPolicy - weblogic.jms.extensions.WLMessageProducer
    Pulse generated ejb deployment descriptor
    weblogic-ejb-jar.xml (around 200 BMP EJB 2.1)
    weblogic libraries for ejb compilation
    maven plugin for weblogic ejb compilation (around 20 jars)
    weblogic.wsee.util.StringUtil - in 3 classes, should be removed
    maven plugin for jsp compilation

Regards,
Kunal

-----
Kunal Limaye

Reply from Brad:

Have you run Windup against the application?

The delayed queue sender policy probably maps to Message Delay, which isn't part of the EE spec.  If they are using JBoss AMQ or HornetQ, there are some additional properties that can be set to the message including : https://activemq.apache.org/delay-and-schedule-message-delivery.html

Weblogic JMS queue should be straight forward... HornetQ / A-MQ.  You should convert this to a standard JMS Queue object to support JEE.
Some of this is covered with Windup for Weblogic descriptors.  
Windup already documents the Weblogic Logger and migration to Log4j or SLF4j.
Weblogic Timers should be converted to either a) EJB Timers or b) Quartz depending on the strategic direction.
EJB 2.x should work in JBoss.  

Brad Davis


Version-Release number of selected component (if applicable):



How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Scott Mumford 2014-02-14 02:08:01 UTC
*** Bug 1064553 has been marked as a duplicate of this bug. ***

Comment 3 sgilda 2015-06-05 13:55:28 UTC
Closing this issue because it was moved here: https://issues.jboss.org/browse/WINDUP-628


Note You need to log in before you can comment on or make changes to this bug.