Reasons for EJB Models in Webdynpro JAVA

[Former Member]

Hi All,

Could you kindly share the primary reasons for usage of EJB Models in Webdynpro JAVA?

Best Regards,

Suresh S

[Former Member · Accepted solution]

Benefits of Java Bean Model Layered Approach

Clear segregation of responsibilities.

Clear rules of behavior.

Reduces coupling of layers – presentation vs. business layer.

Hides details of underlying layer, such as EJB lookup logic, business implementation, etc.

Using Command Bean Pattern exposes commands in addition to properties (Java Bean). Methods

take no arguments, context is JavaBean state.

Using Java Bean Models mapped to context variables in Web Dynpro will make the life of the

developer much easier as he does not have to populate manually the context variables in Web

Dynpro Component and View controllers.

Please check in

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70d2638c-4b04-2d10-d2a3-992fdf1e3...

Thanks,

Patralekha

[Former Member]

Hi,

I don't know if it is the primary reason but I have used EJB models to wrap CAF services in the past.  You could argue that EJB models could be used to call services that can't be WS enabled via SOAP, or alternatively for potential performance gains by not going through the SOAP layer and instead calling the EJB direct.  You might have business logic exposed via EJB in your landscape too that you want to re-use in your WD.

As with many things, there are often many ways to skin a cat.

Gareth.