We have ceased using standalone Hibernate in favor of EJB 3.0. We would like to see FDS 2.0 move in this direction. XML files for defining entities are no longer needed, because this functionality is provided much better by Annotations.
Hibernate also provides an API to read the configuration after Hibernate processes the XML files, which could be used for legacy support. In enterprise development work, our goal is to completely avoid having the same information in more than one place. Having to define our functions, objects, and entity identifiers in a separate XML file specific to Flex is contrary to our design philosophy (the destination tags in flex-data-service.xml). Since our entities are annotated with security information, key information, information about relationships with other entities, our methods are exposed through remote interfaces, and our EJB's are published to JNDI, FDS should be aware of all of these aspects of our persistence layer wouth the need for pulling out into XML that which already exists in our server tier software. In another thread, I speak of what appears to be a lack of JNDI support in FDS 2.0 for locating services such as EJB's, something we've been happily using in the standalone Flash Remoting product. I am hopeful that while building a next generation product in Flex 2.0, Adobe will take advantage of all of the newest ways to make our workflow as efficient as possible, so these large applications with hundreds if not thousands of entities can be maintained from one source - the annontated Java class files which define them. -- 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/ <*> 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/
