Slashdot Mirror
Red Hat Sued Over Hibernate ORM Patent Claim
fmarines writes "Firestar Software has filed a patent claim against Red Hat for infringing on a patent Firestar filed in 2000 covering O/R mapping. The amount of the lawsuit was not disclosed. The complaint centers around JBoss 3, and the patent claims that JBoss was given prior notice that marketing, distribution, and support services violates Firestar's patent, and that Firestar 'has suffered and will continue to suffer substantial damages.' Firestar produces the ObjectSpark, an transactional object mapping engine which appears to not have had a new release since May 2003, according to the Firestar press release page."
Red Hat Sued Over Hibernate 3 ORM Patent Infringement Claim
Posted by Floyd Marinescu on jun 29, 2006 09:40 PM
Community Java Topics Legal Matters, Data Access, Business
Firestar Software has filed a patent claim against Red Hat for infringing on a patent Firestar filed in 2000 covering O/R mapping. The amount of the lawsuit was not disclosed. The complaint centers around JBoss 3, and the patent claims that JBoss was given prior notice that marketing, distribution, and support services violates Firestars patent, and that Firestar "has suffered and will continue to suffer substantial damages." Firestar produces the ObjectSpark, an transactional object mapping engine which appears to not have had a new release since May 2003, according to the Firestars press release page.
The patent covers (from US Patent office patent # 6,101,502):
A method for interfacing an object oriented software application with a relational database, comprising the steps of:
selecting an object model;
generating a map of at least some relationships between schema in the database and the selected object model;
employing the map to create at least one interface object associated with an object corresponding to a class associated with the object oriented software application; and
utilizing a runtime engine which invokes said at least one interface object with the object oriented application to access data from the relational database. ide interface objects that are utilized by an object oriented software application to access the relational database.
Interestingly, the same patent (follow link for full PDFs) was filed under a different company name to the European patent office back in 1998, but was withdrawn. The patent is not related to yet another patent Mapping architecture for arbitrary data models filed in 2005.
Patent experts told InfoQ that the lawsuit appears to be skillful manoeuvring on Firestar's part; they waited until after the JBoss Red Hat acquisition intentions were announced and notified JBoss about the potential infringement on May 26th, which was within the JBoss Red Hat due dilligence period. This would have required JBoss to either instantly settle with Firestar or be forced to notify Red Hat which could have cancelled the acquisition deal, which was announced as finalized on June 5th (with Red Hat aware of the risks). Firestar then notified Red Hat on June 7th that they were in violation of Firestar's patent. As a further example of manoeuvring, the word among patent experts is that the specific district Firestar selected to perform the lawsuit in (eastern district of Texas) is famous among patent circles because a patent claimant has never lost a lawsuit there.
It seems clear that the timing of the lawsuit was designed to take advantage of the Red Hat acquisition. Firestar certainly had other potential targets, including Oracle (TopLink), BEA (Kodo), and even the JCP (EJB JPA).
Note: updated June 29th, 10:40pm
--- "To pee or not to pee, that is the question." ---
Continue allowing these suits to be brought before the court. However, if the plaintiff loses on the basis of an invalid patent, he/she will receive 100 lashes with wet bamboo strips -- the plaintiff's attorneys as well.
So they're not doing that well and need cash?
What we really need here is a proverbial SPAM filter on lawsuits for things like this. It is no wonder that people and/or companies with valid claims tend to hesitate to take their claims to court, knowing that this kind of hogwash is bogging down the system.
Seems like Firestar's time could be better spent actually developing something new, instead of sitting around waiting for an excuse to sue in order to generate some cashflow.
Support a true independent artist - Leila Lopez
JBoss 3 was released in May 2002.
However, Hibernate wasn't a JBoss project until September 2003.
I'd guess that the claim relates to Hibernate 3, but they are desperate to mention JBoss as much as possible for the FUD value.
This is really low - wait until your software gets in heavy rotation and then go after people using it. My question is why did they go after RedHat/JBoss? Why not go after the big dogs; Oracle (TopLink), BEA (Kodo), and even the JCP (EJB JPA)?
Again, software patents are a bad idea.
KangarooBox - We make IT simple!
How can you implement an Object Realstional Mapper and not violate this patent?
Just took a quick read of the patent and it looks like this is a pretty wide reaching patent. Anything that maps a database to an object is covered by this one. Does this mean Ruby on Rails is under the gun? Of course, they have no money (I guess) so they wouldn't be a target. But they would still be violating a patent and that could limit their future growth potential.
KangarooBox - We make IT simple!
We need reforms which basically state that if you choose to enforce your patents selectively then you should lose them.
You either license to everyone you intend to allow use of your patent or you lose it.. you should not be allowed to hide in wait and opportunistically/arbitrarily ambush companies and developers.
This should especially apply to companies who apply for patents, then sit on them while other companies do the work, only to sue them and take all their credit and revenue.
That's not capitalist.. it's parasitic.
VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
Surely there's a wealth or prior art for this kind of thing, ORM was popular before 2000. What about Next Computer's Enterprise Objects Framework? That's been around since at least 1994 according to WikiPedia - it still lives on as part of Apple's WebObjects system.
I am NaN
Last time I looked at Jboss, it was written in Java, and as such is helping to Spread Sun's dominance.
Unles of course you meant to say Sun's application server / portal server dominance, in which case, please excuse me while I fall of my chair laughing. - Neither products are going anywhere.
Jboss is not a competitor to Sun. IBM and BEA maybe, but not Sun.
...Economics.
All these projects have been registered before or in 2000 (when the patent has been filed according to TFA):
http://sourceforge.net/projects/jgrinder
http://sourceforge.net/projects/leap
http://sourceforge.net/projects/neo
http://sourceforge.net/projects/nexusproject
As this is a patent it shouldnt matter too much, if they actually had a working implementation at that time. (IANAL and all that jazz).
They have some nice offices here, no language problems for existing staff if they move to Guildford (UK).
[**] - OK -- I know that some are trying to introduce it, but the EU seems to not be that stupid (fingers crossed)
At my company, we wrote software that basically does the same thing back in the late 80's - early 90's and have been using it for high-profile, high-cost software ever since... While I don't know if we ever applied for a patent on the idea, I would bet that there is a lot of prior art out there... I just hope that Red Hat's lawyers are good enough to find it and use it appropriately.
Logic is the beginning of reason, not the end of it.
Smalltalk at an OR/M mapping engine from about 1994. I think I'm right in saying it was subsequently acquired by Oracle, ported to Java and became know as Toplink. In any case it's a pretty clear-cut prior art so the patent won't stand if anyone wants to defend it.
Enterprise Objects certainly implements everything described by that patent and a bit more because it provides a data access controller layer (not just a data model layer). Not to mention I've had some limited experience viewing someone else's hibernate-based code. EO/WO is so much better than Hibernate can ever hope to be.