Regarding iBatis. By now I use the information extracted from the models for the (re)creation of the EntityState that is loaded from the database. Instead using the models directly another way would be to configure all this information at configuration time for each composite at the service (using metaInfo). But that would mean to duplicate the information that is already available in the model or at least duplicate the mechanisms of extracting this information (then the Composite classes would have to be passed to the service).
Information needed is: * names & types of properties * names & types & multiplicity of associations * names & types of value composites that are embedded in the persistent store of an entity So that makes a mapping of the composite design to the relational structure of the database tables. I don't know if it is possible for extensions not to rely on runtime but just on API/SPI. I'll look into it again. Michael Niclas Hedhman schrieb: > On Wed, Jul 9, 2008 at 4:02 PM, Georg Ragaller <[EMAIL PROTECTED]> wrote: >> Never peeked at it :), here it is, it's compilable against 1.4 (without >> logging statements also for 1.3). So maybe you might want to add some >> generics stuff, remove the log statements and add #initCause() at the >> throw statements. > > Thanks. Although I have massively modified the code (less deep > structures, no logging), I really appreciate the "kick-start". You > have been listed in <contributors> for all time to come ;-) > > I have managed to get most things back to run, but we still have "old > failures" that prevents me to see all tests run. (At least, I don't > know how to tell Maven to run all tests without stopping.) > If there is "No Application Factory found..." exceptions, it typically > means that the qi4j-core-runtime module is not on the classpath, and > you will need to add; > > <dependency> > <groupId>org.qi4j.core</groupId> > <artifactId>qi4j-core-runtime</artifactId> > <version>0.3-SNAPSHOT</version> > <scope>test</scope> > </dependency> > > There is currently 2 modules that depend on Runtime directly, plus I > have disabled the RDF generation of the app. Those two are; > > - Library Framework - Sonny's Visualizer is inspecting the runtime internals. > > - iBatis EntityStore - dealing with the model directly. > > These two use-cases should be the basis for what (and how) we should > expose from the internal model. > > > I will continue to make Qi4j runnable in an OSGi environment. (No dynamic > bits.) > > > Cheers > Niclas > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
