ControllerContext.setModel() is indeed how you are supposed to do it. You're setting an org.w3c.dom.Document instance? What view type are you using?
Actually, nevermind, I see the problem. You're using domify, and you're trying to adapt something that is already a Node. If you want an instant fix, change your view type to "trivial" and you should be ok. Trivial views just hand the model off to the transform process, which is what you want. I'll fix the domify view so that it handles this case, though. Btw, 2.0 still used Controller.model(). The setModel() method is a 2.1 thing. But this "bug" was in 2.0, too. Jeff Schnitzer [EMAIL PROTECTED] > -----Original Message----- > From: Barrie Selack [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 14, 2002 3:47 PM > To: [EMAIL PROTECTED] > Subject: [Mav-user] passing self-built XML documents > > In pre 2.0 there was a model() method to pass a document that the > application built. In 2.0 I can't quite figure how it get's passed. > I've tried the setModel() and setting model in the HttpRequest. the > former has the effect of taking 100% of the cpu, the latter seems to > have no effect. So how is this done now? > > Thanks, > > Barrie > > -- > ------------------------------------------------------------- > > Rockhopper Communications, Inc. [EMAIL PROTECTED] > 280 Pleasant Hill Road http://www.rockhopper.com/ > Lewisberry, PA 17339 717 938-1581 > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas - > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > > [INVALID FOOTER] _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink [INVALID FOOTER]
