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

http://www.starprecision.com

 

The concept i've been thinking is something like this:

A simple GUI or command line app, the connect's to a database and get's all metadata for tables and then generate the configuration xml's and skeleton classes. My main objective is NOT to use XML, you may ask why, simple, XML is pretty cool to read and parse, but when you have to write on your favourite editor (notepad, vi, whatever) is a very boring task... if there's a better way (or my idea is completly wrong) let me know and i'll go for that...

Anyway, there's got to be a way to feed the app with some input file in order to generate other beans like session or message driven.

I've been reading SUN's Blueprints and the code their sample EJB-app "adventure" so i'm thinking in making the generated code the most compliant possible. There's only one thing that i'm not thinking to follow, it's the encapsulation os entity beans inside session beans, instead, i'd go for common java beans, since openejb is running in embed mode inside tomcat.

What would be cool for the app, would be somekind of template in order to generate the code, instead of having it all hardcoded, maybe using java.text.Format or something else... this way it would be easy to port it to ejb 2.x with the same configurations...

<<inline: netvita.gif>>

Reply via email to