As soon as I started using Eclipse, I pretty much stopped using
WebObjects Builder and started using the built-in component editor of
Eclipse. The more I used the built-in component editor, the more I
got sick of keeping my bindings in a separate file, and so I started
using WOOgnl to put all my bindings in-line. To me it's much more
readable, and there are scads of cool little features about it that
can save you a ton of time. The problem was that I had tons of
existing code that used the old style of bindings, and after
converting two or three to WOOgnl format, I was fed up pretty
quickly. So I bit the bullet and wrote a PERL script to do it for
me. It took awhile to account for all the outside cases of different
acceptable syntax, but I've now used the script on hundreds of
components, and it seems to work quite well. If anyone is
interested, I've posted the scripts for public consumption.
Of course, there is no warranty implied whatsoever, so please use
with caution! The first script (convertToWOOgnl) simply takes the
path to a .wo file and spits out a WOOgnl-ized HTML file to standard
out. You can then copy this output over the HTML portion of your .wo
and delete the contents of the .wod portion. The second script
(convertProjectToWOOgnl), for the truly brave, invokes the first. It
takes a directory path as an argument, updates the .html of every .wo
in the directory, and whacks the .wod file. It does nothing to back
up the directory before-hand, so PLEASE be prudent if you use this
and make a copy of the directory first, and test your components
after. The scripts work smashingly for me, but you never know when
there's an outside case that you missed coding for, so I just want to
be sure everybody is clear about the implications of using the second
script. The first is extremely safe, since it only works on one file
at a time, doesn't modify any files, and simply writes its output to
the terminal.