On Thu, Apr 2, 2015 at 7:53 PM, Sameera Medagammaddegedara < samee...@wso2.com> wrote:
> Hi, > > 1. When we add a new custom RXT to G-Reg, the integrated Publisher should >> also show it (without creating any ES asset extension). >> While testing this scenario for M4 (to be released) pack, the new >> RXT(application.rxt) is shown in the list down menu. Yet when I click the >> 'Add' button to add a new entry, following error occured >> > This is occurring due to the Publisher attempting to auto populate > provider names.Since the endpoint.rxt does not have a provider this is > causing the above issue when rendering the Create, Update and Details pages. > > This issue will be fixed prior to the next GREG milestone [1] > They are users waiting to evaluate GC from M3 release onwards and this is a very core use case for G-Reg, hence this issue is a blocker and we can't release G-Reg M4 with this issue, specially we can't break such important feature worked properly in previous releases. BTW this indicate we don't have enough test cases in both ES/G-Reg, @Denuwanthi, in the meantime can we add a test case to G-Reg to verify this issue ? > > 2. RXT hot deployment is not happening in Publisher. >> When we add a new RXT, from G-Reg admin console, and go to Publisher , it >> is not added in Publisher front. >> We need to restart the server in order to view it. This might be a >> problem in production environments if we have to restart the server. >> > Noted. This is a feature which we are planning to support in the future. > +1 we can wait for this feature. Thanks ! > > *Reference* > [1] https://wso2.org/jira/browse/STORE-663 > > Thank You, > Sameera > > On Thu, Apr 2, 2015 at 7:29 PM, Denuwanthi De Silva <denuwan...@wso2.com> > wrote: > >> Hi, >> >> While migrating G-Reg 5.0.0-SNAPSHOT UI to ES 2.0.1-SNAPSHOT, I faced the >> following issues: >> >> 1. When we add a new custom RXT to G-Reg, the integrated Publisher should >> also show it (without creating any ES asset extension). >> While testing this scenario for M4 (to be released) pack, the new >> RXT(application.rxt) is shown in the list down menu. Yet when I click the >> 'Add' button to add a new entry, following error occured >> >> HTTP Status 500 - org.mozilla.javascript.WrappedException: Wrapped >> org.jaggeryjs.scriptengine.exceptions.ScriptException: >> org.mozilla.javascript.EcmaError: TypeError: Cannot set property "value" of >> undefined to "org.mozilla.javascript.NativeJavaObject@4d817183" (eval >> code#1(eval)#266) (/publisher/controllers/assets-router.jag#75) >> What could be the issue for this? We should be able to support this >> without creating any custom asset extension. >> In the G-Reg 5.0.0 M3 pack, we did not occur any such error, and we could >> deploy a new RXT and add entries without problem. >> >> >> 2. RXT hot deployment is not happening in Publisher. >> When we add a new RXT, from G-Reg admin console, and go to Publisher , it >> is not added in Publisher front. >> We need to restart the server inorder to view it. This might be a problem >> in production environments if we have to restart the server. >> >> >> >> Thanks, >> >> -- >> Denuwanthi De Silva >> Software Engineer; >> WSO2 Inc.; http://wso2.com, >> Email: denuwan...@wso2.com >> Blog: https://denuwanthi.wordpress.com/ >> > > > > -- > Sameera Medagammaddegedara > Software Engineer > > Contact: > Email: samee...@wso2.com > Mobile: + 94 077 255 3005 > -- 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
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
