April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6017) Improve BPEL validation

by Robert (Bob) Brodt (JIRA)

Improve BPEL validation ----------------------- Key: JBIDE-6017 URL: https://jira.jboss.org/jira/browse/JBIDE-6017 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: All Reporter: Robert (Bob) Brodt While there has been a great deal of work already done to improve the BPEL validation, I still ran across some compilation errors that the in-built validator did not catch. My recommendation would be to run the Riftsaw bpelc compiler just before deployment to ensure the bpel will compile. Compilation is relatively fast and I don't anticipate this being a huge performance hit. -- 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

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6764) Handle WSDL updates better

by Jeff DeLong (JIRA)

Handle WSDL updates better -------------------------- Key: JBIDE-6764 URL: https://jira.jboss.org/browse/JBIDE-6764 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpel Affects Versions: 3.2.0.M1 Environment: Eclipse 3.6 on Mac; JB Tools 3.2 Reporter: Jeff DeLong When a WSDL is updated in the bpelContent file, the BPEL Editor can reports many validation errors with associated receive or invoke activity. The only way to recover appears to be to delete the associated Variable and PartnerLink and re-create them. The BPEL Editor should be enhanced to modify the existing partner links and variables when a WSDL is updated. -- 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
8
0 / 0

[JBoss JIRA] Moved: (JBDS-1615) Missing Documentation for Cloud Reference Guide?

by Anne-Louise Tangring (JIRA)

[ https://issues.jboss.org/browse/JBDS-1615?page=com.atlassian.jira.plugin.... ] Anne-Louise Tangring moved SOA-2944 to JBDS-1615: ------------------------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: JBoss Enterprise SOA Platform) Key: JBDS-1615 (was: SOA-2944) Affects Version/s: 4.0.0.GA (was: 5.1.0.CR1) Component/s: (was: Documentation) Security: (was: Public) > Missing Documentation for Cloud Reference Guide? > ------------------------------------------------ > > Key: JBDS-1615 > URL: https://issues.jboss.org/browse/JBDS-1615 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 4.0.0.GA > Reporter: Mark Drilling > > docs.redhat.com references a "Cloud Tools Reference Guide" [1], but it is missing. Is it supposed to be there or is the table in error? > [1] http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-1546) Bankrupcy history.brl file from Guvnor examples is not opened properly

by Toshiya Kobayashi (JIRA)

Bankrupcy history.brl file from Guvnor examples is not opened properly ---------------------------------------------------------------------- Key: JBDS-1546 URL: https://issues.jboss.org/browse/JBDS-1546 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: drools Affects Versions: 4.0.0.Beta1, 3.0.1.GA Reporter: Toshiya Kobayashi Platform JIRA for [JBIDE-6247] Bankrupcy history.brl file from Guvnor examples is not opened properly -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8691) JUnit JBIDE2010Test.testElTemplateSimple2() fails after moving to XULRunner 1.9.2.16 and Eclipse 3.7

by Yahor Radtsevich (JIRA)

JUnit JBIDE2010Test.testElTemplateSimple2() fails after moving to XULRunner 1.9.2.16 and Eclipse 3.7 ---------------------------------------------------------------------------------------------------- Key: JBIDE-8691 URL: https://issues.jboss.org/browse/JBIDE-8691 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Environment: XULRunner 1.9.2.16 and Eclipse 3.7 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.0.M1 JUnit JBIDE2010Test.testElTemplateSimple2() fails with the following stack trace: {quote} junit.framework.AssertionFailedError: Value should contain background style [background: red] at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE2010Test.testElTemplateSimple2(JBIDE2010Test.java:92) 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.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:56) 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:4125) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3742) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplication.runApp(NonUIThreadTestApplication.java:43) at org.eclipse.pde.internal.junit.runtime.UITestApplication.runApp(UITestApplication.java:44) at org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplication.start(NonUIThreadTestApplication.java:37) 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:344) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-161) Documentation does not contain information on reporting defects

by Joshua Wulf (JIRA)

Documentation does not contain information on reporting defects --------------------------------------------------------------- Key: TOOLSDOC-161 URL: https://issues.jboss.org/browse/TOOLSDOC-161 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Joshua Wulf Assignee: Isaac Rooskov All the books' prefaces now point to the Documentation Conventions book. In that book a "We Need Feedback!" section appears, however it is not the "We Need Feedback!" information for the whole suite of documentation, but rather refers only to itself, advising readers to log a bug in Bugzilla against the Document_Conventions component. It should probably direct users to open a bug in JIRA against the "Documentation for JBoss Tools and Developer Studio" component. It took me a while to find this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Commented: (JBIDE-8242) Change the ModeShape Eclipse plugin to enable resource versioning in the repository.

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8242?page=com.atlassian.jira.plugin... ] Dan Florian commented on JBIDE-8242: ------------------------------------ A user preference was added to indicate if the user desires published files to be versioned. At the time of publishing the user can override this preference. Developed using a ModeShape 2.5.0 beta jar. Need to test once a GA jar is available. > Change the ModeShape Eclipse plugin to enable resource versioning in the repository. > ------------------------------------------------------------------------------------ > > Key: JBIDE-8242 > URL: https://issues.jboss.org/browse/JBIDE-8242 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: modeshape > Affects Versions: 3.2.0.Beta2 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 3.2.1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Based on MODE-1027, the Eclipse plugin needs to be changed to enable versioning of resouces in the repository. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-8675) VPE JUnits fail baecause of different style values for different XULRunner versions

by Yahor Radtsevich (JIRA)

VPE JUnits fail baecause of different style values for different XULRunner versions ----------------------------------------------------------------------------------- Key: JBIDE-8675 URL: https://issues.jboss.org/browse/JBIDE-8675 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core, Visual Page Editor Templates Affects Versions: 3.3.0.M1 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.0.M1 There are many JUnits that do not fail with XULRunner 1.9.1 and fail with XULRunner 1.9.2. The reason of these failures is different order of CSS vaule parameters, like [red none repeat scroll 0% 0%] in XULRunner 1.9.1, and [none repeat scroll 0% 0% red] with XULRunner 1.9.2. One example: {quote} junit.framework.AssertionFailedError: D:\doc\prj\jboss\wrksps\junit-workspace\htmlTest\WebContent\pages\components\text\hr.html.xml[/tests/test/HR/@STYLE]: Style value for parameter [background] is different. Expected [ red none repeat scroll 0% 0%] but was [ none repeat scroll 0% 0% red] at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.base.test.ComponentContentTest.compareContent(ComponentContentTest.java:118) at org.jboss.tools.vpe.base.test.ComponentContentTest.performContentTestByFullPath(ComponentContentTest.java:98) at org.jboss.tools.vpe.base.test.ComponentContentTest.performContentTest(ComponentContentTest.java:69) at org.jboss.tools.vpe.html.test.HtmlComponentContentTest.testHr(HtmlComponentContentTest.java:314) 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:56) 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:4125) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3742) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplication.runApp(NonUIThreadTestApplication.java:43) at org.eclipse.pde.internal.junit.runtime.UITestApplication.runApp(UITestApplication.java:44) at org.eclipse.pde.internal.junit.runtime.NonUIThreadTestApplication.start(NonUIThreadTestApplication.java:37) 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:344) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8274) Frozen IDE during browsing JBossAS in MBean Explorer

by Jiri Peterka (JIRA)

Frozen IDE during browsing JBossAS in MBean Explorer ---------------------------------------------------- Key: JBIDE-8274 URL: https://issues.jboss.org/browse/JBIDE-8274 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 3.2.0.CR1 Environment: JBDS 4.0.0.CR1 H100, Linux 64 Reporter: Jiri Peterka Attachments: eap-td.txt, eclipse-td.txt IDE has frozen during expanding tree in MBean explorer. Situation. Started EAP 5.0.1, Deployed Seam war project. Unable to replicate again. Threaddump from Eclipse and JBossAS attached for a further investigation. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8672) Move bpel / jboss as mapping into a bpel plugin

by Rob Stryker (JIRA)

Move bpel / jboss as mapping into a bpel plugin ----------------------------------------------- Key: JBIDE-8672 URL: https://issues.jboss.org/browse/JBIDE-8672 Project: Tools (JBoss Tools) Issue Type: Task Components: bpel, JBossAS Affects Versions: 3.2.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.M1 By having the bpel / jboss as mapping in the jboss-as's plugin.xml, when run in an environment without bpel, error messages are logged. This mapping should be done in a bpel plugin or a bpel integration plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
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 April 2011