In the current version, you can only import a pre-exisitng schema. You can't create anything yourself, Middlegen creates entities and relations based on what's in the database. However, you can modify the entities, fields and relations that Middlegen creates.
Aslak -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of tek1 Sent: 9. oktober 2001 18:03 To: [EMAIL PROTECTED] Subject: Re: [Xdoclet-user] Middlegen - source code generator for XDoclet/EJBGen here are the links for info about dods and jboss gui: dods: http://dods.enhydra.org/cvs_source/DODS/index.html jboss gui: http://www.joyful-noise.de/jbossgui/index.html a question abt middlegen, do you start by creating the objects in your tool first, or do you start by importing a pre-existing db schema, or are both possible? thx. :) At 01:27 01/10/10 +0200, you wrote: >Hi tek1, all! > >I am not familiar with either dods or the jboss gui, as I spend all my EJB >time with WLS, so I'm not in the position to judge whether or not the >projects you're mentioning could benefit from synergy effects. I'd be happy >to work with any project that fits. > >I'll describe the intention of Middlegen further, so that people familiar >with dods and jboss gui (and other projects like EJBGen and XDoclet) have a >better basis to judge whether cooperation/integration is appropriate: > >Middlegen is (at least in its current state) a code generation tool for >Entity Beans. Its architecture makes it possible to write code generator >plugins for special targets. Currently, it generates code that can be >further processed by XDoclet, but it would be easy to extend it so that it >generates code for EJBGen or any other "platform". (You could extend it to >generate Commodore 64 basic code for that matter, although that code >probably wouldn't be able to do anything useful). > >The basis for the code generation is an internal model that represents a >database schema with its tables, fields, keys and relations. This model is >populated by reading meta data from a database using JDBC. > >The reason why it is a gui tool is that users will want to tune the output >before generating code. Say, for a CUSTOMER table, you would maybe want to >generate only setters for some fields, and getters for some. Maybe you want >to map the table's BLOB 'picture' field to an InputStream 'photo' attribute >in the generated Customer Entity bean. -And maybe you want some attributes >to be available only in the local EJB interface, and not in the remote >interface. You can also tune relations to make them unidirectional or >bidirectional, cascade-delete and so on. The intention is to support >additional app-server specific tuning too. When you're done tuning, you >generate the code. The you pass that code to EJBGen or XDoclet (or dods?). > >I am involved with the XDoclet project, so my energy will go into the >Middlegen core and XDoclet generation for WLS. However, anybody who wants to >add support for EJBGen, XDoclet/JBoss, XDoclet/Orion (or whatever product >could benefit from Middlegen) are encouraged to contact me and join the >project. Guess I could need som help with the core too. > >More viewpoints are most welcome. > ><aslak/> _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
