| [newbie] ECore Classes [message #379074] |
Fri, 18 July 2003 18:49  |
Eclipse User |
|
|
|
Originally posted by: gsrt.terra.com.br
Hi folks,
All the classes generated by EMF are Framework provided subclasses.
Object means EObject in EMF and so on.
As the project evolve, I believe that more and more APIs available will
be generated by engine (EJB, Struts and Hibernate, for example).
I hope some day to make just definition that my class will be persisted
by Hibernate, and let the whole code to be generated by EMF
automatically.
Is it a dream? I can't see as it could be possible without a
reengineering of the Hibernate.
Force all the classes to be a parent in the Framework does not limit the
code generation in a near future ?
[]s
Glauco
|
|
|
| Re: [newbie] ECore Classes [message #379102 is a reply to message #379074] |
Wed, 23 July 2003 17:35  |
| Eclipse User |
|
|
|
Glauco,
I'm not too familiar with Hibernate. From taking a quick look on the Web,
it appears to be some kind of relational store for Java classes.,
It sounds like you're asking if it's possible for EMF to generate classes
that are independent of the EMF framework, i.e., that don't extend from
EObject. Unfortunately, that isn't possible.
The following (posted by Dave Steinberg) in the thread "Generating without
EMF Code" which began a few days ago sums this up well:
>Making all model classes extend EObject is central to the design
>of EMF. EObject provides necessary support for EMF mechanisms including
>containment, resources, notification, and the reflective API. Without
>these, the framework just wouldn't hold together.
>You could reuse EMF's codegen component (the org.eclipse.emf.codegen
>plug-in) to build your own generator for simple classes that aren't meant
to
>run on the framework.
--Gary
Glauco Reis wrote:
> Hi folks,
>
> All the classes generated by EMF are Framework provided subclasses.
> Object means EObject in EMF and so on.
> As the project evolve, I believe that more and more APIs available will
> be generated by engine (EJB, Struts and Hibernate, for example).
> I hope some day to make just definition that my class will be persisted
> by Hibernate, and let the whole code to be generated by EMF
> automatically.
> Is it a dream? I can't see as it could be possible without a
> reengineering of the Hibernate.
> Force all the classes to be a parent in the Framework does not limit the
> code generation in a near future ?
>
> []s
> Glauco
|
|
|
Powered by
FUDForum. Page generated in 0.03586 seconds
Home