Model-Glue and Reactor Divorce!
Apparently, rumor has it that MG was having an affair with another ORM framework named Transfer, and Reactor, well, reacted and promptly filed for divorce. Joe Rinehart made it final on December 22 by pulling Reactor's configuration from the sample application template as well as removing the Reactor-specific portions from MG's core configuration file.
Said Joe, "Everyone thought it was a marriage made in heaven, but I guess it wasn't meant to be."
Model-Glue wouldn't speak with us concerning the breakup, but when contacted, Reactor shared the following:
"Look, I know I reacted pretty strongly back then when I first found out about MG and his new, ehem, ORM, but I guess I'm OK now. We're still gonna work together tho'. We're just not married anymore. Looking back, I guess we were too tightly coupled."
Pressed for details about how they were going to continue their working relationship in the future, Reactor confided:
"Well, let's just say that for now, you can add the ORM configuration information in the ColdSpring.xml file of your MG app yourself, like this ..."
(Reactor, Transfer, Michelle, Roxy, etc) -->
<bean id="ormAdapter" class="ModelGlue.unity.orm.ReactorAdapter">
<constructor-arg name="framework"><ref bean="ModelGlue" /></constructor-arg>
</bean>
<!-- Defines the ORM service itself -->
<bean id="ormService" class="reactor.reactorFactory">
<constructor-arg name="configuration"><ref bean="reactorConfiguration" /></constructor-arg>
</bean>
Indeed, Reactor's tip was very timely. We noticed we got a nasty error without these additional bean definitions in place using the latest build of Unity downloaded from SVN.
"And you might need an example of MY configuration, which still goes in ColdSpring.xml like before (sigh) ...", Reactor continued.
<bean id="reactorConfiguration" class="reactor.config.config">
<constructor-arg name="pathToConfigXml"><value>/modelglueapplicationtemplate/config/Reactor.xml</value></constructor-arg>
<property name="dsn"><value>thedsn</value></property>
<property name="type"><value>mysql</value></property>
<property name="mapping"><value>/modelglueapplicationtemplate/model/data</value></property>
<!-- development or production -->
<property name="mode"><value>development</value></property>
</bean>
We asked Reactor what she thought of the name 'Unity' going forward, now that MG was also going with Transfer.
"Look, if you're asking if the 3 of us are going to move in together on the same server, you can just FORGET IT!"
She paused a moment, staring across the room ...
"I guess somebody's gonna tell me I'm over-reacting again, huh?"
Nah ... ;-)
I did full manyToOne, oneToMany, and manyToMany scaffolding implementation in MG:U last night, so expect a commit to Model-Glue soon that allows it to play with both transparently :).
-Joe
Wow oneToMan manyToOne manyToMany scaffolds will BE THE COOLEST!!