On 26/04/2010, at 11.34, Rickard Öberg wrote:
That being said, I *have* created a bunch of libraries in
Streamflow, that might be valuable to move into Qi4j-Libraries, such
as DCI support, REST-DCI, a library for selecting file system
locations based on OS (e.g. on Unix files are stored in ~/.<appname>/
data), and so on.
Thumbs up! - and any documentation for those librarires would be
greatly appreciated :)
I guess the Event Sourcing infrastructure would also be natural to
include...
Are there any features that you see missing in Qi4j-Core, or is the
main work to be done now in creating libraries+extensions?
I'm open for suggestions!
Nice-to-have suggestions:
Once DCI- and EventSourcing libraries are integrated :), it would be
great to port the DDD sample application using DCI-CQS-EventSourcing
so that one (read: the hard working POJO guys ;) can compare
implementations!
Even a simple HelloWorld tutorial implementing DCI-CQS-EventSourcing-
Qi4j infrastructure would be nice as a starter in the documentation
(maybe without the Restlet implementation so that you could add wicket/
other frameworks of choice on top).
It could also be interesting to "challenge" other POJO examples like
http://thinkbeforecoding.com/post/2009/11/05/Event-Sourcing-and-CQRS-Serialization
http://elegantcode.com/2009/11/11/cqrs-la-greg-young/
http://blog.xebia.com/2009/12/03/domain-driven-design-and-command-query-separation-example-application/
(or others) by making Qi4j implementations... (not a high priority,
just an idea)
I know it's already mentioned and acknowledged, but I just want to say
that I also find documentation to be a high priority. Especially
coming from "outside" / being a newbie. But it could even be helpful
and attractive for more experienced developers too, and give a more
"serious" impression of Qi4j as a whole ("content goes here..." is not
so cool). At the same time I'm thankful for the already existing
documentation! :)
A domain library?
Please correct me if this is crazy: what about starting building a
library of reusable DCI domain objects? Take ContactEmail,
ContactAddress, Describable, Notable, Taggable, Commentable, Ownable
etc etc - aren't these and many more going to look pretty much the
same in different projects? At least one could extend/copy and modify,
or just get inspired from such a library of "common code base"
building blocks. This could also demonstrate the reusable powers of
Qi4j. Even standard contexts could be included organized by "BC"'s
(whatever definition we use in the Qi4j world). WDYT?
Cheers,
Marc
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
