Re: npe on simple type usage

2013-05-31 Thread Jens Breitenstein
Ken, I am glad you figured it out. But next time can you please examine the stacktrace more carefully? Let me show you what I mean: at org.apache.tapestry5.ioc.internal.util.ConstructorInvoker.invoke(ConstructorInvoker.java:48) at org.apache.tapestry5.ioc.internal.util.LoggingInvokab

Re: npe on simple type usage

2013-05-30 Thread Bob Harner
Ken, please try to moderate your own posts better, as others have said. Four emails in about an hour, with only you replying to your own emails, is a real waste of everybody's attention. Until you've spent at least a few hours on a problem, you're probably not stuck enough to beg free time from oth

RE: npe on simple type usage

2013-05-29 Thread Ken in Nashua
Solution... this was a hibernate initialization issue. I was seeding an entity I skipped a few fields thinking it was not a problem. but hibernate didn't like me operating on the entity while it was in its initialization phase. rule of thumb? initialize all your properties before your code deci

RE: npe on simple type usage

2013-05-29 Thread Ken in Nashua
I use these types to get padding and comfort. It doesnt make sense to me. Sorry to keep posting. Just trying to click and go. What could be causing an NPE? @Entity @ClassDescriptor(hasCyclicRelationships = true) @BeanModels( { @BeanModel(pageType = PageType.LIST, include = "player, gp, g

RE: npe on simple type usage

2013-05-29 Thread Ken in Nashua
Caused by: java.lang.NullPointerException at org.tynamo.examples.pphl.model.PlayerStats.getPts(PlayerStats.java:137) at org.tynamo.examples.pphl.model.PlayerStats.getPpa(PlayerStats.java:125) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMetho