Community
Participate
Working Groups
Build Identifier: Use Java2EGL generator to generate service and library from an entity record definition. See Bug 367261 for more details. Reproducible: Always
After reviewing the SQL Record to EGL wizard, I believe that we lead you down the wrong path by recommending that Java 2 EGL be used to implement this solution. The SQL Record to EGL Wizard currently uses the EglSourceGenerator, which is located in the /org.eclipse.edt.gen.generator.eglsource plug-in. This generator walks a Data Tools Object (Java class) and emits an EGL Record (i.e. there are NO IR files involved). I think it would be best if the Service and Library wizards extend this generator to emit a Service or Library based on a DTO. This should avoid the need to re-parse the newly created EGL Record to find out what information was used by walking the Data Tools Object. In the Service/Library wizard, we can run both generators to produce both the Record and the Library/Service. NOTE: It may also be worth while to ask Jeff, Matt, or Joe if there is precedence for one generator producing two types of artifacts, in which case we can follow that approach here and produce both the record and Service/Library in one generator.
I agree with this approach. One thought: the length of the service/library expected to be generated by this wizard is long (hundreds of lines). I wonder if the generator should read a file that contains the base content for the resulting service/library and then substitute strings throughout the file. This would make it easier for us (and possibly others in the future) to alter the source in the future. It would also require a LOT less code in the generator. For example, a line in the template file might look like this: function get{$TypeName}(id int in) returns ($TypeName) The generator would substitute in the appropriate values. I would definitely suggest following a pre-defined pattern - like in the current code templates in Preferences > EGL > Code Templates - and not try to invent some new syntax for this.
I discuss with Jeff about how one generator produce two types of artifacts yesterday. Jeff said one generator only can produce one EGL file. If need to produce multiple EGL files, we need to modify the generator or call generators multiple times. I created a new Java2EGL generator extends EGLGenerator, and make is return a Hashtable<filename, filecontent> after the generation operation, then save the files in the UI wizard performFinish function.
Sorry, the a new Java2EGL generator extends EGLSourceGenerator instead of EGLGenerator
=== Comment from Brian === I am wondering if it makes sense to extend the EGLSourceGenerator, or if we should just modify the EGLSourceGenerator to always return a map of EGL Source files. This could also be tied into the fact that we want to generalize the Summary page of the wizard to always display a drop down for the file names if more than one file is available. A general solution would allow us to write a Summary page for all EGLSourceGenerator users, where both the generator and the wizard page are capable of handling the creation of multiple EGL files. This also seems like a good opportunity to test the extensible nature of our generator framework, where the Record, Service, and Library wizards will be contributing a different set of Templates to the same generator via the contributor.
fixed
