Hi there!
Per the other threads I've found on the issue it seems that CMDBuild has some issues when there are odd characters in the path of the application.
However, I've discovered that this also applies to when you normally deploy the WAR using Tomcat manager, which is inconvenient as I use a CM engine that interfaces with the Tomcat manager to make this automatic and simply to recreate.
As you can maybe guess, it means that instead of the path being /var/lib/tomcat/webapps/cmdbuild, it ends up being /var/lib/tomcat/webapps/cmdbuild##2.4.1, which is per the documentation of Tomcat correct when it finds version information available in the WAR-file.
Do I really need to work around this issue, or is there a way to actually fix this so that CMDBuild actually works per the EE standard?
Best regards,
Thor
Thank you for your submission, we will do some checks about that.
Best regards.
-- CMDBuild Team
Previously Thor K. H. wrote:
Hi there!
Per the other threads I've found on the issue it seems that CMDBuild has some issues when there are odd characters in the path of the application.
However, I've discovered that this also applies to when you normally deploy the WAR using Tomcat manager, which is inconvenient as I use a CM engine that interfaces with the Tomcat manager to make this automatic and simply to recreate.
As you can maybe guess, it means that instead of the path being /var/lib/tomcat/webapps/cmdbuild, it ends up being /var/lib/tomcat/webapps/cmdbuild##2.4.1, which is per the documentation of Tomcat correct when it finds version information available in the WAR-file.
Do I really need to work around this issue, or is there a way to actually fix this so that CMDBuild actually works per the EE standard?
Best regards,
Thor
Thanks a lot for following up! :)
I can report that I've filed a pull request with the configuration management system, so that I'm able to easily deploy CMDBuild without using a version identifier in Tomcat, which means that it's not an imminent problem anymore.
However, it's still something which should be possible as to be able to run multiple versions of CMDBuild in parallell, where Tomcat automatically chooses the deployment with the highest version number.
Have a continued good summer!
Previously Tecnoteca wrote:
Thank you for your submission, we will do some checks about that.
Best regards.
-- CMDBuild Team
Previously Thor K. H. wrote:
Hi there!
Per the other threads I've found on the issue it seems that CMDBuild has some issues when there are odd characters in the path of the application.
However, I've discovered that this also applies to when you normally deploy the WAR using Tomcat manager, which is inconvenient as I use a CM engine that interfaces with the Tomcat manager to make this automatic and simply to recreate.
As you can maybe guess, it means that instead of the path being /var/lib/tomcat/webapps/cmdbuild, it ends up being /var/lib/tomcat/webapps/cmdbuild##2.4.1, which is per the documentation of Tomcat correct when it finds version information available in the WAR-file.
Do I really need to work around this issue, or is there a way to actually fix this so that CMDBuild actually works per the EE standard?
Best regards,
Thor