Re: [Dev] New global parent pom

[Samiyuru Senarathne]

Hi Manu,

This parent pom is meant to upload to maven central since this is the
parent of some of the project poms [1][2] we have introduced. One
requirement of this pom was to hide the project structure that is in the
root pom. So mss-parent pom directly inherits from wso2 parent.

[1] - https://github.com/wso2/msf4j/tree/master/mss-jar-parent
[2] - https://github.com/wso2/msf4j/tree/master/mss-lite-parent

Best Regards,
Samiyuru

On Mon, Feb 1, 2016 at 11:59 AM, Manuranga Perera  wrote:

> Hi Samiyuru,
> Is there any reason why org.wso2.carbon.mss pom [1] not pointing to
> carbon-mss as the parent. just wondering.
>
> [1]
> https://github.com/wso2/msf4j/blob/7eb8a028e7ea0cb343546492b1a7408ef2c0af06/carbon-mss/components/org.wso2.carbon.mss/pom.xml#L26
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
Samiyuru Senarathne
*Software Engineer*
Mobile : +94 (0) 71 134 6087
samiy...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to add patch improvements for Developer Studio update site

[Rajeeva Uthayasangar]

Hi Nuwan,

Please follow the steps:

1) Build the product with fix.
2) Navigate to below location in builder machine and create a folder called
"feature-updater" inside the product where the fix should be applied.
/home/developerstudio/wso2/developer-studio/

for example:if the fix is for ESB , then navigate to
 /home/developerstudio/wso2/developer-studio/esb and create the folder
called "feature-updater" in it.
3) then create the two folders  as features and plugins inside
feature-updater folder.
4) then add the feature jar to the features folder and the plugin jars
related to the feature inside the plugins folder.
5) Extract a eclipse distribution and give it's path as eclipse_home in the
publish.sh script
6) Execute the script
7) while it runs, it asks for the feature. Give the feature name without
the version
8) Script will create a newP2 which will contain p2 of the fix
9) then navigate to the below location. Create a folder with patch number
under updates. Please note, below location points to esb.

/home/developerstudio/public_html/developer-studio-kernel/4.0.0/esb-tools/updates
10) Copy the p2 (which is created in step 8) inside the newly created patch
folder
11)then update the compositeArtifacts.xml and compositeContent.xml to add
the new patch folder

thanks
Rajeeva.

On Mon, Feb 1, 2016 at 12:52 PM, Nuwan Pallewela  wrote:

> Hi All,
>
> What is the process for adding improvements done for a patch, to Developer
> Studio update site?
>
> Thanks,
> Nuwan
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Rajeeva Uthayasangar*
Software Engineer
WSO2, Inc.:http://wso2.com


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

Re: [Dev] How to add patch improvements for Developer Studio update site

[Susinda Perera]

On Mon, Feb 1, 2016 at 2:04 PM, Rajeeva Uthayasangar 
wrote:

> Hi Nuwan,
>
> Please follow the steps:
>
> 1) Build the product with fix.
> 2) Navigate to below location in builder machine and create a folder
> called "feature-updater" inside the product where the fix should be applied.
> /home/developerstudio/wso2/developer-studio/
>
> for example:if the fix is for ESB , then navigate to
>  /home/developerstudio/wso2/developer-studio/esb and create the folder
> called "feature-updater" in it.
> 3) then create the two folders  as features and plugins inside
> feature-updater folder.
>
@ Rajeewa : I think we can automate these folder creation in the publish.sh
script


> 4) then add the feature jar to the features folder and the plugin jars
> related to the feature inside the plugins folder.
> 5) Extract a eclipse distribution and give it's path as eclipse_home in
> the publish.sh script
> 6) Execute the script
> 7) while it runs, it asks for the feature. Give the feature name without
> the version
>
But we have to make sure the version is correct in the script. (This will
work for 4.0.0 but if you use the same script without modifying for a new
version, this will not work)


> 8) Script will create a newP2 which will contain p2 of the fix
> 9) then navigate to the below location. Create a folder with patch number
> under updates. Please note, below location points to esb.
>
> /home/developerstudio/public_html/developer-studio-kernel/4.0.0/esb-tools/updates
> 10) Copy the p2 (which is created in step 8) inside the newly created
> patch folder
> 11)then update the compositeArtifacts.xml and compositeContent.xml to add
> the new patch folder
>
> thanks
> Rajeeva.
>
> On Mon, Feb 1, 2016 at 12:52 PM, Nuwan Pallewela  wrote:
>
>> Hi All,
>>
>> What is the process for adding improvements done for a patch, to
>> Developer Studio update site?
>>
>> Thanks,
>> Nuwan
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Rajeeva Uthayasangar*
> Software Engineer
> WSO2, Inc.:http://wso2.com
>
>
> Mobile: +94777298873
>
>


-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to add patch improvements for Developer Studio update site

[Rajeeva Uthayasangar]

On Mon, Feb 1, 2016 at 3:15 PM, Susinda Perera  wrote:

>
>
> On Mon, Feb 1, 2016 at 2:04 PM, Rajeeva Uthayasangar 
> wrote:
>
>> Hi Nuwan,
>>
>> Please follow the steps:
>>
>> 1) Build the product with fix.
>> 2) Navigate to below location in builder machine and create a folder
>> called "feature-updater" inside the product where the fix should be applied.
>> /home/developerstudio/wso2/developer-studio/
>>
>> for example:if the fix is for ESB , then navigate to
>>  /home/developerstudio/wso2/developer-studio/esb and create the folder
>> called "feature-updater" in it.
>> 3) then create the two folders  as features and plugins inside
>> feature-updater folder.
>>
> @ Rajeewa : I think we can automate these folder creation in the
> publish.sh script
>

If we automate the folder creation, we need to automate the copying jars
part as well. In that case, we need to point the location  and name of the
jars. Those we can give a text file and read from there.

>
>
>> 4) then add the feature jar to the features folder and the plugin jars
>> related to the feature inside the plugins folder.
>> 5) Extract a eclipse distribution and give it's path as eclipse_home in
>> the publish.sh script
>> 6) Execute the script
>> 7) while it runs, it asks for the feature. Give the feature name without
>> the version
>>
> But we have to make sure the version is correct in the script. (This will
> work for 4.0.0 but if you use the same script without modifying for a new
> version, this will not work)
>
>
>> 8) Script will create a newP2 which will contain p2 of the fix
>> 9) then navigate to the below location. Create a folder with patch number
>> under updates. Please note, below location points to esb.
>>
>> /home/developerstudio/public_html/developer-studio-kernel/4.0.0/esb-tools/updates
>> 10) Copy the p2 (which is created in step 8) inside the newly created
>> patch folder
>> 11)then update the compositeArtifacts.xml and compositeContent.xml to add
>> the new patch folder
>>
>> thanks
>> Rajeeva.
>>
>> On Mon, Feb 1, 2016 at 12:52 PM, Nuwan Pallewela  wrote:
>>
>>> Hi All,
>>>
>>> What is the process for adding improvements done for a patch, to
>>> Developer Studio update site?
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com *
>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Rajeeva Uthayasangar*
>> Software Engineer
>> WSO2, Inc.:http://wso2.com
>>
>>
>> Mobile: +94777298873
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>


-- 
*Rajeeva Uthayasangar*
Software Engineer
WSO2, Inc.:http://wso2.com


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

[Dev] WSO2 Committers += Maduranga Siriwardena

[Johann Nallathamby]

Hi All,

It's my pleasure to announce Maduranga Siriwardena as a WSO2 Committer.
Maduranga has been a valuable contributor for WSO2 Identity Server product,
and in recognition of his contribution to WSO2, he has been voted as a WSO2
Committer.

Maduranga, congratulations and keep up the good work!

Thanks & Regards.

-- 

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading Smooks to version 1.5

[Buddhima Wijeweera]

Hi Kishanthan,

I tried with given osgi bundles which provides freemaker. But again met up
with another problem of requiring groovy:

BundleException: The bundle "org.milyn.smooks.osgi_1.5.0 [143]" could not
be resolved. Reason: Missing Constraint: Import-Package: groovy.xml;
version="1.5.7"

Therefore after offline discussions, decided to go ahead with the earlier
approach of bundling Smooks as an orbit bundle.

Thank you,


On Mon, Feb 1, 2016 at 12:56 PM, Kishanthan Thangarajah  wrote:

> Can we try with [1] or [2] as the FreeMaker OSGi bundle? If these doesn't
> bring any additional OSGi dependencies, we can use it, but let's try out
> these first.
>
> [1]
> http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.freemarker&version=2.3.15
> [2]
> http://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.freemarker/2.3.15_5
>
> On Mon, Feb 1, 2016 at 12:04 PM, Buddhima Wijeweera 
> wrote:
>
>> Thanks Kasun,
>>
>> [Adding dev mailing list]
>>
>> On Mon, Feb 1, 2016 at 12:02 PM, Kasun Indrasiri  wrote:
>>
>>> Shouldn't we discuss this in a mailing list?
>>>
>>> On Mon, Feb 1, 2016 at 12:00 PM, Buddhima Wijeweera 
>>> wrote:
>>>
 Hi All,

 For the the next ESB release we need to upgrade Smooks version from 1.4
 to 1.5. Currently Smooks bundle is created through orbit which reside in
 location [1].

 According to offline discussion had with Kishanthan, we have asked to
 try directly using smooks osgi bundle in carbon-mediation but we ended up
 with a problem activating Smooks OSGI bundle as it required certain
 additional dependencies.

 example:

 BundleException: The bundle "org.milyn.smooks.osgi_1.5.0 [142]" could
 not be resolved. Reason: Missing Constraint: Import-Package:
 freemarker.cache; version="2.3.15"

 Which means smooks osgi bundle is searching for freemarker dependency.

 The freemarker can be found as a jar [2]. But even after we add it to
 "/lib" folder, still the smooks bundle fails to activate, since it can't
 find the matching version (freemarker bundle is in active state).

 The reason behind this is the version of free marker carbon server
 generated. Even by bundling freemarker as a orbit bundle (which adds "wso2"
 post-fix to version), the exact version "2.3.15" cannot be satisfied,
 according to my knowledge.

 The best option so far can be seen is to re-bundle smooks along
 with dependencies as an orbit bundle, which is the way it was there before.

 Please let us know if there's any other alternative to overcome this
 confusion.
 [1] https://svn.wso2.org/repos/wso2/trunk/orbit/smooks/
 [2] http://mvnrepository.com/artifact/org.freemarker/freemarker/2.3.15

 Thank you,
 --
 Buddhima Wijeweera
 Software Engineer; WSO2 Inc.; http://wso2.com ,

 Mobile: +94 71 427 9966
 Email: buddh...@wso2.com
 Blog:   https://buddhimawijeweera.wordpress.com
 GitHub Profile: https://github.com/Buddhima

>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> Buddhima Wijeweera
>> Software Engineer; WSO2 Inc.; http://wso2.com ,
>>
>> Mobile: +94 71 427 9966
>> Email: buddh...@wso2.com
>> Blog:   https://buddhimawijeweera.wordpress.com
>> GitHub Profile: https://github.com/Buddhima
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Associate Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,

Mobile: +94 71 427 9966
Email: buddh...@wso2.com
Blog:   https://buddhimawijeweera.wordpress.com
GitHub Profile: https://github.com/Buddhima
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading Smooks to version 1.5

[Buddhima Wijeweera]

Hi All,

Please find the relevant link for the PR :
https://github.com/wso2/orbit/pull/170

Thank you,

On Mon, Feb 1, 2016 at 5:52 PM, Buddhima Wijeweera 
wrote:

> Hi Kishanthan,
>
> I tried with given osgi bundles which provides freemaker. But again met up
> with another problem of requiring groovy:
>
> BundleException: The bundle "org.milyn.smooks.osgi_1.5.0 [143]" could not
> be resolved. Reason: Missing Constraint: Import-Package: groovy.xml;
> version="1.5.7"
>
> Therefore after offline discussions, decided to go ahead with the earlier
> approach of bundling Smooks as an orbit bundle.
>
> Thank you,
>
>
> On Mon, Feb 1, 2016 at 12:56 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Can we try with [1] or [2] as the FreeMaker OSGi bundle? If these doesn't
>> bring any additional OSGi dependencies, we can use it, but let's try out
>> these first.
>>
>> [1]
>> http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.freemarker&version=2.3.15
>> [2]
>> http://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.freemarker/2.3.15_5
>>
>> On Mon, Feb 1, 2016 at 12:04 PM, Buddhima Wijeweera 
>> wrote:
>>
>>> Thanks Kasun,
>>>
>>> [Adding dev mailing list]
>>>
>>> On Mon, Feb 1, 2016 at 12:02 PM, Kasun Indrasiri  wrote:
>>>
 Shouldn't we discuss this in a mailing list?

 On Mon, Feb 1, 2016 at 12:00 PM, Buddhima Wijeweera 
 wrote:

> Hi All,
>
> For the the next ESB release we need to upgrade Smooks version from
> 1.4 to 1.5. Currently Smooks bundle is created through orbit which reside
> in location [1].
>
> According to offline discussion had with Kishanthan, we have asked to
> try directly using smooks osgi bundle in carbon-mediation but we ended up
> with a problem activating Smooks OSGI bundle as it required certain
> additional dependencies.
>
> example:
>
> BundleException: The bundle "org.milyn.smooks.osgi_1.5.0 [142]" could
> not be resolved. Reason: Missing Constraint: Import-Package:
> freemarker.cache; version="2.3.15"
>
> Which means smooks osgi bundle is searching for freemarker dependency.
>
> The freemarker can be found as a jar [2]. But even after we add it to
> "/lib" folder, still the smooks bundle fails to activate, since it can't
> find the matching version (freemarker bundle is in active state).
>
> The reason behind this is the version of free marker carbon server
> generated. Even by bundling freemarker as a orbit bundle (which adds 
> "wso2"
> post-fix to version), the exact version "2.3.15" cannot be satisfied,
> according to my knowledge.
>
> The best option so far can be seen is to re-bundle smooks along
> with dependencies as an orbit bundle, which is the way it was there 
> before.
>
> Please let us know if there's any other alternative to overcome this
> confusion.
> [1] https://svn.wso2.org/repos/wso2/trunk/orbit/smooks/
> [2] http://mvnrepository.com/artifact/org.freemarker/freemarker/2.3.15
>
> Thank you,
> --
> Buddhima Wijeweera
> Software Engineer; WSO2 Inc.; http://wso2.com ,
>
> Mobile: +94 71 427 9966
> Email: buddh...@wso2.com
> Blog:   https://buddhimawijeweera.wordpress.com
> GitHub Profile: https://github.com/Buddhima
>



 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

>>>
>>>
>>>
>>> --
>>> Buddhima Wijeweera
>>> Software Engineer; WSO2 Inc.; http://wso2.com ,
>>>
>>> Mobile: +94 71 427 9966
>>> Email: buddh...@wso2.com
>>> Blog:   https://buddhimawijeweera.wordpress.com
>>> GitHub Profile: https://github.com/Buddhima
>>>
>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Associate Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan *
>>
>
>
>
> --
> Buddhima Wijeweera
> Software Engineer; WSO2 Inc.; http://wso2.com ,
>
> Mobile: +94 71 427 9966
> Email: buddh...@wso2.com
> Blog:   https://buddhimawijeweera.wordpress.com
> GitHub Profile: https://github.com/Buddhima
>



-- 
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,

Mobile: +94 71 427 9966
Email: buddh...@wso2.com
Blog:   https://buddhimawijeweera.wordpress.com
GitHub Profile: https://github.com/Buddhima
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

[Rajeenthini Satkunam]

Hi sajith,

i have added this Student class for example.As for current implementation
goes like this way in Jaggery below.

public static String serializeJSON(Object obj) {
if (obj instanceof Wrapper) {
obj = ((Wrapper) obj).unwrap();
}
if (obj == null) {
return "null";
}
if (obj instanceof Undefined) {
return "null";
}
if (obj instanceof Boolean) {
return Boolean.toString((Boolean) obj);
}
if (obj instanceof String) {
return serializeString((String) obj);
}
if (obj instanceof ConsString) {
return serializeString(obj.toString());
}
if (obj instanceof Number) {
return obj.toString();
}
if (obj instanceof XMLObject) {
return serializeString(serializeXML((ScriptableObject) obj));
}
if (obj instanceof NativeObject) {
return serializeNativeObject((NativeObject) obj);
}
if (obj instanceof NativeArray) {
return serializeNativeArray((NativeArray) obj);
}
if (obj instanceof Object[]) {
return serializeObjectArray((Object[]) obj);
}
if (obj instanceof Scriptable) {
Scriptable object = (Scriptable) obj;
String jsClass = object.getClassName();
if ("Date".equals(jsClass)) {
return serializeString(serializeNativeDate(object));
} else if ("Error".equals(jsClass)) {
return serializeString(serializeNativeError(object));
}
}
String JsonString = null;
try{
ObjectMapper mapper = new ObjectMapper();
JsonString = mapper.writeValueAsString(obj);
}catch (Exception e){
System.out.println(e.getMessage());
}

return "{\"javaObject\":\"true\",\"object\":\"" + JsonString + "\"}";
}

AFAIU since we are parsing Object type of argument It is better we can use
ObjectMapper.Correct me If I am wrong.Your suggestion would be more
appreciated.

On Sun, Jan 31, 2016 at 10:23 AM, Sajith Ariyarathna 
wrote:

> Hi Rajeenthini,
>
> AFAIK ability to convert a POJO into JSON object does nor affect the
> output of a Jaggery Log of that POJO.
> To get a proper log output for a Java object, you need to implement the
> "toString" method in that Java class. For example in your case,
>
> public class Student {
>
> ...
>
> public String toString() {
>
> return "{name: " + this.name + ", age: " + this.age + ", indexNo: " +
> this.indexNo + "}";
>
> }
>
> }
>
> Now you can log a Student object in your Jaggery code as following.
>
> log.info(studentObj.toString());
>
>
> Thanks.
>
>
>
> On Sat, Jan 30, 2016 at 9:28 PM, Rajeenthini Satkunam <
> rajeenth...@wso2.com> wrote:
>
>> Hi,
>>
>> I have worked on writing Jaggery test for Jaggery-Product.I can observe
>> when we tried to log the object it always gives us empty JSON
>> ({}).Currently the implementation goes this way when we try to log java
>> object.
>>
>> So I was trying to get rid of this observed behavior of Jaggery.I have
>> gone through a solution.
>>
>> *using Jackson[1] *
>>
>> We can convert java object to JSON[2] and can log it.
>>
>> I have shared the piece of code I have tried out with Jackson below.
>>
>> *Simple POJO Student class*
>>
>> public class Student {
>> private int age;
>> private String name;
>> private String indexNo;
>>
>> public int getAge() {
>> return age;
>> }
>>
>> public void setAge(int age) {
>> this.age = age;
>> }
>>
>> public String getName() {
>> return name;
>> }
>>
>> public void setName(String name) {
>> this.name = name;
>> }
>>
>> public String getIndexNo() {
>> return indexNo;
>> }
>>
>> public void setIndexNo(String indexNo) {
>> this.indexNo = indexNo;
>> }
>> }
>>
>> *Simple class to test Jackson*
>>
>> import com.fasterxml.jackson.databind.ObjectMapper;
>> import util.Student;
>> public class MyTest {
>> public static void main(String args[]){
>> Student st = new Student();
>> st.setIndexNo("DS001");
>> st.setAge(12);
>> st.setName("kareena");
>> try{
>> ObjectMapper mapper = new ObjectMapper();
>> String jsonInString = mapper.writeValueAsString(st);
>> 
>> System.out.println("");
>> System.out.println(jsonInString);
>> 
>> System.out.println("");
>>
>> }catch(Exception e){
>> System.out.print("Exception caught  "+ e);
>> }
>>
>> }
>> }
>>
>> Actual output by above code.
>> 
>> {"age":12,"name":"kareena","indexNo":"DS001"}
>> 
>>
>> I have added a dependency in the POM.xml
>>
>> 
>> com.fasterxml.jackson.core
>> jackson-databind
>> 2.6.3
>> 
>>
>>
>> IMHO we can use the same scenario in case of log JAVA object.Your help
>> and sugge

Re: [Dev] Dev] [VOTE] Release WSO2 Business Process Server 3.5.1 RC2

[Hasitha Aravinda]

Hi team,

We are canceling this vote, as we found L1 [1] issue.
​We are working on fixing it and will soon provide WSO2 BPS
 3.5.1 RC
​3 pack for testing.

[1] - https://wso2.org/jira/browse/CARBON-15776

Thanks,
Hasitha.

On Sat, Jan 30, 2016 at 11:44 PM, Hasitha Aravinda  wrote:

> ​I have verified Pack contents and tested followings,
>
>- Tested Main BPEL functionalists in clustered environment ( LB :
>Nginx , DB : MySQL )
>- Tested BPEL and Human Task Integration in clustered environment.
>- Tested Human Task Coordination in Super tenant and tenant mode.
>- Tested ODE JOB reassignment in clustered mode.
>
> No issue found.
> [X] Stable - Go ahead and release.
>
> Thanks,
> Hasitha
>
> On Fri, Jan 29, 2016 at 5:34 PM, Amal Gunatilake  wrote:
>
>> Hi,
>>
>> I have tested the following.
>>
>>- Main functionalities of BPEL, Humantask, BPMN on Windows
>>environment.
>>- Main functionalities of BPEL, Humantask, BPMN connecting to Oracle
>>DB.
>>- BPMN
>>- Deployment / Undeployment
>>   - Process View
>>   - Manage instances
>>   - BPMN manage user access permission
>>   - REST invocations
>>   - Correlation
>>- Core functionalities of BPMN Rest API
>>
>> No issues found.
>> [x] Stable - go ahead and release
>>
>> Best regards,
>> Amal.
>>
>>
>> On Fri, Jan 29, 2016 at 4:23 PM, Samitha Chathuranga 
>> wrote:
>>
>>> Hi all,
>>>
>>> I've tested following features.
>>>
>>> 1) BPMN Explorer
>>> 2) BPMN Samples
>>> 3) HumanTask Samples
>>>
>>> No issues found.
>>> [x] Stable - go ahead and release
>>>
>>> Thank you.
>>>
>>> On Fri, Jan 29, 2016 at 1:58 PM, Sathya Bandara  wrote:
>>>
 Hi all,

 I have tested the bpel samples. No issues found.
 [x] Stable - go ahead and release

 Thanks and regards,

 *Sathya Bandara*
 Software Engineering Intern
 Email: sat...@wso2.com
 Mobile: +94 715 360 421

 On Fri, Jan 29, 2016 at 12:04 PM, Natasha Wijesekara 
 wrote:

> Hi All,
>
> I've tested the functionalities of the following components using h2
> and mysql as the databases :
>
> 1) BPMN-Explorer
> 2) Human-Task Explorer
> 3) Core functionalities of the BPMN REST API
> 4) BPMN and BPEL instance cleanup scripts
> 5) BPEL Process cleanup tool
> 6) BPMN Samples
>
> No issues found.
> [x] Stable - go ahead and release
>
> Thanks and Regards,
> Natasha
>
> On Fri, Jan 29, 2016 at 10:40 AM, Isuru Wijesinghe 
> wrote:
>
>> Hi All,
>>
>> I've tested the following features for h2 and postgreSQL.
>>
>> 1.) BPMN-Explorer
>> 2.) HumanTask-Explorer
>> 3.) BPMN Data Publisher
>>
>> No issues found.
>> [x] Stable - go ahead and release
>>
>> Thanks and Regards,
>>
>>
>> On Thu, Jan 28, 2016 at 8:00 PM, Firzhan Naqash 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the second release candidate of WSO2 Business Process Server
>>> 3.5.1
>>>
>>> The vote will be open for 72 hours or as needed. Please download,
>>> test the product and vote.
>>>
>>> ​​This release fixes the following issues:
>>>
>>> https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12625
>>>
>>> Binary distribution is available here:
>>>
>>> https://github.com/wso2/product-bps/releases/download/v3.5.1-RC2/wso2bps-3.5.1.zip
>>>
>>> ​​Source is available here:
>>> https://github.com/wso2/product-bps/archive/v3.5.1-RC2.zip
>>>
>>> ​​Maven staging repo:
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2bps-312/
>>>
>>> ​​The tag to be voted upon:
>>> ​​https://github.com/wso2/product-bps/releases/tag/v3.5.1-RC2
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>>
>>> ​Thanks,
>>> ​WSO2 BPS Team,
>>>
>>> Regards,
>>> Firzhan
>>>
>>>
>>> --
>>> *Firzhan Naqash*
>>> Senior Software Engineer - Integration Platform Team
>>> WSO2 Inc. http://wso2.com
>>>
>>> email: firz...@wso2.com
>>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>>> blog: http://firzhanblogger.blogspot.com/
>>>   
>>> *
>>> *twitter: https://twitter.com/firzhan007
>>>  | linked-in: 
>>> **https://www.linkedin.com/in/firzhan
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Isuru Wijesinghe
>> *Software Engineer*
>> WSO2 inc : http://wso2.com
>> lean.enterprise.middleware
>> Mobile: 0710933706
>> isur...@wso2.com
>>
>> _

[Dev] Build failure in MSS in Windows

[Shazni Nazir]

Hi all,

I tried building the https://github.com/wso2/msf4j repo in windows and I
get the following build failure.

[1]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 6.204s
[INFO] Finished at: Mon Feb 01 12:51:44 EST 2016
[INFO] Final Memory: 30M/361M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.16:check (validate) on
project msf4j-core: Failed during checkstyle execution: There are 13 errors
reported by Checkstyle 6.2 with
https://raw.githubusercontent.com/wso2/code-quality-tools/master/checkstyle/checkstyle.xml
ruleset. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :msf4j-core

Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in MSS in Windows

[Shazni Nazir]

Attached is the checkstyle errors xml for your reference.

Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com

On Mon, Feb 1, 2016 at 1:03 PM, Shazni Nazir  wrote:

> Hi all,
>
> I tried building the https://github.com/wso2/msf4j repo in windows and I
> get the following build failure.
>
> [1]
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 6.204s
> [INFO] Finished at: Mon Feb 01 12:51:44 EST 2016
> [INFO] Final Memory: 30M/361M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.16:check (validate) on
> project msf4j-core: Failed during checkstyle execution: There are 13 errors
> reported by Checkstyle 6.2 with
> https://raw.githubusercontent.com/wso2/code-quality-tools/master/checkstyle/checkstyle.xml
> ruleset. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :msf4j-core
>
> Shazni Nazeer
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>



http://www.puppycrawl.com/dtds/configuration_1_3.dtd";>




































  




































































































































































































































































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

Re: [Dev] Build failure in MSS in Windows

[Shazni Nazir]

Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com

On Mon, Feb 1, 2016 at 1:08 PM, Shazni Nazir  wrote:

> Attached is the checkstyle errors xml for your reference.
>
> Shazni Nazeer
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> On Mon, Feb 1, 2016 at 1:03 PM, Shazni Nazir  wrote:
>
>> Hi all,
>>
>> I tried building the https://github.com/wso2/msf4j repo in windows and I
>> get the following build failure.
>>
>> [1]
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 6.204s
>> [INFO] Finished at: Mon Feb 01 12:51:44 EST 2016
>> [INFO] Final Memory: 30M/361M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-checkstyle-plugin:2.16:check (validate) on
>> project msf4j-core: Failed during checkstyle execution: There are 13 errors
>> reported by Checkstyle 6.2 with
>> https://raw.githubusercontent.com/wso2/code-quality-tools/master/checkstyle/checkstyle.xml
>> ruleset. -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :msf4j-core
>>
>> Shazni Nazeer
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>
>



http://www.puppycrawl.com/dtds/configuration_1_3.dtd";>




































  




































































































































































































































































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

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

[Sajith Ariyarathna]

Hi Rajeenthini,

You are hoping to add the following code snippet to the serializeJSON
method [1] of the org.jaggeryjs.scriptengine.util.HostObjectUtil class.

> String JsonString = null;
> try{
> ObjectMapper mapper = new ObjectMapper();
> JsonString = mapper.writeValueAsString(obj);
> }catch (Exception e){
> System.out.println(e.getMessage());
> }
>
> return "{\"javaObject\":\"true\",\"object\":\"" + JsonString + "\"}";
>
> There are few issue in this code snippet.

   - Don't catch generic Exception, always catch a specific exception. In
   here you should catch JsonProcessingException [2].
   - Don't use System.out.println to log exceptions. Instead use a proper
   logger. HostObjectUtil class has a log object defined in line 30 [3],
   you can use that.
   - Returning '{"javaObject": "true", "object": "{ ... }"}' string gives a
   wrong impression that there are two attributes called 'javaObject' &
   'object' in the logged object. I think just returning the JSON string will
   be enough.

After corrections (I also took the liberty to reduce no of lines):

try {

return (new ObjectMapper()).writeValueAsString(obj);

} catch (JsonProcessingException e) {

log.debug("Object " + obj.toString() + " of class " + obj.getClassName() +
" cannot be converted to JSON");

}

return "{}";


[1]
https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L78
[2]
https://static.javadoc.io/com.fasterxml.jackson.core/jackson-databind/2.6.3/com/fasterxml/jackson/databind/ObjectMapper.html#writeValueAsString(java.lang.Object)
[3]
https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L30

Thanks.


On Mon, Feb 1, 2016 at 8:13 PM, Rajeenthini Satkunam 
wrote:

> Hi sajith,
>
> i have added this Student class for example.As for current implementation
> goes like this way in Jaggery below.
>
> public static String serializeJSON(Object obj) {
> if (obj instanceof Wrapper) {
> obj = ((Wrapper) obj).unwrap();
> }
> if (obj == null) {
> return "null";
> }
> if (obj instanceof Undefined) {
> return "null";
> }
> if (obj instanceof Boolean) {
> return Boolean.toString((Boolean) obj);
> }
> if (obj instanceof String) {
> return serializeString((String) obj);
> }
> if (obj instanceof ConsString) {
> return serializeString(obj.toString());
> }
> if (obj instanceof Number) {
> return obj.toString();
> }
> if (obj instanceof XMLObject) {
> return serializeString(serializeXML((ScriptableObject) obj));
> }
> if (obj instanceof NativeObject) {
> return serializeNativeObject((NativeObject) obj);
> }
> if (obj instanceof NativeArray) {
> return serializeNativeArray((NativeArray) obj);
> }
> if (obj instanceof Object[]) {
> return serializeObjectArray((Object[]) obj);
> }
> if (obj instanceof Scriptable) {
> Scriptable object = (Scriptable) obj;
> String jsClass = object.getClassName();
> if ("Date".equals(jsClass)) {
> return serializeString(serializeNativeDate(object));
> } else if ("Error".equals(jsClass)) {
> return serializeString(serializeNativeError(object));
> }
> }
> String JsonString = null;
> try{
> ObjectMapper mapper = new ObjectMapper();
> JsonString = mapper.writeValueAsString(obj);
> }catch (Exception e){
> System.out.println(e.getMessage());
> }
>
> return "{\"javaObject\":\"true\",\"object\":\"" + JsonString + "\"}";
> }
>
> AFAIU since we are parsing Object type of argument It is better we can use
> ObjectMapper.Correct me If I am wrong.Your suggestion would be more
> appreciated.
>
> On Sun, Jan 31, 2016 at 10:23 AM, Sajith Ariyarathna 
> wrote:
>
>> Hi Rajeenthini,
>>
>> AFAIK ability to convert a POJO into JSON object does nor affect the
>> output of a Jaggery Log of that POJO.
>> To get a proper log output for a Java object, you need to implement the
>> "toString" method in that Java class. For example in your case,
>>
>> public class Student {
>>
>> ...
>>
>> public String toString() {
>>
>> return "{name: " + this.name + ", age: " + this.age + ", indexNo: " +
>> this.indexNo + "}";
>>
>> }
>>
>> }
>>
>> Now you can log a Student object in your Jaggery code as following.
>>
>> log.info(studentObj.toString());
>>
>>
>> Thanks.
>>
>>
>>
>> On Sat, Jan 30, 2016 at 9:28 PM, Rajeenthini Satkunam <
>> rajeenth...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have worked on writing Jaggery test for Jaggery-Product.I can observe
>>> when we tried to log the object it always gives us empty JSON
>>> ({}).Currently the implementation goes this way when we try to log java
>>> object.
>>>
>>> So I was

Re: [Dev] Build failure in MSS in Windows

[Shazni Nazir]

I got a pull of the git and I get there are only 4 errors remaining with
check style. They are the following. Thanks for the very quick fix Azeez.













regards


Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com

On Mon, Feb 1, 2016 at 1:16 PM, Shazni Nazir  wrote:

>
>
> Shazni Nazeer
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> On Mon, Feb 1, 2016 at 1:08 PM, Shazni Nazir  wrote:
>
>> Attached is the checkstyle errors xml for your reference.
>>
>> Shazni Nazeer
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>> On Mon, Feb 1, 2016 at 1:03 PM, Shazni Nazir  wrote:
>>
>>> Hi all,
>>>
>>> I tried building the https://github.com/wso2/msf4j repo in windows and
>>> I get the following build failure.
>>>
>>> [1]
>>>
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 6.204s
>>> [INFO] Finished at: Mon Feb 01 12:51:44 EST 2016
>>> [INFO] Final Memory: 30M/361M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-checkstyle-plugin:2.16:check (validate) on
>>> project msf4j-core: Failed during checkstyle execution: There are 13 errors
>>> reported by Checkstyle 6.2 with
>>> https://raw.githubusercontent.com/wso2/code-quality-tools/master/checkstyle/checkstyle.xml
>>> ruleset. -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>> [ERROR]   mvn  -rf :msf4j-core
>>>
>>> Shazni Nazeer
>>> Mob : +94 37331
>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>> Blog : http://shazninazeer.blogspot.com
>>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] WSO2 Complex Event Processor 4.1.0 Alpha Released

[Mohanadarshan Vivekanandalingam]

Hi All,

WSO2 CEP Team is pleased to announce the Alpha release of WSO2 Complex
Event Processor 4.1.0.

WSO2 Complex Event Processor (CEP) can be used to identify the most
meaningful events within an event cloud, analyzes their impacts, and acts
on them in real time. Built to be extremely high performing it offers
significant time saving and affordable acquisition. WSO2 CEP Manager is
released under the Apache Software License 2.0.

The distribution is available at [1]. The documentation for CEP 4.1.0 Alpha
can be found at [2] (which is WIP). Your feedback is most welcome, and any
issues can be reported to the project at [3].

Following bug fixes, improvements and new features have been added along
with this release .

*Improvements*

   - [CEP-644 ] - add insertOrUpdate
   to event table
   - [CEP-1419 ] - Provide "insert
   or update" functionality to event tables
   - [CEP-1426 ] - When passing
   parameters to function allow the syntax func(*) if all the attributes of
   the inputstream have to be passed
   - [CEP-1439 ] - Map extension
   support
   - [CEP-1445 ] - Improve
   user-friendliness by sorting drop-down lists
   - [CEP-1448 ] - Hazelcast Event
   Table for Siddhi
   - [CEP-1450 ] - Adding Arbitrary
   Map support for Receiver Components
   - [CEP-1453 ] - Pause, Resume and
   Stop support for Event Simulator
   - [CEP-1458 ] - Support for more
   then 2 nodes in HA deployment


*New Features*

   - [CEP-101 ] - Indexing for
   Hazelcast table
   - [CEP-105 ] - Time length window
   implementation for Siddhi
   - [CEP-1365 ] - Add a function to
   extract 'DAY OF WEEK' from time/timestamp
   - [CEP-1423 ] - Support
   outer/left joins in Siddhi
   - [CEP-1440 ] - Geo Closest
   function
   - [CEP-1441 ] - External Batch
   window for siddhi
   - [CEP-1457 ] - Minima and Maxima
   detection on Siddhi
   - [CEP-1459 ] - Instrumentation &
   Monitoring support for CEP and Siddhi


*Bugs*

   - [CEP-1117 ] - No default value
   support for Map mapping
   - [CEP-1338 ] - [Intermittent]
   Error observed in edit tenant UI
   - [CEP-1352 ] - 'The [action]
   cannot be processed at the receiver' error when clicked on 'Streams' option
   - [CEP-1361 ] - Index Out of
   Bounds Exception after a new field is added to Stream
   - [CEP-1363 ] - Execution plan
   does not display "from" when we type @ symbol as a result this needs to be
   added
   - [CEP-1375 ] -
   org.wso2.carbon.event.processor.admin bundle activation is getting delayed
   because it get wires with wrong dependency version
   - [CEP-1393 ] - NPE thrown for
   Websocket Local Input Receiver if the same receiver is redeployed
   - [CEP-1400 ] - Error when
   integrating ML extension to CEP storm cluster
   - [CEP-1401 ] - Issue in email
   event adapter
   - [CEP-1405 ] - "No extension
   exist for StreamFunctionExtension{namespace='ml'}" exception when started
   worker node with -DworkerNode=true property
   - [CEP-1407 ] - In conditions
   cannot be used in select statement
   - [CEP-1408 ] - Concurrent
   Modification exception
   - [CEP-1409 ] - When modifying an
   event stream, information does not get removed from in-memory cache at
   databridge
   - [CEP-1410 ] - Validate Input
   Stream for WSO2Event custom mapping
   - [CEP-1411 ] - Siddhi thread
   dead on invalid inputs
   - [CEP-1415 ] - Event Table
   Update results in duplicate inserts
   - [CEP-1418 ] - Test cases are
   failing in SnapshotOutputRateLimitTestCase due to possible thread
   contention issue
   - [CEP-1422 ] -
   ArrayIndexOutOfBoundsException when adding wso2-event publisher with
   invalid Receiver URL
   - [CEP-1427 

Re: [Dev] Build failure in MSS in Windows

[Afkham Azeez]

On Tue, Feb 2, 2016 at 12:04 AM, Shazni Nazir  wrote:

> MimeMapperTest


Thanks for reporting these issues Shazni. Please check now.


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

Re: [Dev] Build failure in MSS in Windows

[Shazni Nazir]

Build is successful now. Thanks for the quick fix.

Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com

On Mon, Feb 1, 2016 at 1:49 PM, Afkham Azeez  wrote:

>
> On Tue, Feb 2, 2016 at 12:04 AM, Shazni Nazir  wrote:
>
>> MimeMapperTest
>
>
> Thanks for reporting these issues Shazni. Please check now.
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Message Broker 3.1.0 RC 1

[Akalanka Pagoda Arachchi]

Hi Devs,

This is the first release candidate of WSO2 Message Broker 3.0.0.

This release fixes the following issues:
https://wso2.org/jira/issues/?filter=12633


Please download MB 3.1.0 RC1 and test the functionality and vote. Vote will
be open for 72 hours or as needed.

Source & binary distribution files:
https://github.com/wso2/product-mb/releases/tag/v3.1.0-RC1

Maven staging repo:
http://maven.wso2.org/nexus/content/repositories/orgwso2mb-316/

The tag to be voted upon:
https://github.com/wso2/product-mb/tree/v3.1.0-RC1


[+] Stable - go ahead and release
[-]  Broken - do not release (explain why)

Thanks and Regards,
~ WSO2 MB Team ~

-- 
*Darshana Akalanka Pagoda Arachchi,*
*Software Engineer*
*078-4721791*



-- 
*Darshana Akalanka Pagoda Arachchi,*
*Software Engineer*
*078-4721791*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to add patch improvements for Developer Studio update site

[Awanthika Senarath]

I have tried working on that but it did not work in reading the feature.xml
file and copying the relevant jars.

it is doable though. It should be easier to read it from a text file and
copy the jars.

Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Mon, Feb 1, 2016 at 3:27 PM, Rajeeva Uthayasangar 
wrote:

>
>
> On Mon, Feb 1, 2016 at 3:15 PM, Susinda Perera  wrote:
>
>>
>>
>> On Mon, Feb 1, 2016 at 2:04 PM, Rajeeva Uthayasangar 
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> Please follow the steps:
>>>
>>> 1) Build the product with fix.
>>> 2) Navigate to below location in builder machine and create a folder
>>> called "feature-updater" inside the product where the fix should be applied.
>>> /home/developerstudio/wso2/developer-studio/
>>>
>>> for example:if the fix is for ESB , then navigate to
>>>  /home/developerstudio/wso2/developer-studio/esb and create the folder
>>> called "feature-updater" in it.
>>> 3) then create the two folders  as features and plugins inside
>>> feature-updater folder.
>>>
>> @ Rajeewa : I think we can automate these folder creation in the
>> publish.sh script
>>
>
> If we automate the folder creation, we need to automate the copying jars
> part as well. In that case, we need to point the location  and name of the
> jars. Those we can give a text file and read from there.
>
>>
>>
>>> 4) then add the feature jar to the features folder and the plugin jars
>>> related to the feature inside the plugins folder.
>>> 5) Extract a eclipse distribution and give it's path as eclipse_home in
>>> the publish.sh script
>>> 6) Execute the script
>>> 7) while it runs, it asks for the feature. Give the feature name without
>>> the version
>>>
>> But we have to make sure the version is correct in the script. (This will
>> work for 4.0.0 but if you use the same script without modifying for a new
>> version, this will not work)
>>
>>
>>> 8) Script will create a newP2 which will contain p2 of the fix
>>> 9) then navigate to the below location. Create a folder with patch
>>> number under updates. Please note, below location points to esb.
>>>
>>> /home/developerstudio/public_html/developer-studio-kernel/4.0.0/esb-tools/updates
>>> 10) Copy the p2 (which is created in step 8) inside the newly created
>>> patch folder
>>> 11)then update the compositeArtifacts.xml and compositeContent.xml to
>>> add the new patch folder
>>>
>>> thanks
>>> Rajeeva.
>>>
>>> On Mon, Feb 1, 2016 at 12:52 PM, Nuwan Pallewela 
>>> wrote:
>>>
 Hi All,

 What is the process for adding improvements done for a patch, to
 Developer Studio update site?

 Thanks,
 Nuwan

 --
 --

 *Nuwan Chamara Pallewela*


 *Software Engineer*

 *WSO2, Inc. *http://wso2.com
 *lean . enterprise . middleware*

 Email   *nuw...@wso2.com *
 Mobile  *+94719079739 <%2B94719079739>@*



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


>>>
>>>
>>> --
>>> *Rajeeva Uthayasangar*
>>> Software Engineer
>>> WSO2, Inc.:http://wso2.com
>>>
>>>
>>> Mobile: +94777298873
>>>
>>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>>
>
>
> --
> *Rajeeva Uthayasangar*
> Software Engineer
> WSO2, Inc.:http://wso2.com
>
>
> Mobile: +94777298873
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [che-dev] Trying Eclipse Che latest release on ubuntu

[Awanthika Senarath]

Hi Alexander,

Running the exact script given by you results in the following error[1]. I
will try in another machine to see whether this is related to my local
setup.

It says that the che.sh file has some syntax errors..

My OS does not seem to recognize the function declarations in the SH file.

[1] GNU bash, version 4.3.8(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
 3897 pts/1S+ 0:00 sh che.sh run
 3900 pts/1S+ 0:00 grep che.sh
che.sh: 22: che.sh: function: not found
che.sh: 101: che.sh: Syntax error: "}" unexpected



Regards
Awanthika


Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Fri, Jan 29, 2016 at 4:24 PM, Awanthika Senarath 
wrote:

> Thanks Alexander, will try
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Fri, Jan 29, 2016 at 3:49 PM, Alexander Garagatyi <
> agaraga...@codenvy.com> wrote:
>
>> Replace content of che.sh with
>> https://gist.githubusercontent.com/garagatyi/5fe3f7abc0732a794391/raw/127bcf8ce3922721bac33ee8c214cce290859bc9/che.sh
>>
>> On Fri, Jan 29, 2016 at 11:39 AM, Awanthika Senarath 
>> wrote:
>>
>>> Could you please send me the script that you are working with? the
>>> script that is available in the pack is somewhat different to the script in
>>> your git repo.
>>>
>>> It would be great if you could send me the exact script that I need to
>>> start Che with.
>>>
>>> Regards
>>> Awanthika
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> On Fri, Jan 29, 2016 at 3:05 PM, Alexander Garagatyi <
>>> agaraga...@codenvy.com> wrote:
>>>
 I'm working on ubuntu 14.04 and everything is ok.

 Please, try to update your version of Che.
 Provide output of *bash --version*
 Also comment these lines

 https://github.com/codenvy/che/blob/master/assembly-main/src/assembly/bin/che.sh#L14

 https://github.com/codenvy/che/blob/master/assembly-main/src/assembly/bin/che.sh#L17
 And add *ps ax | grep che.sh *on top of the script. Then send here
 output of this command and *bash --version*


 On Fri, Jan 29, 2016 at 8:52 AM, Awanthika Senarath >>> > wrote:

> My ubuntu version : 14.04
>
>
> Attached is the script im running,
>
> I also tried deleting the first two lines of the script as well.
>
> I have docker info as below:
>
> Client:
>  Version:  1.9.1
>  API version:  1.21
>  Go version:   go1.4.2
>  Git commit:   a34a1d5
>  Built:Fri Nov 20 13:12:04 UTC 2015
>  OS/Arch:  linux/amd64
>
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Wed, Jan 27, 2016 at 2:56 PM, Alexander Garagatyi <
> agaraga...@codenvy.com> wrote:
>
>> Please provide your version of ubuntu, bash and attach exact script
>> that you launched (including your changes). Thank you.
>>
>> On Wed, Jan 27, 2016 at 4:49 AM, Awanthika Senarath <
>> awanth...@wso2.com> wrote:
>>
>>> Hello Alexander,
>>>
>>> I tried by removing the first two lines that was causing the issue
>>> from the script, which resulted in the error [1]. I removed the lines
>>>
>>> set -e
>>> set -o pipefail, from the script which I assume cause the whole
>>> script to exit on failure according to [2].
>>>
>>> Any idea on how to get it to running?
>>>
>>>
>>>
>>> [1]
>>>
>>> trap: SIGHUP: bad trap
>>> che.sh: 19: che.sh: function: not found
>>> che.sh: 98: che.sh: Syntax error: "}" unexpected
>>>
>>> [2] https://sipb.mit.edu/doc/safe-shell/
>>>
>>> thanks and regards
>>> Awanthika
>>>
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> On Tue, Jan 26, 2016 at 4:54 PM, Awanthika Senarath <
>>> awanth...@wso2.com> wrote:
>>>
 Hello Alexander,

 Thanks, will try it out.

 Awanthika Senarath
 Software Engineer, WSO2 Inc.
 Mobile: +94717681791



 On Tue, Jan 26, 2016 at 2:11 PM, Alexander Garagatyi <
 agaraga...@codenvy.com> wrote:

> Hi!
>
> This check fails because you use shell that doesn't support it. I
> think we should remove this check. I'll submit PR for that.
> To workaround that you can try start che inside bash shell or
> remove that line
> 
> .
>
> On Tue, Jan 26, 2016 at 5:46 AM, Awanthika S

Re: [Dev] How to add patch improvements for Developer Studio update site

[Awanthika Senarath]

Further, please find the below corrections in the method described above



1) Build the product with fix.
2) Navigate to below location in builder machine and create a folder called
"feature-updater" inside the product where the fix should be applied.
/home/developerstudio/wso2/developer-studio/

for example:if the fix is for ESB , then navigate to
 /home/developerstudio/wso2/developer-studio/esb and create the folder
called "feature-updater" in it.

ESB product already contains the feature-updater tool and you need to get
the publish.sh script from that location. If you are providing a fix for
some other product tool create the folder in the root level of that product
tool source and copy the publish.sh file from the ESB/feature-updater
location
3) then create the two folders  as features and plugins inside
feature-updater folder.
the features and plugins folders should be created inside the
feature-updater/p2 folder. it should be inside p2 folder from where the
publish.sh script resides
4) then add the feature jar to the features folder and the plugin jars
related to the feature inside the plugins folder.
5) Extract a eclipse distribution and give it's path as eclipse_home in the
publish.sh script
6) Execute the script
7) while it runs, it asks for the feature. Give the feature name without
the version
8) Script will create a newP2 which will contain p2 of the fix
9) then navigate to the below location. Create a folder with patch number
under updates. Please note, below location points to esb.

/home/developerstudio/public_html/developer-studio-kernel/4.0.0/esb-tools/updates
10) Copy the p2 (which is created in step 8) inside the newly created patch
folder
11)then update the compositeArtifacts.xml and compositeContent.xml to add
the new patch folder

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Tue, Feb 2, 2016 at 8:06 AM, Awanthika Senarath 
wrote:

> I have tried working on that but it did not work in reading the
> feature.xml file and copying the relevant jars.
>
> it is doable though. It should be easier to read it from a text file and
> copy the jars.
>
> Regards
> Awanthika
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Mon, Feb 1, 2016 at 3:27 PM, Rajeeva Uthayasangar 
> wrote:
>
>>
>>
>> On Mon, Feb 1, 2016 at 3:15 PM, Susinda Perera  wrote:
>>
>>>
>>>
>>> On Mon, Feb 1, 2016 at 2:04 PM, Rajeeva Uthayasangar 
>>> wrote:
>>>
 Hi Nuwan,

 Please follow the steps:

 1) Build the product with fix.
 2) Navigate to below location in builder machine and create a folder
 called "feature-updater" inside the product where the fix should be 
 applied.
 /home/developerstudio/wso2/developer-studio/

 for example:if the fix is for ESB , then navigate to
  /home/developerstudio/wso2/developer-studio/esb and create the folder
 called "feature-updater" in it.
 3) then create the two folders  as features and plugins inside
 feature-updater folder.

>>> @ Rajeewa : I think we can automate these folder creation in the
>>> publish.sh script
>>>
>>
>> If we automate the folder creation, we need to automate the copying jars
>> part as well. In that case, we need to point the location  and name of the
>> jars. Those we can give a text file and read from there.
>>
>>>
>>>
 4) then add the feature jar to the features folder and the plugin jars
 related to the feature inside the plugins folder.
 5) Extract a eclipse distribution and give it's path as eclipse_home in
 the publish.sh script
 6) Execute the script
 7) while it runs, it asks for the feature. Give the feature name
 without the version

>>> But we have to make sure the version is correct in the script. (This
>>> will work for 4.0.0 but if you use the same script without modifying for a
>>> new version, this will not work)
>>>
>>>
 8) Script will create a newP2 which will contain p2 of the fix
 9) then navigate to the below location. Create a folder with patch
 number under updates. Please note, below location points to esb.

 /home/developerstudio/public_html/developer-studio-kernel/4.0.0/esb-tools/updates
 10) Copy the p2 (which is created in step 8) inside the newly created
 patch folder
 11)then update the compositeArtifacts.xml and compositeContent.xml to
 add the new patch folder

 thanks
 Rajeeva.

 On Mon, Feb 1, 2016 at 12:52 PM, Nuwan Pallewela 
 wrote:

> Hi All,
>
> What is the process for adding improvements done for a patch, to
> Developer Studio update site?
>
> Thanks,
> Nuwan
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

[Rajeenthini Satkunam]

Hi sajith,

Noted and thank you for the suggestions.

On Mon, Feb 1, 2016 at 11:53 PM, Sajith Ariyarathna 
wrote:

> Hi Rajeenthini,
>
> You are hoping to add the following code snippet to the serializeJSON
> method [1] of the org.jaggeryjs.scriptengine.util.HostObjectUtil class.
>
>> String JsonString = null;
>> try{
>> ObjectMapper mapper = new ObjectMapper();
>> JsonString = mapper.writeValueAsString(obj);
>> }catch (Exception e){
>> System.out.println(e.getMessage());
>> }
>>
>> return "{\"javaObject\":\"true\",\"object\":\"" + JsonString + "\"}";
>>
>> There are few issue in this code snippet.
>
>- Don't catch generic Exception, always catch a specific exception. In
>here you should catch JsonProcessingException [2].
>- Don't use System.out.println to log exceptions. Instead use a proper
>logger. HostObjectUtil class has a log object defined in line 30 [3],
>you can use that.
>- Returning '{"javaObject": "true", "object": "{ ... }"}' string gives
>a wrong impression that there are two attributes called 'javaObject' &
>'object' in the logged object. I think just returning the JSON string will
>be enough.
>
> After corrections (I also took the liberty to reduce no of lines):
>
> try {
>
> return (new ObjectMapper()).writeValueAsString(obj);
>
> } catch (JsonProcessingException e) {
>
> log.debug("Object " + obj.toString() + " of class " + obj.getClassName() +
> " cannot be converted to JSON");
>
> }
>
> return "{}";
>
>
> [1]
> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L78
> [2]
> https://static.javadoc.io/com.fasterxml.jackson.core/jackson-databind/2.6.3/com/fasterxml/jackson/databind/ObjectMapper.html#writeValueAsString(java.lang.Object)
> [3]
> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L30
>
> Thanks.
>
>
> On Mon, Feb 1, 2016 at 8:13 PM, Rajeenthini Satkunam  > wrote:
>
>> Hi sajith,
>>
>> i have added this Student class for example.As for current implementation
>> goes like this way in Jaggery below.
>>
>> public static String serializeJSON(Object obj) {
>> if (obj instanceof Wrapper) {
>> obj = ((Wrapper) obj).unwrap();
>> }
>> if (obj == null) {
>> return "null";
>> }
>> if (obj instanceof Undefined) {
>> return "null";
>> }
>> if (obj instanceof Boolean) {
>> return Boolean.toString((Boolean) obj);
>> }
>> if (obj instanceof String) {
>> return serializeString((String) obj);
>> }
>> if (obj instanceof ConsString) {
>> return serializeString(obj.toString());
>> }
>> if (obj instanceof Number) {
>> return obj.toString();
>> }
>> if (obj instanceof XMLObject) {
>> return serializeString(serializeXML((ScriptableObject) obj));
>> }
>> if (obj instanceof NativeObject) {
>> return serializeNativeObject((NativeObject) obj);
>> }
>> if (obj instanceof NativeArray) {
>> return serializeNativeArray((NativeArray) obj);
>> }
>> if (obj instanceof Object[]) {
>> return serializeObjectArray((Object[]) obj);
>> }
>> if (obj instanceof Scriptable) {
>> Scriptable object = (Scriptable) obj;
>> String jsClass = object.getClassName();
>> if ("Date".equals(jsClass)) {
>> return serializeString(serializeNativeDate(object));
>> } else if ("Error".equals(jsClass)) {
>> return serializeString(serializeNativeError(object));
>> }
>> }
>> String JsonString = null;
>> try{
>> ObjectMapper mapper = new ObjectMapper();
>> JsonString = mapper.writeValueAsString(obj);
>> }catch (Exception e){
>> System.out.println(e.getMessage());
>> }
>>
>> return "{\"javaObject\":\"true\",\"object\":\"" + JsonString + "\"}";
>> }
>>
>> AFAIU since we are parsing Object type of argument It is better we can
>> use ObjectMapper.Correct me If I am wrong.Your suggestion would be more
>> appreciated.
>>
>> On Sun, Jan 31, 2016 at 10:23 AM, Sajith Ariyarathna 
>> wrote:
>>
>>> Hi Rajeenthini,
>>>
>>> AFAIK ability to convert a POJO into JSON object does nor affect the
>>> output of a Jaggery Log of that POJO.
>>> To get a proper log output for a Java object, you need to implement the
>>> "toString" method in that Java class. For example in your case,
>>>
>>> public class Student {
>>>
>>> ...
>>>
>>> public String toString() {
>>>
>>> return "{name: " + this.name + ", age: " + this.age + ", indexNo: " +
>>> this.indexNo + "}";
>>>
>>> }
>>>
>>> }
>>>
>>> Now you can log a Student object in your Jaggery code as following.
>>>
>>> log.info(studentObj.toString());
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> On Sat, Jan 30, 2016 at 9:28 PM, Rajeenthini Satkunam

[Dev] Null pointer exception when running Test cases

[Menaka Jayawardena]

Hello,

I get this exception when trying to run tests in IOT server.

But all test cases are running without any problem.

Feb 02, 2016 10:44:42 AM
org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension

WARNING: Failed to initializing the Extension Class
Feb 02, 2016 10:44:42 AM
org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension

SEVERE: Error initializing the Automation Context
java.lang.NullPointerException
at
org.wso2.carbon.automation.engine.extensions.ListenerExtension.setParameterMap(ListenerExtension.java:51)
at
org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension.(ExecutionListenerExtension.java:31)
at
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.(CarbonServerExtension.java:29)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:383)
at
org.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.initiate(TestNGExtensionExecutor.java:97)
at
org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionStart(TestExecutionListener.java:46)
at org.testng.TestNG.runExecutionListeners(TestNG.java:1068)
at org.testng.TestNG.run(TestNG.java:1015)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)


I debugged the test platform and the parameter map gets null.

What could be the reason for this?


Thanks and regards
Menaka Madusanka

-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS Authenticator] Issue in logout from mailchimp authenticator

[Hariprasath Thanarajah]

Hi All,

I have implemented mailChimp Authenticator for IS. When I logout from
sample webapp(travelocity.com) i got the below error,

[2016-02-02 11:41:01,907] ERROR
{org.wso2.carbon.identity.sso.saml.processors.SPInitLogoutRequestProcessor}
-  ssoTokenId cookie not found in the logout request


Any suggestions?

-- 


*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev