November 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13115) Connection dialog won't close after creating connection with different server

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-13115: -------------------------------------- Summary: Connection dialog won't close after creating connection with different server Key: JBIDE-13115 URL: https://issues.jboss.org/browse/JBIDE-13115 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.CR1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Fix For: 4.0.0.CR2 See the screencast: [^out.ogv] -- 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

13 years, 5 months

4
11
0 / 0

[JBoss JIRA] (JBIDE-12887) JAX-RS should not analyse jars in the project's classpath

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12887: ------------------------------------- Summary: JAX-RS should not analyse jars in the project's classpath Key: JBIDE-12887 URL: https://issues.jboss.org/browse/JBIDE-12887 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.Beta1 I haven't worked out when :-( I'll try to reproduce it now -- 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

13 years, 5 months

3
19
0 / 0

[JBoss JIRA] (JBIDE-13118) Port Forwarding - OK Button

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-13118: -------------------------------------- Summary: Port Forwarding - OK Button Key: JBIDE-13118 URL: https://issues.jboss.org/browse/JBIDE-13118 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.Beta1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 4.0.0.CR2 Attachments: port.png Wrong alignment of the 'OK' button, as in JBIDE-13072. !port.png|thumbnail! -- 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

13 years, 5 months

3
15
0 / 0

[JBoss JIRA] (JBIDE-12935) Changing @Path value on JAX-RS Resource reorders the endpoints in the Project explorer view

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12935: ------------------------------------- Summary: Changing @Path value on JAX-RS Resource reorders the endpoints in the Project explorer view Key: JBIDE-12935 URL: https://issues.jboss.org/browse/JBIDE-12935 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Xavier Coulon -- 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

13 years, 5 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-13140) remote start of as7.0.1 fails because it is bound to localnost and so web poller does not work

by Martin Malina (JIRA)

Martin Malina created JBIDE-13140: ------------------------------------- Summary: remote start of as7.0.1 fails because it is bound to localnost and so web poller does not work Key: JBIDE-13140 URL: https://issues.jboss.org/browse/JBIDE-13140 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 4.0.0.CR1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.1.x JBIDE-13045 fixed the problem that -b was used for remote AS 7.0.1 which doesn't support it. But now the problem is that without -b the server is always deployed to localhost. So the web poller cannot work obviously. So unless you expose management port and use JBoss 7 management start poller you cannot really start the server properly - it starts but doesn't recognize the startup and when timeout is reached it shows an error. Now how do we solve this? Is it even worth solving? ;) We could say that the workaround is to always use the as7 management (if that works for 7.0.1 at all). -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-13033) When server editor is closed and opened Deployment tab is enabled even if it should not

by Martin Malina (JIRA)

Martin Malina created JBIDE-13033: ------------------------------------- Summary: When server editor is closed and opened Deployment tab is enabled even if it should not Key: JBIDE-13033 URL: https://issues.jboss.org/browse/JBIDE-13033 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.0.0.Beta2 Environment: JBT 4.0.0.Beta2 B43 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.0.0.CR1 Not sure how you control the disabling of the Deployment tab, but it doesn't always work correctly. When it's disabled and you reopen (close&open) the server editor it is enabled again. Also the comment at the top of the Deployment tab says: "Settings on this page may only be modified if the server has 0 modules and is fully synchronized." - this is not totally accurate - should have something like: "or the server is stopped" -- 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

13 years, 5 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12818) WS features are not dependent on as feature any more

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12818: ----------------------------------------- Summary: WS features are not dependent on as feature any more Key: JBIDE-12818 URL: https://issues.jboss.org/browse/JBIDE-12818 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 4.0.0.Alpha2 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 4.0.0.Beta1 JAX-RS tools and Web Services tools features are not longer dependent on AS feature as they used to before. To fully use these two features you have to install AS feature as well. -- 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

13 years, 5 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-12918) Cannot deploy archive on the server

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12918: ----------------------------------------- Summary: Cannot deploy archive on the server Key: JBIDE-12918 URL: https://issues.jboss.org/browse/JBIDE-12918 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 4.0.0.Beta1 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Priority: Blocker Fix For: 4.0.0.Beta1, 4.0.x -- 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

13 years, 5 months

5
35
0 / 0

[JBoss JIRA] (JBIDE-13153) Wrong tag names in JSF pages does not display warnings or errors on Eclipse editor

by Gustavo Gomes (JIRA)

Gustavo Gomes created JBIDE-13153: ------------------------------------- Summary: Wrong tag names in JSF pages does not display warnings or errors on Eclipse editor Key: JBIDE-13153 URL: https://issues.jboss.org/browse/JBIDE-13153 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.1 Environment: Windows 7 64 Bits, JRE 1.6.0_26, Eclipse Indigo (3.7.2), JBoss Tools 3.3.1 Reporter: Gustavo Gomes Assignee: Yahor Radtsevich Priority: Minor I'm working in a project migration to provide JSF 2.0 features. In this case, I'm using Eclipse Ingido as IDE and the JBoss Tools plugin. The project uses the JBoss Seam 2.3.0.Final with RichFaces 4.2.2.Final and will be deployed in the JBoss AS 7.1.1.Final. When I try to migrate JSF pages written using JSF 1.2 and RichFaces 3.3.3.Final to the newest version of these libraries, the JBoss Tools HTML Editor in Eclipse does not display any warnings or errors in the Problems tab for wrong element names or attribute names. Below follow an example JSF page: <ui:define name="body"> <div class="actionButtons"> <h:botton></h:botton> <s:button nothing="nothing" view="/GrupoEdit.xhtml" id="create" propagation="none" value="Criar grupo"> <f:param name="grupoId" /> </s:button> </div> ... </ui:define> In example, the tag <h:botton> does not exists in taglibs nor the attribute nothing in the <s:button> tag. It is already expected that the component of the plugin does not validate this situation? -- 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

13 years, 5 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-13097) test failure in org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess (from org.jboss.tools.common.el.core.test.CommonELAllTests)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13097: ---------------------------------- Summary: test failure in org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess (from org.jboss.tools.common.el.core.test.CommonELAllTests) Key: JBIDE-13097 URL: https://issues.jboss.org/browse/JBIDE-13097 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Alexey Kazakov Priority: Blocker Fix For: 4.0.0.CR2 {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--base/lastCompletedBuild/testReport/org.jboss.tools.common.el.core.test/ELParserTest/testMultiThreadAccess/} Regression org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess (from org.jboss.tools.common.el.core.test.CommonELAllTests) Failing for the past 1 build (Since Unstable#31 ) Error Message: expected:<9990> but was:<9989> Stacktrace junit.framework.AssertionFailedError: expected:<9990> but was:<9989> at junit.framework.Assert.fail(Assert.java:50) at junit.framework.Assert.failNotEquals(Assert.java:287) at junit.framework.Assert.assertEquals(Assert.java:67) at junit.framework.Assert.assertEquals(Assert.java:199) at junit.framework.Assert.assertEquals(Assert.java:205) at org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess(ELParserTest.java:429) {code} -- 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

13 years, 5 months

5
7
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 November 2012