February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1551) Spring Chapter in Visual Web Tools Document is wrong at all

by Vlado Pakan (JIRA)

Spring Chapter in Visual Web Tools Document is wrong at all ----------------------------------------------------------- Key: JBDS-1551 URL: https://issues.jboss.org/browse/JBDS-1551 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: documentation Affects Versions: 4.0.0.CR1 Reporter: Vlado Pakan Spring documentation http://download.jboss.org/jbosstools/nightly-docs/en/jsf/html/springTools... has broken almost all the links to Spring documents -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDS-1535) [Getting Started Guide] Download link is to EOL version of Java

by Andrew Ross (JIRA)

[Getting Started Guide] Download link is to EOL version of Java --------------------------------------------------------------- Key: JBDS-1535 URL: https://issues.jboss.org/browse/JBDS-1535 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: documentation Affects Versions: 4.0.0.CR2 Reporter: Andrew Ross Version: JBoss_Developer_Studio-Getting_Started_Guide-4.0-web-en-US-4.0.0-8.el5 Document links to J2SE 5.0 with EOL Nov 2009. 3.1.1. Installing and Configuring 32-bit Sun JDK 5.0 on Linux "Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's website. " Links to http://www.oracle.com/technetwork/java/javase/downloads/index-jdk5-jsp-14... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1544) Errors in JSF Reference Guide

by Vlado Pakan (JIRA)

Errors in JSF Reference Guide ----------------------------- Key: JBDS-1544 URL: https://issues.jboss.org/browse/JBDS-1544 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Doc - JSFTools Affects Versions: 4.0.0.CR1 Reporter: Vlado Pakan There are these errors in JSF Reference Guide http://download.jboss.org/jbosstools/nightly-docs/en/jsf_tools_ref_guide/... Figure 2.1. Choosing JSF Environment and Figure 2.2. Choosing Facelets Environment and Figure 3.2. Creating a New JSF Project - combo box JSF Environment now contains also "JSF" 2.0 item Figure 3.1. Choosing a JSF Project - JSF node now has new child with label "Faces Config" Figure 3.3. Choosing JSF Templates - Templates combo box has less items than on screenshot Figure 3.6. Adding JSF Capabilities - context menu has some new menu items Figure 5.4. Creating a New View - menu item "Rule" has now label "New View" Figure 5.10. Creating a New Custom Converter - menu items have labels "with id" and "for class" Figure 6.6. "Add Property" Form - Value Text widget now has SWT.MULTI style with scroll bars Figure 7.4. New Java Class Form and Figure 7.9. New Java Class Form - there is missing displayed interface class name in New Java Class wizard screenshot -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-121) JBDS40_006 Smooks: Direct Source to Target

by Isaac Rooskov (JIRA)

JBDS40_006 Smooks: Direct Source to Target ------------------------------------------ Key: TOOLSDOC-121 URL: https://jira.jboss.org/browse/TOOLSDOC-121 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Reporter: Isaac Rooskov Assignee: Isaac Rooskov Tracker for docs on this issue. Current status: Uncommitted -- 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, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-75) Incorrect ESB versions and/or examples in ESB Guide

by Libor Zoubek (JIRA)

Incorrect ESB versions and/or examples in ESB Guide ---------------------------------------------------- Key: TOOLSDOC-75 URL: https://jira.jboss.org/jira/browse/TOOLSDOC-75 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation , esb Affects Versions: 3.0.0.GA Reporter: Libor Zoubek I followed ESB Tools Reference guide http://docs.jboss.org/tools/3.1.0.GA/en/esb_ref_guide/html_single/index.html. I set up Jboss AS 4.2 with ESB 4.7 and tried to run HelloWorld Example (and client) as written in section 2.3. The problem is, that helloWorld examples did not work. ESB archive did not deploy at all. So I tried to install ESB 4.7 into EAP 5. Archive was deployed, but the client worked only partly. Then I figured out, that I was using bad examples. Because ESB 4.7 is part of SOA-P 5, examples found in wizard in tree 'ESB -> JBoss ESB HelloWorld Example' are not expected to work with it. Guide should update Figure 2.7 and change the screenshot selecting from 'ESB for SOA-P 5.0 -> Jboss ESB HelloWorld Example' which works fine. These are same examples, but 'written' and hopefully verified on ESB 4.7. Also there should be some note about which examples to select with which versions. -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6315) Shrinkwrap output visualization

by Pete Muir (JIRA)

Shrinkwrap output visualization ------------------------------- Key: JBIDE-6315 URL: https://jira.jboss.org/browse/JBIDE-6315 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Reporter: Pete Muir When writing packaging descriptions (e.g. via Shrinkwrap or traditionally via Ant/Maven), you often want to view what the generated artifact looks like so you can check where a particular file is placed. Provide a visualization of the current Shrinkwrap, this should view just like the package explorer in eclipse (consistency!) and update in realtime as someone alters their shrinkwrap declaration. Having a filter would be useful as well. -- 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, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6314) NPE on every start of eclipse

by Krasimir Goutcev (JIRA)

NPE on every start of eclipse ----------------------------- Key: JBIDE-6314 URL: https://jira.jboss.org/browse/JBIDE-6314 Project: Tools (JBoss Tools) Issue Type: Bug Environment: nightly build 201005181730 java.version=1.6.0_16 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=bg_BG Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -clean Reporter: Krasimir Goutcev An internal error occurred during: "JBoss Tools Model Update". log: java.lang.NullPointerException at java.util.zip.ZipFile.getInputStream(ZipFile.java:180) at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:200) at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:235) at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:90) at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:74) at org.jboss.tools.common.model.filesystems.impl.JarSystemImpl.loadChildren(JarSystemImpl.java:46) at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildByPathPart(RegularObjectImpl.java:140) at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.getChildByPathPart(JarFolderImpl.java:131) at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:335) at org.jboss.tools.jst.web.tld.TaglibMapping.findTldsInJar(TaglibMapping.java:224) at org.jboss.tools.jst.web.tld.TaglibMapping.findTldsInJars(TaglibMapping.java:208) at org.jboss.tools.jst.web.tld.TaglibMapping.revalidate(TaglibMapping.java:84) at org.jboss.tools.jsf.web.JSFWatcherContributor.updateProject(JSFWatcherContributor.java:49) at org.jboss.tools.common.model.project.Watcher.updateAll(Watcher.java:106) at org.jboss.tools.common.model.project.Watcher.access$0(Watcher.java:89) at org.jboss.tools.common.model.project.Watcher$WatcherRunnable.run(Watcher.java:47) at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:158) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) 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: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-4601) JBoss Profiler throws NPE when Profile > Profile Configurations... dialog is launched for a Main class

by Nick Boldt (JIRA)

JBoss Profiler throws NPE when Profile > Profile Configurations... dialog is launched for a Main class ------------------------------------------------------------------------------------------------------ Key: JBIDE-4601 URL: https://jira.jboss.org/jira/browse/JBIDE-4601 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M2 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Steps to repro: a) install Eclipse 3.5 b) install JBoss Profiler feature from update site http://download.jboss.org/jbosstools/updates/nightly/3.1.0.M2/ c) restart Eclipse d) create a Java project, eg., foobar e) create a Main class in that project, eg., foo.bar.Main f) put this in Main.java: package foo.bar; public class Main { /** * @param args */ public static void main(String[] args) { System.out.println("Hello, Foo!"); } } f) debug the class: right-click in the file and Debug As > Java Application g) add a breakpoint on the println() line h) debug again, this time switching to the Debug perspective when prompted i) right-click in class file, Debug As > Debug Configurations... j) note the new JBoss Profiler tab for your Java Application > Main launch configuration. Close the dialog. k) right-click in class file, Profile As > Profile Configurations... l) note three error dialogs. -- 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, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3557) Externalise English strings (move them from source code into .properties)

by Sean Flanigan (JIRA)

Externalise English strings (move them from source code into .properties) ------------------------------------------------------------------------- Key: JBIDE-3557 URL: https://jira.jboss.org/jira/browse/JBIDE-3557 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Cleanup Reporter: Sean Flanigan Assignee: Sean Flanigan Much of the English text in JBoss Tools is already externalised into .properties files, but my pseudolocalisation testing [1] shows that there is still some hard-coded English text, particularly in files like plugin.xml and feature.xml, but also in parts of the Java source. Any such English text needs to be moved out of the source code into .properties files, and replaced by ResourceBundle lookups. - In the case of plugin.xml or Java source, Eclipse's "Externalize Strings" wizard can help. In most cases, if a plugin already has a ResourceBundle, for instance org.jboss.tools.{plugin}.Messages, it is best to reuse this bundle, rather than creating another one for each package in the bundle. (More bundles create more work for translators.) - In the case of feature.xml, there doesn't seem to be an Eclipse wizard, so externalisation has to be done by hand. [1] Running JBoss Tools together with Eclipse's Babel langpacks, plus the JBoss Tools langpacks. http://www.jboss.org/community/docs/DOC-13256 -- 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, 7 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-4044) Review unused strings from Messages classes as reported by UCDetector

by Sean Flanigan (JIRA)

Review unused strings from Messages classes as reported by UCDetector --------------------------------------------------------------------- Key: JBIDE-4044 URL: https://jira.jboss.org/jira/browse/JBIDE-4044 Project: Tools (JBoss Tools) Issue Type: Task Components: Cleanup Affects Versions: 3.1.0 Reporter: Sean Flanigan I've run UCDetector [1] against the codebase, and it has found 294 fields in *Messages classes which have 0 references. I've attached a list (views well in oocalc). I'd like to remove them, along with their corresponding resourcebundle properties, to reduce the number of translatable strings before localisation begins. I think it should be safe to remove these fields, since any direct usage will be caught by the compiler as soon as we try to remove it (and wouldn't have been listed by UCDetector anyway, unless it is completely broken), and it would be extremely unlikely for anyone to access a Messages field by reflection. If you want to run UCDetector yourself, select one or more plugin projects (not features, not non-Java projects), select UCDetector/Detect unnecessary code, and wait. I recommend configuring Eclipse's Problems view to show problems of type "UCDetector Marker (References)" whose description contains 'Field "'. The relevant problems are of the form 'Field SomethingMessages.SOME_KEY" has 0 references'. [1] http://ucdetector.sourceforge.net/ -- 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, 7 months

10
30
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 2011