ADF and design patterns, comparison with Struts
442847Jul 4 2007 — edited Jul 5 2007I was looking into SRDemo source code, its managed beans, backing beans etc. and was wondering if ADF implements the design patterns in the sense other applications do, based for example on Struts MVC2, front controller, intercepting filter, command, application controller, view handler, view dispatcher, view helper, service to worker, synchronizer token etc? I am not very familiar with ADF but it seems to me there is a lot of "hacks" inside ADF backing, managed and other beans, interaction with binding containers etc. in comparison with "legacy" MVC and J2EE design pattern based applications. For example, in order to invoke a business (e.g. J2EE) service the managed bean (e.g. SRMain bean) has to go through all sorts of other classes, binding container layers, in order to invoke simple execution of a service. Comparing this with, for example, Struts Actions assembling DTOs, invoking business delegates, invoking business services (and all this wired with Spring) and presenting view using tags like display tag etc, I cannot but think that this part of ADF applications is much more difficult to maintain/design than these legacy MVC applications, which seems to have cleaner separation of concerns? This observation is only based on looking into SRDemo code and comparing this with corresponding application that could be written in, for example, Struts, Sitemesh, using Display and other tags, Spring.