Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-10-27 Thread Madusanka Premaratne
15 10:02 PM > *To:* WSO2 Developers' List <dev@wso2.org>; Viral Shah < > vs...@turnberrysolutions.com> > *Subject:* Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to > 0.10.0 > > > > [Adding Dev] > > Hi Viral, > > This is due to a package exported

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-10-27 Thread Madusanka Premaratne
[Adding Dev] Hi Viral, This is due to a package exported by multiple bundles. The error occurs when OSGI picks wrong bundle while starting the server. As a quick workaround try restating WSO2 API manager, if OSGI picks the correct one it will work. Also please note that the issue is fixed in APIM

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-10-02 Thread Madusanka Premaratne
Hi All, The issue is due to incorrectly designed orbit bundles and solved by excluding those from bin.xml Thanks, Madusanka On Wed, Sep 16, 2015 at 9:45 AM, Madusanka Premaratne wrote: > Hi UES team, > I am getting following error intermittently. Which pops out from >

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-09-15 Thread Madusanka Premaratne
Hi UES team, I am getting following error intermittently. Which pops out from org.wso2.carbon.forum.registry.RegistryForumManager. As per my observations the particular package is visible to osgi. The OSGI outputs as follows. osgi> p org.wso2.carbon.forum.registry org.wso2.carbon.forum.registry;

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-29 Thread Madusanka Premaratne
Hi Tanya, The particular .jar exists in the classpath and I use the same java version (1.7.0_80) for both operations. For you to understand the problem, I added the jaggery code snippet which gives the error. var APIUtil = Packages.org.wso2.carbon.apimgt.impl.utils.APIUtil; providerValUe =

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-29 Thread Harsha Kumara
Hi Madusanka, What the value passing for the method argument? If all in place, it should be work. We have used same in 2.0.0. [1] - https://github.com/wso2/carbon-apimgt/blob/master/features/apimgt/org.wso2.carbon.apimgt.publisher.feature/src/main/resources/apipublisher/scripts/provider.js#L586

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-29 Thread Bhathiya Jayasekara
Hi Madusanka, Can you try this? var APIUtil = new Packages.org.wso2.carbon.apimgt.impl.utils.APIUtil(); // or new org.wso2.carbon.apimgt.impl.utils.APIUtil(); providerValUe = APIUtil.replaceEmailDomain(providerValUe); Thanks, Bhathiya On Wed, Jul 29, 2015 at 2:01 PM, Madusanka Premaratne

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-29 Thread Madusanka Premaratne
Hi Bhathiya, It is a static method. And when I try to instantiate it gives me the following error. 2015-07-29 14:14:23,818] ERROR - WebAppManager org.mozilla.javascript.EcmaError: TypeError: [JavaPackage org.wso2.carbon.apimgt.impl.utils.APIUtil] is not a function, it is object.

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-29 Thread Manuranga Perera
Hi Madusanka, it seems this org.wso2.carbon.apimgt.impl.utils.APIUtil class is not visible for jaggery for some reason. if you put a java brake point at org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)and try Class.forName to see if the class is visible we can narrow

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-29 Thread Bhathiya Jayasekara
If the method is static yours should work I think. On Wed, Jul 29, 2015 at 2:09 PM, Bhathiya Jayasekara bhath...@wso2.com wrote: Hi Madusanka, Can you try this? var APIUtil = new Packages.org.wso2.carbon.apimgt.impl.utils.APIUtil(); // or new org.wso2.carbon.apimgt.impl.utils.APIUtil();

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-29 Thread Madusanka Premaratne
Hi Manuranga, It does not recognise the class. I will come and talk to you tomorrow. Thanks for the help On Wed, Jul 29, 2015 at 3:04 PM, Manuranga Perera m...@wso2.com wrote: Hi Madusanka, it seems this org.wso2.carbon.apimgt.impl.utils.APIUtil class is not visible for jaggery for some

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-29 Thread Manuranga Perera
Next step is to take a look at OSGi console to see if org.wso2.carbon.apimgt.impl.utils package is exposed.sure we can take a look tomorrow. On Wed, Jul 29, 2015 at 5:33 PM, Madusanka Premaratne madusan...@wso2.com wrote: Hi Manuranga, It does not recognise the class. I will come and talk to

[Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-28 Thread Madusanka Premaratne
Hi all, I have recently updated jaggery version of APIM from 0.9.0 to 0.10.0 and API Store gives the following error. I checked that the method *raplaceEmailDomain* exists in *APIUtil* and I was not able to find out an issue. [2015-07-29 10:39:34,309] ERROR - WebAppManager

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

2015-07-28 Thread Tanya Madurapperuma
- Check whether the org.wso2.carbon.apimgt.impl.utils.APIUtil jar is available in the classpath. - Check whether the compiled java version of above jar and the java version you started the server are the same Thanks, Tanya On Wed, Jul 29, 2015 at 10:53 AM, Madusanka Premaratne