BES5.2.1 to BAS6.6 ejb migration

"desmond.kirrane@gmail.com"dk

unread,

Sep 25, 2007, 8:50:27 AM9/25/07

to

We have old EJBs created using legacy JBuilder IDEs (releases 7 and previous).

The EJBs are contained within a .ejbgrp file. The .ejbgrp contains the following deployment decriptors:
ejb-jar.xml : the standard deployment descriptor
ejb-inprise.xml : the legacy Borland proprietary deployment descriptor

BAS 6.6 ejbs use the following deployment decriptors:
ejb-jar.xml : the standard deployment descriptor
ejb-borland.xml : the Borland proprietary deployment descriptor

Problems:
1. JBuilder 2007 Enterprise only has a runtime mapping for BAS 6.7 eventhough the documentation for JBuilder says it supports BAS 6.6 also.

2. JBuilder 2007 creates EJBs using XDoclet. XDoclet annotations are embedded in the EJB code.
These annotations are then used to create the above deployment decriptors and EJB Interfaces.
We do not want to recreate our legacy EJBs using XDoclet as this will take up too much time to migrate.

3. We tried migrate our BES5.2.1 install to BAS6.6 install with the migration tool but it doesn't recreate any of out ejb-jars or wars correctly.
All ejbs fail with java.lang.ClassNotFoundException
All wars fail with ERROR - Digester.getParser: java.lang.ClassCastException ERROR - Parse error in default web.xml java.lang.NullPointerException

4. We tried import our legacy JBuilder project into JBuilder 2007 using the import wizard. However the import doesn't do anything with the .ejbgrp file or the deployment descriptors.

Questions:
Is there any way to easily convert the ejb-inprise.xml files to the new ejb-borland.xml file?

Kevin Dean [TeamB]

unread,

Sep 25, 2007, 9:15:15 AM9/25/07

to

"desmond...@gmail.com" DK wrote:

>Questions:
>Is there any way to easily convert the ejb-inprise.xml files to the new
>ejb-borland.xml file?

Regarding the import, the JBuilder 2007 legacy project import doesn't work
all that well to begin with, and probably won't work at all for such an
old version of JBuilder.

I'm honestly not sure what the difference is between ejb-inprise.xml and
ejb-borland.xml. What I would suggest is this:

1) Create an EJB 2.0 project.
2) Create a couple of beans in the project.
3) Exit JBuilder.
4) Inspect the resulting files.
5) Copy ejb-inprise.xml in your old project to ejb-borland.xml and modify
the content to match the format of the new files (shouldn't be very
difficult).
6) Copy over your source files (*.java and *.xml) taking care to match the
exact locations of JBuilder 2007's files.
7) Restart JBuilder.

It's a pain, but that's the only way I can think of to do the migration
you want to do.

--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/

Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html

Lata Amujuri

unread,

Sep 28, 2007, 12:02:33 PM9/28/07

to

BAS has a command line migration tool that you can use to convert your
descriptors.

BAS\bin\iastool -migrate -src oldejb.jar -target newejb.jar -to 1.4

Note, according to BAS help:

"The migrate command only converts the deployment descriptor for an EJB; as
such, code changes may also be required to implement the conversion properly
in your deployment."

You could try doing this and then importing the project into JBuilder 2007

Lata

<desmond...@gmail.com DK> wrote in message
news:46f90413$1...@newsgroups.borland.com...