February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10692) project example dialog should have the icon used in "central"

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10692: ------------------------------------------- Summary: project example dialog should have the icon used in "central" Key: JBIDE-10692 URL: https://issues.jboss.org/browse/JBIDE-10692 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Minor Fix For: 3.3.0.Beta1 the dialog opened with example details does not "inherit" the icon from the actual example. it should. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
18
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] (JBIDE-10827) Web Service tooling cant be properly used with Eclipse for Java Developers

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-10827: ----------------------------------------- Summary: Web Service tooling cant be properly used with Eclipse for Java Developers Key: JBIDE-10827 URL: https://issues.jboss.org/browse/JBIDE-10827 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M5 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Priority: Critical Fix For: 3.3.0.Beta1 Attachments: 1.error-NPE.txt, 2.error-AXIS.txt I have found several problems during mavenization Web Services SWTBot tests. In the beginning I installed Eclipse for Java Developers Indigo SR1. After that I installed web services features (JBoss Web Services Tools, JBoss JAX-RS Tools) from JBoss Tools update site (http://download.jboss.org/jbosstools/updates/development/indigo/). Installation was successful, but many annoying errors I found after that. 1. When I was creating Dynamic Web Project with JBoss Web Service Core facet installed, an error in error log was thrown: * Project facet wst.jsdt.web has not been defined. It is used in plugin org.eclipse.jst.server.core. ** Installing three plugins (org.eclipse.wst.jsdt.web.core, org.eclipse.wst.jsdt.web.support.jsp, org.eclipse.wst.jsdt.web.ui) into eclipse/plugins folder fixed the problem 2. There was option to choose Web Service wizard (New -> Other -> Web Services -> Web Service) but when I was trying to click it, wizard didn't show up and NPE was thrown * "1.error-NPE.txt" attachment ** Installing the feature (org.eclipse.jst.enterprise_ui.feature) fixed the error. 3. Then I created sample web service with wizard "Create a Sample Web Service". This wizard generated simple class which is annotated just like to be SOAP web service as expected.I was trying to create Bottom Up Web Service from generated class with appropriate wizard but it fails, some IWAB0506E error was thrown * IWAB0506E Error when copying Axis jar files to web project (2.error-AXIS.txt attachment) ** I had to install WST Web Services UI feature (org.eclipse.wst.ws_ui.feature.feature.group) to fix this problem. This feature also fixed the problem of nonexisting "WSDL File" wizard which annoyed me. 4. The last feature which I was missing when running bot tests with maven was Eclipse XML Editors and Tools (org.eclipse.wst.xml_ui.feature.feature.group). This feature is located in Eclipse for Java Developers by default, but it is missing in eclipse bundled with maven. To shorten this description, I think that Web Service plugin cant be properly used in Eclipse for Java Developers. There are missing dependencies. These dependencies are the minimum which I found: Features: * org.eclipse.jst.enterprise_ui.feature * org.eclipse.wst.ws_ui.feature.feature.group * org.eclipse.wst.xml_ui.feature.feature.group Plugins: * org.eclipse.wst.jsdt.web.core * org.eclipse.wst.jsdt.web.support.jsp * org.eclipse.wst.jsdt.web.ui In my opinion, further investigation would be needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
37
0 / 0

[JBoss JIRA] (JBIDE-10950) use seam 2.2.1.Final instead of 2.2.1.CR1 and 2.2.1.CR2 in requirements?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10950: ---------------------------------- Summary: use seam 2.2.1.Final instead of 2.2.1.CR1 and 2.2.1.CR2 in requirements? Key: JBIDE-10950 URL: https://issues.jboss.org/browse/JBIDE-10950 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 There's a newer version of the Seam runtime available for use w/ building/testing: http://sourceforge.net/projects/jboss/files/JBoss%20Seam/2.2.1.Final/ Yes, we're still using http://softlayer.dl.sourceforge.net/project/jboss/JBoss%20Seam/2.2.1.CR1/ as noted in this build: https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... Should we just be using the .Final, or is there some reason we're stuck using the two CR1 and CR2 builds? Note: the requirements bootstrap job runs against the requirement builders in this folder: https://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/ https://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.2.1.... https://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/seam-2.2.1.... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
7
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] (JBIDE-10529) test failure in common.verification

by Nick Boldt (Created) (JIRA)

test failure in common.verification ----------------------------------- Key: JBIDE-10529 URL: https://issues.jboss.org/browse/JBIDE-10529 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 After switching to newer target platform (JBIDE-10289), one test is failing: https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... {code} [INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s] !ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037 !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved: !SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037 !MESSAGE Bundle initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/ was not resolved. !SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037 !MESSAGE Missing imported package org.junit.runner.notification_4.0.0. !SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037 !MESSAGE Missing imported package org.junit.runner_4.0.0. {code} Guessing the problem is that the test depends on junit4 but the manifest states only junit (not junit4). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

6
20
0 / 0

[JBoss JIRA] (JBIDE-10390) Support working copy changes in the JAX-RS plugin

by Xavier Coulon (Created) (JIRA)

Support working copy changes in the JAX-RS plugin ------------------------------------------------- Key: JBIDE-10390 URL: https://issues.jboss.org/browse/JBIDE-10390 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.M5 The JAX-RS core plugin should support both changes in the primary copies and in the working copies (ie, the changes done in the Java Editor). As a side effect, the URI Path Templates and other attributes of the JAX-RS endpoints shown in the project explorer should be updated as the user changes his code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
3
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 February 2012