|
Sorry - apparently I wasn't clear enough.I would never even consider COBOL as a web UI tier. RPG-CGI is bad enough... COBOL-CGI? Please, kill me now.
I was including such back-end component generation in the term "batch". I understand that I can create a back end component in RPG/ COBOL/whatever and call it from EGL that's fine. And from what you are saying, maybe I can use EGL to write that back-end piece and gen it in COBOL which is goodness (although not as good as in the days when I didn't have to pay for that extra compiler <grin>). I meant from the perspective of the UI.
In other words - am I always going to have an App Server/Java/JSPs in the mix? I have several customers where that would simply rule the tool out of the game.Yes, you are always going to have Java EE in the mix. Since EGL uses JSF as its thin-client browser interface, there's really no way around that.
Maybe the Eclipse desktop environment will allow for an alternative at some point in the future.Actually, you could use EGL to generate rich client on the browser which would consume RPG or COBOL business logic as a web service. And then you could use one of the i tools to wrap EGL-generated COBOL as a web service. It's a Rube Goldberg solution, but if it's more important to avoid Java EE than to have a cohesive solution, then this is your best route.
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.