Yep! I had two errors in my fetch specs. Both toMany relationships
that I had deleted for optimizing sake, but the old Entity Modeler
didn't kick me in the ass about. With the new 4849 build, the null
pointer went away and it pointed me right to the problems instantly!
Fixed and now generating as I expected for server-side classes.
Thanks a ton Mike!
Dave
On Mar 4, 2008, at 1:17 PM, Mike Schrag wrote:
> Grumble. This is a NPE caused by the new validation checks on
> qualifier bindings, which should be interesting to see what exactly
> the invalid key is. New build running now ... Tap your foot for
> another 15 minutes :) The next time you load your model (load it in
> EM before generating) it should tell you you have an invalid
> qualifier key. It's possible this is wrong. Let me know if it is.
> It should at least generate, but It's possible that if the
> validation thinks your binding is wrong then the generated java will
> also be wrong (because it's using the same code).
>
> ms
>
> On Mar 4, 2008, at 1:08 PM, David Avendasora wrote:
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse !ENTRY
>> org.objectstyle.wolips.eogenerator.core.ActivatorResources 4 4
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse 2008-03-04
>> 13:08:05.850
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse !MESSAGE Failed
>> to generate server_velocity.eogen.
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse !STACK 0
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse
>> java.lang.NullPointerException
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse at
>> org
>> .objectstyle
>> .wolips
>> .eomodeler
>> .core.model.EOFetchSpecification.verify(EOFetchSpecification.java:
>> 732)
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse at
>> org
>> .objectstyle
>> .wolips.eomodeler.core.model.EOEntity.verify(EOEntity.java:2184)
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse at
>> org
>> .objectstyle
>> .wolips.eomodeler.core.model.EOModel.verify(EOModel.java:1093)
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse at
>> org
>> .objectstyle
>> .wolips.eomodeler.core.model.EOModelGroup.verify(EOModelGroup.java:
>> 486)
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse at
>> org
>> .objectstyle
>> .wolips
>> .eogenerator
>> .core
>> .runner
>> .VelocityEOGeneratorRunner.generate(VelocityEOGeneratorRunner.java:
>> 136)
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse at
>> org
>> .objectstyle
>> .wolips
>> .eogenerator
>> .core
>> .model
>> .EOGenerateWorkspaceJob.runInWorkspace(EOGenerateWorkspaceJob.java:
>> 103)
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse at
>> org
>> .eclipse
>> .core
>> .internal
>> .resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
>> 3/4/08 1:08:05 PM [0x0-0x41041].org.eclipse.eclipse at
>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>>
>> On Mar 4, 2008, at 1:02 PM, David Avendasora wrote:
>>
>>> I just updated off Nightly, and My WOLips is now 4948, and I'm
>>> getting the following error when I generate. No matter what I use
>>> in the FS binding:
>>>
>>> /Users/davida/Documents/Projects/BestMaid/Development/
>>> Bakery_Managment/BakeryManagement_Framework/EOGenerator/
>>> server_velocity.eogen:
>>> null
>>>
>>>
>>> Not so helpful. Where can I find more detail about what exactly is
>>> null?
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Tue Mar 04 2008 - 13:47:11 EST