August 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9257) Runtime detectors for SOA are missing in updatesite

by Libor Zoubek (JIRA)

Runtime detectors for SOA are missing in updatesite --------------------------------------------------- Key: JBIDE-9257 URL: https://issues.jboss.org/browse/JBIDE-9257 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite, drools, jbpm Affects Versions: 3.3.0.M2 Reporter: Libor Zoubek Assignee: Douglas Palmer Priority: Critical Fix For: 3.3.0.M3 I just installed http://download.jboss.org/jbosstools/builds/development/3.3.0.M2.soa-tool... (H6) on top of indigo with http://download.jboss.org/jbosstools/builds/development/3.3.0.M2/ (H6), Detection of runtimes does not work, for SOA technologies like drools, jBPM (and others?) AFAIK this functionality is provided by several plugins (1 per technology) which are missing. Without these plugins SOA-P builds are not fully recognized by Runtime Detection Preference page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
7
0 / 0

[JBoss JIRA] Created: (JBDS-1620) CLONE - Enable dropin folder reconciling by default for JBDS product

by Denis Golovin (JIRA)

CLONE - Enable dropin folder reconciling by default for JBDS product -------------------------------------------------------------------- Key: JBDS-1620 URL: https://issues.jboss.org/browse/JBDS-1620 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 4.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.1.0.GA Now to get that supported several additions steps should be done: To activate dropins reconciling you need to do the following: - open studio/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info - find the line org.eclipse.equinox.p2.reconciler.dropins,1.1.0.v20100525,plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525.jar,4,false and change it to org.eclipse.equinox.p2.reconciler.dropins,1.1.0.v20100525,plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525.jar,4,true - create the studio/dropins directory and add plugins as is usual - start JBDS with the -clean option at least once To eliminate this steps plugin org.eclipse.equinox.p2.reconciler.dropins should be marked as auto started in jbds-all.product definition which is used to build JBDS product -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-8700) Add Configure>Detect Project Configuration menu to runtime plugin

by Snjezana Peco (JIRA)

Add Configure>Detect Project Configuration menu to runtime plugin ----------------------------------------------------------------- Key: JBIDE-8700 URL: https://issues.jboss.org/browse/JBIDE-8700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M1 The action would detect different project configurations. For the first time, it would detect CDI based on the existence of cdi-api in the project's classpath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBDS-1673) Installer should align with runtime detection

by Max Rydahl Andersen (JIRA)

Installer should align with runtime detection --------------------------------------------- Key: JBDS-1673 URL: https://issues.jboss.org/browse/JBDS-1673 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Reporter: Max Rydahl Andersen Assignee: Denis Golovin Priority: Blocker Fix For: 5.0.0.M3, 5.0.0.M2 The installer currently has its own form of server detection which generates a file that runtime detection uses to configure specified servers. The detection code is not shared and the workflow/power of them are different. I suggest we either: A) extract the detection code and uses that in both places OR B) change the installer to just ask for directories to scan on every startup which then needs somehow to be read by the runtime detection and then it takes over all this WDYT ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

5
20
0 / 0

[JBoss JIRA] Created: (JBIDE-9388) Support Seam Servlet module

by Alexey Kazakov (JIRA)

Support Seam Servlet module --------------------------- Key: JBIDE-9388 URL: https://issues.jboss.org/browse/JBIDE-9388 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x http://docs.jboss.org/seam/3/servlet/latest/reference/en-US/html/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable

by Martin Malina (JIRA)

Renaming a seam project makes the ds.xml undeployable ----------------------------------------------------- Key: JBIDE-8938 URL: https://issues.jboss.org/browse/JBIDE-8938 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.1.M1 Environment: jbdevstudio-product-eap-macosx-cocoa-4.1.0.v201105091943R-H400-M1.jar Mac OS X 10.6 Snow Leopard Reporter: Martin Malina Assignee: Alexey Kazakov If you rename a seam project it fails to deploy again because of failed dependencies: DEPLOYMENTS MISSING DEPENDENCIES: Deployment "persistence.unit:unitName=#SeamWar" is missing the following dependencies: Dependency "jboss.jca:name=SeamWarDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=SeamWarDatasource,service=DataSourceBinding' **") DEPLOYMENTS IN ERROR: Deployment "jboss.jca:name=SeamWarDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=SeamWarDatasource,service=DataSourceBinding' ** This happens because after the renaming, the ds file becomes undeployable. If you mark it as deployable again, you can then deploy it and also the renamed seam project deploys correctly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
11
0 / 0

[JBoss JIRA] Created: (JBDS-1815) Context menu misnomer when right clicking on struts-config.xml action-mappings in diagram, tree view or outline

by Tony Samlal (JIRA)

Context menu misnomer when right clicking on struts-config.xml action-mappings in diagram, tree view or outline --------------------------------------------------------------------------------------------------------------- Key: JBDS-1815 URL: https://issues.jboss.org/browse/JBDS-1815 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: runtime Affects Versions: 4.0.0.GA, 3.0.1.GA, 4.1.0.GA Environment: Windows 7 64 bit w/ Java 1.6.24, Mac OSX 10.6.8 Reporter: Tony Samlal Priority: Minor When right clicking on an existing action mapping to create a local forward or local exception, the only options are global forward and global exception. Using these context menus does indeed create the respective local forward/exception but it is confusing as right clicking on global-exceptions and global-forwards also gives the same options. The local forwards/exceptions should say either "create forward/create exception" as it does in the original Exadel Studio Pro product which Jboss Developer Tools is based on or perhaps just Local Forward/Local Exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8302) Very slow open of server editors with remote deployement

by Max Rydahl Andersen (JIRA)

Very slow open of server editors with remote deployement -------------------------------------------------------- Key: JBIDE-8302 URL: https://issues.jboss.org/browse/JBIDE-8302 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.2.1 have a server setup for remote connection; restart eclipse; double click the server ...see that it is *blocked* for several seconds (seen between 10 seconds to minutes). Running jstack reveals that it is blocked on getting host by address: "main" prio=8 tid=0000000013801000 nid=0xa0ba9540 runnable [00000000bfffd000] java.lang.Thread.State: RUNNABLE at java.net.Inet6AddressImpl.getHostByAddr(Native Method) at java.net.InetAddress$1.getHostByAddr(InetAddress.java:854) at java.net.InetAddress.getHostFromNameService(InetAddress.java:534) at java.net.InetAddress.getCanonicalHostName(InetAddress.java:505) at org.eclipse.wst.server.core.util.SocketUtil.isLocalhost(SocketUtil.java:296) at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart.updateRuntimeCombo(OverviewEditorPart.java:891) at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart.createGeneralSection(OverviewEditorPart.java:428) at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart.createPartControl(OverviewEditorPart.java:295) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:241) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:211) at org.eclipse.wst.server.ui.internal.editor.ServerEditor.createPages(ServerEditor.java:235) 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.EditorReference.getEditor(EditorReference.java:289) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2863) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2674) at org.eclipse.wst.server.ui.internal.ServerUIPlugin.editServer(ServerUIPlugin.java:425) at org.eclipse.wst.server.ui.internal.ServerUIPlugin.editServer(ServerUIPlugin.java:408) at org.eclipse.wst.server.ui.internal.view.servers.OpenAction.perform(OpenAction.java:36) at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.run(AbstractServerAction.java:60) at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221) at org.eclipse.ui.navigator.CommonNavigatorManager$3.open(CommonNavigatorManager.java:185) at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:845) 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.fireOpen(StructuredViewer.java:843) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1131) at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:462) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1235) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3622) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) 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) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2070) SOA Modeler

by Mark Little (JIRA)

SOA Modeler ----------- Key: JBIDE-2070 URL: http://jira.jboss.com/jira/browse/JBIDE-2070 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: Mark Little Thomas Erl donated IP to us around the SOA Modeler. -- 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

13 years, 12 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8915) Show In > Forge

by Max Rydahl Andersen (JIRA)

Show In > Forge --------------- Key: JBIDE-8915 URL: https://issues.jboss.org/browse/JBIDE-8915 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Assignee: Koen Aers would be nice being able to right click a project and "Show In > Forge" would open the forge view and cd into the project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
7
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 August 2011