[Dev] How to get the page title of a dashboard page

[Kalpa Welivitigoda]

Hi devs,

I have a dashboard with multiple pages. From a gadget in a page, I need to
get the current page title. What would be the recommended approach to do
this?



-- 
Best Regards,

Kalpa Welivitigoda
Senior Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB][3.2.0][Analytics] Remove metrics view from product distribution

[Isuru Perera]

+1 for removing "Messaging Metrics". Let's keep "JVM Metrics" for now.
Since we don't have gadgets for JVM Metrics yet. That means we need to keep
JDBC Reporter as well.


On Fri, Aug 19, 2016 at 2:29 PM, Srinath Perera  wrote:

> Yes, plan is to drop those UI from admin console
>
> On Fri, Aug 19, 2016 at 2:12 PM, Indika Sampath  wrote:
>
>> We have set default reporter to JDBC in metrics.xml with product-mb
>> distribution. IMO, if we are planning to remove messaging metrics page,
>> then no use of having JDBC reporter as well.
>>
>> On Fri, Aug 19, 2016 at 2:08 PM, Ramith Jayasinghe 
>> wrote:
>>
>>> since MB v 3.0.0, it included carbon-matrices lib and there are graphs
>>> to show useful statistics.
>>> (Management Console -> Monitor -> Messaging Metrics).
>>>
>>> However, given that we are going to ship a analytics-mb distribution. Do
>>> we need to have this GUI/page in management console?
>>>
>>> --
>>> Ramith Jayasinghe
>>> Technical Lead
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> E: ram...@wso2.com
>>> P: +94 772534930
>>>
>>
>>
>>
>> --
>> Indika Sampath
>> Senior Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>
>
> --
> 
>WSO2 Inc. http://wso2.com
>Blog: http://srinathsview.blogspot.com/
>Photos: http://www.flickr.com/photos/hemapani/ twitter:@srinath_perera
>Site: http://people.apache.org/~hemapani/
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Orbit] Adding Storm 00.10.1 orbit bundle

[Sajith Ravindra]

Hi Kernal team,

Could you please review and merge the pull request
https://github.com/wso2/orbit/pull/226 to add the new storm version 0.10.1.

Thanks
*,Sajith Ravindra*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 2273550
blog: http://sajithr.blogspot.com/

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

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Nisala Nanayakkara]

Hi all,

I have scheduled a meeting on Wednesday afternoon to discuss about this
matter.

Thanks,
Nisala

On Mon, Aug 22, 2016 at 10:52 AM, Sinthuja Ragendran 
wrote:

> Hi Susinda,
>
> On Mon, Aug 22, 2016 at 10:16 AM, Susinda Perera  wrote:
>
>>
>>
>> On Sun, Aug 21, 2016 at 5:06 PM, Sinthuja Ragendran 
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> So lets create a new repo for our new maven plugin, and lets include
>>> source there as per Susinda.
>>>
>>> @Susinda,
>>> Can you please elaborate bit more with what is the expected outcome when
>>> DevS based tooling using this maven plugin for DS? Because in the context,
>>> DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
>>> intend to provide that sort of functionality with DevS. Therefore IMO we
>>> can maximum provide xml, js, css, jag file editors and lets them to create
>>> the structure of Capp from DevS. IMO creating such extension support will
>>> have considerable effort.
>>>
>>
>> Hi Sinthuja
>> Just had a chat with Nisala,
>> Expected outcome of DevS tooling was to make the developer's life easy on
>> creating dashboards, gadgets, layouts an themes. We have in built support
>> coming from eclipse for xml, html, css etc and we had jaggery editor with
>> code completion features. So I believe we can integrate these bits and
>> pieces and provide a IDE based tooling. As all developers are not command
>> line developers, I believe providing this kind of tooling would be useful
>> for general users.
>> As you already have maven build (packaging) tool and Capp tool for the
>> same, my suggestion is to introduce arch-type, then we can reuse use of
>> same arch-type and maven plugins to create the eclipse IDE plugin. So at
>> the end of the day we will have both command line and IDE based tooling.
>> WDYT?
>>
>
> Basically IMO IDE support is needed for creating custom gadgets and custom
> layouts. But the other parts such as creating dashboards, creating pages
> with default layouts, integrating gadgets into the dashboard pages, etc are
> provided from DS itself, and it's just drag and drop. And hence I don't
> think we need to provide same set of functionality which is already covered
> in DS, rather we need to focus on the point where users could create custom
> gadgets, and layouts which is the dev effort for the users in the context
> of DS. I don't think we can provide such DevS support feature for this
> release given the short time frame now.
>
> But anyhow lets have a discussion on this, come to our plan so that we can
> execute this on the future releases. @Nisala, please schedule a meeting
> Wednesday after noon or Thursday.
>
> Thanks,
> Sinthuja.
>
>
>> Thanks
>> Susinda
>>
>>
>>
>>
>>
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi,

 Thanks for prompt reply. I will arrange a meeting to discuss this
 matter.

 Thanks,
 Nisala

 On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera 
 wrote:

> Hi Nisala
>
> We may need to create a new repo and host these maven plugins. As an
> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
> maintain the maven plugins. As we already have the maven plugins i think 
> we
> can easily build the DevStudio based tooling with using these plugins.
> Please arrange a time to discuss this.
>
> [1] - https://github.com/wso2/maven-tooling-esb
> [2] - https://github.com/wso2/maven-tooling-bps
>
>
>
> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi,
>>
>> I have implemented maven - plugins for each artifacts in WSO2
>> Dashboard Server. So there are four maven - plugins for
>> dashboards,gadgets,layouts and themes which can be used to generate a CAR
>> file consisting with these artifacts. But we are not very much clear 
>> about
>> where we have to maintain these maven - plugins. Is it better to keep it
>> within our carbon-dashboards repository ? Or is it better to maintain 
>> these
>> as a separate repository.
>>
>> @DevStudioTeam : Can you provide recommended way of maintaining these
>> maven-plugins ?
>>
>> Thanks,
>> Nisala
>>
>> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
>> wrote:
>>
>>> Do we have tooling support for this new release, like
>>> create/edit/deploy gadgets/dashboards etc. If not shall we add this to
>>> roadmap. DevS team will be able to help on this task.
>>>
>>> Thanks
>>> Susinda
>>>
>>> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar >> > wrote:
>>>
 WSO2 Dashboard Server 2.1.0-Alpha Released!

 WSO2 Dashboard Server team is pleased to announce the release of

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Sinthuja Ragendran]

Hi Susinda,

On Mon, Aug 22, 2016 at 10:16 AM, Susinda Perera  wrote:

>
>
> On Sun, Aug 21, 2016 at 5:06 PM, Sinthuja Ragendran 
> wrote:
>
>> Hi Nisala,
>>
>> So lets create a new repo for our new maven plugin, and lets include
>> source there as per Susinda.
>>
>> @Susinda,
>> Can you please elaborate bit more with what is the expected outcome when
>> DevS based tooling using this maven plugin for DS? Because in the context,
>> DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
>> intend to provide that sort of functionality with DevS. Therefore IMO we
>> can maximum provide xml, js, css, jag file editors and lets them to create
>> the structure of Capp from DevS. IMO creating such extension support will
>> have considerable effort.
>>
>
> Hi Sinthuja
> Just had a chat with Nisala,
> Expected outcome of DevS tooling was to make the developer's life easy on
> creating dashboards, gadgets, layouts an themes. We have in built support
> coming from eclipse for xml, html, css etc and we had jaggery editor with
> code completion features. So I believe we can integrate these bits and
> pieces and provide a IDE based tooling. As all developers are not command
> line developers, I believe providing this kind of tooling would be useful
> for general users.
> As you already have maven build (packaging) tool and Capp tool for the
> same, my suggestion is to introduce arch-type, then we can reuse use of
> same arch-type and maven plugins to create the eclipse IDE plugin. So at
> the end of the day we will have both command line and IDE based tooling.
> WDYT?
>

Basically IMO IDE support is needed for creating custom gadgets and custom
layouts. But the other parts such as creating dashboards, creating pages
with default layouts, integrating gadgets into the dashboard pages, etc are
provided from DS itself, and it's just drag and drop. And hence I don't
think we need to provide same set of functionality which is already covered
in DS, rather we need to focus on the point where users could create custom
gadgets, and layouts which is the dev effort for the users in the context
of DS. I don't think we can provide such DevS support feature for this
release given the short time frame now.

But anyhow lets have a discussion on this, come to our plan so that we can
execute this on the future releases. @Nisala, please schedule a meeting
Wednesday after noon or Thursday.

Thanks,
Sinthuja.


> Thanks
> Susinda
>
>
>
>
>
>>
>> Thanks,
>> Sinthuja.
>>
>> On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi,
>>>
>>> Thanks for prompt reply. I will arrange a meeting to discuss this matter.
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera 
>>> wrote:
>>>
 Hi Nisala

 We may need to create a new repo and host these maven plugins. As an
 example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
 maintain the maven plugins. As we already have the maven plugins i think we
 can easily build the DevStudio based tooling with using these plugins.
 Please arrange a time to discuss this.

 [1] - https://github.com/wso2/maven-tooling-esb
 [2] - https://github.com/wso2/maven-tooling-bps



 On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
 wrote:

> Hi,
>
> I have implemented maven - plugins for each artifacts in WSO2
> Dashboard Server. So there are four maven - plugins for
> dashboards,gadgets,layouts and themes which can be used to generate a CAR
> file consisting with these artifacts. But we are not very much clear about
> where we have to maintain these maven - plugins. Is it better to keep it
> within our carbon-dashboards repository ? Or is it better to maintain 
> these
> as a separate repository.
>
> @DevStudioTeam : Can you provide recommended way of maintaining these
> maven-plugins ?
>
> Thanks,
> Nisala
>
> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
> wrote:
>
>> Do we have tooling support for this new release, like
>> create/edit/deploy gadgets/dashboards etc. If not shall we add this to
>> roadmap. DevS team will be able to help on this task.
>>
>> Thanks
>> Susinda
>>
>> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
>> wrote:
>>
>>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>>
>>> WSO2 Dashboard Server team is pleased to announce the release of
>>> WSO2 Dashboard Server 2.1.0 Alpha. This release comes with the following
>>> bug fixes, improvements and tasks. You can download the distribution 
>>> from
>>> [1] and view the documentation at [2].
>>> Bug
>>>
>>>- [UES-990 ] - All the
>>>query params get appended to the url 

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.9 RC1

[Thusitha Thilina Dayaratne]

Hi DSS/IS Team,

Can IS and DSS teams test their products with the carbon kernel 4.4.9 and
vote?

Thanks
Thusitha

On Sat, Aug 20, 2016 at 12:22 AM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Devs,
>
> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.9.
>
> This release fixes the following issues
> *https://wso2.org/jira/issues/?filter=13289
> *
>
> Please download, test your products with kernel 4.4.9 RC1 and vote. Vote
> will be open for 72 hours or as longer as needed.
>
> *Source and binary distribution files:*
> *https://github.com/wso2/carbon-kernel/archive/v4.4.9-rc1.zip
> *
> http://svn.wso2.org/repos/wso2/people/thusithad/4.4.9/
> wso2carbon-4.4.9-rc1.zip
>
> *Maven staging repository*
> *https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1035
> *
>
> *The tag to be voted upon : *
> *https://github.com/wso2/carbon-kernel/releases/tag/v4.4.9-rc1
> *
>
> [ ] Broken - Do not release (explain why)
> [ ] Stable  - Go ahead and release
>
> Thank you
> Carbon Team
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>


-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

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

Re: [Dev] wso2 DAS 3.1.0 RC1 dashboard browser compatility issues

[Dakshika Jayathilaka]

Hi Aneela,

What is the Firefox version that you are using?

Regards,

*Dakshika Jayathilaka*
PMC Member & Committer of Apache Stratos
Associate Technical Lead
WSO2, Inc.
lean.enterprise.middleware
0771100911

On Sun, Aug 21, 2016 at 6:18 PM, Aneela Safdar  wrote:

> Hi,
>
> I have been working on CEP for a while and now for some reasons I got
> shifted from CEP to DAS. I copied all receivers, streams, execution plans
> and publishers along with gadgets that I created in CEP to corresponding
> directories of DAS. However there seems to be some rendering issues of DAS
> dashboard with browser. After creating a dashboard and respective pages
> when I try to add gadgets in pages, they dont seem to be loaded and
> clicking is appearing ineffective at all.
>
> As I said there are some rendering issues, the main page on *mozilla
> firefox* looks like this
>
> [image: Inline image]
>
> Though browser is updated. I tried with *chrome *which renders main page
> quite nicely but I am still unable to load different pages and add gadgets
> to them.
>
> [image: Inline image]
>
> Any suggestions?
>
> Regards, Aneela Safdar
>
> ___
> 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

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Susinda Perera]

On Sun, Aug 21, 2016 at 5:06 PM, Sinthuja Ragendran 
wrote:

> Hi Nisala,
>
> So lets create a new repo for our new maven plugin, and lets include
> source there as per Susinda.
>
> @Susinda,
> Can you please elaborate bit more with what is the expected outcome when
> DevS based tooling using this maven plugin for DS? Because in the context,
> DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
> intend to provide that sort of functionality with DevS. Therefore IMO we
> can maximum provide xml, js, css, jag file editors and lets them to create
> the structure of Capp from DevS. IMO creating such extension support will
> have considerable effort.
>

Hi Sinthuja
Just had a chat with Nisala,
Expected outcome of DevS tooling was to make the developer's life easy on
creating dashboards, gadgets, layouts an themes. We have in built support
coming from eclipse for xml, html, css etc and we had jaggery editor with
code completion features. So I believe we can integrate these bits and
pieces and provide a IDE based tooling. As all developers are not command
line developers, I believe providing this kind of tooling would be useful
for general users.
As you already have maven build (packaging) tool and Capp tool for the
same, my suggestion is to introduce arch-type, then we can reuse use of
same arch-type and maven plugins to create the eclipse IDE plugin. So at
the end of the day we will have both command line and IDE based tooling.
WDYT?

Thanks
Susinda





>
> Thanks,
> Sinthuja.
>
> On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi,
>>
>> Thanks for prompt reply. I will arrange a meeting to discuss this matter.
>>
>> Thanks,
>> Nisala
>>
>> On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera 
>> wrote:
>>
>>> Hi Nisala
>>>
>>> We may need to create a new repo and host these maven plugins. As an
>>> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
>>> maintain the maven plugins. As we already have the maven plugins i think we
>>> can easily build the DevStudio based tooling with using these plugins.
>>> Please arrange a time to discuss this.
>>>
>>> [1] - https://github.com/wso2/maven-tooling-esb
>>> [2] - https://github.com/wso2/maven-tooling-bps
>>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi,

 I have implemented maven - plugins for each artifacts in WSO2 Dashboard
 Server. So there are four maven - plugins for dashboards,gadgets,layouts
 and themes which can be used to generate a CAR file consisting with these
 artifacts. But we are not very much clear about where we have to maintain
 these maven - plugins. Is it better to keep it within our carbon-dashboards
 repository ? Or is it better to maintain these as a separate repository.

 @DevStudioTeam : Can you provide recommended way of maintaining these
 maven-plugins ?

 Thanks,
 Nisala

 On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
 wrote:

> Do we have tooling support for this new release, like
> create/edit/deploy gadgets/dashboards etc. If not shall we add this to
> roadmap. DevS team will be able to help on this task.
>
> Thanks
> Susinda
>
> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
> wrote:
>
>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>
>> WSO2 Dashboard Server team is pleased to announce the release of WSO2
>> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
>> fixes, improvements and tasks. You can download the distribution from [1]
>> and view the documentation at [2].
>> Bug
>>
>>- [UES-990 ] - All the
>>query params get appended to the url when navigating via hierarchical 
>> menu
>>- [UES-1016 ] - Tenant ID
>>is always super tenant ID in Gadget Generation Wizard
>>- [UES-1018 ] - DS Console
>>differs from the WSO2 theme
>>- [UES-1022 ] - Product
>>version in footer is incorrect
>>- [UES-1023 ] - Create
>>view menu rendered incorrectly
>>- [UES-1028 ] - Creating
>>gadgets in third-party store - Thumbnail image does not show
>>
>> Improvement
>>
>>- [UES-970 ] - Add download
>>functionality to gadgets listed
>>- [UES-995 ] - Having a
>>landing page for a dashboard is optional
>>- [UES-1003 ] - Modify the
>>ES extension to not allow the assets to be editable 

[Dev] Calling Basic Auth Backend from ESB

[Akalanka Pagoda Arachchi]

Hi All,

I am having trouble calling basic Auth backend from ESB 4.9.0. I have a DSS
service secured by basic Auth using the attached WS Policy file
(WSPolicy-UsernameToken.xml).

I can call this service successfully from SOAP UI by adding 'Authorization'
header.

To call this service from ESB I went through few examples on the web as [1]
which explain to add a property with the 'Authorization' details. When I
use the Call Mediator and invoke the secure DSS service using this method,
I am getting HTTP 500 with below soap fault. There are no errors/logs on
DSS server.

http://www.w3.org/2003/05/soap-envelope;>
   
  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
1.0.xsd">
 http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
2016-08-22T03:27:59.437Z
2016-08-22T03:32:59.437Z
 
  
   
   
  
 
soapenv:Receiver
 
 
InvalidSecurity
 
 
  
   


I enabled the wire logs from ESB and 'Authorization' header is available in
the outgoing message.
I logged the 'Authorization' header from DSS and it is properly received
from the DSS as well.

Looks to me like I'm doing this wrong but cannot figure out what. Any help
is much appreciated.


[1] -
http://xacmlinfo.org/2014/08/20/how-to-esb-invoking-basic-auth-secured-backend-service/
​
 WSPolicy-UsernameToken.xml

​

Thanks,
Akalanka.

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

[Dev] My GSoC experience - GSoC students please read!

[Abhishek Tiwari]

Hello Everyone,

There are some organizations that looks at GSoC as getting free labour and
use it to get as much done as they can within 3 months time, WSO2 is one of
them. I was working 60 hours a week and never received any appreciation
from mentors. It was very disappointing but I always kept a positive
attitude and tried to meet all the deadlines. Mentors were very
unprofessional, they would agree on a meeting time and then never show up,
or they would keep delaying the meeting saying there is another meeting (I
have chat and emails to prove that). They never even cared to send an email
about it, there were so many such incidents, where I ended up waiting
hours. New requirements kept coming as they wanted to get as much work as
possible. There was no feedback on code so I did not learn anything from
code perspective, then just before 2 days mentor provided comments which
changed everything and I had rewrite most of it. The expectations from WSO2
were completely unrealistic from a student point of view. I sincerely hope
that Google looks into it.

Yesterday I was having a hangout call (over a weekend) to discuss the newly
created issues and I was trying to convince that I should work on the high
priority issue rather than changing the whole codebase and architecture
because there is an extra JSON parameter [2]. My mentor shouted at me and
threatened to fail me in the evaluation. This is very disheartening as I
have worked so hard on this project. My college is already started and I am
taking  leaves to work on the project. If anyone else has experienced
similar situations in WSO2, I would recommend reaching out to GSoC
officials as I have done already.

I am a 19 year old, first year engineering student (Freshman). All these
skills I learnt by myself. In the span of GSoC project, I had to learn
Docker, Dockerfiles, Puppet, Kubernetes, Bash scripting, Go language, WSO2
codebase and many other things. It is evident from the code that I have
written so far [1]. It is very easy to judge someone without being in their
shoes, and I feel like my mentors have been pushing work and standards
without caring about my experience level, which in my opinion is completely
unfair.

I am sure there are so many other great mentors in the organization and my
experience might be just one off. However, if any other student has felt
similar situations, it should be investigated.

Thanks
Abhishek

[1]. https://github.com/abhishek0198/wso2dockerfiles-test-
framework/commits/master
[2]. https://github.com/abhishek0198/wso2dockerfiles-
test-framework/issues/22
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] wso2 DAS 3.1.0 RC1 dashboard browser compatility issues

[Aneela Safdar]

Hi,
I have been working on CEP for a while and now for some reasons I got shifted 
from CEP to DAS. I copied all receivers, streams, execution plans and 
publishers along with gadgets that I created in CEP to corresponding 
directories of DAS. However there seems to be some rendering issues of DAS 
dashboard with browser. After creating a dashboard and respective pages when I 
try to add gadgets in pages, they dont seem to be loaded and clicking is 
appearing ineffective at all. 

As I said there are some rendering issues, the main page on mozilla firefox 
looks like this

 Though browser is updated. I tried with chrome which renders main page quite 
nicely but I am still unable to load different pages and add gadgets to them.


Any suggestions?

Regards, Aneela Safdar___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Isuru Haththotuwa]

Hi Abhishek,

Reported two more issues for the usage of grep command [1, 2]. The fixes
are straightforward.

[1].
https://github.com/abhishek0198/wso2dockerfiles-test-framework/issues/29

[2].
https://github.com/abhishek0198/wso2dockerfiles-test-framework/issues/30

On Fri, Aug 19, 2016 at 1:47 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi Thanuja,
>
> I have added the fix to look for ERROR level rather than any error
> keyword. Please test it and let me know if it fixes the issue.
>
> The new repository URL is [1].
>
> Thanks
> Abhishek
>
> [1]. https://github.com/abhishek0198/wso2dockerfiles-test-framework
>
> On Thu, Aug 18, 2016 at 10:49 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi Thanuja,
>>
>> Thanks a lot of using the test framework and pointing out the issue. The
>> check of errors in carbon log is dumb at this point. I will change it look
>> for the correct logging level to find errors.
>>
>> Imesh,
>> Sincerely appreciate code level feedback and creating issues on Github. I
>> will address all these shortly.
>>
>> Thanks
>> Abhishek
>>
>> On Thu, Aug 18, 2016 at 2:39 AM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi Abhishek,
>>>
>>> Great work on Dockerfiles test framework!!! I have used the test
>>> framework to check the flow of building and running WSO2 BPS 3.5.1 docker
>>> image. According to the framework log[1], the test fails because of an
>>> error in the carbon server log. But when I check the carbon server log,
>>> there were no *ERROR* logs and it has 'error' as part of a word in
>>> line[2].
>>>
>>> For this scenario, we should not make the test to be failed. I think
>>> instead of simply grepping the 'error' word as in[3], we should grep the
>>> *ERROR* logs.
>>>
>>> [1].
>>> 2016/08/18 14:20:28 main.go:151: Starting test setup up
>>> 2016/08/18 14:20:28 main.go:154: Completed test setup up
>>> 2016/08/18 14:20:28 main.go:106: Running tests for wso2bps, 3.5.1, using
>>> puppet provisioning, under default platform.
>>> 2016/08/18 14:20:28 common-utils.go:37: Starting building image...
>>> 2016/08/18 14:20:57 common-utils.go:45: Successfully built docker image.
>>> 2016/08/18 14:20:57 common-utils.go:85: No errors were found in docker
>>> build logs
>>> 2016/08/18 14:20:57 common-utils.go:58: Running image...
>>> 2016/08/18 14:20:59 common-utils.go:66: Successfully ran docker image.
>>> 2016/08/18 14:20:59 common-utils.go:98: No errors were found in docker
>>> run logs
>>> 2016/08/18 14:20:59 common-utils.go:130: Attempt: 1. Port 9763 is not
>>> open in the docker container.
>>> 2016/08/18 14:20:59 common-utils.go:133: Sleeping for 2 seconds
>>> 2016/08/18 14:21:01 common-utils.go:130: Attempt: 2. Port 9763 is not
>>> open in the docker container.
>>> 2016/08/18 14:21:01 common-utils.go:133: Sleeping for 4 seconds
>>> 2016/08/18 14:21:05 common-utils.go:130: Attempt: 3. Port 9763 is not
>>> open in the docker container.
>>> 2016/08/18 14:21:05 common-utils.go:133: Sleeping for 6 seconds
>>> 2016/08/18 14:21:11 common-utils.go:130: Attempt: 4. Port 9763 is not
>>> open in the docker container.
>>> 2016/08/18 14:21:11 common-utils.go:133: Sleeping for 8 seconds
>>> 2016/08/18 14:21:19 common-utils.go:136: Port 9763 is open in the docker
>>> container.
>>> 2016/08/18 14:21:19 common-utils.go:136: Port 9443 is open in the docker
>>> container.
>>> 2016/08/18 14:21:20 common-utils.go:153: Carbon server is up and running.
>>> 2016/08/18 14:21:20 common-utils.go:166: Checking Carbon server logs for
>>> any errors
>>> 2016/08/18 14:21:20 docker-utils.go:105: Successfully copied carbon
>>> server logs from docker container
>>> 2016/08/18 14:21:20 common-utils.go:173: Errors founds in carbon server
>>> logs, please check them under wso2bps3.5.1logs
>>> 2016/08/18 14:21:20 main.go:146: Test completed for wso2bps, 3.5.1.
>>> 2016/08/18 14:21:20 main.go:158: Starting test clean up
>>> 2016/08/18 14:21:20 docker-utils.go:61: Stopping and removing docker
>>> container with id: 6f28d71772e6
>>> 2016/08/18 14:21:31 docker-utils.go:67: Successfully stopped and removed
>>> docker container
>>> 2016/08/18 14:21:31 docker-utils.go:43: Removing docker image
>>> wso2bps:3.5.1
>>> 2016/08/18 14:21:31 docker-utils.go:47: Successfully removed docker image
>>> 2016/08/18 14:21:31 main.go:161: Completed test clean up
>>>
>>> [2].
>>> TID: [-1234] [] [2016-08-18 08:51:15,701]  INFO
>>> {org.springframework.beans.factory.support.DefaultListableBeanFactory}
>>> -  Pre-instantiating singletons in org.springframework.beans.fact
>>> ory.support.DefaultListableBeanFactory@38d281d4: defining beans
>>> [cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProce
>>> ssor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.
>>> apache.cxf.bus.spring.BusExtensionPostProcessor,deploymentSe
>>> rvice,runtimeService,queryRuntimeService,historyService,
>>> formService,processDefinitionService,identityService,managem
>>> 

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Sinthuja Ragendran]

Hi Nisala,

So lets create a new repo for our new maven plugin, and lets include source
there as per Susinda.

@Susinda,
Can you please elaborate bit more with what is the expected outcome when
DevS based tooling using this maven plugin for DS? Because in the context,
DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
intend to provide that sort of functionality with DevS. Therefore IMO we
can maximum provide xml, js, css, jag file editors and lets them to create
the structure of Capp from DevS. IMO creating such extension support will
have considerable effort.

Thanks,
Sinthuja.

On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara  wrote:

> Hi,
>
> Thanks for prompt reply. I will arrange a meeting to discuss this matter.
>
> Thanks,
> Nisala
>
> On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera  wrote:
>
>> Hi Nisala
>>
>> We may need to create a new repo and host these maven plugins. As an
>> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
>> maintain the maven plugins. As we already have the maven plugins i think we
>> can easily build the DevStudio based tooling with using these plugins.
>> Please arrange a time to discuss this.
>>
>> [1] - https://github.com/wso2/maven-tooling-esb
>> [2] - https://github.com/wso2/maven-tooling-bps
>>
>>
>>
>> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi,
>>>
>>> I have implemented maven - plugins for each artifacts in WSO2 Dashboard
>>> Server. So there are four maven - plugins for dashboards,gadgets,layouts
>>> and themes which can be used to generate a CAR file consisting with these
>>> artifacts. But we are not very much clear about where we have to maintain
>>> these maven - plugins. Is it better to keep it within our carbon-dashboards
>>> repository ? Or is it better to maintain these as a separate repository.
>>>
>>> @DevStudioTeam : Can you provide recommended way of maintaining these
>>> maven-plugins ?
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera 
>>> wrote:
>>>
 Do we have tooling support for this new release, like
 create/edit/deploy gadgets/dashboards etc. If not shall we add this to
 roadmap. DevS team will be able to help on this task.

 Thanks
 Susinda

 On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
 wrote:

> WSO2 Dashboard Server 2.1.0-Alpha Released!
>
> WSO2 Dashboard Server team is pleased to announce the release of WSO2
> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
> fixes, improvements and tasks. You can download the distribution from [1]
> and view the documentation at [2].
> Bug
>
>- [UES-990 ] - All the query
>params get appended to the url when navigating via hierarchical menu
>- [UES-1016 ] - Tenant ID
>is always super tenant ID in Gadget Generation Wizard
>- [UES-1018 ] - DS Console
>differs from the WSO2 theme
>- [UES-1022 ] - Product
>version in footer is incorrect
>- [UES-1023 ] - Create view
>menu rendered incorrectly
>- [UES-1028 ] - Creating
>gadgets in third-party store - Thumbnail image does not show
>
> Improvement
>
>- [UES-970 ] - Add download
>functionality to gadgets listed
>- [UES-995 ] - Having a
>landing page for a dashboard is optional
>- [UES-1003 ] - Modify the
>ES extension to not allow the assets to be editable in published asset
>- [UES-1010 ] - Add shindig
>features to get the hostName,port and tenant domain
>- [UES-1012 ] - Store the
>theme level properties to dashboard.json and retrieve these theme
>properties while rendering the page
>- [UES-1014 ] - Add new
>gadget/layout button at the end of the gadget listing and layout 
> listings
>when user designs dashboard
>- [UES-1015 ] - Dashboard
>page loading icon for embeddable gadget feature
>
> Task
>
>- [UES-1005 ] - Provide
>common repository for js libraries to use in gadgets
>- [UES-1006 ] - Dashboard
>page loading icon to show after all gadgets are loaded
>- [UES-1007 

Re: [Dev] wso2das : Upgraded version with wso2cep 4.2.0

[Grainier Perera]

Hi Aneela,

>From the next immediate release, both CEP and DAS will have parallel
releases. Therefore, all the new functionalities/improvements of CEP (and
Siddhi) will get included in the DAS release as well. As for now, you can
go ahead and use DAS 3.1.0 RC1 [1].

[1] https://github.com/wso2/product-das/releases/tag/v3.1.0-RC1

Regards,

On Sun, Aug 21, 2016 at 2:57 PM, Aneela Safdar  wrote:

> Hi,
>
> As there is a new candidate release of wso2cep, 4.2.0  is available and I
> am using some of the upgraded functions in siddhi query. I need to shift
> from cep to das but the new functions are unable to compile as I downloaded
> the latest version wso2das 3.0.1.
>
> Is there any release of DAS having CEP 4.2.0 integrated??
>
> Regards,
> Aneela Safdar
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Grainier Perera
Software Engineer
Mobile : +94716122384
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] wso2das : Upgraded version with wso2cep 4.2.0

[Aneela Safdar]

Hi,
As there is a new candidate release of wso2cep, 4.2.0  is available and I am 
using some of the upgraded functions in siddhi query. I need to shift from cep 
to das but the new functions are unable to compile as I downloaded the latest 
version wso2das 3.0.1.
Is there any release of DAS having CEP 4.2.0 integrated?? Regards, Aneela Safdar___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC2016-Contact Development Team Feature

[Nathiesha Maddage]

Hi,

This is the link to the blog post regarding my project [1].
There I have added a brief introduction about the project, and how the
plugin works. I also added the links to the GitHub repositories. Since it
was advised to add the URLs of the commits, in the email I got from Google
regarding the final evaluations, I added the links of my commits as well.
Please have a look and let me know if the post is good enough for
submission.

I also created a blog post [2] on the use of the plugin, and added that
link as well in the above mentioned post[1]. Please let me know whether it
is good enough or any changes need to be done for that.

[1].
http://nathiesha.blogspot.com/2016/08/contact-development-team-feature-in.html
[2].
http://nathiesha.blogspot.com/2016/08/how-to-make-best-use-of-error-reporting.html

Thanks and regards

Nathiesha


On Sat, Aug 20, 2016 at 10:13 AM, Nathiesha Maddage <
nathieshamadd...@gmail.com> wrote:

> Hi ,
>
> Thank you for the suggestion. I started writing a blog post with all the
> repository links in it as you have suggested.
> I will send the link of the blog post as soon as possible.
>
> Thanks and regards
>
> Nathiesha
>
> On Fri, Aug 19, 2016 at 8:31 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> You already have two standalone github repos for the plugin and
>> micro-service. Furthermore, you have a fork of devs-kernel repo with the
>> code for the plugin is merged - the one you have prepared to send the pull
>> request.
>>
>> Since there are multiple places and we cannot submit a single link for
>> them - in my point of view - the best option is to write a blog post as
>> they have suggested. You can include the links to individual repos and
>> forked repo with a filter for your commits. Importantly, you can put the
>> link for pull request too - once you sent it.
>>
>> This way, everyone will have a clear picture of your work and the best
>> part - what is the final work that is going to be merged into WSO2
>> repository.
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 
>>
>> On Thu, Aug 18, 2016 at 11:55 AM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I have completed almost all of the coding part now, and working with
>>> fixing a few left errors and tidying the code.
>>>
>>> I plan to submit the plugin project, feature project and the
>>> documentation as the deliverable.
>>> For the final submission, I need to upload a URL that contains our
>>> project. For that Google has provided certain examples such as the link of
>>> Git Hub commits, a web page or a blog post, public folder in Google Drive
>>> etc. [1]
>>>
>>> What would be the best way of submission, for our project?
>>>
>>> [1]. https://developers.google.com/open-source/gsoc/help/work-product
>>>
>>>
>>> Thanks and regards
>>>
>>> Nathiesha
>>>
>>> On Thu, Aug 11, 2016 at 4:40 PM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hi Nathiesha,

 Great! We can have the meeting at 3.00pm to 4.00pm tomorrow. I will
 send the invitation. Meanwhile, please push the latest changes to github
 before the meeting.

 Thanks,

 *Kavith Lokuhewage*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com
 lean . enterprise . middleware
 Mobile - +94779145123
 Linkedin 
 Twitter 

 On Thu, Aug 11, 2016 at 4:35 PM, Nathiesha Maddage <
 nathieshamadd...@gmail.com> wrote:

> Hi Kavith,
>
> I externalized the credentials in micro-service code and implemented
> the extension point. I plan to start on OSGI services part once I finalize
> the remaining small tasks in these sections.
>
> How about tomorrow evening for the next meeting? I have lectures in
> the morning. So it would be easy if we can arrange the meeting after 2 pm.
>
> Thanks and regards
> Nathiesha
>
> On Thu, Aug 11, 2016 at 11:42 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> How is the progress on remaining tasks? As per the previous update,
>> you are already done with configuring maven build + creating a basic
>> micro-service for publishing reports, aren't you?
>>
>> The remaining work was to externalize hard coded credentials in
>> micro-service code, implement the extension point for providing different
>> JIRA keys to report errors for specific java packages and define an OSGI
>> service to be able to contribute publishers via other eclipse plugins - 
>> if
>> needed in future.
>>
>> It would be great if we can finalize these soon as we are reaching
>> towards the