|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
This needs some discussion before committing to perform.
Going by https://github.com/angular/angular.js/issues/2762, we need to demonstrate overriding of the root context in JBoss (easy, see: https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Administration_and_Configuration_Guide/Replace_the_Default_Welcome_Web_Application1.html).
But doing so would make users jump through hoops if they want to deploy multiple such AngularJS based apps in a nested directory structure like http://example.com/appA, http://example.com/appB etc.
Finally, we also need a URL rewriting library supported in WFK (or use the url rewriting feature in JBossWeb). This is necessary to ensure that SEO-friendly URLs when sent to the deployed app, do not result in 404 responses.
Note - AngularJS generates such URLs after a user browses to the root page in the Single Page App. It rewrites browser history and changes the location in the location bar to perform such routing. The modified URL is not served by the server; but should this happen, then the server must redirect the user to the root page.