On Tue, Oct 21, 2008 at 11:19 AM, Rickard Öberg <[EMAIL PROTECTED]> wrote:
> Hm.. I don't think Citerus would be happy about that. I wouldn't be if
> someone wrote code and put "se.jayway" as package name. Please use
> org.qi4j instead!
Ok, I'll contact them and see if they are interested to receive this
back to their project, and if so whether they want it as se.citerus or
org.qi4j. Meanwhile, we change it to org.qi4j.
>> 1. Singletons
>> public interface LocationRepository
>> {
>> :
>> Location unknownLocation();
>> }
>
> Yeah, that would make sense. In SiteVision I had a couple of "well known
> entities" which were generated at startup with well-known identities,
> and which could be accessed using static methods. This might be an
> example of that.
Ok. In these cases, the Location and CarrierMovement are both Entity,
so works well.
>> 2. Specification
>> I also don't really understand how the RoutingSpecification fits into
>> the bigger picture, such as "Why is the RoutingSpecification created
>> from a Cargo instance?"
>
> This just came up on the DDD Sweden mailing list today. It's messed up.
> I would replace most of that with the Query API, if possible.
Well, as I mentioned, right now it is not used for anything AFAICT.
Cheers
Niclas
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
