TAP5-920 has long been an issue for one of our applications which uses composite keys.
https://issues.apache.org/jira/browse/TAP5-920 In the past we have worked around the issue by providing an encoder with our affected loops. We are now working on upgrading from 5.1.0.5 to 5.2.4 and have run into a new problem: Even if we supply an encoder, the default encoder (HibernateEntityValueEncoder) gets used and the NPE is back. Below is a stack trace. Suggestions? Caused by: java.lang.NullPointerException at org.apache.tapestry5.internal.hibernate.HibernateEntityValueEncoder.<init>(HibernateEntityValueEncoder.java:53) at org.apache.tapestry5.hibernate.HibernateModule$1.create(HibernateModule.java:104) at org.apache.tapestry5.internal.services.ValueEncoderSourceImpl.getValueEncoder(ValueEncoderSourceImpl.java:48) at $ValueEncoderSource_12eead93780.getValueEncoder($ValueEncoderSource_12eead93780.java) at org.apache.tapestry5.internal.services.ComponentDefaultProviderImpl.defaultValueEncoder(ComponentDefaultProviderImpl.java:124) at $ComponentDefaultProvider_12eead93782.defaultValueEncoder($ComponentDefaultProvider_12eead93782.java) at org.apache.tapestry5.corelib.components.Loop.defaultEncoder(Loop.java:304) at org.apache.tapestry5.corelib.components.Loop$MethodAccess_defaultEncoder_12eead93e34.invoke(Loop$MethodAccess_defaultEncoder_12eead93e34.java) at org.apache.tapestry5.internal.transform.ParameterWorker$InvokeParameterDefaultMethod.advise(ParameterWorker.java:95) -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
