[Dev] product-gw build error : wso2carbon-kernel:jar:5.0.0-m5 not found in the repo.

[Kasun Indrasiri]

Seems its not available in [1]. Any thoughts?

[ERROR] Failed to execute goal on project wso2gw: Could not resolve
dependencies for project org.wso2.carbon:wso2gw:pom:1.0.0-SNAPSHOT: The
following artifacts could not be resolved:
org.wso2.carbon:wso2carbon-kernel:jar:5.0.0-m5,
org.wso2.carbon:org.wso2.carbon.gateway.feature:jar:1.0.0-SNAPSHOT: Failure
to find org.wso2.carbon:wso2carbon-kernel:jar:5.0.0-m5 in
http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
local repository, resolution will not be reattempted until the update
interval of wso2-nexus has elapsed or updates are forced -> [Help 1]
[ERROR]


[1]
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.core/5.0.0-m5/
-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Authentication issue in accessing analytics JS API in DAS

[Dunith Dhanushka]

Hi Nayomi,

Can you try following steps after adding * to cors.allowed.origins?

1. Upload analytics-client folder to a web server. You can simply use a
Python server for this purpose [1].

2. Edit /repository/deployment/server/webapps/analytics/WEB-INF/
web.xml fileand put * to allowed origins list.

3. Invokde http://:/analytics-client/index.html



[1] https://docs.python.org/2/library/simplehttpserver.html

On Fri, Oct 23, 2015 at 11:28 AM, Nayomi Dayarathne  wrote:

> Kind reminder.
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>
> On Wed, Oct 21, 2015 at 6:52 PM, Nayomi Dayarathne 
> wrote:
>
>> Hi Gimantha,
>>
>>
>> As the per the current JS API implementation, it was not allowed to
>> access Analytics JS API of DAS due to authentication issue and got the
>> following authentication warnings when we debug the java script we have
>> written using fire bug.
>>
>> *This site makes use of a SHA-1 Certificate; it's recommended you use
>> certificates with signature algorithms that use hash functions stronger
>> than SHA-1.*
>> *Cross-Origin Request Blocked: The Same Origin Policy disallows reading
>> the remote resource at https://localhost:9443/portal/apis/analytics?type=9
>> . (Reason: CORS header
>> 'Access-Control-Allow-Origin' missing).*
>> *Cross-Origin Request Blocked: The Same Origin Policy disallows reading
>> the remote resource at https://localhost:9443/portal/apis/analytics?type=9
>> . (Reason: CORS
>> request failed).*
>>
>> We have tried this scenario locally.And CORS settings has also added to
>> the
>> /repository/deployment/server/webapps/analytics/WEB-INF/web.xml
>> file
>>
>> I have attached the relevant client files that we used to try this
>> scenario, here with.
>>
>> Could you please provide the necessary and correct information to perform
>> this properly?
>>
>> Regards,
>>
>>
>> Nayomi Dayarathne
>>
>> *Software Engineer-QA*
>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>
>> *nay...@wso2.com *
>>
>
>


-- 
Regards,

Dunith Dhanushka,
Senior Software Engineer
WSO2 Inc,

Mobile - +94 71 8615744
Blog - dunithd.wordpress.com 
Twitter - @dunithd 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Swaggers are not showing up after GReg migration 5.0.0 > 5.0.1

[Suhan Dharmasuriya]

[1] http://mail.wso2.org/mailarchive/dev/2015-September/054616.html
[2] http://osdir.com/ml/general/2015-09/msg13727.html

On Fri, Oct 23, 2015 at 11:39 AM, Thushara Ranawaka 
wrote:

> Hi All,
>
> I try reindexing several times but swaggers didn't show up. Then I changed
> the JSONIndexer to PlainTextIndexer in registry.xml and indexed. Now I can
> see swaggers. Please advice.
>
> --
> Thanks,
> Thushara Kasun Ranawaka
> Software Engineer
> WSO2 Inc.; 
> lean.enterprise.middleware
> Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>*
> *thusha...@wso2.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Suhan Dharmasuriya
Software Engineer - Test Automation

*WSO2, Inc. *

lean . enterprise . middleware
Tel: +94 112 145345
Mob: +94 779 869138
Blog: http://suhan-opensource.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 Milestone 7 Released

[Prabath Abeysekera]

Hi Chathurika,

Yeah, the team is currently working on it. There was a few other issues too
that have been uncovered in the M7 shared above. So, planning to host a new
pack as M7 replacing what's already there, shortly. The initial plan was to
be done with it yesterday itself, but couldn't get a proper build out of
Jenkins due to some build issue that we ran into. Will keep you guys
informed once this is all done.

Cheers,
Prabath

On Fri, Oct 23, 2015 at 11:28 AM, Chathurika De Silva 
wrote:

> Hi
>
> As per our understanding the starting point of EMM which is device
> enrolment happens in two ways
>
> 1. User addition
> 2. Through QA code
>
> But both seem to be not working in the M7 pack. Please find the reported
> jiras below. Is there a chance to get a new pack?
>
> [1] https://wso2.org/jira/browse/EMM-846
> 
> [2] https://wso2.org/jira/browse/EMM-845
>
> Thanks
> Erandi
>
> On Wed, Oct 21, 2015 at 11:04 AM, Prabath Abeysekera 
> wrote:
>
>> Guys,
>>
>> Please do report doc JIRAs (blockers) upon any missing pieces in the
>> product documentation. That will help us keep track of things properly and
>> fix them ASAP.
>>
>> Cheers,
>> Prabath
>>
>> On Wed, Oct 21, 2015 at 10:41 AM, Shavindri Dissanayake <
>> shavin...@wso2.com> wrote:
>>
>>> Hi Chamara and Sashika,
>>>
>>> We do have a guide to set up the database [1]. It has details on setting
>>> up H2 [2] and MySQL [3]. Please do let me know if any areas in this doc
>>> needs to updated accordingly.
>>>
>>> Thank you for the heads up!
>>>
>>> [1] https://docs.wso2.com/display/EMM200/Working+with+Databases
>>> [2] https://docs.wso2.com/display/EMM200/Setting+up+H2
>>> [3] https://docs.wso2.com/display/EMM200/Setting+up+MySQL
>>>
>>> Thanks & Regards
>>> Shavindri Dissanayake
>>> Technical Writer
>>>
>>> WSO2 Inc.
>>> lean.enterprise.middleware
>>>
>>> On Wed, Oct 21, 2015 at 10:18 AM, Chamara Ariyarathne >> > wrote:
>>>
 Since there are several datasources to be configured, we need to have a
 guide on setting up databases for the product documentation.

 On Wed, Oct 21, 2015 at 10:09 AM, Sashika Wijesinghe 
 wrote:

> Hi All,
>
> I observed FileNotFoundException when starting a fresh pack with mysql
> database [1] . Further there is a naming issue in WSO2AM_DS datasource,
> same jndi config name is used for WSO2AM_DB and WSO2AM_DS [2].
>
> I have reported JIRA for above issues.
>
> [1] https://wso2.org/jira/browse/EMM-822
> [2] https://wso2.org/jira/browse/EMM-823
>
> Regards,
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>



 --
 *Chamara Ariyarathne*
 Associate Technical Lead - QA
 WSO2 Inc; http://www.wso2.com/
 Mobile; *+94772786766 <%2B94772786766>*

>>>
>>>
>>
>>
>> --
>> Prabath Abeysekara
>> Technical Lead
>> WSO2 Inc.
>> Email: praba...@wso2.com
>> Mobile: +94774171471
>>
>
>
>
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Swaggers are not showing up after GReg migration 5.0.0 > 5.0.1

[Thushara Ranawaka]

Hi All,

I try reindexing several times but swaggers didn't show up. Then I changed
the JSONIndexer to PlainTextIndexer in registry.xml and indexed. Now I can
see swaggers. Please advice.

-- 
Thanks,
Thushara Kasun Ranawaka
Software Engineer
WSO2 Inc.; 
lean.enterprise.middleware
Mobile : *+94 (0) 773438949*
*thusha...@wso2.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 Milestone 7 Released

[Chathurika De Silva]

Hi

As per our understanding the starting point of EMM which is device
enrolment happens in two ways

1. User addition
2. Through QA code

But both seem to be not working in the M7 pack. Please find the reported
jiras below. Is there a chance to get a new pack?

[1] https://wso2.org/jira/browse/EMM-846

[2] https://wso2.org/jira/browse/EMM-845

Thanks
Erandi

On Wed, Oct 21, 2015 at 11:04 AM, Prabath Abeysekera 
wrote:

> Guys,
>
> Please do report doc JIRAs (blockers) upon any missing pieces in the
> product documentation. That will help us keep track of things properly and
> fix them ASAP.
>
> Cheers,
> Prabath
>
> On Wed, Oct 21, 2015 at 10:41 AM, Shavindri Dissanayake <
> shavin...@wso2.com> wrote:
>
>> Hi Chamara and Sashika,
>>
>> We do have a guide to set up the database [1]. It has details on setting
>> up H2 [2] and MySQL [3]. Please do let me know if any areas in this doc
>> needs to updated accordingly.
>>
>> Thank you for the heads up!
>>
>> [1] https://docs.wso2.com/display/EMM200/Working+with+Databases
>> [2] https://docs.wso2.com/display/EMM200/Setting+up+H2
>> [3] https://docs.wso2.com/display/EMM200/Setting+up+MySQL
>>
>> Thanks & Regards
>> Shavindri Dissanayake
>> Technical Writer
>>
>> WSO2 Inc.
>> lean.enterprise.middleware
>>
>> On Wed, Oct 21, 2015 at 10:18 AM, Chamara Ariyarathne 
>> wrote:
>>
>>> Since there are several datasources to be configured, we need to have a
>>> guide on setting up databases for the product documentation.
>>>
>>> On Wed, Oct 21, 2015 at 10:09 AM, Sashika Wijesinghe 
>>> wrote:
>>>
 Hi All,

 I observed FileNotFoundException when starting a fresh pack with mysql
 database [1] . Further there is a naming issue in WSO2AM_DS datasource,
 same jndi config name is used for WSO2AM_DB and WSO2AM_DS [2].

 I have reported JIRA for above issues.

 [1] https://wso2.org/jira/browse/EMM-822
 [2] https://wso2.org/jira/browse/EMM-823

 Regards,
 --

 *Sashika WijesingheSoftware Engineer - QA Team*
 Mobile : +94 (0) 774537487
 sash...@wso2.com

>>>
>>>
>>>
>>> --
>>> *Chamara Ariyarathne*
>>> Associate Technical Lead - QA
>>> WSO2 Inc; http://www.wso2.com/
>>> Mobile; *+94772786766 <%2B94772786766>*
>>>
>>
>>
>
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Authentication issue in accessing analytics JS API in DAS

[Nayomi Dayarathne]

Kind reminder.

Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 <+94+(0)+775246619>

*nay...@wso2.com *

On Wed, Oct 21, 2015 at 6:52 PM, Nayomi Dayarathne  wrote:

> Hi Gimantha,
>
>
> As the per the current JS API implementation, it was not allowed to access
> Analytics JS API of DAS due to authentication issue and got the following
> authentication warnings when we debug the java script we have written using
> fire bug.
>
> *This site makes use of a SHA-1 Certificate; it's recommended you use
> certificates with signature algorithms that use hash functions stronger
> than SHA-1.*
> *Cross-Origin Request Blocked: The Same Origin Policy disallows reading
> the remote resource at https://localhost:9443/portal/apis/analytics?type=9
> . (Reason: CORS header
> 'Access-Control-Allow-Origin' missing).*
> *Cross-Origin Request Blocked: The Same Origin Policy disallows reading
> the remote resource at https://localhost:9443/portal/apis/analytics?type=9
> . (Reason: CORS
> request failed).*
>
> We have tried this scenario locally.And CORS settings has also added to
> the
> /repository/deployment/server/webapps/analytics/WEB-INF/web.xml
> file
>
> I have attached the relevant client files that we used to try this
> scenario, here with.
>
> Could you please provide the necessary and correct information to perform
> this properly?
>
> Regards,
>
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS] "hostname in certificate didn't match:" issue when accessing IS dashboard

[Aparna Karunarathna]

Hi all,

I have encountered a weird "hostname in certificate didn't match:" issue
when accessing IS dashboard. My setup details are as follows.

*Setup Details*
*IS cluster*
- 3 nodes cluster
- Hostname - mgt.is.wso2.com
- Certificate CN - mgt.is.wso2.com

*BPS cluster*
- 2 nodes cluster (manager/worker)
- Hostnames - Manager - mgt.bps.wso2.com / Worker - wrk.bps.wso2.com
- Certificate CN - *.bps.wso2.com

* Both nodes are fronted by same Nginx plus load balancer.

[1]
javax.net.ssl.SSLException: hostname in certificate didn't match: <
mgt.is.wso2.com> != <*.bps.wso2.com>
at
org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238)
at
org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)



When we check the browser cookie, it gave correct certificate. (
mgt.is.wso2.com), but when we check it from java client[2] it gives the bps
certificate (*.bps.wso2.com) instead of IS.

[2]
https://darray.wordpress.com/2015/07/12/freak-vulnerability-and-disabling-weak-export-cipher-suites-in-wso2-carbon-4-2-0-based-products/

What is the reason for this? Is it my config issue or Nginx issue or our
product issue?

-- 
*Regards,*

*Aparna Karunarathna.*


*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need help in customizing a script

[Imesh Gunaratne]

On Fri, Oct 23, 2015 at 10:49 AM, Mariangela Hills 
 wrote:

>
> *@Shavi* - Shavi, there is no need to say sorry! Even though it can look
> a bit contrasting it matches the header.
>
> Yes definitely +1 for doing creative stuff!!
I just conveyed my thoughts on the colour :-) Will let others also to share
their thoughts.

@Mari: I will share the details of the CEP extension distribution soon. We
need to design this.

Thanks

On Fri, Oct 23, 2015 at 10:49 AM, Mariangela Hills 
wrote:

> *@Imesh & Jerad* - Thanks for your feedback! Imesh, we will change the
> border color to a more subtle color.
>
> *@Shavi* - Shavi, there is no need to say sorry! Even though it can look
> a bit contrasting it matches the header.
>
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Fri, Oct 23, 2015 at 9:51 AM, Shavindri Dissanayake  > wrote:
>
>> Hi Imesh,
>>
>> I put that border, sorry my bad actually (was trying to match the header
>> color). Shall remove it :)
>>
>> Thanks & Regards
>> Shavindri Dissanayake
>> Technical Writer
>>
>> WSO2 Inc.
>> lean.enterprise.middleware
>>
>> On Fri, Oct 23, 2015 at 7:50 AM, Imesh Gunaratne  wrote:
>>
>>> Thanks Mari! It looks good.
>>> A quick thought: the blue colour border that we have used, for me its
>>> too contrasting. WDYT?
>>>
>>> Thanks
>>>
>>> On Fri, Oct 23, 2015 at 5:35 AM, Mariangela Hills 
>>> wrote:
>>>
 Hi Imesh,

 The following is the actual page that I was planning on adding this
 script to. However, now, instead of navigating the user off to separate
 pages I have pulled the content from those pages into the main page, so
 that the respective sub content will appear within the main page when the
 user clicks on the respective expand link for instructions.

 https://docs.wso2.com/display/PP410/Deploying+PPaaS+on+a+Preferred+IaaS

 Regards,
 Mariangela


 *Mariangela Hills*
 Senior Technical Writer - WSO2, Inc. http://wso2.com
 Committer and PMC member - Apache Stratos
 email:mariang...@wso2.com | mobile: +94 773 500185

 On Thu, Oct 22, 2015 at 3:04 PM, Imesh Gunaratne 
 wrote:

> Mari, can you please share a link to this page to have a look.
>
> Thanks
>
> On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake <
> shavin...@wso2.com> wrote:
>
>> Thank you Dakshika, this is great!
>>
>> Thanks & Regards
>> Shavindri Dissanayake
>> Technical Writer
>>
>> WSO2 Inc.
>> lean.enterprise.middleware
>>
>> On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills <
>> mariang...@wso2.com> wrote:
>>
>>> Hi Dakshika,
>>>
>>> Awesome, it works now! Thanks loads for taking the time to come up
>>> with a solution!
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka <
>>> daksh...@wso2.com> wrote:
>>>
 Hi,

 I fixed your issue. please check

 
 jQuery(document).ready(function() {
jQuery(".wiki-content a").each(function (){
   if(jQuery(this).context.hash == ''){
  jQuery(this).attr("target", "_blank");
   }
 });
 });
 


 Regards,

 *Dakshika Jayathilaka*
 PMC Member & Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills <
 mariang...@wso2.com> wrote:

> Hi Imesh, Dakshika and Nisrin,
>
> Thanks for all your feedback and help!
>
> *@Dakshika* - I tried the script but it did not work, because
> when I used it all the links were opening in the same page.
>
> *@Imesh -* Thanks for the info!
>
> *@Nisrin* - When a user is new to docs, they will tend to always
> click on a link as opposed to right-clicking on a link. Furthermore, 
> I was
> going on the assumption that they will close a link after they are 
> done
> with a certain set of steps (but I guess it will not always be the 
> case).
>
> As a workaround, I added an "expand macro" and pulled the child
> content into the expand macro using the "Include Page" macro, so that 
> the
> user will not have to see a ton of instructions all at once.
>
>
> Regards,
> Mariangela
>
>>>

Re: [Dev] Need help in customizing a script

[Mariangela Hills]

*@Imesh & Jerad* - Thanks for your feedback! Imesh, we will change the
border color to a more subtle color.

*@Shavi* - Shavi, there is no need to say sorry! Even though it can look a
bit contrasting it matches the header.


Regards,
Mariangela


*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185

On Fri, Oct 23, 2015 at 9:51 AM, Shavindri Dissanayake 
wrote:

> Hi Imesh,
>
> I put that border, sorry my bad actually (was trying to match the header
> color). Shall remove it :)
>
> Thanks & Regards
> Shavindri Dissanayake
> Technical Writer
>
> WSO2 Inc.
> lean.enterprise.middleware
>
> On Fri, Oct 23, 2015 at 7:50 AM, Imesh Gunaratne  wrote:
>
>> Thanks Mari! It looks good.
>> A quick thought: the blue colour border that we have used, for me its too
>> contrasting. WDYT?
>>
>> Thanks
>>
>> On Fri, Oct 23, 2015 at 5:35 AM, Mariangela Hills 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> The following is the actual page that I was planning on adding this
>>> script to. However, now, instead of navigating the user off to separate
>>> pages I have pulled the content from those pages into the main page, so
>>> that the respective sub content will appear within the main page when the
>>> user clicks on the respective expand link for instructions.
>>>
>>> https://docs.wso2.com/display/PP410/Deploying+PPaaS+on+a+Preferred+IaaS
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Thu, Oct 22, 2015 at 3:04 PM, Imesh Gunaratne  wrote:
>>>
 Mari, can you please share a link to this page to have a look.

 Thanks

 On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake <
 shavin...@wso2.com> wrote:

> Thank you Dakshika, this is great!
>
> Thanks & Regards
> Shavindri Dissanayake
> Technical Writer
>
> WSO2 Inc.
> lean.enterprise.middleware
>
> On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills  > wrote:
>
>> Hi Dakshika,
>>
>> Awesome, it works now! Thanks loads for taking the time to come up
>> with a solution!
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka <
>> daksh...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I fixed your issue. please check
>>>
>>> 
>>> jQuery(document).ready(function() {
>>> jQuery(".wiki-content a").each(function (){
>>>   if(jQuery(this).context.hash == ''){
>>>   jQuery(this).attr("target", "_blank");
>>>   }
>>> });
>>> });
>>> 
>>>
>>>
>>> Regards,
>>>
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills <
>>> mariang...@wso2.com> wrote:
>>>
 Hi Imesh, Dakshika and Nisrin,

 Thanks for all your feedback and help!

 *@Dakshika* - I tried the script but it did not work, because when
 I used it all the links were opening in the same page.

 *@Imesh -* Thanks for the info!

 *@Nisrin* - When a user is new to docs, they will tend to always
 click on a link as opposed to right-clicking on a link. Furthermore, I 
 was
 going on the assumption that they will close a link after they are done
 with a certain set of steps (but I guess it will not always be the 
 case).

 As a workaround, I added an "expand macro" and pulled the child
 content into the expand macro using the "Include Page" macro, so that 
 the
 user will not have to see a ton of instructions all at once.


 Regards,
 Mariangela


 *Mariangela Hills*
 Senior Technical Writer - WSO2, Inc. http://wso2.com
 Committer and PMC member - Apache Stratos
 email:mariang...@wso2.com | mobile: +94 773 500185

 On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff 
 wrote:

> Hi Mari,
>
> Wouldn't this result in too many tabs opening up as there will be
> a new tab opening whenever a users clicks on a link.
>
> With how it is now, if a user wants to view the linked section in
> a new tab, they can always right click and then click *Open Link
> in New Tab*/*Open Link in New Window* right.

Re: [Dev] Document issues in DAS

[Rukshani Weerasinha]

Hello Nayomi,

I will work on these issues. Thank you for reporting them.

Best Regards,
Rukshani.

On Thu, Oct 22, 2015 at 4:30 PM, Nayomi Dayarathne  wrote:

> Hi Documentation team,
>
> We would appreciate if you can update the following documents as soon as
> possible.
>
> 1.Sections under analytics javascript (JS) ApI.
> 2.Sections under REST API for analytics data service.
>
> We have noticed that the several contents are not valid and missing under
> above sections.
>
> Therefore, we have already created following JIRAs regarding these.
>
> [1]https://wso2.org/jira/browse/DOCUMENTATION-2605
> [2]https://wso2.org/jira/browse/DOCUMENTATION-2614
> [3]https://wso2.org/jira/browse/DOCUMENTATION-2604
> 
> [4]https://wso2.org/jira/browse/DOCUMENTATION-2600
> 
> [5]https://wso2.org/jira/browse/DOCUMENTATION-2604
> 
> [6]https://wso2.org/jira/browse/DOCUMENTATION-2599
> 
> [7]https://wso2.org/jira/browse/DOCUMENTATION-2568
> 
>
>
> Regards,
>
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Documentation Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to documentation+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 
Rukshani Weerasinha

WSO2 Inc.
Web:http://wso2.com
Mobile: 0777 683 738
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need help in customizing a script

[Shavindri Dissanayake]

Hi Imesh,

I put that border, sorry my bad actually (was trying to match the header
color). Shall remove it :)

Thanks & Regards
Shavindri Dissanayake
Technical Writer

WSO2 Inc.
lean.enterprise.middleware

On Fri, Oct 23, 2015 at 7:50 AM, Imesh Gunaratne  wrote:

> Thanks Mari! It looks good.
> A quick thought: the blue colour border that we have used, for me its too
> contrasting. WDYT?
>
> Thanks
>
> On Fri, Oct 23, 2015 at 5:35 AM, Mariangela Hills 
> wrote:
>
>> Hi Imesh,
>>
>> The following is the actual page that I was planning on adding this
>> script to. However, now, instead of navigating the user off to separate
>> pages I have pulled the content from those pages into the main page, so
>> that the respective sub content will appear within the main page when the
>> user clicks on the respective expand link for instructions.
>>
>> https://docs.wso2.com/display/PP410/Deploying+PPaaS+on+a+Preferred+IaaS
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Thu, Oct 22, 2015 at 3:04 PM, Imesh Gunaratne  wrote:
>>
>>> Mari, can you please share a link to this page to have a look.
>>>
>>> Thanks
>>>
>>> On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake <
>>> shavin...@wso2.com> wrote:
>>>
 Thank you Dakshika, this is great!

 Thanks & Regards
 Shavindri Dissanayake
 Technical Writer

 WSO2 Inc.
 lean.enterprise.middleware

 On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills 
 wrote:

> Hi Dakshika,
>
> Awesome, it works now! Thanks loads for taking the time to come up
> with a solution!
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka <
> daksh...@wso2.com> wrote:
>
>> Hi,
>>
>> I fixed your issue. please check
>>
>> 
>> jQuery(document).ready(function() {
>>  jQuery(".wiki-content a").each(function (){
>>   if(jQuery(this).context.hash == ''){
>>jQuery(this).attr("target", "_blank");
>>   }
>> });
>> });
>> 
>>
>>
>> Regards,
>>
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills <
>> mariang...@wso2.com> wrote:
>>
>>> Hi Imesh, Dakshika and Nisrin,
>>>
>>> Thanks for all your feedback and help!
>>>
>>> *@Dakshika* - I tried the script but it did not work, because when
>>> I used it all the links were opening in the same page.
>>>
>>> *@Imesh -* Thanks for the info!
>>>
>>> *@Nisrin* - When a user is new to docs, they will tend to always
>>> click on a link as opposed to right-clicking on a link. Furthermore, I 
>>> was
>>> going on the assumption that they will close a link after they are done
>>> with a certain set of steps (but I guess it will not always be the 
>>> case).
>>>
>>> As a workaround, I added an "expand macro" and pulled the child
>>> content into the expand macro using the "Include Page" macro, so that 
>>> the
>>> user will not have to see a ton of instructions all at once.
>>>
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff 
>>> wrote:
>>>
 Hi Mari,

 Wouldn't this result in too many tabs opening up as there will be a
 new tab opening whenever a users clicks on a link.

 With how it is now, if a user wants to view the linked section in a
 new tab, they can always right click and then click *Open Link in
 New Tab*/*Open Link in New Window* right.

 So do you think we really need this?

 Thank you.

 Best Regards,
 Nisrin

 Nisrin Sheriff
 Senior Technical Writer

 *WSO2, Inc.*lean.enterprise.middleware.
 mobile: +94 776 24 84 56
 http://wso2.com

 On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka <
 daksh...@wso2.com> wrote:

> Hi Mari,
>
> I have notice that you are using target="_blank" for internal page
> links as wel. remove that attribute from links to navigate within 
> page.
>
>>>

Re: [Dev] Shall we remove API-M 1.9.0 cartridge?

[Imesh Gunaratne]

Thanks Nuwan! We will remove 1.9.0.

Thanks

On Fri, Oct 23, 2015 at 9:07 AM, Nuwan Dias  wrote:

> Hi Imesh,
>
> I think we can live with the 1.9.1 one only.
>
> Thanks,
> NuwanD.
>
> On Thu, Oct 22, 2015 at 12:40 PM, Imesh Gunaratne  wrote:
>
>> Hi Nuwan,
>>
>> We have created two cartridges for API-M [1].
>> Do you think 1.9.0 one is needed?
>>
>> https://github.com/wso2/private-paas-cartridges/tree/master/wso2am
>>
>> Thanks
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shall we remove API-M 1.9.0 cartridge?

[Nuwan Dias]

Hi Imesh,

I think we can live with the 1.9.1 one only.

Thanks,
NuwanD.

On Thu, Oct 22, 2015 at 12:40 PM, Imesh Gunaratne  wrote:

> Hi Nuwan,
>
> We have created two cartridges for API-M [1].
> Do you think 1.9.0 one is needed?
>
> https://github.com/wso2/private-paas-cartridges/tree/master/wso2am
>
> Thanks
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>


-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Manager does not have store and publisher apps

[Nipuna Chandradasa]

Hi Lalanke,

Isn't getting the already built product work for you?. It is easier.

On Thu, Oct 22, 2015 at 7:26 PM, Lakshman Udayakantha 
wrote:

> Hi Lalanke,
>
> We focused only to release store and publisher features for product-apim
> 2.0.0 and master branch not the product. So the mentioned issue is there
> for master branch. If you want latest api manager product, build it from
> 1.10.x branch.
>
> Thanks
>
> On Thu, Oct 22, 2015 at 7:09 PM, Lalanke Athauda  wrote:
>
>> Hi,
>> I have built the latest product-apim. When it runs, I got 404 pages for
>> "store" app and "publisher" app. But in the admin console says "store" and
>> "publisher" apps are running. Do I have to build any other product, before
>> build product-apim correctly? Thanks.
>>
>> --
>> Lalanke Athauda
>> Software Engineer
>> WSO2 Inc.
>> Mobile: 0772264301
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0711241005*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nipuna Marcus
*Software Engineer*
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"
Mobile : +94 (0) 713 667906
nipu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need help in customizing a script

[Jerad Rutnam]

Hi Mari,

I think it's a better approach for a simple content like this. +1 for
keeping the contents on same page and move page to selected step.

Cheers!
Jerad

On Fri, Oct 23, 2015 at 5:35 AM, Mariangela Hills 
wrote:

> Hi Imesh,
>
> The following is the actual page that I was planning on adding this script
> to. However, now, instead of navigating the user off to separate pages I
> have pulled the content from those pages into the main page, so that the
> respective sub content will appear within the main page when the user
> clicks on the respective expand link for instructions.
>
> https://docs.wso2.com/display/PP410/Deploying+PPaaS+on+a+Preferred+IaaS
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Thu, Oct 22, 2015 at 3:04 PM, Imesh Gunaratne  wrote:
>
>> Mari, can you please share a link to this page to have a look.
>>
>> Thanks
>>
>> On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake <
>> shavin...@wso2.com> wrote:
>>
>>> Thank you Dakshika, this is great!
>>>
>>> Thanks & Regards
>>> Shavindri Dissanayake
>>> Technical Writer
>>>
>>> WSO2 Inc.
>>> lean.enterprise.middleware
>>>
>>> On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills 
>>> wrote:
>>>
 Hi Dakshika,

 Awesome, it works now! Thanks loads for taking the time to come up with
 a solution!

 Regards,
 Mariangela


 *Mariangela Hills*
 Senior Technical Writer - WSO2, Inc. http://wso2.com
 Committer and PMC member - Apache Stratos
 email:mariang...@wso2.com | mobile: +94 773 500185

 On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka <
 daksh...@wso2.com> wrote:

> Hi,
>
> I fixed your issue. please check
>
> 
> jQuery(document).ready(function() {
>   jQuery(".wiki-content a").each(function (){
>   if(jQuery(this).context.hash == ''){
> jQuery(this).attr("target", "_blank");
>   }
> });
> });
> 
>
>
> Regards,
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills  > wrote:
>
>> Hi Imesh, Dakshika and Nisrin,
>>
>> Thanks for all your feedback and help!
>>
>> *@Dakshika* - I tried the script but it did not work, because when I
>> used it all the links were opening in the same page.
>>
>> *@Imesh -* Thanks for the info!
>>
>> *@Nisrin* - When a user is new to docs, they will tend to always
>> click on a link as opposed to right-clicking on a link. Furthermore, I 
>> was
>> going on the assumption that they will close a link after they are done
>> with a certain set of steps (but I guess it will not always be the case).
>>
>> As a workaround, I added an "expand macro" and pulled the child
>> content into the expand macro using the "Include Page" macro, so that the
>> user will not have to see a ton of instructions all at once.
>>
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff 
>> wrote:
>>
>>> Hi Mari,
>>>
>>> Wouldn't this result in too many tabs opening up as there will be a
>>> new tab opening whenever a users clicks on a link.
>>>
>>> With how it is now, if a user wants to view the linked section in a
>>> new tab, they can always right click and then click *Open Link in
>>> New Tab*/*Open Link in New Window* right.
>>>
>>> So do you think we really need this?
>>>
>>> Thank you.
>>>
>>> Best Regards,
>>> Nisrin
>>>
>>> Nisrin Sheriff
>>> Senior Technical Writer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>> mobile: +94 776 24 84 56
>>> http://wso2.com
>>>
>>> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka <
>>> daksh...@wso2.com> wrote:
>>>
 Hi Mari,

 I have notice that you are using target="_blank" for internal page
 links as wel. remove that attribute from links to navigate within page.

 >>> href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
 *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
 (CEP)

 *Dakshika Jayathilaka*
 PMC Member & Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Thu, Oct 22, 2015 at 7:10 AM, Dakshika J

Re: [Dev] Need help in customizing a script

[Imesh Gunaratne]

Thanks Mari! It looks good.
A quick thought: the blue colour border that we have used, for me its too
contrasting. WDYT?

Thanks

On Fri, Oct 23, 2015 at 5:35 AM, Mariangela Hills 
wrote:

> Hi Imesh,
>
> The following is the actual page that I was planning on adding this script
> to. However, now, instead of navigating the user off to separate pages I
> have pulled the content from those pages into the main page, so that the
> respective sub content will appear within the main page when the user
> clicks on the respective expand link for instructions.
>
> https://docs.wso2.com/display/PP410/Deploying+PPaaS+on+a+Preferred+IaaS
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Thu, Oct 22, 2015 at 3:04 PM, Imesh Gunaratne  wrote:
>
>> Mari, can you please share a link to this page to have a look.
>>
>> Thanks
>>
>> On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake <
>> shavin...@wso2.com> wrote:
>>
>>> Thank you Dakshika, this is great!
>>>
>>> Thanks & Regards
>>> Shavindri Dissanayake
>>> Technical Writer
>>>
>>> WSO2 Inc.
>>> lean.enterprise.middleware
>>>
>>> On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills 
>>> wrote:
>>>
 Hi Dakshika,

 Awesome, it works now! Thanks loads for taking the time to come up with
 a solution!

 Regards,
 Mariangela


 *Mariangela Hills*
 Senior Technical Writer - WSO2, Inc. http://wso2.com
 Committer and PMC member - Apache Stratos
 email:mariang...@wso2.com | mobile: +94 773 500185

 On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka <
 daksh...@wso2.com> wrote:

> Hi,
>
> I fixed your issue. please check
>
> 
> jQuery(document).ready(function() {
>   jQuery(".wiki-content a").each(function (){
>   if(jQuery(this).context.hash == ''){
> jQuery(this).attr("target", "_blank");
>   }
> });
> });
> 
>
>
> Regards,
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills  > wrote:
>
>> Hi Imesh, Dakshika and Nisrin,
>>
>> Thanks for all your feedback and help!
>>
>> *@Dakshika* - I tried the script but it did not work, because when I
>> used it all the links were opening in the same page.
>>
>> *@Imesh -* Thanks for the info!
>>
>> *@Nisrin* - When a user is new to docs, they will tend to always
>> click on a link as opposed to right-clicking on a link. Furthermore, I 
>> was
>> going on the assumption that they will close a link after they are done
>> with a certain set of steps (but I guess it will not always be the case).
>>
>> As a workaround, I added an "expand macro" and pulled the child
>> content into the expand macro using the "Include Page" macro, so that the
>> user will not have to see a ton of instructions all at once.
>>
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff 
>> wrote:
>>
>>> Hi Mari,
>>>
>>> Wouldn't this result in too many tabs opening up as there will be a
>>> new tab opening whenever a users clicks on a link.
>>>
>>> With how it is now, if a user wants to view the linked section in a
>>> new tab, they can always right click and then click *Open Link in
>>> New Tab*/*Open Link in New Window* right.
>>>
>>> So do you think we really need this?
>>>
>>> Thank you.
>>>
>>> Best Regards,
>>> Nisrin
>>>
>>> Nisrin Sheriff
>>> Senior Technical Writer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>> mobile: +94 776 24 84 56
>>> http://wso2.com
>>>
>>> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka <
>>> daksh...@wso2.com> wrote:
>>>
 Hi Mari,

 I have notice that you are using target="_blank" for internal page
 links as wel. remove that attribute from links to navigate within page.

 >>> href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
 *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
 (CEP)

 *Dakshika Jayathilaka*
 PMC Member & Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka <
 daksh...@w

Re: [Dev] Need help in customizing a script

[Mariangela Hills]

Hi Imesh,

The following is the actual page that I was planning on adding this script
to. However, now, instead of navigating the user off to separate pages I
have pulled the content from those pages into the main page, so that the
respective sub content will appear within the main page when the user
clicks on the respective expand link for instructions.

https://docs.wso2.com/display/PP410/Deploying+PPaaS+on+a+Preferred+IaaS

Regards,
Mariangela


*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185

On Thu, Oct 22, 2015 at 3:04 PM, Imesh Gunaratne  wrote:

> Mari, can you please share a link to this page to have a look.
>
> Thanks
>
> On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake  > wrote:
>
>> Thank you Dakshika, this is great!
>>
>> Thanks & Regards
>> Shavindri Dissanayake
>> Technical Writer
>>
>> WSO2 Inc.
>> lean.enterprise.middleware
>>
>> On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills 
>> wrote:
>>
>>> Hi Dakshika,
>>>
>>> Awesome, it works now! Thanks loads for taking the time to come up with
>>> a solution!
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka >> > wrote:
>>>
 Hi,

 I fixed your issue. please check

 
 jQuery(document).ready(function() {
jQuery(".wiki-content a").each(function (){
   if(jQuery(this).context.hash == ''){
  jQuery(this).attr("target", "_blank");
   }
 });
 });
 


 Regards,

 *Dakshika Jayathilaka*
 PMC Member & Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills 
 wrote:

> Hi Imesh, Dakshika and Nisrin,
>
> Thanks for all your feedback and help!
>
> *@Dakshika* - I tried the script but it did not work, because when I
> used it all the links were opening in the same page.
>
> *@Imesh -* Thanks for the info!
>
> *@Nisrin* - When a user is new to docs, they will tend to always
> click on a link as opposed to right-clicking on a link. Furthermore, I was
> going on the assumption that they will close a link after they are done
> with a certain set of steps (but I guess it will not always be the case).
>
> As a workaround, I added an "expand macro" and pulled the child
> content into the expand macro using the "Include Page" macro, so that the
> user will not have to see a ton of instructions all at once.
>
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff 
> wrote:
>
>> Hi Mari,
>>
>> Wouldn't this result in too many tabs opening up as there will be a
>> new tab opening whenever a users clicks on a link.
>>
>> With how it is now, if a user wants to view the linked section in a
>> new tab, they can always right click and then click *Open Link in
>> New Tab*/*Open Link in New Window* right.
>>
>> So do you think we really need this?
>>
>> Thank you.
>>
>> Best Regards,
>> Nisrin
>>
>> Nisrin Sheriff
>> Senior Technical Writer
>>
>> *WSO2, Inc.*lean.enterprise.middleware.
>> mobile: +94 776 24 84 56
>> http://wso2.com
>>
>> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka <
>> daksh...@wso2.com> wrote:
>>
>>> Hi Mari,
>>>
>>> I have notice that you are using target="_blank" for internal page
>>> links as wel. remove that attribute from links to navigate within page.
>>>
>>> >> href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
>>> *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
>>> (CEP)
>>>
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka <
>>> daksh...@wso2.com> wrote:
>>>
 Hi All,

 IMO open a webpage in new tab or page is recommended depending on
 your use case. AFAIK giving a pop up link will block by browser due to
 security reason.

 So what you can do is, append simple class to "a"(anchor) to
 prevent all links opening in new page.
 Use below code snippet  for Pages that you 

[Dev] Java HttpClient to Greg with SSL

[Lam, Curtis]

Hi,

I am trying to make a GET request to the Greg located on own server. I have 
been provided the "client=truststore.jks" and "wso2carbon.jks" and am following 
the example found here: http://javasecurity.wikidot.com/example-item-1

The arguments are changed to match with the proper values such that:
URL : the server
keystoreFileName : wso2carbon.jks
truststoreFileName : truststore.jks

When running the java application, I get the following error:
javax.net.ssl.SSLHandshakeException: Remote host closed connection during 
handshake
   at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:849)
   at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170)
   at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1197)
   at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1181)
   at 
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:434)
   at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
   at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
   at java.net.URLConnection.getContent(URLConnection.java:688)
   at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getContent(HttpsURLConnectionImpl.java:406)
   at 
main.MutualAuthenticationHTTP.doitAll(MutualAuthenticationHTTP.java:76)
   at 
main.MutualAuthenticationHTTP.running(MutualAuthenticationHTTP.java:52)
   at 
test.MutualAuthenticationHTTPTest.test(MutualAuthenticationHTTPTest.java:14)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
   at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
   at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
   at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
   at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
   at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
   at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)
   at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:830)
   ... 34 more


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

[Dev] [VOTE] Release WSO2 DSS 3.5.0 RC1

[Rajith Vitharana]

Hi,

This is the first release candidate of WSO2 DSS 3.5.0

This release fixes the following issues:
https://wso2.org/jira/browse/DS-1126?filter=12469

Please download, test and vote. The vote will be open for 72 hours or as
needed.

Source & binary distribution files:
https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/RC1/wso2dss-3.5.0.zip

JavaDocs
https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/RC1/javaDocs/index.html

Maven staging repo:
http://maven.wso2.org/nexus/content/repositories/orgwso2dss-045/

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


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

Thanks,
The WSO2 DSS Team
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon Kernel 5.0.x branch build issue

[Kishanthan Thangarajah]

This is fixed and now we can build C5 kernel code base using latest maven
version (3.3.3) also.

On Thu, Oct 22, 2015 at 11:18 PM, Afkham Azeez  wrote:

> Yes, we shouldn't release without build support for the latest version of
> Maven. It is working fine for me on Maven 3.1.1 though.
>
> On Thu, Oct 22, 2015 at 10:45 PM, Sagara Gunathunga 
> wrote:
>
>>
>> @Azeez, This is C5, shouldn't we support to build the source with latest
>> Maven version ? Maven 3.0.5 is released in 2013.
>>
>> Thanks !
>>
>> On Thu, Oct 22, 2015 at 10:39 PM, Isuru Perera  wrote:
>>
>>> Hi,
>>>
>>> Thanks for the help. The Carbon Kernel 5 is building successfully with
>>> Maven 3.0.5. I couldn't figure out that issue is related to Maven version :(
>>>
>>> It's good that you created a JIRA to fix build issues with Maven 3.3.3.
>>>
>>>
>>> On Thu, Oct 22, 2015 at 10:18 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 This looks like an issue when building with maven 3.3.3. Can you try
 building with 3.0.5 (which the jenkins build job is configured)?

 Anyways we are fixing this issue as this is an unused dependency and
 making build ready on maven 3.3.3 :
 https://wso2.org/jira/browse/CARBON-15567.

 On Thu, Oct 22, 2015 at 10:16 PM, Afkham Azeez  wrote:

> Kernel team please help Isuru resolve this soon.
>
> On Thu, Oct 22, 2015 at 9:50 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> I'm trying to build Carbon Kernel 5.0.x branch [1] and I'm seeing
>> following error when building (mvn clean install) from root directory.
>>
>> [INFO] Installing
>> /home/isuru/work/wso2-git/carbon-kernel/features/org.wso2.carbon.core.runtime.feature/target/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
>> to
>> /home/isuru/.m2/repository/org/wso2/carbon/org.wso2.carbon.core.runtime.feature/5.0.0-SNAPSHOT/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
>> [INFO]
>>
>> [INFO]
>> 
>> [INFO] Building WSO2 Carbon Kernel - Distribution 5.0.0-SNAPSHOT
>> [INFO]
>> 
>> [WARNING] The POM for
>> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
>> is missing, no dependency information available
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 Carbon Kernel - Parent Pom  SUCCESS
>> [  5.875 s]
>> [INFO] WSO2 Carbon Kernel - Launcher .. SUCCESS [
>> 24.962 s]
>> [INFO] WSO2 Carbon Kernel - Core .. SUCCESS
>> [01:56 min]
>> [INFO] WSO2 Carbon Kernel - Tests . SUCCESS
>> [  2.131 s]
>> [INFO] WSO2 Carbon Kernel - Sample Tests Artifacts  SUCCESS
>> [  0.849 s]
>> [INFO] WSO2 Carbon Kernel - Sample Startup Coordination Artifacts
>> SUCCESS [  0.955 s]
>> [INFO] WSO2 Carbon Kernel - Sample Transport Manager .. SUCCESS [
>> 41.717 s]
>> [INFO] WSO2 Carbon Kernel - Sample Transport HTTP . SUCCESS [
>> 38.526 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime Manager  SUCCESS [
>> 34.667 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime MSS  SUCCESS [
>> 29.489 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime Webapp . SUCCESS [
>> 37.784 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime JAR  SUCCESS [
>> 36.073 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime BPS  SUCCESS [
>> 36.849 s]
>> [INFO] WSO2 Carbon Kernel - Sample Deployer Manager ... SUCCESS [
>> 39.433 s]
>> [INFO] WSO2 Carbon Kernel - OSGi Tests  SUCCESS [
>> 28.565 s]
>> [INFO] WSO2 Carbon Kernel - Transport . SUCCESS [
>> 49.597 s]
>> [INFO] WSO2 Carbon Kernel - Features Parent ... SUCCESS
>> [  1.659 s]
>> [INFO] WSO2 Carbon Kernel - Carbon Server Feature . SUCCESS
>> [  4.693 s]
>> [INFO] WSO2 Carbon Kernel - Carbon Runtime Feature  SUCCESS
>> [  2.102 s]
>> [INFO] WSO2 Carbon Kernel - Distribution .. FAILURE
>> [  0.095 s]
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 08:56 min
>> [INFO] Finished at: 2015-10-22T21:43:59+05:30
>> [INFO] Final Memory: 108M/1143M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project wso2carbon-kernel: Could
>> not resolve dependencies for project
>> org.ws

Re: [Dev] Carbon Kernel 5.0.x branch build issue

[Afkham Azeez]

Yes, we shouldn't release without build support for the latest version of
Maven. It is working fine for me on Maven 3.1.1 though.

On Thu, Oct 22, 2015 at 10:45 PM, Sagara Gunathunga  wrote:

>
> @Azeez, This is C5, shouldn't we support to build the source with latest
> Maven version ? Maven 3.0.5 is released in 2013.
>
> Thanks !
>
> On Thu, Oct 22, 2015 at 10:39 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> Thanks for the help. The Carbon Kernel 5 is building successfully with
>> Maven 3.0.5. I couldn't figure out that issue is related to Maven version :(
>>
>> It's good that you created a JIRA to fix build issues with Maven 3.3.3.
>>
>>
>> On Thu, Oct 22, 2015 at 10:18 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> This looks like an issue when building with maven 3.3.3. Can you try
>>> building with 3.0.5 (which the jenkins build job is configured)?
>>>
>>> Anyways we are fixing this issue as this is an unused dependency and
>>> making build ready on maven 3.3.3 :
>>> https://wso2.org/jira/browse/CARBON-15567.
>>>
>>> On Thu, Oct 22, 2015 at 10:16 PM, Afkham Azeez  wrote:
>>>
 Kernel team please help Isuru resolve this soon.

 On Thu, Oct 22, 2015 at 9:50 PM, Isuru Perera  wrote:

> Hi,
>
> I'm trying to build Carbon Kernel 5.0.x branch [1] and I'm seeing
> following error when building (mvn clean install) from root directory.
>
> [INFO] Installing
> /home/isuru/work/wso2-git/carbon-kernel/features/org.wso2.carbon.core.runtime.feature/target/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
> to
> /home/isuru/.m2/repository/org/wso2/carbon/org.wso2.carbon.core.runtime.feature/5.0.0-SNAPSHOT/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
> [INFO]
>
> [INFO]
> 
> [INFO] Building WSO2 Carbon Kernel - Distribution 5.0.0-SNAPSHOT
> [INFO]
> 
> [WARNING] The POM for
> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
> is missing, no dependency information available
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon Kernel - Parent Pom  SUCCESS [
> 5.875 s]
> [INFO] WSO2 Carbon Kernel - Launcher .. SUCCESS [
> 24.962 s]
> [INFO] WSO2 Carbon Kernel - Core .. SUCCESS
> [01:56 min]
> [INFO] WSO2 Carbon Kernel - Tests . SUCCESS [
> 2.131 s]
> [INFO] WSO2 Carbon Kernel - Sample Tests Artifacts  SUCCESS [
> 0.849 s]
> [INFO] WSO2 Carbon Kernel - Sample Startup Coordination Artifacts
> SUCCESS [  0.955 s]
> [INFO] WSO2 Carbon Kernel - Sample Transport Manager .. SUCCESS [
> 41.717 s]
> [INFO] WSO2 Carbon Kernel - Sample Transport HTTP . SUCCESS [
> 38.526 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime Manager  SUCCESS [
> 34.667 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime MSS  SUCCESS [
> 29.489 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime Webapp . SUCCESS [
> 37.784 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime JAR  SUCCESS [
> 36.073 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime BPS  SUCCESS [
> 36.849 s]
> [INFO] WSO2 Carbon Kernel - Sample Deployer Manager ... SUCCESS [
> 39.433 s]
> [INFO] WSO2 Carbon Kernel - OSGi Tests  SUCCESS [
> 28.565 s]
> [INFO] WSO2 Carbon Kernel - Transport . SUCCESS [
> 49.597 s]
> [INFO] WSO2 Carbon Kernel - Features Parent ... SUCCESS [
> 1.659 s]
> [INFO] WSO2 Carbon Kernel - Carbon Server Feature . SUCCESS [
> 4.693 s]
> [INFO] WSO2 Carbon Kernel - Carbon Runtime Feature  SUCCESS [
> 2.102 s]
> [INFO] WSO2 Carbon Kernel - Distribution .. FAILURE [
> 0.095 s]
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 08:56 min
> [INFO] Finished at: 2015-10-22T21:43:59+05:30
> [INFO] Final Memory: 108M/1143M
> [INFO]
> 
> [ERROR] Failed to execute goal on project wso2carbon-kernel: Could not
> resolve dependencies for project
> org.wso2.carbon:wso2carbon-kernel:pom:5.0.0-SNAPSHOT: Failure to find
> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
> in http://maven.wso2.org/nexus/content/repositories/releases/ was
> cached in the local repository, resolution will not

Re: [Dev] Carbon Kernel 5.0.x branch build issue

[Sagara Gunathunga]

@Azeez, This is C5, shouldn't we support to build the source with latest
Maven version ? Maven 3.0.5 is released in 2013.

Thanks !
On Thu, Oct 22, 2015 at 10:39 PM, Isuru Perera  wrote:

> Hi,
>
> Thanks for the help. The Carbon Kernel 5 is building successfully with
> Maven 3.0.5. I couldn't figure out that issue is related to Maven version :(
>
> It's good that you created a JIRA to fix build issues with Maven 3.3.3.
>
>
> On Thu, Oct 22, 2015 at 10:18 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> This looks like an issue when building with maven 3.3.3. Can you try
>> building with 3.0.5 (which the jenkins build job is configured)?
>>
>> Anyways we are fixing this issue as this is an unused dependency and
>> making build ready on maven 3.3.3 :
>> https://wso2.org/jira/browse/CARBON-15567.
>>
>> On Thu, Oct 22, 2015 at 10:16 PM, Afkham Azeez  wrote:
>>
>>> Kernel team please help Isuru resolve this soon.
>>>
>>> On Thu, Oct 22, 2015 at 9:50 PM, Isuru Perera  wrote:
>>>
 Hi,

 I'm trying to build Carbon Kernel 5.0.x branch [1] and I'm seeing
 following error when building (mvn clean install) from root directory.

 [INFO] Installing
 /home/isuru/work/wso2-git/carbon-kernel/features/org.wso2.carbon.core.runtime.feature/target/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
 to
 /home/isuru/.m2/repository/org/wso2/carbon/org.wso2.carbon.core.runtime.feature/5.0.0-SNAPSHOT/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
 [INFO]

 [INFO]
 
 [INFO] Building WSO2 Carbon Kernel - Distribution 5.0.0-SNAPSHOT
 [INFO]
 
 [WARNING] The POM for
 org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
 is missing, no dependency information available
 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Carbon Kernel - Parent Pom  SUCCESS [
 5.875 s]
 [INFO] WSO2 Carbon Kernel - Launcher .. SUCCESS [
 24.962 s]
 [INFO] WSO2 Carbon Kernel - Core .. SUCCESS
 [01:56 min]
 [INFO] WSO2 Carbon Kernel - Tests . SUCCESS [
 2.131 s]
 [INFO] WSO2 Carbon Kernel - Sample Tests Artifacts  SUCCESS [
 0.849 s]
 [INFO] WSO2 Carbon Kernel - Sample Startup Coordination Artifacts
 SUCCESS [  0.955 s]
 [INFO] WSO2 Carbon Kernel - Sample Transport Manager .. SUCCESS [
 41.717 s]
 [INFO] WSO2 Carbon Kernel - Sample Transport HTTP . SUCCESS [
 38.526 s]
 [INFO] WSO2 Carbon Kernel - Sample Runtime Manager  SUCCESS [
 34.667 s]
 [INFO] WSO2 Carbon Kernel - Sample Runtime MSS  SUCCESS [
 29.489 s]
 [INFO] WSO2 Carbon Kernel - Sample Runtime Webapp . SUCCESS [
 37.784 s]
 [INFO] WSO2 Carbon Kernel - Sample Runtime JAR  SUCCESS [
 36.073 s]
 [INFO] WSO2 Carbon Kernel - Sample Runtime BPS  SUCCESS [
 36.849 s]
 [INFO] WSO2 Carbon Kernel - Sample Deployer Manager ... SUCCESS [
 39.433 s]
 [INFO] WSO2 Carbon Kernel - OSGi Tests  SUCCESS [
 28.565 s]
 [INFO] WSO2 Carbon Kernel - Transport . SUCCESS [
 49.597 s]
 [INFO] WSO2 Carbon Kernel - Features Parent ... SUCCESS [
 1.659 s]
 [INFO] WSO2 Carbon Kernel - Carbon Server Feature . SUCCESS [
 4.693 s]
 [INFO] WSO2 Carbon Kernel - Carbon Runtime Feature  SUCCESS [
 2.102 s]
 [INFO] WSO2 Carbon Kernel - Distribution .. FAILURE [
 0.095 s]
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 08:56 min
 [INFO] Finished at: 2015-10-22T21:43:59+05:30
 [INFO] Final Memory: 108M/1143M
 [INFO]
 
 [ERROR] Failed to execute goal on project wso2carbon-kernel: Could not
 resolve dependencies for project
 org.wso2.carbon:wso2carbon-kernel:pom:5.0.0-SNAPSHOT: Failure to find
 org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
 in http://maven.wso2.org/nexus/content/repositories/releases/ was
 cached in the local repository, resolution will not be reattempted until
 the update interval of wso2.releases has elapsed or updates are forced ->
 [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

Re: [Dev] Carbon Kernel 5.0.x branch build issue

[Isuru Perera]

Hi,

Thanks for the help. The Carbon Kernel 5 is building successfully with
Maven 3.0.5. I couldn't figure out that issue is related to Maven version :(

It's good that you created a JIRA to fix build issues with Maven 3.3.3.


On Thu, Oct 22, 2015 at 10:18 PM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

> This looks like an issue when building with maven 3.3.3. Can you try
> building with 3.0.5 (which the jenkins build job is configured)?
>
> Anyways we are fixing this issue as this is an unused dependency and
> making build ready on maven 3.3.3 :
> https://wso2.org/jira/browse/CARBON-15567.
>
> On Thu, Oct 22, 2015 at 10:16 PM, Afkham Azeez  wrote:
>
>> Kernel team please help Isuru resolve this soon.
>>
>> On Thu, Oct 22, 2015 at 9:50 PM, Isuru Perera  wrote:
>>
>>> Hi,
>>>
>>> I'm trying to build Carbon Kernel 5.0.x branch [1] and I'm seeing
>>> following error when building (mvn clean install) from root directory.
>>>
>>> [INFO] Installing
>>> /home/isuru/work/wso2-git/carbon-kernel/features/org.wso2.carbon.core.runtime.feature/target/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
>>> to
>>> /home/isuru/.m2/repository/org/wso2/carbon/org.wso2.carbon.core.runtime.feature/5.0.0-SNAPSHOT/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
>>> [INFO]
>>>
>>> [INFO]
>>> 
>>> [INFO] Building WSO2 Carbon Kernel - Distribution 5.0.0-SNAPSHOT
>>> [INFO]
>>> 
>>> [WARNING] The POM for
>>> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
>>> is missing, no dependency information available
>>> [INFO]
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] WSO2 Carbon Kernel - Parent Pom  SUCCESS [
>>> 5.875 s]
>>> [INFO] WSO2 Carbon Kernel - Launcher .. SUCCESS [
>>> 24.962 s]
>>> [INFO] WSO2 Carbon Kernel - Core .. SUCCESS
>>> [01:56 min]
>>> [INFO] WSO2 Carbon Kernel - Tests . SUCCESS [
>>> 2.131 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Tests Artifacts  SUCCESS [
>>> 0.849 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Startup Coordination Artifacts
>>> SUCCESS [  0.955 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Transport Manager .. SUCCESS [
>>> 41.717 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Transport HTTP . SUCCESS [
>>> 38.526 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Runtime Manager  SUCCESS [
>>> 34.667 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Runtime MSS  SUCCESS [
>>> 29.489 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Runtime Webapp . SUCCESS [
>>> 37.784 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Runtime JAR  SUCCESS [
>>> 36.073 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Runtime BPS  SUCCESS [
>>> 36.849 s]
>>> [INFO] WSO2 Carbon Kernel - Sample Deployer Manager ... SUCCESS [
>>> 39.433 s]
>>> [INFO] WSO2 Carbon Kernel - OSGi Tests  SUCCESS [
>>> 28.565 s]
>>> [INFO] WSO2 Carbon Kernel - Transport . SUCCESS [
>>> 49.597 s]
>>> [INFO] WSO2 Carbon Kernel - Features Parent ... SUCCESS [
>>> 1.659 s]
>>> [INFO] WSO2 Carbon Kernel - Carbon Server Feature . SUCCESS [
>>> 4.693 s]
>>> [INFO] WSO2 Carbon Kernel - Carbon Runtime Feature  SUCCESS [
>>> 2.102 s]
>>> [INFO] WSO2 Carbon Kernel - Distribution .. FAILURE [
>>> 0.095 s]
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 08:56 min
>>> [INFO] Finished at: 2015-10-22T21:43:59+05:30
>>> [INFO] Final Memory: 108M/1143M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal on project wso2carbon-kernel: Could not
>>> resolve dependencies for project
>>> org.wso2.carbon:wso2carbon-kernel:pom:5.0.0-SNAPSHOT: Failure to find
>>> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
>>> in http://maven.wso2.org/nexus/content/repositories/releases/ was
>>> cached in the local repository, resolution will not be reattempted until
>>> the update interval of wso2.releases has elapsed or updates are forced ->
>>> [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/DependencyResolutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with

Re: [Dev] Carbon Kernel 5.0.x branch build issue

[Kishanthan Thangarajah]

This looks like an issue when building with maven 3.3.3. Can you try
building with 3.0.5 (which the jenkins build job is configured)?

Anyways we are fixing this issue as this is an unused dependency and making
build ready on maven 3.3.3 : https://wso2.org/jira/browse/CARBON-15567.

On Thu, Oct 22, 2015 at 10:16 PM, Afkham Azeez  wrote:

> Kernel team please help Isuru resolve this soon.
>
> On Thu, Oct 22, 2015 at 9:50 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> I'm trying to build Carbon Kernel 5.0.x branch [1] and I'm seeing
>> following error when building (mvn clean install) from root directory.
>>
>> [INFO] Installing
>> /home/isuru/work/wso2-git/carbon-kernel/features/org.wso2.carbon.core.runtime.feature/target/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
>> to
>> /home/isuru/.m2/repository/org/wso2/carbon/org.wso2.carbon.core.runtime.feature/5.0.0-SNAPSHOT/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
>> [INFO]
>>
>> [INFO]
>> 
>> [INFO] Building WSO2 Carbon Kernel - Distribution 5.0.0-SNAPSHOT
>> [INFO]
>> 
>> [WARNING] The POM for
>> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
>> is missing, no dependency information available
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 Carbon Kernel - Parent Pom  SUCCESS [
>> 5.875 s]
>> [INFO] WSO2 Carbon Kernel - Launcher .. SUCCESS [
>> 24.962 s]
>> [INFO] WSO2 Carbon Kernel - Core .. SUCCESS
>> [01:56 min]
>> [INFO] WSO2 Carbon Kernel - Tests . SUCCESS [
>> 2.131 s]
>> [INFO] WSO2 Carbon Kernel - Sample Tests Artifacts  SUCCESS [
>> 0.849 s]
>> [INFO] WSO2 Carbon Kernel - Sample Startup Coordination Artifacts SUCCESS
>> [  0.955 s]
>> [INFO] WSO2 Carbon Kernel - Sample Transport Manager .. SUCCESS [
>> 41.717 s]
>> [INFO] WSO2 Carbon Kernel - Sample Transport HTTP . SUCCESS [
>> 38.526 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime Manager  SUCCESS [
>> 34.667 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime MSS  SUCCESS [
>> 29.489 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime Webapp . SUCCESS [
>> 37.784 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime JAR  SUCCESS [
>> 36.073 s]
>> [INFO] WSO2 Carbon Kernel - Sample Runtime BPS  SUCCESS [
>> 36.849 s]
>> [INFO] WSO2 Carbon Kernel - Sample Deployer Manager ... SUCCESS [
>> 39.433 s]
>> [INFO] WSO2 Carbon Kernel - OSGi Tests  SUCCESS [
>> 28.565 s]
>> [INFO] WSO2 Carbon Kernel - Transport . SUCCESS [
>> 49.597 s]
>> [INFO] WSO2 Carbon Kernel - Features Parent ... SUCCESS [
>> 1.659 s]
>> [INFO] WSO2 Carbon Kernel - Carbon Server Feature . SUCCESS [
>> 4.693 s]
>> [INFO] WSO2 Carbon Kernel - Carbon Runtime Feature  SUCCESS [
>> 2.102 s]
>> [INFO] WSO2 Carbon Kernel - Distribution .. FAILURE [
>> 0.095 s]
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 08:56 min
>> [INFO] Finished at: 2015-10-22T21:43:59+05:30
>> [INFO] Final Memory: 108M/1143M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project wso2carbon-kernel: Could not
>> resolve dependencies for project
>> org.wso2.carbon:wso2carbon-kernel:pom:5.0.0-SNAPSHOT: Failure to find
>> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
>> in http://maven.wso2.org/nexus/content/repositories/releases/ was cached
>> in the local repository, resolution will not be reattempted until the
>> update interval of wso2.releases has elapsed or updates are forced -> [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/DependencyResolutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :wso2carbon-kernel
>>
>> However I can build from distribution directory and there are no failures.
>>
>> It seems the mentioned dependency is not available in wso2-public repo
>> [2] also
>>
>> What could be reason? I'm still trying to figure out what's happening.
>>
>> [1] https://github.com/wso2/carbon-kernel/tree/5.0.x
>> [2]
>> http://maven.wso2.org/nexus/content/groups/wso2-public

Re: [Dev] Carbon Kernel 5.0.x branch build issue

[Afkham Azeez]

Kernel team please help Isuru resolve this soon.

On Thu, Oct 22, 2015 at 9:50 PM, Isuru Perera  wrote:

> Hi,
>
> I'm trying to build Carbon Kernel 5.0.x branch [1] and I'm seeing
> following error when building (mvn clean install) from root directory.
>
> [INFO] Installing
> /home/isuru/work/wso2-git/carbon-kernel/features/org.wso2.carbon.core.runtime.feature/target/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
> to
> /home/isuru/.m2/repository/org/wso2/carbon/org.wso2.carbon.core.runtime.feature/5.0.0-SNAPSHOT/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
> [INFO]
>
> [INFO]
> 
> [INFO] Building WSO2 Carbon Kernel - Distribution 5.0.0-SNAPSHOT
> [INFO]
> 
> [WARNING] The POM for
> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
> is missing, no dependency information available
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon Kernel - Parent Pom  SUCCESS [
> 5.875 s]
> [INFO] WSO2 Carbon Kernel - Launcher .. SUCCESS [
> 24.962 s]
> [INFO] WSO2 Carbon Kernel - Core .. SUCCESS [01:56
> min]
> [INFO] WSO2 Carbon Kernel - Tests . SUCCESS [
> 2.131 s]
> [INFO] WSO2 Carbon Kernel - Sample Tests Artifacts  SUCCESS [
> 0.849 s]
> [INFO] WSO2 Carbon Kernel - Sample Startup Coordination Artifacts SUCCESS
> [  0.955 s]
> [INFO] WSO2 Carbon Kernel - Sample Transport Manager .. SUCCESS [
> 41.717 s]
> [INFO] WSO2 Carbon Kernel - Sample Transport HTTP . SUCCESS [
> 38.526 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime Manager  SUCCESS [
> 34.667 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime MSS  SUCCESS [
> 29.489 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime Webapp . SUCCESS [
> 37.784 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime JAR  SUCCESS [
> 36.073 s]
> [INFO] WSO2 Carbon Kernel - Sample Runtime BPS  SUCCESS [
> 36.849 s]
> [INFO] WSO2 Carbon Kernel - Sample Deployer Manager ... SUCCESS [
> 39.433 s]
> [INFO] WSO2 Carbon Kernel - OSGi Tests  SUCCESS [
> 28.565 s]
> [INFO] WSO2 Carbon Kernel - Transport . SUCCESS [
> 49.597 s]
> [INFO] WSO2 Carbon Kernel - Features Parent ... SUCCESS [
> 1.659 s]
> [INFO] WSO2 Carbon Kernel - Carbon Server Feature . SUCCESS [
> 4.693 s]
> [INFO] WSO2 Carbon Kernel - Carbon Runtime Feature  SUCCESS [
> 2.102 s]
> [INFO] WSO2 Carbon Kernel - Distribution .. FAILURE [
> 0.095 s]
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 08:56 min
> [INFO] Finished at: 2015-10-22T21:43:59+05:30
> [INFO] Final Memory: 108M/1143M
> [INFO]
> 
> [ERROR] Failed to execute goal on project wso2carbon-kernel: Could not
> resolve dependencies for project
> org.wso2.carbon:wso2carbon-kernel:pom:5.0.0-SNAPSHOT: Failure to find
> org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
> in http://maven.wso2.org/nexus/content/repositories/releases/ was cached
> in the local repository, resolution will not be reattempted until the
> update interval of wso2.releases has elapsed or updates are forced -> [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/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :wso2carbon-kernel
>
> However I can build from distribution directory and there are no failures.
>
> It seems the mentioned dependency is not available in wso2-public repo [2]
> also
>
> What could be reason? I'm still trying to figure out what's happening.
>
> [1] https://github.com/wso2/carbon-kernel/tree/5.0.x
> [2]
> http://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/osgi/org.eclipse.equinox.p2.transport.ecf/1.1.0.v20130516-1858/
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* 

[Dev] Carbon Kernel 5.0.x branch build issue

[Isuru Perera]

Hi,

I'm trying to build Carbon Kernel 5.0.x branch [1] and I'm seeing following
error when building (mvn clean install) from root directory.

[INFO] Installing
/home/isuru/work/wso2-git/carbon-kernel/features/org.wso2.carbon.core.runtime.feature/target/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
to
/home/isuru/.m2/repository/org/wso2/carbon/org.wso2.carbon.core.runtime.feature/5.0.0-SNAPSHOT/org.wso2.carbon.core.runtime.feature-5.0.0-SNAPSHOT.zip
[INFO]

[INFO]

[INFO] Building WSO2 Carbon Kernel - Distribution 5.0.0-SNAPSHOT
[INFO]

[WARNING] The POM for
org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
is missing, no dependency information available
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Carbon Kernel - Parent Pom  SUCCESS [
5.875 s]
[INFO] WSO2 Carbon Kernel - Launcher .. SUCCESS [
24.962 s]
[INFO] WSO2 Carbon Kernel - Core .. SUCCESS [01:56
min]
[INFO] WSO2 Carbon Kernel - Tests . SUCCESS [
2.131 s]
[INFO] WSO2 Carbon Kernel - Sample Tests Artifacts  SUCCESS [
0.849 s]
[INFO] WSO2 Carbon Kernel - Sample Startup Coordination Artifacts SUCCESS
[  0.955 s]
[INFO] WSO2 Carbon Kernel - Sample Transport Manager .. SUCCESS [
41.717 s]
[INFO] WSO2 Carbon Kernel - Sample Transport HTTP . SUCCESS [
38.526 s]
[INFO] WSO2 Carbon Kernel - Sample Runtime Manager  SUCCESS [
34.667 s]
[INFO] WSO2 Carbon Kernel - Sample Runtime MSS  SUCCESS [
29.489 s]
[INFO] WSO2 Carbon Kernel - Sample Runtime Webapp . SUCCESS [
37.784 s]
[INFO] WSO2 Carbon Kernel - Sample Runtime JAR  SUCCESS [
36.073 s]
[INFO] WSO2 Carbon Kernel - Sample Runtime BPS  SUCCESS [
36.849 s]
[INFO] WSO2 Carbon Kernel - Sample Deployer Manager ... SUCCESS [
39.433 s]
[INFO] WSO2 Carbon Kernel - OSGi Tests  SUCCESS [
28.565 s]
[INFO] WSO2 Carbon Kernel - Transport . SUCCESS [
49.597 s]
[INFO] WSO2 Carbon Kernel - Features Parent ... SUCCESS [
1.659 s]
[INFO] WSO2 Carbon Kernel - Carbon Server Feature . SUCCESS [
4.693 s]
[INFO] WSO2 Carbon Kernel - Carbon Runtime Feature  SUCCESS [
2.102 s]
[INFO] WSO2 Carbon Kernel - Distribution .. FAILURE [
0.095 s]
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 08:56 min
[INFO] Finished at: 2015-10-22T21:43:59+05:30
[INFO] Final Memory: 108M/1143M
[INFO]

[ERROR] Failed to execute goal on project wso2carbon-kernel: Could not
resolve dependencies for project
org.wso2.carbon:wso2carbon-kernel:pom:5.0.0-SNAPSHOT: Failure to find
org.eclipse.osgi:org.eclipse.equinox.p2.transport.ecf:jar:1.1.0.v20130516-1858
in http://maven.wso2.org/nexus/content/repositories/releases/ was cached in
the local repository, resolution will not be reattempted until the update
interval of wso2.releases has elapsed or updates are forced -> [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/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :wso2carbon-kernel

However I can build from distribution directory and there are no failures.

It seems the mentioned dependency is not available in wso2-public repo [2]
also

What could be reason? I'm still trying to figure out what's happening.

[1] https://github.com/wso2/carbon-kernel/tree/5.0.x
[2]
http://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/osgi/org.eclipse.equinox.p2.transport.ecf/1.1.0.v20130516-1858/
-- 
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] carbon-multitenancy-4.5.0 released !

[Kalpa Welivitigoda]

Hi folks,

Please note $subject,

org.wso2.carbon.multitenancy
carbon-multitenancy
4.5.0

-- 
Best Regards,

Kalpa Welivitigoda
Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Updated MSS, GW and Transports to use Carbon Kernel 5.0.0-m5

[Kasun Indrasiri]

Done.

On Thu, Oct 22, 2015 at 7:33 PM, Samiyuru Senarathne 
wrote:

> Hi,
>
> Please note the $subject.
>
> Following are the pull requests.
>
> MSS: https://github.com/wso2/product-mss/pull/20
> GW: https://github.com/wso2/product-gw/pull/7
> Transports: https://github.com/wso2/carbon-transports/pull/6
>
> Thank you.
>
> Best Regards,
> Samiyuru
>
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>



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

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] oom - current status

[Manuranga Perera]

Looping Dev.
On Oct 22, 2015 9:29 PM, "Manuranga Perera"  wrote:

> If you are writing integration test, best way to test is not by looking at
> memory. Look at the response headers after doing a request to a test app
> and see JSESSION cookie is created.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Updated MSS, GW and Transports to use Carbon Kernel 5.0.0-m5

[Kishanthan Thangarajah]

Please merge these PRs. We are in the process of restructuring the packages
in kernel to have *org.wso2.carbon.kernel *as the root package. So
depending on SNAPSHOT dependencies will cause build breaks with this
package restructure.

On Thu, Oct 22, 2015 at 7:33 PM, Samiyuru Senarathne 
wrote:

> Hi,
>
> Please note the $subject.
>
> Following are the pull requests.
>
> MSS: https://github.com/wso2/product-mss/pull/20
> GW: https://github.com/wso2/product-gw/pull/7
> Transports: https://github.com/wso2/carbon-transports/pull/6
>
> Thank you.
>
> Best Regards,
> Samiyuru
>
> --
> 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
>
>


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

[Dev] Updated MSS, GW and Transports to use Carbon Kernel 5.0.0-m5

[Samiyuru Senarathne]

Hi,

Please note the $subject.

Following are the pull requests.

MSS: https://github.com/wso2/product-mss/pull/20
GW: https://github.com/wso2/product-gw/pull/7
Transports: https://github.com/wso2/carbon-transports/pull/6

Thank you.

Best Regards,
Samiyuru

-- 
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] API Manager does not have store and publisher apps

[Lakshman Udayakantha]

Hi Lalanke,

We focused only to release store and publisher features for product-apim
2.0.0 and master branch not the product. So the mentioned issue is there
for master branch. If you want latest api manager product, build it from
1.10.x branch.

Thanks

On Thu, Oct 22, 2015 at 7:09 PM, Lalanke Athauda  wrote:

> Hi,
> I have built the latest product-apim. When it runs, I got 404 pages for
> "store" app and "publisher" app. But in the admin console says "store" and
> "publisher" apps are running. Do I have to build any other product, before
> build product-apim correctly? Thanks.
>
> --
> Lalanke Athauda
> Software Engineer
> WSO2 Inc.
> Mobile: 0772264301
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0711241005*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] carbon-commons-4.4.8 is released !

[Kalpa Welivitigoda]

Hi folks,

Please note $subject.


-- 
Best Regards,

Kalpa Welivitigoda
Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] API Manager does not have store and publisher apps

[Lalanke Athauda]

Hi,
I have built the latest product-apim. When it runs, I got 404 pages for
"store" app and "publisher" app. But in the admin console says "store" and
"publisher" apps are running. Do I have to build any other product, before
build product-apim correctly? Thanks.

-- 
Lalanke Athauda
Software Engineer
WSO2 Inc.
Mobile: 0772264301
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to simulate a multipart/form-data submission using a post request in jaggery

[Nipuna Chandradasa]

Hi Team,

I finally got it running.

What i did was captured the request curl from one of the places where we
upload multiple type of data using a Form (File upload with a other string
data) and mimic the request and send it using XMLHttpRequest. This works
perfectly.

This idea was given by Udara.

Thank you.

On Thu, Oct 22, 2015 at 8:19 AM, Nipuna Chandradasa 
wrote:

> It is not a UI test manu This test is for jaggery framework to test
> its multipart parsing function... It's just a Java test case
> On 22 Oct 2015 6:14 a.m., "Manuranga Perera"  wrote:
>
>> If this is an ui test, selenium will allow you to upload a file. It'll
>> automatically be multi part.
>>
>


-- 
Nipuna Marcus
*Software Engineer*
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"
Mobile : +94 (0) 713 667906
nipu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] social component is not working properly.

[Lakshman Udayakantha]

Hi,

As I can see the host and port of social iframe source url is
localhost:9443 in store. That should be actually localhost:9444 according
to the documentation[1]. When I hardcoded that url to 9444 port in relevant
hbs file, social component shows accurate average rating. Where we can
configure social app url in store?

I configured it in sso-idp-config.xml and store-tenant.json. But still the
base of social app url is https://localhost:9443.

[1]
https://docs.wso2.com/display/Governance501/Installing+WSO2+API+Manager+Features

Thanks

On Wed, Oct 21, 2015 at 6:43 PM, Lakshman Udayakantha 
wrote:

> Hi Udara,
>
> Thanks for the quick response. I have checked all the tables
> in WSO2SOCIAL_DB in social-datasources.xml including the SOCIAL_RATING_CACHE
> table also by issuing select * query. But there is no row in that table.
> anyway social iframe is showing comment and rating data after server
> restarting also. is there any other place rating data stored?
>
> Thanks
>
> On Wed, Oct 21, 2015 at 6:22 PM, Udara Rathnayake  wrote:
>
>> rating should be stored within SOCIAL_RATING table and average rating
>> inside SOCIAL_RATING_CACHE
>>
>> On Wed, Oct 21, 2015 at 5:42 PM, Lakshman Udayakantha > > wrote:
>>
>>> Hi ES team,
>>>
>>> I have checked out store 2.3.9-SNAPSHOT and governance registry
>>> 5.1.0-SNAPSHOT and built packs from those branches and created the setup
>>> according to [1].
>>>
>>> After adding several reviews in social components, I can see rating and
>>> comment is updating in social iframe component. but after refreshing the
>>> page, overall rating for the assets is not updating.
>>>
>>> I have checked the database pointed in social-datasources.xml. but
>>> couldn't find any entry stored in it. Where these social data is stored?
>>> any point to trouble shoot this issue is highly appreciated.
>>>
>>> [1]
>>> https://docs.wso2.com/display/Governance501/Installing+WSO2+API+Manager+Features
>>>
>>> --
>>> Lakshman Udayakantha
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>> Mobile: *0711241005*
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0711241005*
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0711241005*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Document issues in DAS

[Nayomi Dayarathne]

Hi Documentation team,

We would appreciate if you can update the following documents as soon as
possible.

1.Sections under analytics javascript (JS) ApI.
2.Sections under REST API for analytics data service.

We have noticed that the several contents are not valid and missing under
above sections.

Therefore, we have already created following JIRAs regarding these.

[1]https://wso2.org/jira/browse/DOCUMENTATION-2605
[2]https://wso2.org/jira/browse/DOCUMENTATION-2614
[3]https://wso2.org/jira/browse/DOCUMENTATION-2604

[4]https://wso2.org/jira/browse/DOCUMENTATION-2600

[5]https://wso2.org/jira/browse/DOCUMENTATION-2604

[6]https://wso2.org/jira/browse/DOCUMENTATION-2599

[7]https://wso2.org/jira/browse/DOCUMENTATION-2568



Regards,


Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 <+94+(0)+775246619>

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

Re: [Dev] Need help in customizing a script

[Imesh Gunaratne]

Mari, can you please share a link to this page to have a look.

Thanks

On Thu, Oct 22, 2015 at 2:16 PM, Shavindri Dissanayake 
wrote:

> Thank you Dakshika, this is great!
>
> Thanks & Regards
> Shavindri Dissanayake
> Technical Writer
>
> WSO2 Inc.
> lean.enterprise.middleware
>
> On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills 
> wrote:
>
>> Hi Dakshika,
>>
>> Awesome, it works now! Thanks loads for taking the time to come up with a
>> solution!
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka 
>> wrote:
>>
>>> Hi,
>>>
>>> I fixed your issue. please check
>>>
>>> 
>>> jQuery(document).ready(function() {
>>> jQuery(".wiki-content a").each(function (){
>>>   if(jQuery(this).context.hash == ''){
>>>   jQuery(this).attr("target", "_blank");
>>>   }
>>> });
>>> });
>>> 
>>>
>>>
>>> Regards,
>>>
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills 
>>> wrote:
>>>
 Hi Imesh, Dakshika and Nisrin,

 Thanks for all your feedback and help!

 *@Dakshika* - I tried the script but it did not work, because when I
 used it all the links were opening in the same page.

 *@Imesh -* Thanks for the info!

 *@Nisrin* - When a user is new to docs, they will tend to always click
 on a link as opposed to right-clicking on a link. Furthermore, I was going
 on the assumption that they will close a link after they are done with a
 certain set of steps (but I guess it will not always be the case).

 As a workaround, I added an "expand macro" and pulled the child content
 into the expand macro using the "Include Page" macro, so that the user will
 not have to see a ton of instructions all at once.


 Regards,
 Mariangela


 *Mariangela Hills*
 Senior Technical Writer - WSO2, Inc. http://wso2.com
 Committer and PMC member - Apache Stratos
 email:mariang...@wso2.com | mobile: +94 773 500185

 On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff 
 wrote:

> Hi Mari,
>
> Wouldn't this result in too many tabs opening up as there will be a
> new tab opening whenever a users clicks on a link.
>
> With how it is now, if a user wants to view the linked section in a
> new tab, they can always right click and then click *Open Link in New
> Tab*/*Open Link in New Window* right.
>
> So do you think we really need this?
>
> Thank you.
>
> Best Regards,
> Nisrin
>
> Nisrin Sheriff
> Senior Technical Writer
>
> *WSO2, Inc.*lean.enterprise.middleware.
> mobile: +94 776 24 84 56
> http://wso2.com
>
> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka <
> daksh...@wso2.com> wrote:
>
>> Hi Mari,
>>
>> I have notice that you are using target="_blank" for internal page
>> links as wel. remove that attribute from links to navigate within page.
>>
>> > href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
>> *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
>> (CEP)
>>
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka <
>> daksh...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> IMO open a webpage in new tab or page is recommended depending on
>>> your use case. AFAIK giving a pop up link will block by browser due to
>>> security reason.
>>>
>>> So what you can do is, append simple class to "a"(anchor) to prevent
>>> all links opening in new page.
>>> Use below code snippet  for Pages that you want to open in new page
>>> or tab.
>>>
>>> for HTML link:
>>>
>>>  this is an external link
>>> 
>>>
>>> for other links
>>>
>>> default 
>>>
>>> Script:
>>>
>>> 
>>> jQuery(document).ready(function() {
>>> jQuery(".wiki-content a.new-page").attr("target", "_blank");
>>> });
>>> 
>>>
>>> Thank you,
>>>
>>> Regards,
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Oct 22, 2015 at 7:02 AM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Mari,

 Opening a new tab or a new browser window is not recommended. Most
 of the browsers block this by default 

Re: [Dev] Need help in customizing a script

[Shavindri Dissanayake]

Thank you Dakshika, this is great!

Thanks & Regards
Shavindri Dissanayake
Technical Writer

WSO2 Inc.
lean.enterprise.middleware

On Thu, Oct 22, 2015 at 2:13 PM, Mariangela Hills 
wrote:

> Hi Dakshika,
>
> Awesome, it works now! Thanks loads for taking the time to come up with a
> solution!
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka 
> wrote:
>
>> Hi,
>>
>> I fixed your issue. please check
>>
>> 
>> jQuery(document).ready(function() {
>>  jQuery(".wiki-content a").each(function (){
>>   if(jQuery(this).context.hash == ''){
>>jQuery(this).attr("target", "_blank");
>>   }
>> });
>> });
>> 
>>
>>
>> Regards,
>>
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills 
>> wrote:
>>
>>> Hi Imesh, Dakshika and Nisrin,
>>>
>>> Thanks for all your feedback and help!
>>>
>>> *@Dakshika* - I tried the script but it did not work, because when I
>>> used it all the links were opening in the same page.
>>>
>>> *@Imesh -* Thanks for the info!
>>>
>>> *@Nisrin* - When a user is new to docs, they will tend to always click
>>> on a link as opposed to right-clicking on a link. Furthermore, I was going
>>> on the assumption that they will close a link after they are done with a
>>> certain set of steps (but I guess it will not always be the case).
>>>
>>> As a workaround, I added an "expand macro" and pulled the child content
>>> into the expand macro using the "Include Page" macro, so that the user will
>>> not have to see a ton of instructions all at once.
>>>
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff  wrote:
>>>
 Hi Mari,

 Wouldn't this result in too many tabs opening up as there will be a new
 tab opening whenever a users clicks on a link.

 With how it is now, if a user wants to view the linked section in a new
 tab, they can always right click and then click *Open Link in New 
 Tab*/*Open
 Link in New Window* right.

 So do you think we really need this?

 Thank you.

 Best Regards,
 Nisrin

 Nisrin Sheriff
 Senior Technical Writer

 *WSO2, Inc.*lean.enterprise.middleware.
 mobile: +94 776 24 84 56
 http://wso2.com

 On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka <
 daksh...@wso2.com> wrote:

> Hi Mari,
>
> I have notice that you are using target="_blank" for internal page
> links as wel. remove that attribute from links to navigate within page.
>
>  href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
> *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
> (CEP)
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka <
> daksh...@wso2.com> wrote:
>
>> Hi All,
>>
>> IMO open a webpage in new tab or page is recommended depending on
>> your use case. AFAIK giving a pop up link will block by browser due to
>> security reason.
>>
>> So what you can do is, append simple class to "a"(anchor) to prevent
>> all links opening in new page.
>> Use below code snippet  for Pages that you want to open in new page
>> or tab.
>>
>> for HTML link:
>>
>>  this is an external link
>> 
>>
>> for other links
>>
>> default 
>>
>> Script:
>>
>> 
>> jQuery(document).ready(function() {
>> jQuery(".wiki-content a.new-page").attr("target", "_blank");
>> });
>> 
>>
>> Thank you,
>>
>> Regards,
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Thu, Oct 22, 2015 at 7:02 AM, Imesh Gunaratne 
>> wrote:
>>
>>> Hi Mari,
>>>
>>> Opening a new tab or a new browser window is not recommended. Most
>>> of the browsers block this by default due to security reasons. May be we
>>> need to think of a different approach.
>>>
>>> Thanks
>>>
>>> On Thu, Oct 22, 2015 at 6:38 AM, Mariangela Hills <
>>> mariang...@wso2.com> wrote:
>>>
 Hi,

 When working with the Wiki (Confluence) docs, there are times when
>>>

Re: [Dev] Need help in customizing a script

[Mariangela Hills]

Hi Dakshika,

Awesome, it works now! Thanks loads for taking the time to come up with a
solution!

Regards,
Mariangela


*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185

On Thu, Oct 22, 2015 at 2:05 PM, Dakshika Jayathilaka 
wrote:

> Hi,
>
> I fixed your issue. please check
>
> 
> jQuery(document).ready(function() {
>   jQuery(".wiki-content a").each(function (){
>   if(jQuery(this).context.hash == ''){
> jQuery(this).attr("target", "_blank");
>   }
> });
> });
> 
>
>
> Regards,
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills 
> wrote:
>
>> Hi Imesh, Dakshika and Nisrin,
>>
>> Thanks for all your feedback and help!
>>
>> *@Dakshika* - I tried the script but it did not work, because when I
>> used it all the links were opening in the same page.
>>
>> *@Imesh -* Thanks for the info!
>>
>> *@Nisrin* - When a user is new to docs, they will tend to always click
>> on a link as opposed to right-clicking on a link. Furthermore, I was going
>> on the assumption that they will close a link after they are done with a
>> certain set of steps (but I guess it will not always be the case).
>>
>> As a workaround, I added an "expand macro" and pulled the child content
>> into the expand macro using the "Include Page" macro, so that the user will
>> not have to see a ton of instructions all at once.
>>
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff  wrote:
>>
>>> Hi Mari,
>>>
>>> Wouldn't this result in too many tabs opening up as there will be a new
>>> tab opening whenever a users clicks on a link.
>>>
>>> With how it is now, if a user wants to view the linked section in a new
>>> tab, they can always right click and then click *Open Link in New Tab*/*Open
>>> Link in New Window* right.
>>>
>>> So do you think we really need this?
>>>
>>> Thank you.
>>>
>>> Best Regards,
>>> Nisrin
>>>
>>> Nisrin Sheriff
>>> Senior Technical Writer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>> mobile: +94 776 24 84 56
>>> http://wso2.com
>>>
>>> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka >> > wrote:
>>>
 Hi Mari,

 I have notice that you are using target="_blank" for internal page
 links as wel. remove that attribute from links to navigate within page.

 >>> href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
 *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
 (CEP)

 *Dakshika Jayathilaka*
 PMC Member & Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka <
 daksh...@wso2.com> wrote:

> Hi All,
>
> IMO open a webpage in new tab or page is recommended depending on your
> use case. AFAIK giving a pop up link will block by browser due to security
> reason.
>
> So what you can do is, append simple class to "a"(anchor) to prevent
> all links opening in new page.
> Use below code snippet  for Pages that you want to open in new page or
> tab.
>
> for HTML link:
>
>  this is an external link
> 
>
> for other links
>
> default 
>
> Script:
>
> 
> jQuery(document).ready(function() {
> jQuery(".wiki-content a.new-page").attr("target", "_blank");
> });
> 
>
> Thank you,
>
> Regards,
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Thu, Oct 22, 2015 at 7:02 AM, Imesh Gunaratne 
> wrote:
>
>> Hi Mari,
>>
>> Opening a new tab or a new browser window is not recommended. Most of
>> the browsers block this by default due to security reasons. May be we 
>> need
>> to think of a different approach.
>>
>> Thanks
>>
>> On Thu, Oct 22, 2015 at 6:38 AM, Mariangela Hills <
>> mariang...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> When working with the Wiki (Confluence) docs, there are times when
>>> we have to point off to sub-pages within a main set of instructions, so
>>> that the main page does not get too bulky. This means that when a user
>>> clicks these links, they will be redirected to those new pages within 
>>> the
>>> same tab. Instead, it will be better if such links can be opened in a 
>>> new
>>> tab/page, so that the user can always have the

Re: [Dev] Clarification of Feature for DAS

[Gokul Balakrishnan]

Yes, the carbon-metrics 1.1.1 features have now been added to DAS and
should be available in the subsequent builds.

On 22 October 2015 at 13:10, Anjana Fernando  wrote:

> Hi Shavantha,
>
> Yeah, Metrics feature also needs to be installed, this was fixed by Gokul
> lately. Thanks.
>
> Cheers,
> Anjana.
>
> On Wed, Oct 21, 2015 at 1:40 PM, Shavantha Weerasinghe  > wrote:
>
>> Hi Anjana
>>
>> The document[1] mentions that the below features should be installed for
>> ML to be used as a CEP extension. However, we also had to install WSO2
>> Carbon - Metrics Group Feature for on DAS in order to use the  ML feature.
>> Should DAS to have the Metrics Group Feature installed similar to CEP400.
>>
>> WSO2 Carbon - ML Siddhi Extension Feature
>> WSO2 Carbon - Machine Learner Core Feature
>> WSO2 Carbon - Machine Learner Database Service Feature
>> WSO2 Carbon - Machine Learner Commons Feature
>>
>> [1]
>> https://docs.wso2.com/display/CEP400/Installing+Machine+Learner+Features
>>
>> Regards,
>> Shavantha Weerasinghe
>> Senior Software Engineer QA
>> WSO2, Inc.
>> lean.enterprise.middleware.
>> http://wso2.com
>> http://wso2.org
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>



-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need help in customizing a script

[Dakshika Jayathilaka]

Hi,

I fixed your issue. please check


jQuery(document).ready(function() {
jQuery(".wiki-content a").each(function (){
  if(jQuery(this).context.hash == ''){
  jQuery(this).attr("target", "_blank");
  }
});
});



Regards,

*Dakshika Jayathilaka*
PMC Member & Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911

On Thu, Oct 22, 2015 at 1:40 PM, Mariangela Hills 
wrote:

> Hi Imesh, Dakshika and Nisrin,
>
> Thanks for all your feedback and help!
>
> *@Dakshika* - I tried the script but it did not work, because when I used
> it all the links were opening in the same page.
>
> *@Imesh -* Thanks for the info!
>
> *@Nisrin* - When a user is new to docs, they will tend to always click on
> a link as opposed to right-clicking on a link. Furthermore, I was going on
> the assumption that they will close a link after they are done with a
> certain set of steps (but I guess it will not always be the case).
>
> As a workaround, I added an "expand macro" and pulled the child content
> into the expand macro using the "Include Page" macro, so that the user will
> not have to see a ton of instructions all at once.
>
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff  wrote:
>
>> Hi Mari,
>>
>> Wouldn't this result in too many tabs opening up as there will be a new
>> tab opening whenever a users clicks on a link.
>>
>> With how it is now, if a user wants to view the linked section in a new
>> tab, they can always right click and then click *Open Link in New Tab*/*Open
>> Link in New Window* right.
>>
>> So do you think we really need this?
>>
>> Thank you.
>>
>> Best Regards,
>> Nisrin
>>
>> Nisrin Sheriff
>> Senior Technical Writer
>>
>> *WSO2, Inc.*lean.enterprise.middleware.
>> mobile: +94 776 24 84 56
>> http://wso2.com
>>
>> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka 
>> wrote:
>>
>>> Hi Mari,
>>>
>>> I have notice that you are using target="_blank" for internal page links
>>> as wel. remove that attribute from links to navigate within page.
>>>
>>> >> href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
>>> *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
>>> (CEP)
>>>
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka >> > wrote:
>>>
 Hi All,

 IMO open a webpage in new tab or page is recommended depending on your
 use case. AFAIK giving a pop up link will block by browser due to security
 reason.

 So what you can do is, append simple class to "a"(anchor) to prevent
 all links opening in new page.
 Use below code snippet  for Pages that you want to open in new page or
 tab.

 for HTML link:

  this is an external link 

 for other links

 default 

 Script:

 
 jQuery(document).ready(function() {
 jQuery(".wiki-content a.new-page").attr("target", "_blank");
 });
 

 Thank you,

 Regards,
 *Dakshika Jayathilaka*
 PMC Member & Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Thu, Oct 22, 2015 at 7:02 AM, Imesh Gunaratne 
 wrote:

> Hi Mari,
>
> Opening a new tab or a new browser window is not recommended. Most of
> the browsers block this by default due to security reasons. May be we need
> to think of a different approach.
>
> Thanks
>
> On Thu, Oct 22, 2015 at 6:38 AM, Mariangela Hills  > wrote:
>
>> Hi,
>>
>> When working with the Wiki (Confluence) docs, there are times when we
>> have to point off to sub-pages within a main set of instructions, so that
>> the main page does not get too bulky. This means that when a user clicks
>> these links, they will be redirected to those new pages within the same
>> tab. Instead, it will be better if such links can be opened in a new
>> tab/page, so that the user can always have the main set of instructions 
>> at
>> hand.
>>
>> I found the following code block in [1], which needs to be added to a
>> HTML macro, to open external links and internal links in a new page.
>> However, the drawback when using this code block is that even the links 
>> in
>> the table of contents open in a new window :(
>>
>> Will someone please be able to help by tweaking this code to stop
>> links in the table of contents opening in a new page?
>> Please note that I have created a set of sample pages in my wiki
>> sandbox in [2], so that you c

Re: [Dev] Missing links in WSO2 docker hub

[Akila Ravihansa Perera]

I purposely kept it like that since we have to change it anyway when we
release.

On Thu, Oct 22, 2015 at 1:49 PM, Pubudu Gunatilaka  wrote:

> Hi,
>
> IMO it should refer to already released version which is 4.1.0 cartridge
> repo until 4.1.1 is released.
>
> Thank you!
>
> On Thu, Oct 22, 2015 at 1:45 PM, Gayan Gunarathne  wrote:
>
>> There are some missing github repo links with the WSO2 docker hub
>> pages[1]. Shall we link those to the master branch until  we do the PPaaS
>> Cartridge release?
>>
>> [1]https://hub.docker.com/r/wso2/as-5.2.1/
>>
>> Thanks,
>> Gayan
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774079049 <%2B94772207163>
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] Missing links in WSO2 docker hub

[Pubudu Gunatilaka]

Hi,

IMO it should refer to already released version which is 4.1.0 cartridge
repo until 4.1.1 is released.

Thank you!

On Thu, Oct 22, 2015 at 1:45 PM, Gayan Gunarathne  wrote:

> There are some missing github repo links with the WSO2 docker hub
> pages[1]. Shall we link those to the master branch until  we do the PPaaS
> Cartridge release?
>
> [1]https://hub.docker.com/r/wso2/as-5.2.1/
>
> Thanks,
> Gayan
>
> --
>
> Gayan Gunarathne
> Technical Lead, WSO2 Inc. (http://wso2.com)
> Committer & PMC Member, Apache Stratos
> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774079049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Missing links in WSO2 docker hub

[Gayan Gunarathne]

There are some missing github repo links with the WSO2 docker hub pages[1].
Shall we link those to the master branch until  we do the PPaaS Cartridge
release?

[1]https://hub.docker.com/r/wso2/as-5.2.1/

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need help in customizing a script

[Mariangela Hills]

Hi Imesh, Dakshika and Nisrin,

Thanks for all your feedback and help!

*@Dakshika* - I tried the script but it did not work, because when I used
it all the links were opening in the same page.

*@Imesh -* Thanks for the info!

*@Nisrin* - When a user is new to docs, they will tend to always click on a
link as opposed to right-clicking on a link. Furthermore, I was going on
the assumption that they will close a link after they are done with a
certain set of steps (but I guess it will not always be the case).

As a workaround, I added an "expand macro" and pulled the child content
into the expand macro using the "Include Page" macro, so that the user will
not have to see a ton of instructions all at once.


Regards,
Mariangela


*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185

On Thu, Oct 22, 2015 at 8:14 AM, Nisrin Sheriff  wrote:

> Hi Mari,
>
> Wouldn't this result in too many tabs opening up as there will be a new
> tab opening whenever a users clicks on a link.
>
> With how it is now, if a user wants to view the linked section in a new
> tab, they can always right click and then click *Open Link in New Tab*/*Open
> Link in New Window* right.
>
> So do you think we really need this?
>
> Thank you.
>
> Best Regards,
> Nisrin
>
> Nisrin Sheriff
> Senior Technical Writer
>
> *WSO2, Inc.*lean.enterprise.middleware.
> mobile: +94 776 24 84 56
> http://wso2.com
>
> On Thu, Oct 22, 2015 at 7:42 AM, Dakshika Jayathilaka 
> wrote:
>
>> Hi Mari,
>>
>> I have notice that you are using target="_blank" for internal page links
>> as wel. remove that attribute from links to navigate within page.
>>
>> > href="#Mainpagewithinstructions-Step2-SetuptheWSO2ComplexEventProcessor(CEP)"
>> *target="_blank"*>Step 2 - Setup the WSO2 Complex Event Processor
>> (CEP)
>>
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Thu, Oct 22, 2015 at 7:10 AM, Dakshika Jayathilaka 
>> wrote:
>>
>>> Hi All,
>>>
>>> IMO open a webpage in new tab or page is recommended depending on your
>>> use case. AFAIK giving a pop up link will block by browser due to security
>>> reason.
>>>
>>> So what you can do is, append simple class to "a"(anchor) to prevent all
>>> links opening in new page.
>>> Use below code snippet  for Pages that you want to open in new page or
>>> tab.
>>>
>>> for HTML link:
>>>
>>>  this is an external link 
>>>
>>> for other links
>>>
>>> default 
>>>
>>> Script:
>>>
>>> 
>>> jQuery(document).ready(function() {
>>> jQuery(".wiki-content a.new-page").attr("target", "_blank");
>>> });
>>> 
>>>
>>> Thank you,
>>>
>>> Regards,
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Oct 22, 2015 at 7:02 AM, Imesh Gunaratne  wrote:
>>>
 Hi Mari,

 Opening a new tab or a new browser window is not recommended. Most of
 the browsers block this by default due to security reasons. May be we need
 to think of a different approach.

 Thanks

 On Thu, Oct 22, 2015 at 6:38 AM, Mariangela Hills 
 wrote:

> Hi,
>
> When working with the Wiki (Confluence) docs, there are times when we
> have to point off to sub-pages within a main set of instructions, so that
> the main page does not get too bulky. This means that when a user clicks
> these links, they will be redirected to those new pages within the same
> tab. Instead, it will be better if such links can be opened in a new
> tab/page, so that the user can always have the main set of instructions at
> hand.
>
> I found the following code block in [1], which needs to be added to a
> HTML macro, to open external links and internal links in a new page.
> However, the drawback when using this code block is that even the links in
> the table of contents open in a new window :(
>
> Will someone please be able to help by tweaking this code to stop
> links in the table of contents opening in a new page?
> Please note that I have created a set of sample pages in my wiki
> sandbox in [2], so that you can test the tweaked code if needed.
>
> 
> jQuery(document).ready(function() {
> jQuery(".wiki-content a").attr("target", "_blank");
> });
> 
>
>
>
> [1]
> https://confluence.atlassian.com/display/CONFKB/How+to+force+links+to+open+in+a+new+window
> [2] https://docs.wso2.com/display/SM100/Main+page+with+instructions
>
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>



 --
>

Re: [Dev] Incorporated carbon-feature-plugin-2.0.0-m1 in MSS and GW projects

[Sameera Jayasoma]

On Thu, Oct 22, 2015 at 12:47 AM, Sameera Jayasoma  wrote:

> Hi Azeez,
>
> Yeah, this is a major design decision of the new Carbon feature plugin. We
> had few design meetings for this plugin, there we finalized the
> configuration based on some of the following points.
>
> 1) Adopted a Maven dependency-like configuration for features and bundles
> instead of the strings and colon(:) configuration. I believe having a
> proper/valid XML structure is much better than the previous configuration.
> Because,
>
>- It's clean.
>- Configuration can be validated with a schema.
>- You get the same maven experience.
>
> e.g.
>
>
> *javax.ws.rs:javax.ws.rs-api*
>
> vs
>
> **
> *   javax.ws.rs-api*
> *${rs-api.version}*
> **
>
>
> 2) Refactored maven goals we had in the previous plugin and came up with
> easy to understand, self-explanatory set of Maven goal names.
>
>- *generate*
>- maven goal for generate carbon features (formerly known as
>   p2-feature-gen)
>
>
>-
> *generate-repo  *
>   - maven goal for generate repositories (formerly known as
>   p2-repo-gen)
>
>
>- *install*
>- maven goal for install features into a product (formerly known as
>   p2-profile-gen)
>
>
>- *uninstall*
> - maven goal for uninstalling features
>-
> *generate-profile *
>   - maven goal for generate profiles (formerly known as
>   materialize-product)
>
>
>- *publish-product*
>- maven goal for publishing a product
>
> Thanks,
> Sameera.
>
>
> On Thu, Oct 22, 2015 at 12:06 AM, Afkham Azeez  wrote:
>
>> Yes, merge the PR. On second thoughts, I think the new XML syntax is
>> better than the previous one because it specifically highlights that it is
>> using the bundle symbolic name & not the maven group or artifact ID.
>>
>> On Thu, Oct 22, 2015 at 12:34 PM, Kasun Indrasiri  wrote:
>>
>>> Should we go ahead with this change?
>>>
>>> On Mon, Oct 19, 2015 at 5:01 PM, Afkham Azeez  wrote:
>>>
 I am seeing a lot of introduction of new tags.

 e.g. 1. org.wso2.carbon.p2.category.type:server is now written as

 org.wso2.carbon.p2.category.type
 server


 2.
 javax.ws.rs:javax.ws.rs-api

 is now written as. Also we have the additional burden of specifying the
 version again.

 
javax.ws.rs-api
 ${rs-api.version}
 

 Why have we made the configuration more verbose? More XML tags is not
 necessarily better.


 On Mon, Oct 19, 2015 at 3:42 PM, Dinusha Boteju 
 wrote:

> Hi all,
>
> I have updated the pom files in WSO2 MSS and WSO2 GW projects to
> incorporate carbon-feature-plugin 2.0.0-m1 and sent pull requests to
> relevant repositories.
>
> jira link for MSS : https://wso2.org/jira/browse/WMS-2
> PR link for MSS : https://github.com/wso2/product-mss/pull/14
>
> jira link for GW   : https://wso2.org/jira/browse/WGW-1
> 
> PR link for GW   : https://github.com/wso2/product-gw/pull/6
>
> Best regards,
> --
> *Dinusha Boteju*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: dinus...@wso2.com 
> phone:(+94) 776640275 <%28%2B94%29%2039736>
>



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

>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> *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*
>>
>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>


-- 
Sameera Jayasoma,
Softw

Re: [Dev] How to pass java InputStream object to jaggery.

[Lakshman Udayakantha]

Creating new stream object in jaggery, I could access the input stream
returned by java method.

document.data = new Stream(new ByteArrayInputStream(content.get("Data")));

Thanks Denuwanthi for the help.

On Thu, Oct 22, 2015 at 12:04 PM, Lakshman Udayakantha 
wrote:

> Hi Denuwanthi,
>
> Thanks for the answer. Anyway I will not get file object from jaggery
> layer. content hashmap include a input stream object as a value for the key
> called "Data". I want to get that input stream object. Other values like
> name and contentType in hashmap can retrieve successfully from hash map.
> problem is that inputstream object will not be extractable from jaggery
> method.
>
> Thanks
>
> On Thu, Oct 22, 2015 at 10:48 AM, Denuwanthi De Silva  > wrote:
>
>> Hi Lakshman,
>>
>> Did you try the following?
>>
>> var inputStream = Packages.java.io.InputStream;
>>
>> inputStream = file.getStream().getStream();
>>
>> (You need to call getStream() method twice)
>>
>>
>> Thanks,
>>
>>
>>
>>
>>
>>
>> On Wed, Oct 21, 2015 at 3:39 PM, Lakshman Udayakantha > > wrote:
>>
>>> Hi ES team,
>>>
>>> There is a method to get document from registry in API Manager Impl
>>> layer. We can get any file saved in registry with that method. But when I
>>> pass the returned file object to jaggery method, jaggery layer gets an
>>> empty object.
>>>
>>> public static Map getDocument(String userName, String
>>> resourceUrl,
>>>   String tenantDomain)
>>>  {
>>> Map documentMap = new HashMap();
>>>
>>> InputStream inStream = null;
>>>
>>> Resource apiDocResource;
>>>
>>> inStream = apiDocResource.getContentStream();
>>> documentMap.put("Data", inStream);
>>> documentMap.put("contentType",
>>> apiDocResource.getMediaType());
>>> String[] content = apiDocResource.getPath().split("/");
>>> documentMap.put("name", content[content.length - 1]);
>>>
>>> return documentMap;
>>> }
>>> above is the getDocument method. It gets the document from registry and
>>> put into a hash map. Below is the jaggery method to get the file where I
>>> can get the hash map values successfully but the file content.
>>>
>>>  StoreAPIProxy.prototype.getDocument = function (username, resourcepath,
>>> tenantDomain) {
>>> var document = {};
>>>
>>> var content = APIUtil.getDocument(username, resourcepath,
>>> tenantDomain);
>>> document.data = content.get("Data");
>>> document.contentType = content.get("contentType");
>>> document.name = content.get("name");
>>>
>>> return {
>>> error:false,
>>> document:document
>>> };
>>> }
>>> };
>>>
>>> How do I get the InputStream object returns by java method to jaggery
>>> method?
>>>
>>> Thanks
>>> --
>>> Lakshman Udayakantha
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>> Mobile: *0711241005*
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Denuwanthi De Silva
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com,
>> Email: denuwan...@wso2.com
>> Blog: https://denuwanthi.wordpress.com/
>>
>
>
>
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0711241005*
>
>


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0711241005*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Incorporated carbon-feature-plugin-2.0.0-m1 in MSS and GW projects

[Sameera Jayasoma]

Hi Azeez,

Yeah, this is a major design decision of the new Carbon feature plugin. We
had few design meetings for this plugin, there we finalized the
configuration based on some of the following points.

1) Adopted a Maven dependency-like configuration for features and bundles
instead of the strings and colon(:) configuration. I believe having a
proper/valid XML structure is much better than the previous configuration.
Because,

   - It's clean.
   - Configuration can be validated with a schema.
   - You get the same maven experience.

e.g.


*javax.ws.rs:javax.ws.rs-api*

vs

**
*   javax.ws.rs-api*
*${rs-api.version}*
**


2) Refactored maven goals we had in the previous plugin and came up with
easy to understand, self-explanatory set of Maven goal names.

   - *generate*
   - maven goal for generate carbon features (formerly known as
  p2-feature-gen)


   -
*generate-repo  *
  - maven goal for generate repositories (formerly known as p2-repo-gen)


   - *install*
   - maven goal for install features into a product (formerly known as
  p2-profile-gen)


   - *uninstall*
- maven goal for uninstalling features
   -
*generate-profile *
  - maven goal for generate profiles (formerly known as
  materialize-product)


   - *publish-product*
   - maven goal for publishing a product

Thanks,
Sameera.


On Thu, Oct 22, 2015 at 12:06 AM, Afkham Azeez  wrote:

> Yes, merge the PR. On second thoughts, I think the new XML syntax is
> better than the previous one because it specifically highlights that it is
> using the bundle symbolic name & not the maven group or artifact ID.
>
> On Thu, Oct 22, 2015 at 12:34 PM, Kasun Indrasiri  wrote:
>
>> Should we go ahead with this change?
>>
>> On Mon, Oct 19, 2015 at 5:01 PM, Afkham Azeez  wrote:
>>
>>> I am seeing a lot of introduction of new tags.
>>>
>>> e.g. 1. org.wso2.carbon.p2.category.type:server is now written as
>>>
>>> org.wso2.carbon.p2.category.type
>>> server
>>>
>>>
>>> 2.
>>> javax.ws.rs:javax.ws.rs-api
>>>
>>> is now written as. Also we have the additional burden of specifying the
>>> version again.
>>>
>>> 
>>>javax.ws.rs-api
>>> ${rs-api.version}
>>> 
>>>
>>> Why have we made the configuration more verbose? More XML tags is not
>>> necessarily better.
>>>
>>>
>>> On Mon, Oct 19, 2015 at 3:42 PM, Dinusha Boteju 
>>> wrote:
>>>
 Hi all,

 I have updated the pom files in WSO2 MSS and WSO2 GW projects to
 incorporate carbon-feature-plugin 2.0.0-m1 and sent pull requests to
 relevant repositories.

 jira link for MSS : https://wso2.org/jira/browse/WMS-2
 PR link for MSS : https://github.com/wso2/product-mss/pull/14

 jira link for GW   : https://wso2.org/jira/browse/WGW-1
 
 PR link for GW   : https://github.com/wso2/product-gw/pull/6

 Best regards,
 --
 *Dinusha Boteju*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: dinus...@wso2.com 
 phone:(+94) 776640275 <%28%2B94%29%2039736>

>>>
>>>
>>>
>>> --
>>> *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*
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> *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*
>



-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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

Re: [Dev] Clarification of Feature for DAS

[Anjana Fernando]

Hi Shavantha,

Yeah, Metrics feature also needs to be installed, this was fixed by Gokul
lately. Thanks.

Cheers,
Anjana.

On Wed, Oct 21, 2015 at 1:40 PM, Shavantha Weerasinghe 
wrote:

> Hi Anjana
>
> The document[1] mentions that the below features should be installed for
> ML to be used as a CEP extension. However, we also had to install WSO2
> Carbon - Metrics Group Feature for on DAS in order to use the  ML feature.
> Should DAS to have the Metrics Group Feature installed similar to CEP400.
>
> WSO2 Carbon - ML Siddhi Extension Feature
> WSO2 Carbon - Machine Learner Core Feature
> WSO2 Carbon - Machine Learner Database Service Feature
> WSO2 Carbon - Machine Learner Commons Feature
>
> [1]
> https://docs.wso2.com/display/CEP400/Installing+Machine+Learner+Features
>
> Regards,
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>


-- 
*Anjana Fernando*
Senior Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can't find jira project for carbon-transports

[Dinusha Boteju]

Restructured the project as discussed. PR link for this is [1]. Please
review and revert to me if anything needs to be changed.

[1] - https://github.com/wso2/carbon-transports/pull/5

Thanks,

On Thu, Oct 22, 2015 at 12:04 PM, Afkham Azeez  wrote:

> Ok, go ahead with that structure.
>
> On Thu, Oct 22, 2015 at 11:54 AM, Kasun Indrasiri  wrote:
>
>> Hi Dinusha,
>>
>> We don't have a jira project yet, please send PRs if you need to add
>> anything.
>>
>> I think the structure should be
>>
>> carbon-transports/http/netty... because there will be multiple protocols
>> supported by Netty (tcp, rtsp etc.). So, Netty is too generic.
>>
>> On Thu, Oct 22, 2015 at 11:50 AM, Afkham Azeez  wrote:
>>
>>> I merged your PR.
>>>
>>> Can you restructure this project so that we have the following structure.
>>>
>>> carbon-transports/netty/
>>> carbon-transports/netty/pom.xml
>>> pom.xml
>>>
>>> The idea is that we will have more transports under this repo.
>>>
>>> On Thu, Oct 22, 2015 at 11:42 AM, Dinusha Boteju 
>>> wrote:
>>>
 Hi,

 I have integrated carbon-feature-plugin into carbon-transports.
 Following is the PR link;
 https://github.com/wso2/carbon-transports/pull/4

 Thanks,

 On Wed, Oct 21, 2015 at 3:42 PM, Dinusha Boteju 
 wrote:

> Hi Kasun,
>
> I'm in the process of integrating carbon-feature-plugin into
> carbon-transports project to create a feature from carbon-transports
> bundle. However, I couldn't find a jira project to create a ticket for 
> this
> task. Thus I would like to know under which jira project should I create a
> ticket for this task.
>
> Thanks
> --
> *Dinusha Boteju*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: dinus...@wso2.com 
> phone:(+94) 776640275 <%28%2B94%29%2039736>
>



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

 email: dinus...@wso2.com 
 phone:(+94) 776640275 <%28%2B94%29%2039736>

>>>
>>>
>>>
>>> --
>>> *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*
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> *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*
>



-- 

*Dinusha Boteju*
*Associate Tech Lead,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: dinus...@wso2.com 
phone:(+94) 776640275 <%28%2B94%29%2039736>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Shall we remove API-M 1.9.0 cartridge?

[Imesh Gunaratne]

Hi Nuwan,

We have created two cartridges for API-M [1].
Do you think 1.9.0 one is needed?

https://github.com/wso2/private-paas-cartridges/tree/master/wso2am

Thanks

-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Incorporated carbon-feature-plugin-2.0.0-m1 in MSS and GW projects

[Afkham Azeez]

Yes, merge the PR. On second thoughts, I think the new XML syntax is better
than the previous one because it specifically highlights that it is using
the bundle symbolic name & not the maven group or artifact ID.

On Thu, Oct 22, 2015 at 12:34 PM, Kasun Indrasiri  wrote:

> Should we go ahead with this change?
>
> On Mon, Oct 19, 2015 at 5:01 PM, Afkham Azeez  wrote:
>
>> I am seeing a lot of introduction of new tags.
>>
>> e.g. 1. org.wso2.carbon.p2.category.type:server is now written as
>>
>> org.wso2.carbon.p2.category.type
>> server
>>
>>
>> 2.
>> javax.ws.rs:javax.ws.rs-api
>>
>> is now written as. Also we have the additional burden of specifying the
>> version again.
>>
>> 
>>javax.ws.rs-api
>> ${rs-api.version}
>> 
>>
>> Why have we made the configuration more verbose? More XML tags is not
>> necessarily better.
>>
>>
>> On Mon, Oct 19, 2015 at 3:42 PM, Dinusha Boteju 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have updated the pom files in WSO2 MSS and WSO2 GW projects to
>>> incorporate carbon-feature-plugin 2.0.0-m1 and sent pull requests to
>>> relevant repositories.
>>>
>>> jira link for MSS : https://wso2.org/jira/browse/WMS-2
>>> PR link for MSS : https://github.com/wso2/product-mss/pull/14
>>>
>>> jira link for GW   : https://wso2.org/jira/browse/WGW-1
>>> 
>>> PR link for GW   : https://github.com/wso2/product-gw/pull/6
>>>
>>> Best regards,
>>> --
>>> *Dinusha Boteju*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: dinus...@wso2.com 
>>> phone:(+94) 776640275 <%28%2B94%29%2039736>
>>>
>>
>>
>>
>> --
>> *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*
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
*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] Incorporated carbon-feature-plugin-2.0.0-m1 in MSS and GW projects

[Kasun Indrasiri]

Should we go ahead with this change?

On Mon, Oct 19, 2015 at 5:01 PM, Afkham Azeez  wrote:

> I am seeing a lot of introduction of new tags.
>
> e.g. 1. org.wso2.carbon.p2.category.type:server is now written as
>
> org.wso2.carbon.p2.category.type
> server
>
>
> 2.
> javax.ws.rs:javax.ws.rs-api
>
> is now written as. Also we have the additional burden of specifying the
> version again.
>
> 
>javax.ws.rs-api
> ${rs-api.version}
> 
>
> Why have we made the configuration more verbose? More XML tags is not
> necessarily better.
>
>
> On Mon, Oct 19, 2015 at 3:42 PM, Dinusha Boteju  wrote:
>
>> Hi all,
>>
>> I have updated the pom files in WSO2 MSS and WSO2 GW projects to
>> incorporate carbon-feature-plugin 2.0.0-m1 and sent pull requests to
>> relevant repositories.
>>
>> jira link for MSS : https://wso2.org/jira/browse/WMS-2
>> PR link for MSS : https://github.com/wso2/product-mss/pull/14
>>
>> jira link for GW   : https://wso2.org/jira/browse/WGW-1
>> 
>> PR link for GW   : https://github.com/wso2/product-gw/pull/6
>>
>> Best regards,
>> --
>> *Dinusha Boteju*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: dinus...@wso2.com 
>> phone:(+94) 776640275 <%28%2B94%29%2039736>
>>
>
>
>
> --
> *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*
>



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

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev