| Category: | Bug report |
Priority: | Normal |
Status: | Feedback Requested |
| Project: | Severity: | Minor |
Resolution: | Open |
|
| Component: | Reproducibility: | Always |
Assigned to: |
The symptoms was described in this thread on JasperForge
And then I further investigated and noted these
During a source build, the PRO version of WEB-INF/web.xml comes directly from the CE version of webappAdditions/WEB-INF/web.xml (with some filtering going on during the CE build). In other words, there is no WEB-INF/web.xml in the PRO source directory (i.e. jasperserver-pro/jasperserver-war/src/main/webapp/WEB-INF/web.xml) that would shadow/override the CE version. Nor is there any filtering that would swap out the value of webAppRootKey from jasperserver.root to jasperserver-pro.root.
I cannot explain why the bitrock installer does not have this same problem.
3 Comments:
The Pro web.xml is updated during the Pro build.
How were you doing the build?
I was following the "manual build" procedures as documented in Chapter 5 "Configuring the Build Environment Manually" of the JasperServer-Pro-Source-Build-Guide.pdf (Release 3.5).
Could it be my source zip file is out of of sync with the 3.5.0 snapshot? I am asking this question because in another occasion I found that my applicationContext.xml (in the CE directory) is missing these two lines
<value>WEB-INF/bundles/ja_mondrian_messages</value>
<value>WEB-INF/bundles/mondrian_exception_messages</value>
for the bean "messageSource". I also could not find any mechanism to override or filter the CE version into the Pro version. I had to manually make a copy in my Pro directory to shadow the CE version.
The Maven build process for the Pro WAR calls an Ant task to do the update. Have a look at the Pro jasperserver-war/pom.xml. Can you see it executing?