October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7406) DeltaCloud UI does not store cloud type

by Andre Dietisheim (JIRA)

DeltaCloud UI does not store cloud type --------------------------------------- Key: JBIDE-7406 URL: https://jira.jboss.org/browse/JBIDE-7406 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Andre Dietisheim The current implementation of the deltacloud UI does not store the cloud type correctly. It does not pass the type parameter in constructors: class DeltaCloud: public DeltaCloud(String name, String url, String username, String passwd) throws MalformedURLException { this(name, url, username, passwd, null, false, IImageFilter.ALL_STRING, IInstanceFilter.ALL_STRING); ^^^^ } Therefore, when a cloud is edited, a bad type is extracted from the settings (a String "null"). Either the type shall not stored at all and calculated on each connection edit (by querying the server) or it shall be stored and displayed without server query. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7366) Properties Viewer doesn't show keyname for RUNNING instances after refresh or initial start-up

by Jeff Johnston (JIRA)

Properties Viewer doesn't show keyname for RUNNING instances after refresh or initial start-up ---------------------------------------------------------------------------------------------- Key: JBIDE-7366 URL: https://jira.jboss.org/browse/JBIDE-7366 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Beta1 Reporter: Jeff Johnston Fix For: 3.2.0.Beta2 If an instance is running and Deltacloud tools are brought up, the keyname is missing in the Properties viewer. The same occurs if the list of instances is refreshed. The keyname should be shown. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7260) Links in EC2 wizard are linking to the amazone console instead of to the relevant section

by Max Andersen (JIRA)

Links in EC2 wizard are linking to the amazone console instead of to the relevant section ----------------------------------------------------------------------------------------- Key: JBIDE-7260 URL: https://jira.jboss.org/browse/JBIDE-7260 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Reporter: Max Andersen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7284) the connection wizard does not disable the finish button if you change the url to an invalid one

by Andre Dietisheim (JIRA)

the connection wizard does not disable the finish button if you change the url to an invalid one ------------------------------------------------------------------------------------------------ Key: JBIDE-7284 URL: https://jira.jboss.org/browse/JBIDE-7284 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 1) enter name, VALID Url, user and pw 2) correct the Url to get invalid. result: finish-button is enabled expected behavior: finish-button should be disabled -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7307) user should be able to add new cloud connection in the context menu

by Andre Dietisheim (JIRA)

user should be able to add new cloud connection in the context menu ------------------------------------------------------------------- Key: JBIDE-7307 URL: https://jira.jboss.org/browse/JBIDE-7307 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 A user intuitively expects to be able to add a new cloud connection in the context menu of the cloud viewer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7367) Cloud Viewer should only present applicable actions for instances

by Jeff Johnston (JIRA)

Cloud Viewer should only present applicable actions for instances ----------------------------------------------------------------- Key: JBIDE-7367 URL: https://jira.jboss.org/browse/JBIDE-7367 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Jeff Johnston Assignee: Andre Dietisheim Instances have states (e.g. RUNNING, STOPPED, TERMINATED). As well, there is a set of applicable actions as defined by the Deltacloud server (e.g. a RUNNING instance will allow STOP and REBOOT actions whereas a STOPPED instance may allow START and DESTROY). At present, all possible actions are being shown in the right-click menu for an instance. The non-applicable options should either be removed or disabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (RHDS-123) Make sure welcome screen does not conflict with our visual editor on windows and linux

by Max Andersen (JIRA)

Make sure welcome screen does not conflict with our visual editor on windows and linux -------------------------------------------------------------------------------------- Key: RHDS-123 URL: http://jira.jboss.com/jira/browse/RHDS-123 Project: Red Hat Developer Studio Issue Type: Sub-task Components: visualeditor Affects Versions: 1.0.0.beta1 Reporter: Max Andersen Assigned To: Victor Rubezhny Priority: Critical Fix For: 1.0.0.beta2 Sergey V. said that Welcome screens makes our visual editor fail from starting if the welcome screen is implemented in a certain way. Victor please sync up with Sergey on what can and cannot work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7319) Save state of Seam and KB models only at saving Eclipse workspace rather than after each build

by Viacheslav Kabanovich (JIRA)

Save state of Seam and KB models only at saving Eclipse workspace rather than after each build ---------------------------------------------------------------------------------------------- Key: JBIDE-7319 URL: https://jira.jboss.org/browse/JBIDE-7319 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF, Seam Affects Versions: 3.2.0.Beta1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.2.0.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7425) How to ask JBoss Tools not to deploy jaxb-impl-2.1.3.jar?

by Burr Sutter (JIRA)

How to ask JBoss Tools not to deploy jaxb-impl-2.1.3.jar? --------------------------------------------------------- Key: JBIDE-7425 URL: https://jira.jboss.org/browse/JBIDE-7425 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter Attachments: server.log My Spring Travel application fails to deploy via JBDS4 Beta1 to AS6 because of jaxb-impl-2.1.3.jar. Video coming, along with logs and resulting .war Stack trace 15:14:55,475 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to PostClassLoader: name=vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/travel.war state=ClassLoader mode=Manual requiredState=PostClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/travel.war at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.Alpha7] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha7] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.20100911-M5] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.1.0.Alpha1] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59) [:0.1.0.Alpha1] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.1.0.Alpha1] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94) [:0.1.0.Alpha1] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.1.0.Alpha1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_20] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_20] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20] at java.lang.Thread.run(Thread.java:619) [:1.6.0_20] Caused by: java.lang.Error: Error visiting "/C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/travel.war/WEB-INF/lib/jaxb-impl-2.1.3.jar/com/sun/xml/bind/v2/schemagen/XmlSchemaGenerator$Namespace.class" at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:268) [jboss-classloading-vfs.jar:2.2.0.Alpha8] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:407) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:395) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:102) [jboss-classloading-vfs.jar:2.2.0.Alpha8] at org.jboss.deployers.vfs.plugins.classloader.VFSDeploymentClassLoaderPolicyModule.visit(VFSDeploymentClassLoaderPolicyModule.java:181) [:2.2.0.Alpha7] at org.jboss.scanning.plugins.DeploymentUnitScanner.scan(DeploymentUnitScanner.java:111) [:1.0.0.Alpha6] at org.jboss.scanning.spi.helpers.UrlScanner.scan(UrlScanner.java:96) [:1.0.0.Alpha6] at org.jboss.scanning.deployers.ScanningDeployer.deploy(ScanningDeployer.java:90) [:1.0.0.Alpha6] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha7] ... 37 more Caused by: java.lang.RuntimeException: Error visiting resource: VFSResourceContext @ com/sun/xml/bind/v2/schemagen/XmlSchemaGenerator$Namespace.class / BaseClassLoader@1534d8c{vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/travel.war}, visitor: org.jboss.scanning.annotations.plugins.GenericAnnotationVisitor@1d7dfda at org.jboss.scanning.plugins.visitor.IgnoreSetErrorHandler.handleError(IgnoreSetErrorHandler.java:56) [:1.0.0.Alpha6] at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:91) [:1.0.0.Alpha6] at org.jboss.scanning.annotations.plugins.AnnotationsScanningPlugin.visit(AnnotationsScanningPlugin.java:89) [:1.0.0.Alpha6] at org.jboss.scanning.spi.helpers.ScanningPluginWrapper.visit(ScanningPluginWrapper.java:112) [:1.0.0.Alpha6] at org.jboss.classloading.plugins.visitor.FederatedResourceVisitor.visit(FederatedResourceVisitor.java:101) [jboss-classloading.jar:2.2.0.Alpha8] at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:264) [jboss-classloading-vfs.jar:2.2.0.Alpha8] ... 51 more Caused by: java.lang.reflect.GenericSignatureFormatError at sun.reflect.generics.parser.SignatureParser.error(SignatureParser.java:103) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseSimpleClassTypeSignature(SignatureParser.java:262) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignatureSuffix(SignatureParser.java:270) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignature(SignatureParser.java:244) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(SignatureParser.java:228) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseTypeArgument(SignatureParser.java:319) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseTypeArguments(SignatureParser.java:287) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseSimpleClassTypeSignature(SignatureParser.java:260) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignatureSuffix(SignatureParser.java:270) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignature(SignatureParser.java:244) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(SignatureParser.java:228) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseTypeSignature(SignatureParser.java:359) [:1.6.0_20] at sun.reflect.generics.parser.SignatureParser.parseTypeSig(SignatureParser.java:157) [:1.6.0_20] at sun.reflect.generics.repository.FieldRepository.parse(FieldRepository.java:34) [:1.6.0_20] at sun.reflect.generics.repository.FieldRepository.parse(FieldRepository.java:24) [:1.6.0_20] at sun.reflect.generics.repository.AbstractRepository.<init>(AbstractRepository.java:56) [:1.6.0_20] at sun.reflect.generics.repository.FieldRepository.<init>(FieldRepository.java:30) [:1.6.0_20] at sun.reflect.generics.repository.FieldRepository.make(FieldRepository.java:48) [:1.6.0_20] at java.lang.reflect.Field.getGenericInfo(Field.java:85) [:1.6.0_20] at java.lang.reflect.Field.getGenericType(Field.java:223) [:1.6.0_20] at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl$1.run(IntrospectionTypeInfoFactoryImpl.java:202) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl$1.run(IntrospectionTypeInfoFactoryImpl.java:190) [jboss-reflect.jar:2.2.0.Alpha9] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_20] at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getFields(IntrospectionTypeInfoFactoryImpl.java:189) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredFields(ClassInfoImpl.java:432) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.scanning.plugins.visitor.ClassHierarchyResourceVisitor.handleClass(ClassHierarchyResourceVisitor.java:81) [:1.0.0.Alpha6] at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.doVisit(ReflectResourceVisitor.java:108) [:1.0.0.Alpha6] at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:86) [:1.0.0.Alpha6] ... 55 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7413) "Generate Entities" gets frozen

by Juergen Zimmermann (JIRA)

"Generate Entities" gets frozen ------------------------------- Key: JBIDE-7413 URL: https://jira.jboss.org/browse/JBIDE-7413 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.Beta1 Reporter: Juergen Zimmermann Assignee: Max Andersen When I want to generate Entity classes via "JPA Tools" > "Generate Entities from Tables", the wizard's last window gets frozen. There is no message in the log file. I'll attach a screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
5
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 2010