[JBoss JIRA] (WFLY-7048) Servlet 3.x metadata-complete="true" does not honour absolute-ordering element
by Darryl Miles (JIRA)
[ https://issues.jboss.org/browse/WFLY-7048?page=com.atlassian.jira.plugin.... ]
Darryl Miles updated WFLY-7048:
-------------------------------
Description:
Servlet 3.x metadata-complete="true" does not honour absolute-ordering element.
If I have a web.xml that sets metadata-complete="true" in the <web-app> element.
The container is expected to only allow the initialization of the named entries inside the <absolute-ordering> element that does not have the presence of an <others/> element inside it.
So a metadata-complete="true" with a non-existing (or empty) <absolute-ordering> is expected to effectively filter and then exclude ALL ServletContainerInitializer found. Since nothing was specified by a <name> element, and the <others/> element is not present.
This might also be considered a fast-path to prevent any package scanning for annotations / interfaces.
The bug here is that I can observe no change in behaviour (regardless of metadata-complete="true" setting, or the contents I tried of the <absolute-ordering> element, it always has the same results of finding and processing everything found in the classpath JARs).
Does WEB-INF/jboss-web.xml support undertow specific filtering of the packages to scan for ServletContainerInitializer ? Many other contains have support for this (jetty/tomcat) and the jboss-web.xml seems the obvious place to put it.
I can provide references to this feature, since it still helps in the developmentMode scenario (where I spend most of my time and care most about startup performance).
Also the servlet 3.x spec seem to have omited the notion of allowing WEB-INF/classes to contain a ServletContainerInitializer, they omitted having a section in web.xml to provide this, they omitted allowing a WAR to have WEB-INF/META-INF/services/javax.servlet.ServletContainerInitializer as well.
was:
Servlet 3.x metadata-complete="true" does not honour absolute-ordering element.
If I have a web.xml that sets metadata-complete="true" in the <web-app> element.
The container is expected to only allow the initialization of the named entries inside the <absolute-ordering> element that does not have the presense of an <others/> element inside it.
So a metadata-complete="true" with a non-existing (or empty) <absolute-ordering> is expected to effectively filter and then exclude ALL ServletContainerInitializer found. Since nothing was specified by a <name> element, and the <others/> element is not present.
This might also be considered a fast-path to prevent any package scanning for annotations / interfaces.
The bug here is that I can observe no change in behaviour (regardless of metadata-complete="true" setting, or the contents I tried of the <absolute-ordering> element, it always has the same results of finding and processing everything found in the classpath JARs).
Does WEB-INF/jboss-web.xml support undertow specific filtering of the packages to scan for ServletContainerInitializer ? Many other contains have support for this (jetty/tomcat) and the jboss-web.xml seems the obvious place to put it.
I can provide references to this feature, since it still helps in the developmentMode scenario (where I spend most of my time and care most about startup performance).
Also the servlet 3.x spec seem to have omited the notion of allowing WEB-INF/classes to contain a ServletContainerInitializer, they omitted having a section in web.xml to provide this, they omitted allowing a WAR to have WEB-INF/META-INF/services/javax.servlet.ServletContainerInitializer as well.
> Servlet 3.x metadata-complete="true" does not honour absolute-ordering element
> ------------------------------------------------------------------------------
>
> Key: WFLY-7048
> URL: https://issues.jboss.org/browse/WFLY-7048
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final
> Reporter: Darryl Miles
> Assignee: Stuart Douglas
>
> Servlet 3.x metadata-complete="true" does not honour absolute-ordering element.
> If I have a web.xml that sets metadata-complete="true" in the <web-app> element.
> The container is expected to only allow the initialization of the named entries inside the <absolute-ordering> element that does not have the presence of an <others/> element inside it.
> So a metadata-complete="true" with a non-existing (or empty) <absolute-ordering> is expected to effectively filter and then exclude ALL ServletContainerInitializer found. Since nothing was specified by a <name> element, and the <others/> element is not present.
> This might also be considered a fast-path to prevent any package scanning for annotations / interfaces.
> The bug here is that I can observe no change in behaviour (regardless of metadata-complete="true" setting, or the contents I tried of the <absolute-ordering> element, it always has the same results of finding and processing everything found in the classpath JARs).
> Does WEB-INF/jboss-web.xml support undertow specific filtering of the packages to scan for ServletContainerInitializer ? Many other contains have support for this (jetty/tomcat) and the jboss-web.xml seems the obvious place to put it.
> I can provide references to this feature, since it still helps in the developmentMode scenario (where I spend most of my time and care most about startup performance).
> Also the servlet 3.x spec seem to have omited the notion of allowing WEB-INF/classes to contain a ServletContainerInitializer, they omitted having a section in web.xml to provide this, they omitted allowing a WAR to have WEB-INF/META-INF/services/javax.servlet.ServletContainerInitializer as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-161) Overwriting a node in the source yields an out-of-sync diagram
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-161?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-161.
---------------------------
Resolution: Out of Date
> Overwriting a node in the source yields an out-of-sync diagram
> --------------------------------------------------------------
>
> Key: GPD-161
> URL: https://issues.jboss.org/browse/GPD-161
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Affects Versions: jBPM JPDL Designer 3.1.0.CR
> Environment: RHEL 5
> 3.1.0cr1
> Reporter: Micah Gideon Modell
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.x
>
> Attachments: cheat.txt, processdefinition.xml, websale.par
>
>
> I edited the source xml by pasting in the Decision Node from the cheat.txt (attached) over the "Evaluate web order" found in the example websale process. When I switched back to visual mode, I found an unattached Decision Node with no name and the "Evaluate web order" remained as before.
> I'll attach the before and after JPDL as well as the substitution text after I open this bug.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-162) Deploying a process does not pull in necessary Java classes
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-162?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-162.
---------------------------
Resolution: Out of Date
> Deploying a process does not pull in necessary Java classes
> -----------------------------------------------------------
>
> Key: GPD-162
> URL: https://issues.jboss.org/browse/GPD-162
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Affects Versions: jBPM JPDL Designer 3.1.0.CR
> Environment: RHEL 5
> GPD 3.1.0.CR1
> Reporter: Micah Gideon Modell
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.x
>
> Attachments: websale.par
>
>
> When I try to deploy a process from the GPD, the class files referenced in the definition do not come across properly.
> 1) Modified an existing process (as per GPD 161).
> 2) Save the process. (.par will be attached)
> 3) Use the Deployment tab to deploy the updated process.
> 4) Execute the process and you get the following error:
> In the web page:
> Error completing task: An exception of type "org.jbpm.graph.def.DelegationException" was thrown.
> On the console:
> 12:48:35,403 ERROR [Delegation] couldn't instantiate delegation class 'org.jbpm.websale.DeciderHandler'
> java.lang.NullPointerException
> at org.jbpm.instantiation.FieldInstantiator.newInstance(FieldInstantiator.java:105)
> at org.jbpm.instantiation.FieldInstantiator.instantiate(FieldInstantiator.java:48)
> at org.jbpm.instantiation.Delegation.instantiate(Delegation.java:163)
> at org.jbpm.instantiation.Delegation$$FastClassByCGLIB$$6bae1598.invoke(<generated>)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
> at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
> at org.jbpm.instantiation.Delegation$$EnhancerByCGLIB$$a8c02805.instantiate(<generated>)
> at org.jbpm.graph.node.Decision.execute(Decision.java:87)
> at org.jbpm.graph.def.Node.enter(Node.java:318)
> at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
> at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
> at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.enter(<generated>)
> at org.jbpm.graph.def.Transition.take(Transition.java:151)
> at org.jbpm.graph.def.Node.leave(Node.java:393)
> at org.jbpm.graph.node.StartState.leave(StartState.java:70)
> at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
> at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
> at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.leave(<generated>)
> at org.jbpm.graph.exe.Token.signal(Token.java:194)
> at org.jbpm.graph.exe.Token.signal(Token.java:139)
> at org.jbpm.graph.exe.Token$$FastClassByCGLIB$$74df1c6e.invoke(<generated>)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
> at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
> at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$5a16e027.signal(<generated>)
> at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:476)
> at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:390)
> at org.jbpm.jsf.core.action.CompleteTaskActionListener.handleAction(CompleteTaskActionListener.java:47)
> at org.jbpm.jsf.core.impl.JbpmActionListenerWrapper.processAction(JbpmActionListenerWrapper.java:82)
> at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
> at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:758)
> at javax.faces.component.UICommand.broadcast(UICommand.java:368)
> at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.broadcast(UITaskFormButtonBase.java:56)
> at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:448)
> at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
> at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
> at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
> at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
> at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
> at java.lang.Thread.run(Thread.java:595)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (WFLY-7048) Servlet 3.x metadata-complete="true" does not honour absolute-ordering element
by Darryl Miles (JIRA)
[ https://issues.jboss.org/browse/WFLY-7048?page=com.atlassian.jira.plugin.... ]
Darryl Miles updated WFLY-7048:
-------------------------------
Steps to Reproduce:
Make a WAR project with 2 WEB-INF/lib/*.jar that have META-INF/services/javax.servlet.ServletContainerInitializer (that simply log the calls to #onStartup())
Now modify web.xml with various permutations of settings to observe behaviour doesn't seem to change.
Test cases to cover:
No web.xml
web.xml (no metadata-complete attribute, no absolute-ordering element)
web.xml (no metadata-complete="true" set, no absolute-ordering element)
web.xml (no metadata-complete="true" set, absolute-ordering element with 1 name item)
web.xml (no metadata-complete="true" set, no absolute-ordering element with 2 name items)
web.xml (no metadata-complete="true" set, no absolute-ordering element with 1 name item and 1 others element item)
web.xml (no metadata-complete="true" set, no absolute-ordering element with 1 name item and 1 others element item - the other way round the previous test)
The result wants to be a List in order of what was invoked.
was:
Make a WAR project with 2 WEB-INF/lib/*.jar that have META-INF/services/javax.servlet.ServletContainerInitializer (that simply log the calls to #onStartup())
Now modify web.xml with various permutations of settings to observe behaviour doesn't seem to change.
Test cases to over:
No web.xml
web.xml (no metadata-complete attribute, no absolute-ordering element)
web.xml (no metadata-complete="true" set, no absolute-ordering element)
web.xml (no metadata-complete="true" set, absolute-ordering element with 1 name item)
web.xml (no metadata-complete="true" set, no absolute-ordering element with 2 name items)
web.xml (no metadata-complete="true" set, no absolute-ordering element with 1 name item and 1 others element item)
web.xml (no metadata-complete="true" set, no absolute-ordering element with 1 name item and 1 others element item - the other way round the previous test)
The result wants to be a List in order of what was invoked.
> Servlet 3.x metadata-complete="true" does not honour absolute-ordering element
> ------------------------------------------------------------------------------
>
> Key: WFLY-7048
> URL: https://issues.jboss.org/browse/WFLY-7048
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final
> Reporter: Darryl Miles
> Assignee: Stuart Douglas
>
> Servlet 3.x metadata-complete="true" does not honour absolute-ordering element.
> If I have a web.xml that sets metadata-complete="true" in the <web-app> element.
> The container is expected to only allow the initialization of the named entries inside the <absolute-ordering> element that does not have the presense of an <others/> element inside it.
> So a metadata-complete="true" with a non-existing (or empty) <absolute-ordering> is expected to effectively filter and then exclude ALL ServletContainerInitializer found. Since nothing was specified by a <name> element, and the <others/> element is not present.
> This might also be considered a fast-path to prevent any package scanning for annotations / interfaces.
> The bug here is that I can observe no change in behaviour (regardless of metadata-complete="true" setting, or the contents I tried of the <absolute-ordering> element, it always has the same results of finding and processing everything found in the classpath JARs).
> Does WEB-INF/jboss-web.xml support undertow specific filtering of the packages to scan for ServletContainerInitializer ? Many other contains have support for this (jetty/tomcat) and the jboss-web.xml seems the obvious place to put it.
> I can provide references to this feature, since it still helps in the developmentMode scenario (where I spend most of my time and care most about startup performance).
> Also the servlet 3.x spec seem to have omited the notion of allowing WEB-INF/classes to contain a ServletContainerInitializer, they omitted having a section in web.xml to provide this, they omitted allowing a WAR to have WEB-INF/META-INF/services/javax.servlet.ServletContainerInitializer as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-183) Cut/Copy/Paste of transitions and nodes in the process designer
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-183?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-183.
---------------------------
Resolution: Out of Date
> Cut/Copy/Paste of transitions and nodes in the process designer
> ---------------------------------------------------------------
>
> Key: GPD-183
> URL: https://issues.jboss.org/browse/GPD-183
> Project: jBPM GPD
> Issue Type: Feature Request
> Components: jpdl
> Reporter: Matthew Sandoz
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 4.x
>
>
> It would be very useful to support cut/copy/paste in the process designer. These operations would have the challenge of creating new element names where there were conflicts and determining which transitions to carry along - only connected transitions - that is those whose source and target nodes are also in the selection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (WFLY-7048) Servlet 3.x metadata-complete="true" does not honour absolute-ordering element
by Darryl Miles (JIRA)
Darryl Miles created WFLY-7048:
----------------------------------
Summary: Servlet 3.x metadata-complete="true" does not honour absolute-ordering element
Key: WFLY-7048
URL: https://issues.jboss.org/browse/WFLY-7048
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.1.0.Final
Reporter: Darryl Miles
Assignee: Stuart Douglas
Servlet 3.x metadata-complete="true" does not honour absolute-ordering element.
If I have a web.xml that sets metadata-complete="true" in the <web-app> element.
The container is expected to only allow the initialization of the named entries inside the <absolute-ordering> element that does not have the presense of an <others/> element inside it.
So a metadata-complete="true" with a non-existing (or empty) <absolute-ordering> is expected to effectively filter and then exclude ALL ServletContainerInitializer found. Since nothing was specified by a <name> element, and the <others/> element is not present.
This might also be considered a fast-path to prevent any package scanning for annotations / interfaces.
The bug here is that I can observe no change in behaviour (regardless of metadata-complete="true" setting, or the contents I tried of the <absolute-ordering> element, it always has the same results of finding and processing everything found in the classpath JARs).
Does WEB-INF/jboss-web.xml support undertow specific filtering of the packages to scan for ServletContainerInitializer ? Many other contains have support for this (jetty/tomcat) and the jboss-web.xml seems the obvious place to put it.
I can provide references to this feature, since it still helps in the developmentMode scenario (where I spend most of my time and care most about startup performance).
Also the servlet 3.x spec seem to have omited the notion of allowing WEB-INF/classes to contain a ServletContainerInitializer, they omitted having a section in web.xml to provide this, they omitted allowing a WAR to have WEB-INF/META-INF/services/javax.servlet.ServletContainerInitializer as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-141) IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-141?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-141.
---------------------------
Resolution: Out of Date
> IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception
> ------------------------------------------------------------------------------------------------
>
> Key: GPD-141
> URL: https://issues.jboss.org/browse/GPD-141
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Affects Versions: jBPM JPDL Designer 3.1.0.CR
> Environment: Eclipse 3.2 on Windows 2000
> Reporter: Matthias Hanisch
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.2
>
> Attachments: gpd-141.diff
>
>
> Following part of my processdefinition.xml:
> <event type="node-leave">
> <action class="x.y.z.MyClass" name="An Action">
> <arg>
> anArg
> </arg>
> </action>
> </event>
> MyClass is in a jar which is added to the classpath of the Process Project. Saving throws an event loop exception in Error Log View with the following stack.
> Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null argument;
> at org.eclipse.jface.util.Assert.isNotNull(Assert.java:150)
> at org.eclipse.jface.util.Assert.isNotNull(Assert.java:126)
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:577)
> at org.eclipse.jface.viewers.CheckboxTreeViewer.setCheckedElements(CheckboxTreeViewer.java:431)
> at org.jbpm.gd.jpdl.deployment.IncludeInDeploymentTreeViewer.setCheckedElements(IncludeInDeploymentTreeViewer.java:61)
> at org.jbpm.gd.jpdl.deployment.DeploymentForm$17.run(DeploymentForm.java:635)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
> The problem is, that DeploymentForm.getElementsToCheckFor() does not respect that MyClass returns null for getCompilationUnit(). As a consequence, setCheckedElements is called with null in the Object[].
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-149) Creating tasks by editing XML source will prevent the XML file from being re-opened
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-149?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-149.
---------------------------
Resolution: Out of Date
> Creating tasks by editing XML source will prevent the XML file from being re-opened
> -----------------------------------------------------------------------------------
>
> Key: GPD-149
> URL: https://issues.jboss.org/browse/GPD-149
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Affects Versions: jBPM JPDL Designer 3.1.0.CR
> Environment: Eclipse 3.3, Designer 3.1.0 CR
> Reporter: jeffcwang
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.x
>
>
> When you create new tasks by editing the source, it will break the process definition and not allow you to re-open it in Eclipse.
> Steps to recreate:
> 1) Create a new process definition
> 2) Create a task node using the GUI
> 3) Switch to the source tab
> 4) Copy the task xml tag
> 5) Rename the task name to something unique
> 6) Close the file
> 7) Re-open using the JBPM editor
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-179) pages.xml doesn't work with pageflow editor
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-179?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-179.
---------------------------
Resolution: Out of Date
> pages.xml doesn't work with pageflow editor
> -------------------------------------------
>
> Key: GPD-179
> URL: https://issues.jboss.org/browse/GPD-179
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.2
>
>
> a pages.xml with a proper page flow syntax does not have the pageflow editor in the right click menu.
> and when using Open with... and choosing jBpm pageflow designer (not the correct name is it ?) I get
> java.lang.NullPointerException
> at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addProcessDiagramDimension(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.initInput(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.init(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186)
> at org.jbpm.ui.pageflow.editor.PageFlowEditor.addGraphPage(Unknown Source)
> at org.jbpm.ui.pageflow.editor.PageFlowEditor.createPages(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
> at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-136) Widget is disposed in Task Controller Variables Table
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-136?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-136.
---------------------------
Resolution: Out of Date
> Widget is disposed in Task Controller Variables Table
> -----------------------------------------------------
>
> Key: GPD-136
> URL: https://issues.jboss.org/browse/GPD-136
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Environment: Eclipse 3.2.2 on Windows 2000
> Reporter: Matthias Hanisch
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.2
>
>
> Select a Task Node. Go to Properties View.
> Select Tasks:<task>:Controller (default).
> Add two variables, remove the second.
> Error Log view contains the following SWT Exception:
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:3374)
> at org.eclipse.swt.SWT.error(SWT.java:3297)
> at org.eclipse.swt.SWT.error(SWT.java:3268)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:435)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:330)
> at org.eclipse.swt.widgets.Control.setVisible(Control.java:2642)
> at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.applyName(VariableTableItemWrapper.java:164)
> at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.cancelEditing(VariableTableItemWrapper.java:150)
> at org.jbpm.gd.jpdl.util.VariableTableCellClickedResolver.mouseDown(VariableTableCellClickedResolver.java:25)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 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.core.launcher.Main.invokeFramework(Main.java:336)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
> After that, table input is not working anymore ("Mapped Name" column not editable anymore, for example).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month