Great, Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests. Ideally All AS Jaggery and MS tests should be passed, and samples need to work correctly.
Regards, /Nuwan On Wed, Jun 6, 2012 at 10:13 AM, Ruchira Wageesha <[email protected]> wrote: > >>> After integration of the MS and Jaggery in to AS. >>> When we call for jaggery application in second server start up It could >>> not initialize class org.wso2.carbon.scriptengine.engine.RhinoEngine. >>> In osgi level org.wso2.carbon.scriptengine_1.0.0.SNAPSHOT bundle is >>> active and it contains the org.wso2.carbon.scriptengine.engine.RhinoEngine >>> class. >>> Some MS bundle has blocked org.wso2.carbon.jaggery.core.manager >>> on accessing rhino engine class. >>> >>> Currently Ruchira is converting mashup deploy-er in to compilation mode >>> from interpreter mode. Those new MS codes will be used jaggery codes. >>> There for this could solve the problem. >>> >>> Jaggery and MS issue is depend on above task. Therefore I am pausing >>> this task (MS and Jaggery integration issue) till that MS >>> deployer rewriting complete. >>> When it is completed I will start this task and follow it. >>> >> > I have committed the re-written code to the trunk + an issue in XSLT > hostobject which also lead the conflict. Please update following components > and proceed. > > components/script-engine, > components/hostobjects, > components/mashup, > features/mashup > -- *Thanks & Regards, Nuwan Bandara Associate Technical Lead & Member, MC, Development Technologies WSO2 Inc. - lean . enterprise . middleware | http://wso2.com blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
