January 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (RHDS-345) Language correction

by Svetlana mukhina (JIRA)

Language correction ------------------- Key: RHDS-345 URL: http://jira.jboss.com/jira/browse/RHDS-345 Project: Red Hat Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.0.0.CR1 Reporter: Svetlana mukhina Assigned To: Svetlana mukhina Fix For: 1.1 spelling and grammar mistakes should be checked in all guides -- 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

1
14
0 / 0

[JBoss JIRA] Created: (JBDS-727) Dev jira tasks review for Tools 3.1.0 release

by Svetlana mukhina (JIRA)

Dev jira tasks review for Tools 3.1.0 release --------------------------------------------- Key: JBDS-727 URL: https://jira.jboss.org/jira/browse/JBDS-727 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.0.1 Review all dev tasks mark as affects documentation, create corresponding doc tasks to document changes made by dev team. -- 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

1
162
0 / 0

[JBoss JIRA] Created: (JBIDE-4927) There isa no way to edit JMX Connection properties in MBean Explorer

by Denis Golovin (JIRA)

There isa no way to edit JMX Connection properties in MBean Explorer -------------------------------------------------------------------- Key: JBIDE-4927 URL: https://jira.jboss.org/jira/browse/JBIDE-4927 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jmx Affects Versions: 3.1.0.M4 Reporter: Denis Golovin -- 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
8
0 / 0

[JBoss JIRA] Created: (JBDS-973) Splash Screen has wrong Version

by Vlado Pakan (JIRA)

Splash Screen has wrong Version ------------------------------- Key: JBDS-973 URL: https://jira.jboss.org/jira/browse/JBDS-973 Project: JBoss Developer Studio Issue Type: Bug Components: ui/branding Affects Versions: 2.1.1 Environment: Linux 32 bit Reporter: Vlado Pakan Splash screen displayed when Studio is starting has wrong version number 2.1.0 GA instead 2.1.1 GA. -- 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

6
11
0 / 0

[JBoss JIRA] Created: (JBDS-950) Refactoring of Managed Bean/Methods/Properties which are used in ELs

by Svetlana mukhina (JIRA)

Refactoring of Managed Bean/Methods/Properties which are used in ELs -------------------------------------------------------------------- Key: JBDS-950 URL: https://jira.jboss.org/jira/browse/JBDS-950 Project: JBoss Developer Studio Issue Type: Task Components: Doc - JSFTools, Doc - RHDS GSG, Doc - Seam Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc /trunk/documentation/whatsnew/seam/seam-news-3.1.0.M4.html: "Rename action for Seam Components/Methods/Properties: Rename action for Seam Components/Methods/Properties also shows all resources that has references renamed element in EL Rename actions are available: * from context menu on a Seam component inside Seam Components View * from context menu on a method/property in Java Source editor" also see the linked task -- 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

2
8
0 / 0

[JBoss JIRA] Created: (JBDS-1066) rendering unknown tags in VPE Template dialog

by Svetlana mukhina (JIRA)

rendering unknown tags in VPE Template dialog --------------------------------------------- Key: JBDS-1066 URL: https://jira.jboss.org/jira/browse/JBDS-1066 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Doc - VisualWebTools, Doc - RHDS GSG Affects Versions: 3.0.0.CR1 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 3.0.0.CR2-doc see the linked tasks, update VPE section -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-835) Cannot create WS artifacts for POJO when in default package

by Shaun Appleton (JIRA)

Cannot create WS artifacts for POJO when in default package ----------------------------------------------------------- Key: JBDS-835 URL: https://jira.jboss.org/jira/browse/JBDS-835 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Shaun Appleton You cannot create a webservice from a simple pojo which is in the default package. I note there is a warning on the Web Service Dialog box - ! The service implementation selected does not follow Java naming conventions. But it still allows you to progress. until you get the following - log4j:WARN No appenders could be found for logger (org.jboss.wsf.framework.DefaultSPIProvider). log4j:WARN Please initialize the log4j system properly. Error: Could not generate. (use --show-traces to see full traces) Error: Cannot obtain @WebService annotation from: myPojo I can't see anything in the docs[1] to prohibit this. [1] http://download.jboss.org/jbosstools/nightly-docs/en/ws_ref_guide/html_si... -- 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

6
20
0 / 0

[JBoss JIRA] Created: (JBDS-1047) JBDS 3.0 CR1, can a check be made when running from the command line to install as root

by Jim Tyrrell (JIRA)

JBDS 3.0 CR1, can a check be made when running from the command line to install as root --------------------------------------------------------------------------------------- Key: JBDS-1047 URL: https://jira.jboss.org/jira/browse/JBDS-1047 Project: JBoss Developer Studio Issue Type: Feature Request Components: installer Environment: Linux JDK 6 Reporter: Jim Tyrrell When I ran the installer I was not paying attention and ran it as root, it ended up installed in /usr/local/jbdevstudio3cr1. I then tried to run the uninstaller and was left with a few items in the Applications -> Programming Main menu as seen in the attached screen shot. Should we check to see if you are trying to install as root on linux. It also seemed that I was not able to have any servers available in the server view, although I am not sure if that is a first time running the cr1 installer error as seemed to have happened on my mac, where I never run as root. Now that I have installed once there is no way to test this hypothesis. -- 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
17
0 / 0

[JBoss JIRA] Created: (JBIDE-5744) Deadlock after CSS editor usage

by Krasimir Goutcev (JIRA)

Deadlock after CSS editor usage ------------------------------- Key: JBIDE-5744 URL: https://jira.jboss.org/jira/browse/JBIDE-5744 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: Win 2003 Server JBT - 3.1.0.v201001262102N-H170-CR2 Reporter: Krasimir Goutcev Fix For: 3.1.0.CR2 for reproduce this for test case you should : 1.place cursor in <rich:menuItem ... /> 2.in Properties view click on row "iconStyle" 3. click on button "..." 4.Click "Ok" button only restart eclipse will help. -- 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

7
40
0 / 0

[JBoss JIRA] Created: (JBIDE-5143) ClassCastException when create f:selectItem inside h:selectManyListBox

by Yura Zhishko (JIRA)

ClassCastException when create f:selectItem inside h:selectManyListBox ---------------------------------------------------------------------- Key: JBIDE-5143 URL: https://jira.jboss.org/jira/browse/JBIDE-5143 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.1.0.M4 Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Minor 1) Open attached page with VPE. 2) Find any line that contains f:selectItem and comment it. RESULT: During visual DOM building next exception occurs: java.lang.ClassCastException: $Proxy26 at org.jboss.tools.jsf.vpe.jsf.template.selectitem.AbstractSelectItemTemplate.processOutputAttribute(AbstractSelectItemTemplate.java:99) at org.jboss.tools.jsf.vpe.jsf.template.selectitem.AbstractOptionSelectItemTemplate.create(AbstractOptionSelectItemTemplate.java:67) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:489) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:689) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:235) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.rebuildDom(VpeVisualDomBuilder.java:263) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:987) at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:661) at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:489) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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) -- 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

5
19
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 January 2010