October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15830) openshift-java-client incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15830: ------------------------------------- Fix Version/s: 4.1.1.Beta1 > openshift-java-client incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15830 > URL: https://issues.jboss.org/browse/JBIDE-15830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Brenton Leanhardt > Assignee: Andre Dietisheim > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin. > In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling. > You can see this for details: > https://github.com/openshift/origin-server/blob/master/documentation/arch... > In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45). -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15499: --------------------------------------- Radim, Rastislav, I suppose you have tried to drop the URL into an empty editor area. The editor area has its drop target that opens an editor. There is no easy way to add our target to the editor area. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=248462 The issue happens on Linux and Windows. The difference is that Windows doesn't throw an exception. If you drop the URL to the toolbar area, menu area, JBoss Central editor, it will work correctly. Max, Nick, Do you mean I need to make a fix/workaround for this issue? > Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15499 > URL: https://issues.jboss.org/browse/JBIDE-15499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds. > Similar to eclipse marketplace for marketplace urls something like: > * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or > * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra... > would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e" > This would allow drag'n'drop install from html docs. > Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15829) CLONE - Incorrect Constraint Problem for JSF composite component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15829?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15829: ---------------------------------------- We fixed this particular problem for JSF composite component. The main problem with internal XModel validation is described in JBIDE-8445 > CLONE - Incorrect Constraint Problem for JSF composite component > ---------------------------------------------------------------- > > Key: JBIDE-15829 > URL: https://issues.jboss.org/browse/JBIDE-15829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, jsf > Affects Versions: 4.1.0.Final > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.Alpha1 > > > First at all we must have a preference page where we can disable this validation. > There should not be any validation which is imposible to disable. > Every validation problem should have a default quick fix which opens the corresponding preference page and disable this validation rule. > We have such preferences/quick fixes for our validation that extends common validation framework. > But this one is a part of XModel validation (https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/...). -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15826) Incorrect Constraint Problem for JSF composite component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15826?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15826: ---------------------------------------- We fixed this particular problem for JSF composite component. The main problem with internal XModel validation is described in JBIDE-8445 > Incorrect Constraint Problem for JSF composite component > -------------------------------------------------------- > > Key: JBIDE-15826 > URL: https://issues.jboss.org/browse/JBIDE-15826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, jsf > Affects Versions: 4.1.0.Final > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: respin-b > Fix For: 4.1.1.Beta1 > > > First at all we must have a preference page where we can disable this validation. > There should not be any validation which is imposible to disable. > Every validation problem should have a default quick fix which opens the corresponding preference page and disable this validation rule. > We have such preferences/quick fixes for our validation that extends common validation framework. > But this one is a part of XModel validation (https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/...). -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8445) Do not create markers at internal attribute validation by XModel

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8445?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-8445: ---------------------------------- Issue Type: Bug (was: Feature Request) > Do not create markers at internal attribute validation by XModel > ---------------------------------------------------------------- > > Key: JBIDE-8445 > URL: https://issues.jboss.org/browse/JBIDE-8445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 3.2.0.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > This framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. > It is ok to have some internal validation for model consistency, but it should not interfere with the standard framework. Markers should be created by delegates of the validation job. > Now, trees and forms of JBoss Tools editors recognize markers created by XModel and display them. We may try to replace this by > 1) either to be able to bind any markers with model objects > Profit: that would immensely improve displaying problems in tree/form in JBoss Tools editors > Possible Minus: It may be very resource consuming; > 2) or to store the found problems as internal objects, not as markers, and refactor editors/views to displaying them > Profit: Preserve feature at the current level > Minus: Developing internal framework that cannot be reused; > 3) or just drop it > Profit: No need for development, just do not create markers. > Minus: Problems in tree/form in JBoss Tools editors will not be displayed. Also, other possible unexpected aftermath should be addressed to. > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8445) Do not create markers at internal attribute validation by XModel

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8445?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-8445: ---------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) > Do not create markers at internal attribute validation by XModel > ---------------------------------------------------------------- > > Key: JBIDE-8445 > URL: https://issues.jboss.org/browse/JBIDE-8445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 3.2.0.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > > This framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. > It is ok to have some internal validation for model consistency, but it should not interfere with the standard framework. Markers should be created by delegates of the validation job. > Now, trees and forms of JBoss Tools editors recognize markers created by XModel and display them. We may try to replace this by > 1) either to be able to bind any markers with model objects > Profit: that would immensely improve displaying problems in tree/form in JBoss Tools editors > Possible Minus: It may be very resource consuming; > 2) or to store the found problems as internal objects, not as markers, and refactor editors/views to displaying them > Profit: Preserve feature at the current level > Minus: Developing internal framework that cannot be reused; > 3) or just drop it > Profit: No need for development, just do not create markers. > Minus: Problems in tree/form in JBoss Tools editors will not be displayed. Also, other possible unexpected aftermath should be addressed to. > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8445) Do not create markers at internal attribute validation by XModel

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8445?page=com.atlassian.jira.plugin... ] Viacheslav Kabanovich updated JBIDE-8445: ----------------------------------------- Description: This framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. It is ok to have some internal validation for model consistency, but it should not interfere with the standard framework. Markers should be created by delegates of the validation job. Now, trees and forms of JBoss Tools editors recognize markers created by XModel and display them. We may try to replace this by 1) either to be able to bind any markers with model objects Profit: that would immensely improve displaying problems in tree/form in JBoss Tools editors Possible Minus: It may be very resource consuming; 2) or to store the found problems as internal objects, not as markers, and refactor editors/views to displaying them Profit: Preserve feature at the current level Minus: Developing internal framework that cannot be reused; 3) or just drop it Profit: No need for development, just do not create markers. Minus: Problems in tree/form in JBoss Tools editors will not be displayed. Also, other possible unexpected aftermath should be addressed to. was:Besides, this framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. > Do not create markers at internal attribute validation by XModel > ---------------------------------------------------------------- > > Key: JBIDE-8445 > URL: https://issues.jboss.org/browse/JBIDE-8445 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 3.2.0.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > This framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. > It is ok to have some internal validation for model consistency, but it should not interfere with the standard framework. Markers should be created by delegates of the validation job. > Now, trees and forms of JBoss Tools editors recognize markers created by XModel and display them. We may try to replace this by > 1) either to be able to bind any markers with model objects > Profit: that would immensely improve displaying problems in tree/form in JBoss Tools editors > Possible Minus: It may be very resource consuming; > 2) or to store the found problems as internal objects, not as markers, and refactor editors/views to displaying them > Profit: Preserve feature at the current level > Minus: Developing internal framework that cannot be reused; > 3) or just drop it > Profit: No need for development, just do not create markers. > Minus: Problems in tree/form in JBoss Tools editors will not be displayed. Also, other possible unexpected aftermath should be addressed to. > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15830) openshift-java-client incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin

by Brenton Leanhardt (JIRA)

Brenton Leanhardt created JBIDE-15830: ----------------------------------------- Summary: openshift-java-client incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin Key: JBIDE-15830 URL: https://issues.jboss.org/browse/JBIDE-15830 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Brenton Leanhardt OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin. In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling. You can see this for details: https://github.com/openshift/origin-server/blob/master/documentation/arch... In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45). -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8445) Do not create markers at internal attribute validation by XModel

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8445?page=com.atlassian.jira.plugin... ] Viacheslav Kabanovich updated JBIDE-8445: ----------------------------------------- Summary: Do not create markers at internal attribute validation by XModel (was: Add preference disabling attribute validation in JBoss Tools XML editor) > Do not create markers at internal attribute validation by XModel > ---------------------------------------------------------------- > > Key: JBIDE-8445 > URL: https://issues.jboss.org/browse/JBIDE-8445 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 3.2.0.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > Besides, this framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15829) CLONE - Incorrect Constraint Problem for JSF composite component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15829?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15829: ----------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) (was: 4.1.1.Beta1) > CLONE - Incorrect Constraint Problem for JSF composite component > ---------------------------------------------------------------- > > Key: JBIDE-15829 > URL: https://issues.jboss.org/browse/JBIDE-15829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, jsf > Affects Versions: 4.1.0.Final > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.Alpha1 > > > First at all we must have a preference page where we can disable this validation. > There should not be any validation which is imposible to disable. > Every validation problem should have a default quick fix which opens the corresponding preference page and disable this validation rule. > We have such preferences/quick fixes for our validation that extends common validation framework. > But this one is a part of XModel validation (https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/...). -- 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

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2013