Re: [Dev] Merging Jaggery with AS

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.

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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 servi

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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 b

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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 tes

Re: [Dev] Merging Jaggery with AS

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 A

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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 sam

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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 successful

Re: [Dev] Merging Jaggery with AS

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 >

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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

Re: [Dev] Merging Jaggery with AS

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 r

Re: [Dev] Merging Jaggery with AS

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.

Re: [Dev] Merging Jaggery with AS

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

[Dev] Merging Jaggery with AS

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