|
Joe, Did your tone just get a little harsh or I am I reading something into it? > How often is code ENTIRELY stable, Mark? Be realistic. You made it sound as though this code is changing infrequently, for example, I consider JT400 to be "stable". You get periodic new releases. If you are only changing your code once a month packaging it into a JAR is not a hardship. > Well, you disagree with every text on JIT compilers that I've read, > including the white papers from IBM. Who should I believe? The guys that > write the compilers or you? Just talking about what I have observed. I do not believe I passed myself off as an authority. Please send me links to those white papers though. I do not believe it would be even remotely possible for the JIT process to be effected by JAR or no JAR. I do think it could effect class loading however, which is also a performance consideration. > Why does a web application need a lot of small loosely related classes? My > architecture doesn't. My architecture never adds new classes, with the > exception of the JSPs. This seems a much more rational approach to web > design. I may have been misunderstanding all along. Are you saying you would like the .class files that are created for your JSP's to all be bundled in a JAR? I am not aware of anything that would do that. I am not sure it would even work if you did it manually, because the JSP compiler engine would probably just see the JSP as not having been compiled. I could definitely be wrong on that though. I follow an MVC approach to design. I see the model as being the core API layer. I develop this in its own project and package it as one or more JAR files that are updated on some kind of periodic basis. We use these same JAR files in our Web application, our Eclipse plugins, and other Java-based UI. My view layer is specific to the UI's I just mentioned, in the case of a web application it is JSP's that are used from Struts. These JSP's are logicless. They just display the data they are given. My controller layer in web applications is Struts. This leads to a lot of little classes that go go out and get data from the model layer and present it in the view layer. When I say loosely related, I mean that one of these classes does not interact directly with another similar class. They are only called by Struts and they only access our model and Struts. These are deployed as .class files under my WEB-INF/classes folder. Hope this helps. Mark
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.