Is the new WebFacing tool the first step to Web enablement?
Hi Nathan, Many good questions you have been raising. My recollection was that with both Jacada's and IBM's conversions, the output was Java code (AWT?) that, in Jacada's case, could be modified and enhanced, and in IBM's case, could at the least be enhanced to call additional code. IBM has too many things going for me to stay on top of. Is the Webfacing stuff being discussed strictly HTML output, or is the output for Java AWT clients? The reason I ask is that the difficult conversions you speak of are a different beast altogether if the conversion is to a Java client (source code generated in Jacada's case, or a Java client product with exit calls in IBM's case). Of course, if I'm mistaken and this is some super duper upgrade from 5250 Gateway web pages, then I would like to see what the constraints of the conversion are. Ralph
Hi Nathan, Many good questions you have been raising. My recollection was that with both Jacada's and IBM's conversions, the output was Java code (AWT?) that, in Jacada's case, could be modified and enhanced, and in IBM's case, could at the least be enhanced to call additional code. IBM has too many things going for me to stay on top of. Is the Webfacing stuff being discussed strictly HTML output, or is the output for Java AWT clients? The reason I ask is that the difficult conversions you speak of are a different beast altogether if the conversion is to a Java client (source code generated in Jacada's case, or a Java client product with exit calls in IBM's case). Of course, if I'm mistaken and this is some super duper upgrade from 5250 Gateway web pages, then I would like to see what the constraints of the conversion are. Ralph
Comment