Hi Sumedha,
IMO, this is the first time, that one of our component used both Mozilla
Rhino(Jaggery) and Synapse core directly, which indirectly links BSF
embedded Rhino version too. Anyway, we will take this into consideration
when Rhino version of Jaggery is updated again.
/Ruchira
On Mon, May
On Sun, May 11, 2014 at 11:32 AM, Ruwan Yatawara wrote:
> Hi All,
>
> After much research, we rounded up the problem, this is caused by the API
> Manager host object using both synapse and jaggery. As I explained in my
> previous email, when we use two different bundles that use different
> versi
Hi All,
After much research, we rounded up the problem, this is caused by the API
Manager host object using both synapse and jaggery. As I explained in my
previous email, when we use two different bundles that use different
versions of the same package, inside the same class space, "package use
co
Hi,
This[1] can be helpful for such scenario,
And you issue encounter is correct,
*You can check some AS releases, where it also occurred and fixed as we
added jaggery and mashup to AS.*
[1]
http://madhukaudantha.blogspot.com/2014/02/writing-hostobject-for-jaggery.html
On Fri, May 9, 2014 at 8
Please meet me in the office. Will be able to help you.
/Ruchira
On Fri, May 9, 2014 at 12:02 AM, Ruwan Yatawara wrote:
> Hi All,
>
> We ran in to $subject when trying to use the script mediator in API
> Manager.
>
> When trying to use script mediator in AM APIs the following error is
> thrown
Hi All,
We ran in to $subject when trying to use the script mediator in API Manager.
When trying to use script mediator in AM APIs the following error is thrown.
*Caused by: java.lang.NoClassDefFoundError:
com/sun/phobos/script/javascript/RhinoScriptEngineFactory*
* at
org.apache.synapse.mediato
