Debugging a EJB

[tobiashoess]

Hello,

i develop a J2EE Application with Netweaver Developer Studio on Web AS 6.40 Sneak Preview. A jsp call a servlet and the servlet uses a EJB. Is it possible to debug the code of the EJB? I always get the message, that the source code was not found.

Thanks

Tobias

[tobiashoess · Accepted solution]

I tried the tutorial, but there is only described, how to debug a servlet or a jsp. I can debug the servlet or the jsp, but i can't jump into to the Bean Object/methods of the bean. I can deploy the the application, and the application with the EJB is running.

[SvetoManolov · Accepted solution]

Hello,

every EJB call goes through server-generated proxy objects before invoking the implementation of the business method in the bean class. The proxy classes are generated by the J2EE Engine during the application deployment, so they are not part of the IDE EJB project and their code is unknown for the debugger.

I would propose you to set a breakpoint in the beginning of your business method implementation. From the moment the call leaves the servlet till the moment it enters the bean's business method it goes through the server-generated code which sould not be relevant for your debugging.

Regards,

Svetoslav

[Benny · Accepted solution]

This is impossible. If your JSP is using a bean whatsoever, you will access this code and therdfore run into it with the debugger.

Did you try setting a breakpoint for your bean?

Did you walk through step by step?

Does your web page call the bean anyway?

Regards,

Benny

[Benny]

There is a tutorial for debugging in the manuals. Did you try that?

Regards,

Benny.

[Former Member]

Well...the first obvious question is that do you have all the EJB source code in your debuggers path and have you compiled the sources in debug mode?

Cheers,

Kalle

[Benny]

Kalle,

it's surely not necessary to compile in debug mode. You do not have to recompile or even redeploy if going in debug mode.

Regards,

Benny