March 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6078) Tool to support development of a BlackTie domain

by Tom Jenkinson (JIRA)

Tool to support development of a BlackTie domain ------------------------------------------------ Key: JBIDE-6078 URL: https://jira.jboss.org/jira/browse/JBIDE-6078 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: IDE Reporter: Tom Jenkinson Priority: Minor This request is in response to the open feature requests notification published on thecore The BlackTie project currently has no tooling available for it within the IDE and it would be really cool to get a tool that can help users to design their BlackTie domain. There is a schema within svn: https://anonsvn.jboss.org/repos/blacktie/trunk/blacktie-xsd/src/main/xsd/... I was thinking that a visual tool to: 1. Help users design their domain based on this schema 2. Output configuration compliant to the schema 3. Autogenerate some template services in C and Java 4. Autogenerate some ant build scripts to generate the servers based on the configuration Would be of great use to the team The tool would allow users to configure where the transaction manager, message broker, AS and databases are in their domain, which services reside at which server and the path to the generated executables. -- 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-6009) Error if a Bean VAlidation constraint is placed on an incompatible property

by Emmanuel Bernard (JIRA)

Error if a Bean VAlidation constraint is placed on an incompatible property --------------------------------------------------------------------------- Key: JBIDE-6009 URL: https://jira.jboss.org/jira/browse/JBIDE-6009 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Emmanuel Bernard ie the property returned type does not match any of the constraint validator (or more than one) according to the BV spec resolution algorithm. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1036) MySQL connection profile

by Gavin King (JIRA)

MySQL connection profile ------------------------ Key: JBIDE-1036 URL: http://jira.jboss.com/jira/browse/JBIDE-1036 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King Currently, Eclipse ships with a limited number of "Connection Profiles", we should at least have one for MySQL. This may be due to license incompatibilities, but we should at least investigate whether it is possible for us to dist the MySQL driver. -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6010) Tooling Support for Byteman Rule Injection

by Andrew Dinn (JIRA)

Tooling Support for Byteman Rule Injection ------------------------------------------ Key: JBIDE-6010 URL: https://jira.jboss.org/jira/browse/JBIDE-6010 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Andrew Dinn It would be nice to have support for Byteman in these areas: 1) editor support for creation and modification of Byteman rule files 2) debugger support for detection of successful or ailed rule injection at runtime 3) debugger support for stepping through injected rule code the byteman agent already runs a listener which provides the info required for ii. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBDS-1008) Create Shortcuts fails on 64-bit Vista

by Burr Sutter (JIRA)

Create Shortcuts fails on 64-bit Vista -------------------------------------- Key: JBDS-1008 URL: https://jira.jboss.org/jira/browse/JBDS-1008 Project: JBoss Developer Studio Issue Type: Bug Components: installer Affects Versions: 3.0.0.CR1 Reporter: Burr Sutter Attachments: Shortcuts.jpg Click the Next button produces the following stack trace on the console. The workaround is to just hit Finish instead of next (screenshot provided) Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at com.izforge.izpack.panels.ShortcutPanel.isValidated(ShortcutPanel.jav a:580) at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFra me.java:1453) at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFra me.java:1444) at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP erformed(InstallerFrame.java:1529) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:19 95) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav a:2318) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel .java:387) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242 ) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonL istener.java:236) at java.awt.Component.processMouseEvent(Component.java:6216) at javax.swing.JComponent.processMouseEvent(JComponent.java:3265) at java.awt.Component.processEvent(Component.java:5981) at java.awt.Container.processEvent(Container.java:2041) at java.awt.Component.dispatchEventImpl(Component.java:4583) at java.awt.Container.dispatchEventImpl(Container.java:2099) at java.awt.Component.dispatchEvent(Component.java:4413) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4556 ) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4220) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4150) at java.awt.Container.dispatchEventImpl(Container.java:2085) at java.awt.Window.dispatchEventImpl(Window.java:2475) at java.awt.Component.dispatchEvent(Component.java:4413) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre ad.java:269) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread. java:184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre ad.java:174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) -- 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, 8 months

7
27
0 / 0

[JBoss JIRA] Created: (JBIDE-4160) Add option in JBoss ESB Editor to disable an ESB action

by Joao Paulo Viragine (JIRA)

Add option in JBoss ESB Editor to disable an ESB action ------------------------------------------------------- Key: JBIDE-4160 URL: https://jira.jboss.org/jira/browse/JBIDE-4160 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.0.0.GA Environment: JBDS 2.0.0.GA Reporter: Joao Paulo Viragine Priority: Optional It would be great if we could disable an specific action in ESB. E.g. <action class="org.jboss.soa.esb.actions.SystemPrintln" name="Println" enabled="false"> <property name="message" value="JBoss ESB Rulez"/> </action> -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1965) display links from tiles definitions on stuts diagram (like from jsp pages)

by Alex Titov (JIRA)

display links from tiles definitions on stuts diagram (like from jsp pages) --------------------------------------------------------------------------- Key: JBIDE-1965 URL: http://jira.jboss.com/jira/browse/JBIDE-1965 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: struts/shale Affects Versions: 2.0.1 Reporter: Alex Titov Priority: Minor Stuts plugin can display links from jsp page to actions and other jsp pages on diagram. That is grate! But if you use tiles plugin you don't work with jsp pages directly. Instead you work with tiles definition. For example <definition name="..." path="/WEB-INF/jsp/template.jsp"> <put name="content" value="/WEB-INF/graph.jsp"></put> </definition> Both template.jsp and graph.jsp are jsp pages and have links but struts plugin does not understand this. So links from these pages are not displayed in struts diagram. Also it would be nice if there were way to select jsp page for "value" attribute in "put" element in tiles editor (like for "path" attribute in "definition" element). -- 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, 8 months

4
3
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, 8 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, 8 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, 8 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 March 2010