Support for Static File deployment

[leggetter]

BRJS currently only supports deployments as WAR files. We need to support deployments in simple flat files for deployment to hosting such as GitHub pages or any CDN.

• create an export command for flat-file export
• create a filter so that the bundles can be referred to using their proper extension type, in preparation for flat file export
• Remove WEB-INF (create a J2eeifyCommandPlugin that allows the WEB-INF folder to be made explicit again #90 and modify the app template to no longer add 'WEB-INF.xml' and allow the server to add this in programtically #91)

Related:

• create a flat file export command #289
• "Live" flat file export #530
• change the war command to use flat file export features #348

[thecapdan]

following the merge of the flatfile work e338536 , we have problems opening apps from the dashboard due to locale being appended to the appname, e.g.

url requested: http://localhost:7070/dashboard/#apps/myappen/
should be: http://localhost:7070/dashboard/en/#apps/myapp/

[thecapdan]

issue described above is fixed in latest build

[thecapdan]

testing this is blocked by the build-app -w command not working.

Currently throws an exception:

java.io.FileNotFoundException: C:\Users\danielo\Desktop\TESTING\BladeRunnerJS-v0.8-350-g5e4229e\BladeRunnerJS\apps\brjstodo\mobile-aspect\themes\common\aliases.xml

[andy-berry-dev]

@thecapdan the FileNotFoundException you were seeing should now be gone (fixed in 90e9035).

[thecapdan]

FileNotFoundExcelption fixed + thanks @andyberry88 for sprinkling some magic dust over my test and getting it to pass.

I am now able to get the application running with tomcat.

[thecapdan]

Tested static file deployment running on python http server. Tested with different locales

[leggetter]

Is the WEB-INF folder "no more"?

[thecapdan]

It still exists for newly created apps - but you can have an app without one

[andy-berry-dev]

Until we fix #90 and #91 the WEB-INF needs to stay in the app template.

[leggetter]

I wouldn't class this as complete until we don't have the WEB-INF. Should this issue be reopened or is this requirement tracked elsewhere?

[andy-berry-dev]

@leggetter see above comment (I think we commented at the same time). They are the issues tracking the remaining work.

[dchambers]

We are now much closer to finishing this task as it's currently possible to delete an app's 'WEB-INF' directory and still have it broadly work, but there are some remaining items before this task can be closed:

• Get rid of the SLF4J warnings you currently get if you delete your 'WEB-INF' directory.
• Make running build-app -w myapp cause a 'WEB-INF' to be added if it's been deleted.
• Don't create a 'WEB-INF' directory by default.
• Create a 'j2eeify-app' command that adds in the default 'WEB-INF' directory for those that want to add additional servlets and servlet filters (covered by create a J2eeifyCommandPlugin that allows the WEB-INF folder to be made explicit again #90).
• Add support for deployment properties files (e.g. 'dev.properties', 'uat.properties', 'prod.properties', etc) that make up for the lack of JNDI when deploying statically.

[andy-berry-dev]

Closed in error when I closed other issues for the v0.9 release.

[andy-berry-dev]

The last issues #90 and #91 for this were fixed (and closed) in v0.12.

[dchambers]

@andyberry88, what about my comment:

We are now much closer to finishing this task as it's currently possible to delete an app's 'WEB-INF' directory and still have it broadly work, but there are some remaining items before this task can be closed:

• Get rid of the SLF4J warnings you currently get if you delete your 'WEB-INF' directory.
• Make running build-app -w myapp cause a 'WEB-INF' to be added if it's been deleted.
• Don't create a 'WEB-INF' directory by default.
• Create a 'j2eeify-app' command that adds in the default 'WEB-INF' directory for those that want to add additional servlets and servlet filters (covered by create a J2eeifyCommandPlugin that allows the WEB-INF folder to be made explicit again #90).
• Add support for deployment properties files (e.g. 'dev.properties', 'uat.properties', 'prod.properties', etc) that make up for the lack of JNDI when deploying statically.

Are all of these issues done, or have we created new issues for stuff that hasn't been done yet?

[andy-berry-dev]

@dchambers everything apart from the properties files (the originaly requirements for the issue) have been done. Deployment properties is covered by #749 which is yet to be looked at.

[dchambers]

Thanks @andyberry88 👍