On Fri, May 30, 2008 at 12:17 PM, Gwyn Evans <[EMAIL PROTECTED]> wrote: > On Fri, May 30, 2008 at 5:14 PM, David Nedrow <[EMAIL PROTECTED]> wrote: >> >> On May 30, 2008, at 11:47 AM, Thomas Mäder wrote: >> >>> 2) You're being done in by the BoundCompoundPropertyModel you have in the >>> item. Fire up the debugger and check the values directly (relying on >>> toString() is bad; some object might be lying to you. Step into the >>> item.getModelObject(). >> >> After stepping into getModelObject(), I can clearly see that there is a list >> of protocol items containing expected data. > > Just to double-check Thomas's point (1), are there any of the jars > being loaded from the AppServer's class-path rather than the Web-App's > classpath? (What AppServer anyway?) >
You can do Protocol.class.equals(item.getModelObject().getClass()) to see if you're running into classloader issues. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]