> Your architecture potentially has no technical disadvantages compared with EJB, > it's just you'll end up re-inventing the wheel an awful lot. You are > essentially writing EJBs, just not running them in a container. That means > anything the container does for EJBs you have to do. This effectively means > you have to write your own persistence manager, transaction manager, resource > manager, security manager, connection pools, mail interface, message queing, > logging, management architecture, everything. Why not use services which > already exist, instead of re-writing them all, potentially for every bean? > Just sticking your head in the sand and saying, "I don't need it," isn't really > good enough, because one day you might, and then you can either move to EJB or > write it yourself. > > Get the picture? ;-) Got. And abstractly I got it already. I was serious when I said I couldn't start jBoss. Could you *please* tell me if a web server is indeed launched along with the servlet engine, or if something has yet to be configured for a web service to be ready for requests ? And, more precisely than my precedent message set it: is it possible to avoid using cookies with jboss ? thanks, candide -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] List Help?: [EMAIL PROTECTED]
