[JBoss JIRA] Created: (JBIDE-5862) org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets fails with: expected:<[ a] > but was:<[ >] >
by Nick Boldt (JIRA)
org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets fails with: expected:<[ a] > but was:<[ >] >
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-5862
URL: https://jira.jboss.org/jira/browse/JBIDE-5862
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.1.0.CR2
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Regression
JsfAllTests.testEditingSPecialSymbolsVPE_JBIDE3810
Failing for the past 1 build (Since #251 )
Took 13 sec.
add description
Error Message
expected:<[ a] > but was:<[ >] >
Stacktrace
junit.framework.ComparisonFailure: expected:<[
a]
> but was:<[ >]
>
at org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets(EditingSPecialSymbolsVPE_JBIDE3810.java:160)
at org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.testEditingSPecialSymbolsVPE_JBIDE3810(EditingSPecialSymbolsVPE_JBIDE3810.java:58)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195)
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:3468)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115)
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.test.UITestApplication.runApplication(UITestApplication.java:138)
at org.eclipse.test.UITestApplication.run(UITestApplication.java:60)
at org.eclipse.test.UITestApplication.start(UITestApplication.java:210)
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 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)
at org.eclipse.core.launcher.Main.main(Main.java:34)
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3...
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
by Denis Golovin (JIRA)
VPE Part should not show exceptions but readable explanation why it cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Maxim Areshkau
Fix For: 3.2.0.Beta2
Exceptions related to loading xulrunner should be handled right way. Human friendly messages would be good here for usecases we know. VPE should check for current platform and if it is not supported do not scary users with exceptions. It should try to load XL just in case path to XL injected outside through System property, but show explanation instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported platforms and possible workarounds. please read this article on JBoss Tools Community Portal". If someone is trying to inject XULRunner implementation using system property it can say, That "Visual Editor tried to load XL from provided loaction ${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
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
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-6708) MDB WTP Wizard Annotations for HornetQ
by Gary Lamperillo (JIRA)
MDB WTP Wizard Annotations for HornetQ
--------------------------------------
Key: JBIDE-6708
URL: https://jira.jboss.org/browse/JBIDE-6708
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.1
Environment: JBDS 3.0.1 , EAP 5.1 Beta, HornetQ 2.1
Reporter: Gary Lamperillo
Fix For: 3.1.2
Using the Message Driven Bean WTP Wizard that is in JBDS 3.0.1, an annotation in the format is created:
@MessageDriven( activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue")
HornetQ will need an annotation in the following format:
@MessageDriven(
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue"),
@ActivationConfigProperty(propertyName = "useLocalTx", propertyValue = "true") },
mappedName = "queue/testQueue")
Either HornetQ will nee to correspond to WTPs expectation or the wizard will need to be modified to accept the hornetq specific changes. Since the tooling will still need to work with other providers such as JBoss Messaging, a radio button will need to be added to the Wizard as well to select HornetQ.
--
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
14 years, 10 months