Hello Matthias, Friday, July 12, 2002, 4:19:33 AM, you wrote:
MB> this week, I have completed the development of an open source code generator MB> that takes a Unified Modeling Language (UML) model from a CASE-tool in XML MB> Metadata Interchange (XMI) format and generates Enterprise JavaBeans classes MB> with XDoclet tags as output ... I am developing a tool who works like this. My tool has many thing in common with yours. The first version was almost the same idea from : XMI code to XDoclets sources. The model (on Rational Rose) had esteriotypes to show what they should create. But I start to study Java (and Jboss,XDoclet,J2EE) all at the same time just some months ago. So I start to use XDoclet and it is not a good idea use it if you are not very confortable with EJBs. So my prototype is creating the source code of all classes and interfaces (home,remote,bean implementation). I start to use it with XMI files exported from Rational Rose. But when I try to use it from XMI files from Poseidon I discover the same problem you had. There are dialects on the XMI language. So I use the same solution : the XMI files are processed to a XML file with all information I need. I call it the model.xml file. So I only need one routine to each UML tool. As I need to do this fast (because I want to show this on a demonstration) I make this XMI to "my XML format" with a Delphi program. This is very good for Rose because the can communicate using COM on Windows. This is a XDoclet list but I will say something. What do you think about create just plain Java files and not XDoclets files ? Today I can understand XDoclet and this is not a problem to me. But if we are generating files why not create all of them ? To the final user this does not make any difference. In fact is better because the user shoud not need to install XDoclet. On my first version I had some very simple code geration routines. In fact they are just println statements. For the next version I am planning something better. I am creating values objects to my entitys too. On another e-mail Chris Shaw talk about use reflection to make a persistence layer which can work on small non-complicated projects. This is another thing I am already doing. I am using the same XML file used to generate the files (the model.xml) at runtime to create a user interface. All entitys are a option on the menu. Inside this option I will can insert/ delete/update the entity. The relationships are show too, and the user will can edit this from there. This is a very natural way of work. But as Chris say before this is off-topic. It is a good idea everyone who want to make this work subscribe the UML2EJB list. I think we can do a very good job with this. -- Best regards, Danilo mailto:[EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
