[Mork]

I hope that MyEclipse 6 fixes the bug, as R had promised, when debugging an enterprise project with Weblogic where every time you debug, you have to add the workspace folder so you can actually see the source code.

This is is a terrible bug.

Thanks.

— M

[Riyad Kalla]

Mork,
I just double-checked the status of this bug, and the developer confirmed the issue and posted this workaround:

Create a launch config and use the debug menu to launch WebLogic. All changes
to the source lookup path are preserved. No changes to MyEclipse are necessary
for this workaround.

Could you test that and see if it does infact fix the problem? If it does, the developer knows how to fix the issue.

[Mork]

I’m disappointed by this reply message.

You wouldn’t ask a car customer to put duct tape around his tire if it’s leaking or ask him to re-wire the alternator if the car wasn’t starting.

So why then would you ask your customer to create a special launch configuration to “fix” a product defect that’s clearly on your side?

Plus, you promised to fix this WebLogic debug bug in version 6.

Therefore, please fix it. You have no idea how annoying this bug is.

Thanks.

– M

[support-michael]

I apologize for my tardiness to this tread. I have two points to discuss.

1) I want to correct a statement we made that using a the custom launch configuration mechanism is a workaround for a bug. This is just not true. The default appserver launch model that has been used by MyEclipse for 5 years while very powerful is basic regarding its support mechanisms for src code location and persistence. Several years ago we introduced the more advanced launch configuration support to give our connectors more customization support and to go beyond the simpler version’s scope. Thus I do not view our recommendation to use a launch configuration as a workaround for a bug. It is a more advanced and smarter mechanism that we rely upon when an appserver+project configuration have requirements that extend beyond the basic appserver connector’s mechansims. Weblogic with certain project configurations happens to be one of those cases that occasionally requires the more advanced launch model. Creating the launch configuration needed is as simple as pressing the ‘Create Launch Configuration’ button on the preference page at Window > Preferences > MyEclipse > Application Servers > WebLogic x.y > Launch and is provided to make this more advanced usage as simple as possible. So I apologize that we did not establish this fact earlier in this conversation and for the false negative of conceding to what is not technically a bug.

2) We are interested in learning how we can improve the basic Weblogic connector. In ME 5.5 the src lookup and persistence should be operating properly for most deployment/debug scenarios. But from this tread it is clear you continue to experience a problem with the debugger loosing src attachments. Can you share with us the exact scenario for us to replicate? Presently, we know of only 1 scenario. That is, src attached to an external jar on a deployed project’s buildpath. For this case the more advanced launch configuration model should resolve the problem. Are you seeing this case or something different? Any specific information you can provide will be most appreciated.

Regards,

[Mork]

Hi Michael,

The Enterprise project is deployed as an EAR file to WebLogic.

If I set a breakpoint in any Java Source file, start the browser and navigate to the page with the breakpoint, then MyEclipse pops up saying it can’t find the source code and gives me an option (each time I debug) to add the source folder.

Thus, I go to the workspace/src folder and add it every time. Unfortunately, this project is not set to a hot deployment, which adds more time to each build and debug cycle.

In fairness, I see the same situation using the JBOSS IDE that others on the team are using so it may be another issue. Since “rkalla” said it was a MyEclipse bug a while back, I just continued on this assumption.

I look forward to your reply.

Thanks.

M

[Scott Anderson]

M,

How are you deploying this project? Are you using our deployer or your own Ant task for example? Do you see the same issue if you deploy to JBoss from MyEclipse as you do from WebLogic?

[Mork]

It’s an Ant script that builds the EAR.

The EAR runs the application fine.

I wish I could use the MyE deployer, but the project wasn’t setup with that in mind.

The JBOSS test is a great idea. I’ll try that shortly and let you know.

Thanks!

– M

[Scott Anderson]

Mork,

The issue is likely that your Ant script is recompiling the java code and not setting the debug flags properly. This prevents
the debugger from finding the source. The default flags change from Ant release to Ant release and we’ve seen an
upgrade to the new Ant version that Eclipse include cause this issue as the defaults silently change. To correct, please
adjust your Ant scripts to explicitly set the debug flags in the Java tasks exactly as specified in the current version of the Ant documentation.

[Mork]

I’ll look into this, thanks!

This would also explain why it happens in other IDEs like JBOSS’.

Thanks again.

🙂

M

[Author]

Posts