There are many "issues" with using "Java Enterprise" with web applications I will list my favorites (But if you google there are so many, many, many more):
- State replication is something I haven't seen done correctly in the container implementations I have seen. So cross out EJB, stateful sessions beans and messaging.
- "Java Enterprise" is marketing hype replace Java Enterprise with mainframe and bingo, the empire has no clothes.
- The enourmous learning curve is not justified by productivity or performance. (Maybe justify better pay)
- It isn't fun.
Good Luck,
Lateef
P.S. note about distributed:
Framework support for "distributed" is really marketing hype. Make sure you write code that doesn't depend on being run on a single machine. Think processes not threads.
On 4/10/06, pierreth <[EMAIL PROTECTED]> wrote:
Well,
I want to create a website where users can subscribe to read messages
from mailing lists. The goal is to host about as many mailing lists as
possible and enable users to read them and create new ones. I think I
would need my application to be spread across many servers so this why
I want it to be distributed. I want to be able to shut down the server
and still keep my application running. The application should be able
to be transferred to another server without being stop.
I am a Java certified programmer. But I don't have experienced
developing Web applications. As I see things, tools like Turbo Gears
are good for small things but if you have a volume that is more
important then, you need a Java Enterprise server. Am I right? I don't
know so this why I am investigating the question.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
