[jboss-jira] [JBoss JIRA] Commented: (JBPM-975) jbmp-3.2.xsd: start-state doesn't support a timer anymore

[Roland Huss (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-975?page=comments#action_12363952 ] 
            
Roland Huss commented on JBPM-975:
----------------------------------

Ok, I agree that a start-state might never receive a "node-enter" event, because its, well, a start-state. 
But, frankly, when I use a <timer> element within a <node> or <start-state>  I don't mind to which events internally
a CreateTimerAction and CancelTimerAction is registered (it's done implicetly by JpdlXmlReader.readNodeTimer()).

So why not simply register a CreateTimerAction to the "process-create" Event when a <timer> is used within a <start-state> from 
within JpdlXmlReader ?  IMO it is a perfect valid use case for a timer within a start state to trigger some sort of escalation if no one "picks up" the ticket 
(by moving on to an additional state). Why not supporting it explicitely even it implies internally some registeration to a different event ? 
At least, the usage of a <timer> remains transparent even in a start-state ....

> jbmp-3.2.xsd: start-state doesn't support a timer anymore
> ---------------------------------------------------------
>
>                 Key: JBPM-975
>                 URL: http://jira.jboss.com/jira/browse/JBPM-975
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2
>            Reporter: Roland Huss
>         Assigned To: Tom Baeyens
>            Priority: Critical
>
> The XSD Schema jbpm-3.2.xsd doesn't support a <timer> subelement anymore (in contrast to jbpm-3.1.xsd):
> <xs:element name="start-state">
>     <xs:complexType>
>       <xs:choice minOccurs="0" maxOccurs="unbounded">
>         <xs:element ref="description" />
>         <xs:element ref="task"/>
>         <xs:element ref="transition"/>
>         <xs:element ref="event"/>
>         <xs:element ref="exception-handler"/>
>       </xs:choice>
>       <xs:attribute name="name" type="xs:string"/>
>     </xs:complexType>
>   </xs:element>
> Adding a <xs:element ref="timer"/> should fix this (except if this should be intended behaviour but I can hardly see the reason for why a timer shouldn't be allowed during a start-state)

-- 
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