There is several reasons for this: - the GWT console shouldn't be tight to a particular jbpm version or bpm runtime in general (at least we try to avoid it) - GWT only supports a limited set of JDK classes. Pulling in the jbpm model would cause all kind of dependency problems, which most result in GWT compiler errors due to unkown / unsupported classes - the dto's are fit to support particular console usecases. not less and not more - last but not least, the jbpm3 model is directly exposed which IMO is wrong from the beginning View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186085#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...