November 2008 - jbosstools-issues

[JBoss JIRA] Updated: (JBIDE-351) Clean out bad exception handling

by Denis Golovin (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-351?page=com.atlassian.jira.plug... ] Denis Golovin updated JBIDE-351: -------------------------------- Fix Version/s: 3.1.0 (was: 3.0.0.cr1) > Clean out bad exception handling > -------------------------------- > > Key: JBIDE-351 > URL: https://jira.jboss.org/jira/browse/JBIDE-351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 3.1.0 > > > weed out all ex.printStackTrace() by either > a) remove them (and their catch clause) > b) replace them with log to the error log > There is waay to many of them ;) -- 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

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-3139) CLONE -Unnecessary "Restore Defaults" and "Apply" buttons on JBoss Tools and jBPM preferences pages.

by Koen Aers (JIRA)

CLONE -Unnecessary "Restore Defaults" and "Apply" buttons on JBoss Tools and jBPM preferences pages. ---------------------------------------------------------------------------------------------------- Key: JBIDE-3139 URL: https://jira.jboss.org/jira/browse/JBIDE-3139 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 2.1.0.GA Reporter: Koen Aers Assignee: Koen Aers Priority: Minor Fix For: 3.0.0.cr1 EXECUTE: Window -> Preferences ->JBoss jBPM FAILURE: Unnecessary buttons on the page EXECUTE: Window -> Preferences ->JBoss Tools FAILURE: Unnecessary buttons on the page Screenshots attached/ -- 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

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-3138) CLONE -jBPM Task Reminder can't update processdefinition.xml

by Koen Aers (JIRA)

CLONE -jBPM Task Reminder can't update processdefinition.xml ------------------------------------------------------------ Key: JBIDE-3138 URL: https://jira.jboss.org/jira/browse/JBIDE-3138 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 2.1.2, 3.0.0.alpha Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.0.0.cr1 After I input data in Task Reminder, the source was not updated. -- 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

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-3082) Seam Validator runs even when set to IGNORE

by Chris Simons (JIRA)

Seam Validator runs even when set to IGNORE ------------------------------------------- Key: JBIDE-3082 URL: https://jira.jboss.org/jira/browse/JBIDE-3082 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.GA Environment: Windows XP SP2; 2 GB RAM; Eclipse Version: 3.3.1.1Build id: M20071023-1652; JBoss Tools 3.0.0GA; Seam 2.0.GA Reporter: Chris Simons All project-level Seam Validator settings are set to IGNORE. However, since 3.0.0GA of JBoss Tools, the Seam Validator runs whenever I save a Java or XHTML file. The Validator process can be stopped, but then launches into multiple instances of itself. The Seam Validator is less resource intensive than in previous releases, but can still bog down Eclipse/JBoss Tools - cause a stutter of about 5 seconds whenever it kicks off. ** Personally, I dont see the Seam Validator as being all that useful. -- 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

17 years, 5 months

3
13
0 / 0

[JBoss JIRA] Created: (JBIDE-3095) Normal page doesn't be allow display the "Mapping" ResourceConfig elements.

by Xue Peng (JIRA)

Normal page doesn't be allow display the "Mapping" ResourceConfig elements. --------------------------------------------------------------------------- Key: JBIDE-3095 URL: https://jira.jboss.org/jira/browse/JBIDE-3095 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.0.0.cr1 Reporter: Xue Peng Assignee: Xue Peng Fix For: 3.0.0.cr1 Normal page doesn't be allow display the "Mapping" ResourceConfig elements. But now the normal page show all resourceconfig elements on the panel. -- 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

17 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-2988) Handling unsupported/incomplete/incorrect Smooks configuration files

by John Graham (JIRA)

Handling unsupported/incomplete/incorrect Smooks configuration files -------------------------------------------------------------------- Key: JBIDE-2988 URL: https://jira.jboss.org/jira/browse/JBIDE-2988 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: John Graham Assignee: Xue Peng Priority: Critical Fix For: 3.0.0.beta1 When the Smooks editor can not read a smooks configuration file for whatever reason (whether it is not a correct file, incomplete, or contains configuration elements not supported by the editor), the editor should: a. Pop up a dialog saying that the file could not be processed. If the load exception gives any indication/message that might be useful, include that in the dialog too. b. Open a text editor with the file contents. -- 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

17 years, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3040) ESB projects does not have a module icon

by Max Rydahl Andersen (JIRA)

ESB projects does not have a module icon ---------------------------------------- Key: JBIDE-3040 URL: https://jira.jboss.org/jira/browse/JBIDE-3040 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.0.0.beta1 Reporter: Max Rydahl Andersen Fix For: 3.0.0.beta1 Ear, War, Utility jar etc module types in WTP all have a unique overlay icon; shouldn't ESB projects have that too ? Do we have an ESB module or is it just a facet ? -- 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

17 years, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2742) 4.0.x servers should add JDK_HOME/lib/tools.jar, otherwise jmx-console might be broken

by Galder Zamarreno (JIRA)

4.0.x servers should add JDK_HOME/lib/tools.jar, otherwise jmx-console might be broken -------------------------------------------------------------------------------------- Key: JBIDE-2742 URL: https://jira.jboss.org/jira/browse/JBIDE-2742 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.alpha Reporter: Galder Zamarreno jmx-console access for AS 4.0.1.SP1 (for example) instances started via JBDS is broken. When you try to access the jmx-console, you get: ype Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: Unable to compile class for JSP org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:97) org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:346) org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:414) org.apache.jasper.compiler.Compiler.compile(Compiler.java:472) org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) root cause Unable to find a javac compiler; com.sun.tools.javac.Main is not on the classpath. Perhaps JAVA_HOME does not point to the JDK org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.getCompiler(CompilerAdapterFactory.java:105) org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:929) org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758) org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:382) org.apache.jasper.compiler.Compiler.compile(Compiler.java:472) org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) I don't get this issue when I start up via run.sh. Why? I suspect that run.sh adds lib/tools.jar to the classpath as shown in boot-normal.log [galder@dhcp-144-245 jdk1.5.0_12]$ find . -name "*.jar" | xargs grep com/sun/tools/javac/Main Binary file ./lib/tools.jar matches grep -nH -e "lib/tools.jar" boot-normal.log boot-normal.log:78:11:20:32,723 DEBUG [ServerInfo] java.class.path: /home/galder/access/as-rel/4.0.1.sp1/bin/run.jar:/usr/java/jdk1.5.0_12/lib/tools.jar Whereas when started from JBDS does not: grep -nH -e "lib/tools.jar" boot-jbds.log Grep finished with no matches found at Mon Sep 8 11:28:39 Please find attached both boot.log files. IMO, JBDS should be more conservative just like run.sh is which requires pointing to a JDK vs a JRE, at least for the 4.0.x series. I think you can get away with using a JRE for 4.2 or 4.3 but I'm not sure. -- 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

17 years, 5 months

3
6
0 / 0

[JBoss JIRA] Commented: (JBIDE-558) Use Ivy as foundation for libmanagement tool

by Francisco Jose Peredo Noguez (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-558?page=com.atlassian.jira.plug... ] Francisco Jose Peredo Noguez commented on JBIDE-558: ---------------------------------------------------- I like this idea a lot, but I only hope Ivy 2.0 finally gets released in the not so distant future > Use Ivy as foundation for libmanagement tool > -------------------------------------------- > > Key: JBIDE-558 > URL: https://jira.jboss.org/jira/browse/JBIDE-558 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: libmanagement > Reporter: Max Rydahl Andersen > Fix For: LATER > > > Ivy is non-intrusive, ant and maven compatible and it is very pluggable. > For libraries there does not exist pom's/ivy-xml we can create them and have an rhds-ivy lib, it handles multiple configuration (usefull for hibernate) and it supports just copying to local lib dir ...all good. > Links: > main site: http://incubator.apache.org/ivy/ > classpath container in eclipse: http://incubator.apache.org/ivy/ivyde/cp_container.html (right direction, but needs more) > still not solved: > how to handle related javadoc and source attachements ? -- 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

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-1372) JSF project validation error

by Aliaksey Nis (JIRA)

JSF project validation error ---------------------------- Key: JBIDE-1372 URL: http://jira.jboss.com/jira/browse/JBIDE-1372 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.CR1 Reporter: Aliaksey Nis Priority: Minor 1.Create JSF 1.2 KickStart project. 2. While validation take place - add custom capabilities. NPE appears. *** ERROR ***: Mon Nov 26 18:47:13 EET 2007 org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescriptorLoadException: WEB-INF/web.xml Stack trace of nested exception: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.EmptyResourceException: platform:/resource/hhk/WebContent/WEB-INF/web.xml at org.eclipse.jst.j2ee.commonarchivecore.internal.util.ArchiveUtil.getRoot(ArchiveUtil.java:440) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.XmlBasedImportStrategyImpl.primLoadDeploymentDescriptor(XmlBasedImportStrategyImpl.java:42) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.War22ImportStrategyImpl.loadDeploymentDescriptor(War22ImportStrategyImpl.java:87) at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.War22ImportStrategyImpl.importMetaData(War22ImportStrategyImpl.java:81) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.getDeploymentDescriptor(WARFileImpl.java:145) at org.eclipse.jst.j2ee.model.internal.validation.WarValidator.validateInJob(WarValidator.java:328) at org.eclipse.jst.j2ee.internal.web.validation.UIWarValidator.validateInJob(UIWarValidator.java:111) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

17 years, 5 months

5
10
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 November 2008