[JBoss JIRA] Created: (JBIDE-5576) java.lang.NullPointerException is occured while creating New File filter or XPath for SCP remote server
by Anton Klimkovich (JIRA)
java.lang.NullPointerException is occured while creating New File filter or XPath for SCP remote server
-------------------------------------------------------------------------------------------------------
Key: JBIDE-5576
URL: https://jira.jboss.org/jira/browse/JBIDE-5576
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR1
Reporter: Anton Klimkovich
Assignee: Rob Stryker
EXECUTE: Opne JBoss Server View
EXECUTE: Add SCP Remote server
EXECUTE: Try to create new File Filter or XPath
FAILURE:
java.lang.NullPointerException
at org.jboss.ide.eclipse.archives.webtools.filesets.FilesetActionProvider$1.run(FilesetActionProvider.java:208)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
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)
--
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 months
[JBoss JIRA] Created: (JBIDE-5542) Potential NullPointerException in VPE openned on file from project without JBossTools nature
by Denis Golovin (JIRA)
Potential NullPointerException in VPE openned on file from project without JBossTools nature
--------------------------------------------------------------------------------------------
Key: JBIDE-5542
URL: https://jira.jboss.org/jira/browse/JBIDE-5542
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.CR2
Reporter: Denis Golovin
Fix For: 3.1.0.CR1
I cannot provide exact steps to reproduce it but stack trace tells me that that might happen for any none JBossTools project. For me it happens on project with JSF capabilities. To fix this problem on JBossTools JSF project, it should be closed/opened and VPE starts working.
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:3884)
at org.eclipse.swt.SWT.error(SWT.java:3799)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
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.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(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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: java.lang.NullPointerException
at org.jboss.tools.vpe.editor.bundle.BundleMap.refreshRegisteredBundles(BundleMap.java:100)
at org.jboss.tools.vpe.editor.bundle.BundleMap.refresh(BundleMap.java:343)
at org.jboss.tools.vpe.editor.VpeController.refreshTemplates(VpeController.java:1689)
at org.jboss.tools.vpe.editor.VpeEditorPart$ActivationListener.handleActivation(VpeEditorPart.java:1075)
at org.jboss.tools.vpe.editor.VpeEditorPart$ActivationListener.access$1(VpeEditorPart.java:1064)
at org.jboss.tools.vpe.editor.VpeEditorPart$ActivationListener$1.run(VpeEditorPart.java:1059)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
... 22 more
--
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 months
[JBoss JIRA] Created: (JBIDE-2023) Population of Action Class / Process Method
by Tom Cunningham (JIRA)
Population of Action Class / Process Method
-------------------------------------------
Key: JBIDE-2023
URL: http://jira.jboss.com/jira/browse/JBIDE-2023
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Environment: Mac OS X, nightly 04/04 JBoss Tools build, Europa JEE eclipse build
Reporter: Tom Cunningham
It would be nice if the ESB editor could somehow populate an action class drop down or do autocompletion of the class name, while at the same time retaining the ability for the user to type in their action class name. Action classes in the drop down should probably be restricted to classes within project which extend AbstractActionLifecycle or AbstractActionPipelineProcessor and the org.jboss.soa.esb.actions package classes.
--
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, 6 months
[JBoss JIRA] Created: (JBIDE-3378) Seam EL validation does not use same technique as the EL resolver (Continued)
by Tim Evers (JIRA)
Seam EL validation does not use same technique as the EL resolver (Continued)
-----------------------------------------------------------------------------
Key: JBIDE-3378
URL: https://jira.jboss.org/jira/browse/JBIDE-3378
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.beta1, 3.0.0.alpha, 2.1.2
Environment: Latest nightly build of JBoss Tools. On eclipse 3.4 SR1. JSF/Facelets/Richfaces/Seam 2.1.x environment
Reporter: Tim Evers
JBoss Tools does not validate method EL expressions properly if the method name starts with 'is'
If I have a method in my SEAM bean like this.
public boolean isEditButtonDisplayed() {
return true; //removed what this method actually does for example
}
and then I have in my xhtml this:
<gekko:commandButton
id="tenureEditButton"
value="Edit"
action="#{TenureKeyController.editButtonClicked()}"
rendered="#{TenureKeyController.isEditButtonDisplayed()}" />
When I validate this it says: "isEditButtonDisplayed" cannot be resolved.
It looks like when the validation method sees the word 'is' it automatically thinks that the expression is a value expression. This should not be the case. Infact if I end my expression witih '()' it should always look for a method.
The behaviour of the EL validation should be exactly the same as what happens when I run the system. But this is not what is happening. If I change my code to what the JBoss Tools autocomplete says to it actually breaks the application. According to JBoss Tools it says I should have this.
<gekko:commandButton
id="tenureEditButton"
value="Edit"
action="#{TenureKeyController.editButtonClicked()}"
rendered="#{TenureKeyController.editButtonDisplayed}" />
Which of course will not work when the app is deployed.
This is somewhat related to: https://jira.jboss.org/jira/browse/JBIDE-2673 just a different scenario.
The fundamental problem is that the rules of validation are not the same as a running app.
--
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 months
[JBoss JIRA] Created: (JBIDE-5463) BPEL Editor gives validation errors after creating correlation variables
by Jeff DeLong (JIRA)
BPEL Editor gives validation errors after creating correlation variables
------------------------------------------------------------------------
Key: JBIDE-5463
URL: https://jira.jboss.org/jira/browse/JBIDE-5463
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Environment: JBoss BPEL Editor 1.0.0.v200912111224M-H175-RC1 org.jboss.tools.bpel.feature.feature.group on Mac with JDK 1.6
Reporter: Jeff DeLong
I created a CorrelationSet with a single correlation variable and four mappings. After doing this and cleaning the project I get four errors:
Description Resource Path Location Type
The XPath segment "child::receivePolicyQuote" cannot be resolved. PolicyQuoteProcessArtifacts.wsdl /PolicyQuoteProcessService/bpelContent query BPEL Validation Marker
Description Resource Path Location Type
The XPath segment "child::receivePolicyQuote" cannot be resolved. PolicyQuoteProcessArtifacts.wsdl /PolicyQuoteProcessService/bpelContent query BPEL Validation Marker
Description Resource Path Location Type
The XPath segment "child::ssn" cannot be resolved. PolicyQuoteProcessArtifacts.wsdl /PolicyQuoteProcessService/bpelContent query BPEL Validation Marker
Description Resource Path Location Type
The XPath segment "child::ssn" cannot be resolved. PolicyQuoteProcessArtifacts.wsdl /PolicyQuoteProcessService/bpelContent query BPEL Validation Marker
I will zip up and attach the project files.
--
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 months
[JBoss JIRA] Created: (JBIDE-5578) ClassCastException occures when the proper context cannot be created
by Victor Rubezhny (JIRA)
ClassCastException occures when the proper context cannot be created
--------------------------------------------------------------------
Key: JBIDE-5578
URL: https://jira.jboss.org/jira/browse/JBIDE-5578
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common, jsp/jsf/xml source editing
Affects Versions: 3.1.0.CR1
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 3.1.0.CR2
ClassCastException occures when the proper context cannot be created. See the stack trace below:
java.lang.ClassCastException: org.jboss.tools.jst.web.kb.internal.XmlContextImpl
at org.jboss.tools.jst.jsp.contentassist.JspContentAssistProcessor.getContext(JspContentAssistProcessor.java:63)
at org.jboss.tools.jst.jsp.outline.JSPPropertySourceAdapter.setTarget(JSPPropertySourceAdapter.java:127)
at org.jboss.tools.jst.jsp.outline.JSPPropertySourceAdapter.<init>(JSPPropertySourceAdapter.java:103)
at org.jboss.tools.jst.jsp.outline.JSPPropertySheetConfiguration$JSPPropertySourceProvider0.getPropertySource(JSPPropertySheetConfiguration.java:56)
at org.eclipse.ui.views.properties.PropertySheetEntry.getPropertySource(PropertySheetEntry.java:470)
at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:752)
at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:973)
at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:510)
at org.eclipse.wst.sse.ui.internal.properties.ConfigurablePropertySheetPage.selectionChanged(ConfigurablePropertySheetPage.java:174)
at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:361)
at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156)
at org.eclipse.ui.internal.AbstractSelectionService.setActivePart(AbstractSelectionService.java:282)
at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:60)
at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136)
at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3528)
at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:3071)
at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:279)
at org.eclipse.ui.internal.EditorPane.requestActivation(EditorPane.java:98)
at org.eclipse.ui.internal.presentations.PresentablePart.setFocus(PresentablePart.java:192)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:94)
at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:270)
at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:275)
at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.handleMouseDown(AbstractTabFolder.java:345)
at org.eclipse.ui.internal.presentations.util.AbstractTabFolder$3.mouseDown(AbstractTabFolder.java:79)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
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(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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, 6 months
[JBoss JIRA] Created: (JBIDE-5577) OpenOn for xhtml page from link with <page_name>.jsf
by Maxim Areshkau (JIRA)
OpenOn for xhtml page from link with <page_name>.jsf
----------------------------------------------------
Key: JBIDE-5577
URL: https://jira.jboss.org/jira/browse/JBIDE-5577
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml source editing
Affects Versions: 3.1.0.CR1
Reporter: Maxim Areshkau
Assignee: Denis Maliarevich
Fix For: 3.1.0.CR2
#1 Import /home/mareshkau/Projects/jboss/trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test project,
#2 open page index.html and try to openOn from <a href="pages/components/head2.jsf">h:head (2nd)</a>
ASSERT head2.xhtml should be opened
Also take into account that link to page can be specified in this was #{facesContext.externalContext.requestContextPath}/<path>
--
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 months