Showing posts from June, 2013

How to revert all the local changes in SVN

When working with SVN now and then you will need to revert changes that was done by you or by applying a patch. Recently i wanted to revert all the changes done locally and found a nice command that can get this done :). Thanks goes to the original poster here.

svn st -q | awk '{print $2;}' | xargs svn revert
Hope this helps someone who is looking for the same functionality.

WSO2 Governance Registry - Lifecycle Management Part 1 - Check Items

The Lifecycle Management(LCM) plays a major role in SOA Governance. The default LCM supported by the WSO2 Governance Registry allows users to promote and demote life cycle states of a given resource. Furthermore, it can be configured to use checklists as well check out the documentation here.

The Lifecycle configuration templates allows advance users to extend its functionality through 6 data elements which are listed below
check itemstransition validationstransition permissionstransition executionstransition UItransition scriptsBellow is the full template of the lifecycle configuration. in this article series we will take a look at each item and see how they can be used to customize lifecycle management in WSO2 Governance Registry. In this article we will look at check items.

check items
Check items allow you to define a list, ideally an check list that can be used to control changes in lifecycle states and make sure specific requirements are met before the lifecycle is changed to the ne…

How to define XSD to allow any XML element as child element

While working on a new feature for WSO2 GREG i came across a requirement  to allow any arbitrary XML element to be passed as a child element and i needed to define this in an XSD file. After a bit of searching and some help i was able to find the correct XSD structure for this and thought i might be helpful to share it

<xs:element maxoccurs="unbounded" minoccurs="0" name="parameter"> <xs:complextype> <xs:sequence> <xs:any maxoccurs="unbounded" minoccurs="0" processcontents="skip"> </xs:any></xs:sequence> <xs:attribute name="name" type="xs:string" use="optional"> <xs:attribute name="value" type="xs:string" use="optional"> </xs:attribute></xs:attribute></xs:complextype> </xs:element>
The given XSD will allow an XML such as the example given below

<parameter name=…