 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | Porting an existing J2EE application : weblogic - > jboss | Porting an existing J2EE application : weblogic - > jboss 2004-08-19 - By Guy Katz
Back
1. i cant offer a plan.
but i'd say the key for AS porting is proper application packaging because
there are subtle differences in AS classloading schemes.
changing the vendor specific DDs is not that big a deal.
if the applicatiojn code is badly written, you might have to change some of
it to port the App.
2. if you are reffering to
http://www.jboss.org/index.html?module=html&op=userdisplay&id=services/bea-p
ort , i havnt worked with it but most of the stuff that jboss produces are
very handy.
-- --Original Message-- --
From: An interest list for Sun Java Center J2EE Pattern Catalog
[mailto:J2EEPATTERNS-INTEREST@(protected)]On Behalf Of Peter Petrov
Sent: Thursday, August 19, 2004 2:49 PM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Porting an existing J2EE application : weblogic -> jboss
Hi all,
We have a task of porting a complex existing J2EE application which is
currently running on weblogic 7.0 to jboss 3.2.x.
I have one very high-level and one concrete question.
1) In general what is the right point to start from when such a task arises
?
The application is pretty complex ( though not rocket science of course ).
There are
parts of it which are nicely implemented and parts which are badly
implemented.
Another factor is we don't know everything about it from a business point of
view.
So does anyone have an idea what kind of plan can we make at first about the
steps we
should take for implementing that porting to JBoss.
The plan would be for our own usage. I think it could can also help
ourselves
maintaining a clear idea of the steps we follow during the process a porting
and also give
us a mechanism for estimating our progress in implementing the task.
Having even unprecise or too high-level plan and mechanism is still better
then having no
such plan/mechanism at all.
2) My second question is more technical, more specific. Has anyone used this
http://www.jboss.org/index.html?module=html&op=userdisplay&id=services/bea-p
ort ?
If so what do you think about it ? Is it applicable and really doing its job
?
One more thing - on the page I mention above they say this tool is
applicable for
Weblogic 6.1 while our application is running on Weblogic 7.0.
Could that be a big problem if choosing the above tool as a helper one for
doing
the port to JBoss.
Peter Petrov
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
listserv@(protected)
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
