Rahul Thakur wrote:
Overall I think the core of Continuum should be re-though to be more
pluggable. In particular a workflow engine should be in the middle of
the execution to orchestrate any steps involved with building a
project. This is one of the places where people should be able to plug
Rahul Thakur wrote:
1-2)I would like to bring Guice to the mix. I think it is worth
investigating for Continuum 2.0 - WDYT?
I need a reason to drop the current set of technologies, why is the
new set better etc.
My motivations behind this were:
# leverage Java 5 language and other lib
Sorry, that was sort of my point - many implementation-specific tricks
make it into OR/M configuration, and sometimes code. Or rather
assumptions about subtle behaviour or one ORM are factored into the
design, but another ORM may not perform in the same way under the same
conditions because
Hibernate can be used in a completely JPA-compliant mode, so it would be
(theoretically) just as swappable as any other JPA implementation as long as
you don't use any hibernate-specific extensions.
On Feb 5, 2008 10:12 PM, Christian Edward Gruber <[EMAIL PROTECTED]>
wrote:
> Toplink is mentioned
This looks very exciting, and agree with most of the thread that
follows. I'm just going to reply in summary - most of my thoughts are
actually non-technical :)
Regarding databases: I don't think xml files are the solution (except
for the configuration where it makes a lot more sense :) - t
Jesse McConnell wrote:
1-2)I would like to bring Guice to the mix. I think it is worth
investigating for Continuum 2.0 - WDYT?
I don't think. I don't see the interest to look at it for Continuum. We
already use Plexus that works fine, and if we decide to move to something
else, it
On Jan 30, 2008 12:34 PM, Jesse McConnell <[EMAIL PROTECTED]> wrote:
> How important is the database really to things in continuum?
>
> To me it has always seemed somewhat of an annoyance to have to manage and
> maintain when so much of things could just be some xml files on disk.
Like the General
t; > lists. Having said that, JPA providers would ultimately be swap'able
>> > under the hood.
>> >
>> > Also, I think we should stick with JPA annotations on model entities
>> > instead of using Modello. I hope writing the data access code from
>> > s
k with JPA annotations on model entities
> > instead of using Modello. I hope writing the data access code from
> > scratch implies the current ContinuumStore will be refactored into
> > something which is less verbose than what we have currently, and so
> > would the Continuum i
Hi
I started a document [1] with my ideas about Continuum 2.
As you can see in this doc, I want to add lot of things in the next version.
Feel free to comment on it.
[1]
http://docs.codehaus.org/display/CONTINUUM/Continuum+2.0+Design+Discussion
Emmanuel
10 matches
Mail list logo
