The OSGi Alliance has decided to accommodate vendor-specific manifest headers by listing them in a public registry. The aim is to avoid clashes between vendors and between vendors and OSGi’s own headers.
This is the second in a series of three blogs describing a step-by-step approach to building and deploying GWT applications in the SpringSource dm Server™. The first blog looked at the process of creating a simple WAR file from a sample GWT application. This next blog will look at turning the WAR file we created in Part 1 into a “Shared Libraries” WAR. This means that we are going to externalize the GWT dependencies of our application into an OSGi bundle so that it can be shared by any number of GWT applications. You can think of it as extending our dm Server with GWT remoting capabilities.
In his recent blog entry, Glyn provided an introduction to the OSGi “uses” directive. In this blog, I want to dig a little deeper into the causes of uses constraint violations and present some tips for diagnosing uses problems in your applications.
For most of the examples I’m going to be using raw Equinox and not dm Server. The reason for this is that uses constraints are not specific to dm Server but are relevant to all OSGi users. At the end of this blog, I’ll demonstrate some of the smart constraint failure diagnostics built into dm Server.
Dear Spring Community,
We are pleased to announce that Spring Integration 1.0.0.RC2 is now available.
Download | Reference Documentation | JavaDoc
For more information, please check out the announcement within the Spring Integration Forum, and be sure to visit the Spring Integration Home.
Spring Integration Lead
I’m pleased to announce the first release of Grails since the acquisition of G2One by SpringSource. Grails 1.0.4 includes a number of improvements as well as upgrades to key libraries that underpin Grails and can be downloaded from the Grails download page. More specifically Grails 1.0.4 ships with the latest Spring 2.5.6 release that came out a week or so ago.
Beyond the improvements there are a couple of interesting new features in this release. The first is the addition of a feature that better supports mapping of Hibernate user type definitions in GORM. You can now map custom user types onto multiple columns, including the ability to customize the underlying SQL type:
Grails is a great fit with Spring and SpringSource technologies. Grails is built on Spring. It offers another route to adopt Spring, the de facto standard component model for enterprise Java. All the power of Spring (and Java) lies beneath the surface of every Grails based application—a key reason that Grails can scale to enterprise use, as well as a validation of Spring’s power and flexibility.
- WCF integration - Configure WCF services using dependency injection. Apply AOP advice to WCF services.
- MSMQ integration - MSMQ helper classes to increase your productivity developing messaging applications. Provides integration with Spring’s transaction management features.
- Apache ActiveMQ integration - Helper classes to increase your productivity developing messaging applications with ActiveMQ/NMS
- Quartz integration - Configure Quartz jobs, schedulers, triggers using dependency injection. Convenience classes for implementing Quartz Jobs.
- AOP- New inheritance based AOP proxy generation
- NHibernate 2.0.1 support.
This will be a series of 3 blogs describing a step-by-step approach to building and deploying GWT applications in the SpringSource dm Server™. The focus of the blogs will be as follows:
- Building and deploying the GWT StockWatcher sample app as a WAR file in dm Server, using the SpringSource Tool Suite to build it from scratch.
- Deploying with a “Shared Libraries” approach: How to remove the GWT dependencies from the WAR and deploy them as an OSGi bundle in dm Server.
- Deploying with a “Shared Services” approach: We convert the single WAR file into OSGi services which can be shared by other applications and hot-swapped out.
- @AnnotationDrivenTx - support for declarative transaction management
- @AnnotationDrivenConfig - support for @Autowired, @Resource, et al.
- @ComponentScan - scan for @Component classes directly from JavaConfig
- @AspectJAutoProxy - first-class support for @Aspect beans
- @MBeanExport - first class support for exporting JMX MBeans
- Complete PetClinic sample now available with distribution demonstrating use of JavaConfig
- Improved support for externalized values with @ExternalValue and @PropertiesValueSource
- @ImportXml - bootstrap Spring XML bean definitions from JavaConfig
- Improved error handling
- ... and dozens of other resolved issues