May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1655) Recognize and define Drools Runtime from SOA-P standalone product during installation

by Vlado Pakan (JIRA)

Recognize and define Drools Runtime from SOA-P standalone product during installation ------------------------------------------------------------------------------------- Key: JBDS-1655 URL: https://issues.jboss.org/browse/JBDS-1655 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 4.1.0.M1 Reporter: Vlado Pakan When searching for runtimes during installation SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes when installed JBDS is run. Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04. JDBS should automatically detect ESB Runtime within SOA-P product during installation and define it for later use. Has to be working also with SOA-P Standalone products. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

10
15
0 / 0

[JBoss JIRA] Created: (JBIDE-3113) Consolidation/clean up of preference pages

by John Graham (JIRA)

Consolidation/clean up of preference pages ------------------------------------------ Key: JBIDE-3113 URL: https://jira.jboss.org/jira/browse/JBIDE-3113 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, drools, jbpm Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk Reporter: John Graham Priority: Minor JBT currently has three preference page categories: 1. Drools 2. JBoss jBPM 3. JBoss Tools The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss: - JBoss -- Drools -- jBPM Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) ) -- 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, 6 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-8126) Manage Keys Dialog: should select keys and close dialog on double click

by Andre Dietisheim (JIRA)

Manage Keys Dialog: should select keys and close dialog on double click ----------------------------------------------------------------------- Key: JBIDE-8126 URL: https://issues.jboss.org/browse/JBIDE-8126 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.x -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8290) Delete hotkey should do nothing unless all selections are DeltaCloud objects (not instances)

by Rob Stryker (JIRA)

Delete hotkey should do nothing unless all selections are DeltaCloud objects (not instances) -------------------------------------------------------------------------------------------- Key: JBIDE-8290 URL: https://issues.jboss.org/browse/JBIDE-8290 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Rob Stryker Assignee: Andre Dietisheim Fix For: 3.2.1 I continually end up deleting my entire cloud by accident. I select a few instances, try to delete them (which is of course impossible), and quickly press enter, and then my entire cloud is removed. This is a big pain. It'd be better if the delete hotkey did nothing if the selection is not only DeltaCloud objects -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8944) Unable to start eclipse after JbossTools installed

by Libor Zoubek (JIRA)

Unable to start eclipse after JbossTools installed --------------------------------------------------- Key: JBIDE-8944 URL: https://issues.jboss.org/browse/JBIDE-8944 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.M1 Reporter: Libor Zoubek Priority: Blocker Fix For: 3.3.0.M1 I've installed all features from updatesite zip on top of eclipse-jee-indigo-M6a http://download.jboss.org/jbosstools/builds/development/3.3.0.M1a/2011-05... {noformat} !SESSION 2011-05-13 09:37:08.483 ----------------------------------------------- eclipse.buildId=I20110310-1119 java.version=1.6.0_25 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product !ENTRY org.teiid.designer.datatools 4 0 2011-05-13 09:37:16.097 !MESSAGE FrameworkEvent ERROR !STACK 0 java.util.zip.ZipException: Exception in opening zip file: /data/eclipse/jbosstools-3.3.0a-M1-H2359/eclipse/plugins/org.teiid.designer.datatools_7.5.0.v20110511-0152-H402-M1.jar at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAction.java:287) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.basicOpen(ZipBundleFile.java:87) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getZipFile(ZipBundleFile.java:100) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.checkedOpen(ZipBundleFile.java:73) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getEntry(ZipBundleFile.java:245) at org.eclipse.osgi.baseadaptor.BaseData.getEntry0(BaseData.java:114) at org.eclipse.osgi.baseadaptor.BaseData.getEntry(BaseData.java:105) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getEntry0(AbstractBundle.java:1246) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getEntry(AbstractBundle.java:1241) at org.eclipse.core.internal.registry.osgi.EclipseBundleListener.getExtensionURL(EclipseBundleListener.java:120) at org.eclipse.core.internal.registry.osgi.EclipseBundleListener.addBundle(EclipseBundleListener.java:163) at org.eclipse.core.internal.registry.osgi.EclipseBundleListener.processBundles(EclipseBundleListener.java:90) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.onStart(RegistryStrategyOSGI.java:224) at org.eclipse.core.internal.registry.ExtensionRegistry.<init>(ExtensionRegistry.java:725) at org.eclipse.core.runtime.RegistryFactory.createRegistry(RegistryFactory.java:58) at org.eclipse.core.internal.registry.osgi.Activator.startRegistry(Activator.java:137) at org.eclipse.core.internal.registry.osgi.Activator.start(Activator.java:56) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:460) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) at org.eclipse.osgi.internal.loader.MultiSourcePackage.loadClass(MultiSourcePackage.java:31) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at org.eclipse.equinox.internal.app.Activator.start(Activator.java:55) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:460) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.eclipse.core.internal.runtime.PlatformActivator.startAppContainer(PlatformActivator.java:44) at org.eclipse.core.internal.runtime.PlatformActivator.start(PlatformActivator.java:31) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:127) at java.util.zip.ZipFile.<init>(ZipFile.java:144) at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAction.java:274) ... 73 more {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
16
0 / 0

[JBoss JIRA] Created: (JBIDE-5099) OpenOn for custom Jsf 2.0 components

by Maxim Areshkau (JIRA)

OpenOn for custom Jsf 2.0 components ------------------------------------ Key: JBIDE-5099 URL: https://jira.jboss.org/jira/browse/JBIDE-5099 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing, Visual Page Editor core Affects Versions: 3.1.0.M4 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.1.0.CR1 OpenOn for custom Jsf 2.0 components from source part. -- 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, 6 months

7
17
0 / 0

[JBoss JIRA] Created: (JBIDE-1104) .sar file cannot be included in .ear file

by Juergen Zimmermann (JIRA)

.sar file cannot be included in .ear file ----------------------------------------- Key: JBIDE-1104 URL: http://jira.jboss.com/jira/browse/JBIDE-1104 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.Beta4 Environment: JBoss Tools nightly build 20071017 Reporter: Juergen Zimmermann I need a .ear file which contains a .sar file (service archive for JBoss). Such a .sar file is declared in META-INF/jboss-app.xml of the EAR project "hska" as follows: <jboss-app> <security-domain>java:/jaas/hska</security-domain> <module> <service>hska.sar</service> </module> </jboss-app> I have a "General Project" named hskaSAR which has a META-INF subdirectory for the xml files of the .sar file. Creating hskaSAR/hska.sar via the "Project Archives" view of JBoss Tools works fine. However, there is no possibility to include the .sar file within the (exploded) .ear. I tried to edit and extend the file .settings/org.eclipse.wst.common.component within the EAR project as follows: <dependent-module deploy-path="/" handle="module:/classpath/lib/hskaSAR/hska.sar"> <dependency-type>uses</dependency-type> </dependent-module> However, this workaround doesn't work. -- 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

14 years, 6 months

6
23
0 / 0

[JBoss JIRA] Created: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars

by Gonne (JIRA)

EAR deployment with option "as compressed archives" results in ear containing invalid jars ------------------------------------------------------------------------------------------ Key: JBIDE-6320 URL: https://jira.jboss.org/browse/JBIDE-6320 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.1.0.GA Environment: Windows XP Pro SP3, Java JDK 1.6.0_20, Eclipse IDE for JEE 3.5.2, JBoss Tools 3.1 (JBossAS Tools 2.1.0.v201003050540R-H56-GA), WTP Patches 3.1.2.v201003181725), m2Eclipse 0.10.0 Reporter: Gonne Assignee: Rob Stryker The deployment of a minimal Enterprise Application Project (consisting of e.g. jboss-seam.jar as ejb-module and mvel2.jar as 3rd-party jar) with the deployment option "Deploy projects as compressed archives" activated, results in an ear containing some invalid jars: These invalid jars are containing only one jar with the same name which finally contains the actual jar content. E.g. the mvel2.jar contains a mvel2.jar which contains the "META-INF" and an "org" directory. It seems that every supplied jar is affected that is determined as module jar, because it is an ejb-module (e.g. jboss-seam.jar) or its manifest contains a "Main-class" entry marking it as client-module. -- 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, 6 months

6
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8460) Get JBossTools added to wtp's list of server adapters

by Rob Stryker (JIRA)

Get JBossTools added to wtp's list of server adapters ----------------------------------------------------- Key: JBIDE-8460 URL: https://issues.jboss.org/browse/JBIDE-8460 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: UpStream Affects Versions: 3.2.0.Final Reporter: Rob Stryker Assignee: Nick Boldt Fix For: 3.3.x It seems what happens is you must make use of the org.eclipse.wst.server.discovery plugin. This plugin has a file (discovery.xml) which has "sites", and those sites (such as http://public.dhe.ibm.com/software/websphere/wasce/updates/) seem to be an eclipse update site. The entry point for this wizard is in the New Runtime wizard. At the top is a hyperlink that reads "Download other adapters" (or something similar). It then queries these sites, and allows you to select one of those available. It seems the objects are then downloaded as IInstallableUnit's, which is in the org.eclipse.equinox.p2.metadata package. I kinda lose track of it here, but, I suspect that after this it is downloaded as an actual eclipse bundle and added into the eclipse installation. But I guess I could trace through further Changes to our site would require adding the category and adding it to certain features in our site.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

8
35
0 / 0

[JBoss JIRA] Created: (JBIDE-8683) JPA: @Type annotation doesnt work correctly

by Dmitry Geraskov (JIRA)

JPA: @Type annotation doesnt work correctly ------------------------------------------- Key: JBIDE-8683 URL: https://issues.jboss.org/browse/JBIDE-8683 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.Final Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.M1 Index composite is not updated if add @Index in source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
5
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 May 2011