Hi Guys,
generally speaking since FB 15 (not sure which version, probably 15.0) there have been some changes implemented to the /web folder, i.e. all the resources like css and js file are no longer taken from the /web/public folder but from the proper service folder under /web/work (like jetty-0.0.0.0-{PORT}-funnelback-publicui.war-...).
I would like to expose some resources to public (reports, CSV) and also allow the scripts (cgi) to be executed from the external sources (Magento) on FB >15. The solution works fine on 14.2 and my question is what would be the best way to achieve similar behaviour on >15.
We've noticed that on FB 15 there is a lack (probably intended) of one file - search-classic.xml which previously was present under /web/conf/contexts-http. That config file sets some kind of alias that can be reached, among the other things:
<Set name="contextPath">/search</Set>
<Set name="resourceBase"><SystemProperty name="funnelback.installdir"/>/web/public</Set>
Recreating that file on FB 15 under /web/conf/contexts-public, creating /public directory under /web and restarting Jetty basically helps but I am wondering if removing the previous concept was intended is there any other way of doing that so it can suit to how the FB 15 works with public resources?
Is putting all needed resources in the proper service folder under /work (/work/{service}/webapp/) in the same way as css and js files is a good idea?
Where can I find or set the Jetty settings to allow the particular folder to be exposed (in the same way it's done for /resources-global folder)?
Thanks,
Mirek