September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4926) Provide Integration plugin to allow monitoring of Hibernate Preformance through JMX using JMX Plugin

by Denis Golovin (JIRA)

Provide Integration plugin to allow monitoring of Hibernate Preformance through JMX using JMX Plugin ---------------------------------------------------------------------------------------------------- Key: JBIDE-4926 URL: https://jira.jboss.org/jira/browse/JBIDE-4926 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate, jmx Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Integration plug-in should provide a way to start monitoring hibernate project performance. It can be a wizard that ask what metrics should be monitored and then show it in graphic. -- 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

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBDS-1771) JBDS50_0450: [COMMIT] (PM) Document Bit Delivery Channels

by mark yarborough (JIRA)

JBDS50_0450: [COMMIT] (PM) Document Bit Delivery Channels --------------------------------------------------------- Key: JBDS-1771 URL: https://issues.jboss.org/browse/JBDS-1771 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
14
0 / 0

[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, 12 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, 12 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, 12 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9711) AS7 Adapter : Deployment of OSGI projects fails if the temporary folder doesn't exist

by Libor Zoubek (JIRA)

AS7 Adapter : Deployment of OSGI projects fails if the temporary folder doesn't exist ------------------------------------------------------------------------------------- Key: JBIDE-9711 URL: https://issues.jboss.org/browse/JBIDE-9711 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M2 Environment: JBossAS Tools 2.3.0.v20110617-0009-H467-M2 Reporter: Libor Zoubek Assignee: Rob Stryker Fix For: 3.3.0.M3 I noticed that, in the context of JBIDE-9133, for the existing -broken- AS7 server instances the utility projects were not zipped to the deployment area. On the other hand, creating a new server instance fixed the issue. So it seems the temporary folder is only created at the same time as the server instance. It's an issue in the sense that you can not guarantee the temporary folder will exist at deployment time (could have been deleted by the user ...). Solution is to call tempdir.mkdirs() right before the actual deployment occurs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

6
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-9673) Dialog "Show All Generic Beans" should looks like "Open Implementation" in JDT

by Alexey Kazakov (JIRA)

Dialog "Show All Generic Beans" should looks like "Open Implementation" in JDT ------------------------------------------------------------------------------ Key: JBIDE-9673 URL: https://issues.jboss.org/browse/JBIDE-9673 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: CDI extensions Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.0.M4 See JBIDE-8692 Now you have to press Ctrl+Click and not to release the button until you click on the needed bean. It's not so convenient. Let's use some dialog like JDT uses in Open Implementation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
15
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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2011