|
Joe, Just so it is clear up front, I am not debating whether your architecture is better than WebFacing, I think you architecture sounds very well designed and thought out. I do want to question you on a few points you are raising. 1) You criticize WebFacing for using war/ear deployment but this comes straight from J2EE. Can you explain how you install a PSC/400 application in WebSphere without packaging it in a war or ear file? 2) You say that your architecture is easier than WebFacing because you just have to copy the changed JSP to the server, yet this is exactly the same way you do it with WebFacing (albeit with a lot more files). Again, why is it acceptable when you do it, but unacceptable when Buck does it? By the way, WebSphere Studio can deploy changes directly to a WebSphere server. I am not sure if it worked with the iSeries in 4.x, but I believe it does with 5.x. You can definitely do it to remote Windows/Linux servers in 5.x. Of course I would recommend using a change control system to do this, but I am obviously biased. Mark
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.