It seems that the major problem that EJB currently have (and would hopefully be solved by the EJB-JMS integration) is EJB primarily focuses on POP-style applications. That is when the server starts nothing really happens. It takes a client to submit a request to get things going. Then the AS cranks up it's service, activates the objects, sends requests here and there. Ie. the information is _pulled_ out from the ejb-application. EJB simply fulfills a clients requests. This is pretty okay because the webb is pretty much a POP-oriented world as well. But mysterious things are happening to the web. Strangely encoded CORBA/DCOM method-calls, straying and confused EDI-messages and blistering, hyper-modern b2b xml-documents is beginning to find it's way around the web, mainly using the http post-method. The web is starting to become more and more MOM-oriented. It's okay, http 1.1 is a better protocol than one would think. Also, the EJB-design has to meet these new requirements of web-applications. The b2c electronic-commerce applications are mainly POP-oriented, there's not really a system receiving messages. B2B has another requirements. For EJB to succeed it really needs great support for JMS. Jon Tirs�n Chief Architect Itec Open Business Integrator AB PGP key lookup: http://certserver.pgp.com:11371/pks/lookup?op=get&search=0xE9032B9A
BEGIN:VCARD VERSION:2.1 N:Tirs�n;Jon;;; FN:Jon Tirs�n ORG:Itec; TITLE:Chief Architect TEL;WORK;VOICE:+46 (8) 343431 TEL;CELL;VOICE:+46 (709) 306109 TEL;WORK;FAX:+46 (8) 343438 ADR;WORK:;;Box 23049;Stockholm;;104 35;Sweden LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Box 23049=0D=0AStockholm 104 35=0D=0ASweden ADR;POSTAL:;;Ynglingagatan 17;Stockholm;;104 35;Sweden LABEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Ynglingagatan 17=0D=0AStockholm, 104 35=0D=0ASweden URL: URL:http://www.itec.se EMAIL;PREF;INTERNET:[EMAIL PROTECTED] EMAIL;INTERNET:[EMAIL PROTECTED] REV:19990417T134712Z END:VCARD
