I can get both of them to "work", but neither one is creating executable
code. Ultimately, I expect Apple's will turn out to be the winner, but
while we wait...
I'm seeing the following out of Velocity:
public $attribute.javaClassName accountAccess() {
return ($attribute.javaClassName) storedValueForKey("accountAccess");
}
public void setAccountAccess($attribute.javaClassName value) {
if (_Users.LOG.isDebugEnabled()) {
_Users.LOG.debug( "updating accountAccess from " + accountAccess() +
" to " + value);
}
takeStoredValueForKey(value, "accountAccess");
}
This is using Eclipse 3.3.1.1 and WOLips 3.3.4655, WO 5.4 on Leopard. This
is using the latest templates.
I think it will be less work to go back to JavaEOGenerator, but it's all
painful. Argh!
I wish I had time to fix the templates myself, but I'll just punt for now as
I'm a way behind schedule. I suspect the best solution will be to take
the Apple templates and hack them with ideas from Velocity and fix the bugs.
--
Les Vogel
808 870-0418
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
