This is again a small JMS configuration stuff we have to do in JBoss 5. There is considerable difference in doing it in JBoss 5 compared to JBoss 4 and don’t expect our old configuration to work well with JBoss 5 without any change. In JBoss 5 they are using JBoss Messaging in place of JBoss MQ. You can read a detailed post on migrating from JBoss 4 to JBoss 5 here.
Upgrading JBoss 4 to JBoss 5 with Java 5 to Java 6
The information presented here comes from an effort to upgrade a Java enterprise application to the most current versions of all of its parts; primarily to get onto Java 6. Its starting system specifications were the following:
bnd is the Swiss army knife of OSGi, it is used for creating and working with OSGi bundles. Its primary goal is take the pain out of developing bundles. With OSGi you are forced to provide additional metadata in the JAR's manifest to verify the consistency of your "class path". This metadata must be closely aligned with the class files in the bundle and the policies that a company has about versioning. Maintaining this metdata is an error prone chore because many aspects are redundant.
FeatureMapper is a tool approach to combine Software Product Line Engineering (SPLE) and Model-Driven Software Development.
It supports mapping features from feature models to solution artefacts expressed in EMF/Ecore-based languages (such as UML2 or your home-made domain-specific language), provides various visualisations of these mappings, allows for mapping-based transformation of solution models, and provides an extensible interface to utilise different transformation techniques.
In addition to its own feature metamodel, it also supports feature models and variant models of pure::variants, an industrial-strength tool for variant management.
FeatureMapper is under development at the Software Technology Group of Technische Universität Dresden, partly in the context of the BMBF-funded feasiPLe research project.
JaMoPP is a set of Eclipse plug-ins that can be used to parse Java source code into EMF-based models and vice versa. JaMoPP consists of:
a complete Java5 Ecore Metamodel,
a complete Java5 EMFText Syntax, and
an implementation of Java5's static semantics analysis.
Through JaMoPP, every Java program can be processed as any other EMF model. JaMoPP therefore bridges the gap between modelling and Java programming. It enables the application of arbitrary EMF-based tools on full Java programs. Since JaMoPP is developed through metamodelling and code generation, extending Java and embedding Java into other modelling languages, using standard metamodeling techniques and tools, is now possible. To ensure the quality of JaMoPP, it has been successfully tested on a large code base.
The SKOS API is a Java interface and implementation for the W3C Simple Knowledge Organisation System SKOS. For more information about SKOS see here. An implementation of the SKOS API is provided which uses the OWL 2 API, at present you will need to obtain the OWL API seperately from the OWL 2 website. [UPDATE 12-09-2011] The current release of the SKOS API has been deprecated, a new version_3 developer branch is available in the SVN repository that works with the latest OWL API v3.
For more information please contact the user group at skos-dev@googlegroups.com
The SKOS API is open source and is available under the LGPL License
The SKOS API includes the following components:
An API for the major SKOS constructs and an efficient in-memory reference implementation based on the OWL 2 API
Abstract data model for working for SKOS that avoids commitment to any of the concrete syntaxes, such as RDF
RDF/XML parser and writer
OWL/XML parser and writer
OWL Functional Syntax parser and writer
Turtle parser and writer
Support for extending the underlying SKOS data model via the OWL 2 API
Support for integration with reasoners such as Pellet and FaCT++
Range of convenience methods for working with SKOS
We have used Spring Roo in a web project and show how we generated an early prototype and transistioned to early development and then to production code.
E. Sekerinski, and R. Zurob. &\#171;UML&\#187; '01: Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools, page 376--390. London, UK, Springer-Verlag, (2001)