On 2010-09-29 16.48, Stanislav Muhametsin wrote:
Yes, the 1-1 relationship is a tradeoff I knowingly made, since it is
"light-weight" and "simple". Also, now that you mention it, I realize I
forgot to add this info to README file. :)

But for the DCI part I would say it's more lightweight to not do anything at all...

Yeah, I looked at streamflow code, and it seemed very good. However, I
have a question about RoleMap in Streamflow: you basically forbid the
same type of role to appear twice, is that right? I mean, if I have two
same-type objects, but I want them to be in different 'roles' (let's
say, artificially, that my context is two integers, and my interaction
is addition of integers), what do I do?

Integer is not a role. The roles need to be defined by the context! So no, you will never have several objects playing the same role. You can definitely create several roles in the context and have those integers play them though.

If you want integers playing roles though, most likely they are simply arguments to the interaction.

Main point now is that SQL-generation uses only "Typeable" from LWDCI
API and its implementations (+ skeletons for mapping types to
interactions) from LWDCI SPI. So now I just wanna push these frameworks
to Maven repo, or OPS4J, so that I could finally push the changes I made
to Qi4j.

You want to bring in a framework just for Typeable? What's the point of that, compared to duplicating Typeable in your project?

/Rickard

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to