Dear Forum Readers and Adrian! If you followed this thread thoughtfully perhaps you have conclusions similar to mine - as follows:
The Professional Open Source Company (henceforth referenced as JBOSS) did not provide any official and detailed descriptions or how-to's about durable descriptions and topics or making messages persistent. There are lot of sources available on the web however most of them are outdated and/or contradicting each other - especially for newbies, like us. We continously failed to persist or messages under 4.0.1 AS so as a last resort we tried to get some help from the official JBOSS forum. Although my posts did not have any allusions that this was a Jboss bug (which it actually turned out to be) I was rewarded with a uniquely hostile behaviour from Adrian: anonymous wrote : The stuff you have posted does not show anything. It is just some xml out of context. | ... | All I have seen so far in this post in lots of assertions with the usual | "IT DOES NOT WORK". So show me what it IS doing. . So this was the point where my project leader (henceforth referenced as mormota) came into the picture. He tried to shepherd to flow of this conversation into a constructive tunnel. (It's very funny how this good-cop, bad-coop scenario works and what a scientific degree could mean...) As time passed our developer team succesfully provided an unambigous evidence that there is a bug in the JMS handling of JBOSS and a bug report has been posted (http://jira.jboss.com/jira/browse/JBAS-1351?page=comments#action_12315048) , which was rejected firstly, however Adrian in his last post admitted that right now the 4.0.1 version is incapable of providing topic management corresponding to the EJB 2.1 recommendation. Actually that part of code could have never worked. We are working for a large telecommunication company. We, like most informatical projects have limited time and developer resources. Still it was our task to provide a detailed test-case so that JBOSS finally could accept that it is not our defect or laziness that causes the problem. Adrian, please help me! Help me to explain my costumer that JBOSS AS is the definite open source target platform that could be recommended because the thorough testing and open support! Help me to make them understand that JBOSS is not a bad and risky choice! I'will be here, waiting for your answer. Regards: Frank-15 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864325#3864325 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864325 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
