[JBoss JIRA] Created: (JBIDE-7351) General issues with Variable Initialization, Assign, and Copy
by Jeff DeLong (JIRA)
General issues with Variable Initialization, Assign, and Copy
-------------------------------------------------------------
Key: JBIDE-7351
URL: https://jira.jboss.org/browse/JBIDE-7351
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Jeff DeLong
I see several issues with the variable initialization in Assign. Some are ease-of-use related, others seem like bugs. I have written a JIRA for Riftsaw, https://jira.jboss.org/browse/RIFTSAW-301 that requests automatic initialization of variables inside the engine. This is one approach to addressing variable initialization problems (moves the responsibility to the engine). In that JIRA I have also noted examples where the BPEL Editor said a copy operation was in error that executed fine on the server, as well as not flagging errors in a copy operation that threw an Assignment Fault at runtime. In general the relationship between the initialization (which is done through a copy operation) and well as the actual assign copy operations, is too confusing for the average BPEL Editor user. The user (we are not talking a business analyst type here, but a process architect / developer) should not have to worry about the syntax of these various copy statement and knowing whether they are correct. They should just be able to say which parts of a message get copied to which parts of another message. Either the tooling or the engine should take care of the rest.
--
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, 3 months
[JBoss JIRA] Created: (JBIDE-6588) BPEL deployment to ODE running in Tomcat
by Gary Brown (JIRA)
BPEL deployment to ODE running in Tomcat
----------------------------------------
Key: JBIDE-6588
URL: https://jira.jboss.org/browse/JBIDE-6588
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: bpel
Reporter: Gary Brown
Currently the BPEL plugins in JBoss Tools support deployment of a BPEL process and ODE deployment descriptor to RiftSaw (ODE running in JBossAS).
It may be useful to allow users to also deploy the same processes to ODE running inside Tomcat.
This would enable existing ODE/Tomcat users to benefit from a supported version of the BPEL editor, and easily switch to using RiftSaw if they wanted.
The Eclipse BPEL project already provides a deploy for ODE in Tomcat. The only change that would be required is to change the bpel-deploy.xml to deploy.xml during deployment, as ODE does not recognize bpel-deploy.xml.
--
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, 3 months
[JBoss JIRA] Created: (JBDS-1455) WS Tester View can't be loaded in JBDS after 3rd party plugins installation (subversive, m2eclipse, ....)
by Jiri Peterka (JIRA)
WS Tester View can't be loaded in JBDS after 3rd party plugins installation (subversive, m2eclipse,....)
--------------------------------------------------------------------------------------------------------
Key: JBDS-1455
URL: https://issues.jboss.org/browse/JBDS-1455
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
Affects Versions: 4.0.0.Beta2
Reporter: Jiri Peterka
Priority: Critical
This issue is related JBIDE-6450. When javax.xml.soap (1.3) bundle is loaded, it's unable to start WS Tester (java.xml.soap 1.2 can't be loaded properly). There is no problem on JBT 3.2.beta2, so it seems it's JBDS related (at least for some cases).
Error message:
Could not create the view: Plug-in "org.jboss.tools.ws.ui" was unable to instantiate class "org.jboss.tools.ws.ui.views.JAXRSWSTestView2".
java.lang.VerifyError: (class: org/jboss/tools/ws/ui/views/JAXRSWSTestView2, method: getOpNameFromRequestBody signature: ()Ljava/lang/String;) Incompatible object argument for function call
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.newInstance0(Class.java:326)
at java.lang.Class.newInstance(Class.java:308)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:904)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
by Brian Fitzpatrick (JIRA)
Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
----------------------------------------------------------------------------------------------------------
Key: JBIDE-6450
URL: https://jira.jboss.org/browse/JBIDE-6450
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M1
Reporter: Brian Fitzpatrick
Assignee: Brian Fitzpatrick
Priority: Critical
Fix For: 3.2.0.M1
Finally got to the heart of the java.lang.VerifyError issue I've been running into with the WS Tester.
javax.xml.soap (1.2) is an old-school plug-in jar wrapper that takes saaj.jar and exposes it in Eclipse.
javax.xml.soap (1.3) is a new-school OSGI-compatible wrapper that builds the individual saaj classes and wraps them to expose them in Eclipse.
As Nick said in a recent IRC chat - ".jar!/org/whatever/*.class is better than .jar!foo.jar". But in my case, it causes the lovely java.lang.VerifyError when I try to use a utility class that takes advantage of classes from javax.xml.soap.
After doing some digging, it turns out the javax.xml.soap (1.3) plug-in is coming from the Atlassian update site for the latest & greatest version of their JIRA/Mylyn plug-ins. Without Atlassian JIRA connectors installed, it runs just fine.
So this presents an issue... If we're meant to certify against Atlassian JIRA connectors, this is going to come up again. So how do we work around it?
--
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, 3 months
[JBoss JIRA] Created: (JBIDE-7758) Error when defining new resource file via Externalize String Dialog and adding reference to resource file via <f:loadBundle>
by Vlado Pakan (JIRA)
Error when defining new resource file via Externalize String Dialog and adding reference to resource file via <f:loadBundle>
----------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-7758
URL: https://jira.jboss.org/browse/JBIDE-7758
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.2.0.Beta2
Environment: Linux 32bit, jbdevstudio-eap-linux-gtk-4.0.0.v201011291019R-H12-Beta2.jar java, Java Sun JDK 1.6.
Reporter: Vlado Pakan
Assignee: Alexey Kazakov
1. Create JSF 1.2 Kick Start Project
2. Open <JSF Project>/WebContent/pages/inputUserName.jsp
3. Insert tag '<h:outputText value="translate"/>' within <f:view> tag
4. Select "translate" text within tag mentioned in point 3
5. Open Externalize String > Check create a new properties file checkbox > Choose Next > Choose Next > select a place to register this bundle > via <f:loadBundle> tag on current page
6. Choose OK
Dialog is not closed, resource file is created and Exception is thrown. No changes are made to inputUserName.jsp.
Error log:
Unhandled event loop exception
java.lang.NullPointerException
at org.jboss.tools.jst.jsp.i18n.ExternalizeStringsWizard.performFinish(ExternalizeStringsWizard.java:340)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.jboss.tools.jst.jsp.i18n.handlers.I18nHandler.execute(I18nHandler.java:121)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:820)
at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:806)
at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:796)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
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)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-6606) Unable to specify styleClass attribute for selected tag when used CSS class contains @CHARSET "UTF-8"; at keyword.
by Vlado Pakan (JIRA)
Unable to specify styleClass attribute for selected tag when used CSS class contains @CHARSET "UTF-8"; at keyword.
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6606
URL: https://jira.jboss.org/browse/JBIDE-6606
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M1
Environment: JBDS Version: 4.0.0.M1 Build id: v201007091251N Build date: 201007091354
Linux 32bit
Java Sun JDK 1.6
Reporter: Vlado Pakan
Assignee: Maxim Areshkau
Steps to reproduce:
1. Create new JSF project
2. Create and open new CSS file test,css in the <jsf project>/WebContent/pages/ directory: Menu File > New > Others > Css File. It should has content @CHARSET "UTF-8";
3. Open <jsf project>/WebContent/pages/inputUserName.jsp and insert "link href="test.css" type="text/css"/>" after "<body>" tag.
4. Open Properties view: Window > Show View > Properties
5. Select "h:outputText" tag within source pane of opened page
6. Select styleClass property within Properties view and choose button with label "..." trying to specify styleClass property
No dialog is displayed and in Error Log is this error:
java.lang.ClassCastException: org.eclipse.wst.css.core.internal.document.CSSCharsetRuleImpl cannot be cast to org.eclipse.wst.css.core.internal.provisional.document.ICSSStyleRule
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.model.CSSSelectorTreeModel.initModel(CSSSelectorTreeModel.java:52)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.model.CSSSelectorTreeModel.<init>(CSSSelectorTreeModel.java:37)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.model.CSSJSPRecognizer.getCssStyleClassTreeModel(CSSJSPRecognizer.java:163)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.model.CSSJSPRecognizer.getCssStyleClassTreeModel(CSSJSPRecognizer.java:169)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSSelectorPartComposite.initDefaultContent(CSSSelectorPartComposite.java:133)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSSelectorPartComposite.creatSelectorPart(CSSSelectorPartComposite.java:116)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSSelectorPartComposite.<init>(CSSSelectorPartComposite.java:108)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSStyleClassSelector.createCSSClassComposite(CSSStyleClassSelector.java:62)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSStyleClassSelector.createControlComposite(CSSStyleClassSelector.java:49)
at org.jboss.tools.jst.jsp.outline.cssdialog.AbstractCSSDialog.createControlPane(AbstractCSSDialog.java:118)
at org.jboss.tools.jst.jsp.outline.cssdialog.AbstractCSSDialog.createDialogArea(AbstractCSSDialog.java:88)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSStyleClassSelector.createDialogArea(CSSStyleClassSelector.java:91)
at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:155)
at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSStyleClassSelector.createContents(CSSStyleClassSelector.java:57)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at org.eclipse.jface.window.Window.open(Window.java:790)
at org.jboss.tools.jst.jsp.outline.JSPDialogCellEditor.openDialogBox(JSPDialogCellEditor.java:141)
at org.eclipse.jface.viewers.DialogCellEditor$2.widgetSelected(DialogCellEditor.java:244)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1234)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159)
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)
--
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, 3 months