January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7681) Cannot create two or more web services in a web project

by Lukas Jungmann (JIRA)

Cannot create two or more web services in a web project ------------------------------------------------------- Key: JBIDE-7681 URL: https://jira.jboss.org/browse/JBIDE-7681 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.Beta2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Priority: Critical -create a new ear project ("Ear") -create a new dynamic web project ("WsWar") -create a top down ws from some wsdl using wtp wizard in WsWar project - ws project WsWar, ear project Ear, server runtime JBossAS6.0, ws runtime JBossWS -create another top down ws from different wsdl there - ws project WsWar, ear project Ear, server runtime JBossAS6.0, ws runtime JBossWS => wizard ends with "The Web Service Name has been used in the web.xml of the web project." error message and doesn't allow user to finish it but all I'm trying to do is to create two completely different services in one project message is comming from line 190 in org.jboss.tools.ws.creation.core.commands.MergeWebXMLCommand -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
24
0 / 0

[JBoss JIRA] Created: (JBIDE-7913) Top-Down ws wizard is overwriting existing unrelated ws impl classes

by Lukas Jungmann (JIRA)

Top-Down ws wizard is overwriting existing unrelated ws impl classes -------------------------------------------------------------------- Key: JBIDE-7913 URL: https://issues.jboss.org/browse/JBIDE-7913 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.Beta2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick this came up as a result of JBIDE-7681 (see comment from 12/15/10) -create a new Dynamic web project -create following interface there: package x; import javax.jws.WebService; @WebService() public interface Zws { String test(); } -create following class there: package x; import javax.jws.WebService; @WebService() public class ZwsImpl { public String test() { return "Hello Dolly!"; } } -create some Top-Down ws there using default settings package (use default package) -open ZwsImpl.java in the editor => Current: ZwsImpl class is rewritten Expected: the class remains untouched Note for myself: Check this also for Bottom up case -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8067) OutOfMemoryError while opening or closing faces-config.xml

by Yahor Radtsevich (JIRA)

OutOfMemoryError while opening or closing faces-config.xml ---------------------------------------------------------- Key: JBIDE-8067 URL: https://issues.jboss.org/browse/JBIDE-8067 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Environment: Windows XP, JBDS 4.0.0.Beta2, . Reporter: Yahor Radtsevich Assignee: Alexey Kazakov Priority: Critical The error appears sometimes when I try to open or close faces-config.xml and Studio proposes to exit. If I choose exit, than this workspace cannot be opened anymore and Studio fails to start. I do not know any reproducible way to catch this error, but it appears several times a day in my workspace that has two JSF projects in it. The full stacktrace follows: java.lang.OutOfMemoryError at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:199) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) at org.jboss.tools.common.util.FileUtil.readBytes(FileUtil.java:103) at org.jboss.tools.common.util.FileUtil.readFileWithEncodingCheck(FileUtil.java:83) at org.jboss.tools.common.model.filesystems.impl.EclipseFileBodySource.get(FolderImpl.java:1184) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.getEntityProperties(FolderImpl.java:240) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateNew(FolderImpl.java:673) at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:399) at org.jboss.tools.common.model.util.EclipseResourceUtil.findResourceInFileSystem(EclipseResourceUtil.java:552) at org.jboss.tools.common.model.util.EclipseResourceUtil.getObjectByResource(EclipseResourceUtil.java:137) at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:335) at org.jboss.tools.common.model.markers.XMarkerManager.reload(XMarkerManager.java:105) at org.jboss.tools.common.model.markers.XMarkerManager.reload(XMarkerManager.java:90) at org.jboss.tools.common.model.markers.XMarkerManager.<init>(XMarkerManager.java:40) at org.jboss.tools.common.model.markers.XMarkerManager.getInstance(XMarkerManager.java:31) at org.jboss.tools.common.model.ui.navigator.LabelDecoratorImpl.getErrorState(LabelDecoratorImpl.java:71) at org.jboss.tools.common.model.ui.navigator.LabelDecoratorImpl.decorateImage(LabelDecoratorImpl.java:40) at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:94) at org.eclipse.jface.viewers.DecoratingLabelProvider.updateLabel(DecoratingLabelProvider.java:356) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:183) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:934) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1014) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:481) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2141) at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:829) at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:804) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:778) at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:644) at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:749) at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1492) at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:833) at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1476) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1422) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1383) at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1469) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:274) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1664) at org.jboss.tools.common.editor.XModelObjectTreeViewComponent.createControl(XModelObjectTreeViewComponent.java:90) at org.jboss.tools.common.editor.form.SampleTreeForm.createClientArea(SampleTreeForm.java:81) at org.jboss.tools.common.model.ui.forms.ExpandableForm.createControl(ExpandableForm.java:108) at org.jboss.tools.common.model.ui.forms.SplitFormContainer.createFirstForm(SplitFormContainer.java:79) at org.jboss.tools.common.model.ui.forms.SplitFormContainer.createControl(SplitFormContainer.java:103) at org.jboss.tools.common.model.ui.forms.DefaultFormContainer.createControl(DefaultFormContainer.java:47) at org.jboss.tools.common.model.ui.forms.DefaultFormPage.createFormControl(DefaultFormPage.java:94) at org.jboss.tools.common.editor.TreeFormPage.createFormControl(TreeFormPage.java:151) at org.jboss.tools.common.model.ui.forms.DefaultFormPage.createControl(DefaultFormPage.java:108) at org.jboss.tools.common.editor.TreeFormPage.createPartControl(TreeFormPage.java:405) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:241) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:211) at org.jboss.tools.common.editor.ObjectMultiPageEditor.addFormPage(ObjectMultiPageEditor.java:933) at org.jboss.tools.jsf.ui.editor.FacesConfigEditor.doCreatePages(FacesConfigEditor.java:59) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:239) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:176) 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.PartPane.setVisible(PartPane.java:313) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1254) at org.eclipse.ui.internal.PartStack.handleDeferredEvents(PartStack.java:1222) at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400) at org.eclipse.ui.internal.PartSashContainer.handleDeferredEvents(PartSashContainer.java:1409) at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400) at org.eclipse.ui.internal.WorkbenchPage.handleDeferredEvents(WorkbenchPage.java:1420) at org.eclipse.ui.internal.WorkbenchPage.deferUpdates(WorkbenchPage.java:1410) at org.eclipse.ui.internal.WorkbenchPage.access$14(WorkbenchPage.java:1401) at org.eclipse.ui.internal.WorkbenchPage$16.runWithException(WorkbenchPage.java:3304) 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(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

6
25
0 / 0

[JBoss JIRA] Created: (JBIDE-7949) CDI is not validating @Inject Inject<[type]> correctly

by Max Andersen (JIRA)

CDI is not validating @Inject Inject<[type]> correctly ------------------------------------------------------ Key: JBIDE-7949 URL: https://issues.jboss.org/browse/JBIDE-7949 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Max Andersen Priority: Critical Fix For: 3.2.0.CR1 @Inject private Instance<Project> project; is marked with: Multiple beans are eligible for injection to the injection point AbstractShellTest.java /forge-test-harness/src/main/java/org/jboss/seam/forge/test line 84 CDI Problem Instance<...> means there can be 0 to N matches thus shouldn't be marked as a validation error. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7944) CDI is not enabled on CDI projects like seam forge

by Max Andersen (JIRA)

CDI is not enabled on CDI projects like seam forge -------------------------------------------------- Key: JBIDE-7944 URL: https://issues.jboss.org/browse/JBIDE-7944 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299), maven Affects Versions: 3.2.0.Beta1 Reporter: Max Andersen Assignee: Snjezana Peco Priority: Critical Fix For: 3.2.0.CR1 EXECUTE: Import seam-forge as maven projects (https://github.com/seam/forge) ASSERT: Project that uses CDI and related javax.inject.* annotations have CDI enabled. (<-- this fails) How come ? What is currently the trigger for enabling CDI if not the javax.inject.* annotations ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8194) JBoss Tools GWT integration can't be installed

by Maxim Areshkau (JIRA)

JBoss Tools GWT integration can't be installed ---------------------------------------------- Key: JBIDE-8194 URL: https://issues.jboss.org/browse/JBIDE-8194 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 3.2.0.CR1 Reporter: Maxim Areshkau Assignee: Denis Golovin JBoss Tools GWT integration couldn't be installed via update site. See forum reference. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8185) Launch instance wizard: cannot launch instance on clean workspace

by Andre Dietisheim (JIRA)

Launch instance wizard: cannot launch instance on clean workspace ----------------------------------------------------------------- Key: JBIDE-8185 URL: https://issues.jboss.org/browse/JBIDE-8185 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR2 (tentative) Attachments: DeltaCloud.java.patch -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8186) Manage Keys Dialog: OK stays disabled when creating the first key

by Andre Dietisheim (JIRA)

Manage Keys Dialog: OK stays disabled when creating the first key ----------------------------------------------------------------- Key: JBIDE-8186 URL: https://issues.jboss.org/browse/JBIDE-8186 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR2 (tentative) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8183) Instances View: has no "ID" column

by Andre Dietisheim (JIRA)

Instances View: has no "ID" column ---------------------------------- Key: JBIDE-8183 URL: https://issues.jboss.org/browse/JBIDE-8183 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR2 (tentative) Attachments: idColumn.patch The instances view has no column that displays the id of the instances. In consequence the id might only be looked up in the cloudview (xxx[id]) or in the properties view. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6214) Support project example with no Eclipse metadata, only pom.xml, in zip

by Pete Muir (JIRA)

Support project example with no Eclipse metadata, only pom.xml, in zip ---------------------------------------------------------------------- Key: JBIDE-6214 URL: https://jira.jboss.org/jira/browse/JBIDE-6214 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Reporter: Pete Muir Assignee: Snjezana Peco If projects want to incorporate producing project examples into their release process, they are likely not to have any valid eclipse metadata available for the example when using Maven. -- 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

15 years, 2 months

7
20
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 January 2011