eclipselink-maven-plugin 2.6.2 released
I’m happy to announce version 2.6.2 of eclipselink-maven-plugin!
I’m happy to announce version 2.6.2 of eclipselink-maven-plugin!
Simple script to copy all branches and code from one repo to another.
In the land of traditional ACID DBs, I often encounter code that is trying to collaborate with some external system using a queue or notification system. The problem is that it ends up sending the notification to the external system before the data has been committed to the central database. Then when the external system tries to query for data based on the notification, the data is not there yet (a different or outside a transaction).
This page was created to try to distill the information from more than 5,000 forum posts.
For some time I have meant to fully document all the different APIs I’m involved in. It gives a more professional feel, it helps integrators and front-end developers and it actually makes it easier to spot inconsistencies in naming or configuration.
Our clients were a bit unhappy with the inability to log out from basic auth protected services. As I did not want to have everyone update their passwords (and having them kept in a file is actually flexible enough for such a small service), I wrote a small helper class to match username/password in the existing .htpasswd file.
To speed things up I had applied the excellent @Cacheable annotation to a service method in our application (don’t miss the excellent performance analysis here, btw). However, I had not paid too much attention to the parameters going into the cache key. I would have expected something like concatenated toString() or something similar, however the default is to use the hashCode() of each parameter and create another (32-bit) hash code. Obviously this can easily generate collisions, as we shall soon see.
I thought that since it feels pretty late to enter the blogosphere at my age, I will write up a small explanation, if there is anyone interested.
Notes from my internship at an RFID company in Singapore, spring 2005.
After a few days of writing code directly for drawing surfaces and cylinders, it turned out to be very hard work to get a good-looking robot. That gave me the idea of loading a model made in a 3D program instead. This gives much more flexibility when the models need updating, and it also makes it possible to set some material properties and light settings there, so that this does not have to be done by hand. The next step is to draw the robot's part models in the right position, and then animate the robot. The robot can be controlled either manually or through a control file, specified in XML.