6 ms·
Anyone thought they were pretty good at reading source until they encountered a Spring application context spread over multiple XML files.
by ishbits 14y ago
Anyone thought they were pretty good at reading source until they encountered a Spring application context spread over multiple XML files.
- ajuc 14y agoWe had 2 tier application - Rich client in Qt3 based framework and PL/SQL for "servre side". We moved to J2EE using EJB3, Hibernate, Eclipse RCP. Our application was meant to be 3-tier, but actually it's more like 10-tier. We have hibernate mappings, java model, xml files specyfing possible queries and reports, java EJB3 beans wrapping these xml files, java classes for DTO, xml files specyfing possible views and editors in RCP, and xml files specyfing how to map from query to view or editor. And java classes for custom code in views/editors. When I want to see what database column is shown in view, I need to start with view class, and descend all those layers down to hibernate mapping. In our previous qt framework we had one xml file per client view, specyfing columns/sorts/filters/etc just for this view. Our consultants understood these files and changed them when they needed to. Now they would need to understand all those layers. Now I think more than 2 layers in application is antipattern.