Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

lachoy (1663)

lachoy
  chris.winters@gmail.com
http://www.cwinters.com/

I am actually Chris Winters; I am actually living in Pittsburgh, Pennsylvania, USA; I am actually married and have three cats. (Guess what one of them is named?) I am the "OpenInteract" guy, which could be good or bad.

Journal of lachoy (1663)

Wednesday March 20, 2002
08:15 AM

Code generation

[ #3666 ]

I'm revisiting the system used to generate lots of Entity and Session beans for the system at work. It uses a Java class to dump JDBC metadata to a file, then a series of Perl clases that use this data metadata, human-entered relationship and usage metadata, and s series of Template Toolkit templates to generate lots of Java source and the necessary XML deployment descriptors. (Huh, maybe I should have submitted that to OSCON...)

It works pretty well right now, but my reasons for revisiting are:

  • 20% allowing someone else to edit the relationship/usage metadata (currently in one big serialized perl data structure, going to be in separate INI files)
  • 40% to extend it to create the classes necessary to implement the Business Delegate pattern and make the Entity beans "dumber", and
  • 40% to simplify it, so that I can understand it when I look at it in six months :-)

I toyed with the idea of rewriting it in Java so the system would be more homogenous (and I'd get some experierience with Java templating systems) but there's not enough time for that.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.