Ok :-) Let's see, if she fit's to my requirements.
I'm living in an enterprise environment. Taken this
1) Developers in that environment have special needs:
a) ease of use. This is the most important thing! They do not
want to care about technical things - they want to concentrate on
business logic. No factories, no xml, even no connection handling, no
SQL if possible. Just POJOs - all as easy as possible.
b) stabibility. The software must life for at least 10 years -
interfaces should not change during that time.
c) flexibility. I have to roll back transactions because of
business logic for example. And maybe I'll need nested transactions too.
And I need long transactions and bulk operations.
2) enterprise applications are complex: Normal object models consists of
more than 100 persistent classes. Components consist of 1 to 20
persistent classes (covered by a component facade).
Taken all this, I don't see automatic transaction management at the
moment. It is easy and smart - agreed. But I'm loosing to much
flexibility.
What do you think?
Andreas
> -----Original Message-----
> From: Hamilton Verissimo de Oliveira (Engenharia - SPO)
> [mailto:[EMAIL PROTECTED]
> Sent: Montag, 16. Februar 2004 20:36
> To: Avalon Developers List
> Subject: Re: FW: [Proposal] Augmenting Fortress extensions support
>
> Sure - specially if she's doesn't fit in my requirements :-)
>
> -----Mensagem original-----
> De: andreas oberhack [mailto:[EMAIL PROTECTED]
> Enviada em: segunda-feira, 16 de fevereiro de 2004 16:29
>
> Hm - do you choose a underware if a naked woman would like to enter
your
> bedroom??
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
