DynaBeans Rock

Filed under: Engineering, webMethods

What do you do, if you’re stuck with a proprietary class model (such as webMethods’ internal datastructure)?

I can only recommend DynaBeans. It took me a good 2 hours to write a DynaBean (and DynaClass) implementation (sorry, no opensource) which recursively wraps webMethods datastructure (IData) object models. That way, its possible to use the result of webMethods services in my favourite taglib Displaytag as well as a range of other for data mapping, such as JXPath without any intermediate class model.

Mar 6, 2006 at 21:05 | Permalink

2 Comments

  • 1. Mika  |  March 8th, 2006 at 10:16 pm

    Jep, they rock.

    Not only for your reason, but because they are so good integrated with the other commons projects as well.
    I’ve built an app which enables users to create dynamic forms. I persist the assembly of the form into the db and create it in the fill out stage using dynaclass. That enables me to seemlessly use it with commons-beanutils and commons-validator, having a straightforward struts-action class, no fancy stuff there.

    Cheers, Mika

  • 2. Stefan  |  March 8th, 2006 at 11:14 pm

    Mika, of course you’re right. And they don’t rock, if your library can not cope with them. ;-) The persistence stuff is interesting however - how did you persist you DynaBeans. Did you use a (ORM-)tool? I’d really be interested in this, as webMethods’ JDBC adapter only offers pretty plain SQL support (no object-relational-mapping at all).

    Btw: I found some interesting coments on DynaBeans by Gavin King and James Strachan in this TSS thread on service data objects (SDO) from 2003. (Did you know that Hibernate once supported Dynabeans?)

Leave a Comment

(Required, Why?)

(Required)

(Optional)

Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

Trackback this post  |  Subscribe to the comments via RSS Feed