|
Paulo, I
can see why you wouldn’t want to use XML but I think XML is the way to
go. I might be persuaded to think
otherwise if I knew how you planned on getting the database with the current
information and such. Could you
explain this a bit more? I have a
few concerns I think I should mention, although they’ll probably be
rectified in your explanation.
Doesn’t involving a database require more overhead than
necessary? This will require
OpenEJB or the end user to install, populate and maintain a database. With XML, it’s all created by the
developers and then, no one needs any extra steps or knowledge. Also, there would be a performance hit
if we had to connect to databases instead of parsing an XML file. I think XML would be the way to go but
that is my opinion and we all have our own. I think the GUI approach would be
awesome but it might be easier to just create a command line tool first, since
OpenEJB is all done from command line, and then add a GUI later. I guess we’ll reconvene when you
email me back. In the meantime, my
Instant Messenger screen names are as follows if you’d like to contact me
that way: Yahoo: JCScoobyRS AIM: NuLinuxLvr MSNM: [EMAIL PROTECTED] I’ll
also be in the OpenEJB IRC. Here is
the info: Server: irc.freenode.net Port: 6667 Channel: #openejb I
look forward to hearing from you, Jeremy -----Original Message----- Jeremy Whitlock wrote: Paulo,
I’m interested in helping you with your Bean Generator. I have the
code, and I’ve fixed the problem with the absolute path to input.txt but
I want to know how you plan on this thing working. Also, how will it
become a part of OpenEJB? The reason I ask is that your answers will
determine how the app is written and packaged. Get back with me regarding
your thoughts. Thanks, Jeremy Whitlock ---
MCP/MCSA IT Manager for Star
Precision, Inc. Phone: (970)
535-4795 Metro: (303)
926-0559 Fax: (970) 535-0780 Metro Fax: (303)
926-0559 The concept i've been thinking is something like this: --
|
<<image001.gif>>
