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."

29 of 170 comments (clear)

  1. before it gets slashdotted... by N3wsByt3 · · Score: 4, Informative

    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." ---
  2. Time to implement public caning by Anonymous Coward · · Score: 5, Funny

    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.

  3. Blah by ms1234 · · Score: 4, Insightful

    So they're not doing that well and need cash?

    1. Re:Blah by DRM_is_Stupid · · Score: 3, Insightful

      I know it's technically correct according to business jargon, but they say they're "suffering losses" - as if it's their God given right to have an artificial monopoly.

    2. Re:Blah by ThosLives · · Score: 4, Insightful
      What's really interesting is that if I open a restaraunt, and a guy next door opens a restaraunt, and people like the food and/or service of the guy next door better, my restaraunt will "suffer losses."

      I do not think that "suffering losses" means what people think it means...

      --
      "There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
  4. Legal System Upgrade by freemywrld · · Score: 4, Insightful

    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.

  5. TFA seems confused by Brian+Blessed · · Score: 4, Interesting
    It says:
    The complaint centers around JBoss 3

    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.
  6. Buy a company - get sued! by Corrado · · Score: 5, Interesting

    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!
  7. Conspiracy theory... by jkrise · · Score: 3, Insightful

    1. JBoss gains widespread acceptance, and threatens Sun's Java model, dominance.
    2. Despite Sun introducing new enhancements, developers are switching to the JBoss architecture and portal in droves.
    3. RedHat acquires JBoss, gets sued, and loses - 'tainting' JBoss in the process.
    4. Sun wins - one big competitor tainted and gone.... MS wins - open source apps around JBoss fall away.
    Sound plausible?

    --
    If you keep throwing chairs, one day you'll break windows....
    1. Re:Conspiracy theory... by powerpointmonkey · · Score: 5, Insightful

      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.

  8. This is the definition of an obvious patent by chriseyre2000 · · Score: 4, Interesting

    How can you implement an Object Realstional Mapper and not violate this patent?

    1. Re:This is the definition of an obvious patent by mikeburke · · Score: 4, Informative

      Exactly. They'll have to go after TopLink as well, which certainly predates 2000. Hell, I was working with a commercial framework called 'Persistence' in 1997 that used a similar approach (albeit in C++).

    2. Re:This is the definition of an obvious patent by dsurber · · Score: 3, Interesting

      TopLink existed as a Smalltalk product in the early 90's, '93 or '94. I know because my company developed a Smalltalk OR mapping product that competed with TopLink.

      It takes more discipline than I have to try to understand a patent, but I'd be astonished if the there isn't a ton of prior art, starting with TopLink.

    3. Re:This is the definition of an obvious patent by TheRaven64 · · Score: 4, Informative

      NeXT had an OR mapper in WebObjects over a decade ago, so either you can implement an OR mapper without violating this patent or there is prior art (since the patent was only filed in 2000, 4 years after NeXT had a shipping product).

      --
      I am TheRaven on Soylent News
    4. Re:This is the definition of an obvious patent by mzwaterski · · Score: 4, Informative
      I'll admit I didn't read the article, I just skimmed for the patent number (these articles never correctly characterize the patent anyway). The patent number is: 6101502. According to the USPTO that patent was filed on September 25, 1998 and issued August 8, 2000. The patent also claims priority to a provisional filed December 9, 1997 and a provisional filed September 26, 1997. Presumably some claims can use that as their earliest date. Feel free to check it for yourself:

      http://patft1.uspto.gov/netacgi/nph-Parser?Sect1=P TO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2F srchnum.htm&r=1&f=G&l=50&s1=6,101,502.PN.&OS=PN/6, 101,502&RS=PN/6,101,502

      and

      http://portal.uspto.gov/external/portal/!ut/p/_s.7 _0_A/7_0_CH/.cmd/ad/.ar/sa.getBib/.c/6_0_69/.ce/7_ 0_1ET/.p/5_0_18L/.d/1?selectedTab=fileHistorytab&i sSubmitted=isSubmitted&dosnum=09161028#7_0_1ET

  9. Is Ruby on Rails Affected? by Corrado · · Score: 4, Interesting

    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!
  10. This kind of "lawsuit inc." business needs to stop by plasmacutter · · Score: 4, Insightful

    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!!
  11. Sue them back into oblivion. by lowieken · · Score: 3, Interesting

    Firestarter Software is probably not doing very well. Why else would they launch a software patent lawsuit? On top of that, they have actual products in the market. Seems to me that this makes them very vulnerable to countersuits.

    Am I right thinking it shouldn't be too difficult to sue Firestarter Software into oblivion?

  12. Prior Art? by Phil+John · · Score: 4, Interesting

    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
    1. Re:Prior Art? by MemoryDragon · · Score: 3, Informative

      Toplink also has been there fore ages (92 or 93), the patent is not worth the toilet paper it was written on, and as usual the USPTO has proven not to have any knowledge of the fields it grants patents on.

  13. Their CTO and VP Engineering have degrees in.. by mikeburke · · Score: 5, Funny

    ...Economics.

  14. Ohm, Prior art? by Sweetshark · · Score: 4, Informative

    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).

  15. Time for Red Hat to leave the USA by Alain+Williams · · Score: 4, Interesting
    Relocate to Europe where we don't have this patent lunacy[**]. These patent trolls would then be limited to trying to steal the USA turnover of Red Hat; Red Hat could perhaps take the option of abandoning the USA market. If Red Hat were to leave the USA it would send a strong message to congress how patents damage the USA economy ... they might even decide that doing right by their country is preferable to accepting the slush funds from the patent lobbyists.

    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)

    1. Re:Time for Red Hat to leave the USA by Erwos · · Score: 4, Insightful

      Be real. Do you really think Red Hat is going to up and leave the country because of a single software patent suit? This is the same Red Hat that established a legal defense fund for just this sort of thing - if anything, I would think they're going to enjoy the opportunity to crush these guys like a bug.

      As for the "EU not being that stupid", good luck with that - they've proven time and time again that the US has no monopoly on idiocy.

      -Erwos

      --
      Plausible conjecture should not be misrepresented as proof positive.
  16. Prior Art by bbroerman · · Score: 4, Interesting

    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.
  17. smalltalk by Anonymous Coward · · Score: 4, Informative

    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.

  18. Enterprise Objects (WebObjects) by Jimithing+DMB · · Score: 4, Interesting

    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.

  19. They said contact them.... by 955301 · · Score: 3, Funny

    Thank you for reading that wonderful article everyone. You may now reach Firestars public relations department at the following email address:

    "Media Contact
    Contact our public relations group to inquire about press information, to arrange interviews, to receive company information or bios of key personnel, and to request media/press kits.
    pr@firestarsoftware.com"

    Sales and Marketing and partnerships seem to be the same fool:
    Rob McGowan
    SVP, Sales and Marketing
    FireStar Software, Inc.
    Phone: (201) 784-3894, (201) 522-7788
    E-mail: McGowan@firestarsoftware.com

    Have fun, be creative!

    --
    You are checking your backups, aren't you?
  20. Patenter Don't Know Shit by Bob9113 · · Score: 3, Informative

    6. The method of claim 1 further including the step of mapping class inheritance to rows within a table.

    Clearly the person writing the patent doesn't understand object oriented programming or databases. Row 2 extends row 1? I think not (except maybe as a lab experiment proving it's possible).

    And as an aside, I have violated this patent. Twice. A friend of mine working on the same project was violating it at the same time. Then we hired a third guy who violated it again. Yes, we have a project which contains four, count 'em, four, independently developed O-R mapping tools. Three of them (one of mine and the two others) were developed not knowing the others existed. Then someone recommended TopLink, which we chose not to use. Then a friend of mine showed me WebObjects, which we chose not to use. Then we hired a guy who told us about Hibernate, which we now use. WebObjects started as a NeXT project in the mid 90's. TopLink is older than the patent (I think). Our independent implementations were done without knowing about any of the existing tools or the patent, and before (I admit with some shame) we were aware of Scott Ambler's outstanding research on the subject (which dates back to 1998).

    Summary judgement to the defendant, obvious and not novel.