Community
Participate
Working Groups
The current EMF-based models in DTP components were last generated with EMF 2.2.2 in order to support JDK 1.4.2. DTP is now upgraded to build with JDK 1.5 and EMF 2.4.1 for the Galileo release. All the EMF-based models in DTP (including Query Model, SQL Query Model, ODA Design Model) should be upgraded in Galileo and re-generate using EMF 2.4.x. Such upgrades will need to provide backward compatibility handling of those model objects that were persisted using older DTP releases.
Hey Hemant... Did this ever happen? I'm guessing so and we just need to close it...
let me double check on the Query Model, SQL Query Model, ODA Design Model and get back.
Hi Brian, i checked all ecore models and all of them seem upto date except for below. could you and Linda check if the models in the following plugins are at Eclipse3.4/EMF 2.4 level. org.eclipse.datatools.connectivity.oda.design i see a lot of difference in generated code if i use the ecore file as source as compared to the code in CVS. org.eclipse.datatools.enablement.sybase.asa.models i got some errors related to default values when i tried to reload the genmodel. the errors did not pinpoint where in the model the offending default values were defined.
Max or Samuel, can you take a look at the ASA model to see what's going on and why it's not regenerating properly? We need to get all the models regenerated with 2.4.1 to better support the Galileo release.
Samuel, please look into this asap. Thanks.
Created attachment 133044 [details] update ASA emf model Remove useless 'defaultValueLiteral=""' to avoid emf genmodel error.
Created attachment 133054 [details] Patch - upgrade ODA design model to EMF 2.4.x Committed patch of oda.design plugin, whose source are re-generated with EMF 2.4.1 and JDK compliance level 5.0. Applied tag v200904241122.
(In reply to comment #6) > Created an attachment (id=133044) [details] > update ASA emf model > > Remove useless 'defaultValueLiteral=""' to avoid emf genmodel error. > Delivered. Tag v200904240306
Hemant, can you take a look again to see if this has been resolved?
yes. though i have a question for Linda. the DesignXML.xsd under model folder in the oda.design plugin does not seem to be the source for the oda.design.ecore model. because if i used DesignXML.xsd to reload the genmodel and regenerate the ecore and code, i see a whole lot of differences. that was what i had observed. i defer this to Linda to make the call on this as she is more informed about the model then i am.
I'd used odaDesignSession.genmodel as the base to re-generate the source. The DesignXML.xsd is also generated/exported from genmodel. I have now also added its model files in the binary build.
Can we consider this done?
Assigned to Kamal to confirm whether the tasks (from Linda and Song Lin) are considered done.
1.7M7 is already in test stage, moved to 1.7RC1 for now. Please confirm if it's considered done. Thanks.
Hemant? Is this already to be considered done?
Since I have heard nothing from anyone about this, I'm going to consider this fixed.
sorry, Brian. had meant to reply last week but got distracted. yes, after the taks done by Linda, Song Lin, we can consider this done.
