April 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-9941) Recognize and define ESB Runtime from SOA-P product

by Vlado Pakan (Created) (JIRA)

Recognize and define ESB Runtime from SOA-P product --------------------------------------------------- Key: JBIDE-9941 URL: https://issues.jboss.org/browse/JBIDE-9941 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime detection Affects Versions: 3.2.1.M1 Reporter: Vlado Pakan Assignee: Snjezana Peco Priority: Critical Fix For: 3.2.2.M1, 3.3.0.M4 When searching for runtimes (Menu Window > Preferences > JBoss Tools > JBoss Tools Runtimes) SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes. Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04. JBT should automatically detect ESB Runtime within SOA-P product and define it for later use. Has to be working also with SOA-P Standalone products. -- 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

12 years, 3 months

8
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9675) ErrorLog View shows "Invalid preference page path: XML Syntax/HTML Syntax/JSP Syntax" errors after installing JBT Seam 2 Tools on Eclipse SDK

by Denis Golovin (JIRA)

ErrorLog View shows "Invalid preference page path: XML Syntax/HTML Syntax/JSP Syntax" errors after installing JBT Seam 2 Tools on Eclipse SDK --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9675 URL: https://issues.jboss.org/browse/JBIDE-9675 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.M3 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.3.0.M4 The errors appear in Error Log View after requesting context menu on any project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] (JBDS-2085) Link to download JBDS installers on JBDS early access staging update site points to nowhere

by Vlado Pakan (JIRA)

Vlado Pakan created JBDS-2085: --------------------------------- Summary: Link to download JBDS installers on JBDS early access staging update site points to nowhere Key: JBDS-2085 URL: https://issues.jboss.org/browse/JBDS-2085 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: updatesite Affects Versions: 5.0.0.Beta2 Reporter: Vlado Pakan Fix For: 5.0.0.Beta2 1. Open link https://devstudio.jboss.com/updates/5.0/staging/ 2. There is ling pointing to https://devstudio.jboss.com/updates/download/ with label 'click here to purchase or download it free'. This link is pointing to nowhere. -- 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

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-9713) jboss tools knowledge base preference page has broken/complex english

by Max Rydahl Andersen (JIRA)

jboss tools knowledge base preference page has broken/complex english --------------------------------------------------------------------- Key: JBIDE-9713 URL: https://issues.jboss.org/browse/JBIDE-9713 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common/jst/core Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Fix For: 3.3.0.M4 The text on the pref page for knowledge base is rather intense. We need to find a simpler explanation than that otherwise users will be scared to enable it ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7030) HTML highlighting and code assist in JS editor inside string variables

by Dzianis Sheka (JIRA)

HTML highlighting and code assist in JS editor inside string variables ---------------------------------------------------------------------- Key: JBIDE-7030 URL: https://jira.jboss.org/browse/JBIDE-7030 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Reporter: Dzianis Sheka Assignee: Maxim Areshkau When we develop something on JavaScript,sometimes we use the next constructions: function insert_tree_base(data) { eval("window.items=" + data + ";"); if (items && (items.length > 0)) { var s = "<table cellspacing='0' cellpadding='5' class='tree'>"; for (var i=0; i < items.length; i++) { s = s + "<tr><td valign='top' align='left'>" + window.insert_tree_build(window.items[i], 0) + "</td></tr>"; } s = s + "</table>"; jQuery("#treeFragment").append(s); } And in VPE we don't have a html highlighting inside s = s + "<tr><td valign='top' align='left'>" + window.insert_tree_build(window.items[i], 0) + "</td></tr>"; -- 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

12 years, 3 months

7
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6173) Parsing and color coding the two paned editor

by Jim Tyrrell (JIRA)

Parsing and color coding the two paned editor --------------------------------------------- Key: JBIDE-6173 URL: https://jira.jboss.org/jira/browse/JBIDE-6173 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: All Reporter: Jim Tyrrell Attachments: Screen shot 2010-04-09 at 7.05.05 PM.png If a quotation mark disappears the color coding of the facelet page should be toggled to black to help with error detection when writing code. The red x on the left is nice, but it is hard to know if things are coded correctly. The attached screen shot shows a missing quotation mark on the tag: <ui:define name=body"> It would be nice if the body text would turn black letting you know it was not parsing, or if it could be underlined in red as the possible problem. -- 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

12 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9028) Validator framework should report to log if some required builder is registered in project after validator builder

by Viacheslav Kabanovich (JIRA)

Validator framework should report to log if some required builder is registered in project after validator builder ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-9028 URL: https://issues.jboss.org/browse/JBIDE-9028 Project: Tools (JBoss Tools) Issue Type: Task Components: common Affects Versions: 3.3.0.M1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-9994) Hot deployment not working in JBT with EAP 5.1.1

by Martin Malina (Created) (JIRA)

Hot deployment not working in JBT with EAP 5.1.1 ------------------------------------------------ Key: JBIDE-9994 URL: https://issues.jboss.org/browse/JBIDE-9994 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.2.2.Final Environment: JBoss Tools 3.2.2.CR1, build H1422 Tried on Mac OS X and RHEL 6 EAP 5.1.1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.2.2.Final For some reason hot deployment doesn't seem to work with JBoss Tools, but DOES work with JBDS. Scenario: 1. Add EAP 5.1.1 server 2. Create a simple Seam Web Project MySeamProject 3. Start server and deploy MySeamProject 4. Check http://localhost:8080/MySeamProject 5. Make changes to home.xhml (e.g. change the text in <h1>) and save the document 6. Wait for publish (a few seconds) 7. Reload the browser; assert: you should see the change I don't see any change. What I don't understand is why it doesn't work for me when using JBT, but works when using JBDS. The I change the xhtml file and save it, the file in deploy/ gets changed and its mtime updated. Also the directory of the exploded war gets touched. All of this is correct, but still the changes don't get processed by EAP. -- 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

12 years, 3 months

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8629) NPE in case of only VPE plugins set use - after click on Palette View -> Import button

by Vitali Yemialyanchyk (JIRA)

NPE in case of only VPE plugins set use - after click on Palette View -> Import button -------------------------------------------------------------------------------------- Key: JBIDE-8629 URL: https://issues.jboss.org/browse/JBIDE-8629 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.3.x Reporter: Vitali Yemialyanchyk Assignee: Viacheslav Kabanovich Priority: Critical Attachments: screenshot-1 - set of plugins.jpg !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at org.jboss.tools.common.model.ui.wizards.special.DefaultSpecialWizard.getStep(DefaultSpecialWizard.java:145) at org.jboss.tools.common.model.ui.wizards.special.DefaultSpecialWizard.setStep(DefaultSpecialWizard.java:119) at org.jboss.tools.common.model.ui.wizards.special.DefaultSpecialWizard.open(DefaultSpecialWizard.java:81) at org.jboss.tools.common.model.ui.wizards.special.DefaultSpecialWizard.execute(DefaultSpecialWizard.java:64) at org.jboss.tools.common.meta.action.impl.handlers.DefaultSpecialHandler.executeHandler(DefaultSpecialHandler.java:61) at org.jboss.tools.common.meta.action.impl.XActionImpl.executeHandler(XActionImpl.java:65) at org.jboss.tools.common.model.ui.action.XModelObjectAction.actionPerformed(XModelObjectAction.java:96) at org.jboss.tools.common.model.ui.action.XModelObjectActionInvoker.execute(XModelObjectActionInvoker.java:36) at org.jboss.tools.common.meta.action.XActionInvoker.invoke(XActionInvoker.java:53) at org.jboss.tools.common.meta.action.XActionInvoker.invoke(XActionInvoker.java:33) at org.jboss.tools.vpe.ui.palette.model.PaletteModel.runImportTLDDialog(PaletteModel.java:214) at org.jboss.tools.vpe.ui.palette.PaletteAdapter$ImportTLDAction.run(PaletteAdapter.java:154) 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$6.handleEvent(ActionContributionItem.java:452) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
7
0 / 0

[JBoss JIRA] (JBIDE-9946) New Server Runtime - EAP 6 has an extra space

by Burr Sutter (Created) (JIRA)

New Server Runtime - EAP 6 has an extra space --------------------------------------------- Key: JBIDE-9946 URL: https://issues.jboss.org/browse/JBIDE-9946 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter Attachments: New_server_runtime_EAP6.png The default string for the runtime (and server) name includes an extra space "JBoss EAP 6.0 Runtime" between the 'P' and the '6'. -- 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

12 years, 3 months

5
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2012