воскресенье, 31 марта 2019 г.
x86 as platform configuration causes compilation error
Вы не сталкивались? Билд в Maven падает с ошибкой компиляции "The type
org.eclipse.swt.widgets.Composite cannot be resolved. It is indirectly
referenced from required .class files". Мне удалось решить убрав
упоминания x86 из конфига платформы arch.
среда, 9 августа 2017 г.
ClassMaker
ClassSupplier is renamed to ClassMaker and it's development are proceeding.
Concerning conception of current blog, I developed the metaModel test. It creates an instance of EMF meta-model EClass, then makes generated form of it from dynamic, creates model instance of this meta-model which is then transformed back into Ecore. Now it's possible to produce this model and use it as a meta-model for subsequent instantiations (in other words, repeat the cycle).
I found that QVT[o] transformation is not possible for dynamic metamodel EClasses, and ClassMaker enables to build it at runtime, programmatically.
Of course, it is not the sole purpose of this library. Above all, it makes possible the creation of adaptable applications achieved through programmatic run-time building of default format module components.
Hope, that someone will find this useful.
Maybe you'll want to help.
See ya later!
https://www.enterprisedomain.ru/
Concerning conception of current blog, I developed the metaModel test. It creates an instance of EMF meta-model EClass, then makes generated form of it from dynamic, creates model instance of this meta-model which is then transformed back into Ecore. Now it's possible to produce this model and use it as a meta-model for subsequent instantiations (in other words, repeat the cycle).
I found that QVT[o] transformation is not possible for dynamic metamodel EClasses, and ClassMaker enables to build it at runtime, programmatically.
Of course, it is not the sole purpose of this library. Above all, it makes possible the creation of adaptable applications achieved through programmatic run-time building of default format module components.
Hope, that someone will find this useful.
Maybe you'll want to help.
See ya later!
https://www.enterprisedomain.ru/
среда, 14 мая 2014 г.
Vision
There often exists some impicit level of semantics in software implied by application-specific usage of IT terms and domain logic. For example, the Order, represented by POJO plays the domain-specific role of Document in some kind of enterprise system. If we introduce the level of indirection between technical, like POJO and concrete domain objects, it could be the subject of programming by itself.
In actually, technical representation POJO Order becomes generatable instance of meta-model object Document, represented, for example in EMF Ecore model, with instructions on how to transform it into text.
I am currently developing ClassSupplier that allows to instantly load generated classes in client runtime.
Everyone is welcome to participate!
Later I am going to develop DSL for purpose mentioned above, that would extensively use ClassSupplier. The technologies of choice for it is Xtext and Xtend. Again, if you could help with this, please feel free to contact me.
Thank you for reading!
In actually, technical representation POJO Order becomes generatable instance of meta-model object Document, represented, for example in EMF Ecore model, with instructions on how to transform it into text.
I am currently developing ClassSupplier that allows to instantly load generated classes in client runtime.
Everyone is welcome to participate!
Later I am going to develop DSL for purpose mentioned above, that would extensively use ClassSupplier. The technologies of choice for it is Xtext and Xtend. Again, if you could help with this, please feel free to contact me.
Thank you for reading!
четверг, 8 мая 2014 г.
Welcome
Hello, my name is Kyrill. This is the first post of blog about Java, Eclipse, JEE, EMF, RCP, OSGi, Enterprise OSGi.
Подписаться на:
Сообщения (Atom)