November 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1346) New Server Runtime for SOA Platform 5.2 needed

by Gary Lamperillo (JIRA)

New Server Runtime for SOA Platform 5.2 needed ---------------------------------------------- Key: JBDS-1346 URL: https://jira.jboss.org/browse/JBDS-1346 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.M2 Environment: SOA-P 5.2 and JBDS 4 M2 Reporter: Gary Lamperillo In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific internals are known and the wizard would not need to have the subsequent screens if SOA-P 5.2 is selected instead of the community release. Without a EAP 5.1 or SOA-P 5.2, the following warning appears : This server type expects a version of 5.0 but the server directory is of version 5.1.0. see screen attachments. -- 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

15 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7149) usage reporting needs a user guide / current one should get completed

by Andre Dietisheim (JIRA)

usage reporting needs a user guide / current one should get completed --------------------------------------------------------------------- Key: JBIDE-7149 URL: https://jira.jboss.org/browse/JBIDE-7149 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: usage Affects Versions: 3.2.0.M2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 There's currently a user guide on http://jboss.org/tools/usage but it lacks informations and needs screenshots. -- 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

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-1359) Importing ESB example into JBDS results in log error

by Len DiMaggio (JIRA)

Importing ESB example into JBDS results in log error ----------------------------------------------------- Key: JBDS-1359 URL: https://jira.jboss.org/browse/JBDS-1359 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Affects Versions: 4.0.0.Beta1 Environment: Environment: Version: 4.0.0.Beta1 Build id: v201010052359R Build date: 201010060016 Reporter: Len DiMaggio Attachments: import_helloworld.log The example imports and works - but an error is logged -- 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

15 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7228) Code Generation Config -> Query Exporter -> "The property value must be non-empty" should inform this error in launch config dialog

by Vitali Yemialyanchyk (JIRA)

Code Generation Config -> Query Exporter -> "The property value must be non-empty" should inform this error in launch config dialog ----------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7228 URL: https://jira.jboss.org/browse/JBIDE-7228 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.2.0.Beta1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.2.0.Beta2 -- 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

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7112) Error during building project archives without any archive definition

by Jiri Peterka (JIRA)

Error during building project archives without any archive definition --------------------------------------------------------------------- Key: JBIDE-7112 URL: https://jira.jboss.org/browse/JBIDE-7112 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.2.0.M2 Environment: JBDS 4.0.0.m2 #480, Linux 64 Reporter: Jiri Peterka Attachments: building-project-archive-descriptior-location.png There is error when selecting build without any archive definition: 1. New workspace 2. Create seam war 3. Open project archive view 4. Select seam project 5. Click on seam project in project archive view -> Build project full -- 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

15 years, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6685) JSF 2 Quickfixes should be more descriptive about its intent

by Max Rydahl Andersen (JIRA)

JSF 2 Quickfixes should be more descriptive about its intent ------------------------------------------------------------ Key: JBIDE-6685 URL: https://jira.jboss.org/browse/JBIDE-6685 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.2.0.M2 Reporter: Max Rydahl Andersen Assignee: Maxim Areshkau Fix For: 3.2.0.M2 The new JSF 2 quick fixes are great but they are very hard to understand what they want to do based on their generic description. "Create folder container for JSF 2 resources" for a xmlns:custom="http://java.sun.com/jsf/composite/custom" without matching folder should have a quickfix saying something like "Create 'custom' folder for composite resources" and then possibly and extra info describing it more, i.e. "Create folder '/MyProject/WebContent/custom' to hold resources for custom component resources. same goes for: "Create JSF 2 Composite Component in project resources folder" for a <custom:table should be something like: "Create composite component named 'table' in '/WebContent/custom'" "Create attribute in an interface declariton of composite component" for a unknwon attribute "width" should be: "Add 'width' attribute to interface of <custom:table>" with info saying "Add 'width' attribute to interface of <custom:table> at '/WebContent/custom/table.xhtml' -- 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

15 years, 4 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-7153) Odd drop targets during DnD in VPE

by Yahor Radtsevich (JIRA)

Odd drop targets during DnD in VPE ---------------------------------- Key: JBIDE-7153 URL: https://jira.jboss.org/browse/JBIDE-7153 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.2.0.Beta1 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.2.0.Beta2 STEPS TO REPRODUCE: 1. Open file \trunk\jsf\tests\org.jboss.tools.jsf.vpe.jsf.test\resources\jsfTest\WebContent\pages\JBIDE\5042_6229\JBIDE-5042-6229.html in VPE. 2. Drag "DraggableBn" button over "Draggable Text". RESULT: An odd drop target is shown (see screenshot-1.png). -- 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

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4705) Move toolbar button for position switching from internal tool bar panel to external one.

by Yura Zhishko (JIRA)

Move toolbar button for position switching from internal tool bar panel to external one. ---------------------------------------------------------------------------------------- Key: JBIDE-4705 URL: https://jira.jboss.org/jira/browse/JBIDE-4705 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.1.0.M3 Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Minor Tool bar button for switching of Visual and Source panes positions influences on all pages in VPE (even if the page hadn't been opened before), so, I think, that this button should be moved from internal tool bar panel to external one (see screenshot-1). -- 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

15 years, 4 months

6
10
0 / 0

[JBoss JIRA] Created: (JBIDE-4701) Move "Preferences" tool bar button to external tool bar

by Yura Zhishko (JIRA)

Move "Preferences" tool bar button to external tool bar ------------------------------------------------------- Key: JBIDE-4701 URL: https://jira.jboss.org/jira/browse/JBIDE-4701 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.1.0.M2 Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Minor So far as preferences what user set in VPE "Preferences" dialog are common for all pages, I think that we should move "Preferences" tool bar button from internal tool bar panel to external one (see screenshot-1). -- 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

15 years, 4 months

8
22
0 / 0

[JBoss JIRA] Created: (JBIDE-7570) JUnit fails: org.jboss.tools.jsf.vpe.richfaces.test.RichFacesComponentContentTest.testColumn()

by Yahor Radtsevich (JIRA)

JUnit fails: org.jboss.tools.jsf.vpe.richfaces.test.RichFacesComponentContentTest.testColumn() ---------------------------------------------------------------------------------------------- Key: JBIDE-7570 URL: https://jira.jboss.org/browse/JBIDE-7570 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.2.0.Beta2 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.2.0.Beta2 junit.framework.AssertionFailedError: D:\doc\prj\jboss\wrksps\junit-workspace\richFacesTest\WebContent\pages\components\column.xhtml.xml[/tests/test[5]/DIV/DIV[2]/TABLE/COLGROUP/@SPAN]: string is"3" but must be "4" at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.ui.test.ComponentContentTest.compareContent(ComponentContentTest.java:117) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTestByFullPath(ComponentContentTest.java:97) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTest(ComponentContentTest.java:68) at org.jboss.tools.jsf.vpe.richfaces.test.RichFacesComponentContentTest.testColumn(RichFacesComponentContentTest.java:96) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116) 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:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) 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.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47) 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

15 years, 4 months

2
2
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 2010