Problem When trying to use the Google Docs API inside an OSGi bundle, the following exception is thrown, for instance when trying to upload a document: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type application/atom+xml at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:877) at javax.activation.DataHandler.
Problem When attempting to serialize a bean, which uses property change support, XStream throws the following exepection. message : Cannot create java.beans.PropertyChangeSupport by JDK serialization : null cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException Solution The only solution I found was to ignore the field pointing to the PropertyChangeSupport class
Problem When trying to package or install a project using the maven-bundle-plugin, an error message as the following is given: [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Cannot find lifecycle mapping for packaging: 'bundle'. Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingbundle.
Problem When creating eclipse meta-data with the maven-eclipse-plugin for plug-in projects, other related projects, which are part of the same eclipse workspace are not added to the project‘s classpath. Therewith, the project, although it compiles without problems in maven, shows syntax errors such as „[class] cannot be resolved“ and
Version ranges have slightly different meaning in OSGi and Maven. in OSGi: 1.0.0 is an earlier version than 1.0.0-SNAPSHOT, therewith 1.0.0-SNAPSHOT is in [1.0,2.0) in Maven: 1.0.0 is a later version than 1.0.0-SNAPSHOT, therewith 1.0.0-SNAPSHOT
Design patterns are a well-established concept for the design of classes and their relationships in object oriented programming. Build tools like Maven can encourage us to think of similar patterns for modules or libraries. In Maven, every module or library (a project in Maven terms) is described by a project
Pax Exam is a very useful framework to write automatic tests for OSGi bundles in multiple OSGi containers. Resources Pax Exam Core Configuration Options Pax Exam Reference Documentation Wiki Page about using Pax-Exam (from Fuse ESB) DZone article Test Driven Development in OSGi
Problem Java code completion does not work in MyEclipse after installation on Mac OS X. The first time, Java code completion is used, the following message is displayed: Solution Change the settings in the Content Assist as shown below: Resources Java Code Completion does not work in MyEclipse 7.1,
Just a number of pointers on the debugging, testing and deployment of OSGi applications ... Debugging Debugging is often an essential activity if the application just does not want to work as it is supposed to. Eclipse offers strong support for debugging of OSGi applications through the Plug-In Development Environment (PDE)
To get eclipse PDE working hand in hand with Maven is a rather tricky task. I have already written about some necessary tweaks to get it working. Another way is to use the Apache Felix Maven bundle plugin. This Maven plugin is able to generate the necessary files for the
Problem Maven uploads work fine using the normal goal deploy:deploy, but when using deploy:deploy-file it seems like the authentication information in the settings.xml is ignored. So, it is not possible to upload to a Nexus repository, which requires password authentication for upload of artifacts. mvn deploy:deploy-file
The Problem Some libraries like XStream or Beans serialization require direct access to the classloader of the bundles, which use them. These libraries need access the classes, in order to deserialze them. Otherwise expections like the one below occur: SCHWERWIEGEND: Application class de.mxro.textedit.gdocseditor.gui.GoogleDocsEditorGUIApp failed to
