| JET templates for interfaces missing with EMF 2.2.1 [message #56780] |
Mon, 09 October 2006 04:45  |
Eclipse User |
|
|
|
Hi All,
We had been using EMF 2.0.1 for code generation using JETEmitter
templates. EMF 2.0.1 codegen used to include following JET templates.
Interface_
PackageInterface_
FactoryInterface_
Now I found that EMF codgen 2.2.1 no longer included these templates. Does
that mean generated code (using JET templates) no longer include
XXXXPackage interface class which will be implemented by the
XXXXPackageImpl class ?
Thanks
Nalaka
|
|
|
|
| Re: JET templates for interfaces missing with EMF 2.2.1 [message #56835 is a reply to message #56808] |
Tue, 10 October 2006 06:47  |
| Eclipse User |
|
|
|
Thanks Merks.
Nalaka
Ed Merks wrote:
> Nalaka,
> In the 2.2 development cycle we introduce an option that allows clients
> to generate code that combines the interface and the implementation into
> a single generated result. For this reason, Interface.javajet and
> Class.javajet were merged into a single template able to generate the
> interface, the impl, or a combined result. A similar thing has happened
> for the factory and the package.
> Nalaka Gamage wrote:
>> Hi All,
>> We had been using EMF 2.0.1 for code generation using JETEmitter
>> templates. EMF 2.0.1 codegen used to include following JET templates.
>> Interface_
>> PackageInterface_
>> FactoryInterface_
>> Now I found that EMF codgen 2.2.1 no longer included these templates.
>> Does that mean generated code (using JET templates) no longer include
>> XXXXPackage interface class which will be implemented by the
>> XXXXPackageImpl class ?
>> Thanks
>> Nalaka
>>
>>
>>
|
|
|
| Re: JET templates for interfaces missing with EMF 2.2.1 [message #593785 is a reply to message #56780] |
Mon, 09 October 2006 09:09 |
| Eclipse User |
|
|
|
Nalaka,
In the 2.2 development cycle we introduce an option that allows clients
to generate code that combines the interface and the implementation into
a single generated result. For this reason, Interface.javajet and
Class.javajet were merged into a single template able to generate the
interface, the impl, or a combined result. A similar thing has happened
for the factory and the package.
Nalaka Gamage wrote:
> Hi All,
> We had been using EMF 2.0.1 for code generation using JETEmitter
> templates. EMF 2.0.1 codegen used to include following JET templates.
> Interface_
> PackageInterface_
> FactoryInterface_
> Now I found that EMF codgen 2.2.1 no longer included these templates.
> Does that mean generated code (using JET templates) no longer include
> XXXXPackage interface class which will be implemented by the
> XXXXPackageImpl class ?
> Thanks
> Nalaka
>
>
>
|
|
|
| Re: JET templates for interfaces missing with EMF 2.2.1 [message #593799 is a reply to message #56808] |
Tue, 10 October 2006 06:47 |
| Eclipse User |
|
|
|
Thanks Merks.
Nalaka
Ed Merks wrote:
> Nalaka,
> In the 2.2 development cycle we introduce an option that allows clients
> to generate code that combines the interface and the implementation into
> a single generated result. For this reason, Interface.javajet and
> Class.javajet were merged into a single template able to generate the
> interface, the impl, or a combined result. A similar thing has happened
> for the factory and the package.
> Nalaka Gamage wrote:
>> Hi All,
>> We had been using EMF 2.0.1 for code generation using JETEmitter
>> templates. EMF 2.0.1 codegen used to include following JET templates.
>> Interface_
>> PackageInterface_
>> FactoryInterface_
>> Now I found that EMF codgen 2.2.1 no longer included these templates.
>> Does that mean generated code (using JET templates) no longer include
>> XXXXPackage interface class which will be implemented by the
>> XXXXPackageImpl class ?
>> Thanks
>> Nalaka
>>
>>
>>
|
|
|
Powered by
FUDForum. Page generated in 0.03666 seconds
Home