JSON Schema to XSD
Everyone is moving from XML to JSON. I just wrote a tool that goes the other way.
Everyone is moving from XML to JSON. I just wrote a tool that goes the other way.
EclipseLink needs to change your entity classes to do lazy loading and change tracking properly. It can do that when the application starts. That sounds convenient. It has been a pain in the neck on every server I have set it up on.
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.