Slashdot Mirror

← Back to Domains

Domain: objectstyle.org

Stories and comments across the archive that link to objectstyle.org.

Comments · 9

  1. Re:Look at the sad story of WebObjects by sqar · · Score: 1 · on Apple's Macworld Looking To Corporate Users

    I am doing WO development for my living and until recently I used some XP machine for this. Never had any troubles so far (besides the restriction to W0 5.2.4 instead of 5.3 when using Apple tools) but our company went for WOLips (Eclipse plug in, see http://wiki.objectstyle.org/confluence/display/WOL /WOLips ) which gives you all the stuff you need to develop. Yes, it can sometimes be tricky to do WO on XP but somehow you get it to work (I didn't fiddle out all the nitty gritty detail of installing it - our admins did - so I had a smooth journey) regards

  2. Try Cayenne by doktorjayd · · Score: 0 · on Red Hat Sued Over Hibernate ORM Patent Claim

    yep,

    EO/WO was the stuff back in the late 90's. .. shame apple dragged their feet on it.

    fortunately, these folks have taken the design principles and brought it all hurtling into modern java:

    http://objectstyle.org/cayenne

    its recently become an apache incubator project:

    http://incubator.apache.org/projects/cayenne

    forget hibernate, i had the serious displeasure recently of listening to the self aggrandiosment of gavin king, and the way he prattles on you'd be forgiven for thinking the sun really did shine out his ass, and that the only way to do it was his way.

    try cayenne, especially if you have a little WebObjects background. ( and even more so if you think hibernate is it and a bit )

    anyway, back OT, +1 on the lashings with wet bamboo canes above please.

  3. Re:The Original Author of Tapestry? WebObjects. by alphaFlight · · Score: 1 · on Tapestry Making Web Development a Breeze?

    I'm curious to see if part two of the DeveloperWorks article will mention cayenne as a good ORM framework. An older post with examples of using tapestry and cayenne can be found here.

  4. Re:The Original Author of Tapestry? WebObjects. by alphaFlight · · Score: 1 · on Tapestry Making Web Development a Breeze?

    I'm curious to see if part two of the DeveloperWorks article will mention cayenne as a good ORM framework. An older post with examples of using tapestry and cayenne can be found here.

  5. Instead Try: Tomcat + Cayenne + Tapestry by CtAhBeAbNoAy · · Score: 2, Interesting · on JBoss - A Developer's Notebook

    http://www.objectstyle.org/cayenne/index.html
    http://jakarta.apache.org/tomcat/index.html
    http://jakarta.apache.org/tapestry/

    http://www.eclipse.org/
    http://ant.apache.org/

    Choose any database you want. Tapestry is simply AMAZING!!! Everything is a component. It is like have all of the coolest legos and building sites in not time. Also, if you don't like the block, it is EASY to make custom components. Howard Lewis Ship is a genius.

    Okay, the Java world needs to really wake up and start buying into Cayenne. Get off the Hibernate kick!!! All I see is ways to improve Hibernate and Cayenne already has it all in place. Plus Cayenne and Tapestry were made for each other.

    J2EE was a nice try, but way, WAY too complicated. Both Cayenne and Tapestry are straight-forward and easy to use, IMHO!!!

  6. Cayenne - You'll like it better. by CtAhBeAbNoAy · · Score: 2, Informative · on Hibernate - A J2EE Developers Guide

    If you think Hibernate is good, then try Cayenne and really be blown away.
    I am not affiliated with Cayenne at all - just a VERY satisfied customer.
    http://objectstyle.org/cayenne/

  7. Yet Another Object Relational Mapping Framework by stefaanh · · Score: 1 · on Hibernate in Action
    I don not want to start a "this is better than that" discussion, I simply want to add something of my experience to this topic, because good ORM can be a time or life saver for any project.

    I have some experience with EOF (Enterprise Object[1] Framework) and was looking at Hibernate. Now i'm using Cayenne[2]. There is not so much difference between the two latter, taking simplicity and elegance into account. But here is why we choose Cayenne for our situation:
    - a friendly open userbase
    - a project which got its priorities right
    - it resembles, and, can import the model files of EOF
    - it reverse engineers existing databases with ease.
    - I get a *great* cross platform modeling/mapping GUI tool which saves me lots of work.
    - I could write my own database adaptor by subclassing the work already done.
    - inheritance is used to separate business logic from persistence and mapping logic. You never need to touch the latter.

    etcetera...

    From the Cayenne website:
    Bill Dudney posted a Cayenne vs. Hibernate[3] entry in his blog. This ended up as a pretty long thread discussing the merits of GUI tools for ORM among other things.
    It is interesting because Bill fooled around quiet a bit with the frameworks, and you get a quick idea of what your code will look like in both. Also it gave me the right strategic insight.

    The main maintainers of Cayenne got there first with
    a good introduction to their creation[4].
    Another quote: Unfortunately popular feature-for-feature comparisons[5] of such frameworks provide as much information about the substance as nutrition labels about the food taste. So this is a bit like choosing a dish in a restaurant - its all about the flavor.
    1. http://developer.apple.com/documentation/WebObje cts/Enterprise_Objects/Introduction/chapter_2_sect ion_1.html
    2. http://objectstyle.org/cayenne
    3. http://www.theserverside.com/blogs/showblog.tss? id=CayenneAndHibernate
    4. http://www.theserverside.com/articles/article.ts s?l=Cayenne
    5. http://c2.com/cgi/wiki?ObjectRelationalToolCompa rison


    Evolution will tell. But this is my bell.
  8. Cayenne Solution [Re:Java Data Objects are nice..] by Andrus · · Score: 1 · on Java Data Objects
    While I am trying to stay away from commenting on EJB (the whole state of affairs in this area is just making me sad), among the real O/R frameworks (be it JDO-compatible or not), there are 3 major solutions:
    1. Use bytcode "enhancements" (JDO)
    2. Use reflection
    3. Use common superclass

    Personally I am in favor of (3). This allows to solve a problem mentioned by the parent - tracking object changes - with as little overhead as possible, and still keep your system clean OO. This is how Cayenne O/R Framework works:

    http://objectstyle.org/cayenne/

    This allows to track changes to objects as they occur, instead of doing a blanket analysis of all objects on commit. And in general this allows a better control of objects persistence behavior by the framework. There is another (commercial) product that uses the same approach: NeXT/Apple's WebObjects. The downside of (3) is that you must have a common superclass for all your business objects, but I still have to see the case when this is undesirable.

    Andrus

    Disclaimer: I am personally involved with Cayenne and therefore not impartial :-)

  9. Re:WebObjects is Web Applications done right. by hysterion · · Score: 2 · on Thursday Release Party
    The great part is that this technology is so transparent, so clean, that I imagine it should be fairly simple to re-implement as OSS. Perhaps this is what the Tapestry project is trying to do...
    Two others are Cayenne and GNUstepWeb.

    (The latter even appears to have been backported to OS X.)

    Anyone experienced with them?