[JBoss JIRA] (GPD-289) Process Debugger
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-289?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-289.
---------------------------
Resolution: Out of Date
> Process Debugger
> ----------------
>
> Key: GPD-289
> URL: https://issues.jboss.org/browse/GPD-289
> Project: jBPM GPD
> Issue Type: Task
> Components: jpdl
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 4.x
>
>
> It should be possible to add breakpoints to the process definition. When the process is run from a unit test in debugging mode, the execution should stop at the appropriate breakpoint, giving the developer the possibility to inspect process variables, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-234) Two Nodes with the same name
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-234?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-234.
---------------------------
Resolution: Out of Date
> Two Nodes with the same name
> ----------------------------
>
> Key: GPD-234
> URL: https://issues.jboss.org/browse/GPD-234
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Affects Versions: jBPM jPDL Designer 3.1.3
> Environment: Eclipse 3.3.2
> Reporter: Sven Daumann
> Assignee: Koen Aers
> Fix For: jBPM jPDL Designer 3.x
>
>
> step1: Create a Node and put a transition to this Node.
> step2: Rename the Node and use the name of an existing Node.
> The GPD show both Nodes with Transitions.
> step3: Close the diagram
> step4: Reopen the diagram
> problem: Only one Node is visible, the two transitions go to the one Node.
> step5: Move the Node. The moving Node has no transition. Under the moved Node, the other Node is now visible, with both transitions.
> During rename, there is no warning, that another Node with the same name exist.
> The XML data contains two Nodes.
> processdefinition.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <process-definition xmlns="" name="Test">
> <start-state name="start-state1">
> <transition to="node1" name="startet"></transition>
> </start-state>
> <node name="node1">
> <transition to="node2" name="ok"></transition>
> <transition to="Test" name="toTest"></transition>
> </node>
> <node name="node2">
> <transition to="end-state1" name="ok"></transition>
> <transition to="Test" name="toTest"></transition>
> </node>
> <task-node name="Test"></task-node>
> <task-node name="Test"></task-node>
> <end-state name="end-state1"></end-state>
> </process-definition>
> gpd.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <root-container name="Test" width="675" height="634">
> <node name="start-state1" x="375" y="272" width="132" height="36">
> <edge>
> <label x="5" y="-10"/>
> </edge>
> </node>
> <node name="node1" x="374" y="353" width="132" height="36">
> <edge>
> <label x="5" y="-10"/>
> </edge>
> <edge>
> <label x="5" y="-10"/>
> </edge>
> </node>
> <node name="node2" x="378" y="448" width="132" height="36">
> <edge>
> <label x="5" y="-10"/>
> </edge>
> <edge>
> <label x="5" y="-10"/>
> </edge>
> </node>
> <node name="end-state1" x="383" y="548" width="132" height="36"/>
> <node name="Test" x="172" y="347" width="132" height="36"/>
> <node name="Test" x="174" y="451" width="132" height="36"/>
> </root-container>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (GPD-337) image clipping
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/GPD-337?page=com.atlassian.jira.plugin.sy... ]
Koen Aers resolved GPD-337.
---------------------------
Resolution: Out of Date
> image clipping
> --------------
>
> Key: GPD-337
> URL: https://issues.jboss.org/browse/GPD-337
> Project: jBPM GPD
> Issue Type: Task
> Components: jpdl
> Reporter: Tom Baeyens
> Assignee: Koen Aers
> Priority: Minor
> Fix For: jBPM jPDL Designer 4.x
>
>
> the generated images are too large. clipping them would be nice to have.
> watch out with clipping the top left corner (i assume that is coordinates 0,0). if you clip that while saving the image, then the coordinates in the process, used by the console might be affected.
> while clipping the bottom right corner should be possible without problem for the console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (WFLY-7045) domain-elytron.xml, missing singelton subsystem, different ejb cache type
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7045?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-7045:
----------------------------------------
>From what I can see the latter appears to be a bug in feature pack assembly.
The EJB3 Subsystem is defined as: -
{code:xml}
<subsystem supplement="ha-elytron">ejb3.xml</subsystem>
{code}
In the subsystem this is defined as: -
{code:xml}
<supplement name="ha-elytron" includes="ha elytron"/>
{code}
These in turn are defined as : -
{code:xml}
<supplement name="ha">
<replacement placeholder="STATEFUL-BEAN">
<stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/>
</replacement>
</supplement>
<supplement name="elytron" includes="default">
<replacement placeholder="ELYTRON">
<application-security-domains>
<application-security-domain name="other" security-domain="ApplicationDomain"/>
</application-security-domains>
</replacement>
</supplement>
{code}
But default is defines as: -
{code:xml}
<supplement name="default">
<replacement placeholder="STATEFUL-BEAN">
<stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/>
</replacement>
</supplement>
{code}
So somehow the replacement defined in default is used instead of the one defined in ha.
> domain-elytron.xml, missing singelton subsystem, different ejb cache type
> -------------------------------------------------------------------------
>
> Key: WFLY-7045
> URL: https://issues.jboss.org/browse/WFLY-7045
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Fix For: 11.0.0.Alpha1
>
>
> When I compare domain-elytron.xml to domain.xml,
> 1) There is missing org.wildfly.extension.clustering.singleton extension installed.
> 2) There is changed ejb cache configuration
> 1254c1129
> < <stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/>
> ---
> > <stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month