Performance of controller code vs bean in webdynpro

[Former Member]

I have a general question regarding performance in web dynpro java applications. We have an application that reads data from a file on the presentation server, parses it, does some heavy calculation of the data, then spits it back out to another file. Currently the calculations of the data are implemented in the Component Controller of the web dynpro application. We are starting to see some performance degradataion as larger files are being processed. Is there a performance impact of doing these calculations in the Component Controller vs creating a bean model? Would doing these calculations in the bean make things slower/faster/no visible difference?

Any thoughts would be appreciated.

[Former Member · Accepted solution]

Hi

Disadvantages :

1 . Time elapse in calling the bean

2 . Time for populating the values in the bean class

3 . Time for Returning the values back.

Advantages :

1 . Its a Structured and Standard way of coding.

2 . Its Easy for coding and maintaining and enhancements.

As heavy calculations are involved with your application from a long time view its better you go for using seperate bean for this case

Regards

Abhijith YS

[Former Member]

JavaBean model allows us to introduce an additional layer of abstraction that has some great benefits like hiding the underlying service, improves availability and performance