Custom Installer created from April build broken
20 May, 2015
System Error on login:
The absolute uri: http://struts.apache.org/tags-bean cannot be resolved in either web.xml or the jar files deployed with this application
I had to resolve it manually by taking the files mentioned in the fix from another install:
http://www.mkyong.com/struts/the-absolute-uri-httpstruts-apache-orgtags-bean-cannot-be-resolved-in-either-web-xml-or-the-jar-files-deployed-with-this-application/
I do not know why these files are missing from the installer. My custom installer properties do not change any of the internal files for the base installer, merely add files for customized header and footer and login page.
The absolute uri: http://struts.apache.org/tags-bean cannot be resolved in either web.xml or the jar files deployed with this application
I had to resolve it manually by taking the files mentioned in the fix from another install:
http://www.mkyong.com/struts/the-absolute-uri-httpstruts-apache-orgtags-bean-cannot-be-resolved-in-either-web-xml-or-the-jar-files-deployed-with-this-application/
I do not know why these files are missing from the installer. My custom installer properties do not change any of the internal files for the base installer, merely add files for customized header and footer and login page.
Hello Justin,
Sorry for the inconvenience this has caused you. I came across this issue after
a quick search and found a note from one of our developers; I have pasted it below.
This is an artefact of upgrading to Struts 1.4
Change all instances of:
jakarta.apache.org/struts/
to
struts.apache.org/
in all custom JSPs.
Let me know if you have any follow up questions to this.
Thank you,
Kyle
Sorry for the inconvenience this has caused you. I came across this issue after
a quick search and found a note from one of our developers; I have pasted it below.
This is an artefact of upgrading to Struts 1.4
Change all instances of:
jakarta.apache.org/struts/
to
struts.apache.org/
in all custom JSPs.
Let me know if you have any follow up questions to this.
Thank you,
Kyle
One thing I also did to resolve this, which we talked about via email, is that new example customized login pages and header/footer pages were released with YF, and I simply customized those updated pages to make sure I'm using all appropriate package/class/method calls.
