Well all the other attributes were accessible.
I checked the ECs, even created a new one.
My suspicion lies in the word "services"
Maybe I will try that again in some other little project to doubly test.
On Feb 13, 2013, at 7:05 PM, Chuck Hill wrote:
> Maybe you forgot to call super someplace
it was originally a many-to-many with a flattened relationship.
I couldn't even check for that via the flattened attribute... would just balk
up an NPE.
anyway I have moved on.
On Feb 13, 2013, at 6:58 PM, David Avendasora wrote:
> A to-many relationship should never give you null in the fir
Maybe you forgot to call super someplace in your EO? Or you have an EO which
is not actually in an EC yet (and hence IMO is not really and EO)
Chuck
On 2013-02-13, at 4:58 PM, David Avendasora wrote:
> A to-many relationship should never give you null in the first place.
> To-manys always re
A to-many relationship should never give you null in the first place. To-manys
always return an empty array.
There must something wrong with the flattened relationship. What is the name of
the join Entity and it's relationships?
Dave
On Feb 14, 2013, at 8:18 AM, James Cicenia wrote:
>
> No
Well it turns out that after reviewing the model... We don't need a
many-to-many relation.
A user can only have one "service." So I changed the model and made the
attribute
and relation be "serviceLevel."
So things work now. Though now I have that little irritating lingering question
about
if
Details?
On 2013-02-13, at 4:33 PM, James Cicenia wrote:
>
> Just a typical null pointer exception hmmm, I wonder if "services" is
> some reserved word...
>
>
>
>
> On Feb 13, 2013, at 6:21 PM, Chuck Hill wrote:
>
>> Catch the exception, and log out e.getTargetException()
>>
>> On 20
Just a typical null pointer exception hmmm, I wonder if "services" is some
reserved word...
On Feb 13, 2013, at 6:21 PM, Chuck Hill wrote:
> Catch the exception, and log out e.getTargetException()
>
> On 2013-02-13, at 4:18 PM, James Cicenia wrote:
>
>>
>> No... it just throws the ex
Catch the exception, and log out e.getTargetException()
On 2013-02-13, at 4:18 PM, James Cicenia wrote:
>
> No... it just throws the exception to the console which it shouldn't.
>
> even if I do a test of if(user.services == null) it still gives me this dump.
>
> I have never seen this behavi
No... it just throws the exception to the console which it shouldn't.
even if I do a test of if(user.services == null) it still gives me this dump.
I have never seen this behavior before. It is a flattened many to many.
Thanks
James
On Feb 13, 2013, at 5:54 PM, Chuck Hill wrote:
> Unresolv
Unresolved compilation error? Picking up some other User class?
Crashes how? JVM exits? Machine reboots?
On 2013-02-13, at 2:31 PM, James Cicenia wrote:
> Hello -
>
> I notice that if I do this:
>
> System.out.println("services is "+user.services());
>
> it doesn't print,,, it just crashe
Hello -
I notice that if I do this:
System.out.println("services is "+user.services());
it doesn't print,,, it just crashes?
And yes user exists.
thanks
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.Na
11 matches
Mail list logo
