Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

hi, Kasun

yap, there we have created absolute path for link that is the reason.
I will fix that jaggery sample app, by making those links relative path.

thank you.

On Tue, Jun 12, 2012 at 5:12 PM, Kasun Gajasinghe  wrote:

> Hi Madhuka,
>
> I'm still building the trunk that has your new changes. But I have tested
> the Jaggery docs/ app in the pack I built few days ago.
> The app was broken. While the home page (index.jag) worked fine except a
> minor issue in the logo, the links in header are wrong. As I see they are
> missing the /docs/ context. For example, the link to Documentation looks
> like the following.
>
> http://localhost:9764/documentation.jag
>
> I have also attached a screenshot.
>
> Regards,
> --KasunG
>
>
> On Tue, Jun 12, 2012 at 4:58 PM, Madhuka Udantha  wrote:
>
>> hi,
>>
>> So by default, we can ship all samples we have, and if you want, you can
>> un-install them all using a tool or a command.
>> +1
>>
>> I will do it.
>>
>> By default,
>>
>>- *jaggery docs* is deployed as jaggery apps
>>- *RESTSample*.js is deployed  as mashup apps
>>
>> all other mashup samples can be found in
>> "wso2as-5.0.0-SNAPSHOT\samples\mashupSamples" and
>> Taskmaster and sample jaggery samples can be found in
>> "wso2as-5.0-SNAPSHOT\samples\jaggerySamples"
>>
>> In both sample locations you can find
>>
>>- README file  - that explain how deploy those samples to Appserver
>>- build.xml - for ant command
>>
>>
>> Thanks
>>
>>
>> On Sun, Jun 10, 2012 at 1:12 PM, Madhuka Udantha wrote:
>>
>>> hi,
>>>
>>> So by default, we can ship all samples we have, and if you want, you can
>>> un-install them all using a tool or a command.
>>> +1
>>>
>>> I will do it.
>>>
>>>
>>> On Sat, Jun 9, 2012 at 6:01 AM, Samisa Abeysinghe wrote:
>>>


 On Fri, Jun 8, 2012 at 9:29 PM, Kasun Gajasinghe wrote:

>
>
> On Fri, Jun 8, 2012 at 8:58 PM, Supun Malinga  wrote:
>
>>
>>
>> On Fri, Jun 8, 2012 at 8:41 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Hi,
>>> I see the following set of js-services(mashup) in the default
>>> service list (see attached screenshot). Should they be deployed by
>>> default?. I think they are meant for mashup samples. In that case we 
>>> should
>>> not deploy them by default. Or we can have few default js-services.
>>>
>> +1 for having one or two js-samples only.
>>
>>
> Only one AppServer sample is deployed by default in the packs
> (HelloWorld/HelloService). The echo, and Version comes from Kernel. So, 
> may
> be one sample from mashups is just enough.
>
>
 I think otherwise. It is the samples that help people learn what it is
 all about. Rather than removing exiting samples, what we really need to do
 is to have a means to install/uninstall all samples.

 So by default, we can ship all samples we have, and if you want, you
 can un-install them all using a tool or a command.



> Thanks,
> --KasunG
>
>
>> thanks,
>>
>>>
>>> Thanks,
>>> Kishanthan.
>>>
>>>
>>> On Thu, Jun 7, 2012 at 6:18 PM, Madhuka Udantha wrote:
>>>
 Hi,

 Jagger samples are tested in new packs.All jaggery samples worked
 fine and it is added to pack,
 Deploying issues are fixed.

 In MS samples were also added to pack,

- FormulaFlicks, RESTSample, TomatoTube, TwitterMap, Version
samples are working Fine
- Digit2image, ExchangeRate, FeedCache, GmapsAPIKey, Storexml,
UpgradeChecker are fails (Working on this)


 Those samples are broken in MS also,
 MS integration tests are been fails and currently we are looking in
 to those.

 After fixing integration tests it will committed to new AS pack

 Thank you


 On Thu, Jun 7, 2012 at 12:17 PM, Ruchira Wageesha >>> > wrote:

> Mashup + AS conflicts again due to the ntask(DS) and old
> scheduled-task(MS) components. Reason is, they depend on different 
> quartz
> versions.
>
> So, I am going to fix MS components to use ntask which would be
> better than having multiple quartz versions in AS.
>
>
> On Wed, Jun 6, 2012 at 3:47 PM, Nuwan Bandara wrote:
>
>> Madhuka, You cannot change the log level of those messages since
>> they are thrown from the framework, we need to find out the cause of 
>> it.
>> and fix it in some other way
>>
>>
>> On Wed, Jun 6, 2012 at 3:41 PM, Madhuka Udantha > > wrote:
>>
>>> hi, kishanthan
>>>
>>> saw warning messages, But in OSGI console those bundles are up
>>> correctly.
>>>
>>> [image: Inline image 1]
>>

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

hi,

So by default, we can ship all samples we have, and if you want, you can
un-install them all using a tool or a command.
+1

I will do it.

By default,

   - *jaggery docs* is deployed as jaggery apps
   - *RESTSample*.js is deployed  as mashup apps

all other mashup samples can be found in
"wso2as-5.0.0-SNAPSHOT\samples\mashupSamples" and
Taskmaster and sample jaggery samples can be found in
"wso2as-5.0-SNAPSHOT\samples\jaggerySamples"

In both sample locations you can find

   - README file  - that explain how deploy those samples to Appserver
   - build.xml - for ant command


Thanks

On Sun, Jun 10, 2012 at 1:12 PM, Madhuka Udantha  wrote:

> hi,
>
> So by default, we can ship all samples we have, and if you want, you can
> un-install them all using a tool or a command.
> +1
>
> I will do it.
>
>
> On Sat, Jun 9, 2012 at 6:01 AM, Samisa Abeysinghe  wrote:
>
>>
>>
>> On Fri, Jun 8, 2012 at 9:29 PM, Kasun Gajasinghe  wrote:
>>
>>>
>>>
>>> On Fri, Jun 8, 2012 at 8:58 PM, Supun Malinga  wrote:
>>>


 On Fri, Jun 8, 2012 at 8:41 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> Hi,
> I see the following set of js-services(mashup) in the default service
> list (see attached screenshot). Should they be deployed by default?. I
> think they are meant for mashup samples. In that case we should
> not deploy them by default. Or we can have few default js-services.
>
 +1 for having one or two js-samples only.


>>> Only one AppServer sample is deployed by default in the packs
>>> (HelloWorld/HelloService). The echo, and Version comes from Kernel. So, may
>>> be one sample from mashups is just enough.
>>>
>>>
>> I think otherwise. It is the samples that help people learn what it is
>> all about. Rather than removing exiting samples, what we really need to do
>> is to have a means to install/uninstall all samples.
>>
>> So by default, we can ship all samples we have, and if you want, you can
>> un-install them all using a tool or a command.
>>
>>
>>
>>> Thanks,
>>> --KasunG
>>>
>>>
 thanks,

>
> Thanks,
> Kishanthan.
>
>
> On Thu, Jun 7, 2012 at 6:18 PM, Madhuka Udantha wrote:
>
>> Hi,
>>
>> Jagger samples are tested in new packs.All jaggery samples worked
>> fine and it is added to pack,
>> Deploying issues are fixed.
>>
>> In MS samples were also added to pack,
>>
>>- FormulaFlicks, RESTSample, TomatoTube, TwitterMap, Version
>>samples are working Fine
>>- Digit2image, ExchangeRate, FeedCache, GmapsAPIKey, Storexml,
>>UpgradeChecker are fails (Working on this)
>>
>>
>> Those samples are broken in MS also,
>> MS integration tests are been fails and currently we are looking in
>> to those.
>>
>> After fixing integration tests it will committed to new AS pack
>>
>> Thank you
>>
>>
>> On Thu, Jun 7, 2012 at 12:17 PM, Ruchira Wageesha 
>> wrote:
>>
>>> Mashup + AS conflicts again due to the ntask(DS) and old
>>> scheduled-task(MS) components. Reason is, they depend on different 
>>> quartz
>>> versions.
>>>
>>> So, I am going to fix MS components to use ntask which would be
>>> better than having multiple quartz versions in AS.
>>>
>>>
>>> On Wed, Jun 6, 2012 at 3:47 PM, Nuwan Bandara wrote:
>>>
 Madhuka, You cannot change the log level of those messages since
 they are thrown from the framework, we need to find out the cause of 
 it.
 and fix it in some other way


 On Wed, Jun 6, 2012 at 3:41 PM, Madhuka Udantha 
 wrote:

> hi, kishanthan
>
> saw warning messages, But in OSGI console those bundles are up
> correctly.
>
> [image: Inline image 1]
>
> Reasons for that messages:
> JS Deployer initialization is delay till those host
> object bundles getting into active.
>
> It is to be INFO rather than WARN. I will correct it.
>
> Thanks
>
>
> On Wed, Jun 6, 2012 at 2:58 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> I'm seeing the following set of warnings at server start-up.
>>
>> [2012-06-06 14:54:14,906]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>>  -
>>  JS Deployer initialization is delayed due to the following 
>> unsatisfied
>> Host Objects..
>> [2012-06-06 14:54:14,908]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>>  -
>>  Waiting for required Host Object :
>> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
>> [2012-06-06 14:54:14,908]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServices

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

hi,

So by default, we can ship all samples we have, and if you want, you can
un-install them all using a tool or a command.
+1

I will do it.

On Sat, Jun 9, 2012 at 6:01 AM, Samisa Abeysinghe  wrote:

>
>
> On Fri, Jun 8, 2012 at 9:29 PM, Kasun Gajasinghe  wrote:
>
>>
>>
>> On Fri, Jun 8, 2012 at 8:58 PM, Supun Malinga  wrote:
>>
>>>
>>>
>>> On Fri, Jun 8, 2012 at 8:41 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 Hi,
 I see the following set of js-services(mashup) in the default service
 list (see attached screenshot). Should they be deployed by default?. I
 think they are meant for mashup samples. In that case we should
 not deploy them by default. Or we can have few default js-services.

>>> +1 for having one or two js-samples only.
>>>
>>>
>> Only one AppServer sample is deployed by default in the packs
>> (HelloWorld/HelloService). The echo, and Version comes from Kernel. So, may
>> be one sample from mashups is just enough.
>>
>>
> I think otherwise. It is the samples that help people learn what it is all
> about. Rather than removing exiting samples, what we really need to do is
> to have a means to install/uninstall all samples.
>
> So by default, we can ship all samples we have, and if you want, you can
> un-install them all using a tool or a command.
>
>
>
>> Thanks,
>> --KasunG
>>
>>
>>> thanks,
>>>

 Thanks,
 Kishanthan.


 On Thu, Jun 7, 2012 at 6:18 PM, Madhuka Udantha wrote:

> Hi,
>
> Jagger samples are tested in new packs.All jaggery samples worked fine
> and it is added to pack,
> Deploying issues are fixed.
>
> In MS samples were also added to pack,
>
>- FormulaFlicks, RESTSample, TomatoTube, TwitterMap, Version
>samples are working Fine
>- Digit2image, ExchangeRate, FeedCache, GmapsAPIKey, Storexml,
>UpgradeChecker are fails (Working on this)
>
>
> Those samples are broken in MS also,
> MS integration tests are been fails and currently we are looking in to
> those.
>
> After fixing integration tests it will committed to new AS pack
>
> Thank you
>
>
> On Thu, Jun 7, 2012 at 12:17 PM, Ruchira Wageesha wrote:
>
>> Mashup + AS conflicts again due to the ntask(DS) and old
>> scheduled-task(MS) components. Reason is, they depend on different quartz
>> versions.
>>
>> So, I am going to fix MS components to use ntask which would be
>> better than having multiple quartz versions in AS.
>>
>>
>> On Wed, Jun 6, 2012 at 3:47 PM, Nuwan Bandara  wrote:
>>
>>> Madhuka, You cannot change the log level of those messages since
>>> they are thrown from the framework, we need to find out the cause of it.
>>> and fix it in some other way
>>>
>>>
>>> On Wed, Jun 6, 2012 at 3:41 PM, Madhuka Udantha wrote:
>>>
 hi, kishanthan

 saw warning messages, But in OSGI console those bundles are up
 correctly.

 [image: Inline image 1]

 Reasons for that messages:
 JS Deployer initialization is delay till those host
 object bundles getting into active.

 It is to be INFO rather than WARN. I will correct it.

 Thanks


 On Wed, Jun 6, 2012 at 2:58 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> I'm seeing the following set of warnings at server start-up.
>
> [2012-06-06 14:54:14,906]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  JS Deployer initialization is delayed due to the following 
> unsatisfied
> Host Objects..
> [2012-06-06 14:54:14,908]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  Waiting for required Host Object :
> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
> [2012-06-06 14:54:14,908]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  Waiting for required Host Object :
> org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
> [2012-06-06 14:54:24,906]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  JS Deployer initialization is delayed due to the following 
> unsatisfied
> Host Objects..
> [2012-06-06 14:54:24,907]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  Waiting for required Host Object :
> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
> [2012-06-06 14:54:24,907]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  Waiting

Re: [Dev] Merging Jaggery with AS

[Kishanthan Thangarajah]

On Sat, Jun 9, 2012 at 6:01 AM, Samisa Abeysinghe  wrote:

>
>
> On Fri, Jun 8, 2012 at 9:29 PM, Kasun Gajasinghe  wrote:
>
>>
>>
>> On Fri, Jun 8, 2012 at 8:58 PM, Supun Malinga  wrote:
>>
>>>
>>>
>>> On Fri, Jun 8, 2012 at 8:41 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 Hi,
 I see the following set of js-services(mashup) in the default service
 list (see attached screenshot). Should they be deployed by default?. I
 think they are meant for mashup samples. In that case we should
 not deploy them by default. Or we can have few default js-services.

>>> +1 for having one or two js-samples only.
>>>
>>>
>> Only one AppServer sample is deployed by default in the packs
>> (HelloWorld/HelloService). The echo, and Version comes from Kernel. So, may
>> be one sample from mashups is just enough.
>>
>>
> I think otherwise. It is the samples that help people learn what it is all
> about. Rather than removing exiting samples, what we really need to do is
> to have a means to install/uninstall all samples.
>
> So by default, we can ship all samples we have, and if you want, you can
> un-install them all using a tool or a command.
>

A similar thing is done with the AppServer samples. We are shipping all of
them and each of them can be installed separately using ant (mostly) or
maven. Each of the samples has their own README which includes
the installation & running instructions. We could follow the same for
MS/Jaggery samples.

>
>
>
>> Thanks,
>> --KasunG
>>
>>
>>> thanks,
>>>

 Thanks,
 Kishanthan.


 On Thu, Jun 7, 2012 at 6:18 PM, Madhuka Udantha wrote:

> Hi,
>
> Jagger samples are tested in new packs.All jaggery samples worked fine
> and it is added to pack,
> Deploying issues are fixed.
>
> In MS samples were also added to pack,
>
>- FormulaFlicks, RESTSample, TomatoTube, TwitterMap, Version
>samples are working Fine
>- Digit2image, ExchangeRate, FeedCache, GmapsAPIKey, Storexml,
>UpgradeChecker are fails (Working on this)
>
>
> Those samples are broken in MS also,
> MS integration tests are been fails and currently we are looking in to
> those.
>
> After fixing integration tests it will committed to new AS pack
>
> Thank you
>
>
> On Thu, Jun 7, 2012 at 12:17 PM, Ruchira Wageesha wrote:
>
>> Mashup + AS conflicts again due to the ntask(DS) and old
>> scheduled-task(MS) components. Reason is, they depend on different quartz
>> versions.
>>
>> So, I am going to fix MS components to use ntask which would be
>> better than having multiple quartz versions in AS.
>>
>>
>> On Wed, Jun 6, 2012 at 3:47 PM, Nuwan Bandara  wrote:
>>
>>> Madhuka, You cannot change the log level of those messages since
>>> they are thrown from the framework, we need to find out the cause of it.
>>> and fix it in some other way
>>>
>>>
>>> On Wed, Jun 6, 2012 at 3:41 PM, Madhuka Udantha wrote:
>>>
 hi, kishanthan

 saw warning messages, But in OSGI console those bundles are up
 correctly.

 [image: Inline image 1]

 Reasons for that messages:
 JS Deployer initialization is delay till those host
 object bundles getting into active.

 It is to be INFO rather than WARN. I will correct it.

 Thanks


 On Wed, Jun 6, 2012 at 2:58 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> I'm seeing the following set of warnings at server start-up.
>
> [2012-06-06 14:54:14,906]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  JS Deployer initialization is delayed due to the following 
> unsatisfied
> Host Objects..
> [2012-06-06 14:54:14,908]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  Waiting for required Host Object :
> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
> [2012-06-06 14:54:14,908]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  Waiting for required Host Object :
> org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
> [2012-06-06 14:54:24,906]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  JS Deployer initialization is delayed due to the following 
> unsatisfied
> Host Objects..
> [2012-06-06 14:54:24,907]  WARN
> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
>  -
>  Waiting for required Host Object :
> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostOb

Re: [Dev] Merging Jaggery with AS

[Samisa Abeysinghe]

On Fri, Jun 8, 2012 at 9:29 PM, Kasun Gajasinghe  wrote:

>
>
> On Fri, Jun 8, 2012 at 8:58 PM, Supun Malinga  wrote:
>
>>
>>
>> On Fri, Jun 8, 2012 at 8:41 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Hi,
>>> I see the following set of js-services(mashup) in the default service
>>> list (see attached screenshot). Should they be deployed by default?. I
>>> think they are meant for mashup samples. In that case we should
>>> not deploy them by default. Or we can have few default js-services.
>>>
>> +1 for having one or two js-samples only.
>>
>>
> Only one AppServer sample is deployed by default in the packs
> (HelloWorld/HelloService). The echo, and Version comes from Kernel. So, may
> be one sample from mashups is just enough.
>
>
I think otherwise. It is the samples that help people learn what it is all
about. Rather than removing exiting samples, what we really need to do is
to have a means to install/uninstall all samples.

So by default, we can ship all samples we have, and if you want, you can
un-install them all using a tool or a command.



> Thanks,
> --KasunG
>
>
>> thanks,
>>
>>>
>>> Thanks,
>>> Kishanthan.
>>>
>>>
>>> On Thu, Jun 7, 2012 at 6:18 PM, Madhuka Udantha wrote:
>>>
 Hi,

 Jagger samples are tested in new packs.All jaggery samples worked fine
 and it is added to pack,
 Deploying issues are fixed.

 In MS samples were also added to pack,

- FormulaFlicks, RESTSample, TomatoTube, TwitterMap, Version
samples are working Fine
- Digit2image, ExchangeRate, FeedCache, GmapsAPIKey, Storexml,
UpgradeChecker are fails (Working on this)


 Those samples are broken in MS also,
 MS integration tests are been fails and currently we are looking in to
 those.

 After fixing integration tests it will committed to new AS pack

 Thank you


 On Thu, Jun 7, 2012 at 12:17 PM, Ruchira Wageesha wrote:

> Mashup + AS conflicts again due to the ntask(DS) and old
> scheduled-task(MS) components. Reason is, they depend on different quartz
> versions.
>
> So, I am going to fix MS components to use ntask which would be better
> than having multiple quartz versions in AS.
>
>
> On Wed, Jun 6, 2012 at 3:47 PM, Nuwan Bandara  wrote:
>
>> Madhuka, You cannot change the log level of those messages since they
>> are thrown from the framework, we need to find out the cause of it. and 
>> fix
>> it in some other way
>>
>>
>> On Wed, Jun 6, 2012 at 3:41 PM, Madhuka Udantha wrote:
>>
>>> hi, kishanthan
>>>
>>> saw warning messages, But in OSGI console those bundles are up
>>> correctly.
>>>
>>> [image: Inline image 1]
>>>
>>> Reasons for that messages:
>>> JS Deployer initialization is delay till those host
>>> object bundles getting into active.
>>>
>>> It is to be INFO rather than WARN. I will correct it.
>>>
>>> Thanks
>>>
>>>
>>> On Wed, Jun 6, 2012 at 2:58 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 I'm seeing the following set of warnings at server start-up.

 [2012-06-06 14:54:14,906]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
  -
  JS Deployer initialization is delayed due to the following unsatisfied
 Host Objects..
 [2012-06-06 14:54:14,908]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
  -
  Waiting for required Host Object :
 org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
 [2012-06-06 14:54:14,908]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
  -
  Waiting for required Host Object :
 org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
 [2012-06-06 14:54:24,906]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
  -
  JS Deployer initialization is delayed due to the following unsatisfied
 Host Objects..
 [2012-06-06 14:54:24,907]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
  -
  Waiting for required Host Object :
 org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
 [2012-06-06 14:54:24,907]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent}
  -
  Waiting for required Host Object :
 org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject


 On Wed, Jun 6, 2012 at 2:17 PM, Samisa Abeysinghe 
 wrote:

>
>
> On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha  > wrote:
>
>> hi,
>>
>> New AS

Re: [Dev] Merging Jaggery with AS

[Kasun Gajasinghe]

On Fri, Jun 8, 2012 at 8:58 PM, Supun Malinga  wrote:

>
>
> On Fri, Jun 8, 2012 at 8:41 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi,
>> I see the following set of js-services(mashup) in the default service
>> list (see attached screenshot). Should they be deployed by default?. I
>> think they are meant for mashup samples. In that case we should
>> not deploy them by default. Or we can have few default js-services.
>>
> +1 for having one or two js-samples only.
>
>
Only one AppServer sample is deployed by default in the packs
(HelloWorld/HelloService). The echo, and Version comes from Kernel. So, may
be one sample from mashups is just enough.

Thanks,
--KasunG


> thanks,
>
>>
>> Thanks,
>> Kishanthan.
>>
>>
>> On Thu, Jun 7, 2012 at 6:18 PM, Madhuka Udantha  wrote:
>>
>>> Hi,
>>>
>>> Jagger samples are tested in new packs.All jaggery samples worked fine
>>> and it is added to pack,
>>> Deploying issues are fixed.
>>>
>>> In MS samples were also added to pack,
>>>
>>>- FormulaFlicks, RESTSample, TomatoTube, TwitterMap, Version samples
>>>are working Fine
>>>- Digit2image, ExchangeRate, FeedCache, GmapsAPIKey, Storexml,
>>>UpgradeChecker are fails (Working on this)
>>>
>>>
>>> Those samples are broken in MS also,
>>> MS integration tests are been fails and currently we are looking in to
>>> those.
>>>
>>> After fixing integration tests it will committed to new AS pack
>>>
>>> Thank you
>>>
>>>
>>> On Thu, Jun 7, 2012 at 12:17 PM, Ruchira Wageesha wrote:
>>>
 Mashup + AS conflicts again due to the ntask(DS) and old
 scheduled-task(MS) components. Reason is, they depend on different quartz
 versions.

 So, I am going to fix MS components to use ntask which would be better
 than having multiple quartz versions in AS.


 On Wed, Jun 6, 2012 at 3:47 PM, Nuwan Bandara  wrote:

> Madhuka, You cannot change the log level of those messages since they
> are thrown from the framework, we need to find out the cause of it. and 
> fix
> it in some other way
>
>
> On Wed, Jun 6, 2012 at 3:41 PM, Madhuka Udantha wrote:
>
>> hi, kishanthan
>>
>> saw warning messages, But in OSGI console those bundles are up
>> correctly.
>>
>> [image: Inline image 1]
>>
>> Reasons for that messages:
>> JS Deployer initialization is delay till those host
>> object bundles getting into active.
>>
>> It is to be INFO rather than WARN. I will correct it.
>>
>> Thanks
>>
>>
>> On Wed, Jun 6, 2012 at 2:58 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> I'm seeing the following set of warnings at server start-up.
>>>
>>> [2012-06-06 14:54:14,906]  WARN
>>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} 
>>> -
>>>  JS Deployer initialization is delayed due to the following unsatisfied
>>> Host Objects..
>>> [2012-06-06 14:54:14,908]  WARN
>>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} 
>>> -
>>>  Waiting for required Host Object :
>>> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
>>> [2012-06-06 14:54:14,908]  WARN
>>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} 
>>> -
>>>  Waiting for required Host Object :
>>> org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
>>> [2012-06-06 14:54:24,906]  WARN
>>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} 
>>> -
>>>  JS Deployer initialization is delayed due to the following unsatisfied
>>> Host Objects..
>>> [2012-06-06 14:54:24,907]  WARN
>>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} 
>>> -
>>>  Waiting for required Host Object :
>>> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
>>> [2012-06-06 14:54:24,907]  WARN
>>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} 
>>> -
>>>  Waiting for required Host Object :
>>> org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
>>>
>>>
>>> On Wed, Jun 6, 2012 at 2:17 PM, Samisa Abeysinghe 
>>> wrote:
>>>


 On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha 
 wrote:

> hi,
>
> New AS+MS+Jaggery build OK,
>

 Does the pack work now with the new changes?


>
> yap, MS built failed, I will check on it too.
>
>
> On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara wrote:
>
>> Hi,
>>
>> There is a build failure in MS,
>>
>> Installation failed.
>> Cannot complete the install because one or more required items
>> could not be found.
>>  Software being installed: WSO2

Re: [Dev] Merging Jaggery with AS

[Supun Malinga]

On Fri, Jun 8, 2012 at 8:41 PM, Kishanthan Thangarajah
wrote:

> Hi,
> I see the following set of js-services(mashup) in the default service list
> (see attached screenshot). Should they be deployed by default?. I think
> they are meant for mashup samples. In that case we should not deploy them
> by default. Or we can have few default js-services.
>
+1 for having one or two js-samples only.

thanks,

>
> Thanks,
> Kishanthan.
>
>
> On Thu, Jun 7, 2012 at 6:18 PM, Madhuka Udantha  wrote:
>
>> Hi,
>>
>> Jagger samples are tested in new packs.All jaggery samples worked fine
>> and it is added to pack,
>> Deploying issues are fixed.
>>
>> In MS samples were also added to pack,
>>
>>- FormulaFlicks, RESTSample, TomatoTube, TwitterMap, Version samples
>>are working Fine
>>- Digit2image, ExchangeRate, FeedCache, GmapsAPIKey, Storexml,
>>UpgradeChecker are fails (Working on this)
>>
>>
>> Those samples are broken in MS also,
>> MS integration tests are been fails and currently we are looking in to
>> those.
>>
>> After fixing integration tests it will committed to new AS pack
>>
>> Thank you
>>
>>
>> On Thu, Jun 7, 2012 at 12:17 PM, Ruchira Wageesha wrote:
>>
>>> Mashup + AS conflicts again due to the ntask(DS) and old
>>> scheduled-task(MS) components. Reason is, they depend on different quartz
>>> versions.
>>>
>>> So, I am going to fix MS components to use ntask which would be better
>>> than having multiple quartz versions in AS.
>>>
>>>
>>> On Wed, Jun 6, 2012 at 3:47 PM, Nuwan Bandara  wrote:
>>>
 Madhuka, You cannot change the log level of those messages since they
 are thrown from the framework, we need to find out the cause of it. and fix
 it in some other way


 On Wed, Jun 6, 2012 at 3:41 PM, Madhuka Udantha wrote:

> hi, kishanthan
>
> saw warning messages, But in OSGI console those bundles are up
> correctly.
>
> [image: Inline image 1]
>
> Reasons for that messages:
> JS Deployer initialization is delay till those host
> object bundles getting into active.
>
> It is to be INFO rather than WARN. I will correct it.
>
> Thanks
>
>
> On Wed, Jun 6, 2012 at 2:58 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> I'm seeing the following set of warnings at server start-up.
>>
>> [2012-06-06 14:54:14,906]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
>>  JS Deployer initialization is delayed due to the following unsatisfied
>> Host Objects..
>> [2012-06-06 14:54:14,908]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
>>  Waiting for required Host Object :
>> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
>> [2012-06-06 14:54:14,908]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
>>  Waiting for required Host Object :
>> org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
>> [2012-06-06 14:54:24,906]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
>>  JS Deployer initialization is delayed due to the following unsatisfied
>> Host Objects..
>> [2012-06-06 14:54:24,907]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
>>  Waiting for required Host Object :
>> org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
>> [2012-06-06 14:54:24,907]  WARN
>> {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
>>  Waiting for required Host Object :
>> org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
>>
>>
>> On Wed, Jun 6, 2012 at 2:17 PM, Samisa Abeysinghe wrote:
>>
>>>
>>>
>>> On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha 
>>> wrote:
>>>
 hi,

 New AS+MS+Jaggery build OK,

>>>
>>> Does the pack work now with the new changes?
>>>
>>>

 yap, MS built failed, I will check on it too.


 On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara wrote:

> Hi,
>
> There is a build failure in MS,
>
> Installation failed.
> Cannot complete the install because one or more required items
> could not be found.
>  Software being installed: WSO2 Carbon - Javascript Service
> Hosting Feature 4.0.0.SNAPSHOT 
> (org.wso2.carbon.jsservices.feature.group
> 4.0.0.SNAPSHOT)
>  Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
> (org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
> com.google.gson [2.1.0,3.0.0)' but it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Javascript Service Hosting Feature
> 4.0.0.SNAPSHOT (

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

Hi,

Jagger samples are tested in new packs.All jaggery samples worked fine and
it is added to pack,
Deploying issues are fixed.

In MS samples were also added to pack,

   - FormulaFlicks, RESTSample, TomatoTube, TwitterMap, Version samples are
   working Fine
   - Digit2image, ExchangeRate, FeedCache, GmapsAPIKey, Storexml,
   UpgradeChecker are fails (Working on this)


Those samples are broken in MS also,
MS integration tests are been fails and currently we are looking in to
those.

After fixing integration tests it will committed to new AS pack

Thank you

On Thu, Jun 7, 2012 at 12:17 PM, Ruchira Wageesha  wrote:

> Mashup + AS conflicts again due to the ntask(DS) and old
> scheduled-task(MS) components. Reason is, they depend on different quartz
> versions.
>
> So, I am going to fix MS components to use ntask which would be better
> than having multiple quartz versions in AS.
>
>
> On Wed, Jun 6, 2012 at 3:47 PM, Nuwan Bandara  wrote:
>
>> Madhuka, You cannot change the log level of those messages since they are
>> thrown from the framework, we need to find out the cause of it. and fix it
>> in some other way
>>
>>
>> On Wed, Jun 6, 2012 at 3:41 PM, Madhuka Udantha  wrote:
>>
>>> hi, kishanthan
>>>
>>> saw warning messages, But in OSGI console those bundles are up correctly.
>>>
>>> [image: Inline image 1]
>>>
>>> Reasons for that messages:
>>> JS Deployer initialization is delay till those host
>>> object bundles getting into active.
>>>
>>> It is to be INFO rather than WARN. I will correct it.
>>>
>>> Thanks
>>>
>>>
>>> On Wed, Jun 6, 2012 at 2:58 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 I'm seeing the following set of warnings at server start-up.

 [2012-06-06 14:54:14,906]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
  JS Deployer initialization is delayed due to the following unsatisfied
 Host Objects..
 [2012-06-06 14:54:14,908]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
  Waiting for required Host Object :
 org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
 [2012-06-06 14:54:14,908]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
  Waiting for required Host Object :
 org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
 [2012-06-06 14:54:24,906]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
  JS Deployer initialization is delayed due to the following unsatisfied
 Host Objects..
 [2012-06-06 14:54:24,907]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
  Waiting for required Host Object :
 org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
 [2012-06-06 14:54:24,907]  WARN
 {org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
  Waiting for required Host Object :
 org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject


 On Wed, Jun 6, 2012 at 2:17 PM, Samisa Abeysinghe wrote:

>
>
> On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha wrote:
>
>> hi,
>>
>> New AS+MS+Jaggery build OK,
>>
>
> Does the pack work now with the new changes?
>
>
>>
>> yap, MS built failed, I will check on it too.
>>
>>
>> On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara wrote:
>>
>>> Hi,
>>>
>>> There is a build failure in MS,
>>>
>>> Installation failed.
>>> Cannot complete the install because one or more required items could
>>> not be found.
>>>  Software being installed: WSO2 Carbon - Javascript Service Hosting
>>> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group
>>> 4.0.0.SNAPSHOT)
>>>  Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
>>> (org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
>>> com.google.gson [2.1.0,3.0.0)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Javascript Service Hosting Feature
>>> 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.jsservices.server.feature.group
>>> [4.0.0.SNAPSHOT]
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Javascript Service Hosting Server Feature
>>> 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.server.feature.group
>>> 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.scriptengine [1.0.0.SNAPSHOT,1.1.0)
>>> Application failed, log file location:
>>> /home/nuwanbando/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1338960392351.log
>>>
>>>
>>> On Wed, Jun 6, 2012 at 11:04 AM, Madhuka Udantha 
>>> wrote:
>>>
 hi,

 I have committed the re-written code to the trunk
 +1

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

hi, samisa

Does the pack work now with the new changes?
yap,  it works,
But have some issue in 'hot deployment' but not from the changes. (Looking
in to it)
test with some Jaggery and MS samples, Work fine.

Currently I am adding jaggery/MS samples to AS pack


On Wed, Jun 6, 2012 at 2:17 PM, Samisa Abeysinghe  wrote:

>
>
> On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha  wrote:
>
>> hi,
>>
>> New AS+MS+Jaggery build OK,
>>
>
> Does the pack work now with the new changes?
>
>
>>
>> yap, MS built failed, I will check on it too.
>>
>>
>> On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara  wrote:
>>
>>> Hi,
>>>
>>> There is a build failure in MS,
>>>
>>> Installation failed.
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 Carbon - Javascript Service Hosting
>>> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group
>>> 4.0.0.SNAPSHOT)
>>>  Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
>>> (org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
>>> com.google.gson [2.1.0,3.0.0)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Javascript Service Hosting Feature 4.0.0.SNAPSHOT
>>> (org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.jsservices.server.feature.group [4.0.0.SNAPSHOT]
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Javascript Service Hosting Server Feature
>>> 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.server.feature.group
>>> 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.scriptengine [1.0.0.SNAPSHOT,1.1.0)
>>> Application failed, log file location:
>>> /home/nuwanbando/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1338960392351.log
>>>
>>>
>>> On Wed, Jun 6, 2012 at 11:04 AM, Madhuka Udantha wrote:
>>>
 hi,

 I have committed the re-written code to the trunk
 +1

 Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests.
 Yap, I am progressing on this.


 On Wed, Jun 6, 2012 at 10:24 AM, Nuwan Bandara  wrote:

> 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 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: nu...@wso2.com; phone: +94 11
> 763 9629
> *
> 
>



 --
 *Madhuka* Udantha
 http://madhukaudantha.blogspot.com/


>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Associate Technical Lead & Member, MC, Development Technologies
>>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>>> 9629
>>> *
>>> 
>>>
>>
>>
>>
>> --
>> *Madhuka* Udantha
>> http://madhukaudantha.blogspot.com/
>>
>>  Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>


-- 
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Kishanthan Thangarajah]

I'm seeing the following set of warnings at server start-up.

[2012-06-06 14:54:14,906]  WARN
{org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
 JS Deployer initialization is delayed due to the following unsatisfied
Host Objects..
[2012-06-06 14:54:14,908]  WARN
{org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
 Waiting for required Host Object :
org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
[2012-06-06 14:54:14,908]  WARN
{org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
 Waiting for required Host Object :
org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject
[2012-06-06 14:54:24,906]  WARN
{org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
 JS Deployer initialization is delayed due to the following unsatisfied
Host Objects..
[2012-06-06 14:54:24,907]  WARN
{org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
 Waiting for required Host Object :
org.wso2.carbon.mashup.javascript.hostobjects.system.SystemHostObject
[2012-06-06 14:54:24,907]  WARN
{org.wso2.carbon.mashup.jsservices.internal.JSServicesServiceComponent} -
 Waiting for required Host Object :
org.wso2.carbon.mashup.javascript.hostobjects.wsrequest.WSRequestHostObject


On Wed, Jun 6, 2012 at 2:17 PM, Samisa Abeysinghe  wrote:

>
>
> On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha  wrote:
>
>> hi,
>>
>> New AS+MS+Jaggery build OK,
>>
>
> Does the pack work now with the new changes?
>
>
>>
>> yap, MS built failed, I will check on it too.
>>
>>
>> On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara  wrote:
>>
>>> Hi,
>>>
>>> There is a build failure in MS,
>>>
>>> Installation failed.
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 Carbon - Javascript Service Hosting
>>> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group
>>> 4.0.0.SNAPSHOT)
>>>  Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
>>> (org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
>>> com.google.gson [2.1.0,3.0.0)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Javascript Service Hosting Feature 4.0.0.SNAPSHOT
>>> (org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.jsservices.server.feature.group [4.0.0.SNAPSHOT]
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Javascript Service Hosting Server Feature
>>> 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.server.feature.group
>>> 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.scriptengine [1.0.0.SNAPSHOT,1.1.0)
>>> Application failed, log file location:
>>> /home/nuwanbando/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1338960392351.log
>>>
>>>
>>> On Wed, Jun 6, 2012 at 11:04 AM, Madhuka Udantha wrote:
>>>
 hi,

 I have committed the re-written code to the trunk
 +1

 Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests.
 Yap, I am progressing on this.


 On Wed, Jun 6, 2012 at 10:24 AM, Nuwan Bandara  wrote:

> 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 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
> 

Re: [Dev] Merging Jaggery with AS

[Samisa Abeysinghe]

On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha  wrote:

> hi,
>
> New AS+MS+Jaggery build OK,
>

Does the pack work now with the new changes?


>
> yap, MS built failed, I will check on it too.
>
>
> On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara  wrote:
>
>> Hi,
>>
>> There is a build failure in MS,
>>
>> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Javascript Service Hosting
>> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group
>> 4.0.0.SNAPSHOT)
>>  Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
>> (org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
>> com.google.gson [2.1.0,3.0.0)' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Javascript Service Hosting Feature 4.0.0.SNAPSHOT
>> (org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
>>   To: org.wso2.carbon.jsservices.server.feature.group [4.0.0.SNAPSHOT]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Javascript Service Hosting Server Feature
>> 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.server.feature.group
>> 4.0.0.SNAPSHOT)
>>   To: org.wso2.carbon.scriptengine [1.0.0.SNAPSHOT,1.1.0)
>> Application failed, log file location:
>> /home/nuwanbando/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1338960392351.log
>>
>>
>> On Wed, Jun 6, 2012 at 11:04 AM, Madhuka Udantha wrote:
>>
>>> hi,
>>>
>>> I have committed the re-written code to the trunk
>>> +1
>>>
>>> Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests.
>>> Yap, I am progressing on this.
>>>
>>>
>>> On Wed, Jun 6, 2012 at 10:24 AM, Nuwan Bandara  wrote:
>>>
 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 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: nu...@wso2.com; phone: +94 11 763
 9629
 *
 

>>>
>>>
>>>
>>> --
>>> *Madhuka* Udantha
>>> http://madhukaudantha.blogspot.com/
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Associate Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>> 9629
>> *
>> 
>>
>
>
>
> --
> *Madhuka* Udantha
> http://madhukaudantha.blogspot.com/
>
>  Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

Ah am sorry, no, not to worry. we dont need MS to be built.
sure.

think you was able to build new AS+MS+Jaggery with out issue.?


On Wed, Jun 6, 2012 at 11:18 AM, Nuwan Bandara  wrote:

>
>
> On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha  wrote:
>
>> hi,
>>
>> New AS+MS+Jaggery build OK,
>>
>
> Ah am sorry, no, not to worry. we dont need MS to be built.
>
>
>>
>> yap, MS built failed, I will check on it too.
>>
>>
>> On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara  wrote:
>>
>>> Hi,
>>>
>>> There is a build failure in MS,
>>>
>>> Installation failed.
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 Carbon - Javascript Service Hosting
>>> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group
>>> 4.0.0.SNAPSHOT)
>>>  Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
>>> (org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
>>> com.google.gson [2.1.0,3.0.0)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Javascript Service Hosting Feature 4.0.0.SNAPSHOT
>>> (org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.jsservices.server.feature.group [4.0.0.SNAPSHOT]
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Javascript Service Hosting Server Feature
>>> 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.server.feature.group
>>> 4.0.0.SNAPSHOT)
>>>   To: org.wso2.carbon.scriptengine [1.0.0.SNAPSHOT,1.1.0)
>>> Application failed, log file location:
>>> /home/nuwanbando/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1338960392351.log
>>>
>>>
>>> On Wed, Jun 6, 2012 at 11:04 AM, Madhuka Udantha wrote:
>>>
 hi,

 I have committed the re-written code to the trunk
 +1

 Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests.
 Yap, I am progressing on this.


 On Wed, Jun 6, 2012 at 10:24 AM, Nuwan Bandara  wrote:

> 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 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: nu...@wso2.com; phone: +94 11
> 763 9629
> *
> 
>



 --
 *Madhuka* Udantha
 http://madhukaudantha.blogspot.com/


>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Associate Technical Lead & Member, MC, Development Technologies
>>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>>> 9629
>>> *
>>> 
>>>
>>
>>
>>
>> --
>> *Madhuka* Udantha
>> http://madhukaudantha.blogspot.com/
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Associate Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>



-- 
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/li

Re: [Dev] Merging Jaggery with AS

[Nuwan Bandara]

On Wed, Jun 6, 2012 at 11:15 AM, Madhuka Udantha  wrote:

> hi,
>
> New AS+MS+Jaggery build OK,
>

Ah am sorry, no, not to worry. we dont need MS to be built.


>
> yap, MS built failed, I will check on it too.
>
>
> On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara  wrote:
>
>> Hi,
>>
>> There is a build failure in MS,
>>
>> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Javascript Service Hosting
>> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group
>> 4.0.0.SNAPSHOT)
>>  Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
>> (org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
>> com.google.gson [2.1.0,3.0.0)' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Javascript Service Hosting Feature 4.0.0.SNAPSHOT
>> (org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
>>   To: org.wso2.carbon.jsservices.server.feature.group [4.0.0.SNAPSHOT]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Javascript Service Hosting Server Feature
>> 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.server.feature.group
>> 4.0.0.SNAPSHOT)
>>   To: org.wso2.carbon.scriptengine [1.0.0.SNAPSHOT,1.1.0)
>> Application failed, log file location:
>> /home/nuwanbando/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1338960392351.log
>>
>>
>> On Wed, Jun 6, 2012 at 11:04 AM, Madhuka Udantha wrote:
>>
>>> hi,
>>>
>>> I have committed the re-written code to the trunk
>>> +1
>>>
>>> Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests.
>>> Yap, I am progressing on this.
>>>
>>>
>>> On Wed, Jun 6, 2012 at 10:24 AM, Nuwan Bandara  wrote:
>>>
 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 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: nu...@wso2.com; phone: +94 11 763
 9629
 *
 

>>>
>>>
>>>
>>> --
>>> *Madhuka* Udantha
>>> http://madhukaudantha.blogspot.com/
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Associate Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>> 9629
>> *
>> 
>>
>
>
>
> --
> *Madhuka* Udantha
> http://madhukaudantha.blogspot.com/
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

hi,

New AS+MS+Jaggery build OK,

yap, MS built failed, I will check on it too.

On Wed, Jun 6, 2012 at 11:07 AM, Nuwan Bandara  wrote:

> Hi,
>
> There is a build failure in MS,
>
> Installation failed.
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: WSO2 Carbon - Javascript Service Hosting
> Feature 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group
> 4.0.0.SNAPSHOT)
>  Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
> (org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
> com.google.gson [2.1.0,3.0.0)' but it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Javascript Service Hosting Feature 4.0.0.SNAPSHOT
> (org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
>   To: org.wso2.carbon.jsservices.server.feature.group [4.0.0.SNAPSHOT]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Javascript Service Hosting Server Feature
> 4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.server.feature.group
> 4.0.0.SNAPSHOT)
>   To: org.wso2.carbon.scriptengine [1.0.0.SNAPSHOT,1.1.0)
> Application failed, log file location:
> /home/nuwanbando/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1338960392351.log
>
>
> On Wed, Jun 6, 2012 at 11:04 AM, Madhuka Udantha  wrote:
>
>> hi,
>>
>> I have committed the re-written code to the trunk
>> +1
>>
>> Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests.
>> Yap, I am progressing on this.
>>
>>
>> On Wed, Jun 6, 2012 at 10:24 AM, Nuwan Bandara  wrote:
>>
>>> 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 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: nu...@wso2.com; phone: +94 11 763
>>> 9629
>>> *
>>> 
>>>
>>
>>
>>
>> --
>> *Madhuka* Udantha
>> http://madhukaudantha.blogspot.com/
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Associate Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>



-- 
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Nuwan Bandara]

Hi,

There is a build failure in MS,

Installation failed.
Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 Carbon - Javascript Service Hosting Feature
4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
 Missing requirement: org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT
(org.wso2.carbon.scriptengine 1.0.0.SNAPSHOT) requires 'package
com.google.gson [2.1.0,3.0.0)' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Javascript Service Hosting Feature 4.0.0.SNAPSHOT
(org.wso2.carbon.jsservices.feature.group 4.0.0.SNAPSHOT)
  To: org.wso2.carbon.jsservices.server.feature.group [4.0.0.SNAPSHOT]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Javascript Service Hosting Server Feature
4.0.0.SNAPSHOT (org.wso2.carbon.jsservices.server.feature.group
4.0.0.SNAPSHOT)
  To: org.wso2.carbon.scriptengine [1.0.0.SNAPSHOT,1.1.0)
Application failed, log file location:
/home/nuwanbando/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1338960392351.log


On Wed, Jun 6, 2012 at 11:04 AM, Madhuka Udantha  wrote:

> hi,
>
> I have committed the re-written code to the trunk
> +1
>
> Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests.
> Yap, I am progressing on this.
>
>
> On Wed, Jun 6, 2012 at 10:24 AM, Nuwan Bandara  wrote:
>
>> 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 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: nu...@wso2.com; phone: +94 11 763
>> 9629
>> *
>> 
>>
>
>
>
> --
> *Madhuka* Udantha
> http://madhukaudantha.blogspot.com/
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

hi,

I have committed the re-written code to the trunk
+1

Madhuka, can you proceed, with MS/Jaggery/AS all in one product tests.
Yap, I am progressing on this.


On Wed, Jun 6, 2012 at 10:24 AM, Nuwan Bandara  wrote:

> 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 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: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>



-- 
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Nuwan Bandara]

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  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: nu...@wso2.com; phone: +94 11 763 9629
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Ruchira Wageesha]

>
>
>> 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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Isuru Suriarachchi]

Noted.

Thanks,
~Isuru

On Wed, May 30, 2012 at 4:43 PM, Samisa Abeysinghe  wrote:

> We need a full round of testing to call this done-done.
>
> Need to test all samples in all of AS, Jag and MS.
> Need to deploy all of those into one running instance and test.
> Need to include all Jag and MS samples as part of AS integration tests
> Need to test all security aspects
> Need to do a profiling with all of AS, MS and Jag in place
> Need to do a performance test with all of AS, MS and Jag in place
> Need to test the cloud aspects, with Stratos service - meaning we need to
> test all above with cloud aspects in place
>
> The QA team is not available right now to do all these, hence AS + Jaggery
> teams need to own this.
>
> Please keep posted on the progress made.
>
>
> On Wed, May 30, 2012 at 4:17 PM, Kasun Gajasinghe  wrote:
>
>> Hi Madhuka,
>>
>> For AppServer, please test a generic web-app, a jaxws web-app
>> functionality as well. At one point, I saw the left pane doesn't have the
>> generic web-app related links.
>>
>> Thanks,
>> --KasunG
>>
>>
>> On Wed, May 30, 2012 at 3:50 PM, Madhuka Udantha wrote:
>>
>>> Hi, Nuwan
>>>
>>> Pack was build successfully and start finely.
>>> Now we can see
>>>
>>>- Jaggery Applications in jagery
>>>- JAX-WS/JAX-RS, JavaScript Service Applications from Mashup
>>>- Applications from AS
>>>
>>> In new AS packs, Is there any thing that I have miss?
>>>
>>> But still I am testing each feature on each server from samples.
>>> Still there can be issues and I am doing some smoke test on new packs.
>>>
>>> When it is complete I will inform in this thread.
>>>
>>>
>>>
>>> On Wed, May 30, 2012 at 3:30 PM, Nuwan Bandara  wrote:
>>>
 Madhuka,

 Did MS features + AS worked okey ?

 Regards,
 /Nuwan


 On Wed, May 30, 2012 at 3:23 PM, Madhuka Udantha wrote:

> Hi, Samisa
>
> Merging Jaggery and AS was ok,
>
> Pack was built with MS,Jaggery in to AS.
> Currently I am  trying samples on each product with in new AS pack.
>
> Thanks
>
>
> On Wed, May 30, 2012 at 2:47 PM, Samisa Abeysinghe wrote:
>
>> Maduka, can you send an update on the progress made in merging Jag &
>> MS into AS?
>>
>>
>> On Wed, May 23, 2012 at 6:35 AM, Samisa Abeysinghe 
>> wrote:
>>
>>>
>>>
>>> On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara wrote:
>>>
 Yes its straight forward, in fact the API product and appfactory
 doing it successfully right now. we need to add Jaggery and MS 
 features to
 AS. however when including jaggery and MS both there mite be conflicts.
 lets try this and see.
>>>
>>>
>>> I would rather not put MS in this release itself.
>>> Even Jaggery, if it works out of the box, we can ship. Else, we have
>>> other priorities such as JAX-RS and JAX-WS to worry about. And we are at
>>> the point of feature freeze. So not more new changes please...
>>>
>>>


 On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi <
 is...@wso2.com> wrote:

> Hi all,
>
> Are we going to merge Jaggery with AS for this release?
>
> If so, Nuwan are there any gray areas in doing this? Should be
> straight forward, isn't it?
>
> ~Isuru
>
> --
> Isuru Suriarachchi
> Technical Lead
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>


 --
 *Thanks & Regards,

 Nuwan Bandara
 Associate Technical Lead & Member, MC, Development Technologies
 WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
 blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11
 763 9629
 *
 

>>>
>>>  Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>
>
> --
> *Madhuka* Udantha
> http://madhukaudantha.blogspot.com/
>
>


 --
 *Thanks & Regards,

 Nuwan Bandara
 Associate Technical Lead & Member, MC, Development Technologies
 WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
 blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
 9629
 *
 

>>>
>>>
>>>
>>> --
>>> *Madhuka* Udantha
>>> http://madhukaudantha.blogspot.com/
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> Development Technologies Team, WSO2 Inc.; http://

Re: [Dev] Merging Jaggery with AS

[Samisa Abeysinghe]

We need a full round of testing to call this done-done.

Need to test all samples in all of AS, Jag and MS.
Need to deploy all of those into one running instance and test.
Need to include all Jag and MS samples as part of AS integration tests
Need to test all security aspects
Need to do a profiling with all of AS, MS and Jag in place
Need to do a performance test with all of AS, MS and Jag in place
Need to test the cloud aspects, with Stratos service - meaning we need to
test all above with cloud aspects in place

The QA team is not available right now to do all these, hence AS + Jaggery
teams need to own this.

Please keep posted on the progress made.

On Wed, May 30, 2012 at 4:17 PM, Kasun Gajasinghe  wrote:

> Hi Madhuka,
>
> For AppServer, please test a generic web-app, a jaxws web-app
> functionality as well. At one point, I saw the left pane doesn't have the
> generic web-app related links.
>
> Thanks,
> --KasunG
>
>
> On Wed, May 30, 2012 at 3:50 PM, Madhuka Udantha  wrote:
>
>> Hi, Nuwan
>>
>> Pack was build successfully and start finely.
>> Now we can see
>>
>>- Jaggery Applications in jagery
>>- JAX-WS/JAX-RS, JavaScript Service Applications from Mashup
>>- Applications from AS
>>
>> In new AS packs, Is there any thing that I have miss?
>>
>> But still I am testing each feature on each server from samples.
>> Still there can be issues and I am doing some smoke test on new packs.
>>
>> When it is complete I will inform in this thread.
>>
>>
>>
>> On Wed, May 30, 2012 at 3:30 PM, Nuwan Bandara  wrote:
>>
>>> Madhuka,
>>>
>>> Did MS features + AS worked okey ?
>>>
>>> Regards,
>>> /Nuwan
>>>
>>>
>>> On Wed, May 30, 2012 at 3:23 PM, Madhuka Udantha wrote:
>>>
 Hi, Samisa

 Merging Jaggery and AS was ok,

 Pack was built with MS,Jaggery in to AS.
 Currently I am  trying samples on each product with in new AS pack.

 Thanks


 On Wed, May 30, 2012 at 2:47 PM, Samisa Abeysinghe wrote:

> Maduka, can you send an update on the progress made in merging Jag &
> MS into AS?
>
>
> On Wed, May 23, 2012 at 6:35 AM, Samisa Abeysinghe wrote:
>
>>
>>
>> On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara wrote:
>>
>>> Yes its straight forward, in fact the API product and appfactory
>>> doing it successfully right now. we need to add Jaggery and MS features 
>>> to
>>> AS. however when including jaggery and MS both there mite be conflicts.
>>> lets try this and see.
>>
>>
>> I would rather not put MS in this release itself.
>> Even Jaggery, if it works out of the box, we can ship. Else, we have
>> other priorities such as JAX-RS and JAX-WS to worry about. And we are at
>> the point of feature freeze. So not more new changes please...
>>
>>
>>>
>>>
>>> On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi >> > wrote:
>>>
 Hi all,

 Are we going to merge Jaggery with AS for this release?

 If so, Nuwan are there any gray areas in doing this? Should be
 straight forward, isn't it?

 ~Isuru

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Associate Technical Lead & Member, MC, Development Technologies
>>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11
>>> 763 9629
>>> *
>>> 
>>>
>>
>>  Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>


 --
 *Madhuka* Udantha
 http://madhukaudantha.blogspot.com/


>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Associate Technical Lead & Member, MC, Development Technologies
>>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>>> 9629
>>> *
>>> 
>>>
>>
>>
>>
>> --
>> *Madhuka* Udantha
>> http://madhukaudantha.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> Development Technologies Team, WSO2 Inc.; http://wso2.com ,
> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
> *
>  *blog: **http://blog.kasunbg.org* *
> twitter: **http://twitter.com/kasunbg* *
> *
>
>
> _

Re: [Dev] Merging Jaggery with AS

[Kasun Gajasinghe]

Hi Madhuka,

For AppServer, please test a generic web-app, a jaxws web-app functionality
as well. At one point, I saw the left pane doesn't have the generic web-app
related links.

Thanks,
--KasunG


On Wed, May 30, 2012 at 3:50 PM, Madhuka Udantha  wrote:

> Hi, Nuwan
>
> Pack was build successfully and start finely.
> Now we can see
>
>- Jaggery Applications in jagery
>- JAX-WS/JAX-RS, JavaScript Service Applications from Mashup
>- Applications from AS
>
> In new AS packs, Is there any thing that I have miss?
>
> But still I am testing each feature on each server from samples.
> Still there can be issues and I am doing some smoke test on new packs.
>
> When it is complete I will inform in this thread.
>
>
>
> On Wed, May 30, 2012 at 3:30 PM, Nuwan Bandara  wrote:
>
>> Madhuka,
>>
>> Did MS features + AS worked okey ?
>>
>> Regards,
>> /Nuwan
>>
>>
>> On Wed, May 30, 2012 at 3:23 PM, Madhuka Udantha wrote:
>>
>>> Hi, Samisa
>>>
>>> Merging Jaggery and AS was ok,
>>>
>>> Pack was built with MS,Jaggery in to AS.
>>> Currently I am  trying samples on each product with in new AS pack.
>>>
>>> Thanks
>>>
>>>
>>> On Wed, May 30, 2012 at 2:47 PM, Samisa Abeysinghe wrote:
>>>
 Maduka, can you send an update on the progress made in merging Jag & MS
 into AS?


 On Wed, May 23, 2012 at 6:35 AM, Samisa Abeysinghe wrote:

>
>
> On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara  wrote:
>
>> Yes its straight forward, in fact the API product and appfactory
>> doing it successfully right now. we need to add Jaggery and MS features 
>> to
>> AS. however when including jaggery and MS both there mite be conflicts.
>> lets try this and see.
>
>
> I would rather not put MS in this release itself.
> Even Jaggery, if it works out of the box, we can ship. Else, we have
> other priorities such as JAX-RS and JAX-WS to worry about. And we are at
> the point of feature freeze. So not more new changes please...
>
>
>>
>>
>> On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi 
>> wrote:
>>
>>> Hi all,
>>>
>>> Are we going to merge Jaggery with AS for this release?
>>>
>>> If so, Nuwan are there any gray areas in doing this? Should be
>>> straight forward, isn't it?
>>>
>>> ~Isuru
>>>
>>> --
>>> Isuru Suriarachchi
>>> Technical Lead
>>> WSO2 Inc. http://wso2.com
>>> email : is...@wso2.com
>>> blog : http://isurues.wordpress.com/
>>>
>>> lean . enterprise . middleware
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Associate Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11
>> 763 9629
>> *
>> 
>>
>
>  Thanks,
 Samisa...

 Samisa Abeysinghe
 VP Engineering
 WSO2 Inc.
 http://wso2.com
 http://wso2.org



>>>
>>>
>>> --
>>> *Madhuka* Udantha
>>> http://madhukaudantha.blogspot.com/
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Associate Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>> 9629
>> *
>> 
>>
>
>
>
> --
> *Madhuka* Udantha
> http://madhukaudantha.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kasun Gajasinghe*
Software Engineer;
Development Technologies Team, WSO2 Inc.; http://wso2.com ,
*email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe*
*
*blog: **http://blog.kasunbg.org* *
twitter: **http://twitter.com/kasunbg* *
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Nuwan Bandara]

Good progress, run the samples and see whats broken

On Wed, May 30, 2012 at 3:50 PM, Madhuka Udantha  wrote:

> Hi, Nuwan
>
> Pack was build successfully and start finely.
> Now we can see
>
>- Jaggery Applications in jagery
>- JAX-WS/JAX-RS, JavaScript Service Applications from Mashup
>- Applications from AS
>
> In new AS packs, Is there any thing that I have miss?
>
> But still I am testing each feature on each server from samples.
> Still there can be issues and I am doing some smoke test on new packs.
>
> When it is complete I will inform in this thread.
>
>
>
> On Wed, May 30, 2012 at 3:30 PM, Nuwan Bandara  wrote:
>
>> Madhuka,
>>
>> Did MS features + AS worked okey ?
>>
>> Regards,
>> /Nuwan
>>
>>
>> On Wed, May 30, 2012 at 3:23 PM, Madhuka Udantha wrote:
>>
>>> Hi, Samisa
>>>
>>> Merging Jaggery and AS was ok,
>>>
>>> Pack was built with MS,Jaggery in to AS.
>>> Currently I am  trying samples on each product with in new AS pack.
>>>
>>> Thanks
>>>
>>>
>>> On Wed, May 30, 2012 at 2:47 PM, Samisa Abeysinghe wrote:
>>>
 Maduka, can you send an update on the progress made in merging Jag & MS
 into AS?


 On Wed, May 23, 2012 at 6:35 AM, Samisa Abeysinghe wrote:

>
>
> On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara  wrote:
>
>> Yes its straight forward, in fact the API product and appfactory
>> doing it successfully right now. we need to add Jaggery and MS features 
>> to
>> AS. however when including jaggery and MS both there mite be conflicts.
>> lets try this and see.
>
>
> I would rather not put MS in this release itself.
> Even Jaggery, if it works out of the box, we can ship. Else, we have
> other priorities such as JAX-RS and JAX-WS to worry about. And we are at
> the point of feature freeze. So not more new changes please...
>
>
>>
>>
>> On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi 
>> wrote:
>>
>>> Hi all,
>>>
>>> Are we going to merge Jaggery with AS for this release?
>>>
>>> If so, Nuwan are there any gray areas in doing this? Should be
>>> straight forward, isn't it?
>>>
>>> ~Isuru
>>>
>>> --
>>> Isuru Suriarachchi
>>> Technical Lead
>>> WSO2 Inc. http://wso2.com
>>> email : is...@wso2.com
>>> blog : http://isurues.wordpress.com/
>>>
>>> lean . enterprise . middleware
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Associate Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11
>> 763 9629
>> *
>> 
>>
>
>  Thanks,
 Samisa...

 Samisa Abeysinghe
 VP Engineering
 WSO2 Inc.
 http://wso2.com
 http://wso2.org



>>>
>>>
>>> --
>>> *Madhuka* Udantha
>>> http://madhukaudantha.blogspot.com/
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Associate Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>> 9629
>> *
>> 
>>
>
>
>
> --
> *Madhuka* Udantha
> http://madhukaudantha.blogspot.com/
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

Hi, Nuwan

Pack was build successfully and start finely.
Now we can see

   - Jaggery Applications in jagery
   - JAX-WS/JAX-RS, JavaScript Service Applications from Mashup
   - Applications from AS

In new AS packs, Is there any thing that I have miss?

But still I am testing each feature on each server from samples.
Still there can be issues and I am doing some smoke test on new packs.

When it is complete I will inform in this thread.



On Wed, May 30, 2012 at 3:30 PM, Nuwan Bandara  wrote:

> Madhuka,
>
> Did MS features + AS worked okey ?
>
> Regards,
> /Nuwan
>
>
> On Wed, May 30, 2012 at 3:23 PM, Madhuka Udantha  wrote:
>
>> Hi, Samisa
>>
>> Merging Jaggery and AS was ok,
>>
>> Pack was built with MS,Jaggery in to AS.
>> Currently I am  trying samples on each product with in new AS pack.
>>
>> Thanks
>>
>>
>> On Wed, May 30, 2012 at 2:47 PM, Samisa Abeysinghe wrote:
>>
>>> Maduka, can you send an update on the progress made in merging Jag & MS
>>> into AS?
>>>
>>>
>>> On Wed, May 23, 2012 at 6:35 AM, Samisa Abeysinghe wrote:
>>>


 On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara  wrote:

> Yes its straight forward, in fact the API product and appfactory doing
> it successfully right now. we need to add Jaggery and MS features to AS.
> however when including jaggery and MS both there mite be conflicts. lets
> try this and see.


 I would rather not put MS in this release itself.
 Even Jaggery, if it works out of the box, we can ship. Else, we have
 other priorities such as JAX-RS and JAX-WS to worry about. And we are at
 the point of feature freeze. So not more new changes please...


>
>
> On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi 
> wrote:
>
>> Hi all,
>>
>> Are we going to merge Jaggery with AS for this release?
>>
>> If so, Nuwan are there any gray areas in doing this? Should be
>> straight forward, isn't it?
>>
>> ~Isuru
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Associate Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11
> 763 9629
> *
> 
>

  Thanks,
>>> Samisa...
>>>
>>> Samisa Abeysinghe
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>>
>>>
>>>
>>
>>
>> --
>> *Madhuka* Udantha
>> http://madhukaudantha.blogspot.com/
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Associate Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>



-- 
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Nuwan Bandara]

Madhuka,

Did MS features + AS worked okey ?

Regards,
/Nuwan

On Wed, May 30, 2012 at 3:23 PM, Madhuka Udantha  wrote:

> Hi, Samisa
>
> Merging Jaggery and AS was ok,
>
> Pack was built with MS,Jaggery in to AS.
> Currently I am  trying samples on each product with in new AS pack.
>
> Thanks
>
>
> On Wed, May 30, 2012 at 2:47 PM, Samisa Abeysinghe wrote:
>
>> Maduka, can you send an update on the progress made in merging Jag & MS
>> into AS?
>>
>>
>> On Wed, May 23, 2012 at 6:35 AM, Samisa Abeysinghe wrote:
>>
>>>
>>>
>>> On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara  wrote:
>>>
 Yes its straight forward, in fact the API product and appfactory doing
 it successfully right now. we need to add Jaggery and MS features to AS.
 however when including jaggery and MS both there mite be conflicts. lets
 try this and see.
>>>
>>>
>>> I would rather not put MS in this release itself.
>>> Even Jaggery, if it works out of the box, we can ship. Else, we have
>>> other priorities such as JAX-RS and JAX-WS to worry about. And we are at
>>> the point of feature freeze. So not more new changes please...
>>>
>>>


 On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi wrote:

> Hi all,
>
> Are we going to merge Jaggery with AS for this release?
>
> If so, Nuwan are there any gray areas in doing this? Should be
> straight forward, isn't it?
>
> ~Isuru
>
> --
> Isuru Suriarachchi
> Technical Lead
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>


 --
 *Thanks & Regards,

 Nuwan Bandara
 Associate Technical Lead & Member, MC, Development Technologies
 WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
 blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
 9629
 *
 

>>>
>>>  Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>
>
> --
> *Madhuka* Udantha
> http://madhukaudantha.blogspot.com/
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Madhuka Udantha]

Hi, Samisa

Merging Jaggery and AS was ok,

Pack was built with MS,Jaggery in to AS.
Currently I am  trying samples on each product with in new AS pack.

Thanks

On Wed, May 30, 2012 at 2:47 PM, Samisa Abeysinghe  wrote:

> Maduka, can you send an update on the progress made in merging Jag & MS
> into AS?
>
>
> On Wed, May 23, 2012 at 6:35 AM, Samisa Abeysinghe wrote:
>
>>
>>
>> On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara  wrote:
>>
>>> Yes its straight forward, in fact the API product and appfactory doing
>>> it successfully right now. we need to add Jaggery and MS features to AS.
>>> however when including jaggery and MS both there mite be conflicts. lets
>>> try this and see.
>>
>>
>> I would rather not put MS in this release itself.
>> Even Jaggery, if it works out of the box, we can ship. Else, we have
>> other priorities such as JAX-RS and JAX-WS to worry about. And we are at
>> the point of feature freeze. So not more new changes please...
>>
>>
>>>
>>>
>>> On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi wrote:
>>>
 Hi all,

 Are we going to merge Jaggery with AS for this release?

 If so, Nuwan are there any gray areas in doing this? Should be straight
 forward, isn't it?

 ~Isuru

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Associate Technical Lead & Member, MC, Development Technologies
>>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>>> 9629
>>> *
>>> 
>>>
>>
>>  Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>


-- 
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Samisa Abeysinghe]

Maduka, can you send an update on the progress made in merging Jag & MS
into AS?

On Wed, May 23, 2012 at 6:35 AM, Samisa Abeysinghe  wrote:

>
>
> On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara  wrote:
>
>> Yes its straight forward, in fact the API product and appfactory doing
>> it successfully right now. we need to add Jaggery and MS features to AS.
>> however when including jaggery and MS both there mite be conflicts. lets
>> try this and see.
>
>
> I would rather not put MS in this release itself.
> Even Jaggery, if it works out of the box, we can ship. Else, we have other
> priorities such as JAX-RS and JAX-WS to worry about. And we are at the
> point of feature freeze. So not more new changes please...
>
>
>>
>>
>> On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi wrote:
>>
>>> Hi all,
>>>
>>> Are we going to merge Jaggery with AS for this release?
>>>
>>> If so, Nuwan are there any gray areas in doing this? Should be straight
>>> forward, isn't it?
>>>
>>> ~Isuru
>>>
>>> --
>>> Isuru Suriarachchi
>>> Technical Lead
>>> WSO2 Inc. http://wso2.com
>>> email : is...@wso2.com
>>> blog : http://isurues.wordpress.com/
>>>
>>> lean . enterprise . middleware
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Associate Technical Lead & Member, MC, Development Technologies
>> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
>> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>> 9629
>> *
>> 
>>
>
>  Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Samisa Abeysinghe]

On Tue, May 22, 2012 at 4:23 PM, Nuwan Bandara  wrote:

> Yes its straight forward, in fact the API product and appfactory doing
> it successfully right now. we need to add Jaggery and MS features to AS.
> however when including jaggery and MS both there mite be conflicts. lets
> try this and see.


I would rather not put MS in this release itself.
Even Jaggery, if it works out of the box, we can ship. Else, we have other
priorities such as JAX-RS and JAX-WS to worry about. And we are at the
point of feature freeze. So not more new changes please...


>
>
> On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi wrote:
>
>> Hi all,
>>
>> Are we going to merge Jaggery with AS for this release?
>>
>> If so, Nuwan are there any gray areas in doing this? Should be straight
>> forward, isn't it?
>>
>> ~Isuru
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Associate Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Merging Jaggery with AS

[Nuwan Bandara]

Yes its straight forward, in fact the API product and appfactory doing
it successfully right now. we need to add Jaggery and MS features to AS.
however when including jaggery and MS both there mite be conflicts. lets
try this and see.

On Tue, May 22, 2012 at 11:06 AM, Isuru Suriarachchi  wrote:

> Hi all,
>
> Are we going to merge Jaggery with AS for this release?
>
> If so, Nuwan are there any gray areas in doing this? Should be straight
> forward, isn't it?
>
> ~Isuru
>
> --
> Isuru Suriarachchi
> Technical Lead
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Merging Jaggery with AS

[Isuru Suriarachchi]

Hi all,

Are we going to merge Jaggery with AS for this release?

If so, Nuwan are there any gray areas in doing this? Should be straight
forward, isn't it?

~Isuru

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev