Modules structure

[Matthieu Riou <mr...@gmail.com>]

Hi,

Currently Twister's base modules are: client, common, dist, engine and
samples (with engine and client having submodules). So at first I was
thinking of putting everything into a 'modules' directory and copy
current Agila module in there too. But I think now that the whole
thing should be named Agila, so I guess we should find a name for this
former Agila module.

I was thinking of having a structure like:

/trunk
     /modules
          /bpel
               /client
               /common
               /dist
               /engine
               /samples
          /??? (name of the module corresponding to current Agila).

Maybe something like 'Agila Workflow' or 'Agila BPM' would be ok?

Thanks,

Matt.

Re: Modules structure

[Geir Magnusson Jr <ge...@4quarters.com>]

On Apr 25, 2005, at 12:59 PM, Matthieu Riou wrote:

> Hi,
>
> Currently Twister's base modules are: client, common, dist, engine and
> samples (with engine and client having submodules). So at first I was
> thinking of putting everything into a 'modules' directory and copy
> current Agila module in there too. But I think now that the whole
> thing should be named Agila, so I guess we should find a name for this
> former Agila module.
>
> I was thinking of having a structure like:
>
> /trunk
>      /modules
>           /bpel
>                /client
>                /common
>                /dist
>                /engine
>                /samples
>           /??? (name of the module corresponding to current Agila).
>
> Maybe something like 'Agila Workflow' or 'Agila BPM' would be ok?

No spaces :)

you could put 'bpm' or 'workflow'.  I'd be happy w/ either.  I was 
thinking 'agila' but that doesn't seem to make much sense if the other 
is 'bpel'

>
> Thanks,
>
> Matt.
>
>
-- 
Geir Magnusson Jr                                  +1-203-665-6437
geir@gluecode.com