Re: Ognl issues in tapestry 4.1.6

2009-05-15 Thread Howard.Kelsey
Hi So after much debugging I found that: 1.Our class is available in the WebappClassLoader because classLoader.loadClass(“com.algorithmics.opvantage.model.domain.Event”) returns the class. The problem is that the bytecode enhancement for ongl uses javassist to find the class and if the cl

Re: Ognl issues in tapestry 4.1.6

2009-05-13 Thread Howard.Kelsey
Hi Our domain classes are generated/compiled at startup time to support client data model. These are simple pojos with getters and setters for each property. The class is definitely available because content.domain.startDate, content.domain.getStartDate(), content.domain[‘startDate’] all work,

Re: Ognl issues in tapestry 4.1.6

2009-05-12 Thread Howard Lewis Ship
It would be helpful to see the Domain class. Perhaps there's an overloaded method that's confusing the OGNL code. As you can see, it's trying to generate bytecode for your expression, but failing for some reason. Classloader issues can get very tricky inside this kind of code. On Tue, May 12, 2009