Hi all, Eranda, someone needs to own this and do this. 1 week sounds too much for development. We need to get this sorted out by the end of this week. If there are any bugs we can take it up during the upcoming weeks, but doing what's mentioned here shouldn't take long as it is within the G-Reg domain.
1. Simply take a stable build 2. Fix the code inside the registry and governance components. 3. Compile the registry/governance components and the registry feature. 4. Compile the G-Reg product. That should save a lot of time during development and testing, we just need to ensure that the full build is passing only before the last commit. Thanks, Senaka. On Tue, Nov 27, 2012 at 9:59 AM, Eranda Sooriyabandara <[email protected]>wrote: > +1. I don't think we need lot of effort in this conversion. May be 1 x > week development + 1 x week (testing + fixing bugs). So if really want to > do this on this release that's also doable. Integration will be an > indicator of erroneous implementation. > Here are some steps to follow, > > 1. Create Service.rxt with the existing service mediatype. > 2. Add the UI Generator classes in org.wso2.carbon.governance.services.ui > to org.wso2.carbon.governance.generic.ui > 3. Rid of org.wso2.carbon.governance.services/ui > 4. Rid of ServiceManager Service/ServiceImpl in the > org.wso2.carbon.governance.api > 5. Rid of Tests if there are which are using > AddServiceServiceClient/ServiceManager. > > Please add if there is something I missed here. > For Policy/WSDL and Schema it will be different and should come up with an > improvement to the registry extension configuration. > > thanks > Eranda > > > thanks > Eranda > > > On Tue, Nov 27, 2012 at 6:43 AM, Senaka Fernando <[email protected]> wrote: > >> Hi all, >> >> We should take a firm decision and get rid of service altogether. The >> amount of time wasted on keeping these two in sync (and the time for >> testing etc) is much greater than the effort of getting rid of it. Next >> version of G-Reg will be 4.6.0, so I think it is time to ditch service and >> create an RXT for that. >> >> Thanks, >> Senaka. >> >> >> On Mon, Nov 26, 2012 at 10:33 PM, Eranda Sooriyabandara >> <[email protected]>wrote: >> >>> Hi Chethiya, >>> >>> >>>> I added new attribute called "<xs:attribute name="validate" >>>> type="xs:string"/>" to repository/resources/rxt.xsd and added new RXT with >>>> validate attribute in some fields. >>>> >>>> Now when I'm going to update the rxt it gives the following error. >>>> That's due to ManageGenericArtifactService using >>>> org.wso2.carbon.governance.services.util.Util to validate updated content. >>>> But that services.ui.Util class uses "service-ui-config.xsd" hardcoded in >>>> it to validate. >>>> >>>> Ah yes, in the configure, configuration update is >>> using service-ui-config.xsd to validate the service and the RXT contents. >>> >>> >>>> Is it correct to put "<xs:attribute name="validate" type="xs:string"/>" >>>> in "service-ui-config.xsd" too? In fact what are the usages >>>> of service-ui-config.xsd and rxt.xsd? >>>> >>>> Yes, you should do the same changes to the service-ui-config.xsd if it >>> is a change to the content. Though we have the same content we cannot keep >>> it in a single schema and import, because the content doesn't have a >>> separate namespace. >>> >>> thanks >>> Eranda >>> * >>> * >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > *Eranda Sooriyabandara > *Software Engineer; > Integration Technologies Team; > WSO2 Inc.; http://wso2.com > > * > * > > -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
