[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236376#comment-16236376 ] ASF subversion and git services commented on KNOX-1049: --- Commit 485520df21c94339066b53af35de13fadc5c632c in knox's branch refs/heads/KNOX-998-Package_Restructuring from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=485520d ] KNOX-1049 - add unit test to gatewayfiltertest > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236377#comment-16236377 ] ASF subversion and git services commented on KNOX-1049: --- Commit 710e784871662a54e0e8994b038a49e735f8be2b in knox's branch refs/heads/KNOX-998-Package_Restructuring from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=710e784 ] KNOX-1049 - Default Service or App Context for Topologies > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236373#comment-16236373 ] ASF subversion and git services commented on KNOX-1049: --- Commit c211d05e98c82d57eb0af61487a76f0ddd99660d in knox's branch refs/heads/KNOX-998-Package_Restructuring from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=c211d05 ] KNOX-1049 - check for null topology to avoid NPE in tests > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224165#comment-16224165 ] ASF subversion and git services commented on KNOX-1049: --- Commit 1ee937071b236909a38dc764db451e65a3225ad6 in knox's branch refs/heads/master from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=1ee9370 ] Merge branch 'master' into KNOX-1049 > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224166#comment-16224166 ] ASF subversion and git services commented on KNOX-1049: --- Commit c211d05e98c82d57eb0af61487a76f0ddd99660d in knox's branch refs/heads/master from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=c211d05 ] KNOX-1049 - check for null topology to avoid NPE in tests > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224167#comment-16224167 ] ASF subversion and git services commented on KNOX-1049: --- Commit 485520df21c94339066b53af35de13fadc5c632c in knox's branch refs/heads/master from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=485520d ] KNOX-1049 - add unit test to gatewayfiltertest > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224164#comment-16224164 ] ASF subversion and git services commented on KNOX-1049: --- Commit f5490414dfb23a0d9a46e96aa904a1cc8c04f3e4 in knox's branch refs/heads/master from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=f549041 ] KNOX-1049 - change BeancConverter for path element > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224163#comment-16224163 ] ASF subversion and git services commented on KNOX-1049: --- Commit 3346d99e361e1dab74fc8774d3089f9049529941 in knox's branch refs/heads/master from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=3346d99 ] KNOX-1049 - marshaling changes > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224168#comment-16224168 ] ASF subversion and git services commented on KNOX-1049: --- Commit 710e784871662a54e0e8994b038a49e735f8be2b in knox's branch refs/heads/master from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=710e784 ] KNOX-1049 - Default Service or App Context for Topologies > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224162#comment-16224162 ] ASF subversion and git services commented on KNOX-1049: --- Commit 222385bf85bb0c234ca5da981f575ee8db0cd2d3 in knox's branch refs/heads/master from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=222385b ] KNOX-1049 - change defaultServicePath to path > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224161#comment-16224161 ] ASF subversion and git services commented on KNOX-1049: --- Commit 3a411555fa9a89965281604c4e56709325abf743 in knox's branch refs/heads/master from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=3a41155 ] KNOX-1049 - Default Service or App Context for Topologies > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224159#comment-16224159 ] ASF subversion and git services commented on KNOX-1049: --- Commit 485520df21c94339066b53af35de13fadc5c632c in knox's branch refs/heads/KNOX-1049 from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=485520d ] KNOX-1049 - add unit test to gatewayfiltertest > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220608#comment-16220608 ] ASF subversion and git services commented on KNOX-1049: --- Commit c211d05e98c82d57eb0af61487a76f0ddd99660d in knox's branch refs/heads/KNOX-1049 from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=c211d05 ] KNOX-1049 - check for null topology to avoid NPE in tests > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220515#comment-16220515 ] ASF subversion and git services commented on KNOX-1049: --- Commit 1ee937071b236909a38dc764db451e65a3225ad6 in knox's branch refs/heads/KNOX-1049 from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=1ee9370 ] Merge branch 'master' into KNOX-1049 > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220504#comment-16220504 ] ASF subversion and git services commented on KNOX-1049: --- Commit 3346d99e361e1dab74fc8774d3089f9049529941 in knox's branch refs/heads/KNOX-1049 from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=3346d99 ] KNOX-1049 - marshaling changes > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220503#comment-16220503 ] ASF subversion and git services commented on KNOX-1049: --- Commit 222385bf85bb0c234ca5da981f575ee8db0cd2d3 in knox's branch refs/heads/KNOX-1049 from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=222385b ] KNOX-1049 - change defaultServicePath to path > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KNOX-1049) Default Service or App Context for Topologies
[ https://issues.apache.org/jira/browse/KNOX-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220505#comment-16220505 ] ASF subversion and git services commented on KNOX-1049: --- Commit f5490414dfb23a0d9a46e96aa904a1cc8c04f3e4 in knox's branch refs/heads/KNOX-1049 from [~lmccay] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=f549041 ] KNOX-1049 - change BeancConverter for path element > Default Service or App Context for Topologies > - > > Key: KNOX-1049 > URL: https://issues.apache.org/jira/browse/KNOX-1049 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Larry McCay > Labels: kip-9 > Fix For: 0.14.0 > > > In order to help reduce the complexity and level of granularity of the UI > related rewrite rules, it would be good to be able to have UIs deployed to > their own topology that has implied context paths. For instance, when > authoring the rewrite rules for something like Ambari, we need to add the > "ambari" path element in front of every relative path. > Coupled with the need to do this and the need to disambiguate a relative url > like images/log.gif between one app another, we end up with a rewrite rule > for every single link in a UI. > So, if we can limit UIs to their own topology then we shouldn't have to add > "ambari" in front of each link in rewrite rules. But in order to match a > topology path in the GatewayFilter we will need to know the missing path > element. > This JIRA is an attempt at coding this into the topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
