Those familiar with Flex, Hibernate, Spring, and BlazeDS are familiar with the lack of lazy loading support.

ME4S currently doesn't contain any magic to support lazy loading in this configuration due to the many solutions out there like Adobe's Life Cycle Data Services, or 3rd party libraries like dpHibernate. We also pondered adding in a DTO configuration to also handle this situation, which can be explained in this Spring forum post.

Since this is the first version of Flex generation in MyEclipse for Spring, we are very interested to hear everyone's thoughts on what direction we should take to handle this issue.

In the meantime, one item in the milestone that needs to be manually updated is the One-to-One relationship needs to be changed to EAGER. Go to the parent domain object and find where the field is defining the relationship. Change the FetchType to EAGER. This will populate the form for your one-to-one relationships in the tab navigator.

Kind regards,
Dave

Hi

I'm on the dpHibernate team.

I'd love to discuss getting dpHibernate support included in your Spring / Flex solution out-of-the-box.

Contact me at martypitt [at] me [ dot com ] to discuss how we can help add support.


Marty

Hello Dave and Hello Marty

First of all i have to mention that the "ME4S Flex Scaffolding" feature is what i have always been dreaming of, it is simply amazing and definately made my day :-).
The Spring Security Wizard is also very impressive and timesaving.

At the Moment i'm relaunching a FLEX/PIMENTO/JAVA/SPRING RIA for surveilling, managing solar plants, administrating their owners, service cycles and so on.
Long story, was once developed for the need of just 1 company and is now redeveloped for bigger needs ;-),

Back then I used a Framework featuring Hibernate lazy loading for Flex called Pimento - from SpiceFactory.
Concerning certain security issues for the relaunch i had to evaluate other Frameworks serving lazy loading,


What are my alternatives:

GraniteDS - http://www.graniteds.org/ a very good alternative to Adobe BlazeDS but because of scalability and security reasons it has to be BlazeDS.

LCDS - Definately amazing but expensive as hell, so no deal

DTO-Pattern - Simple overkill on work and a pain to maintain

dpHibernate - I thought it was dead until i visited Martys Blog 2h ago http://martypitt.wordpress.com


Since you released this great Scaffolding Feature and dpHIbernate looking very promising in the current state.

I will go with Spring/SpringSecurity/dpHibernate.

Now back to the Topic "which way should MyEclipse go" ....

In my eyes there should be LazyLoadingSupport for LCDS, simply beacause i'd love to read a slogan like "You're really paying thousands of dollars every year for LCDS? Then at least save time and money at developement - MyEclipse LCDS Edition"

DTO would be fine,since it is all generated! But only if it comes with advanced refactoring: e.g. you edit your entity and the accorting dto is adapted automatically.
Oh and if your really go with DTO don't forget the automated as3 generation!

Seriously DTO is no good!

Going with dpHibernate or something comparable would be amazing, but only if the Framework is seriously maintained!

I am going with dpHibernate and i hope i won't be Bugcrafized ;-).

I hope for the next project i don't have to do the dpHibernate configuration by hand.


If there are any questions, feel free to contact me :-).

Kind regards from Germany

Martin

Great info! Thanks so much for the feedback, Martin and Marty!!

=Dave

If you check out the JIRA for the upcoming Spring-BlazeDS Integration 1.5 project, you will see that SpringSource has been able to fix this issue, and a stable build should hopefully be released before too long. They are already using it in the latest milestone releases for Roo's Flex scaffolding capabilities.

https://jira.springframework.org/browse/FLEX-80

That's great to know, thank you! I'll keep an eye on 1.5, and get that pushed into ME4S as soon as possible after it goes GA.

In the meantime, I'm assuming the 1.5 M1 jars can simply be swapped out for the 1.0.3 jars if folks want to test this in a scaffolded MyEclipse for Spring app.
Kind regards,
Dave