Hi, I'm presented with a middle-tier architectural reworking project and am wondering if anyone out there have been through this and can give some pointers.
My group is mainly concerned with a browser-based client where pagesare rendered on Dynamo web server. Currently this server connects to a centralized Weblogic server for ejb calls. These clustered ejb servers we call the Big Blob because 3-4 departments use it and serves 50 difference SSBs for disparate services. Our delimma is we are too tightly coupled to the app tier for our liking: 1) if the ejb/parameter objects change, we need to bounce both tiers 2) what's worse, on prod, if another department decides to bring down the ejb tier, our browser clients are rendered useless, returning 404 pages on all calls What I would like to do is slip in a persistent queue layer between the web and app server. I can transform ejb-calls into XML messages (pseudo-SOAP) and store it in a JMS persistent topic. Hence browser requests are asynchronous and completely independent of the app tier. Here are some of my issues: 1) Can I use MDB's? I want the persistent queue layer to be independent from EJB container; are there EJB vendors that allow a separate JMS server for their MDBs? 2) Is XML-RPC/SOAP persistent message the way to go? Are there alternatives? 3) If I go the XML-persistence route, are there any good transformation API's available? I've checked out Castor and JOX for parameter-passed JavaBean-to-XML transformation, but what about actual method invocation using XML representation (pseudo-XML-RPC)? Has anyone out there implement a similar layer and care to share your thoughts? Thanks! Gene __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
