Identify options used for Gen Classic Style Java Proxy generation
search cancel

Identify options used for Gen Classic Style Java Proxy generation

book

Article ID: 140385

calendar_today

Updated On:

Products

Gen Gen - Workstation Toolset

Issue/Introduction

In the process of a Gen upgrade to 8.6.
Have been given some old version Java Proxy files and told to generate similar proxies, but not sure what options were selected while generating those old Java Proxies.
Able to identify if "Use Classic Style API for Java Proxy" was selected, but not able to identify if the Asynchronous or XML options were selected.

Environment

Release : 8.6
Component : Gen Generator, Proxy

Resolution

1. When the Additional Programming Interface "Asynchronous" has been selected for a Classic Style Java Proxy generation/build the generated source code in file ...\proxy\java\src\<Server>\Abean\<Server_pstep>.java will contain several extra references to string "async" and defines 4 methods:
executeAsyncGetResponse
executeAsync
checkAsyncResponse
ignoreAsyncResponse
If only compiled files from the Java Proxy Build are available, the file <Server>.jar (from directory ...\proxy\java\deploy\Abean) will contain file <Server_pstep>.class which can be decompiled with a tool like JD-GUI to also verify above.

2. When the Additional Programming Interface "XML" has been selected for a Classic Style Java Proxy generation/build the source code in directory ...\proxy\java\src\<Server> will have an additional XML sub-directory and directory ...\proxy\java\src\Svr1\Abean will contain the Server PStep class file <Server_pstep>$<Server_pstep>Parser.class.
If only compiled files from the Java Proxy Build are available, the file <Server>.jar (from directory ...\proxy\java\deploy\Abean) will also contain the same file <Server_pstep>$<Server_pstep>Parser.class.

Additional Information

NOTE:
The older Classic Java proxy (version 1) has a different structure to the newer Standard Java Proxy (version 2).
If only the generated/built .jar files are available whether they were generated for Classic or Standard can be easily determined. In the Classic version, all types of generated/built proxy jar files will contain a Common folder. The Standard version does not reference any Common folder.
Gen™ 8.6 > Distributed Processing > Working With Proxies > Java Proxy > Java Proxy Interface - Standard
Gen™ 8.6 > Distributed Processing > Working With Proxies > Java Proxy (Classic Style)