I've never tried using an EJB directly as a model; it doesn't seem like a very good pattern. Conventional wisdom in EJB programming seems to be to hide entity beans behind a session bean façade, returning value objects. If all you have to worry about is a single bean, I find it convenient to use the Controller object itself as the model.
Still, I'm surprised that it didn't work. Domify should be able to wrap anything. What was the error? Jeff > -----Original Message----- > From: Gerald de Jong [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 12, 2002 1:11 AM > To: [EMAIL PROTECTED] > Subject: [Mav-user] EJB/Maverick > > i'm having some big fun working with Maverick and JBoss to create a web- > app. > > but it made me wonder: when the controller deals with EJBs it will have > to > work with their remote interfaces. i was not successful when i tried to > incorporate the EJB interface itself in a Maverick model, i think due to > the > remote exception that can be thrown. i had to create a special model bean > for the domifier. > > am i missing something? > > -- > Beautiful Code BV > Rotterdam, The Netherlands > http://www.beautifulcode.nl > > _______________________________________________ > Mav-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/mav-user _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
