![]() |
|||
| November 15, 2005 | |||
Re: SolarMetric, BEA Workshop, reading our blogs, my final dispatch We've been quite busy here at dev2dev this past week. BEA recently acquired SolarMetric. As Gary McBride says, "SolarMetric has developed a truly killer persistence implementation that is fast, scalable, and reliable, and fits well with BEA's core competencies." They're the folks who have a JDO and EJB 3.0 implementation. Read Eric Stahl's take on the acquisition too. In the previous newsletter, I invited you to try NitroX. Well, the products have now been integrated into a new product family, the BEA Workshop product family. See the associated Version Information page for details. Note the subtly different prefixing there...Check out some of the links and blogs on the updated BEA Workshop Product Center for more details - I see you can download the BEA Workshop JSP editor for free too ;-) Also check out the screencast demonstrations. They give a pretty good idea of what's in the products. You'll notice I made many references to blogs. We have numerous blogs on devdev. One that I can recommend is the dev2dev Editor's blog, (the orange RSS tab is the address), and not because I write it. It provides a weekly snapshot of what's happening in and around dev2dev, typically providing more detailed information than supplied in this newletter, and it's more timely too. Also worth a look is the CodeShare News blog, written by Daniel Brookshier. Be sure to check out the other blogs and RSS feeds too. Regards,
Jon Mountjoy ![]()
Sharing Data Among Federated Portals: Using BEA WebLogic Portal, Tangosol Coherence and WSRP
Peak Performance Tuning of CMP 2.0 Entity Beans in WebLogic Server 8.1 and 9.0
Successfully Planning for SOA
Demystifying SAML Featured dev2dev Live! content includes:
Presentation: BEA Workshop Studio 3.0 Demonstrations
Presentation: This JavaOne 2005 discussion addresses the different approaches to the portal market and focuses on large customer endeavors and best practices ![]() Gary McBride asks, "Let's say you need to host a Java application that performs 1,000 transactions per second. How many CPUs do you need to allocate for a WebLogic Server cluster?" He answers by saying that it "depends," but for good measure Gary also includes a table stating the number of CPUs needed to attain 1000 JOPS across different application servers. If you think his figures are contentious, feel free to leave a comment on his blog! Also take a look at Eric Stahl's post, Background on the SolarMetric Acquisition. After providing some history, Eric turns to EJB 3.0 and JDO - and spells out a little of why SolarMetric was acquired by BEA. Learn about the new BEA Workshop suite by reading Pieter Humphrey's blog entry, BEA Workshop Studio 3.0 FAQ. Additional material can be found in Bill Roth's blog, BEA Workshop 3.0 *Now Available* : The Blended Development Environment. Finally, Eugene Kuleshov recently encountered a problem when using a Foreign JMS provider with WebLogic Server when integrating with WebSphereMQ. Frustrated with the WebSphereMQ error codes, he wrote a nifty helper function to extract the symbolic name of the exception by doing introspection on the MQException class! ![]()
|
|||