We were using displaytag 1.0 in our project that also uses <b>Struts 1.1</b> on a <b>Weblogic 8.1 SP3</b> server.
We now want to upgrade to displayTag 1.1, but are facing several issues.
I have already upgraded the commons jars but do I HAVE to upgrade to Struts 1.2.7 ?
Also, we are using Weblogic 8.1 SP3 which supports Servlet API 2.3. I have checked the dependencies page, but am not sure if the 1.1 upgrade will run with the existing server version. I m not re-compiling the displayTag code, do I also need to upgrade to Weblogic 9.0 to run the existing code?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
servlet 2.3 (jsp 1.2) is fine and you should not need to update struts (there should be nothing struts 1.2 specific in displaytag code).
Be sure to delete previously compiled pages (.java and .class files) and to correctly update other core dependencies (commons-lang, commons-collections)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We were using displaytag 1.0 in our project that also uses <b>Struts 1.1</b> on a <b>Weblogic 8.1 SP3</b> server.
We now want to upgrade to displayTag 1.1, but are facing several issues.
I have already upgraded the commons jars but do I HAVE to upgrade to Struts 1.2.7 ?
Also, we are using Weblogic 8.1 SP3 which supports Servlet API 2.3. I have checked the dependencies page, but am not sure if the 1.1 upgrade will run with the existing server version. I m not re-compiling the displayTag code, do I also need to upgrade to Weblogic 9.0 to run the existing code?
servlet 2.3 (jsp 1.2) is fine and you should not need to update struts (there should be nothing struts 1.2 specific in displaytag code).
Be sure to delete previously compiled pages (.java and .class files) and to correctly update other core dependencies (commons-lang, commons-collections)
Further to this.. I m getting a ServletException in a getHtmlId()method after the upgrade. This exception is thrown at the display:table tag.
I dont have the stack trace right now, but I think this might be because of inconsistent jars used.