Re: EOGenerator problem
Hi Jeff, On 30 Jan 2018, at 14:05, Jeff Schmitz wrote: > I recently updated to Eclipse Oxygen and somewhere in the process my > EOGenerator behavior has been changed. As an aside to Johann’s explanation, we got into the practice some time ago of including EOGenerator templates in every project that uses them, and then pointing the .eogen files at those per-project templates. This allows you to update the templates on your schedule, and avoids being bitten at Eclipse/WOLips upgrades like you describe. -- Paul Hoadley https://logicsquad.net/ https://www.linkedin.com/company/logic-squad/ ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: EOGenerator problem
Hi Jeff,
the (very) old EO templates used to use log4j for logging but this was replaced
by slf4j in the current ones some time ago. Perhaps you have a lib problem
there? Passing a null value to e.g. the debug method of slf4j should be no
problem as it converts that to the string „null“ before constructing the
logging message.
What version of Wonder do you use? ERJars includes the slf4j library. What is
the stack trace of your NPE?
If you want to use the old templates instead and you followed the instructions
on the wocommunity wiki, did you download the templates where the link is
pointing to? If the answer is yes then you probably downloaded the (same) new
templates instead of the old ones you wanted. You would have to switch to
another branch like eclipse_3_8 first or go back in git history.
jw
> Am 30.01.2018 um 04:35 schrieb Jeff Schmitz :
>
> Hello List,
>I recently updated to Eclipse Oxygen and somewhere in the process my
> EOGenerator behavior has been changed. Specifically, where it used to
> generate “set” functions like this:
>
> public void setMiscState1(Boolean value) {
> if (_Entry.LOG.isDebugEnabled()) {
> _Entry.LOG.debug( "updating miscState1 from " + miscState1() + " to " +
> value);
> }
> takeStoredValueForKey(value, _Entry.MISC_STATE1_KEY);
> }
>
> It’s now generating them like below, which causes a null pointer exception
> when miscState1() happens to return null.
>
> public void setMiscState1(Boolean value) {
> log.debug( "updating miscState1 from {} to {}", miscState1(), value);
> takeStoredValueForKey(value, _Entry.MISC_STATE1_KEY);
> }
>
> Any idea how I can get back my old EOGenerator functionality? I have tried
> following the instructions here:
> https://wiki.wocommunity.org/display/WOL/EOGenerator and I specified the
> wondierEntity files in my EOGenerator preferences as suggested.
>
> Thanks!
> Jeff
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
EOGenerator problem
Hello List,
I recently updated to Eclipse Oxygen and somewhere in the process my
EOGenerator behavior has been changed. Specifically, where it used to generate
“set” functions like this:
public void setMiscState1(Boolean value) {
if (_Entry.LOG.isDebugEnabled()) {
_Entry.LOG.debug( "updating miscState1 from " + miscState1() + " to " +
value);
}
takeStoredValueForKey(value, _Entry.MISC_STATE1_KEY);
}
It’s now generating them like below, which causes a null pointer exception when
miscState1() happens to return null.
public void setMiscState1(Boolean value) {
log.debug( "updating miscState1 from {} to {}", miscState1(), value);
takeStoredValueForKey(value, _Entry.MISC_STATE1_KEY);
}
Any idea how I can get back my old EOGenerator functionality? I have tried
following the instructions here:
https://wiki.wocommunity.org/display/WOL/EOGenerator
and I specified the
wondierEntity files in my EOGenerator preferences as suggested.
Thanks!
Jeff ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: velocity eogenerator problem
The default eogenerator templates use generics. NSArray/Set/etc is only generic in WO 5.4 or Project Wonder. If you are using WO 5.3 without Wonder, then your NS* is not generic and cannot use the generic templates, so you must use the 1.4 templates. ms On Jun 23, 2008, at 11:33 AM, Patrick Robinson wrote: I'm converting an old Xcode project to WOLips (using Tiger, java 1.5, Eclipse 3.3.2, WOLips 3.3.5266, and WO 5.3.3). I reached the point where I made a change to my model which resulted in velocity EOGenerator being run, and now I have a bunch of code that won't compile. I'm getting: The type NSArray is not generic; it cannot be parameterized with arguments All my WOLips EOGenerator system preferences are blank (i.e. default). In my eogen file, I've specified the superclass package, and the Destination and Subclass Destination folders, and that's it. Project Wonder is not involved at all. I've seen that others have had this problem, and the solution for them has always seemed to involved use of the 5.4 vs 5.3 versions of Wonder - but this project doesn't use Wonder. If I check the EOGenerator preference box for "Use Java 1.4 Templates (Velocity only)", then this problem goes away. But, why? I'm using java 1.5. What's the problem here? -- Patrick Robinson AHNR Info Technology, Virginia Tech [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
velocity eogenerator problem
I'm converting an old Xcode project to WOLips (using Tiger, java 1.5, Eclipse 3.3.2, WOLips 3.3.5266, and WO 5.3.3). I reached the point where I made a change to my model which resulted in velocity EOGenerator being run, and now I have a bunch of code that won't compile. I'm getting: The type NSArray is not generic; it cannot be parameterized with arguments All my WOLips EOGenerator system preferences are blank (i.e. default). In my eogen file, I've specified the superclass package, and the Destination and Subclass Destination folders, and that's it. Project Wonder is not involved at all. I've seen that others have had this problem, and the solution for them has always seemed to involved use of the 5.4 vs 5.3 versions of Wonder - but this project doesn't use Wonder. If I check the EOGenerator preference box for "Use Java 1.4 Templates (Velocity only)", then this problem goes away. But, why? I'm using java 1.5. What's the problem here? -- Patrick Robinson AHNR Info Technology, Virginia Tech [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
