Shyam A said: > Thanks a lot Rick and Matt. I created the > log4j.properties file and the error message > disappeared.
Yeah, it just needs something, ANYTHING, to work with to get rid of that message. > I'm still looking for a solution to the sorting issue. My only suggestion on that is to look into the getters on your class. If you can step into those and see what's getting returned, maybe you'll see that data there. For example, on the object type contained in the jobList, look at the getJobName() or getOneUpNo() methods to see what value those are returning (you can use log4j there to output it to the console, also :). >> <display:column property="jobName" title="Job Name" sortable="true" /> >> <display:column property="oneUpNo" title=" OneUp# " sortable="true" /> Assuming it's not coming from there, then trace into the displaytag source and see if it's coming from there. I haven't ever seen any behavior like that myself. Are you using some sort of portal or proxy that might be mangling the URLs as they're coming out of displaytag? displaytag SHOULD be the last word in terms of what gets displayed at that point, so if it's not generating those params and isn't receiving them from the getters, then there has to be some sort of layer between displaytag and the final output to the browser. -- Rick Herrick [EMAIL PROTECTED] Proud member of the reality-based community Never try to discourage thinking for you are sure to succeed.--Bertrand Russell ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ displaytag-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/displaytag-user
