I am developing an app that uses the remote object tied to a java/spring/hybernate app like you describe. This was a legacy app already written with a jsf front end, and for the most part, the flex stuff has gone over the business logic, pretty well. There have been a couple bumps in the road, but that could have something to do with the way I am implementing it. One of the things I have noticed, is you are not able to lazy load your hybernate objects, so an object with one to many or many to many relationships will error out. You must pass back to flex fully completed java objects when it asks for them. Also when you pass an object to flex, then edit it, and pass it back, I was getting hybernate duplicate object errors. The reason for this is that hybernate is still maintaining the instance of that object, and if you make a change to it, based on id, then it considers them as two objects of the same ID. you can either merge the two of them, delete the hybernate instance, or create a new object based off the flex object being passed, then set the hybernate object params to the flex object params using the getters and setters.
So its not completely seamless, but it shows some promise. Course I could be doing it totally wrong too. I know this way works but it might not be a best practice. This to me seems an area of flex sorely in need of better documentation. There are no tutorials or walkthroughs of anything beyond simple objects being passed to and from java, and usually not having anything to do with spring and hybernate connections. At least if there are some tutorials on passing complex objects (meaning an object with at least another object embedded in it) back and forth using spring/hybernate in either remote object or dataservices I have not found it and would love to see it. --- In [email protected], "dreuimar" <[EMAIL PROTECTED]> wrote: > > Hey everyone, > > I'm currently constructing an application that uses DataServices with > the Hibernate Assembler. I wanted to make the business logic > independent of the view (Flex) so that another application I write > with a web frontend (using Spring MVC) can use the same logic that > Flex uses. I was going to do this using Remote Objects with the > SpringBeanAdapter, but I'm worried about losing the ability for data > pushing, managed classes, etc. Can I still maintain many of the > options I had with FDS using the SpringBeanAdapter? > > Brennan > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
