[JoergStoll]

Greetings,

we are currently evaluating whether MyEclipse Blue 8.5 would be a valid alternative to RSA 7.5

While the evaluation has been progressing well so far, we have recently run into a problem when deploying EJB 3.0

projects on WebSphere AS 7.0.0.9

After starting the server in debug mode from inside MyEclipse Blue and deploying the EAR that contains the EJB,

using the remote debugger MyEclipse Blue automatically provides works fine.
However installing breakpoints into the EJB source code fails with the following error:

Unable to install breakpoint in (EJB class) due to missing line number attributes. Modify compiler options to

generate line number attributes.

This error only occurs when installing breakpoints in EJB classes, debugging webservices or other classes within the

same EAR works fine.

Any help would be greatly appreciated.

Thanks
Joerg

[JoergStoll]

To test this behavior I have imported the entire EAR Project into RSA as well. Testing different startup and

deployment strategies resulted in the following:

Scenario 1:
Starting WebSphere from within RSA in debug mode
Deploying the project from within RSA
Result:
Debugging in MyEclipse Blue works perfectly
Debugging in RSA works perfectly

Scenario 2:
Starting WebSphere from within RSA in debug mode
Deploying the project from within MyEclipse Blue (using the WebSphere remote connector)
Result:
Debugging in MyEclipse Blue fails due to missing line numbers
Debugging in RSA fails due to missing line numbers

Scenario 3:
Starting WebSphere from within MyEclipse Blue in debug mode
Deploying the project from within RSA
Result:
Debugging in MyEclipse Blue works perfectly

Scenario 4:
Starting WebSphere from within MyEclipse Blue in debug mode
Deploying the project from within MyEclipse Blue
Result:
Debugging in MyEclipse Blue fails due to missing line numbers

Something seems wrong with the way MyEclipse deploys EJB projects on WebSphere. I have found that during deployment

MyEclipse Blue starts the WebSphere ejbdeploy tool to recomplie the ejb classes, while RSA does not. Adding -debug

-codegen -trace etc… to the ejbdeploy command line does not help.

[Brian Fernandes]

Joerg,

Thanks for taking the time to document your findings and carry out such a suite of detailed tests. Our Blue team is going through your report right now.

We have noticed certain problems with our use of the ejbdeploy tool and that is very likely the culprit in this case as it changes the way the EJBs are compiled. We are most likely going to to remove that flag or make it’s use optional in the next release of MyEclipse – something you could test in about a week or two with MyEclipse 8.6M1. If any workaround is found in the interim, I will add a note here.

Thanks gain for the support and I trust you will enjoy the rest of what MyEclipse Blue has to offer.

[dkmankotia]

Hi Brian,

We are also evaualuating Myeclipse blue for migration from RSA. Can you tell me how we can pass -codegen and -trace options to ejbdeploy because All my ejbs are failing compilation.

Regards,
Deepak

[Brian Fernandes]

Deepak,

Thank you for asking. We don’t allow you to control those options right now, but are looking at making these settings more flexible. Do you know for sure that you do need ejbDeploy to be run with those options? How are you specifying them in RSA?

[Author]

Posts