Re: [Dev] [Jaggery] - Is setting headers and type mandatory in jaggery post ?
yes. Or any new version, that is top on this On Thu, Feb 2, 2017 at 11:39 AM, Mahesh Chinthaka <mahe...@wso2.com> wrote: > Hi, > Thanks. It means in order to get this fix I will need to update it to > version 0.9.0.ALPHA4.wso2*v4*. > > > On Thu, Feb 2, 2017 at 10:39 AM, madhuka udantha <madhukaudan...@gmail.com > > wrote: > >> Hi, >> >> It is fixed some years ago. (on 0.9.0.ALPHA4.wso2v4). >> >> Thanks >> >> On Wed, Jan 25, 2017 at 9:10 PM, Mahesh Chinthaka <mahe...@wso2.com> >> wrote: >> >>> Hi Manu, >>> Thanks for the help. >>> I found the jira[1] related to this. And it has been fixed with the >>> commit[2]. >>> >>> [1] - https://wso2.org/jira/browse/JAGGERY-359 >>> [2] - https://github.com/wso2/jaggery/commit/a5fa00957e6686c9469 >>> 00e38ab5561c30f45f58a >>> >>> On Wed, Jan 25, 2017 at 7:54 PM, Manuranga Perera <m...@wso2.com> wrote: >>> >>>> I think it's fixed in latest. Old one doesn't have a null check [1] but >>>> the new one [2] does. Can you please back port the fixed line, build, patch >>>> and try? >>>> >>>> [1] https://github.com/wso2/jaggery/blob/0.9.0.ALPHA4.wso2v1/com >>>> ponents/hostobjects/org.jaggeryjs.hostobjects.xhr/src/main/j >>>> ava/org/jaggeryjs/hostobjects/xhr/XMLHttpRequestHostObject.java#L527 >>>> [2] https://github.com/wso2/jaggery/blob/master/components/hosto >>>> bjects/org.jaggeryjs.hostobjects.xhr/src/main/java/org/jagge >>>> ryjs/hostobjects/xhr/XMLHttpRequestHostObject.java#L561 >>>> >>>> On Wed, Jan 25, 2017 at 2:10 PM, Mahesh Chinthaka <mahe...@wso2.com> >>>> wrote: >>>> >>>>> Hi Jaggery Team, >>>>> >>>>> Actually the reason is, >>>>> the endpoint im calling doesnt return anything as response. Just '204 >>>>> No Content' >>>>> >>>>> Since the response is empty/null, it returns a null pointer exception. >>>>> IMO no content responses also should be handled by hostobject. >>>>> Is this fixed now? >>>>> Im using *org.jaggeryjs.hostobjects.xhr_0.9.0.ALPHA4_wso2v1.jar* >>>>> >>>>> On Wed, Jan 25, 2017 at 7:00 PM, Mahesh Chinthaka <mahe...@wso2.com> >>>>> wrote: >>>>> >>>>>> Even though this error occurs, http call happens succesfully. That is >>>>>> weird. >>>>>> >>>>>> On Wed, Jan 25, 2017 at 6:58 PM, Mahesh Chinthaka <mahe...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> Im using jaggery post to a http post call. >>>>>>> I dont need to set the headers, type and data as per my use case >>>>>>> when I use like below, >>>>>>> >>>>>>> var result = post(url); >>>>>>> >>>>>>> It throws following error. >>>>>>> >>>>>>> Caused by: java.lang.NullPointerException >>>>>>> >>>>>>> at org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.execu >>>>>>> teRequest(XMLHttpRequestHostObject.java:527) >>>>>>> >>>>>>> at org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.send( >>>>>>> XMLHttpRequestHostObject.java:515) >>>>>>> >>>>>>> at org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFun >>>>>>> ction_send(XMLHttpRequestHostObject.java:279) >>>>>>> >>>>>>> at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) >>>>>>> >>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >>>>>>> thodAccessorImpl.java:43) >>>>>>> >>>>>>> at java.lang.reflect.Method.invoke(Method.java:606) >>>>>>> >>>>>>> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126) >>>>>>> >>>>>>> Any idea please ? >>>>>>> >>>>>>> -- >>>>>>> *Mahesh Chinthaka Vidanagama* | Software Engineer >>>>>>> WSO2, Inc | lean. enterprise. middleware. >>>>>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>&g
Re: [Dev] [Jaggery] - Is setting headers and type mandatory in jaggery post ?
Hi, It is fixed some years ago. (on 0.9.0.ALPHA4.wso2v4). Thanks On Wed, Jan 25, 2017 at 9:10 PM, Mahesh Chinthaka <mahe...@wso2.com> wrote: > Hi Manu, > Thanks for the help. > I found the jira[1] related to this. And it has been fixed with the > commit[2]. > > [1] - https://wso2.org/jira/browse/JAGGERY-359 > [2] - https://github.com/wso2/jaggery/commit/ > a5fa00957e6686c946900e38ab5561c30f45f58a > > On Wed, Jan 25, 2017 at 7:54 PM, Manuranga Perera <m...@wso2.com> wrote: > >> I think it's fixed in latest. Old one doesn't have a null check [1] but >> the new one [2] does. Can you please back port the fixed line, build, patch >> and try? >> >> [1] https://github.com/wso2/jaggery/blob/0.9.0.ALPHA4.wso2v1/ >> components/hostobjects/org.jaggeryjs.hostobjects.xhr/src/ >> main/java/org/jaggeryjs/hostobjects/xhr/XMLHttpRequestHostOb >> ject.java#L527 >> [2] https://github.com/wso2/jaggery/blob/master/components/ >> hostobjects/org.jaggeryjs.hostobjects.xhr/src/main/java/ >> org/jaggeryjs/hostobjects/xhr/XMLHttpRequestHostObject.java#L561 >> >> On Wed, Jan 25, 2017 at 2:10 PM, Mahesh Chinthaka <mahe...@wso2.com> >> wrote: >> >>> Hi Jaggery Team, >>> >>> Actually the reason is, >>> the endpoint im calling doesnt return anything as response. Just '204 No >>> Content' >>> >>> Since the response is empty/null, it returns a null pointer exception. >>> IMO no content responses also should be handled by hostobject. >>> Is this fixed now? >>> Im using *org.jaggeryjs.hostobjects.xhr_0.9.0.ALPHA4_wso2v1.jar* >>> >>> On Wed, Jan 25, 2017 at 7:00 PM, Mahesh Chinthaka <mahe...@wso2.com> >>> wrote: >>> >>>> Even though this error occurs, http call happens succesfully. That is >>>> weird. >>>> >>>> On Wed, Jan 25, 2017 at 6:58 PM, Mahesh Chinthaka <mahe...@wso2.com> >>>> wrote: >>>> >>>>> >>>>> Hi all, >>>>> >>>>> Im using jaggery post to a http post call. >>>>> I dont need to set the headers, type and data as per my use case >>>>> when I use like below, >>>>> >>>>> var result = post(url); >>>>> >>>>> It throws following error. >>>>> >>>>> Caused by: java.lang.NullPointerException >>>>> >>>>> at org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.execu >>>>> teRequest(XMLHttpRequestHostObject.java:527) >>>>> >>>>> at org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.send( >>>>> XMLHttpRequestHostObject.java:515) >>>>> >>>>> at org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFun >>>>> ction_send(XMLHttpRequestHostObject.java:279) >>>>> >>>>> at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) >>>>> >>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >>>>> thodAccessorImpl.java:43) >>>>> >>>>> at java.lang.reflect.Method.invoke(Method.java:606) >>>>> >>>>> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126) >>>>> >>>>> Any idea please ? >>>>> >>>>> -- >>>>> *Mahesh Chinthaka Vidanagama* | Software Engineer >>>>> WSO2, Inc | lean. enterprise. middleware. >>>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>>> Mobile: +94 71 63 63 083 | Work: +94 112 145 345 >>>>> Email: mahe...@wso2.com | Web: www.wso2.com >>>>> >>>> >>>> >>>> >>>> -- >>>> *Mahesh Chinthaka Vidanagama* | Software Engineer >>>> WSO2, Inc | lean. enterprise. middleware. >>>> #20, Palm Grove, Colombo 03, Sri Lanka >>>> Mobile: +94 71 63 63 083 | Work: +94 112 145 345 >>>> Email: mahe...@wso2.com | Web: www.wso2.com >>>> >>> >>> >>> >>> -- >>> *Mahesh Chinthaka Vidanagama* | Software Engineer >>> WSO2, Inc | lean. enterprise. middleware. >>> #20, Palm Grove, Colombo 03, Sri Lanka >>> Mobile: +94 71 63 63 083 | Work: +94 112 145 345 >>> Email: mahe...@wso2.com | Web: www.wso2.com >>> >> >> >> >> -- >> With regards, >> *Manu*ranga Perera. >> >> phone : 071 7 70 20 50 >> mail : m...@wso2.com >> > > > > -- > *Mahesh Chinthaka Vidanagama* | Software Engineer > WSO2, Inc | lean. enterprise. middleware. > #20, Palm Grove, Colombo 03, Sri Lanka > Mobile: +94 71 63 63 083 | Work: +94 112 145 345 > Email: mahe...@wso2.com | Web: www.wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ML] Accuracy Measure for Anomaly Detection?
Hi,
This is good survey paper that can be found regard to Anomaly detection
[1], According to your need; it seems you will no need to go through whole
the survey papers. But few sub topics will be very useful for you. This
paper will be useful for your work.
[1] Varun Chandola, Arindam Banerjee, and Vipin Kumar. 2009. Anomaly
detection: A survey. ACM Comput. Surv. 41, 3, Article 15 (July 2009), 58
pages. DOI=10.1145/1541880.1541882
<http://www.researchgate.net/profile/Vipin_Kumar26/publication/220565847_Anomaly_detection_A_survey/links/0deec5161f0ca7302a00.pdf>
[Cited by 2458]
On Wed, Sep 16, 2015 at 3:35 PM, Ashen Weerathunga <as...@wso2.com> wrote:
> Hi all,
>
> I am currently doing the integration of anomaly detection feature for ML.
> I have a problem of choosing the best accuracy measure for the model. I can
> get the confusion matrix which consists of true positives, true negatives,
> false positives and false negatives. There are few different measures such
> as sensitivity, accuracy, F1 score, etc. So what will be the best measure
> to give as the model accuracy for anomaly detection model.
>
> [1] <https://en.wikipedia.org/wiki/Sensitivity_and_specificity>Some
> details about those measures.
>
> Terminology and derivations
> from a confusion matrix <https://en.wikipedia.org/wiki/Confusion_matrix> true
> positive (TP)eqv. with hittrue negative (TN)eqv. with correct rejectionfalse
> positive (FP)eqv. with false alarm
> <https://en.wikipedia.org/wiki/False_alarm>, Type I error
> <https://en.wikipedia.org/wiki/Type_I_error>false negative (FN)eqv. with
> miss, Type II error <https://en.wikipedia.org/wiki/Type_II_error>
> --
> sensitivity <https://en.wikipedia.org/wiki/Sensitivity_%28test%29> or
> true positive rate (TPR)eqv. with hit rate
> <https://en.wikipedia.org/wiki/Hit_rate>, recall
> <https://en.wikipedia.org/wiki/Information_retrieval#Recall>[image:
> \mathit{TPR} = \mathit{TP} / P = \mathit{TP} / (\mathit{TP}+\mathit{FN})]
> specificity <https://en.wikipedia.org/wiki/Specificity_%28tests%29> (SPC)
> or true negative rate[image: \mathit{SPC} = \mathit{TN} / N = \mathit{TN}
> / (\mathit{TN}+\mathit{FP})]precision
> <https://en.wikipedia.org/wiki/Information_retrieval#Precision> or positive
> predictive value <https://en.wikipedia.org/wiki/Positive_predictive_value>
> (PPV)[image: \mathit{PPV} = \mathit{TP} / (\mathit{TP} + \mathit{FP})]negative
> predictive value <https://en.wikipedia.org/wiki/Negative_predictive_value>
> (NPV)[image: \mathit{NPV} = \mathit{TN} / (\mathit{TN} + \mathit{FN})]
> fall-out <https://en.wikipedia.org/wiki/Information_retrieval#Fall-out>
> or false positive rate <https://en.wikipedia.org/wiki/False_positive_rate>
> (FPR)[image: \mathit{FPR} = \mathit{FP} / N = \mathit{FP} / (\mathit{FP}
> + \mathit{TN}) = 1-\mathit{SPC}]false negative rate
> <https://en.wikipedia.org/wiki/False_negative_rate> (FNR)[image:
> \mathit{FNR} = \mathit{FN} / (\mathit{TP} + \mathit{FN}) =
> 1-\mathit{TPR}]false
> discovery rate <https://en.wikipedia.org/wiki/False_discovery_rate>
> (FDR)[image:
> \mathit{FDR} = \mathit{FP} / (\mathit{TP} + \mathit{FP}) = 1 - \mathit{PPV}]
> --
> accuracy <https://en.wikipedia.org/wiki/Accuracy> (ACC)[image:
> \mathit{ACC} = (\mathit{TP} + \mathit{TN}) / (\mathit{TP} + \mathit{FP} +
> \mathit{FN} + \mathit{TN})]F1 score
> <https://en.wikipedia.org/wiki/F1_score>is the harmonic mean
> <https://en.wikipedia.org/wiki/Harmonic_mean#Harmonic_mean_of_two_numbers>
> of precision
> <https://en.wikipedia.org/wiki/Information_retrieval#Precision> and
> sensitivity <https://en.wikipedia.org/wiki/Sensitivity_%28test%29>[image:
> \mathit{F1} = 2 \mathit{TP} / (2 \mathit{TP} + \mathit{FP} +
> \mathit{FN})]Matthews
> correlation coefficient
> <https://en.wikipedia.org/wiki/Matthews_correlation_coefficient> (MCC)[image:
> \frac{ \mathit{TP} \times \mathit{TN} - \mathit{FP} \times \mathit{FN} }
> {\sqrt{ (\mathit{TP}+\mathit{FP}) ( \mathit{TP} + \mathit{FN} ) (
> \mathit{TN} + \mathit{FP} ) ( \mathit{TN} + \mathit{FN} ) }
> }]Informedness[image:
> \mathit{TPR} + \mathit{SPC} - 1]Markedness
> <https://en.wikipedia.org/wiki/Markedness>[image: \mathit{PPV} +
> \mathit{NPV} - 1]
>
> *Sources: Fawcett (2006) and Powers (2011).*[1]
> <https://en.wikipedia.org/wiki/Sensitivity_and_specificity#cite_note-Fawcett2006-1>
> [2]
> <https://en.wikipedia.org/wiki/Sensitivity_and_specificity#cite_note-Powers2011-2>
>
> Thanks and Regards,
> Ashen
> --
> *Ashen Weerathunga*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.ent
Re: [Dev] [Jaggery] How to convert String value of true/false to Boolean in Jaggery?
On Tue, Mar 10, 2015 at 1:44 PM, Abimaran Kugathasan abima...@wso2.com
wrote:
On Tue, Mar 10, 2015 at 1:14 PM, Tanya Madurapperuma ta...@wso2.com
wrote:
Hi,
I just tried the following snippet in the try-it of jaggery page and it
gives me the expected output.
var test = true;
var bool_convert = Boolean(test);
print(bool_convert); //true
-
var test = false;
var bool_convert = Boolean(test);
print(bool_convert); //true
This should print false, right? Why this is printing true?
Boolean context in JS/Jaggery[2]
undefined, null and becomes false, any other - true
[1] http://www.w3schools.com/js/js_type_conversion.asp
[2] http://javascript.info/tutorial/object-conversion#boolean-context
---
var test = ;
var bool_convert = Boolean(test);
print(bool_convert); //false
Thanks,
Tanya
On Tue, Mar 10, 2015 at 12:40 PM, Abimaran Kugathasan abima...@wso2.com
wrote:
On Tue, Mar 10, 2015 at 11:45 AM, Tanya Madurapperuma ta...@wso2.com
wrote:
On Tue, Mar 10, 2015 at 11:29 AM, Abimaran Kugathasan
abima...@wso2.com wrote:
Thanks Himasha,
In Jaggery, follwing is possible to do and works fine.
var isLogoutRequest = false;
if(!Boolean(isLogoutRequest)) {
//
}
I was thinking, why can't we have this type of conversion for String
value of true/false in Jagger?
That is because as same as in javascript, as long as your
isLogoutRequest is not an empty string it will evaluate to true.
Nope, It doesn't work in Jaggey. I tried
Boolean(isPassiveAuthRequired), but it returns false even for value
'true'. That's my worry.
Why following doesn't work
var isPassiveAuthRequired = request.getParameter(passiveAuthRequired);
// value is String
if(Boolean(isPassiveAuthRequired)) {
//
}
while following works?
var isLogoutRequest = false; // here value is boolean
if(!Boolean(isLogoutRequest)) {
//
}
How this Boolean() works in Jaggery?
On Tue, Mar 10, 2015 at 11:19 AM, Himasha Guruge himas...@wso2.com
wrote:
Hi Abimaran,
You could check [1] for different options. Check the answer where
they are prioritized based on performance.
[1]
http://stackoverflow.com/questions/263965/how-can-i-convert-a-string-to-boolean-in-javascript/28588344#28588344
Thanks,
Himasha
On Tue, Mar 10, 2015 at 11:03 AM, Abimaran Kugathasan
abima...@wso2.com wrote:
Hi,
I have a query string parameter with value true or false. I need to
convert this value to corresponding boolean value for some conditional
checking.
Currently, I'm using string comparision with == to evaluate.
var isPassiveAuthRequired
= request.getParameter(passiveAuthRequired);
if('true' == isPassiveAuthRequired) {
//
}
This doesn't look a proper way. I tried
Boolean(isPassiveAuthRequired), but it returns false even for value
'true'.
Anybody knows a better way?
--
Thanks
Abimaran Kugathasan
Software Engineer | WSO2 Inc
Data APIs Technologies Team
Mobile : +94 773922820
http://stackoverflow.com/users/515034
http://lk.linkedin.com/in/abimaran
http://www.lkabimaran.blogspot.com/ https://github.com/abimaran
https://twitter.com/abimaran
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
--
Thanks
Abimaran Kugathasan
Software Engineer | WSO2 Inc
Data APIs Technologies Team
Mobile : +94 773922820
http://stackoverflow.com/users/515034
http://lk.linkedin.com/in/abimaran
http://www.lkabimaran.blogspot.com/ https://github.com/abimaran
https://twitter.com/abimaran
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Tanya Madurapperuma
Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
--
Thanks
Abimaran Kugathasan
Software Engineer | WSO2 Inc
Data APIs Technologies Team
Mobile : +94 773922820
http://stackoverflow.com/users/515034
http://lk.linkedin.com/in/abimaran
http://www.lkabimaran.blogspot.com/ https://github.com/abimaran
https://twitter.com/abimaran
--
Tanya Madurapperuma
Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
--
Thanks
Abimaran Kugathasan
Software Engineer | WSO2 Inc
Data APIs Technologies Team
Mobile : +94 773922820
http://stackoverflow.com/users/515034
http://lk.linkedin.com/in/abimaran
http://www.lkabimaran.blogspot.com/ https://github.com/abimaran
https://twitter.com/abimaran
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org
Re: [Dev] Jaggery websocket sample not working
Hi, Try this https://github.com/wso2/jaggery/tree/master/apps/sample/chatroom On Thu, Oct 9, 2014 at 12:02 PM, Sam Sivayogam s...@wso2.com wrote: HI All, I'm trying to run the following sample using wso2as 5.2.1 http://jaggeryjs.org/documentation.jag?api=webSocket But it gives the following error message *ReferenceError: webSocket is not defined.* Thank You. -- *Sam Sivayogam* Software Engineer http://www.wso2.com/ *Mobile* : +94 772 906 439 *Office* : +94 112 145 345 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] jaggery file upload
Hi,
you can do it. absolute path
var absolute = function (path) {
var systemProcess = require('process');
var parent = 'file:///' +
(systemProcess.getProperty('jaggery.home') ||
systemProcess.getProperty('carbon.home')).replace(/[\\]/g,
'/').replace(/^[\/]/g, '');
return parent + MODULE_PATH + path;
};
[1]
https://github.com/Madhuka/sugarcane/blob/master/core/sugarcane/scripts/engine/test.js
On Tue, Oct 7, 2014 at 9:37 AM, Lochana Menikarachchi loch...@wso2.com
wrote:
--
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] [javascript] Generating UUID in javascript
Hi, If you are jaggery Dev, you have jaggery module[1] for it. [1] https://github.com/wso2/jaggery-extensions/tree/master/uuid On Fri, Aug 8, 2014 at 10:25 AM, Rushmin Fernando rush...@wso2.com wrote: whats our standard way of $subject ? -- *Rushmin Fernando* *Technical Lead* WSO2 Inc. http://wso2.com/ - Lean . Enterprise . Middleware email : rush...@wso2.com mobile : +94772310855 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M 1.7.1] - The publisher URL/API Console does not work out of the box if you set a port offset
Hi,
You can used 'loadConfig()' to load carbon config file and read 'offset'
value.
This can be helpful for the $subject
var conf = carbon.server.loadConfig(config file)
On Thu, Jul 24, 2014 at 3:21 PM, Evanthika Amarasiri evanth...@wso2.com
wrote:
Hi All,
With API-M 1.7.1, we noticed that if we set a port offset, we need to
change the site.json files of the publisher jaggery app. If you don't
change these files, when you access the publisher URL, you are redirected
back to https://{default_host}:{default_port}/publisher page. i.e.:-
https://localhost:9443/publisher.
So every time you set a port offset to your server, a user will have to
change the site.json file manually to access publisher URL.
My concern is, why are we introducing additional configuration changes
like these? If we introduce changes, we need to make sure that they work
out of the box, without a person having to change any files manually.
Also, if you set a port offset, API console (Swagger) does not work out of
the box. You need to change the port you give in
*Access-Control-Allow-Origin* parameter.
Regards,
Evanthika Amarasiri
Senior Technical Lead - Quality Assurance
Mobile: +94773125935
wso2.com Lean Enterprise Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M 1.7.1] - The publisher URL/API Console does not work out of the box if you set a port offset
Hi,
yes, offset can be read from system property (/carbon utility services)
but depending on code implementation and use case we need have think those
both options.
If you reading from system property then 'wso2server.sh -DportOffset=1'
will work.
In WSO2 UES we also had some type of such issues some times back.
On Fri, Jul 25, 2014 at 3:32 AM, Nuwan Dias nuw...@wso2.com wrote:
I presume this must have got broken due to the fix introduced for [1].
@Udara should be able to shed some light on this.
@Maduka, I think we have to get the offset from the system property
(portOffset). AFAIK the portOffset is read through the portOffset system
property.
[1] - https://wso2.org/jira/browse/APIMANAGER-2482
Thanks,
NuwanD.
On Fri, Jul 25, 2014 at 1:10 AM, Sumedha Rubasinghe sume...@wso2.com
wrote:
But how did this got broken?
Is this due to an update from Jaggery? This is a fundamental flaw we
are trying to do a patch release.
Madhuka - welcome back ;-) ...
On Thu, Jul 24, 2014 at 4:33 AM, madhuka udantha
madhukaudan...@gmail.com wrote:
Hi,
You can used 'loadConfig()' to load carbon config file and read 'offset'
value.
This can be helpful for the $subject
var conf = carbon.server.loadConfig(config file)
On Thu, Jul 24, 2014 at 3:21 PM, Evanthika Amarasiri evanth...@wso2.com
wrote:
Hi All,
With API-M 1.7.1, we noticed that if we set a port offset, we need to
change the site.json files of the publisher jaggery app. If you don't
change these files, when you access the publisher URL, you are redirected
back to https://{default_host}:{default_port}/publisher page. i.e.:-
https://localhost:9443/publisher.
So every time you set a port offset to your server, a user will have to
change the site.json file manually to access publisher URL.
My concern is, why are we introducing additional configuration changes
like these? If we introduce changes, we need to make sure that they work
out of the box, without a person having to change any files manually.
Also, if you set a port offset, API console (Swagger) does not work out
of the box. You need to change the port you give in
*Access-Control-Allow-Origin* parameter.
Regards,
Evanthika Amarasiri
Senior Technical Lead - Quality Assurance
Mobile: +94773125935
wso2.com Lean Enterprise Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com
--
/sumedha
m: +94 773017743
b : bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Nuwan Dias
Associate Tech Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
--
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Read property file using Jaggery
Hi, You can try below way, here is sample code[1]. There are some other way for $subject also. var conf = carbon.server.loadConfig(config file) [1] https://github.com/wso2/ues/blob/master/modules/apps/portal/app.js On Fri, Jun 6, 2014 at 12:51 PM, Dinesh Bandara dine...@wso2.com wrote: carbon -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery websocket tryit sample not working
Hi, Anuruddha Here[1] is sample code and explain web socket implementation in jaggery[1] as well. Here[2] is jaggery master sample for web socket Thanks [1] http://madhukaudantha.blogspot.com/2014/02/websocket-with-jaggery-jaggeryjs-sample.html [2] https://github.com/wso2/jaggery/tree/master/apps/sample/chatroom On Thu, Jun 5, 2014 at 10:13 AM, Udara Rathnayake uda...@wso2.com wrote: Hi, Yes, We are in the process of updating the Jaggey documentation. Basically we have to remove try-it feature from there(Not only this but identified some other places also). As you can see you have to run server related script and client script separately here. On Thu, Jun 5, 2014 at 10:05 AM, Anuruddha Premalal anurud...@wso2.com wrote: Hi, WebSocket sample in jaggery documentation http://jaggeryjs.org/documentation.jag?api=webSocket doesn't work. It says webSocket is not defined. at line #4 Regards, -- *Anuruddha Premalal* Software Eng. | WSO2 Inc. Mobile : +94710461070 Web site : www.regilandvalley.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Introducing JSR-223 into Jaggery along with Nashorn Support
via http://localhost:9763/demo1
2. https://github.com/ruchiraw/jaggery/tree/master/apps/demo2
- this shows about module versioning and nested modules
- can be accessed via http://localhost:9763/demo2
3. https://github.com/ruchiraw/jaggery/tree/master/apps/demo3
- this shows how you can implement *.jag support on top of
app.serve()
- can be accessed via http://localhost:9763/demo3/index.jag
- you can click on See Docs link too
- at the moment, this doesn't support all the APIs of the current
version, but this is a PoC for that.
4. https://github.com/ruchiraw/jaggery/tree/master/apps/demo4
1. this shows the usage of express like routing module developed by
SameeraM[3]
2. can be accessed via http://localhost:9763/demo4/users/1 or
http://localhost:9763/demo4/apps/1
5. https://github.com/ruchiraw/jaggery/tree/master/apps/demo5
- by copying this into the webapps directory of an apache tomcat
server, you can try out how Jaggery can work on tomcat
- this app is exactly like aboute demo4, but this time, it runs on
tomcat.
- can be accessed via http://localhost:8080/demo5/users/1 or
http://localhost:8080/demo5/apps/1
When, above demos are run, you will be able to see module resolution log
messages at the moment. Hence, if you are doing any kind of load testing
etc.,
- If it is Jaggery server, please make development as false in
jaggery.conf
- If it is on tomcat, set jaggery.development as false in web.xml.
This will enable caching for loaded modules, pooling for script engines
and async servlets. Further, you can fine tune the performances using the
jaggery.conf[4] parameters on Jaggery and web.xml[5] parameters on tomcat.
I have done only a small load test to test the server concurrency. Will do
a proper benchmarking round after improving further.
*Command Line Tool*
- In order to use the cmd tool, you need to first set the environment
variable JAGGERY_HOME pointing to your unzipped Jaggery distribution
- export
JAGGERY_HOME=/Users/ruchira/binaries/jaggery/1.0.0/m0/jaggery-0.9.0-SNAPSHOT
- Then download *.jar at [8]
- Execute the downloaded *.jar using
- java -jar
org.jaggeryjs.cmd-0.9.0-SNAPSHOT-jar-with-dependencies.jar
- You can require the modules
- relative to your working directory. e.g. require('./foo') if it
the module foo is at cwd/foo.js or cwd/foo/
- If you have a jaggery-modules directory working direcotry as
cwd/jaggery-modules, then you can require any module exists there
using
require('foo') etc.
Current implementation is just the core to get started and demonstrate
what I have mentioned above. We have plans along the line to write
a comprehensive Jaggery Package Manager, a maven plugin to execute unit
tests etc.
[1] https://github.com/ruchiraw/jaggery
[2]
https://github.com/ruchiraw/sandbox/raw/master/jaggery/1.0.0/m0/jaggery-0.9.0-SNAPSHOT.zip
[3] https://github.com/splinter/jaggery-pipe
[4]
https://github.com/ruchiraw/jaggery/blob/4560a303f809d532ad041125c1a29ecc2eb9df55/apps/tomgery/jaggery.conf
[5]
https://github.com/ruchiraw/jaggery/blob/master/apps/demo5/WEB-INF/web.xml
[6] https://github.com/vladimirvivien/clamshell-cli
[7]
https://wiki.openjdk.java.net/display/Nashorn/Using+Rhino+JSR-223+engine+with+JDK8
[8]
https://github.com/ruchiraw/sandbox/raw/master/jaggery/1.0.0/m0/org.jaggeryjs.cmd-0.9.0-SNAPSHOT-jar-with-dependencies.jar
--
*Ruchira Wageesha**Associate Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com*
*email: ruch...@wso2.com ruch...@wso2.com, blog:
ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com,
mobile: +94 77 5493444 %2B94%2077%205493444*
___
Architecture mailing list
architect...@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Introducing JSR-223 into Jaggery along with Nashorn Support
On Mon, Jun 2, 2014 at 12:46 PM, Ruchira Wageesha ruch...@wso2.com wrote: Yes, it is the same, except application object itself is replaced by a module. +1 On Mon, Jun 2, 2014 at 12:33 PM, madhuka udantha madhukaudan...@gmail.com wrote: Hi, Ruchira 'app.server()' is similar for existing 'application.serve()' in jaggery , isn't it regard functionality? Here[1] is sample for application.serve(). [1] https://github.com/Madhuka/MadhukaBlogRepo/tree/master/SampleApps/JaggeryApps/service/ On Sun, Jun 1, 2014 at 12:58 PM, Ruchira Wageesha ruch...@wso2.com wrote: Hi All, We have started the integration of JSR-223 i.e. javax.script API with Jaggery. Sorry for the lengthy mail, but this is just to share the status and get your all kinds of feedbacks. A Jaggery fork and a distribution with the following improvements can be found at [1] and [2] respectively. In case you want to try this out before sharing your feedbacks, you can download a Jaggery distribution with all the above implementations at [2]. It consists of 5 demo apps. (At the moment, this has been tested only on linux/mac and you will have to run this either on JDK 7 or 8. As JDK 6 supports only an older version of ECMAScript, this pack will not work. But in order to get the support even on JDK 6, we will have to pack the JSR-223 rhino implementation with a rhino 1.7 version, following a similar way described at [7]) With the integration with JSR-223, we had to and thought to do a few changes and improvements to Jaggery which will be detailed below. BUT, please note that, every existing Jaggery application will work as it is, independent of those improvements. i.e. With a version field in jaggery.conf, we internally decide, whether to go with the newer version. *Key Decisions* 1. JSR-223 support - With this, Jaggery will use Nashorn from JDK8 onwards and will fallback to JDK's embeded Rhino version with JDK7 or below. 2. Saying good bye for hostobjects - Hostobjects are a concept of Rhino and it was needed to follow certain conventions when you write your hostobjects. With JSR-223, we cannot have it anymore. But, instead of that, you can refactor only the hostobject *.java class into *.js file which contains the Java code and plug it. 3. Dropping E4X support - E4X was an extension to ECMAScripts and usage of E4X is being deprecated in many places. Also, AFAIK, there is no support for E4X in nashorn. This will be replaced by a Axiom/DOM like modules. i.e. without altering the spec. 4. Except the bare minimal, everything else is separated into commonjs modules - This will give much more flexibility and extendability for Jaggery. i.e. In order to extend Jaggery, developers don't need to be Java developers anymore 5. Introduction of app.server() method - In the current version, routing mechanism has been implemented by Jaggery core and there is no way to intercept that. This makes it harder to write cooler modules for Jaggery, such as express, connect for node. Using app.server(), Jaggery core delegates request serving to a single callback. But, via that callback, users can call their own routing modules and do whatever they want. You can even implement the current *.jag model, on top of app.server()[refer demo3]. Also, we have written an express like routing framework which can be used to define REST APIs very easily through Jaggery. This will be a good alternative for JAX-RS developers too. 6. Servlet 3.0 Async support - Another key feature is utilizing Async servlet support. So, concurrency will not be restricted by the available thread count anymore. 7. CommonJS module system - At the moment, Jaggery has its own module system. Instead of that, we though of going ahead with commonjs module specification. With this, commonjs compliant modules will be able to use within Jaggery. i.e. Any node module which doesn't depend on node core APIs, can be used in Jaggery as well, without doing any change. 8. Module versioning and nested module support - Another improvement is, adding module versioning support for Jaggery modules. i.e. x app(or module) can use y1 version of y module, while another z app(or module) can use y2 without conflicting each other. For this too, we are also using package.json as per the commonjs specification 9. Support for deploying directly on top of tomcat - With the above Jaggery core minimisations, a Jaggery app can be even deployed on top of tomcat, subjecting to a WEB-INF directory which contains jaggery core jars and web.xml 10. Improved command line tool - clamshell-cli based command line tool with history support etc
Re: [Dev] About Jaggery Apps in Greg 5
715 440 607 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com -- Thanks /subash *Subash Chaturanga* Senior Software Engineer :Platform TG; WSO2 Inc. http://wso2.com email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sugarcane release
Hi, Dilshan $subjet[1] is the jagery-test. Get code from my local repo[1] to jaggery-extensions[2] and rename it to 'jaggery-test'. Rename the feature name in EMM and get jaggery team help to build it from bamboo or jenkins, then it will be solved. Thanks [1] https://github.com/Madhuka/sugarcane [2] https://github.com/wso2/jaggery-extensions On Mon, May 19, 2014 at 3:34 PM, Dilshan Edirisuriya dils...@wso2.comwrote: Hi, I see sugarcane is added as a feature in EMM. It simply breaks the build unless you specifically build the feature from the source repo. From where does it come from? Doesn;t it have to reside in WSO2 feature list? Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Failure to find sugarcane:sugarcane.feature:zip:1.0.0-SNAPSHOT in http://dist.wso2.org/maven2/ was cached in the loca l repository, resolution will not be reattempted until the update interval of wso2-maven2-repository has elapsed or updates are forced Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=sugarcane -DartifactId=sugarcane.feature -Dversion=1.0.0-SNAPSHOT -Dpackaging=zip -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=sugarcane -DartifactId=sugarcane.feature -Dversion=1.0.0-SNAPSHOT -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] sugarcane:sugarcane.feature:zip:1.0.0-SNAPSHOT Regards, Dilshan On Mon, May 12, 2014 at 9:37 PM, madhuka udantha madhukaudan...@gmail.com wrote: HI, chan you can get repo in my local git that you was referring. simple just rename it as you adding wso2 repo. On Mon, May 12, 2014 at 8:46 PM, Chan duli...@wso2.com wrote: Where is jaggery-test? Can't seem to find it.. On Mon, May 12, 2014 at 8:41 PM, madhuka udantha madhukaudan...@gmail.com wrote: Hi, It is 'jaggery-test' and you can added it jaggery-extension. If we have any other repo/org is ready for jaggery modules, you can add it there and get release. [1] https://github.com/wso2/jaggery-extensions On Mon, May 12, 2014 at 6:24 PM, Sagara Gunathunga sag...@wso2.comwrote: On Mon, May 12, 2014 at 6:14 PM, Chan duli...@wso2.com wrote: Hi folks, We are using sugarcane[1] testing framework for unit tests. It's currently not released. Can we please get it released and available in nexus repo. Guys, What is sugarcane ? what happen to JaggeryTest module that we agreed to develop. Cheers~ [1] - https://github.com/Madhuka/sugarcane I can't find any licence on above repo also not sure how we (WSO2) can release a product hosted on personal repo. Thanks ! -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dilshan Edirisuriya Senior Software Engineer - WSO2 Mob: + 94 777878905 http://wso2.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sugarcane release
On Mon, May 19, 2014 at 4:30 PM, Dilshan Edirisuriya dils...@wso2.comwrote: Hi Madhuka, Thanks. I think we have to add it to platform features as well as nexus repo? +1, for to get nexus repo A person trying to build the EMM code has no clue where it is coming from. Regards, Dilshan On Mon, May 19, 2014 at 4:26 PM, madhuka udantha madhukaudan...@gmail.com wrote: Hi, Dilshan $subjet[1] is the jagery-test. Get code from my local repo[1] to jaggery-extensions[2] and rename it to 'jaggery-test'. Rename the feature name in EMM and get jaggery team help to build it from bamboo or jenkins, then it will be solved. Thanks [1] https://github.com/Madhuka/sugarcane [2] https://github.com/wso2/jaggery-extensions On Mon, May 19, 2014 at 3:34 PM, Dilshan Edirisuriya dils...@wso2.comwrote: Hi, I see sugarcane is added as a feature in EMM. It simply breaks the build unless you specifically build the feature from the source repo. From where does it come from? Doesn;t it have to reside in WSO2 feature list? Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Failure to find sugarcane:sugarcane.feature:zip:1.0.0-SNAPSHOT in http://dist.wso2.org/maven2/ was cached in the loca l repository, resolution will not be reattempted until the update interval of wso2-maven2-repository has elapsed or updates are forced Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=sugarcane -DartifactId=sugarcane.feature -Dversion=1.0.0-SNAPSHOT -Dpackaging=zip -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=sugarcane -DartifactId=sugarcane.feature -Dversion=1.0.0-SNAPSHOT -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] sugarcane:sugarcane.feature:zip:1.0.0-SNAPSHOT Regards, Dilshan On Mon, May 12, 2014 at 9:37 PM, madhuka udantha madhukaudan...@gmail.com wrote: HI, chan you can get repo in my local git that you was referring. simple just rename it as you adding wso2 repo. On Mon, May 12, 2014 at 8:46 PM, Chan duli...@wso2.com wrote: Where is jaggery-test? Can't seem to find it.. On Mon, May 12, 2014 at 8:41 PM, madhuka udantha madhukaudan...@gmail.com wrote: Hi, It is 'jaggery-test' and you can added it jaggery-extension. If we have any other repo/org is ready for jaggery modules, you can add it there and get release. [1] https://github.com/wso2/jaggery-extensions On Mon, May 12, 2014 at 6:24 PM, Sagara Gunathunga sag...@wso2.comwrote: On Mon, May 12, 2014 at 6:14 PM, Chan duli...@wso2.com wrote: Hi folks, We are using sugarcane[1] testing framework for unit tests. It's currently not released. Can we please get it released and available in nexus repo. Guys, What is sugarcane ? what happen to JaggeryTest module that we agreed to develop. Cheers~ [1] - https://github.com/Madhuka/sugarcane I can't find any licence on above repo also not sure how we (WSO2) can release a product hosted on personal repo. Thanks ! -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dilshan Edirisuriya Senior Software Engineer - WSO2 Mob: + 94 777878905 http://wso2.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman
Re: [Dev] Sugarcane release
Hi, It is 'jaggery-test' and you can added it jaggery-extension. If we have any other repo/org is ready for jaggery modules, you can add it there and get release. [1] https://github.com/wso2/jaggery-extensions On Mon, May 12, 2014 at 6:24 PM, Sagara Gunathunga sag...@wso2.com wrote: On Mon, May 12, 2014 at 6:14 PM, Chan duli...@wso2.com wrote: Hi folks, We are using sugarcane[1] testing framework for unit tests. It's currently not released. Can we please get it released and available in nexus repo. Guys, What is sugarcane ? what happen to JaggeryTest module that we agreed to develop. Cheers~ [1] - https://github.com/Madhuka/sugarcane I can't find any licence on above repo also not sure how we (WSO2) can release a product hosted on personal repo. Thanks ! -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sugarcane release
HI, chan you can get repo in my local git that you was referring. simple just rename it as you adding wso2 repo. On Mon, May 12, 2014 at 8:46 PM, Chan duli...@wso2.com wrote: Where is jaggery-test? Can't seem to find it.. On Mon, May 12, 2014 at 8:41 PM, madhuka udantha madhukaudan...@gmail.com wrote: Hi, It is 'jaggery-test' and you can added it jaggery-extension. If we have any other repo/org is ready for jaggery modules, you can add it there and get release. [1] https://github.com/wso2/jaggery-extensions On Mon, May 12, 2014 at 6:24 PM, Sagara Gunathunga sag...@wso2.comwrote: On Mon, May 12, 2014 at 6:14 PM, Chan duli...@wso2.com wrote: Hi folks, We are using sugarcane[1] testing framework for unit tests. It's currently not released. Can we please get it released and available in nexus repo. Guys, What is sugarcane ? what happen to JaggeryTest module that we agreed to develop. Cheers~ [1] - https://github.com/Madhuka/sugarcane I can't find any licence on above repo also not sure how we (WSO2) can release a product hosted on personal repo. Thanks ! -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] OSGI Issue when trying to use Script Mediator in APIM
Hi, This[1] can be helpful for such scenario, And you issue encounter is correct, *You can check some AS releases, where it also occurred and fixed as we added jaggery and mashup to AS.* [1] http://madhukaudantha.blogspot.com/2014/02/writing-hostobject-for-jaggery.html On Fri, May 9, 2014 at 8:53 AM, Ruchira Wageesha ruch...@wso2.com wrote: Please meet me in the office. Will be able to help you. /Ruchira On Fri, May 9, 2014 at 12:02 AM, Ruwan Yatawara ruw...@wso2.com wrote: Hi All, We ran in to $subject when trying to use the script mediator in API Manager. When trying to use script mediator in AM APIs the following error is thrown. *Caused by: java.lang.NoClassDefFoundError: com/sun/phobos/script/javascript/RhinoScriptEngineFactory* * at org.apache.synapse.mediators.bsf.ScriptMediator.initScriptEngine(ScriptMediator.java:472)* * at org.apache.synapse.mediators.bsf.ScriptMediator.initInlineScript(ScriptMediator.java:338)* * at org.apache.synapse.mediators.bsf.ScriptMediator.init(ScriptMediator.java:148)* To the best of my understanding, following is whats happening here. The script mediator depends on the bsf-all_3.0.0.wso2v2, which needs org.mozilla.javascript; version=1.6.0 or above to function. Jaggery is built to support org.mozilla.javascript; version=1.7.0 and above, and the API Manager host object, depends on both jaggery and synapse to function. When all of this comes together, we believe synapse has a problem with wiring the correct bundles (package usage conflict), leading to above quoted error. To overcome this, there are two options, and both seem to have considerable consequences a) Update the BSF jar to use org.mozilla.javascript; version=1.7.0 b) Update Synapse, restricting it to use org.mozilla.javascript; version=1.6.0, only and APIM host objects to use 1.7.0 specifically. Since Option A might require changes to ESB script mediator, as API changes may be in effect, we went ahead with option (b). This leads to errors in the API Manager Host objects and the bundle goes in to INSTALLED state. The following error is thrown, at startup and there are also errors when trying to invoke the API. *[2014-05-08 23:56:16,246] ERROR - ModuleManager Error while adding HostObject : APIStore org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject* *java.lang.ClassNotFoundException: org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject* * at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)* * at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)* Has anyone encountered such an issue before? How should we go about fixing this? Your thoughts/ideas/suggestions are welcome. Thanks and Regards, Ruwan Yatawara WSO2 Inc. email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://thoughts.ruwan-ace.com/ www: :http://wso2.com -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES][Jaggery] Getting sender parameters for jaggery file from Axis2.xml
Hi,
Yap, there are few way. one is you can used carbon modules
Here is sample code for you.
%
var carbon = require('carbon');
var conf1 = carbon.server.loadConfig('axis2/axis2.xml');
print(conf1.*::['clustering'].*::['members']);
%
Thanks
On Wed, Apr 30, 2014 at 10:32 AM, Chamila Wijayarathna cham...@wso2.comwrote:
Hi all,
I am using email jaggery module for sending email notification in
Enterprise Store. I have added following code at
/publisher/apis/v1/lifecycle_api_router.jag file.
*var email = require('email');*
*var sender = new email.Sender(smtp.gmail.com http://smtp.gmail.com,
587, wso2demomail, mailpassword, tls);*
Can I get the email sender properties for here from
repository/conf/axis2/axis2.xml without hardcoding these values here?
Thank You!
--
*Chamila Wijayarathna*
Engineering Intern,
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please create a new Jaggery version with attached fix
Hi, Dunith You can go with 0.9.0.ALPHA4.wso2v5[1], 0.9.0.ALPHA4.wso2v5 is for BAM 2.4.1 [1] https://github.com/wso2/jaggery/tree/0.9.0.ALPHA4.wso2v5 On Sat, Apr 26, 2014 at 1:43 AM, Dunith Dhanushka dun...@wso2.com wrote: Hi Madhuka, While fixing BAM-1565 https://wso2.org/jira/browse/BAM-1565 and BAM-1566https://wso2.org/jira/browse/BAM-1566we figured out Jaggery core was still using CarbonContext.getCurrentContext().getTenantId(). Because of this, BAM toolbox deployment for tenant always got a stackoverflow. A fix for this is attached here with. Please make a new Jaggery release for the upcoming BAM 2.4.1 release. Note that Jaggery version we used was 0.9.0.ALPHA4.wso2v4. Regards, Dunith Dhanushka, Senior Software Engineer - BAM, WSO2 Inc, Mobile - +94 71 8615744 Blog - dunithd.wordpress.com http://blog.dunith.com Twitter - @dunithd http://twitter.com/dunithd -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Support for SessionListener in Jaggery.
On Fri, Apr 25, 2014 at 6:57 PM, Ramith Jayasinghe ram...@wso2.com wrote:
BTW, this means we have to upgrade our jaggery version to
0.9.0.ALPHA4.wso2v4
Since you used 0.9.0.ALPHA4.wso2v1.
Moving into 0.9.0.ALPHA4.wso2v4 from 0.9.0.ALPHA4.wso2v1 is not much issue
in my idea, there is no much changes.
(Jaggery module level few). Since both version used same carbon version.,
(AFIK there is no API changes)
On Fri, Apr 25, 2014 at 6:35 PM, Ruchira Wageesha ruch...@wso2.comwrote:
Hi Ramith,
In Jaggery master(from 0.9.0.ALPHA4.wso2v4 onwards), we have added that
support. You can specific scripts to be executed for session create/destroy
events. i.e. In jaggery.conf you can have the following. Within the
scripts, you can also access the session being created/destroyed via
session global.
{
sessionCreatedListeners: [created.js],
sessionDestroyedListeners: [destroyed.js]
}
/Ruchira
On Fri, Apr 25, 2014 at 6:20 PM, Ramith Jayasinghe ram...@wso2.comwrote:
in Appfactory we have a requirement for intercept http sessions being
created and invalidated. in a typical web application this could be done by
having following settings in web.xml:
web-app ...
listener
listener-classorg.wso2.carbon.sample.MyHttpSessionListener/listener-class
/listener/web-app
Could we have something similar in jaggery too?
currently having following in jaggery.conf doesn't seems to do anything:
listener:
{
listener-class:org.wso2.carbon.sample.MyHttpSessionListener
}
Thoughts Please?
P.S.: we are using Jaggery v 0.9.0.ALPHA4.wso2v1
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
--
*Ruchira Wageesha**Associate Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com*
*email: ruch...@wso2.com ruch...@wso2.com, blog:
ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com,
mobile: +94 77 5493444 %2B94%2077%205493444*
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 776715671
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery shifting to test-automation-framework 4.3.1
Hi, I found the cause for the failure. It is about jaggery file structure By debugging automation.engine [CodeCoverageUtils (line 136)] Where try to access \plugins. jaggery file structure bit different[2] to other wso2 products[1]. Jaggery have extra directory called carbon and it is missing in CodeCoverageUtils.java. So we will need some fix for this where we can pass it from configuration or looking on server name or type to define file/path structure. [1] F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT\repository\components\plugins [2] F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT\ *carbon*\repository\components\plugins On Thu, Apr 24, 2014 at 1:08 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Dharshana, The startup script naming problems if fixed already - [1]. So the problems is not with startup script name. [1]https://wso2.org/jira/browse/TA-825 Thanks, Krishantha. On Thu, Apr 24, 2014 at 11:43 AM, Dharshana Warusavitharana dharsha...@wso2.com wrote: Hi Madhuka, Please refine the instrumentation jars listed in intrumentation.txt. Seems like the jar files which are listed to be instrument were not present in the pack. Id the startup script is different that will be the next point. For that you can have your own server startup module and add it as an extensible module to the framework. You can refer [1] to write a extensible module for the framework. [1]. https://docs.wso2.org/display/TA430/Pluggable+Module+Executors Thank You, Dharshana. On Thu, Apr 24, 2014 at 11:10 AM, Madhuka Udantha madh...@wso2.comwrote: Getting error start carbon server from test-automation-framework Since jaggery have different name for server starting script. was it the issue? or is there any config need to added? I have updated below repo and built. - carbon-platform-integration - carbon-platform-integration-utils [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ org.jaggeryjs.integration.tests --- [INFO] Surefire report directory: F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\surefire-reports --- T E S T S --- Running TestSuite Extracting carbon zip file.. Carbon Home - F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp1398317632682\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT Instrumentation of jar files in progress ... Fail to start carbon server java.lang.NullPointerException at org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.instrumentSelectedFiles(CodeCoverageUtils.java:140) at org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.instrument(CodeCoverageUtils.java:108) at org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerManager.startServerUsingCarbonHome(CarbonServerManager.java:71) at org.wso2.carbon.integration.common.extensions.carbonserver.TestServerManager.startServer(TestServerManager.java:102) at org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension.onExecutionStart(CarbonServerExtension.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.executeExtensible(TestNGExtensionExecutor.java:73) at org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionStart(TestExecutionListener.java:48) at org.testng.TestNG.runExecutionListeners(TestNG.java:1032) at org.testng.TestNG.run(TestNG.java:983) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165
Re: [Dev] Jaggery shifting to test-automation-framework 4.3.1
On Thu, Apr 24, 2014 at 2:37 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Any particular reason for making Jaggery directory structure differ from normal carbon directory structure? decision can be found in here[1]. Simple change is that jaggery root have dir called 'carbon' there you can find normal wso2 product directory structure We can make it configurable, however we need to introduce this configuration to all product test modules. Another alternative would be to change jar instrumentation logic to find plugins directory first, and construct the path. We will fix this and let you know. Please raise a TA JIRA for this. done, TA-827[2] Thanks [1] [Architecture] Jaggery distribution structure [2] https://wso2.org/jira/browse/TA-827 Thanks, Krishantha. On Thu, Apr 24, 2014 at 1:58 PM, Madhuka Udantha madh...@wso2.com wrote: Hi, I found the cause for the failure. It is about jaggery file structure By debugging automation.engine [CodeCoverageUtils (line 136)] Where try to access \plugins. jaggery file structure bit different[2] to other wso2 products[1]. Jaggery have extra directory called carbon and it is missing in CodeCoverageUtils.java. So we will need some fix for this where we can pass it from configuration or looking on server name or type to define file/path structure. [1] F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT\repository\components\plugins [2] F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT\ *carbon*\repository\components\plugins On Thu, Apr 24, 2014 at 1:08 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Dharshana, The startup script naming problems if fixed already - [1]. So the problems is not with startup script name. [1]https://wso2.org/jira/browse/TA-825 Thanks, Krishantha. On Thu, Apr 24, 2014 at 11:43 AM, Dharshana Warusavitharana dharsha...@wso2.com wrote: Hi Madhuka, Please refine the instrumentation jars listed in intrumentation.txt. Seems like the jar files which are listed to be instrument were not present in the pack. Id the startup script is different that will be the next point. For that you can have your own server startup module and add it as an extensible module to the framework. You can refer [1] to write a extensible module for the framework. [1]. https://docs.wso2.org/display/TA430/Pluggable+Module+Executors Thank You, Dharshana. On Thu, Apr 24, 2014 at 11:10 AM, Madhuka Udantha madh...@wso2.comwrote: Getting error start carbon server from test-automation-framework Since jaggery have different name for server starting script. was it the issue? or is there any config need to added? I have updated below repo and built. - carbon-platform-integration - carbon-platform-integration-utils [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ org.jaggeryjs.integration.tests --- [INFO] Surefire report directory: F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\surefire-reports --- T E S T S --- Running TestSuite Extracting carbon zip file.. Carbon Home - F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp1398317632682\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT Instrumentation of jar files in progress ... Fail to start carbon server java.lang.NullPointerException at org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.instrumentSelectedFiles(CodeCoverageUtils.java:140) at org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.instrument(CodeCoverageUtils.java:108) at org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerManager.startServerUsingCarbonHome(CarbonServerManager.java:71) at org.wso2.carbon.integration.common.extensions.carbonserver.TestServerManager.startServer(TestServerManager.java:102) at org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension.onExecutionStart(CarbonServerExtension.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.executeExtensible(TestNGExtensionExecutor.java:73) at org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionStart(TestExecutionListener.java:48) at org.testng.TestNG.runExecutionListeners(TestNG.java:1032) at org.testng.TestNG.run
Re: [Dev] Product repo naming in GitHub
On Tue, Apr 22, 2014 at 11:43 AM, Udara Rathnayake uda...@wso2.com wrote:
Hi all,
At the moment we do have our products within GitHub[1][2]. Since we need
to move in to the Git organizational model with repos in both wso2 and
wso2-dev organizations we can,
i) Rename existing repos within wso2 into product-{name}
ii) Create new repos and move existing source
By following the 1st approach we can keep our history
+1, for renaming repo.
It help to track commit history
if we follow (ii), we can have issue in forks, externals,clones. Therefore
we have try (i)
(but we are going to work in wso2-dev fresh repo after this move) and
GitHub will redirect existing information to the new name[3]. Anyway we
have to create new repos within wso2-dev organization.
[1] https://github.com/wso2/enterprise-store
[2] https://github.com/wso2/ues
[3] https://help.github.com/articles/renaming-a-repository
Regards,
UdaraR
--
*Udara Rathnayake*
Software Engineer
WSO2 Inc. : http://wso2.com
Mobile : +94 772207239
Twitter : http://twitter.com/udarakr
Blog: http://udarakr.blogspot.com
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Jaggery shifting to test-automation-framework 4.3.1
Getting error start carbon server from test-automation-framework Since jaggery have different name for server starting script. was it the issue? or is there any config need to added? I have updated below repo and built. - carbon-platform-integration - carbon-platform-integration-utils [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ org.jaggeryjs.integration.tests --- [INFO] Surefire report directory: F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\surefire-reports --- T E S T S --- Running TestSuite Extracting carbon zip file.. Carbon Home - F:\WSO2\git\jaggery\jaggery01\jaggery\server\integration\tests-integration\target\carbontmp1398317632682\jaggery-0.9.0.ALPHA5.wso2v1-SNAPSHOT Instrumentation of jar files in progress ... Fail to start carbon server java.lang.NullPointerException at org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.instrumentSelectedFiles(CodeCoverageUtils.java:140) at org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.instrument(CodeCoverageUtils.java:108) at org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerManager.startServerUsingCarbonHome(CarbonServerManager.java:71) at org.wso2.carbon.integration.common.extensions.carbonserver.TestServerManager.startServer(TestServerManager.java:102) at org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension.onExecutionStart(CarbonServerExtension.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.executeExtensible(TestNGExtensionExecutor.java:73) at org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionStart(TestExecutionListener.java:48) at org.testng.TestNG.runExecutionListeners(TestNG.java:1032) at org.testng.TestNG.run(TestNG.java:983) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to access a HTML element using Jaggery?
Hi, Dumidu Jaggery is basically, server-side Javascript scripting engine.[1]. So you can used jquery in your app regard HTML element operations. Here is sample jaggery app[2], where you can find sample codes and how it have handle. BTW you can try caramel as well[3]. [1] http://jaggeryjs.org/ [2] https://github.com/wso2/jaggery/tree/master/apps [3] https://github.com/wso2/caramel On Mon, Apr 21, 2014 at 11:15 AM, Dumidu Handakumbura dum...@wso2.comwrote: Hi Devs, How can I access a HTML element using Jaggery? Similar to document.getElementById() in JS? Also is there a way to access a variable inside a JS script block from a Jaggery script block in the same document. Thanks and Regards, Dumidu -- *Dumidu Handakumbura* Software Engineer - QA WSO2 Inc; http://www.wso2.com/. Mobile; *+9406740 %2B9406740 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
On Sun, Apr 20, 2014 at 12:48 PM, Amila Maha Arachchi ami...@wso2.comwrote: An alternative solution can be proposed based on the nature of the jaggery app. i.e. is it available in the product itself, similar to publisher and store apps of APIM or is it an app you deploy in to AppServer or any other server. 1. If it is packed with the product, you can simply keep the site.json file as a template in puppet or in a suitable way if you are using any other config management mechanisms. +1 2. If the app is deployed in to a server, then it is somewhat difficult to manage the config files. Then, one option is to bundle the correct config file at the build time (using some maven params or ant stuff). I don't think we should change the way how the config is read. This could be done with alternatives according to your requirements. But, there is no concrete solution IMO. On Fri, Apr 18, 2014 at 11:07 PM, Manuranga Perera m...@wso2.com wrote: *Current Implementation* We currently keep configuration files for jaggery apps within the app itself (eg: site.json). *Issue with Current Implementation* But this is creating some difficulties in multi environment deployments. Since the configuration files will contain some environment specific information (eg: SSO IDP URL), this makes the artifacts un-portable across environments. *Suggested Solution* We can implement a mechanism where the configuration is read from an outside location (eg: repository/conf) at deployment time and keep it in the application context and reuse it. Let's discuss the feasibility of this solution. alternative solutions are welcome. -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] need RegistryKeyStore with kernel patch0004
On Tue, Apr 8, 2014 at 1:33 PM, Sagara Gunathunga sag...@wso2.com wrote:
Hi Madhuka,
Just adding this configuration only does not make much sense instead we
need some description with few lines.
- Use cases for RegistryKeyStore
Configuring an ESB cluster for WS-Security, https and the use of digital
certificates. It is fronted by ELB. Therefore request can be served any
nodes. client app send to the ESB messages that are signed and encrypted
as specifiied by WS-Security; specifically we are using a proxy service
secured with the Sign and encrypt - X509 Authentication ESB security
scenario.
- Why we need another KeyStore other than primary one ( purpose of having
two keystores in carbon.xml)
Cn depends on hostname so the 2 private keys are different
- How this works
For Encrypt Decrypt it will picked from RegistryKeyStore
- What kind of keys supported
Please work with Manoj/a Carbon team/Docs team member to get this done.
Thanks !
On Mon, Apr 7, 2014 at 11:40 AM, Madhuka Udantha madh...@wso2.com wrote:
Hi, Sagara
Here is configuration for RegistryKeyStore that to be used in carbon.xml
!--
Encrypt Decrypt Store will be used for encrypting and decrypting
--
RegistryKeyStore
!-- Keystore file location--
Location${carbon.home}/repository/resources/security/wso2carbon.jks/Location
!-- Keystore type (JKS/PKCS12 etc.)--
TypeJKS/Type
!-- Keystore password--
Passwordwso2carbon/Password
!-- Private Key alias--
KeyAliaswso2carbon/KeyAlias
!-- Private Key password--
KeyPasswordwso2carbon/KeyPassword
/RegistryKeyStore
It is not added to documentation, need[1] to added to documentation.
Thanks
[1] https://wso2.org/jira/browse/DOCUMENTATION-696
On Mon, Apr 7, 2014 at 2:32 PM, Sagara Gunathunga sag...@wso2.comwrote:
HI Manoj/Madhuka,
Could you please point me to the documentation on RegistryKeyStore
entry ?
Thanks !
On Wed, Jan 8, 2014 at 5:28 AM, Manoj Kumara ma...@wso2.com wrote:
Hi All,
This was due to jira issue [1]. Along with the fix we also patched the
carbon.xml file and its on the patch. Please refer the README.txt on
patch0004 [2] for the instructions. This issue is due to missing the config
files during applying the patch.
[1] https://wso2.org/jira/browse/CARBON-14500
[2]
http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0004/README.txt
Thanks,
Manoj
Best Regards..
Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com
Twitter: http://twitter.com/ManKuma
Mobile: +94713448188
On Wed, Jan 8, 2014 at 6:36 AM, Isuru Perera isu...@wso2.com wrote:
What is the reason for introducing another keystore for Registry?
IMO, we should reduce the number of keystores in a product.
On Tue, Jan 7, 2014 at 9:12 PM, Malaka Silva mal...@wso2.com wrote:
Hi,
We have experienced a issue with ESB 4.8.1.
Issue seems to be introduced with kernel patch 004
There was an error thrown when trying to add a tenant using GUI.
Adding following to the carbon.xml (manually) seem to fix it.
RegistryKeyStore
!-- Keystore file location--
Location${carbon.home}/repository/resources/security/wso2carbon.jks/Location
!-- Keystore type (JKS/PKCS12 etc.)--
TypeJKS/Type
!-- Keystore password--
Passwordwso2carbon/Password
!-- Private Key alias--
KeyAliaswso2carbon/KeyAlias
!-- Private Key password--
KeyPasswordwso2carbon/KeyPassword
/RegistryKeyStore
I'm not sure how this needs to be added to the build?
--
Best Regards,
Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/
Save a tree -Conserve nature Save the world for your future. Print
this email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Sagara Gunathunga
Senior Technical Lead; WSO2, Inc.; http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ; http://ssagara.blogspot.com
--
*Madhuka* Udantha
Senior Software
Re: [Dev] [DEV] need RegistryKeyStore with kernel patch0004
Hi, Sagara
Here is configuration for RegistryKeyStore that to be used in carbon.xml
!--
Encrypt Decrypt Store will be used for encrypting and decrypting
--
RegistryKeyStore
!-- Keystore file location--
Location${carbon.home}/repository/resources/security/wso2carbon.jks/Location
!-- Keystore type (JKS/PKCS12 etc.)--
TypeJKS/Type
!-- Keystore password--
Passwordwso2carbon/Password
!-- Private Key alias--
KeyAliaswso2carbon/KeyAlias
!-- Private Key password--
KeyPasswordwso2carbon/KeyPassword
/RegistryKeyStore
It is not added to documentation, need[1] to added to documentation.
Thanks
[1] https://wso2.org/jira/browse/DOCUMENTATION-696
On Mon, Apr 7, 2014 at 2:32 PM, Sagara Gunathunga sag...@wso2.com wrote:
HI Manoj/Madhuka,
Could you please point me to the documentation on RegistryKeyStore entry
?
Thanks !
On Wed, Jan 8, 2014 at 5:28 AM, Manoj Kumara ma...@wso2.com wrote:
Hi All,
This was due to jira issue [1]. Along with the fix we also patched the
carbon.xml file and its on the patch. Please refer the README.txt on
patch0004 [2] for the instructions. This issue is due to missing the config
files during applying the patch.
[1] https://wso2.org/jira/browse/CARBON-14500
[2]
http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0004/README.txt
Thanks,
Manoj
Best Regards..
Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com
Twitter: http://twitter.com/ManKuma
Mobile: +94713448188
On Wed, Jan 8, 2014 at 6:36 AM, Isuru Perera isu...@wso2.com wrote:
What is the reason for introducing another keystore for Registry?
IMO, we should reduce the number of keystores in a product.
On Tue, Jan 7, 2014 at 9:12 PM, Malaka Silva mal...@wso2.com wrote:
Hi,
We have experienced a issue with ESB 4.8.1.
Issue seems to be introduced with kernel patch 004
There was an error thrown when trying to add a tenant using GUI.
Adding following to the carbon.xml (manually) seem to fix it.
RegistryKeyStore
!-- Keystore file location--
Location${carbon.home}/repository/resources/security/wso2carbon.jks/Location
!-- Keystore type (JKS/PKCS12 etc.)--
TypeJKS/Type
!-- Keystore password--
Passwordwso2carbon/Password
!-- Private Key alias--
KeyAliaswso2carbon/KeyAlias
!-- Private Key password--
KeyPasswordwso2carbon/KeyPassword
/RegistryKeyStore
I'm not sure how this needs to be added to the build?
--
Best Regards,
Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/
Save a tree -Conserve nature Save the world for your future. Print
this email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Sagara Gunathunga
Senior Technical Lead; WSO2, Inc.; http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ; http://ssagara.blogspot.com
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] Get the list of data-sources defined in master-datasources.xml
Hi,
Both approaches are valid
Approach 2 will much better to used IMO since
- We have followed approach 2 in ES and UES (in our other products/apps)
- 'carbon' jaggery module have function called 'loadConfig' and it is
written to get carbon server config and
'conf\datasources\master-datasources.xml'
is valid config file to get through carbon module
Thanks
[1]
https://github.com/wso2/enterprise-store/blob/master/modules/apps/publisher/config/app.js
On Tue, Apr 1, 2014 at 12:41 PM, Tanya Madurapperuma ta...@wso2.com wrote:
Hi all,
I need to $ subject in a jaggery app and came across the following two
approaches.
What is the best approach to go ahead with? Or is there any other approach?
*Approach 1*
%
var log = new Log();
var datasourceManager =
Packages.org.wso2.carbon.ndatasource.core.DataSourceManager;
var mydatasourceManager = new datasourceManager();
var coll =
mydatasourceManager.getInstance().getDataSourceRepository().getAllDataSources();
var iterator = coll.iterator();
while (iterator.hasNext()) {
log.info(iterator.next().getDSMInfo().getName());
}
%
*Approach 2*
%
var log = new Log();
var carbon = require('carbon');
var masterds =
carbon.server.loadConfig('datasources/master-datasources.xml');
var ds = masterds.*::['datasources'].*::['datasource'].*::['name'].text();
log.info(ds);
%
Thanks,
Tanya
--
Tanya Madurapperuma
Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] Get the list of data-sources defined in master-datasources.xml
On Tue, Apr 1, 2014 at 2:42 PM, Ruchira Wageesha ruch...@wso2.com wrote:
I think, it better to go with Approach 1. i.e. Then you are independent
from the XML configuration and relying on Java API.
replying on java API is good
+1,
Better we shift other location[1] also to get code consistency.
BTW, rename variable datasourceManager as DataSourceManager. i.e. exactly
like the class name.
/Ruchira
On Tue, Apr 1, 2014 at 2:32 PM, Madhuka Udantha madh...@wso2.com wrote:
Hi,
Both approaches are valid
Approach 2 will much better to used IMO since
- We have followed approach 2 in ES and UES (in our other
products/apps)
- 'carbon' jaggery module have function called 'loadConfig' and it is
written to get carbon server config and
'conf\datasources\master-datasources.xml'
is valid config file to get through carbon module
Thanks
[1]
https://github.com/wso2/enterprise-store/blob/master/modules/apps/publisher/config/app.js
On Tue, Apr 1, 2014 at 12:41 PM, Tanya Madurapperuma ta...@wso2.comwrote:
Hi all,
I need to $ subject in a jaggery app and came across the following two
approaches.
What is the best approach to go ahead with? Or is there any other
approach?
*Approach 1*
%
var log = new Log();
var datasourceManager =
Packages.org.wso2.carbon.ndatasource.core.DataSourceManager;
var mydatasourceManager = new datasourceManager();
var coll =
mydatasourceManager.getInstance().getDataSourceRepository().getAllDataSources();
var iterator = coll.iterator();
while (iterator.hasNext()) {
log.info(iterator.next().getDSMInfo().getName());
}
%
*Approach 2*
%
var log = new Log();
var carbon = require('carbon');
var masterds =
carbon.server.loadConfig('datasources/master-datasources.xml');
var ds =
masterds.*::['datasources'].*::['datasource'].*::['name'].text();
log.info(ds);
%
Thanks,
Tanya
--
Tanya Madurapperuma
Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
--
*Ruchira Wageesha**Associate Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com*
*email: ruch...@wso2.com ruch...@wso2.com, blog:
ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com,
mobile: +94 77 5493444 %2B94%2077%205493444*
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] P2 issues when installing WSO2 Store feature in multiple profiles
Hi, We went with 1.1.0 and notice that Missing requirement: WSO2 Enterprise Store Feature 1.1.0 (org.wso2.store.feature.group 1.1.0) requires 'org.wso2.carbon.registry.contentsearch.server.feature.group [4.2.1,4.3.0)' but it could not be found Had call with Nirmal (offline chat) and think it is much fine them to go with ES 1.0.0 tag[1] with fixed rather 1.0.1 (es-1.0.1-apm-reg - git branch name) Branch 1.0.1[2] cut from [1] tag 1.0.0 (All need fix will go with 1.0.1) Branch es-1.0.1-apm-reg (Non release version of 1.5.0) will be move 1.0.2 [1] https://github.com/wso2/enterprise-store/releases/tag/1.0.0 [2] https://github.com/wso2/enterprise-store/tree/1.0.1 [3] https://github.com/wso2/enterprise-store/tree/es-1.0.1-apm-reg On Fri, Mar 28, 2014 at 10:26 AM, Nirmal Fernando nir...@wso2.com wrote: Thanks Madhuka! On Fri, Mar 28, 2014 at 10:22 AM, Madhuka Udantha madh...@wso2.comwrote: Hi, We will create new branch from store 1.0.0 and fix it. I will inform branch(git) and store version after creating the branch. Thanks On Fri, Mar 28, 2014 at 10:07 AM, Nirmal Fernando nir...@wso2.comwrote: Hi All, Below is the error I get when building a multi-profile product.: Installation failed. An error occurred while configuring the installed items session context was:(profile=default, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null -- [R]org.wso2.store.feature.group 1.0.0, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction). I/O Error while copying /wso2/code/incubator-stratos/products/stratos/modules/p2-profile-gen/target/wso2carbon-core-4.2.0/repository/components/default/../features/org.wso2.store_1.0.0/apps - see details. Caused by: java.io.IOException: Source: /wso2/code/incubator-stratos/products/stratos/modules/p2-profile-gen/target/wso2carbon-core-4.2.0/repository/components/default/../features/org.wso2.store_1.0.0/appsdoes not exists Application failed, log file location: /wso2/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1395934067366.log Can we please get a fix for this issue? -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] P2 issues when installing WSO2 Store feature in multiple profiles
Hi, Branch(ES 1.0.1) work done. Version is out as 1.0.1 [1] https://github.com/wso2/enterprise-store/tree/1.0.1 On Fri, Mar 28, 2014 at 1:17 PM, Madhuka Udantha madh...@wso2.com wrote: Hi, We went with 1.1.0 and notice that Missing requirement: WSO2 Enterprise Store Feature 1.1.0 (org.wso2.store.feature.group 1.1.0) requires 'org.wso2.carbon.registry.contentsearch.server.feature.group [4.2.1,4.3.0)' but it could not be found Had call with Nirmal (offline chat) and think it is much fine them to go with ES 1.0.0 tag[1] with fixed rather 1.0.1 (es-1.0.1-apm-reg - git branch name) Branch 1.0.1[2] cut from [1] tag 1.0.0 (All need fix will go with 1.0.1) Branch es-1.0.1-apm-reg (Non release version of 1.5.0) will be move 1.0.2 [1] https://github.com/wso2/enterprise-store/releases/tag/1.0.0 [2] https://github.com/wso2/enterprise-store/tree/1.0.1 [3] https://github.com/wso2/enterprise-store/tree/es-1.0.1-apm-reg On Fri, Mar 28, 2014 at 10:26 AM, Nirmal Fernando nir...@wso2.com wrote: Thanks Madhuka! On Fri, Mar 28, 2014 at 10:22 AM, Madhuka Udantha madh...@wso2.comwrote: Hi, We will create new branch from store 1.0.0 and fix it. I will inform branch(git) and store version after creating the branch. Thanks On Fri, Mar 28, 2014 at 10:07 AM, Nirmal Fernando nir...@wso2.comwrote: Hi All, Below is the error I get when building a multi-profile product.: Installation failed. An error occurred while configuring the installed items session context was:(profile=default, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null -- [R]org.wso2.store.feature.group 1.0.0, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction). I/O Error while copying /wso2/code/incubator-stratos/products/stratos/modules/p2-profile-gen/target/wso2carbon-core-4.2.0/repository/components/default/../features/org.wso2.store_1.0.0/apps - see details. Caused by: java.io.IOException: Source: /wso2/code/incubator-stratos/products/stratos/modules/p2-profile-gen/target/wso2carbon-core-4.2.0/repository/components/default/../features/org.wso2.store_1.0.0/appsdoes not exists Application failed, log file location: /wso2/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1395934067366.log Can we please get a fix for this issue? -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] P2 issues when installing WSO2 Store feature in multiple profiles
Hi, We will create new branch from store 1.0.0 and fix it. I will inform branch(git) and store version after creating the branch. Thanks On Fri, Mar 28, 2014 at 10:07 AM, Nirmal Fernando nir...@wso2.com wrote: Hi All, Below is the error I get when building a multi-profile product.: Installation failed. An error occurred while configuring the installed items session context was:(profile=default, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null -- [R]org.wso2.store.feature.group 1.0.0, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction). I/O Error while copying /wso2/code/incubator-stratos/products/stratos/modules/p2-profile-gen/target/wso2carbon-core-4.2.0/repository/components/default/../features/org.wso2.store_1.0.0/apps - see details. Caused by: java.io.IOException: Source: /wso2/code/incubator-stratos/products/stratos/modules/p2-profile-gen/target/wso2carbon-core-4.2.0/repository/components/default/../features/org.wso2.store_1.0.0/appsdoes not exists Application failed, log file location: /wso2/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1395934067366.log Can we please get a fix for this issue? -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] jaggery-branch-for-kernel4.3.0 refers webapp.mgt 4.2.1 version
noted On Fri, Mar 21, 2014 at 1:00 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi Madhuka This jaggery branch still refers org.wso2.carbon.webapp.mgt 4.2.1 version [1]. Please change it to 4.3.0-SNAPSHOT. AS packs does not start due to this issue. [1] https://github.com/wso2/jaggery/blob/branch-for-kernel4.3.0/pom.xml Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
On Thu, Mar 20, 2014 at 5:42 PM, Subash Chaturanga sub...@wso2.com wrote: Hi Madhuka I am getting following when building the given jaggery kernel repo locally. The project org.jaggeryjs:jaggery-parent:0.9.0-SNAPSHOT (/home/subash/development/git-repo/jaggery/pom.xml) has 1 error [ERROR] Child module /home/subash/development/git-repo/jaggery/jaggery-extensions/pom.xml of /home/subash/development/git-repo/jaggery/pom.xml does not exist jaggery-extensions need git submodule update On Fri, Feb 28, 2014 at 3:05 PM, Madhuka Udantha madh...@wso2.com wrote: Refereed link [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 2:42 PM, Isuru Perera isu...@wso2.com wrote: %s/kernal/kernel On Fri, Feb 28, 2014 at 2:39 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal 4.2.0. Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with AS5.3.0 Here I have created branch[1] upon on $subject.(Regard 4.3.0 shift commits will add to here[1], late we will merge it to master and release) [1] https://github.com/wso2/jaggery/tree/branch-for-kernal4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks /subash *Subash Chaturanga* Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
On Thu, Mar 20, 2014 at 6:09 PM, Sagara Gunathunga sag...@wso2.com wrote: Subash, Why do you build Jaggery locally ? @ Subash and Sagara He is building master[1], It is also bulid fine, test in bambo build, as i have pointed he is missing sub module update. If he is try kernel 4.3.0 we must build branch[2] I have created. This branch also fixed in (jekins also fixed the build - missing sanshot for uploading rule) [1] https://github.com/wso2/jaggery [2] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 [3] https://wso2.org/bamboo/browse/WSJ001-SCJ002-304 no one suppose to do that other than UES team you should able to get those dependencies from Nexus repo. I have repeated several times about Jaggery build but still those artefacts not available on Nexus Repo. This is a blocker for AS M1 release scheduled for tomorrow please fix this ASAP. Ruchira/SameeraP, please follow up on this item. Thanks ! On Thu, Mar 20, 2014 at 6:02 PM, Madhuka Udantha madh...@wso2.com wrote: On Thu, Mar 20, 2014 at 5:42 PM, Subash Chaturanga sub...@wso2.comwrote: Hi Madhuka I am getting following when building the given jaggery kernel repo locally. The project org.jaggeryjs:jaggery-parent:0.9.0-SNAPSHOT (/home/subash/development/git-repo/jaggery/pom.xml) has 1 error [ERROR] Child module /home/subash/development/git-repo/jaggery/jaggery-extensions/pom.xml of /home/subash/development/git-repo/jaggery/pom.xml does not exist jaggery-extensions need git submodule update On Fri, Feb 28, 2014 at 3:05 PM, Madhuka Udantha madh...@wso2.comwrote: Refereed link [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 2:42 PM, Isuru Perera isu...@wso2.com wrote: %s/kernal/kernel On Fri, Feb 28, 2014 at 2:39 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal 4.2.0. Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with AS5.3.0 Here I have created branch[1] upon on $subject.(Regard 4.3.0 shift commits will add to here[1], late we will merge it to master and release) [1] https://github.com/wso2/jaggery/tree/branch-for-kernal4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks /subash *Subash Chaturanga* Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
Hi, According last build[1] in Jenkins. jaggery branch build fine. When we uploading jar we are getting below error. As Uploading jar need SNAPSHOT for the name? So we could added such for our version. But it seems version number will have ugly as it is branch n using SNAPSHOt Failed to transfer file: http://maven.wso2.org/nexus/content/repositories/snapshots/org/jaggeryjs/components/0.9.0.ALPHA5.wso2v1/components-0.9.0.ALPHA5.wso2v1.pom. Return code is: 400, ReasonPhrase: Bad Request. [1] Build failed in Jenkins: jaggery-branch-for-kernel4.3.0 #8 On Thu, Mar 20, 2014 at 7:54 PM, Sagara Gunathunga sag...@wso2.com wrote: On Thu, Mar 20, 2014 at 7:46 PM, Ruchira Wageesha ruch...@wso2.comwrote: Hi Sagara, What Subash has built is the Jaggery master(see the SNAPSHOT version). Regarding the nexus thing, AFAIK, AS team is building the branch(through jenkins) which Madhuka created. So, according to the Madhuka's reply above, why Jaggery build fails is due to a missing kernal patch. As per the thread Missing patch @dev, Geeth should be working on getting the kernal patch into nexus. But, it doesn't have any updates for last few days. FYI. Thanks for the clarification. Shall we have a meeting tomorrow morning to resolve all these issues ? We need Geeth, KasunG, Madhuka, Subash, Shameera and Manoj for this. Thanks ! @Subath Please follow the README under Jaggery project which says how to build Jaggery master. On Thu, Mar 20, 2014 at 6:09 PM, Sagara Gunathunga sag...@wso2.comwrote: Subash, Why do you build Jaggery locally ? no one suppose to do that other than UES team you should able to get those dependencies from Nexus repo. I have repeated several times about Jaggery build but still those artefacts not available on Nexus Repo. This is a blocker for AS M1 release scheduled for tomorrow please fix this ASAP. Ruchira/SameeraP, please follow up on this item. Thanks ! On Thu, Mar 20, 2014 at 6:02 PM, Madhuka Udantha madh...@wso2.comwrote: On Thu, Mar 20, 2014 at 5:42 PM, Subash Chaturanga sub...@wso2.comwrote: Hi Madhuka I am getting following when building the given jaggery kernel repo locally. The project org.jaggeryjs:jaggery-parent:0.9.0-SNAPSHOT (/home/subash/development/git-repo/jaggery/pom.xml) has 1 error [ERROR] Child module /home/subash/development/git-repo/jaggery/jaggery-extensions/pom.xml of /home/subash/development/git-repo/jaggery/pom.xml does not exist jaggery-extensions need git submodule update On Fri, Feb 28, 2014 at 3:05 PM, Madhuka Udantha madh...@wso2.comwrote: Refereed link [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 2:42 PM, Isuru Perera isu...@wso2.comwrote: %s/kernal/kernel On Fri, Feb 28, 2014 at 2:39 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal 4.2.0. Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with AS5.3.0 Here I have created branch[1] upon on $subject.(Regard 4.3.0 shift commits will add to here[1], late we will merge it to master and release) [1] https://github.com/wso2/jaggery/tree/branch-for-kernal4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks /subash *Subash Chaturanga* Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
On Fri, Mar 21, 2014 at 12:26 AM, Madhuka Udantha madh...@wso2.com wrote: Hi, According last build[1] in Jenkins. jaggery branch build fine. When we uploading jar we are getting below error. As Uploading jar need SNAPSHOT for the name? So we could added such for our version. But it seems version number will have ugly as it is branch n using SNAPSHOt Version Number changed plus SNAPSHOt @Geeth: can trigger jaggery branch build again? Failed to transfer file: http://maven.wso2.org/nexus/content/repositories/snapshots/org/jaggeryjs/components/0.9.0.ALPHA5.wso2v1/components-0.9.0.ALPHA5.wso2v1.pom. Return code is: 400, ReasonPhrase: Bad Request. [1] Build failed in Jenkins: jaggery-branch-for-kernel4.3.0 #8 On Thu, Mar 20, 2014 at 7:54 PM, Sagara Gunathunga sag...@wso2.comwrote: On Thu, Mar 20, 2014 at 7:46 PM, Ruchira Wageesha ruch...@wso2.comwrote: Hi Sagara, What Subash has built is the Jaggery master(see the SNAPSHOT version). Regarding the nexus thing, AFAIK, AS team is building the branch(through jenkins) which Madhuka created. So, according to the Madhuka's reply above, why Jaggery build fails is due to a missing kernal patch. As per the thread Missing patch @dev, Geeth should be working on getting the kernal patch into nexus. But, it doesn't have any updates for last few days. FYI. Thanks for the clarification. Shall we have a meeting tomorrow morning to resolve all these issues ? We need Geeth, KasunG, Madhuka, Subash, Shameera and Manoj for this. Thanks ! @Subath Please follow the README under Jaggery project which says how to build Jaggery master. On Thu, Mar 20, 2014 at 6:09 PM, Sagara Gunathunga sag...@wso2.comwrote: Subash, Why do you build Jaggery locally ? no one suppose to do that other than UES team you should able to get those dependencies from Nexus repo. I have repeated several times about Jaggery build but still those artefacts not available on Nexus Repo. This is a blocker for AS M1 release scheduled for tomorrow please fix this ASAP. Ruchira/SameeraP, please follow up on this item. Thanks ! On Thu, Mar 20, 2014 at 6:02 PM, Madhuka Udantha madh...@wso2.comwrote: On Thu, Mar 20, 2014 at 5:42 PM, Subash Chaturanga sub...@wso2.comwrote: Hi Madhuka I am getting following when building the given jaggery kernel repo locally. The project org.jaggeryjs:jaggery-parent:0.9.0-SNAPSHOT (/home/subash/development/git-repo/jaggery/pom.xml) has 1 error [ERROR] Child module /home/subash/development/git-repo/jaggery/jaggery-extensions/pom.xml of /home/subash/development/git-repo/jaggery/pom.xml does not exist jaggery-extensions need git submodule update On Fri, Feb 28, 2014 at 3:05 PM, Madhuka Udantha madh...@wso2.comwrote: Refereed link [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 2:42 PM, Isuru Perera isu...@wso2.comwrote: %s/kernal/kernel On Fri, Feb 28, 2014 at 2:39 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal 4.2.0. Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with AS5.3.0 Here I have created branch[1] upon on $subject.(Regard 4.3.0 shift commits will add to here[1], late we will merge it to master and release) [1] https://github.com/wso2/jaggery/tree/branch-for-kernal4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks /subash *Subash Chaturanga* Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
Hi, Sagara. Jaggery Build fine and it is fixed[1] in jenkins. *Confirmed from Geeth.* [INFO] Deployment done in 4 min 38 sec Sending e-mails to: buil...@wso2.org madh...@wso2.com Finished: SUCCESS [1] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/9/console On Thu, Mar 20, 2014 at 6:09 PM, Sagara Gunathunga sag...@wso2.com wrote: Subash, Why do you build Jaggery locally ? no one suppose to do that other than UES team you should able to get those dependencies from Nexus repo. I have repeated several times about Jaggery build but still those artefacts not available on Nexus Repo. This is a blocker for AS M1 release scheduled for tomorrow please fix this ASAP. Ruchira/SameeraP, please follow up on this item. Thanks ! On Thu, Mar 20, 2014 at 6:02 PM, Madhuka Udantha madh...@wso2.com wrote: On Thu, Mar 20, 2014 at 5:42 PM, Subash Chaturanga sub...@wso2.comwrote: Hi Madhuka I am getting following when building the given jaggery kernel repo locally. The project org.jaggeryjs:jaggery-parent:0.9.0-SNAPSHOT (/home/subash/development/git-repo/jaggery/pom.xml) has 1 error [ERROR] Child module /home/subash/development/git-repo/jaggery/jaggery-extensions/pom.xml of /home/subash/development/git-repo/jaggery/pom.xml does not exist jaggery-extensions need git submodule update On Fri, Feb 28, 2014 at 3:05 PM, Madhuka Udantha madh...@wso2.comwrote: Refereed link [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 2:42 PM, Isuru Perera isu...@wso2.com wrote: %s/kernal/kernel On Fri, Feb 28, 2014 at 2:39 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal 4.2.0. Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with AS5.3.0 Here I have created branch[1] upon on $subject.(Regard 4.3.0 shift commits will add to here[1], late we will merge it to master and release) [1] https://github.com/wso2/jaggery/tree/branch-for-kernal4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks /subash *Subash Chaturanga* Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Session replication in jaggery apps
On Tue, Mar 18, 2014 at 11:16 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
Great. Shall we also have this documented, if not already done?
Yap, Since some features/functions/APIs lately added to jaggery and had
missed documentation.
We will sync docs and APIs soon. (Around in week)
On Tue, Mar 18, 2014 at 11:04 AM, Dilshan Edirisuriya dils...@wso2.comwrote:
I have implemented this feature and tested it. You have to add
distributable property (true/false) in Jaggery conf file. Rest of the
configurations goes as [1]. Closed the JIRA.
{
displayName:My App,
welcomeFiles:[index.jag],
distributable:true
}
[1] - http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
On Tue, Mar 18, 2014 at 10:24 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
IIRC, the support for session replication for jaggery apps was added
when we implemented it for webapps. There were some changes needed from
jaggery deployment side (eg: reading jag.conf for distributable property)
and it was added. But the related jira is still in open state :
https://wso2.org/jira/browse/JAGGERY-275
@Dilshan, shouldn't this issue be in fixed state? Or is there anything
more to add?
On Mon, Mar 17, 2014 at 7:20 PM, Ruchira Wageesha ruch...@wso2.comwrote:
Hi Amila,
Since Jaggery is based on Tomcat, whatever the session replication
mechanism available for Java webapps, should be valid for Jaggery as
well[1]. But, I doubt whether it will work smoothly if there are any
non-serializable objects in the session.
/Ruchira
[1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi
ami...@wso2.comwrote:
Hi,
Assume the scenario of two API Manager instances fronted with WSO2
ELB. While user is logged in and working in publisher or store app, all
his requests are going to the same node where the session is established.
At this moment if we kill one node, requests will start going to the
other node, but theres no session available in it.
My question is:
Is session replication valid for jaggery apps?
Regards,
AmilaM.
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
*Ruchira Wageesha**Associate Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware | wso2.com
http://wso2.com*
*email: ruch...@wso2.com ruch...@wso2.com, blog:
ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com,
mobile: +94 77 5493444 %2B94%2077%205493444*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware
Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com
http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan
http://twitter.com/kishanthan*
--
Dilshan Edirisuriya
Senior Software Engineer - WSO2
Mob: + 94 777878905
http://wso2.com/
--
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware
Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS integration test migration
On Fri, Mar 14, 2014 at 11:30 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Madhuka, On Fri, Mar 14, 2014 at 10:13 AM, Madhuka Udantha madh...@wso2.comwrote: On Fri, Mar 14, 2014 at 1:01 AM, Kasun Gajasinghe kas...@wso2.comwrote: Hi Madhuka, The main reason being that the Jaggery tests have been failing in Jenkins. Jaggery only had one issue[2] It also have been fixed it build fine[3] [2] [jaggery][kernel]Missing patch @ dev [3] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/lastSuccessfulBuild/ The product-as needs to be able to be able to download the dependent artifacts via the nexus. So, I have disabled the tests for Jaggery in Jenkins. But currently, the uploading artifacts to nexus snapshots repo is failing since the project versions set in the pom.xml are not SNAPSHOT versions. @Madhuka, can you update the relevant jaggery branch, and append '-SNAPSHOT' for the project versions in all the poms? I believe the tests are failing since jaggery is configured to use 4.2.0 based automation framework. Build #3 contains the related errors. [1] Jaggery was using old automation framework (ATF) since there was some miss match with jaggery and ATF. If new ATF is ready we can make that shift I think The test framework is ready to be used and available in git repo. I think you are referring to mismatch with jaggery.sh script. yes If it is the case, then you need to write new sever start-up extension and register that class in our automation.xml will do Thanks, Krishantha. Thanks [1] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/ Thanks, KasunG On Fri, Mar 14, 2014 at 12:44 AM, Madhuka Udantha madh...@wso2.comwrote: On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera krishan...@wso2.com wrote: I'm in the middle of AS integration test migration and seems like JaggeryAppAdmin service is not available in AS yet. @AS team: any reason for this. (If is it due to that kernel patch thing I can skip oath test in jaggery per now) I will migrate all jaggery tests and exclude the tests from testng.xml file. +1 Thanks, Krishantha. On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi all, I've started AS integration test migration to new framework, however unavailability of TenantMgtAdminService casing errors while framework populate test users to the server. I will try to go ahead with disabling tenant creation. Any time-frame that this feature will be available. Thanks, Krishantha. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com http://wso2.com ** cell: **+94 (77) 678-0813 %2B94%20%2877%29%20678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* http://kasunbg.org *twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS integration test migration
On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera krishan...@wso2.com wrote: I'm in the middle of AS integration test migration and seems like JaggeryAppAdmin service is not available in AS yet. @AS team: any reason for this. (If is it due to that kernel patch thing I can skip oath test in jaggery per now) I will migrate all jaggery tests and exclude the tests from testng.xml file. +1 Thanks, Krishantha. On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi all, I've started AS integration test migration to new framework, however unavailability of TenantMgtAdminService casing errors while framework populate test users to the server. I will try to go ahead with disabling tenant creation. Any time-frame that this feature will be available. Thanks, Krishantha. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS integration test migration
On Fri, Mar 14, 2014 at 1:01 AM, Kasun Gajasinghe kas...@wso2.com wrote: Hi Madhuka, The main reason being that the Jaggery tests have been failing in Jenkins. Jaggery only had one issue[2] It also have been fixed it build fine[3] [2] [jaggery][kernel]Missing patch @ dev [3] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/lastSuccessfulBuild/ The product-as needs to be able to be able to download the dependent artifacts via the nexus. So, I have disabled the tests for Jaggery in Jenkins. But currently, the uploading artifacts to nexus snapshots repo is failing since the project versions set in the pom.xml are not SNAPSHOT versions. @Madhuka, can you update the relevant jaggery branch, and append '-SNAPSHOT' for the project versions in all the poms? I believe the tests are failing since jaggery is configured to use 4.2.0 based automation framework. Build #3 contains the related errors. [1] Jaggery was using old automation framework (ATF) since there was some miss match with jaggery and ATF. If new ATF is ready we can make that shift I think Thanks [1] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/ Thanks, KasunG On Fri, Mar 14, 2014 at 12:44 AM, Madhuka Udantha madh...@wso2.comwrote: On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera krishan...@wso2.com wrote: I'm in the middle of AS integration test migration and seems like JaggeryAppAdmin service is not available in AS yet. @AS team: any reason for this. (If is it due to that kernel patch thing I can skip oath test in jaggery per now) I will migrate all jaggery tests and exclude the tests from testng.xml file. +1 Thanks, Krishantha. On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi all, I've started AS integration test migration to new framework, however unavailability of TenantMgtAdminService casing errors while framework populate test users to the server. I will try to go ahead with disabling tenant creation. Any time-frame that this feature will be available. Thanks, Krishantha. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com http://wso2.com ** cell: **+94 (77) 678-0813 %2B94%20%2877%29%20678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* http://kasunbg.org *twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [jaggery] Coffee Shop REST sample Sources Page not found
Hi, Fixed [1] [1] http://jaggeryjs.org/samples.jag On Wed, Mar 12, 2014 at 12:25 PM, Waruna Jayaweera waru...@wso2.com wrote: Hi, In the jaggeryjs sample page (http://jaggeryjs.org/samples.jag) when you click REST sample Sources it shows page not found error. I found that error with github url. Correct github sources url is https://github.com/wso2/jaggery/tree/master/apps/*coffeeshop* but page refers to incorrect URL https://github.com/wso2/jaggery/tree/master/apps/*coffeeShop* (coffeeShop should be replaced by coffeeshop) -- Regards, Waruna Lakshitha Jayaweera Software Engineer WSO2 Inc; http://wso2.com phone: +94713255198 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [jaggery][kernel]Missing patch
Ping for the subject, On Thu, Mar 6, 2014 at 12:03 PM, Manoj Kumara ma...@wso2.com wrote: Hi Tanya, Can you send a pull request correspond to your change to [1] dev-repository, so afterwards we can merge this with [2] [1] https://github.com/wso2-dev/carbon4-kernel [2] https://github.com/wso2/carbon4-kernel Thanks, Manoj *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 On Thu, Mar 6, 2014 at 11:48 AM, Madhuka Udantha madh...@wso2.com wrote: Hi, Kernel[3] seems missing of patched[1] and details can be found in[2]. Need to added that patched for[3]. Since jaggery[4] switch for carbon 4.3.0 and testOAuthProviderOperations failed on jaggery test OauthObjectTestCase. [1] https://wso2.org/jira/browse/CARBON-14635 [2] Email subjected [Dev] Please commit to kernel patch0005 @ dev [3] https://github.com/wso2/carbon4-kernel [4] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Marketing] Request New Public Git Repo
Hi, For to share marketing week samples and demos We will need public git repo called 'wso2-marketing-demos' under WSO2[1]. Please added the repo. [1] https://github.com/wso2 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Marketing] Request New Public Git Repo
On Mon, Mar 10, 2014 at 2:05 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi All, Created in [1]. Thanks thanks Eranda [1]. https://github.com/wso2-dev/wso2-marketing-demos On Mon, Mar 10, 2014 at 12:50 PM, Sagara Gunathunga sag...@wso2.comwrote: On Mon, Mar 10, 2014 at 12:44 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, For to share marketing week samples and demos We will need public git repo called 'wso2-marketing-demos' under WSO2[1]. Please added the repo. Isn't that WSO2-Dev repo [1] is much suitable for above demos and samples ? IMHO these stuff directly related to developer experience rather our Carbon code base. [1] - https://github.com/wso2-dev Thanks ! [1] https://github.com/wso2 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
On Sat, Mar 8, 2014 at 7:10 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi Madhuka, The build is added to Jenkins. Thanks There are two test failures at the moment. Please find the full log here [1] This fixed need kernel patch and it has been reported and details can be found this email thread[1] [1] [jaggery][kernel]Missing patch @dev [1] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/2/consoleFull Regards, KasunG On Thu, Mar 6, 2014 at 11:37 AM, Madhuka Udantha madh...@wso2.com wrote: Hi, You can try to build branch now. On Wed, Mar 5, 2014 at 3:16 PM, Madhuka Udantha madh...@wso2.com wrote: I will confirm branch with testing clean repo and We will sign up Jenkins server On Wed, Mar 5, 2014 at 2:41 PM, Sagara Gunathunga sag...@wso2.comwrote: On Wed, Mar 5, 2014 at 2:13 PM, Kasun Gajasinghe kas...@wso2.comwrote: Hi Ruchira, On Wed, Mar 5, 2014 at 12:24 PM, Ruchira Wageesha ruch...@wso2.comwrote: Hi Saraga, Did you refer [1] as the Jenkins server? Do you guys manage the users or is it the infra? We need permissions to add Jaggery 0.9.0.ALPHA5.wso2v1. Build stabilization team manages this at the moment. To give you the permissions, please sign up there, and provide us your username. We will add the authorizations later on. I guess just send GitHub URL to KasunG so that he can add it. Thanks ! Thanks, KasunG [1] http://54.84.136.218:8080/jenkins On Wed, Mar 5, 2014 at 11:23 AM, Sagara Gunathunga sag...@wso2.comwrote: Madhuka, AFAIK problem is not with the AS integration instead above jaggery branch not getting build with clean repo. BTW Geeth, why are you building jaggery locally you are NOT suppose to do that you should able get jaggery SNAPSHOT dependencies from WSO2 Nexus repo. UES team please add your jaggery build to Jenkins and make your SNAPSHOTs available on Nexus. Thanks ! On Wed, Mar 5, 2014 at 11:10 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Geeth, Did you have any issue with build above branch or issue with integrating with AS? If any issue came across with integrating with AS please do the dependencies version change against for AS and do pull request for above branch.We will test standard jaggery server for you pull request and merge it. Thanks On Tue, Mar 4, 2014 at 10:59 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi Madhuka, I tried to build above branch, But I got some errors when resolving dependencies. Can you please have a look ? Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 On Mon, Mar 3, 2014 at 3:06 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, 'jaggery-0.9.0.ALPHA5.wso2v1' jaggery version[1] can be used for $subject. Above jaggery version is using kernel 4.3.0 [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com http://wso2.com ** cell: **+94 (77) 678-0813 %2B94%20%2877%29%20678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* http://kasunbg.org *twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Madhuka* Udantha Senior
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
I will confirm branch with testing clean repo and We will sign up Jenkins server On Wed, Mar 5, 2014 at 2:41 PM, Sagara Gunathunga sag...@wso2.com wrote: On Wed, Mar 5, 2014 at 2:13 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi Ruchira, On Wed, Mar 5, 2014 at 12:24 PM, Ruchira Wageesha ruch...@wso2.comwrote: Hi Saraga, Did you refer [1] as the Jenkins server? Do you guys manage the users or is it the infra? We need permissions to add Jaggery 0.9.0.ALPHA5.wso2v1. Build stabilization team manages this at the moment. To give you the permissions, please sign up there, and provide us your username. We will add the authorizations later on. I guess just send GitHub URL to KasunG so that he can add it. Thanks ! Thanks, KasunG [1] http://54.84.136.218:8080/jenkins On Wed, Mar 5, 2014 at 11:23 AM, Sagara Gunathunga sag...@wso2.comwrote: Madhuka, AFAIK problem is not with the AS integration instead above jaggery branch not getting build with clean repo. BTW Geeth, why are you building jaggery locally you are NOT suppose to do that you should able get jaggery SNAPSHOT dependencies from WSO2 Nexus repo. UES team please add your jaggery build to Jenkins and make your SNAPSHOTs available on Nexus. Thanks ! On Wed, Mar 5, 2014 at 11:10 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Geeth, Did you have any issue with build above branch or issue with integrating with AS? If any issue came across with integrating with AS please do the dependencies version change against for AS and do pull request for above branch.We will test standard jaggery server for you pull request and merge it. Thanks On Tue, Mar 4, 2014 at 10:59 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi Madhuka, I tried to build above branch, But I got some errors when resolving dependencies. Can you please have a look ? Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 On Mon, Mar 3, 2014 at 3:06 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, 'jaggery-0.9.0.ALPHA5.wso2v1' jaggery version[1] can be used for $subject. Above jaggery version is using kernel 4.3.0 [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com http://wso2.com ** cell: **+94 (77) 678-0813 %2B94%20%2877%29%20678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* http://kasunbg.org *twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [jaggery] Jaggery pom file structure
Hi, Currently jaggery master[1] features[2] and components pom files are also parent POM files. we used to added jaggery component as svn external to svn also we have to release jaggery repo each time. As other products moving in to Git[3] and jaggery contain it's component inside jaggery product so when even we release jaggery-component means we have to release jaggery. Therefore are we going to have only one root(parent) pom for jaggery (in root level) or we will continue as jaggery was. (Where we have parent pom for components and features)? Where Other WSO2 product will have only one root parent pom as[3]. [1] https://github.com/wso2/jaggery [2] https://github.com/wso2/jaggery/blob/master/features/pom.xml [3] Email Subjected Guidelines to move project into GitHub @ dev@wso2.org Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [jaggery] Jaggery pom file structure
On Thu, Mar 6, 2014 at 1:02 AM, Sagara Gunathunga sag...@wso2.com wrote: On Thu, Mar 6, 2014 at 12:31 AM, Madhuka Udantha madh...@wso2.com wrote: Hi, Currently jaggery master[1] features[2] and components pom files are also parent POM files. we used to added jaggery component as svn external to svn also we have to release jaggery repo each time. As other products moving in to Git[3] and jaggery contain it's component inside jaggery product so when even we release jaggery-component means we have to release jaggery. Therefore are we going to have only one root(parent) pom for jaggery (in root level) or we will continue as jaggery was. (Where we have parent pom for components and features)? We have separated code base into number of GItHub repos in a logical manner so that sub-modules/components of a particular repo get released together and will use same version number, with this explanation it's logical to have only one parent POM per GitHub repo. In technical side this rule make ease for snapshot based development and make it possible to apply Maven release plugin for releases. in my POV it's make sense to have one parent POM for jaggery. Where Other WSO2 product will have only one root parent pom as[3]. Yes this will be a compulsory rule to execute new development governance process and we are developing some tooling support to check this. Currently I have created and built jaggery brunch[1] from one root pom (parent pom). I am +1 for to have one parent pom for jaggery as wso2 product moving to git. [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 Thanks ! [1] https://github.com/wso2/jaggery [2] https://github.com/wso2/jaggery/blob/master/features/pom.xml [3] Email Subjected Guidelines to move project into GitHub @ dev@wso2.org Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
Hi, You can try to build branch now. On Wed, Mar 5, 2014 at 3:16 PM, Madhuka Udantha madh...@wso2.com wrote: I will confirm branch with testing clean repo and We will sign up Jenkins server On Wed, Mar 5, 2014 at 2:41 PM, Sagara Gunathunga sag...@wso2.com wrote: On Wed, Mar 5, 2014 at 2:13 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi Ruchira, On Wed, Mar 5, 2014 at 12:24 PM, Ruchira Wageesha ruch...@wso2.comwrote: Hi Saraga, Did you refer [1] as the Jenkins server? Do you guys manage the users or is it the infra? We need permissions to add Jaggery 0.9.0.ALPHA5.wso2v1. Build stabilization team manages this at the moment. To give you the permissions, please sign up there, and provide us your username. We will add the authorizations later on. I guess just send GitHub URL to KasunG so that he can add it. Thanks ! Thanks, KasunG [1] http://54.84.136.218:8080/jenkins On Wed, Mar 5, 2014 at 11:23 AM, Sagara Gunathunga sag...@wso2.comwrote: Madhuka, AFAIK problem is not with the AS integration instead above jaggery branch not getting build with clean repo. BTW Geeth, why are you building jaggery locally you are NOT suppose to do that you should able get jaggery SNAPSHOT dependencies from WSO2 Nexus repo. UES team please add your jaggery build to Jenkins and make your SNAPSHOTs available on Nexus. Thanks ! On Wed, Mar 5, 2014 at 11:10 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Geeth, Did you have any issue with build above branch or issue with integrating with AS? If any issue came across with integrating with AS please do the dependencies version change against for AS and do pull request for above branch.We will test standard jaggery server for you pull request and merge it. Thanks On Tue, Mar 4, 2014 at 10:59 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi Madhuka, I tried to build above branch, But I got some errors when resolving dependencies. Can you please have a look ? Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 On Mon, Mar 3, 2014 at 3:06 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, 'jaggery-0.9.0.ALPHA5.wso2v1' jaggery version[1] can be used for $subject. Above jaggery version is using kernel 4.3.0 [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.comwrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com http://wso2.com ** cell: **+94 (77) 678-0813 %2B94%20%2877%29%20678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* http://kasunbg.org *twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [jaggery][kernel]Missing patch
Hi, Kernel[3] seems missing of patched[1] and details can be found in[2]. Need to added that patched for[3]. Since jaggery[4] switch for carbon 4.3.0 and testOAuthProviderOperations failed on jaggery test OauthObjectTestCase. [1] https://wso2.org/jira/browse/CARBON-14635 [2] Email subjected [Dev] Please commit to kernel patch0005 @ dev [3] https://github.com/wso2/carbon4-kernel [4] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
Hi Geeth, Did you have any issue with build above branch or issue with integrating with AS? If any issue came across with integrating with AS please do the dependencies version change against for AS and do pull request for above branch.We will test standard jaggery server for you pull request and merge it. Thanks On Tue, Mar 4, 2014 at 10:59 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi Madhuka, I tried to build above branch, But I got some errors when resolving dependencies. Can you please have a look ? Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 On Mon, Mar 3, 2014 at 3:06 PM, Madhuka Udantha madh...@wso2.com wrote: Hi, 'jaggery-0.9.0.ALPHA5.wso2v1' jaggery version[1] can be used for $subject. Above jaggery version is using kernel 4.3.0 [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
Hi, 'jaggery-0.9.0.ALPHA5.wso2v1' jaggery version[1] can be used for $subject. Above jaggery version is using kernel 4.3.0 [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
Hi, Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal 4.2.0. Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with AS5.3.0 Here I have created branch[1] upon on $subject.(Regard 4.3.0 shift commits will add to here[1], late we will merge it to master and release) [1] https://github.com/wso2/jaggery/tree/branch-for-kernal4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.
Refereed link [1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0 On Fri, Feb 28, 2014 at 2:42 PM, Isuru Perera isu...@wso2.com wrote: %s/kernal/kernel On Fri, Feb 28, 2014 at 2:39 PM, Madhuka Udantha madh...@wso2.com wrote: Hi, Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal 4.2.0. Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with AS5.3.0 Here I have created branch[1] upon on $subject.(Regard 4.3.0 shift commits will add to here[1], late we will merge it to master and release) [1] https://github.com/wso2/jaggery/tree/branch-for-kernal4.3.0 On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi We need to have a jaggery release from carbon kernal 4.3.0 to ship with Application Server 5.3.0. New AS will be released on end of Q1. Latest jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0 branch. Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com http://wso2.com/ * *lean.enterprise.middleware.* email: ge...@wso2.com phone:(+94) 777911226 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery][WebSocket] Update on Missing WebSocket APIs
Current Jaggery (server side script) is missing APIs[1] (4.2.2. and 5.5.). Now you have full web socket api for js over jaggery. Core level of implementation can be found in here. [5] http://madhukaudantha.blogspot.com/2014/02/jaggery-socket-implementation-in-tomcat.html On Wed, Feb 26, 2014 at 10:58 AM, Chan duli...@wso2.com wrote: I didn't understand the point you are trying to make. Do we need to do tomcat configurations to get web-sockets to work? No need any config. (Same as it was but completed web socket API) On Tue, Feb 25, 2014 at 10:56 AM, Madhuka Udantha madh...@wso2.comwrote: Hi, Jaggery webSocket[4] is missing basic and important apis according to webSocket defined by RFC 6455[1] and Java WebSocket 1.0 API defined by JSR-356[3].There for jaggery WebSocket API will be fixed upon[2] on the $subject Thanks [1] http://tools.ietf.org/html/rfc6455 [2] http://tomcat.apache.org/tomcat-7.0-doc/web-socket-howto.html [3] http://www.oracle.com/technetwork/articles/java/jsr356-1937161.html [4] http://jaggeryjs.org/apidocs/websocket.jag -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulithawijewantha.com http://dulithawijewantha.com/ * * ~Blog blog.dulithawijewantha.com http://dulichan.github.io/chan/* * ~Twitter @dulitharw https://twitter.com/dulitharw* -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery][WebSocket] Update on Missing WebSocket APIs
On Wed, Feb 26, 2014 at 11:11 AM, Sagara Gunathunga sag...@wso2.com wrote: On Tue, Feb 25, 2014 at 10:56 AM, Madhuka Udantha madh...@wso2.comwrote: Hi, Jaggery webSocket[4] is missing basic and important apis according to webSocket defined by RFC 6455[1] and Java WebSocket 1.0 API defined by JSR-356[3].There for jaggery WebSocket API will be fixed upon[2] on the $subject +1 as per offline chat make sure Jaggery WebSocket support is compliance with JSR-356, once we make them compliance we can build storing WSO2 WebSocket story using both Java and JS. +1, jaggery will handle webSocket Thanks ! Thanks [1] http://tools.ietf.org/html/rfc6455 [2] http://tomcat.apache.org/tomcat-7.0-doc/web-socket-howto.html [3] http://www.oracle.com/technetwork/articles/java/jsr356-1937161.html [4] http://jaggeryjs.org/apidocs/websocket.jag -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Connect WSO2 ES and WSO2 UES via SSO
Hi, Here is steps you can follow. Register New Service Provider (with Issuer UES dashboard App) In UES dashboard app update 'ssoConfiguration' in config.json file for ES if is it acting as IDP. You can try this in UES 1.0.1[1] since UES 1.0.0 was using sso hostobject and UES 1.0.1 and ES 1.0.0 is using SSO module. (few app level code changes can be required). Here I am sharing few links that can help you on $subject [1] http://dist.wso2.org/maven2/org/wso2/ues/wso2ues/1.0.1/ [2] http://madhukaudantha.blogspot.com/2013/04/enabling-sso-in-wso2-user-engagement.html [3] http://madhukaudantha.blogspot.com/2014/01/sso-with-claims-in-wso2-is.html2 . On Thu, Feb 20, 2014 at 11:46 AM, Pubudud Dissanayake pubu...@wso2.comwrote: Hi All, We are working on a scenario where we want to put a link to a UES Dashboard inside an user Interface on Enterprise Store. Through this link we are passing several query string parameters which are needed by the dashboard to render the gadgets. We need to enable SSO between these two apps where a logged in user of ES will be automatically logged in and redirected to the dashboard with parameters upon clicking on the link. As a start we just tried to get this scenario working without SSO. We simply put the link to Dashboard page (on separate UES instance) and tried accessing it via ES user interface. But it redirects the request to sso/samlsso.jag of ES instance and nothing will happen afterwards. can anyone suggest a solution for this particular scenario? Suggestions and comments are welcome, Thanks. -- *Pubudu Dissanayake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile: 0775503304 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Jaggery][WebSocket] Update on Missing WebSocket APIs
Hi, Jaggery webSocket[4] is missing basic and important apis according to webSocket defined by RFC 6455[1] and Java WebSocket 1.0 API defined by JSR-356[3].There for jaggery WebSocket API will be fixed upon[2] on the $subject Thanks [1] http://tools.ietf.org/html/rfc6455 [2] http://tomcat.apache.org/tomcat-7.0-doc/web-socket-howto.html [3] http://www.oracle.com/technetwork/articles/java/jsr356-1937161.html [4] http://jaggeryjs.org/apidocs/websocket.jag -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need to get a release of caramel for BAM release
Hi, 1.0.1[1] branched for the $subject with fixed for multi profile. Since handlebars and markdown removed from caramel you also need[2]. For those two you can go with jaggery-extensions 1.0.0-SNAPSHOT, we will branched it before BAM released. Those two also fixed for $subject Before BAM release we have get jaggery-extensions [2]repo location confirm. [1] https://github.com/wso2/caramel/tree/1.0.1 [2] https://github.com/wso2/jaggery-extensions On Fri, Feb 21, 2014 at 3:27 PM, Gihan Anuruddha gi...@wso2.com wrote: Hi, We need $subject. Current caramel v 1.0.0 not supported with multi server profile products. Regards, Gihan -- W.G. Gihan Anuruddha Senior Software Engineer | WSO2, Inc. M: +94772272595 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need to get a release of caramel for BAM release
Hi, [1] is branched from 1.0.0.,(Same branch was updated). Therefore now you only need to build caramel for BAM. [1] https://github.com/wso2/caramel/tree/1.0.1 On Fri, Feb 21, 2014 at 4:32 PM, Ruchira Wageesha ruch...@wso2.com wrote: Hi Madhuka, Please release 1.0.1 basing the 1.0.0 branch. Master has been updated to use jaggery-extensions and it has been versioned as 1.1.0. What BAM guys needs is a patched 1.0.0, hence, branch from 1.0.0. Then, they don't need to depend on jaggery extensions. /Ruchira On Fri, Feb 21, 2014 at 3:48 PM, Madhuka Udantha madh...@wso2.com wrote: Hi, 1.0.1[1] branched for the $subject with fixed for multi profile. Since handlebars and markdown removed from caramel you also need[2]. For those two you can go with jaggery-extensions 1.0.0-SNAPSHOT, we will branched it before BAM released. Those two also fixed for $subject Before BAM release we have get jaggery-extensions [2]repo location confirm. [1] https://github.com/wso2/caramel/tree/1.0.1 [2] https://github.com/wso2/jaggery-extensions On Fri, Feb 21, 2014 at 3:27 PM, Gihan Anuruddha gi...@wso2.com wrote: Hi, We need $subject. Current caramel v 1.0.0 not supported with multi server profile products. Regards, Gihan -- W.G. Gihan Anuruddha Senior Software Engineer | WSO2, Inc. M: +94772272595 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Username sets to null when using get method
.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936) at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NullPointerException at org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.setUsername(XMLHttpRequestHostObject.java:436) at org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFunction_open(XMLHttpRequestHostObject.java:217) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126) ... 59 more Where is the implementation of the get method in jaggery? It's not in the xhr hostobject. -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulithawijewantha.com http://dulithawijewantha.com/ * * ~Blog blog.dulithawijewantha.com http://dulichan.github.io/chan/* * ~Twitter @dulitharw https://twitter.com/dulitharw* -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Username sets to null when using get method
Hi
This is fixed in master
On Thu, Feb 13, 2014 at 10:26 AM, Madhuka Udantha madh...@wso2.com wrote:
Hi,
Just check jaggery comments regard any change that can effect for this, as
our offline chat.
This line xhr.open(method, url, callback !== null, username, password);
in [1]
Can cause error
'get()' can be find in xhr line 463.
[1]
https://github.com/wso2/jaggery/commit/2d9fa03a01ca61a36bf8b13801ba756eae7685b9
On Thu, Feb 13, 2014 at 9:32 AM, Chan duli...@wso2.com wrote:
Hi guys,
When I say get(url, {}); I get a
09:29:58,919 {JAGGERY.router:jag}
org.mozilla.javascript.WrappedException: Wrapped
java.lang.NullPointerException (http#212)
at
org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at
org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
at
org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at org.mozilla.javascript.gen.http_1._c_anonymous_5(http:212)
at org.mozilla.javascript.gen.http_1.call(http)
at
org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at org.mozilla.javascript.gen.http_1._c_anonymous_7(http:221)
at org.mozilla.javascript.gen.http_1.call(http)
at
org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at
org.jaggeryjs.rhino.mam.modules.c6._c_anonymous_17(/mam/modules/store.js:275)
at org.jaggeryjs.rhino.mam.modules.c6.call(/mam/modules/store.js)
at
org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)
at
org.jaggeryjs.rhino.mam.controller.c1._c_anonymous_2(/mam/controller/console.js:18)
at
org.jaggeryjs.rhino.mam.controller.c1.call(/mam/controller/console.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.mam.modules.c13._c_anonymous_15(/mam/modules/absolute.js:266)
at
org.jaggeryjs.rhino.mam.modules.c13.call(/mam/modules/absolute.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at org.jaggeryjs.rhino.mam.c0._c_script_0(/mam//router.jag:325)
at org.jaggeryjs.rhino.mam.c0.call(/mam//router.jag)
at
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at org.jaggeryjs.rhino.mam.c0.call(/mam//router.jag)
at org.jaggeryjs.rhino.mam.c0.exec(/mam//router.jag)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:447)
at
org.jaggeryjs.jaggery.core.JaggeryServlet.doGet(JaggeryServlet.java:24)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2
[Dev] [Jaggery][Github] jaggery, UES and ES features remain under git project
Hi, Since jaggery[1], UES[3] and ES[3] products were in github and those jaggery/UES/ES feature also under those products[1,2,3]. They will remain same in git (Offline chat with sagara with matter). Therefore whenever other product that used one of this features(UES/jaggery/ES features) those product(eg:jaggery) need to release since we have components/features inside the products only. This is our current model in release, is this to continue? Regard to jaggery-extensions[4] will be contains p2-features that will be jaggery modules (such as caramel/jaggery-test). Thanks [1] https://github.com/wso2/jaggery [2] https://github.com/wso2/enterprise-store [3] https://github.com/wso2/ues [4] https://github.com/wso2/jaggery-extensions -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Bamboo Build Failed Error occurred while running Task 'Checkout Default Repository(1)'
Hi, $subject was occurring, with error of *Error occurred while running Task 'Checkout Default Repository(1)' of type com.atlassian.bamboo.plugins.vcs:task.vcs.checkout.* *(java.lang.RuntimeException : com.atlassian.bamboo.repository.RepositoryException: WSJ001-SCJ002-JOB1-266: Checkout to revision 6b7e98ae06c4a92358f7c7c0636b5d58d865a408 has failed.Creating directories for /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSJ001-SCJ002-JOB1/.git failed)* *(11 Feb 2014, 4:44:03 AM, Agents: WSO2JAGGERY)* Full log can be found in here[1], Thanks [1] http://wso2.org/bamboo/browse/WSJ001-SCJ002-JOB1-266/log -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Guidelines to move project into GitHub
/releases /pluginRepository /pluginRepositories 8. Make sure you have defined distribution management section as follows on your parent POM file. Jenkins will use these details to deploy your project's SNAPSHOT artefacts into Nexus so that others can use your components without building locally. distributionManagement repository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url /repository snapshotRepository idwso2.snapshots/id nameApache Snapshot Repository/name Why this is called *Apache* Snapshot Repository ? I guess name should be changed. Yes, it should be 'WSO2' not 'Apache'. Geeth, please note and modify on [1]. Thanks ! Thanks. urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url /snapshotRepository /distributionManagement Please use carbon-deployment[3] as a reference project. Eranda/Geeth please add if I missed anything. [1] - https://github.com/wso2/carbon-deployment/blob/master/pom.xml [2] - https://github.com/wso2/carbon-deployment/blob/master/components/webapp-mgt/org.wso2.carbon.webapp.mgt.ui/pom.xml [3] - https://github.com/wso2/carbon-deployment/ Thanks ! -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Isuru Udana* Senior * Software Engineer* WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Guidelines to move project into GitHub
On Wed, Feb 12, 2014 at 11:52 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Madhuka, On Wed, Feb 12, 2014 at 11:30 AM, Madhuka Udantha madh...@wso2.comwrote: Hi, Jaggery, UES[2] and ES[3] almost developed and maintain in git, for we only had git external for SVN. We have missed UES and ES features and component shared google spread sheet caled 'Moving to Git'. pls added those, It will helpful who are work on $subject ES and UES features which are only used by those relevant products, Nope, other products are using/ will use UES feature will be used in BAM, CEP *ES features will be used in other products (such as Greg - service store,ESB - connector store) - please don't add a new repo instead add them directly to the product itself. No planing to added new repo, Since other product can get feature from ES/UES product. (In this case then depend on products so one of product release we will need product release) thanks Eranda Jaggery will be consider as project and jaggery feature can be found in jaggery product[1]. [1] https://github.com/wso2/jaggery [2] https://github.com/wso2/enterprise-store [3] https://github.com/wso2/ues [4] https://github.com/wso2/jaggery-extensions On Wed, Feb 12, 2014 at 9:38 AM, Sagara Gunathunga sag...@wso2.comwrote: On Wed, Feb 12, 2014 at 9:20 AM, Isuru Udana isu...@wso2.com wrote: Hi Sagara, On Wed, Feb 12, 2014 at 12:07 AM, Sagara Gunathunga sag...@wso2.comwrote: Please find POM restructuring guidelines in addition to things we discussed during today's meeting. 1. Top level POM file is the 'parent POM' for your project and there is no real requirement to have separate Maven module to host parent POM file. 2. Eliminate POM files available on 'component' , 'service-stub' and 'features' directories as there is no gain from them instead directly call real Maven modules from parent pom file ( REF - [1] ) e.g - modules moduleservice-stubs/service-mgt/module moduleservice-stubs/webapp-mgt/module modulecomponents/service-mgt/module modulecomponents/webapp-mgt/module modulefeatures/as-runtimes/module modulefeatures/service-mgt/module modulefeatures/webapp-mgt/module /modules [ You can keep same directory structure to enhance human readability ] 3. You must have a dependencyManagementsection on parent POM and should define all your project dependencies along with versions. ( REF - [1] ) 5. You CAN'T have dependencyManagement sections on any other POM file other than parent POM. 6. In each submodule make sure you have Maven dependencies WITHOUT versions ( REF - [2] ) e.g -dependency groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2/artifactId /dependency When you introduce a new Maven dependency define it's version under dependencyManagement section of parent POM file. 7. Make sure you have defined following repositories and plugin repositories on parent POM file. These will be used to drag SNAPSHOT versions of other carbon projects which used as dependencies of your project. repositories repository idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository repository idwso2.snapshots/id nameApache Snapshot Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/snapshots//url snapshots enabledtrue/enabled updatePolicydaily/updatePolicy /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idwso2.releases/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/repositories/releases//url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /pluginRepository pluginRepository
Re: [Dev] Bamboo Build Failed Error occurred while running Task 'Checkout Default Repository(1)'
Hi, This is fixed[1] [1] http://wso2.org/bamboo/browse/WSJ001-SCJ002-267 On Tue, Feb 11, 2014 at 6:10 PM, Madhuka Udantha madh...@wso2.com wrote: Hi, $subject was occurring, with error of *Error occurred while running Task 'Checkout Default Repository(1)' of type com.atlassian.bamboo.plugins.vcs:task.vcs.checkout.* *(java.lang.RuntimeException : com.atlassian.bamboo.repository.RepositoryException: WSJ001-SCJ002-JOB1-266: Checkout to revision 6b7e98ae06c4a92358f7c7c0636b5d58d865a408 has failed.Creating directories for /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSJ001-SCJ002-JOB1/.git failed)* *(11 Feb 2014, 4:44:03 AM, Agents: WSO2JAGGERY)* Full log can be found in here[1], Thanks [1] http://wso2.org/bamboo/browse/WSJ001-SCJ002-JOB1-266/log -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] Writing a Jaggery Client for secured REST Resource
Hi Sudheera, To call REST service you can try Http Client define in jaggery, You can fine sample codes in jaggery documentation as well. - get()[1] - post() [2] - put() [3] - del() [4] Thanks [1] http://jaggeryjs.org/apidocs/get.jag [2] http://jaggeryjs.org/apidocs/post.jag [3] http://jaggeryjs.org/apidocs/put.jag [4] http://jaggeryjs.org/apidocs/del.jag On Tue, Jan 21, 2014 at 9:47 AM, Sudheera Palihakkara sudhe...@wso2.comwrote: Hi, Thank you for the reply. Can we use the WSRequest object to invoke a REST resource defined in DSS? I have followed this blog post so far[1], and using http GET, POST, DELETE etc methods to invoke the REST resources. [1] http://blog.samisa.org/2014/01/rest-in-json-with-wso2-data-services.html thanks. On Mon, Jan 20, 2014 at 6:33 PM, Ruchira Wageesha ruch...@wso2.comwrote: You can invoke the secured service using WSRequest object of Jaggery. Please refer the doc at [1]. Several sections of the article [2](written for mashup server), would also be helpful. /Ruchira [1] http://jaggeryjs.org/apidocs/ws.jag [2] http://ruchirawageesha.blogspot.com/2011/12/blog-post.html On Mon, Jan 20, 2014 at 4:06 PM, Sudheera Palihakkara sudhe...@wso2.comwrote: Hi, I have exposed a data service as a *REST* resource and coded a *Jaggery*client for the service. Now I want to secure this service, using DSS I have already secured the service with *Username Token* implementation, but I have no idea how to write a *Jaggery* client to go along with it. Is there are any documentation or blog posts written on this? Thank you. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] Writing a Jaggery Client for secured REST Resource
Hi Sudheera. you can pass token as header or data[1] depending on your BE service is expect. get(url[, data][, headers][, type][, success(data, xhr)]) [1] http://jaggeryjs.org/apidocs/get.jag On Tue, Jan 21, 2014 at 10:22 AM, Sudheera Palihakkara sudhe...@wso2.comwrote: Hi madhuka, Yeah I'm referring to those, But I couldn't find any documentation about how to send the security parameters with the request. For example I have secured my data service with UsernameToken method[1], so in oder to invoke the service I have to send the username and the password with the request. How to send those parameters with jaggery GET or POST methods? [1] http://docs.wso2.org/display/DSS311/Security+Implementation#SecurityImplementation-1UsernameToken thank you all. :) On Tue, Jan 21, 2014 at 10:13 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Sudheera, To call REST service you can try Http Client define in jaggery, You can fine sample codes in jaggery documentation as well. - get()[1] - post() [2] - put() [3] - del() [4] Thanks [1] http://jaggeryjs.org/apidocs/get.jag [2] http://jaggeryjs.org/apidocs/post.jag [3] http://jaggeryjs.org/apidocs/put.jag [4] http://jaggeryjs.org/apidocs/del.jag On Tue, Jan 21, 2014 at 9:47 AM, Sudheera Palihakkara sudhe...@wso2.comwrote: Hi, Thank you for the reply. Can we use the WSRequest object to invoke a REST resource defined in DSS? I have followed this blog post so far[1], and using http GET, POST, DELETE etc methods to invoke the REST resources. [1] http://blog.samisa.org/2014/01/rest-in-json-with-wso2-data-services.html thanks. On Mon, Jan 20, 2014 at 6:33 PM, Ruchira Wageesha ruch...@wso2.comwrote: You can invoke the secured service using WSRequest object of Jaggery. Please refer the doc at [1]. Several sections of the article [2](written for mashup server), would also be helpful. /Ruchira [1] http://jaggeryjs.org/apidocs/ws.jag [2] http://ruchirawageesha.blogspot.com/2011/12/blog-post.html On Mon, Jan 20, 2014 at 4:06 PM, Sudheera Palihakkara sudhe...@wso2.com wrote: Hi, I have exposed a data service as a *REST* resource and coded a *Jaggery* client for the service. Now I want to secure this service, using DSS I have already secured the service with *Username Token*implementation, but I have no idea how to write a *Jaggery* client to go along with it. Is there are any documentation or blog posts written on this? Thank you. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] Writing a Jaggery Client for secured REST Resource
Hi, Samisa On Tue, Jan 21, 2014 at 11:19 AM, Samisa Abeysinghe sam...@wso2.com wrote: Do we have a sample around this? We do not have specific sample for this $subject But post()[1] 'try it' jaggery sample code used simple rest services in[2]. We need one! Yap, some thing we have do. Thanks [1] http://jaggeryjs.org/apidocs/post.jag [2] http://jaggeryjs.org/apidocs/resources/data.jag Thanks, Samisa... Samisa Abeysinghe Vice President Developer Evangelism WSO2 Inc. http://wso2.com On Tue, Jan 21, 2014 at 10:43 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Sudheera. you can pass token as header or data[1] depending on your BE service is expect. get(url[, data][, headers][, type][, success(data, xhr)]) [1] http://jaggeryjs.org/apidocs/get.jag On Tue, Jan 21, 2014 at 10:22 AM, Sudheera Palihakkara sudhe...@wso2.com wrote: Hi madhuka, Yeah I'm referring to those, But I couldn't find any documentation about how to send the security parameters with the request. For example I have secured my data service with UsernameToken method[1], so in oder to invoke the service I have to send the username and the password with the request. How to send those parameters with jaggery GET or POST methods? [1] http://docs.wso2.org/display/DSS311/Security+Implementation#SecurityImplementation-1UsernameToken thank you all. :) On Tue, Jan 21, 2014 at 10:13 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Sudheera, To call REST service you can try Http Client define in jaggery, You can fine sample codes in jaggery documentation as well. - get()[1] - post() [2] - put() [3] - del() [4] Thanks [1] http://jaggeryjs.org/apidocs/get.jag [2] http://jaggeryjs.org/apidocs/post.jag [3] http://jaggeryjs.org/apidocs/put.jag [4] http://jaggeryjs.org/apidocs/del.jag On Tue, Jan 21, 2014 at 9:47 AM, Sudheera Palihakkara sudhe...@wso2.com wrote: Hi, Thank you for the reply. Can we use the WSRequest object to invoke a REST resource defined in DSS? I have followed this blog post so far[1], and using http GET, POST, DELETE etc methods to invoke the REST resources. [1] http://blog.samisa.org/2014/01/rest-in-json-with-wso2-data-services.html thanks. On Mon, Jan 20, 2014 at 6:33 PM, Ruchira Wageesha ruch...@wso2.comwrote: You can invoke the secured service using WSRequest object of Jaggery. Please refer the doc at [1]. Several sections of the article [2](written for mashup server), would also be helpful. /Ruchira [1] http://jaggeryjs.org/apidocs/ws.jag [2] http://ruchirawageesha.blogspot.com/2011/12/blog-post.html On Mon, Jan 20, 2014 at 4:06 PM, Sudheera Palihakkara sudhe...@wso2.com wrote: Hi, I have exposed a data service as a *REST* resource and coded a *Jaggery* client for the service. Now I want to secure this service, using DSS I have already secured the service with *Username Token* implementation, but I have no idea how to write a *Jaggery*client to go along with it. Is there are any documentation or blog posts written on this? Thank you. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev][jaggery]
)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
[2014-01-13 16:58:14,777] ERROR {JAGGERY.WSjaggeryTest:jag} -
JavaException: org.jaggeryjs.scriptengine.exceptions.ScriptException:
Error occured while invoking the service
I followed the above references. And this error comes when I invoke a fire
and forget like operations.
Thanx
On Mon, Jan 13, 2014 at 4:42 PM, Madhuka Udantha madh...@wso2.com wrote:
Hi Iroshan,
Can you give full error trace (/log)?
Here[1,2] are references for WSRequest
[1]
http://madhukaudantha.blogspot.com/2013/02/invoke-web-service-with-jaggery-with.html
[2] http://jaggeryjs.org/apidocs/ws.jag
On Thu, Jan 9, 2014 at 11:15 AM, Iroshan Wickramarathna iros...@wso2.com
wrote:
Hi all,
I'm trying to invoke a data service using a simple jaggery app. When I
invoke a operation which doesn't give any result. it gives an error.
Ex. trying to invoke a insert drink operation
function invokeinsertDrink() {
var log = new Log();
var ws = require(ws);
var CSDS = new ws.WSRequest();
var options = new Array();
options.useSOAP = 1.2;
options.action = urn:insert_drink_operation;
var payload =' p:insert_drink_operation xmlns:p=
http://ws.wso2.org/dataservice;xs:id xmlns:xs=
http://ws.wso2.org/dataservice;3/xs:idxs:name xmlns:xs=
http://ws.wso2.org/dataservice;cococola/xs:name xs:cost xmlns:xs=
http://ws.wso2.org/dataservice
50/xs:cost/p:insert_drink_operation';
var result;
try {
CSDS.open(options,
https://10.100.4.53:9443/services/CofeeShopService/;, false);
CSDS.send(payload);
result = CSDS;
} catch (e) {
log.error(e.toString());
return e.toString();
}
return result.responseText;
}
print(invokeinsertDrink());
}
Even though data has been added to the data base properly it gives
following error.
JavaException: org.jaggeryjs.scriptengine.exceptions.ScriptException:
Error occured while invoking the service
how can I handle this error?
--
Thanx.
Ujitha Iroshan
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
--
Thanx.
Ujitha Iroshan
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery post() is not working when the response is empty.
] INFO
{org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port
: 9443
[2014-01-14 18:50:09,180] INFO
{org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port
: 9763
[2014-01-14 18:50:09,553] INFO
{org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
service:jmx:rmi://localhost:1/jndi/rmi://localhost:/jmxrmi
[2014-01-14 18:50:09,554] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server
: Jaggery Runtime-0.9.0.ALPHA4.wso2v1
[2014-01-14 18:50:09,554] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
Carbon started in 10 sec
[2014-01-14 18:50:09,699] INFO
{org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
: https://10.227.55.140:9443/admin/carbon/
[2014-01-14 18:51:42,826] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2014-01-14 18:51:42,825+0530]
from IP address 10.227.55.140
[1] https://github.com/wso2/jaggery/tree/0.9.0.ALPHA4.wso2v1
[2] https://wso2.org/jira/browse/JAGGERY-359
On Tue, Jan 14, 2014 at 5:28 PM, Pradeep Fernando prad...@wso2.com wrote:
[2014-01-14 17:08:44,299] ERROR
{org.jaggeryjs.jaggery.core.manager.ModuleManager} - Error while adding
HostObject : XMLHttpRequest
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject
java.lang.ClassNotFoundException:
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
On Tue, Jan 14, 2014 at 5:14 PM, Pradeep Fernando prad...@wso2.comwrote:
Hi madhuka,
Little problem. The server doesnt even starts with the patch.. :) may be
a version issue. (?)
java.lang.ClassNotFoundException:
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
On Tue, Jan 14, 2014 at 9:30 AM, Madhuka Udantha madh...@wso2.comwrote:
Hi Pradeep,
Your issue is fixed my last sending patched(Attaching here as well),
here I am sending sample app (json type) that matches for your requirement.
The type, which the response is expected. Allowed types are json, xml
or text[1].
[1] http://jaggeryjs.org/apidocs/post.jag
On Mon, Jan 13, 2014 at 10:42 AM, Madhuka Udantha madh...@wso2.comwrote:
Hi Pradeep,
Can you check provided patched, with sample jag file(app).
On Mon, Jan 13, 2014 at 9:44 AM, Pradeep Fernando prad...@wso2.comwrote:
Hi,
Observed the $subject. (NPE) Madhuka is working on it to fix it. Hope
this is not a spec violation. The same thing worked fine with
curl/google-rest client.
--Pradeep
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
--
*Pradeep Fernando*
Associate Technical Lead;WSO2 Inc.; http://wso2.com
blog: http://pradeepfernando.blogspot.com
m: +94776603662
--
*Pradeep Fernando*
Associate Technical Lead;WSO2 Inc.; http://wso2.com
blog: http://pradeepfernando.blogspot.com
m: +94776603662
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
org.jaggeryjs.hostobjects.xhr_0.9.0.ALPHA4_wso2v1.jar
Description: application/java-archive
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery post() is not working when the response is empty.
On Tue, Jan 14, 2014 at 5:14 PM, Pradeep Fernando prad...@wso2.com wrote: Hi madhuka, Little problem. The server doesnt even starts with the patch.. :) may be a version issue. (?) Most of time could version problem, Any way I commit this jaggery master by now, you can verify on there. BTW I have sent org.jaggeryjs.hostobjects.xhr_0.9.0.ALPHA4_wso2v1.jar on version '0.9.0.ALPHA4_wso2v1' I tryed it on github branch[1]. [1] https://github.com/wso2/jaggery/tree/0.9.0.ALPHA4.wso2v1 . java.lang.ClassNotFoundException: org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) On Tue, Jan 14, 2014 at 9:30 AM, Madhuka Udantha madh...@wso2.com wrote: Hi Pradeep, Your issue is fixed my last sending patched(Attaching here as well), here I am sending sample app (json type) that matches for your requirement. The type, which the response is expected. Allowed types are json, xml or text[1]. [1] http://jaggeryjs.org/apidocs/post.jag On Mon, Jan 13, 2014 at 10:42 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Pradeep, Can you check provided patched, with sample jag file(app). On Mon, Jan 13, 2014 at 9:44 AM, Pradeep Fernando prad...@wso2.comwrote: Hi, Observed the $subject. (NPE) Madhuka is working on it to fix it. Hope this is not a spec violation. The same thing worked fine with curl/google-rest client. --Pradeep -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Pradeep Fernando* Associate Technical Lead;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev][jaggery]
Hi Iroshan,
Can you give full error trace (/log)?
Here[1,2] are references for WSRequest
[1]
http://madhukaudantha.blogspot.com/2013/02/invoke-web-service-with-jaggery-with.html
[2] http://jaggeryjs.org/apidocs/ws.jag
On Thu, Jan 9, 2014 at 11:15 AM, Iroshan Wickramarathna iros...@wso2.comwrote:
Hi all,
I'm trying to invoke a data service using a simple jaggery app. When I
invoke a operation which doesn't give any result. it gives an error.
Ex. trying to invoke a insert drink operation
function invokeinsertDrink() {
var log = new Log();
var ws = require(ws);
var CSDS = new ws.WSRequest();
var options = new Array();
options.useSOAP = 1.2;
options.action = urn:insert_drink_operation;
var payload =' p:insert_drink_operation xmlns:p=
http://ws.wso2.org/dataservice;xs:id xmlns:xs=
http://ws.wso2.org/dataservice;3/xs:idxs:name xmlns:xs=
http://ws.wso2.org/dataservice;cococola/xs:name xs:cost xmlns:xs=
http://ws.wso2.org/dataservice;50/xs:cost/p:insert_drink_operation';
var result;
try {
CSDS.open(options,
https://10.100.4.53:9443/services/CofeeShopService/;, false);
CSDS.send(payload);
result = CSDS;
} catch (e) {
log.error(e.toString());
return e.toString();
}
return result.responseText;
}
print(invokeinsertDrink());
}
Even though data has been added to the data base properly it gives
following error.
JavaException: org.jaggeryjs.scriptengine.exceptions.ScriptException:
Error occured while invoking the service
how can I handle this error?
--
Thanx.
Ujitha Iroshan
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery post() is not working when the response is empty.
Hi Pradeep, Can you check provided patched, with sample jag file(app). On Mon, Jan 13, 2014 at 9:44 AM, Pradeep Fernando prad...@wso2.com wrote: Hi, Observed the $subject. (NPE) Madhuka is working on it to fix it. Hope this is not a spec violation. The same thing worked fine with curl/google-rest client. --Pradeep -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [UES-468] Carbon automation core gives error UES
Hi,
When UES master[1] ingratiating with UI test[2] in wso2.carbon.automation
it run UI test with passing test. After test execution finished, below
exception is throwing.
[2013-12-13 12:24:39,199] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2013-12-13 12:24:39,098] INFO
{org.apache.axis2.transport.tcp.TCPTransportSender} - TCP Sende
r Shutdown
[2013-12-13 12:24:39,200] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2013-12-13 12:24:39,102] ERROR
{org.wso2.carbon.core.init.CarbonServerManager} - Failed to Un-
register Servlets
[2013-12-13 12:24:39,206] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
java.lang.NullPointerException
[2013-12-13 12:24:39,206] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.webapp.mgt.WebApplication.lazyUnload(WebApplication.java:358)
[2013-12-13 12:24:39,206] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.webapp.mgt.WebApplication.lazyUnload(WebApplication.java:354)
[2013-12-13 12:24:39,207] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.lazyUnload(TomcatGenericWebap
psDeployer.java:379)
[2013-12-13 12:24:39,207] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.cleanup(AbstractWebappDeployer.java
:259)
[2013-12-13 12:24:39,208] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.apache.axis2.deployment.DeploymentEngine.cleanup(DeploymentEngine.java:1386)
[2013-12-13 12:24:39,208] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.core.CarbonAxisConfigurator.cleanup(CarbonAxisConfigurator.java:449)
[2013-12-13 12:24:39,208] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.apache.axis2.engine.AxisConfiguration.cleanup(AxisConfiguration.java:1438)
[2013-12-13 12:24:39,209] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.apache.axis2.context.ConfigurationContext.terminate(ConfigurationContext.java:788
)
[2013-12-13 12:24:39,209] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.apache.axis2.transport.http.AxisServlet.destroy(AxisServlet.java:528)
[2013-12-13 12:24:39,209] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.destroy(ServletRegistra
tion.java:38)
[2013-12-13 12:24:39,209] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.unregister(ProxyServlet.java:1
53)
[2013-12-13 12:24:39,210] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.eclipse.equinox.http.servlet.internal.HttpServiceImpl.unregister(HttpServiceImpl.
java:88)
[2013-12-13 12:24:39,210] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.core.init.CarbonServerManager.stop(CarbonServerManager.java:925)
[2013-12-13 12:24:39,210] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.deactivate(CarbonCoreService
Component.java:82)
[1] https://github.com/wso2/ues
[2] https://wso2.org/jira/browse/UES-468
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [UES-468] Carbon automation core gives error UES
Thanks Nuwan for the point.
I will follow it.
On Fri, Dec 13, 2013 at 2:51 PM, Nuwan Wimalasekara nuw...@wso2.com wrote:
Hi maduka,
As the log, the exception throws from the UES when shutting down the
server. Test framework core does only calling the server shutting down
service after the tests. Then it prints the logs of what UES server console
prints. so we need to test the UES shutting down manually an make sure
that it is working without any error logs. if it works fine, We need to
look the test flow of the UES test cases to identify which test case makes
server unstable.
Thanks,
Nuwanw
On Fri, Dec 13, 2013 at 2:15 PM, Madhuka Udantha madh...@wso2.com wrote:
Hi,
When UES master[1] ingratiating with UI test[2] in wso2.carbon.automation
it run UI test with passing test. After test execution finished, below
exception is throwing.
[2013-12-13 12:24:39,199] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2013-12-13 12:24:39,098] INFO
{org.apache.axis2.transport.tcp.TCPTransportSender} - TCP Sende
r Shutdown
[2013-12-13 12:24:39,200] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2013-12-13 12:24:39,102] ERROR
{org.wso2.carbon.core.init.CarbonServerManager} - Failed to Un-
register Servlets
[2013-12-13 12:24:39,206] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
java.lang.NullPointerException
[2013-12-13 12:24:39,206] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.webapp.mgt.WebApplication.lazyUnload(WebApplication.java:358)
[2013-12-13 12:24:39,206] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.webapp.mgt.WebApplication.lazyUnload(WebApplication.java:354)
[2013-12-13 12:24:39,207] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.lazyUnload(TomcatGenericWebap
psDeployer.java:379)
[2013-12-13 12:24:39,207] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.cleanup(AbstractWebappDeployer.java
:259)
[2013-12-13 12:24:39,208] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.apache.axis2.deployment.DeploymentEngine.cleanup(DeploymentEngine.java:1386)
[2013-12-13 12:24:39,208] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.core.CarbonAxisConfigurator.cleanup(CarbonAxisConfigurator.java:449)
[2013-12-13 12:24:39,208] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.apache.axis2.engine.AxisConfiguration.cleanup(AxisConfiguration.java:1438)
[2013-12-13 12:24:39,209] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.apache.axis2.context.ConfigurationContext.terminate(ConfigurationContext.java:788
)
[2013-12-13 12:24:39,209] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.apache.axis2.transport.http.AxisServlet.destroy(AxisServlet.java:528)
[2013-12-13 12:24:39,209] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.destroy(ServletRegistra
tion.java:38)
[2013-12-13 12:24:39,209] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.unregister(ProxyServlet.java:1
53)
[2013-12-13 12:24:39,210] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.eclipse.equinox.http.servlet.internal.HttpServiceImpl.unregister(HttpServiceImpl.
java:88)
[2013-12-13 12:24:39,210] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.core.init.CarbonServerManager.stop(CarbonServerManager.java:925)
[2013-12-13 12:24:39,210] INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.deactivate(CarbonCoreService
Component.java:82)
[1] https://github.com/wso2/ues
[2] https://wso2.org/jira/browse/UES-468
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http
Re: [Dev] Missing Patch in kernel/4.2.0/patches/patch0001/ regard to 'CARBON-14500'
Hi, Manoj
I have attached patch[2] in jira[1] created for kernel patch 0004. pls
added to kernel.
When you add it let us know.
Thanks
[1] https://wso2.org/jira/browse/CARBON-14602
[2]
https://wso2.org/jira/secure/attachment/29719/RegistryKeyStore-Patch0004.patch
On Wed, Dec 4, 2013 at 6:09 PM, Madhuka Udantha madh...@wso2.com wrote:
On Wed, Dec 4, 2013 at 2:00 PM, Manoj Kumara ma...@wso2.com wrote:
Hi Madhuka,
Can you please re create the patch for kernel patch0003 so I can apply
this.
I will build patch for kernel patch0003,
I will pass it you.
Thanks,
Manoj
Best Regards..
Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com
Twitter: http://twitter.com/ManKuma
Mobile: +94713448188
On Wed, Dec 4, 2013 at 1:17 PM, Madhuka Udantha madh...@wso2.com wrote:
Hi,
Here I am reopening jira[1], was build for email thread[5] as there is
need[2] of this patch and it is not committed/or missing in[3]
Jira one have diff[6], added to kernel.
Since this was not committed to [3] and missing in kernel through it is
in[4].
@carbon team: Pls added this patch to kernel soon.
[1] https://wso2.org/jira/browse/CARBON-14500
[2] Email Subjected: Encrypting Confidential Data In the Platform { was:
Re: (QSPPROD-22) [CSI Piemonte] How to Decrypt Already Encrypted Values and
Re-encrypt using different certificate}
[3]
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0001/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/RegistryResources.java
[4]
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core-old/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/RegistryResources.java
[5] Email Subjected: 'Support commits missing in public SVN'
from:prab...@wso2.com
[6] https://wso2.org/jira/secure/attachment/28460/RegistryKeyStore.patch
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Jaggery Test Framework is ready to Test
Hi, Jaggery Test frame work[1] currently built (RC1 - [5]) and p2 features[2] also completed, Still in git local. We will added it wso2 github soon. Now you all are welcome to test your jaggery unit test coding with it. (Sample test app can be found in[1,2] and documentation can be found in[4,2:wiki]). You can suggest a name for jaggery test framework in email thread [subjected to: Name for Jaggery Test Framework] *@ strategy-group*. It contains, *Task* *JAGGERY-324 https://wso2.org/jira/browse/JAGGERY-324* Define Test Engine for jaggery *JAGGERY-325 https://wso2.org/jira/browse/JAGGERY-325* Front End Controller for Test Module/Testuits/TestSpecs to be handle *JAGGERY-326 https://wso2.org/jira/browse/JAGGERY-326* JSON report for Engine *JAGGERY-333 https://wso2.org/jira/browse/JAGGERY-333* Simple Wiki Documentation *Improvement* *JAGGERY-332 https://wso2.org/jira/browse/JAGGERY-332* File structure and URL pattern Inter Connection *JAGGERY-337 https://wso2.org/jira/browse/JAGGERY-337* Composite Reporter (JSON/HTML) *JAGGERY-334 https://wso2.org/jira/browse/JAGGERY-334* URL ID rather than 'test Spec name' *JAGGERY-335 https://wso2.org/jira/browse/JAGGERY-335* Simplify execute.jag *JAGGERY-340 https://wso2.org/jira/browse/JAGGERY-340* ListSpecs Suits *JAGGERY-342 https://wso2.org/jira/browse/JAGGERY-342* Report neeed only it results of request *JAGGERY-341 https://wso2.org/jira/browse/JAGGERY-341* setForFullName for the name of test for identifies *JAGGERY-328 https://wso2.org/jira/browse/JAGGERY-328* RESTful API (JSON) for Automation test framework to Intrgrate *JAGGERY-336 https://wso2.org/jira/browse/JAGGERY-336* Listing End points (test File URLs) *JAGGERY-327 https://wso2.org/jira/browse/JAGGERY-327* HTML reporter Engine *JAGGERY-330 https://wso2.org/jira/browse/JAGGERY-330* Sample with jaggery test framework *JAGGERY-329 https://wso2.org/jira/browse/JAGGERY-329* Development of framework with few sample testing (One module in ES) *JAGGERY-331 https://wso2.org/jira/browse/JAGGERY-331* Testing Syntax to be Test *Bug* *JAGGERY-347 https://wso2.org/jira/browse/JAGGERY-347* If there is no test items (assert) in test user to inform it. *JAGGERY-348 https://wso2.org/jira/browse/JAGGERY-348* Handling empty testSuite *JAGGERY-343 https://wso2.org/jira/browse/JAGGERY-343* Top checked box is used to 'selectAll' and 'deSelectAll' rather buttons *JAGGERY-346 https://wso2.org/jira/browse/JAGGERY-346* Grouping test Suite with testSpec name label level *JAGGERY-344 https://wso2.org/jira/browse/JAGGERY-344* In summary report will have total test count, selected count, pass and fail counts *JAGGERY-349 https://wso2.org/jira/browse/JAGGERY-349* Error message Handling for testSpec *JAGGERY-351 https://wso2.org/jira/browse/JAGGERY-351* removed . in passed or failed label in test *JAGGERY-353 https://wso2.org/jira/browse/JAGGERY-353* Adding identifiable for error failure in test assert message *JAGGERY-354 https://wso2.org/jira/browse/JAGGERY-354* TMP files (linux) and etc file support for crawling features in test framework *JAGGERY-338 https://wso2.org/jira/browse/JAGGERY-338* Bringing Finalizing log to reporter *JAGGERY-350 https://wso2.org/jira/browse/JAGGERY-350* adding Wrong files in name in test spec files in test *JAGGERY-352 https://wso2.org/jira/browse/JAGGERY-352* Bring down select count in UI (Under the select Button) If you encounter some bugs or feature limitations/improvements, you can report those in here[3]. Thanks *References * [1] https://github.com/Madhuka/jaggery-test-framewrok/branches [2] https://github.com/Madhuka/jaggery-test-framewrok/branches [3] https://wso2.org/jira/browse/JAGGERY/component/11521 [4] http://madhukaudantha.blogspot.com/search/label/Test%20Framework [5] https://github.com/Madhuka/jaggery-test-framewrok/tree/rc1 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery - How to process a SOAP request
Hi, Nuwan Yap, trying is correct, Jaggery Web hostobject had bug regard to 'request.getContent()' and it is be fixed in github master. Thinking you try some old jaggery version. Here I will attaching patch (0.9.0.ALPHA4_wso2v1) for you and sample jaggery file for you to test. On Tue, Dec 10, 2013 at 8:30 PM, Nuwan Dias nuw...@wso2.com wrote: Hi, I have a restful jaggery endpoint and I now want to make this serve SOAP requests as well. My idea is to look at the Content-Type header and determine whether the request is REST or SOAP. I need to know how I can process a SOAP request from jaggery. When I try 'request.getContent()', it gives me a null value. Yap, it was bug in jaggery. It is fixed. Try this and let us know. Thanks Is there a way to process a SOAP Body from jaggery? Thanks, NuwanD. -- Nuwan Dias Senior Software Engineer - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ org.jaggeryjs.hostobjects.web_0.9.0.ALPHA4_wso2v1.jar Description: application/java-archive index.jag Description: Binary data ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Integration test failure EmailHostObjectTestCase
Hi Supun, Which jaggery version your using in here (In above AS)? And you testing files reagrd to jaggery are external form git jaggery branch? or SVN (non git externals) On Wed, Dec 4, 2013 at 2:27 PM, Supun Malinga sup...@wso2.com wrote: Hi Madhuka, Can you have a look pls. Error [1] [1] http://ec2-54-205-250-106.compute-1.amazonaws.com/chunk-05/03-12-2013/surefire-reports/#testEmailJaggery thanks, -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Integration test failure EmailHostObjectTestCase
Hi, AS having there own testApp (jaggery app) zip that was created from Git (not external). Git hub change will not effect on those AS intgration tests. Checked the issue in AS new pack, in local (supunM also) It was working fine. Email host object and email test case have no error and issues. As it was not return value from 'email.jag' in ec2 as it not able able to send email in EC2 in this particular instance. (You can check EC2 for allowing email to send on applicationss or you can skip the email test in EC2, but cover it in smoke email test. etc.) Thanks On Wed, Dec 4, 2013 at 2:46 PM, Supun Malinga sup...@wso2.com wrote: Hi, Jaggery version, : 0.9.0.ALPHA4.wso2v1. This is the 4.2.0 released version AFAIK. thanks, On Wed, Dec 4, 2013 at 2:38 PM, Madhuka Udantha madh...@wso2.com wrote: Hi Supun, Which jaggery version your using in here (In above AS)? And you testing files reagrd to jaggery are external form git jaggery branch? or SVN (non git externals) On Wed, Dec 4, 2013 at 2:27 PM, Supun Malinga sup...@wso2.com wrote: Hi Madhuka, Can you have a look pls. Error [1] [1] http://ec2-54-205-250-106.compute-1.amazonaws.com/chunk-05/03-12-2013/surefire-reports/#testEmailJaggery thanks, -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] wso2ues-1.0.1 pack does not contain/appear User Management
Hi, Dimuthu UES/jaggery have 'org.wso2.carbon.user.api' and 'org.wso2.carbon.user.core' bundle not the UI bundle. You can't see that 'user and role' in carbon management console as you have not install those UI bundles. When you install those UI bundle you can see that menu and UI. (org.wso2.carbon.user.mgt.ui) Since we need only back end API for our user management module we have them not the UI. If any one need to view/see 'user and roles' in carbon management console can install features 'org.wso2.carbon.user.mgt.feature' for it. Here sample steps for 'WSO2 User Engagement Server with RXT view in management console'[1], same thing you have to do for the above ui bundles that you need. [1] http://madhukaudantha.blogspot.com/2013/08/wso2-ues-with-rxt-view-in-management.html Thanks On Wed, Nov 27, 2013 at 2:04 PM, Dimuthu De Lanerolle dimut...@wso2.comwrote: Hi, We are in the process of implementing some UI automation tests for UES. We noted that wso2ues-1.0.1.zip pack does not contain/appear User Management (Users and Roles) under the configure tab in the management console.AFAIK we need to ship this with every product. Is there any valid reason for this? Regards -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Developer Studio 3.3.0 Alpha 3 Released!
/browse/TOOLS-2080] - Code Assistance doc for built-ins methods Wish - [TOOLS-1916 https://wso2.org/jira/browse/TOOLS-1916] - Out of the box IntelliJ support Your feedbacks are most welcome. Please report issues at [3] and specify the affect version as 3.3.0 Alpha 3. [1] http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.3.0/Alpha3/wso2-developer-studio_3.3.0.zip [2] http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.3.0/Alpha3/installed-distributions/ [3] https://wso2.org/jira/browse/TOOLS Thanks and Regards, WSO2 Developer Studio Team. -- *Asanka Sanjeewa* Senior Software Engineer Mobile: +94772532924 WSO2 Inc. http://wso2.com/ Blog: http://asanka-tech-blog.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Chintana Wilamuna Architect - Solution Architecture WSO2, Inc.; http://wso2.com lean.enterprise.middleware phone: +94 72 145 4545 blog: http://engwar.com/ photos: http://flickr.com/photos/chintana linkedin: http://www.linkedin.com/in/engwar twitter: twitter.com/std_err -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] Adding getUserListOfRole to the user-manager.js
Hi, Merged[1]. Thanks As there are some missing user management API in user-manager (user-manager.js), we will add those also in to there. [Adding 'd...@jaggeryjs.org' as it is about jaggery dev] [1] https://github.com/wso2/jaggery/pull/69 On Tue, Nov 19, 2013 at 4:51 PM, Gayan Dhanushka gay...@wso2.com wrote: Hi, Please merge the pull request of $subject. merge id is #69 https://github.com/wso2/jaggery/issues/69 Thanks GayanD Gayan Dhanuska Software Engineer http://wso2.com/ Lean Enterprise Middleware Mobile 071 666 2327 Office Tel : 94 11 214 5345 Fax : 94 11 214 5300 Twitter : https://twitter.com/gayanlggd -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [Jaggery] [Test] Test framework for jaggery
On Mon, Nov 18, 2013 at 2:55 PM, Dharshana Warusavitharana
dharsha...@wso2.com wrote:
Hi Madhuka/ Ruchira,
Currently we are working on a phase 2 of the automation framework which
will come up with the test case side extentions on testng listners.
So you might not want to reinvent the wheel in implementing this.
yes, had meeting with krishantha also $subject and it also updated in this
thread,
If there any new change happen for existing thing, let me know
Basically there is no JS (Server side scripting/jaggery) testing framework
in our platform so far,
But this $subject will have rest full interface for interact with existing
system.
It would be great if we can have a 5 min discussion on this.
Yap,
Thank You,
Dharshana.
On Mon, Nov 18, 2013 at 2:47 PM, Ruchira Wageesha ruch...@wso2.comwrote:
Hi Madhuka,
Have you come up to a conclusion? Are there any existing framework that
can be used without touching their code(probably jasmine)? If it needs we
can write a layer on top of that to make it compatible with Jaggery model.
Or, will you have to start something from scratch?
/Ruchira
On Sun, Nov 17, 2013 at 8:10 PM, Madhuka Udantha madh...@wso2.comwrote:
Here is requirement list for the $subject,
*Basic things that will be in $subject ( jaggery test framework)*
- Testing Jaggery (.jag) API with function levels (simple as unit
test) - online
- Jaggery module testing under application (app/{appName}/module)
- Changing to any test case then only the test case file needs to be
updated [Script will remain the same]
- Application-independent. Test resource/spec of test will be inside
the application (app/{appName}/test)
- Easy to expand, maintain, and perpetuate. (Try to follow same JS
frame work structure such as *jasmine[1] *)
- Supportable with automation test framework with some configure
changing/pom/ant
- Should have low cost on maintaining
- Easy to write test (less time)
- REST/JSON report Supporting (Console commanding not implemented,
As above discussion)
- HTML Test coverage reporting
*Scopes for Framework*
Application-oriented Framework, Test resources for application will be
inside application
*Test framework type*
It will be 'Hybrid' as It will be following (Script Modularity
Framework, Library Architecture Framework and Structured Framework will be
used in implementation)
*Responsibilities of $subject*
- Defining the format in which to express expectations
- Running the tests which exercise the public interface (REST
interfaces)
- Result with interface of JSON
- Interact with platform testing and build time with simple
interface (interface for REST client)
- Calling test suites and skipping test suit with changing test spec
(Test case js/jag )
- Executing the tests (Without console commanding)
- Reporting results of the test HTML interface also
If there I am missing any requirement for $subject, pls add it here,
Here is some more we will consider before writing $subject[2], Some
trying out existing JS test framework[3] for $subject for matter for
comparison and understating design on existing system.
[1] http://pivotal.github.io/jasmine/
[2]
http://madhukaudantha.blogspot.com/2013/11/what-to-be-know-about-test-framework.html
[3] http://madhukaudantha.blogspot.com/search/label/Test%20Framework
Thanks
On Fri, Nov 15, 2013 at 10:57 AM, Madhuka Udantha madh...@wso2.comwrote:
On Fri, Nov 15, 2013 at 10:30 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Functinalities like Server startup/shutdown, coverage generation and
result generation already implemented in WSO2 Test Automation framework.
So
we need to reuse those functionalities in here.
Yap, sure we will be reusing those.
Having a Rest API to call tests scripts embedded in each jaggery app
would be nice addition. In that way we could easily integrate it with our
existing framework and use though out the platform.
And this framework should support for continuous integration. So
everything have to be executed without human interactions. So avoiding
command line test runners etc.. is required.
We will have json/RESTful API for app developer to run the test rather
command line, (No command line (cmd/ jaggery console)). Therefore there
will be html (web interface for app developer to run his/her test in
easily). We will avoid command line testing and will provide web interface
testing.
Thanks
Thanks,
Krishantha
On Thu, Nov 14, 2013 at 11:02 PM, Madhuka Udantha madh...@wso2.comwrote:
On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayake uda...@wso2.comwrote:
Hi all,
While designing the test framework, its good if we can keep in mind
that jaggery2 product also underway.
Any thoughts?
Sure, will think.
Mainly test framework will coming for javascript(jag/js) testing so
it will be written where can be extended.
Regards
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
On Mon, Nov 18, 2013 at 2:40 PM, Ruchira Wageesha ruch...@wso2.com wrote:
Jaggery module testing under application (app/{appName}/module)
One of the hard part of testing javascript modules is that when we use
closure base privacy everything gets harder to test. Since those members
aren’t visible other than the js scope itself we might have to think about
our total approach to modules itself.
I don't think we need to address it as a part of the test framework
itself. Independent from the programming language, this kind of code smells
will be there in any code and will need a different framework such as
findbugs etc. to detect those things.
Yap, agreed to Ruchira comment
[1]
http://sidekicksrc.com/post/closures-for-classmodule-privacy-considered-harmful/
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
On Mon, Nov 18, 2013 at 2:47 PM, Ruchira Wageesha ruch...@wso2.com wrote:
Hi Madhuka,
Have you come up to a conclusion? Are there any existing framework that
can be used without touching their code(probably jasmine)?
Yap, most of time (95%) It will be jasmine.
I will be using existing framework (Jasmine 1.3.1 revision). While Jasmine
is going with MIT license It wan't be matter using in here. Any matter with
license?
will do some wrapping and upgrade which matching to our requirement.
[1] http://pivotal.github.io/jasmine/
[2] https://github.com/pivotal/jasmine
If it needs we can write a layer on top of that to make it compatible with
Jaggery model.
yap.
Or, will you have to start something from scratch?
No, As there are some existing JS test framework and people are familiarly
with all of them, and their syntax.
Therefore I think it is much better to go with existing one with upgrading
and wrapping it where it will cover all over requirements
/Ruchira
On Sun, Nov 17, 2013 at 8:10 PM, Madhuka Udantha madh...@wso2.com wrote:
Here is requirement list for the $subject,
*Basic things that will be in $subject ( jaggery test framework)*
- Testing Jaggery (.jag) API with function levels (simple as unit
test) - online
- Jaggery module testing under application (app/{appName}/module)
- Changing to any test case then only the test case file needs to be
updated [Script will remain the same]
- Application-independent. Test resource/spec of test will be inside
the application (app/{appName}/test)
- Easy to expand, maintain, and perpetuate. (Try to follow same JS
frame work structure such as *jasmine[1] *)
- Supportable with automation test framework with some configure
changing/pom/ant
- Should have low cost on maintaining
- Easy to write test (less time)
- REST/JSON report Supporting (Console commanding not implemented,
As above discussion)
- HTML Test coverage reporting
*Scopes for Framework*
Application-oriented Framework, Test resources for application will be
inside application
*Test framework type*
It will be 'Hybrid' as It will be following (Script Modularity Framework,
Library Architecture Framework and Structured Framework will be used in
implementation)
*Responsibilities of $subject*
- Defining the format in which to express expectations
- Running the tests which exercise the public interface (REST
interfaces)
- Result with interface of JSON
- Interact with platform testing and build time with simple interface
(interface for REST client)
- Calling test suites and skipping test suit with changing test spec
(Test case js/jag )
- Executing the tests (Without console commanding)
- Reporting results of the test HTML interface also
If there I am missing any requirement for $subject, pls add it here,
Here is some more we will consider before writing $subject[2], Some
trying out existing JS test framework[3] for $subject for matter for
comparison and understating design on existing system.
[1] http://pivotal.github.io/jasmine/
[2]
http://madhukaudantha.blogspot.com/2013/11/what-to-be-know-about-test-framework.html
[3] http://madhukaudantha.blogspot.com/search/label/Test%20Framework
Thanks
On Fri, Nov 15, 2013 at 10:57 AM, Madhuka Udantha madh...@wso2.comwrote:
On Fri, Nov 15, 2013 at 10:30 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Functinalities like Server startup/shutdown, coverage generation and
result generation already implemented in WSO2 Test Automation framework. So
we need to reuse those functionalities in here.
Yap, sure we will be reusing those.
Having a Rest API to call tests scripts embedded in each jaggery app
would be nice addition. In that way we could easily integrate it with our
existing framework and use though out the platform.
And this framework should support for continuous integration. So
everything have to be executed without human interactions. So avoiding
command line test runners etc.. is required.
We will have json/RESTful API for app developer to run the test rather
command line, (No command line (cmd/ jaggery console)). Therefore there
will be html (web interface for app developer to run his/her test in
easily). We will avoid command line testing and will provide web interface
testing.
Thanks
Thanks,
Krishantha
On Thu, Nov 14, 2013 at 11:02 PM, Madhuka Udantha madh...@wso2.comwrote:
On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayake uda...@wso2.comwrote:
Hi all,
While designing the test framework, its good if we can keep in mind
that jaggery2 product also underway.
Any thoughts?
Sure, will think.
Mainly test framework will coming for javascript(jag/js) testing so it
will be written where can be extended.
Regards,
UdaraR
On Thu, Nov 14, 2013 at 10:15 AM, Madhuka Udantha
madh...@wso2.comwrote:
Hi Krishantha and test automation team,
I would like
Re: [Dev] Package Management for Jaggery Front-end components
Hi, There is extensions repository for Jaggery[1] in WSO2 Github, where to checkin all jaggery extensions but still there is no extension to be found, So we can added those extenstion/tryout/modules in there such as repo for jaggery extension. (Extension has to be a p2 feature such as caramel[2],simple documentation with sample try out) [1] https://github.com/wso2/jaggery-extensions [2] https://github.com/wso2/caramel On Sun, Nov 17, 2013 at 1:13 PM, Chan duli...@wso2.com wrote: Hi all, Have we thought about the $subject? Bower.io [1] is a great example of front end package management. Too bad bower has a dependency over npm[2] and node[3]. [1] - http://bower.io/ [2] - http://npmjs.org/ [3] - http://nodejs.org/ *Peace~* --- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2mobile.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulithawijewantha.com http://dulithawijewantha.com/* * ~Blog blog.dulithawijewantha.com http://dulichan.github.io/chan/ * * ~Twitter @dulitharw https://twitter.com/dulitharw* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
Here is requirement list for the $subject,
*Basic things that will be in $subject ( jaggery test framework)*
- Testing Jaggery (.jag) API with function levels (simple as unit test)
- online
- Jaggery module testing under application (app/{appName}/module)
- Changing to any test case then only the test case file needs to be
updated [Script will remain the same]
- Application-independent. Test resource/spec of test will be inside the
application (app/{appName}/test)
- Easy to expand, maintain, and perpetuate. (Try to follow same JS frame
work structure such as *jasmine[1] *)
- Supportable with automation test framework with some configure
changing/pom/ant
- Should have low cost on maintaining
- Easy to write test (less time)
- REST/JSON report Supporting (Console commanding not implemented, As
above discussion)
- HTML Test coverage reporting
*Scopes for Framework*
Application-oriented Framework, Test resources for application will be
inside application
*Test framework type*
It will be 'Hybrid' as It will be following (Script Modularity Framework,
Library Architecture Framework and Structured Framework will be used in
implementation)
*Responsibilities of $subject*
- Defining the format in which to express expectations
- Running the tests which exercise the public interface (REST interfaces)
- Result with interface of JSON
- Interact with platform testing and build time with simple interface
(interface for REST client)
- Calling test suites and skipping test suit with changing test spec
(Test case js/jag )
- Executing the tests (Without console commanding)
- Reporting results of the test HTML interface also
If there I am missing any requirement for $subject, pls add it here,
Here is some more we will consider before writing $subject[2], Some trying
out existing JS test framework[3] for $subject for matter for comparison
and understating design on existing system.
[1] http://pivotal.github.io/jasmine/
[2]
http://madhukaudantha.blogspot.com/2013/11/what-to-be-know-about-test-framework.html
[3] http://madhukaudantha.blogspot.com/search/label/Test%20Framework
Thanks
On Fri, Nov 15, 2013 at 10:57 AM, Madhuka Udantha madh...@wso2.com wrote:
On Fri, Nov 15, 2013 at 10:30 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Functinalities like Server startup/shutdown, coverage generation and
result generation already implemented in WSO2 Test Automation framework. So
we need to reuse those functionalities in here.
Yap, sure we will be reusing those.
Having a Rest API to call tests scripts embedded in each jaggery app
would be nice addition. In that way we could easily integrate it with our
existing framework and use though out the platform.
And this framework should support for continuous integration. So
everything have to be executed without human interactions. So avoiding
command line test runners etc.. is required.
We will have json/RESTful API for app developer to run the test rather
command line, (No command line (cmd/ jaggery console)). Therefore there
will be html (web interface for app developer to run his/her test in
easily). We will avoid command line testing and will provide web interface
testing.
Thanks
Thanks,
Krishantha
On Thu, Nov 14, 2013 at 11:02 PM, Madhuka Udantha madh...@wso2.comwrote:
On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayake uda...@wso2.comwrote:
Hi all,
While designing the test framework, its good if we can keep in mind
that jaggery2 product also underway.
Any thoughts?
Sure, will think.
Mainly test framework will coming for javascript(jag/js) testing so it
will be written where can be extended.
Regards,
UdaraR
On Thu, Nov 14, 2013 at 10:15 AM, Madhuka Udantha madh...@wso2.comwrote:
Hi Krishantha and test automation team,
I would like to get your opinion on this task regard to
is there standard methodology on current testing framework where we
can added such testing framework or better to go on fully independent
model?
My thinking is,
- As it is application level testing frame work, better to work
with much independent of the current system
- Where application writer (developer) can run test for specific
application rather running all test for platform or product
- It will help to maintain both test framework with low cost
- Each test frame have it's own scope (such as
platform/product/appilcation). if not, complexity of the code and
system
will be increase but there will be API interface for interaction
among the
test framework.
- And I thought to have interface (simple REST interface) in
jaggery test frame work where current test framework also can interact
with
it into some extend.
Thanks
On Tue, Nov 12, 2013 at 5:57 PM, Madhuka Udantha madh...@wso2.comwrote:
Hi,
Still we do not have jaggery test framework even though
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
Hi Dulitha,
Please find inline comments in below,
On Mon, Nov 18, 2013 at 9:21 AM, Chan duli...@wso2.com wrote:
*Peace~*
---
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2Mobile
Lean.Enterprise.Mobileware
* ~Email duli...@wso2mobile.com duli...@wso2mobile.com*
* ~Mobile +94712112165 %2B94712112165*
* ~Website dulithawijewantha.com http://dulithawijewantha.com/*
* ~Blog blog.dulithawijewantha.com
http://dulichan.github.io/chan/*
* ~Twitter @dulitharw https://twitter.com/dulitharw*
On November 17, 2013 at 8:13:10 PM, Madhuka Udantha (madh...@wso2.com)
wrote:
Here is requirement list for the $subject,
*Basic things that will be in $subject ( jaggery test framework)*
- Testing Jaggery (.jag) API with function levels (simple as unit
test) - online
I believe you meant API’s via HTTP - Since Goose.js discourage usage of
.jag files to write APIs.
I means both HTTP level APIs as well as function APIs also
-
Jaggery module testing under application (app/{appName}/module)
One of the hard part of testing javascript modules is that when we use
closure base privacy everything gets harder to test.
Yap, some thing planing to cover up.
Since those members aren’t visible other than the js scope itself we might
have to think about our total approach to modules itself.
Testing framework will have consider scope different (js scope/etc..)
regard to testing. BTW js functionality test can be achieved with pure JS
test framework (Such as Jasmine).
In here Module testing refereed for application level modules.
- Changing to any test case then only the test case file needs to be
updated [Script will remain the same]
- Application-independent. Test resource/spec of test will be inside
the application (app/{appName}/test)
I think we need to implement a Jaggery App build process that will neatly
package a js app after testing and everything [http://yeoman.io/].
With interface of testing framework will allow to connect with building
process and executes app test while it is building.
This would allow us to strip away the test suits when going into
production.
Good point.
(To achieve this there can be some script or configuration to set at build
time)
Thanks for your feed back,
- Easy to expand, maintain, and perpetuate. (Try to follow same JS
frame work structure such as *jasmine[1] *)
- Supportable with automation test framework with some configure
changing/pom/ant
- Should have low cost on maintaining
- Easy to write test (less time)
- REST/JSON report Supporting (Console commanding not implemented,
As above discussion)
- HTML Test coverage reporting
*Scopes for Framework*
Application-oriented Framework, Test resources for application will be
inside application
*Test framework type*
It will be 'Hybrid' as It will be following (Script Modularity Framework,
Library Architecture Framework and Structured Framework will be used in
implementation)
*Responsibilities of $subject*
- Defining the format in which to express expectations
- Running the tests which exercise the public interface (REST
interfaces)
- Result with interface of JSON
- Interact with platform testing and build time with simple interface
(interface for REST client)
- Calling test suites and skipping test suit with changing test spec
(Test case js/jag )
- Executing the tests (Without console commanding)
- Reporting results of the test HTML interface also
If there I am missing any requirement for $subject, pls add it here,
Here is some more we will consider before writing $subject[2], Some trying
out existing JS test framework[3] for $subject for matter for comparison
and understating design on existing system.
[1] http://pivotal.github.io/jasmine/
[2]
http://madhukaudantha.blogspot.com/2013/11/what-to-be-know-about-test-framework.html
[3] http://madhukaudantha.blogspot.com/search/label/Test%20Framework
Thanks
On Fri, Nov 15, 2013 at 10:57 AM, Madhuka Udantha madh...@wso2.com
wrote:
On Fri, Nov 15, 2013 at 10:30 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Functinalities like Server startup/shutdown, coverage generation and
result generation already implemented in WSO2 Test Automation framework. So
we need to reuse those functionalities in here.
Yap, sure we will be reusing those.
Having a Rest API to call tests scripts embedded in each jaggery app
would be nice addition. In that way we could easily integrate it with our
existing framework and use though out the platform.
And this framework should support for continuous integration. So
everything have to be executed without human interactions. So avoiding
command line test runners etc.. is required.
We will have json/RESTful API for app developer to run the test rather
command line, (No command line (cmd/ jaggery console)). Therefore
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayake uda...@wso2.com wrote: Hi all, While designing the test framework, its good if we can keep in mind that jaggery2 product also underway. Any thoughts? Sure, will think. Mainly test framework will coming for javascript(jag/js) testing so it will be written where can be extended. Regards, UdaraR On Thu, Nov 14, 2013 at 10:15 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Krishantha and test automation team, I would like to get your opinion on this task regard to is there standard methodology on current testing framework where we can added such testing framework or better to go on fully independent model? My thinking is, - As it is application level testing frame work, better to work with much independent of the current system - Where application writer (developer) can run test for specific application rather running all test for platform or product - It will help to maintain both test framework with low cost - Each test frame have it's own scope (such as platform/product/appilcation). if not, complexity of the code and system will be increase but there will be API interface for interaction among the test framework. - And I thought to have interface (simple REST interface) in jaggery test frame work where current test framework also can interact with it into some extend. Thanks On Tue, Nov 12, 2013 at 5:57 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, Still we do not have jaggery test framework even though there are considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there is no JS testing framework under WSO2 Platform. Testing framework will be under application level such as mocha, jasmine. Test frame will be apply to (basically)test. - jaggery API (js functions and arguments ) - REST APIs that are expose under jaggery application - With test coverage reporting We will be evaluating existing JavaScript test frame works regard mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and jsunit[7] to $subject. All suggestions are welcome. [1] http://visionmedia.github.io/mocha/ [2] http://pivotal.github.io/jasmine/ [3] http://qunitjs.com/ [4] http://vowsjs.org/ [5] http://visionmedia.github.io/expresso/ [6] https://github.com/caolan/nodeunit [7] https://github.com/pivotal/jsunit Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
On Fri, Nov 15, 2013 at 10:30 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Functinalities like Server startup/shutdown, coverage generation and result generation already implemented in WSO2 Test Automation framework. So we need to reuse those functionalities in here. Yap, sure we will be reusing those. Having a Rest API to call tests scripts embedded in each jaggery app would be nice addition. In that way we could easily integrate it with our existing framework and use though out the platform. And this framework should support for continuous integration. So everything have to be executed without human interactions. So avoiding command line test runners etc.. is required. We will have json/RESTful API for app developer to run the test rather command line, (No command line (cmd/ jaggery console)). Therefore there will be html (web interface for app developer to run his/her test in easily). We will avoid command line testing and will provide web interface testing. Thanks Thanks, Krishantha On Thu, Nov 14, 2013 at 11:02 PM, Madhuka Udantha madh...@wso2.comwrote: On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayake uda...@wso2.comwrote: Hi all, While designing the test framework, its good if we can keep in mind that jaggery2 product also underway. Any thoughts? Sure, will think. Mainly test framework will coming for javascript(jag/js) testing so it will be written where can be extended. Regards, UdaraR On Thu, Nov 14, 2013 at 10:15 AM, Madhuka Udantha madh...@wso2.comwrote: Hi Krishantha and test automation team, I would like to get your opinion on this task regard to is there standard methodology on current testing framework where we can added such testing framework or better to go on fully independent model? My thinking is, - As it is application level testing frame work, better to work with much independent of the current system - Where application writer (developer) can run test for specific application rather running all test for platform or product - It will help to maintain both test framework with low cost - Each test frame have it's own scope (such as platform/product/appilcation). if not, complexity of the code and system will be increase but there will be API interface for interaction among the test framework. - And I thought to have interface (simple REST interface) in jaggery test frame work where current test framework also can interact with it into some extend. Thanks On Tue, Nov 12, 2013 at 5:57 PM, Madhuka Udantha madh...@wso2.comwrote: Hi, Still we do not have jaggery test framework even though there are considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there is no JS testing framework under WSO2 Platform. Testing framework will be under application level such as mocha, jasmine. Test frame will be apply to (basically)test. - jaggery API (js functions and arguments ) - REST APIs that are expose under jaggery application - With test coverage reporting We will be evaluating existing JavaScript test frame works regard mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and jsunit[7] to $subject. All suggestions are welcome. [1] http://visionmedia.github.io/mocha/ [2] http://pivotal.github.io/jasmine/ [3] http://qunitjs.com/ [4] http://vowsjs.org/ [5] http://visionmedia.github.io/expresso/ [6] https://github.com/caolan/nodeunit [7] https://github.com/pivotal/jsunit Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
Hi Krishantha and test automation team, I would like to get your opinion on this task regard to is there standard methodology on current testing framework where we can added such testing framework or better to go on fully independent model? My thinking is, - As it is application level testing frame work, better to work with much independent of the current system - Where application writer (developer) can run test for specific application rather running all test for platform or product - It will help to maintain both test framework with low cost - Each test frame have it's own scope (such as platform/product/appilcation). if not, complexity of the code and system will be increase but there will be API interface for interaction among the test framework. - And I thought to have interface (simple REST interface) in jaggery test frame work where current test framework also can interact with it into some extend. Thanks On Tue, Nov 12, 2013 at 5:57 PM, Madhuka Udantha madh...@wso2.com wrote: Hi, Still we do not have jaggery test framework even though there are considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there is no JS testing framework under WSO2 Platform. Testing framework will be under application level such as mocha, jasmine. Test frame will be apply to (basically)test. - jaggery API (js functions and arguments ) - REST APIs that are expose under jaggery application - With test coverage reporting We will be evaluating existing JavaScript test frame works regard mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and jsunit[7] to $subject. All suggestions are welcome. [1] http://visionmedia.github.io/mocha/ [2] http://pivotal.github.io/jasmine/ [3] http://qunitjs.com/ [4] http://vowsjs.org/ [5] http://visionmedia.github.io/expresso/ [6] https://github.com/caolan/nodeunit [7] https://github.com/pivotal/jsunit Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Jaggery] [Test] Test framework for jaggery
Hi, Still we do not have jaggery test framework even though there are considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there is no JS testing framework under WSO2 Platform. Testing framework will be under application level such as mocha, jasmine. Test frame will be apply to (basically)test. - jaggery API (js functions and arguments ) - REST APIs that are expose under jaggery application - With test coverage reporting We will be evaluating existing JavaScript test frame works regard mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and jsunit[7] to $subject. All suggestions are welcome. [1] http://visionmedia.github.io/mocha/ [2] http://pivotal.github.io/jasmine/ [3] http://qunitjs.com/ [4] http://vowsjs.org/ [5] http://visionmedia.github.io/expresso/ [6] https://github.com/caolan/nodeunit [7] https://github.com/pivotal/jsunit Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
