Thanks Graham.
I thought/hoped this would be the case. It is a lot easier to test it out with jQuery libraries as you can just hotlink to them hosted elsewhere, as many people have done in various blogs already, or just import the .js file as a mime into your BSP application.
I started down this route with UI5 but as you mention, at 80Mb (and a complex directory structure too) adding all of the content in as mimes to a BSP app isn't the most efficient way of doing things!
Graham Robinson wrote:
So you might want to consider putting them in a file system directory on the WAS and accessing them from the ICF using a system parameter like this.
icm/HTTP/file_access_1 = PREFIX=/sapui5/,DOCROOT=C:\usr\sapui5,BROWSEDIR=2,CACHECTRL=+28800
I'm not familair with this approach sorry (been working on the Java stack for too long!) Am I right in thinking this just makes the UI5 libraries available on the WAS, much the same as if I dropped them into htdocs on apache or similar? Or is there more to it? I am trying to build a solution that doesn't use ICF if possible, just BSP - not sure if this fits in with that or not?
Thanks,
Gareth.