[
https://issues.apache.org/jira/browse/KNOX-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141812#comment-15141812
]
Larry McCay commented on KNOX-670:
----------------------------------
Due to the nature of our API and inparticular our URLs, applications need to do
some form of the following:
1. code to a particular topology assumption "gateway/sandbox/webhdfs/v1"
2. code to the default topology "webhdfs/v1"
3. have some sort of configuration to indicate which to use
4. have some user input within the application that allows them to choose the
topology
In the knoxplorer sample, I use a topology query parameter to override the
default of "gateway/sandbox/v1".
If were to deploy applications like this within the context of the topology
that they are intended to use then we can combine that deployment time context
with option #3 above to inject the knowledge of each topology it is deployed
within. This would probably require the deployment machinery/contributor type
components to add additional config to a deployed war within data/deployments
that is a child of the overall topology war. Resulting in a war per "instance"
of the app across topologies.
It would make for an app programming model with built-in topology awareness
(really just URL discovery).
> Knox Should be able to Host Simple Web Apps
> -------------------------------------------
>
> Key: KNOX-670
> URL: https://issues.apache.org/jira/browse/KNOX-670
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Kevin Minder
> Fix For: 0.9.0
>
> Attachments: KNOX-670_001.patch, KNOX-670_002.patch
>
>
> I think that we need the ability to serve up arbitrary web app resources.
> Given a conf/applications along side conf/topologies, we should be able to
> spin up a simple application that can be used as a central login facility
> with KnoxSSO, a management UI or any number of simple applications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
