|
|
Spring is just the ticket
Andy Piper's Blog |
January 31, 2006 2:39 AM
|
Comments (2)
When we posted the original Spring support kit and whitepaper back in the summer we were unsure of what the response would be. Sure, Spring has a loyal customer base, but would official WebLogic support just be another tick in the box for them? Ok, we put a few extra goodies in there such as clustered Spring remoting, console support for Spring components and a comprehensively integrated sample application, but the real value of the package was the endorsement and certification by us on WebLogic Server. So the overwhelmingly positive response from both customers and the developer community took us completely by surprise! I am sure that this is not just a reflection of the undeniably high-quality code, but also the professionalism and dedication of our friends at Interface21.
Spring is definitely in the air. Our customers love it and we love it too. The simplicity of the programming model really is light years ahead of many current technologies. And, in case you thought this was just a marketing ploy by us, we have now certified Spring 1.2.6 on the newly released Weblogic Server 9.1. We have integrated the fixes required by WebLogic Server 9.0 into this release, including a well-known hibernate issue. But that's not all. Most excitingly we have just released WebLogic Real Time of which Spring 1.2.6 is an integral part.
If you have not tried Spring before then I encourage you to download the kit and jump right in.
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
-
Hi, I am trying to use springs 1.2.8 on weblogic 9.1.
I need a clarification on Spring clustering . The scenario is something like this I have a war file (exploded) which has few spring beans of which one needs to be exposed as MBean. This war has to be deployed on a weblogic cluster (admin is not part of this cluster). In this case How will weblogic jmx console for spring objects maps with spring beans on different server instances.
Can you point me to some examples for the same?
Thanks.
Posted by: shirishgoel on June 21, 2006 at 4:46 PM
-
The JMX exporter only exports local beans. So you would deploy your spring app on each server and depending on where you ran the console you would see different bean definitions in the console.
I can also see potential for conflict if each server tries to register under the same JMX ObjectName, its probably something that we need to consider resolving.
I will be blogging about configuring the console support fairly soon.
Posted by: andypiper on June 23, 2006 at 2:58 AM
|
|
