November 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-8741) Toggle/add/remove block comment actions are missing from the menu while editing JSP

by Yahor Radtsevich (JIRA)

Toggle/add/remove block comment actions are missing from the menu while editing JSP ----------------------------------------------------------------------------------- Key: JBIDE-8741 URL: https://issues.jboss.org/browse/JBIDE-8741 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Reporter: Yahor Radtsevich Assignee: Alexey Kazakov Fix For: 3.3.x Toggle/add/remove are removed from the menu due to recent API changes in WTP 3.3. It seems that to enable this functionality, the {{org.eclipse.wst.sse.comments}} context and the {{org.eclipse.wst.sse.ui.commentingStrategy}} extension point should be used. Also see JBIDE-8686 and [related WTP bug|https://bugs.eclipse.org/86520]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9296) JSF 2: Add to VPE Open On support of annotated managed beans

by Yahor Radtsevich (JIRA)

JSF 2: Add to VPE Open On support of annotated managed beans ------------------------------------------------------------ Key: JBIDE-9296 URL: https://issues.jboss.org/browse/JBIDE-9296 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.x We need to ensure that Open On functionality of VPE will work with JSF 2 annotated beans. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10224) JBossAS 7.1 cannot be launched

by Juergen Zimmermann (Created) (JIRA)

JBossAS 7.1 cannot be launched ------------------------------ Key: JBIDE-10224 URL: https://issues.jboss.org/browse/JBIDE-10224 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Juergen Zimmermann Assignee: Rob Stryker I just installed JBossAS 7.1.Beta1. However, the server start is hanging in an endless loop (see below). Maybe it's due to the new security mechanism in standalone/configuration/mgmt-users.properties. Console output: 13:55:42,836 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.Beta1 "Tesla" started in 2862ms - Started 143 of 206 services (60 services are passive or on-demand) 13:55:45,116 ERROR [org.jboss.remoting.remote] (Remoting "iwi-w-ziju01-c:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 001bd732 to /127.0.0.1:53864 // from now on: endless loop of the preceeding line -- 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

14 years, 4 months

17
32
0 / 0

[JBoss JIRA] (JBIDE-10103) JSF 2 composite components should be loaded from Java source folders

by Viacheslav Kabanovich (Created) (JIRA)

JSF 2 composite components should be loaded from Java source folders -------------------------------------------------------------------- Key: JBIDE-10103 URL: https://issues.jboss.org/browse/JBIDE-10103 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, jsp/jsf/xml source editing Affects Versions: 3.2.1.M1 Environment: JSF2.0, maven 3. Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 Attachments: tagsuggestion-testapp.rar I have a composite component in a jars META-INF folder, it has been stored on META-INF/resouces/components/seamfaces (nested directories). adding this jar as a dependency it should be possible to use this component on a JSF2 application. In this version jbosstools validates the composite components existense but it does not provide code completion to it. related to: https://issues.jboss.org/browse/JBIDE-8275 -- 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

14 years, 4 months

7
6
0 / 0

[JBoss JIRA] (JBIDE-10149) RichFaces palette is missing components

by Pavol Pitonak (Created) (JIRA)

RichFaces palette is missing components --------------------------------------- Key: JBIDE-10149 URL: https://issues.jboss.org/browse/JBIDE-10149 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M4 Reporter: Pavol Pitonak Assignee: Alexey Kazakov RichFaces 4 palette is missing the following components: * rich:notify * rich:notifyMessage * rich:notifyMessages * rich:notifyStack -- 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

14 years, 4 months

7
9
0 / 0

[JBoss JIRA] (JBIDE-10161) Web Verification rules are run derived folders

by Jesper Skov (Created) (JIRA)

Web Verification rules are run derived folders ---------------------------------------------- Key: JBIDE-10161 URL: https://issues.jboss.org/browse/JBIDE-10161 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.3.0.M4 Environment: Windows XP, Eclipse Indigo SR1 Reporter: Jesper Skov We have a "build" output folder in all our projects used for parallel builds by Gradle. This folder is marked as Derived. JBoss Tools Verification rules are run on the contents of this folder. This wastes CPU cycles (degraded user experience due to slower feedback), and shows duplet validation errors (causing confusion). This is probably similar in nature to https://issues.jboss.org/browse/JBIDE-784 It would be nice, if Derived folders could be excluded from the verification run. -- 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

14 years, 4 months

7
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9320) template.xhtml does not work for EPP 5.1 Seam Portlet Applications

by Gary Lamperillo (JIRA)

template.xhtml does not work for EPP 5.1 Seam Portlet Applications ------------------------------------------------------------------ Key: JBIDE-9320 URL: https://issues.jboss.org/browse/JBIDE-9320 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Gary Lamperillo this may be related to https://issues.jboss.org/browse/JBPAPP-4259 However, this issue occurs in JBDS 4.0 and EPP 5.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
12
0 / 0

[JBoss JIRA] (JBIDE-10008) Null Pointer Exception in XModelEntityImpl.getRequiredChildren() method

by Daniel Azarov (Created) (JIRA)

Null Pointer Exception in XModelEntityImpl.getRequiredChildren() method ----------------------------------------------------------------------- Key: JBIDE-10008 URL: https://issues.jboss.org/browse/JBIDE-10008 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.M3 Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 java.lang.NullPointerException at org.jboss.tools.common.meta.impl.XModelEntityImpl.getRequiredChildren(XModelEntityImpl.java:386) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.loadChildren(XModelObjectLoaderUtil.java:309) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoaderUtil.loadChildren(FileSystemsLoader.java:272) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.load(XModelObjectLoaderUtil.java:98) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.loadChildren(XModelObjectLoaderUtil.java:320) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoaderUtil.loadChildren(FileSystemsLoader.java:272) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.load(XModelObjectLoaderUtil.java:98) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.loadChildren(XModelObjectLoaderUtil.java:320) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoaderUtil.loadChildren(FileSystemsLoader.java:272) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.load(XModelObjectLoaderUtil.java:98) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.load(XModelObjectLoaderUtil.java:688) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.load(FileSystemsLoader.java:95) at org.jboss.tools.common.model.loaders.impl.RootLoaderImpl.load(RootLoaderImpl.java:33) at org.jboss.tools.common.model.impl.XModelImpl.load(XModelImpl.java:410) at org.jboss.tools.common.model.XModelFactory.createInstance(XModelFactory.java:36) at org.jboss.tools.common.model.XModelFactory.getModel(XModelFactory.java:29) at org.jboss.tools.common.model.project.ModelNature.createProject(ModelNature.java:134) at org.jboss.tools.common.model.project.ModelNature.setProject(ModelNature.java:64) at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) at org.jboss.tools.common.model.util.EclipseResourceUtil.getModelNature(EclipseResourceUtil.java:264) at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:36) at org.jboss.tools.seam.internal.core.scanner.lib.ClassPath.init(ClassPath.java:65) at org.jboss.tools.seam.internal.core.SeamProject.setProject(SeamProject.java:267) at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) at org.jboss.tools.seam.core.SeamCorePlugin.getSeamProject(SeamCorePlugin.java:206) at org.jboss.tools.seam.internal.core.validation.SeamProjectPropertyValidator.validateProject(SeamProjectPropertyValidator.java:156) at org.jboss.tools.seam.internal.core.validation.SeamProjectPropertyValidator.validateInJob(SeamProjectPropertyValidator.java:132) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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

14 years, 4 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10111) ConcurrentModificationException after closing Seam War project

by Denis Golovin (Created) (JIRA)

ConcurrentModificationException after closing Seam War project -------------------------------------------------------------- Key: JBIDE-10111 URL: https://issues.jboss.org/browse/JBIDE-10111 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.Beta1 Reporter: Denis Golovin Assignee: Alexey Kazakov Now Test case in steps to reproduce fails on last step with bunch of exceptions. First is throws exception {noformat}org.eclipse.core.internal.resources.ResourceException: Resource '/seam22hib' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:150) at org.eclipse.core.internal.resources.Resource.findMarkers(Resource.java:1007) at org.jboss.tools.jst.web.kb.internal.validation.KBValidator.findBuilderOrderMarker(KBValidator.java:129) at org.jboss.tools.jst.web.kb.internal.validation.KBValidator.validateBuilderOrder(KBValidator.java:89) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateBuilderOrder(ELValidator.java:482) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.shouldValidate(ELValidator.java:468) at org.jboss.tools.common.validation.ValidationContext.init(ValidationContext.java:86) at org.jboss.tools.common.validation.ValidationContext.<init>(ValidationContext.java:42) at org.jboss.tools.common.validation.ContextValidationHelper.getValidationContextManager(ContextValidationHelper.java:161) at org.jboss.tools.common.validation.ContextValidationHelper.getValidationContextManager(ContextValidationHelper.java:153) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:65) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){noformat} then {noformat}java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:810) at java.util.HashMap$KeyIterator.next(HashMap.java:845) at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.syncProcessedPaths(AbstractClassPathMonitor.java:110) at org.jboss.tools.seam.internal.core.scanner.lib.ClassPath.process(ClassPath.java:73) at org.jboss.tools.seam.internal.core.scanner.lib.ClassPath.build(ClassPath.java:178) at org.jboss.tools.seam.internal.core.SeamProject.build(SeamProject.java:371) at org.jboss.tools.seam.core.SeamCoreBuilder.build(SeamCoreBuilder.java:50) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){noformat} and finally {noformat}java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:810) at java.util.HashMap$KeyIterator.next(HashMap.java:845) at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.syncProcessedPaths(AbstractClassPathMonitor.java:110) at org.jboss.tools.seam.internal.core.scanner.lib.ClassPath.process(ClassPath.java:73) at org.jboss.tools.seam.internal.core.scanner.lib.ClassPath.build(ClassPath.java:178) at org.jboss.tools.seam.internal.core.SeamProject.build(SeamProject.java:371) at org.jboss.tools.seam.core.SeamCoreBuilder.build(SeamCoreBuilder.java:50) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){noformat} -- 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

14 years, 4 months

7
10
0 / 0

[JBoss JIRA] (JBIDE-10214) JBoss Perspective: Close outline and palette

by Burr Sutter (Created) (JIRA)

JBoss Perspective: Close outline and palette -------------------------------------------- Key: JBIDE-10214 URL: https://issues.jboss.org/browse/JBIDE-10214 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Attachments: Screen Shot 2011-11-22 at 11.06.56 AM.png The Outline and Palette take up valuable real estate inside the IDE. It is unclear how important those are and the average end-user seems to just close them so they hav enough room to see what they are editing or to view JBoss Central. -- 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

14 years, 4 months

9
10
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 2011