September 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4402) Some input files use unchecked or unsafe operations. Recompile with -Xlint:unchecked for details.

by Nick Boldt (JIRA)

Some input files use unchecked or unsafe operations. Recompile with -Xlint:unchecked for details. ------------------------------------------------------------------------------------------------- Key: JBIDE-4402 URL: https://jira.jboss.org/jira/browse/JBIDE-4402 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 3.1.0.M1 Reporter: Nick Boldt http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-2.... [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. Suggest reviewing your sources w/ PDE API Tools and compiling locally to see what these unsafe/unchecked operations are. -- 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

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-729) generate plugin dependencies in eclipse.ini/config.ini rather than hardcoding versions

by Nick Boldt (JIRA)

generate plugin dependencies in eclipse.ini/config.ini rather than hardcoding versions -------------------------------------------------------------------------------------- Key: JBDS-729 URL: https://jira.jboss.org/jira/browse/JBDS-729 Project: Developer Studio Issue Type: Bug Affects Versions: 2.0.1 Reporter: Nick Boldt Assignee: Denis Golovin >From Denis: > Bumped in JBDS launch problem, the reason is - migration to Eclipse 3.5 wasn't done for installer. Fixed for linux version, but need find a way to update original config.ini/eclipse.ini files during build adding xsl.transformation plug-ins in it without keeping a copies of ini files -- 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

16 years, 4 months

3
22
0 / 0

[JBoss JIRA] Created: (JBIDE-4611) To aid in test automation - always have a descriptive title for dialogs

by Len DiMaggio (JIRA)

To aid in test automation - always have a descriptive title for dialogs ----------------------------------------------------------------------- Key: JBIDE-4611 URL: https://jira.jboss.org/jira/browse/JBIDE-4611 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: QA Reporter: Len DiMaggio Fix For: 2.1.3 I'm developing EGT tests for JBDS-BRMS and have hit a limitation with SWTBot - the tool can only extract title text from eclipse dialogs. As a result, any dialogs that have blank title text cannot be reliably located. See the attached screenshots - the 'error' dialog has a title that can be found by SWTBot - but a better title would make test automation easier. The properties dialog has blank text in its title. -- 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

16 years, 4 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4825) Replace "Apache ODE " from all labels in BPEL plugin code with "JBoss BPEL "

by Denny Xu (JIRA)

Replace "Apache ODE " from all labels in BPEL plugin code with "JBoss BPEL " ----------------------------------------------------------------------------- Key: JBIDE-4825 URL: https://jira.jboss.org/jira/browse/JBIDE-4825 Project: Tools (JBoss Tools) Issue Type: Task Components: bpm Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.1.0.M3 -- 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

16 years, 4 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3690) Incorrect styleClass is applying for the tags, which use <span> wrapping

by Yura Zhishko (JIRA)

Incorrect styleClass is applying for the tags, which use <span> wrapping ------------------------------------------------------------------------ Key: JBIDE-3690 URL: https://jira.jboss.org/jira/browse/JBIDE-3690 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.0.0.CR2 Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) Insert next source code into source path: <%@ taglib uri="http://richfaces.org/rich" prefix="rich"%> <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %> <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %> <%@ taglib uri="http://richfaces.org/a4j" prefix="a4j" %> <html> <head> <style type="text/css"> span{ color: yellow; background-color:green; } </style> </head> <body style="text-align: center"> <f:view> <h:form id="form1"> <h:outputText value="Command Link"></h:outputText> <f:verbatim>Exit</f:verbatim> <a4j:commandLink action="None" value="Begining"/> <a4j:htmlCommandLink value="Going throw"></a4j:htmlCommandLink> <h:message for="form1" /> <h:messages /> </h:form> </f:view> </body> </html> 2) Compare Visual representation in VPE to Server side (see screenshot-1). RESULT: This difference occurs due to wrapping with <span> tag of current tags. And our VPE renders this style OK. But browser doesn't wrap this tag in <span>. -- 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

16 years, 4 months

5
20
0 / 0

[JBoss JIRA] Created: (JBIDE-4946) Tool tip for tag/attributes in XHTML editor.

by Alexey Kazakov (JIRA)

Tool tip for tag/attributes in XHTML editor. -------------------------------------------- Key: JBIDE-4946 URL: https://jira.jboss.org/jira/browse/JBIDE-4946 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.1.0.M4 The idea is adding tool tips for tags/attributes in XHTM editor as WTP does for JSP editor. We can get info for tool tips from KB. -- 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

16 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4320) ESB Projects does not respect WTP module dependency rules

by Vincent Girard-Reydet (JIRA)

ESB Projects does not respect WTP module dependency rules --------------------------------------------------------- Key: JBIDE-4320 URL: https://jira.jboss.org/jira/browse/JBIDE-4320 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.GA Environment: Windows XP, Eclipse Ganymede 3.4.2 Reporter: Vincent Girard-Reydet Description of the problem ***************************** It is not possible to include modules as dependencies of a JBossESB module. The expected behaviour is that ESB modules should behave as EAR modules. For example, if I want to mimick the webservice_consumer quickstart structure using WTP projects, I expect to end-up with 2 projects : - an ESB project - a Dynamic Web Module project, set as dependency of the ESB project The expected behaviour is to have the .war archive copied at the root of the ESB archive. The same applies for EJB/EJB3 projects (to mimick the helloworld_service quickstart), JPA projects and Utility projects. -- 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

16 years, 4 months

4
31
0 / 0

[JBoss JIRA] Created: (JBIDE-4931) 'Preview' button in 'Edit XPath' dialog throws exception

by Denis Golovin (JIRA)

'Preview' button in 'Edit XPath' dialog throws exception -------------------------------------------------------- Key: JBIDE-4931 URL: https://jira.jboss.org/jira/browse/JBIDE-4931 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 3.1.0.M4 Reporter: Denis Golovin 1. EXECUTE: Create JBoss AS Server and expand XMP COnfiguration/Ports node in JBoss Servre View 2. EXECUTE: Select 'Edit XPath' form popup menu on JBoss Web child node 3. EXECUTE: Press 'Preview' 4. ASSERT: There is no exceptions in Error Log View now it throws exception showed below org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.SWT.error(SWT.java:3799) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.jboss.ide.eclipse.as.ui.dialogs.XPathDialogs$XPathDialog.previewPressed(XPathDialogs.java:411) at org.jboss.ide.eclipse.as.ui.dialogs.XPathDialogs$XPathDialog$7.widgetSelected(XPathDialogs.java:302) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.ide.eclipse.as.ui.views.server.extensions.XPathActionProvider$4.run(XPathActionProvider.java:145) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) Caused by: java.lang.NullPointerException at org.jboss.ide.eclipse.as.ui.dialogs.XPathDialogs$XPathDialog$8$1.run(XPathDialogs.java:405) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 44 more -- 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

16 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-1012) Failed to delete project

by Slava Litskevich (JIRA)

Failed to delete project ------------------------ Key: JBIDE-1012 URL: http://jira.jboss.com/jira/browse/JBIDE-1012 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta4 Environment: RHDS 1.0.0 beta 2 JDK 1.5.0_12 Reporter: Slava Litskevich Fix For: 2.0.0.Beta4 Create new Seam Web Project: 1. File -> New -> Seam Web Project: new project dialog opens 2. Specifiy project name -> Next 3. Mark "Java Persistence" -> Next -> Next -> Next 4. Mark "Server Supplied JSF Implementation" -> Next -> Finish 5. File -> New -> Seam Generate Entities Try to delete the project with the project content: 6. Rightclick the project -> Delete -> choose to delete the project content Deletion fails. Error message dialog appears. Details window content: Problems encountered while deleting resources. Could not delete '/aa3'. Problems encountered while deleting resources. Problems encountered while deleting files. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-ui.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-ioc.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-pdf.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-remoting.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-mail.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-debug.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\oscache-2.3.2.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-digester-1.6.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jbpm-3.1.4.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\ajax4jsf-1.1.1-SNAPSHOT.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-collections-3.1.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jsf-facelets.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-beanutils-1.7.0.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\janino-2.4.3.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-jci-janino-2.4.3.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\antlr-2.7.6.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\antlr-3.0ea8.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-jci-core-1.0-406301.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\drools-compiler-3.0.5.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\drools-core-3.0.5.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\stringtemplate-2.3b6.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\hsqldb.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent. Could not delete: D:\projects\workspace\seam-rhds\aa3. Problems encountered while deleting files. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-ui.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-ioc.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-pdf.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-remoting.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-mail.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jboss-seam-debug.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\oscache-2.3.2.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-digester-1.6.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jbpm-3.1.4.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\ajax4jsf-1.1.1-SNAPSHOT.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-collections-3.1.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\jsf-facelets.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-beanutils-1.7.0.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\janino-2.4.3.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-jci-janino-2.4.3.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\antlr-2.7.6.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\antlr-3.0ea8.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\commons-jci-core-1.0-406301.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\drools-compiler-3.0.5.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\drools-core-3.0.5.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\stringtemplate-2.3b6.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib\hsqldb.jar. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF\lib. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent\WEB-INF. Could not delete: D:\projects\workspace\seam-rhds\aa3\WebContent. Could not delete: D:\projects\workspace\seam-rhds\aa3. -- 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

16 years, 4 months

7
32
0 / 0

[JBoss JIRA] Created: (JBIDE-4647) new JSF Project on tomcat 6.0.20 generates doubled el-api.jar and causes LinkageError

by Tomasz Bartczak (JIRA)

new JSF Project on tomcat 6.0.20 generates doubled el-api.jar and causes LinkageError ------------------------------------------------------------------------------------- Key: JBIDE-4647 URL: https://jira.jboss.org/jira/browse/JBIDE-4647 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.M2 Environment: eclipse galileo 20090621-0832, Vista Reporter: Tomasz Bartczak Created a new JSF Project with FaceletsKickStartRI and chosen a fresh tomcat 6.0.20. java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ELResolver used in the signature when starting server and this app. and i cannot see an option of removing el-api.jar from web app libraries. instead i had to remove jar from tomcat when I did that I had class not found ! java.lang.NoClassDefFoundError: javax/el/ExpressionFactory I think because of tomcat needs it on its internal classpath... so there is no solution! -- 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

16 years, 4 months

3
6
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 2009