[JBoss JIRA] (GPD-205) Designer adds script tag without expression
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-205?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-205.
---------------------------
Resolution: Out of Date
> Designer adds script tag without expression
> -------------------------------------------
>
> Key: GPD-205
> URL: https://issues.jboss.org/browse/GPD-205
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Reporter: Rafal Zukowski
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.x
>
> Original Estimate: 4 minutes
> Remaining Estimate: 4 minutes
>
> When You create transition and add "Script Action" to Actions in Properties, You can write some script which will run every time the transition will be used.
> Designer puts this text into <script> element, when jbpm expects script as a text in <expression> element, not in <script> element.
> sample correct xml:
> <transition to="end-state1">
> <script>
> <expression>
> System.out.println("test");
> </expression>
> </script>
> </transition>
> what designer does:
> <transition to="end-state1">
> <script>
> System.out.println("test");
> </script>
> </transition>
> I've made a patch to fix this problem, I'll attach it to this issue later...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (GPD-204) Additional Attribute for ESB Service Node
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-204?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-204.
---------------------------
Resolution: Out of Date
> Additional Attribute for ESB Service Node
> -----------------------------------------
>
> Key: GPD-204
> URL: https://issues.jboss.org/browse/GPD-204
> Project: jBPM GPD
> Issue Type: Feature Request
> Components: jpdl
> Reporter: Jeff DeLong
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.2
>
> Attachments: org.jbpm.gd.jpdl.diff
>
>
> There are two other options of the ESBActionHandler described in the SOA_ESB_JBPM_Integration_Guide.pdf
> default - optional attribute which can hold a default value if the esb MVEL expression does
> not find a value set in the EsbMessage.
> exceptionTransition - optional element. The name of the transition that should be taken if
> an exception occurs while processing the Service. This requires the current node to have
> more then one outgoing transition where one of the transition handles "exception
> processing"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (GPD-233) Delete a Timer in a TaskNode
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-233?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-233.
---------------------------
Resolution: Out of Date
> Delete a Timer in a TaskNode
> ----------------------------
>
> Key: GPD-233
> URL: https://issues.jboss.org/browse/GPD-233
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Affects Versions: jBPM jPDL Designer 3.1.3
> Environment: Eclipse 3.3.2, JPDL Designer 3.1.2, 3.1.3sp2
> Reporter: Sven Daumann
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.x
>
>
> step1: Create a timer in the properties-menu of a TaskNode
> step2: Delete the created timer in the menu
> problem: The timer is still visible. The timer is also visible after changing the tabs
> workaround: deselect the TaskNode
> Repeating step 1 and 2 with creating an event works fine.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (GPD-187) Expose properties of base classes in field/bean configuration of GPD
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-187?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-187.
---------------------------
Resolution: Out of Date
> Expose properties of base classes in field/bean configuration of GPD
> --------------------------------------------------------------------
>
> Key: GPD-187
> URL: https://issues.jboss.org/browse/GPD-187
> Project: jBPM GPD
> Issue Type: Feature Request
> Components: jpdl
> Affects Versions: jBPM jPDL Designer 3.1.0.SP1
> Environment: Windows XP (and others)
> Reporter: s b
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.2
>
>
> In the process designer interface for setting bean/field properties for custom classes such as an AssignmentHandler, it would be desirable if the properties/fields of the base classes (that the custom class inherits from) are also exposed. Then we could use inheritance much more effectively in our custom class designs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[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)
9 years, 8 months
[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)
9 years, 8 months
[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)
9 years, 8 months
[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)
9 years, 8 months