December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7345) Open of faces-config.xml is slooow

by Krasimir Goutcev (JIRA)

Open of faces-config.xml is slooow ---------------------------------- Key: JBIDE-7345 URL: https://jira.jboss.org/browse/JBIDE-7345 Project: Tools (JBoss Tools) Issue Type: Bug Environment: windows xp Java 1.6_0_16 JBoss Tools 3.2.0.v20101014-2053-H92-Beta2 Reporter: Krasimir Goutcev Eclipse freezes for 9 minutes -- 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

14 years, 10 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded

by Denis Golovin (JIRA)

VPE Part should not show exceptions but readable explanation why it cannot be loaded ------------------------------------------------------------------------------------ Key: JBIDE-7308 URL: https://jira.jboss.org/browse/JBIDE-7308 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.M2 Environment: All other platforms except supported ones: macosx-carbon-x86 macosx-cocoa-x86 win32-win32-x86 linux-gtk-x86 linux-gtk-x86_64 Reporter: Denis Golovin Assignee: Maxim Areshkau Fix For: 3.2.0.Beta2 Exceptions related to loading xulrunner should be handled right way. Human friendly messages would be good here for usecases we know. VPE should check for current platform and if it is not supported do not scary users with exceptions. It should try to load XL just in case path to XL injected outside through System property, but show explanation instead of just exception. Something like: "Current platform ${os}-${ws}-${arch} is not supported. To find list of supported platforms and possible workarounds. please read this article on JBoss Tools Community Portal". If someone is trying to inject XULRunner implementation using system property it can say, That "Visual Editor tried to load XL from provided loaction ${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log View". We could also have check box to remove VE related parts from editor: "[x] Open only source part of Visual Editor". -- 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

14 years, 10 months

6
29
0 / 0

[JBoss JIRA] Created: (JBIDE-6379) Unbound Java Build Path

by Burr Sutter (JIRA)

Unbound Java Build Path ----------------------- Key: JBIDE-6379 URL: https://jira.jboss.org/browse/JBIDE-6379 Project: Tools (JBoss Tools) Issue Type: Bug Components: core Affects Versions: 3.1.0.GA Environment: JBoss Developer Studio Version: 3.0.0.GA Build id: v201003100055R Build date: 201003100222 Reporter: Burr Sutter The settings in the Java Build Path become "unbound" between JBDS restarts. I have seen this on multiple Windows machines (32-bit JVM) and have heard that it happens on Linux as well. Specifically with the SOA Platform 5/ESB Libraries but sometimes with the JVM/JDK as well. My Projects are here: http://anonsvn.jboss.org/repos/labs/labs/jbossesb/workspace/bsutter/soa5d... -- 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

14 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7223) ModeShapeMessageConsole Illegally Extends MessageConsole

by Dan Florian (JIRA)

ModeShapeMessageConsole Illegally Extends MessageConsole -------------------------------------------------------- Key: JBIDE-7223 URL: https://jira.jboss.org/browse/JBIDE-7223 Project: Tools (JBoss Tools) Issue Type: Task Components: modeshape Affects Versions: 3.2.0.M2 Reporter: Dan Florian Fix For: 3.3.x ModeShapeMessageConsole is extending MessageConsole which has the @noextend annotation. Rewrite ModeShapeMessageConsole so that it is not a subclass of MessageConsole. This doesn't appear to be causing any runtime problems. -- 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

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5851) New Seam Web Project -> -test project has hsqldb settings in any case

by Vitali Yemialyanchyk (JIRA)

New Seam Web Project -> -test project has hsqldb settings in any case --------------------------------------------------------------------- Key: JBIDE-5851 URL: https://jira.jboss.org/jira/browse/JBIDE-5851 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate, Seam Affects Versions: 3.1.0.CR2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Attachments: screenshot-init-configuration.jpg New -> Seam Web Project -> Configure Seam Facet Settings -> setup MySQL database -> general project has MySQL settings, but -test project has hsqldb settings -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7883) In Seam perspective WPE can't restore it's state after Eclipse restart

by Vitali Yemialyanchyk (JIRA)

In Seam perspective WPE can't restore it's state after Eclipse restart ---------------------------------------------------------------------- Key: JBIDE-7883 URL: https://issues.jboss.org/browse/JBIDE-7883 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Alexey Kazakov in Seam perspective: 1) open some xhtml in VPE; 2) open same xhtml in WPE (Web Page Editor); 3) restart Eclipse: Unable to create editor ID org.eclipse.jst.pagedesigner.PageDesignerEditor: An unexpected exception was thrown. java.lang.NullPointerException at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176) at org.eclipse.jst.j2ee.internal.web.classpath.WebAppLibrariesContainer.computeReferences(WebAppLibrariesContainer.java:100) at org.eclipse.jst.common.jdt.internal.classpath.FlexibleProjectContainer.computeClasspathEntries(FlexibleProjectContainer.java:183) at org.eclipse.jst.j2ee.internal.web.classpath.WebAppLibrariesContainer.computeClasspathEntries(WebAppLibrariesContainer.java:119) at org.eclipse.jst.common.jdt.internal.classpath.FlexibleProjectContainer.<init>(FlexibleProjectContainer.java:120) at org.eclipse.jst.j2ee.internal.web.classpath.WebAppLibrariesContainer.<init>(WebAppLibrariesContainer.java:58) at org.eclipse.jst.j2ee.internal.web.classpath.WebAppLibrariesContainerInitializer.initialize(WebAppLibrariesContainerInitializer.java:35) at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2707) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1850) at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2705) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2645) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2783) at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1948) at org.eclipse.jst.jsp.core.taglib.ProjectDescription.ensureUpTodate(ProjectDescription.java:994) at org.eclipse.jst.jsp.core.taglib.ProjectDescription.getAvailableTaglibRecords(ProjectDescription.java:1085) at org.eclipse.jst.jsp.core.taglib.TaglibIndex.internalGetAvailableTaglibRecords(TaglibIndex.java:847) at org.eclipse.jst.jsp.core.taglib.TaglibIndex.getAvailableTaglibRecords(TaglibIndex.java:506) at org.eclipse.jst.jsf.core.metadata.internal.TaglibMetaDataLocator.locateMetaDataModelProviders(TaglibMetaDataLocator.java:69) at org.eclipse.jst.jsf.common.metadata.internal.DomainLoadingStrategy.locateMetaDataSourceInstances(DomainLoadingStrategy.java:143) at org.eclipse.jst.jsf.common.metadata.internal.DomainLoadingStrategy.load(DomainLoadingStrategy.java:55) at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModel.load(MetaDataModel.java:93) at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModelManager.loadMetadata(MetaDataModelManager.java:147) at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModelManager.getModel(MetaDataModelManager.java:90) at org.eclipse.jst.jsf.common.metadata.query.TaglibDomainMetaDataQueryHelper.getMDModel(TaglibDomainMetaDataQueryHelper.java:205) at org.eclipse.jst.jsf.common.metadata.query.TaglibDomainMetaDataQueryHelper.getModel(TaglibDomainMetaDataQueryHelper.java:90) at org.eclipse.jst.jsf.common.metadata.query.TaglibDomainMetaDataQueryHelper.getEntities(TaglibDomainMetaDataQueryHelper.java:123) at org.eclipse.jst.jsf.common.metadata.query.TaglibDomainMetaDataQueryHelper.getEntity(TaglibDomainMetaDataQueryHelper.java:101) at org.eclipse.jst.jsf.common.metadata.query.TaglibDomainMetaDataQueryHelper.getTrait(TaglibDomainMetaDataQueryHelper.java:254) at org.eclipse.jst.pagedesigner.dtmanager.DefaultDTInfoFactory.getDTInfo(DefaultDTInfoFactory.java:49) at org.eclipse.jst.pagedesigner.dtmanager.DTManager.getDTInfo(DTManager.java:99) at org.eclipse.jst.pagedesigner.dtmanager.converter.internal.DTTagConverterFactory.createConverter(DTTagConverterFactory.java:32) at org.eclipse.jst.pagedesigner.dtmanager.DTManager.getTagConverter(DTManager.java:65) at org.eclipse.jst.pagedesigner.parts.ElementEditPart.getTagConverter(ElementEditPart.java:163) at org.eclipse.jst.pagedesigner.parts.ElementEditPart.setModel(ElementEditPart.java:84) at org.eclipse.jst.pagedesigner.parts.HTMLEditPartsFactory.createEditPart(HTMLEditPartsFactory.java:69) at org.eclipse.gef.editparts.AbstractEditPart.createChild(AbstractEditPart.java:268) at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:770) at org.eclipse.jst.pagedesigner.parts.DocumentEditPart.refreshChildren(DocumentEditPart.java:134) at org.eclipse.jst.pagedesigner.parts.DocumentEditPart.refreshChildren(DocumentEditPart.java:126) at org.eclipse.gef.editparts.AbstractEditPart.refresh(AbstractEditPart.java:718) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:633) at org.eclipse.jst.pagedesigner.parts.DocumentEditPart.refresh(DocumentEditPart.java:114) at org.eclipse.gef.editparts.AbstractEditPart.addNotify(AbstractEditPart.java:252) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addNotify(AbstractGraphicalEditPart.java:223) at org.eclipse.jst.pagedesigner.parts.NodeEditPart.addNotify(NodeEditPart.java:104) at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:211) at org.eclipse.gef.editparts.SimpleRootEditPart.setContents(SimpleRootEditPart.java:105) at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:617) at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:626) at org.eclipse.jst.pagedesigner.editors.SimpleGraphicalEditor.setModel(SimpleGraphicalEditor.java:425) at org.eclipse.jst.pagedesigner.editors.HTMLEditor.connectDesignPage(HTMLEditor.java:363) at org.eclipse.jst.pagedesigner.editors.HTMLEditor.createPages(HTMLEditor.java:443) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271) at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1429) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1567) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2548) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7589) Deltacloud client: extract to its own plugin

by Andre Dietisheim (JIRA)

Deltacloud client: extract to its own plugin -------------------------------------------- Key: JBIDE-7589 URL: https://jira.jboss.org/browse/JBIDE-7589 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 The deltacloud client currently is hidden in org.jboss.tools.deltacloud.core. In order to have a java client, that deltacloud may offer officially (we already had talks to them), we need to put the client into its own bundle. As bundle, this component may also be used by non-osgi apps since osgi only add additional properties to the manifest which will be simply ignored by non-osgi apps. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6708) MDB WTP Wizard Annotations for HornetQ

by Gary Lamperillo (JIRA)

MDB WTP Wizard Annotations for HornetQ -------------------------------------- Key: JBIDE-6708 URL: https://jira.jboss.org/browse/JBIDE-6708 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.1 Environment: JBDS 3.0.1 , EAP 5.1 Beta, HornetQ 2.1 Reporter: Gary Lamperillo Fix For: 3.1.2 Using the Message Driven Bean WTP Wizard that is in JBDS 3.0.1, an annotation in the format is created: @MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") HornetQ will need an annotation in the following format: @MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue"), @ActivationConfigProperty(propertyName = "useLocalTx", propertyValue = "true") }, mappedName = "queue/testQueue") Either HornetQ will nee to correspond to WTPs expectation or the wizard will need to be modified to accept the hornetq specific changes. Since the tooling will still need to work with other providers such as JBoss Messaging, a radio button will need to be added to the Wizard as well to select HornetQ. -- 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

14 years, 10 months

6
16
0 / 0

[JBoss JIRA] Created: (JBIDE-7295) Closing Jboss Tools Jsp Editor causes Eclipse to crash

by Luca Cavagnoli (JIRA)

Closing Jboss Tools Jsp Editor causes Eclipse to crash ------------------------------------------------------ Key: JBIDE-7295 URL: https://jira.jboss.org/browse/JBIDE-7295 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.M2 Environment: Ubuntu 10.04 64bit Eclipse 3.6 Helios 64bit, Build id: 20100617-1415 OpenJDK Java 6 Runtime Reporter: Luca Cavagnoli Assignee: Alexey Kazakov Eclipse crashes whenever Jboss Tools Jsp Editor is closed. Just open a Jsp page, close it with Ctrl+F4 or by clicking on the panel's red cross, and Eclipse crashes. The problem occurs with both Eclipse 3.5 and Eclipse 3.6. -- 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

14 years, 10 months

6
18
0 / 0

[JBoss JIRA] Created: (JBIDE-7102) Open xhtml file with VPE -> An internal error occurred during: "Refreshing XPath View".

by Vitali Yemialyanchyk (JIRA)

Open xhtml file with VPE -> An internal error occurred during: "Refreshing XPath View". --------------------------------------------------------------------------------------- Key: JBIDE-7102 URL: https://jira.jboss.org/browse/JBIDE-7102 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Maxim Areshkau 1) Open some xhtml file with VPE first time - so VPE start a little bit long time (XPath view was not active, was not opened); 2) Press "Show selection bar" just when this became be possible - do not sure could this be related with exception; 3) get exception message box; 4) exception in "Error Log": java.lang.RuntimeException: Не удалось преобразовать узел в дескриптор at org.apache.xml.dtm.ref.DTMManagerDefault.getDTMHandleFromNode(DTMManagerDefault.java:576) at org.apache.xpath.XPathContext.getDTMHandleFromNode(XPathContext.java:184) at org.apache.xpath.XPath.execute(XPath.java:303) at org.apache.xpath.jaxp.XPathExpressionImpl.eval(XPathExpressionImpl.java:129) at org.apache.xpath.jaxp.XPathExpressionImpl.eval(XPathExpressionImpl.java:99) at org.apache.xpath.jaxp.XPathExpressionImpl.evaluate(XPathExpressionImpl.java:184) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer.evaluateXPath(XPathComputer.java:212) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer.executeXPath(XPathComputer.java:185) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer.doCompute(XPathComputer.java:165) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer.access$2(XPathComputer.java:164) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer$2.run(XPathComputer.java:154) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 5) try to open other xhtml files - get this exception for every file open; 6) open XPath view - get this exception regularly - almost every mouse click; -- 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

14 years, 10 months

6
9
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 December 2010