A possible workaround for the LTW issue that appeared in JBoss 6 using Spring 3 (SPR-7887) is to add an empty jboss-scanning.xml file to EAR and WAR files.
In my day-to-day work, I encounter several interesting programming patterns that I don’t have a name for. Maybe you have?! So name the following pattern:
Today I tried to create a combo viewer in Eclipse with a different approach than the it seems the widgets was designed. I have an object which has to main properties an ID and a descriptive name. While this is nothing unusual following requirements seems to be:
After upgrading my server and cleaning up stuff, I thought it would be nice to work a little bit on the homepage again. Since iWeb seems to be stuck and I am working mostly on Linux now, I thought it would be interesting to give WordPress a try.
Let’s see what happens …
Reading an object from an ObjectInputStream is easy. But using OSGi it can be a little bit more difficult. Due to the class loader system of OSGi the ObjectInputStream might not know the class that was stored. Assume you have a Bundle A, B and C. B provides the storing capabilities that stores objects somewhere and C provides the data object itself. Now if A tells B to store some object from C this will not be a problem, since the object class is attached to the object instance. But reading back the object will result in a ClassNotFoundException since B has no reference to C and therefore does not know any classes of C.