+1 to change the <form> tag into <transitionInputs>. Please see the diff of
scxml.xsd to enable this.
--- wso2greg-5.0.0-SNAPSHOT/repository/resources/scxml.xsd 2015-03-10
21:13:38.000000000 +0530
+++ ../wso2greg-5.0.0-SNAPSHOT/repository/resources/scxml.xsd 2015-04-02
17:38:54.547890501 +0530
@@ -78,9 +78,21 @@
<xs:attribute
type="xs:string" name="forEvent" use="optional"/>
</xs:complexType>
</xs:element>
- <xs:element
name="execution" maxOccurs="unbounded" minOccurs="0">
+ <xs:element name="execution" maxOccurs="unbounded" minOccurs="0">
<xs:complexType
mixed="true">
<xs:sequence>
+ <xs:element
name="transitionInputs" maxOccurs="unbounded" minOccurs="0">
+
<xs:complexType>
+
<xs:sequence>
+
<xs:element name="input" maxOccurs="unbounded" minOccurs="0">
+
<xs:complexType>
+
<xs:attribute name="name" use="required"/>
+
<xs:attribute name="type" use="required"/>
+
</xs:complexType>
+
</xs:element>
+
</xs:sequence>
+
</xs:complexType>
+ </xs:element>
<xs:element
name="parameter" maxOccurs="unbounded"
minOccurs="0">
<xs:complexType>
Thanks!
Isuruwan
On Thu, Apr 2, 2015 at 6:45 AM, Sagara Gunathunga <sag...@wso2.com> wrote:
>
> +1
>
> We used to have custom JSP for same purpose but that is not user friendly
> and hard to understand, I guess it was introduced to match with JSP based
> admin console. Now we have GC with better UI experience and ES technology
> hence it's time to simplify this model so that user only define how many
> inputs and what are the types of these inputs etc. while ES render nice UI
> based on user specification.
>
> One suggestion is instead of <form>, <transitionInputs> is much meaningful
> to me also Isuruwan please mention full spec as XSD diff.
>
> Thanks !
>
> On Wed, Apr 1, 2015 at 11:29 PM, Isuruwan Herath <isuru...@wso2.com>
> wrote:
>
>> Hi,
>>
>> In current g-reg we have the option of giving a transition UI for the
>> lifecycle transition in the management console. This UI is used to take the
>> user inputs for the executor logic.
>>
>> To incorporate this feature into the publisher view, we have come up with
>> the proposal of embedding a set of new elements in the LC definition. This
>> will be parsed from the publisher side and it will display a rendered page
>> for user inputs. To enable this we will modify the scxml.xsd and the user
>> will have to set the input parameters as follows:
>>
>> <data name="transitionExecution">
>> <execution forEvent="Promote"
>> class="org.wso2.carbon.governance.registry.extensions.executors.ServiceVersionExecutor">
>> *<form>*
>> * <input name="approver" type="text"/>*
>> * <input name="comment"
>> type="text-area"/>*
>> * </form>*
>> <parameter name="currentEnvironment"
>> value="/_system/governance/trunk/{@resourcePath}/{@version}/{@resourceName}"/>
>> <parameter name="targetEnvironment"
>> value="/_system/governance/branches/testing/{@resourcePath}/{@version}/{@resourceName}"/>
>> <parameter name="service.mediatype"
>> value="application/vnd.wso2-service+xml"/>
>> <parameter name="wsdl.mediatype"
>> value="application/wsdl+xml"/>
>> <parameter name="endpoint.mediatype"
>> value="application/vnd.wso2.endpoint"/>
>> </execution>
>> </data>
>> Appreciate any feedback about this approach.
>>
>> Thanks!
>> Isuruwan
>>
>> --
>> Isuruwan Herath
>> Technical Lead
>>
>> Contact: +94 776 273 296
>>
>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.; http://wso2.com
> V.P Apache Web Services; http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ; http://ssagara.blogspot.com
>
>
--
Isuruwan Herath
Technical Lead
Contact: +94 776 273 296
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
