Web Dynpro DC vs. EJB

[Former Member]

Hello all,

I want to create a central method for connecting the DB from WebDynpro.

In some of the documents its recommended to create an EJB for that purpose.

Can anyone tell me why is it more recomended than using a webDynpro DC?

Thanks, Adi.

[Former Member · Accepted solution]

Adi,

If you place your logic in EJB then you be able to:

have several client technologies (pure J2EE Web, WebDynpro, desktop). Plus it is possible to expose business logic via WebService-s or similar B2B technology.

This is not possible if you code your logic directly at WD ( client ) layer.

Valery Silaev

EPAM Systems

http://www.NetWeaverTeam.com

[Former Member]

Thanks (-;

[Former Member]

Hi,

I was put up with the same question but i went for a Java DC, which inturn is consumed in an EJB.

One simple reason is:

An application can have webdynpro components and regulat java components (say Java DC). A Java DC can be consumed in a webdynpro DC but a webdynpro DC (say you have implemented the connection configuration in Controller) cannot be consumed in Java DC.

So for having a single point of control on DB Connection for webdynpro and java components we generally go for a Java DC component which will provide connection (JDBC and RFC).

Hope that helps.

Regards,

S.Divakar