If this is true, does it also holds true for n-tiers, only with an additional application server component?
If this is not the case, can you set some examples of a 3-tier or an n-tier architecture that does not involve a browser and a web server? [ October 06, 2007: Message edited by: J Vallejo ]
Originally posted by Narendra Dhande: The Integration tier and Resource tier is combined in this diagram. I think they should be separate.
Aren't both tiers one and the same?
Look how Sun mix both names when it describes the DAO Patternhere. In the diagram they call the tier, where DAO is embedded, Integration tier while in the description of DAO they call it Resource tier. [ October 09, 2007: Message edited by: Darya Akbari ]
I think three tier is very much the idea of a client tier with an visual front end, a middle tier mitigating access to back end data, and of course, the third tier being the back end. Certainly in that regards, any stand-alone Java application interacting with middle tier technology, such as SLSBs or SFSBs, would indeed be a non-browser based 3-tier implementation.
Am I right to say that web services should be linked to the business tier?
Here is how I implemented a web service using spring framework:
Web Front-End Business tier - Web Services DAO
is web service the 4th tier?
I work with the following technologies: Webwork 2.2, Xwork, iReport 0.5.2 Jasper Reports 1.1.0, JSP 2.0, CSS, Java Script, Hibernate 3.0.5, MySQL 4.1.7, Eclipse 3.1, Tomcat 5.5.9, JBoss 4.0.2. Any Doubt? ask me, denon82@msn.com