April 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10164) Seam UI test failure

by Alexey Kazakov (Created) (JIRA)

Seam UI test failure -------------------- Key: JBIDE-10164 URL: https://issues.jboss.org/browse/JBIDE-10164 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 {code} Failed tests: testAddComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testRenameComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testDeleteComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testAddComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testRenameComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testDeleteComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Tests in error: testFlatSeamPackages(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testHierarchicalSeamPackages(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Tests run: 72, Failures: 6, Errors: 2, Skipped: 0, Time elapsed: 564.94 sec <<< FAILURE! testAddComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 2.336 sec <<< FAILURE! junit.framework.AssertionFailedError: Seam model is not updated, expected package 'myPackage' is not found in tree at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testAddComponentInXmlFile(SeamComponentsViewTest.java:128) testRenameComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 0.542 sec <<< FAILURE! junit.framework.AssertionFailedError: Expected package 'myPackage' was not found it tree at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testRenameComponentInXmlFile(SeamComponentsViewTest.java:148) testDeleteComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 0.555 sec <<< FAILURE! junit.framework.AssertionFailedError: Package "myNewPackage" not found! at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testDeleteComponentInXmlFile(SeamComponentsViewTest.java:216) testAddComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 2.066 sec <<< FAILURE! junit.framework.AssertionFailedError: Package "demo" not found! at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testAddComponentInClass(SeamComponentsViewTest.java:286) testRenameComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 1.055 sec <<< FAILURE! junit.framework.AssertionFailedError: Package "demo" not found! at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testRenameComponentInClass(SeamComponentsViewTest.java:304) testDeleteComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 0.673 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at junit.framework.Assert.assertNotNull(Assert.java:207) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testDeleteComponentInClass(SeamComponentsViewTest.java:359) testFlatSeamPackages(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 1.679 sec <<< ERROR! java.lang.NullPointerException at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testFlatSeamPackages(SeamComponentsViewTest.java:418) testHierarchicalSeamPackages(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 1.565 sec <<< ERROR! java.lang.NullPointerException at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testHierarchicalSeamPackages(SeamComponentsViewTest.java:454) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-9857) Openshift Express: provide possibility to request with a custom user agent string so that we can identify request done by our tooling

by Andre Dietisheim (Created) (JIRA)

Openshift Express: provide possibility to request with a custom user agent string so that we can identify request done by our tooling ------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9857 URL: https://issues.jboss.org/browse/JBIDE-9857 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 We want to be able to track requests our tooling does compared to requests that are done by the web gui. We therefore need to provide the capability to supply a custom user agent to the openshift express service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
13
0 / 0

[JBoss JIRA] Created: (JBIDE-9525) PublishCopyUtil#copyFile throws an Exception but it's impl catches it and returns an IStatus instead

by Andre Dietisheim (JIRA)

PublishCopyUtil#copyFile throws an Exception but it's impl catches it and returns an IStatus instead ---------------------------------------------------------------------------------------------------- Key: JBIDE-9525 URL: https://issues.jboss.org/browse/JBIDE-9525 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.x see https://source.jboss.org/cru/REV-JBIDE-4/#c79 PublishCopyUtil#copyFile should either throw Exceptions or return status objects. The current impl where exceptions are declared in the method signature but catched in the impl makes no sense. We have to decide what strategy to take (either throw or catch and return status). {code} private IStatus copyFile(InputStream in, IPath to, long ts, IModuleFile mf) throws CoreException { File tempFile = null; try { File file = to.toFile(); tempFile = writeToTempFile(in, to); moveTempFile(tempFile, file); if (ts != IResource.NULL_STAMP && ts != 0) file.setLastModified(ts); } catch (CoreException e) { throw e; } catch (Exception e) { IPath path = mf.getModuleRelativePath().append(mf.getName()); return new Status(IStatus.ERROR, ServerPlugin.PLUGIN_ID, IEventCodes.JST_PUB_FAIL, NLS.bind(Messages.errorCopyingFile, path.toOSString(), e.getLocalizedMessage()), null); } finally { if (tempFile != null && tempFile.exists()) tempFile.deleteOnExit(); try { if (in != null) in.close(); } catch (Exception ex) { // ignore } } return null; } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-9889) Openshift Express: when we import an openshift express project to the local workspace, we have to make sure the ssh public key is listed in the private keys in the preferences

by Andre Dietisheim (Created) (JIRA)

Openshift Express: when we import an openshift express project to the local workspace, we have to make sure the ssh public key is listed in the private keys in the preferences ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9889 URL: https://issues.jboss.org/browse/JBIDE-9889 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 When the user imports an openshift app to the local workspace, the remote git repo is cloned locally. In order to be able to do this, you'd need to have your ssh public key, that he used when creating the openshift domain, listed in the ssh private keys in the eclipse preferences (General->Network Connection->SSH2->Private keys -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9076) Port text field in server editor should not allow you to enter alphanumeric values

by Andre Dietisheim (JIRA)

Port text field in server editor should not allow you to enter alphanumeric values ---------------------------------------------------------------------------------- Key: JBIDE-9076 URL: https://issues.jboss.org/browse/JBIDE-9076 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.x Attachments: invalid-port-value.png, saved-even-though-invalid.png The server editor allows you to enter alphanumeric aka invalid port values. If you then try to save the editor, you'll get an error that tells you that the editor could not be saved because of invalid values. !invalid-port-value.png! The editor gets saved though - the editor gets clean even though the value is still present in the editor. !saved-even-though-invalid.png! We can avoid this easily by disallowing alphanumeric values while typing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9326) Replace Delegates-mapping by proper solution

by Andre Dietisheim (JIRA)

Replace Delegates-mapping by proper solution -------------------------------------------- Key: JBIDE-9326 URL: https://issues.jboss.org/browse/JBIDE-9326 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.x We implementation our own delegation on top of the wtp delegation because WTP is not flexible enough for our needs. We did not want to have separate servers for remote/local behavior and we therefore provide a single server which may be switch to local/remote behavior and delegates to appropriate components. The components are currently mapped to local/remote behaviors on behalf of static maps: * DelegatingJBoss7ServerBehavior#addDelegateMapping * DelegatingJBoss7ServerBehavior#getDelegateMap * DelegatingServerBehavior#addDelegateMapping * DelegatingServerBehavior#getDelegate etc. This solution works but is far from optimal since all those statics make subclassing pretty hard. Furthermore it basically does what the platform provides by extensions and osgi services. We should replace the current implementation by those platform mechanisms. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-9845) Unify publish / behaviour / launch APIs for AS/Servers

by Rob Stryker (Created) (JIRA)

Unify publish / behaviour / launch APIs for AS/Servers ------------------------------------------------------ Key: JBIDE-9845 URL: https://issues.jboss.org/browse/JBIDE-9845 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.M4 The APIs for these things are not unified, spread through manual class calls and extension points. This needs to be collected in preparation for adding a third behaviour type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
5
0 / 0

[JBoss JIRA] (JBIDE-10002) run as on jsf javaee6-webapp result in wrong url

by Max Rydahl Andersen (Created) (JIRA)

run as on jsf javaee6-webapp result in wrong url ------------------------------------------------ Key: JBIDE-10002 URL: https://issues.jboss.org/browse/JBIDE-10002 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers, maven Affects Versions: 3.3.0.M4 Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 Doing run on server on for index.html result in localhost:8080/appname/faces/index.html where it should be localhost:8080/appname/index.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

7
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8458) Mavenized Seam EAR Project can't be deployed to JBoss AS 6.0.0.Final

by Snjezana Peco (JIRA)

Mavenized Seam EAR Project can't be deployed to JBoss AS 6.0.0.Final -------------------------------------------------------------------- Key: JBIDE-8458 URL: https://issues.jboss.org/browse/JBIDE-8458 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M1 If you create a mavenized Seam EAR project using the New Seam Web Project wizard, it will create application.xml that contains the following entries: ... <module> <ejb>/test-ejb.jar</ejb> </module> <module> <ejb>/jboss-seam-2.2.1.Final.jar</ejb> </module> <module> <web> <web-uri>/test.war</web-uri> <context-root>test</context-root> </web> </module> ... Such a project can be deployed to JBoss AS <= 6.0, but can't to JBoss AS 6.0.0 A workaround is to open the EAR's pom.xml and remove the bundleDir element for ejb and web modules. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-10189) AS7 management port not automatically detected

by Nicklas Karlsson (Created) (JIRA)

AS7 management port not automatically detected ---------------------------------------------- Key: JBIDE-10189 URL: https://issues.jboss.org/browse/JBIDE-10189 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Nicklas Karlsson Assignee: Rob Stryker The location of the management interface port recently changed in standalone.xml so the server adapter can no longer parse the port automatically -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2012