What functionality are you successfully using in your EO SuperClasses?

Question

Hi Everyone:
We are very new to JHeadstart/JDeveloper and have just established the method we are going to use at the Entity Level to convert input to Uppercase by putting the following code into a superclass and extending the .xml files of the entities from EntityImpl to this superclass which we called UWEntityImpl.
What I am wondering is what other ways is this functionality being used by you more experienced JHeadstart Developers? I am trying not to re-invent the wheel and utilize methods that have worked well for you.
Of course I can think of toLowerCase, what else are you using?
Thanks so much in advance.
Mary
U of Windsor
Example Code:
package its.sis.BusinessModel.model;
import oracle.jbo.AttributeDef;
import oracle.jbo.server.EntityImpl;
public class UWEntityImpl extends EntityImpl {
public UWEntityImpl () {
// This code converts the inputted string to Uppercase in the database.
// April 27, 2007 mb
protected void setAttributeInternal(int i, Object object) {
Object value = object;
AttributeDef def = getEntityDef().getAttributeDef(i);
if ("true".equalsIgnoreCase((String)def.getProperty("UPPERCASE"))) {
if (value != null && value instanceof String) {
value = ((String)value).toUpperCase();
super.setAttributeInternal(i, value);
}

Answer 1

to)? I was curious because it seems to store them in
a proprietary format, and before I get into moving
hundreds more images I thought I would ask. I have
2-300 gigs of usable space but Aperture seems like it
could get huge with image adjustments.
Hi Eric,
I'm not a pro, but I wanted to clear up one of your issues. Aperture does not store or convert your files in a proprietary format. The image files that you store in the library will remain in their original format and untouched. The "Library" is a Mac OS X entity called a package. A package appears as a single file, but it's an illusion. If you ever needed to extract your image files, you can do so in the Finder (without Aperture) by option-clicking on the "Library" and selecting "Show Package Contents". Now you can navigate the file and folder structure to get at your originals. Of course, a much faster and easier way is to have Aperture export the originals. However, my point was to clear up the "proprietary" structure misunderstanding.
Also--as was mentioned--each adjustment doesn't create a new image file. Every new version of your original is merely a list of instructions or "recipe" used to apply adjustments to the original to recreate the version for screen and print. This is done dynamically, on the fly. A finished version of the original is never created and saved to a file until you tell it to export a version. Thus, every version is a very small addition to the database. This is very unlike iPhoto, where every new version of a file creates a new image to store...all the more reason to move to Aperture.
Hope that helps.