[Dev] WSO2 Carbon Kernel 4.4.7 Released

[Jayanga Dissanayake]

The Carbon team is pleased to announce the release of Carbon Kernel 4.4.7.

Improvements and Bug fixes
https://wso2.org/jira/issues/?filter=13113

Known Issues
https://wso2.org/jira/issues/?filter=13114

How to Contribute

   - WSO2 Carbon Kernel code is hosted in github.
   - The Git repository is https://github.com/wso2/carbon-kernel/
   - Carbon Kernel 4.4.7 release tag is
https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7
   - Please report issues at Carbon Jira,
https://wso2.org/jira/browse/CARBON

Contact Us

​WSO2 Carbon developers​ can be contacted via following mailing lists:

   - WSO2 Developers List: dev@wso2.org
   - WSO2 Architecture List: architect...@wso2.org

​You can download the released distribution from the following location.
http://wso2.com/products/carbon/

​Thank you for your interest in WSO2 Carbon Kernel​.

Best Regards
Carbon Team​
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Docker images layered composition

[Isuru Haththotuwa]

Hi Imesh,

Sorry for the late response.

On Tue, Jun 28, 2016 at 9:06 AM, Imesh Gunaratne  wrote:

>
>
> On Mon, Jun 27, 2016 at 11:44 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Imesh,
>>
>> Agreed on the size impact. My concern is that this change does not bring
>> in a significant improvement for the model that we have now.
>>
>
> ​I think it has a significant improvement. If we don't use a base image​,
> each product image will build on top of an OS image and each build will
> download all the prerequisites. As a result the internet bandwidth will get
> utilized unnecessarily. AFAIK we all faced this issue and created our own
> base images to solve the problem. Therefore I think it's better to have a
> base image in the remote repository.
>
> At the time a production environment is being created, users can change
> the base image to an OS image and get the image size optimizations done.
> WDYT?
>
The rationale behind my previous statement is that once the docker images
are pushed to a registry, the users do not have to continuously build them,
but rather can extend from the product Docker images and do development and
testing.

However, I do agree that this change is indeed useful for scenarios where
you need to build images in network isolated environments. In such cases
having a base image is essential, otherwise it would not be possible to
build the Docker images. Therefore,  +1 for adding a base image.

>
> Thanks
>
>
>> Anyway, lets give this a go and try to improve ii as we go along. Anyway
>> we should be able to push proper product images to the Dockerhub once we
>> have OpenJDK support.
>>
>>>
>>> Thanks
>>>

 --
 Thanks and Regards,

 Isuru H.
 +94 716 358 048* *



>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> Lean . Enterprise . Middleware
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploying wso2das 3.x.x on Mesos

[Akila Ravihansa Perera]

[Looping Anjana and Isuru]

@Anjana, Niranda: is it possible to plugin a custom member discovery scheme
for Spark? In the current implementation how does a wso2das with embedded
Spark instance discover the other members?
I'm referring to Spark cluster mode deployment here.

Thanks.

On Wed, Jul 6, 2016 at 6:49 AM, Nirmal Fernando  wrote:

> [Looping Niranda]
>
> On Tue, Jul 5, 2016 at 10:22 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi,
>>
>> Deploying wso2das in Mesos is bit tricky due to lack of overlay network
>> support in Mesos OOTB. This is mainly because Spark cluster (when running
>> in Spark cluster mode) is unable to communicate through Docker IP addresses
>> when they are assigned to different host machines in a multi-node Mesos
>> deployment. I checked the config options in [1] and tried setting
>> SPARK_PUBLIC_DNS parameter to Mesos host IP without any success.
>>
>> The main problem is there is no way to instruct Spark members to bind to
>> the local Docker IP and advertise a different IP (Mesos slave host IP) to
>> other members.
>>
>> @Niranda, Nirmal: is this something we can fix from our side? AFAIU, we
>> are using Hazelcast to discover Spark/wso2das members and adding them to
>> Spark context, right?
>>
>> On a side note, there is a Wiki page explaining how Spark should be used
>> with Mesos in [2]. This is available after Spark 1.2.0. In this approach,
>> we treat each Mesos slave as a Spark member and Spark/Mesos driver can
>> directly schedule tasks on Mesos slaves instead of running Spark itself as
>> a container. We should consider this approach in our C5 based efforts. We
>> can leverage Kubernetes in the same way.
>>
>> IMO, we should recommend users to use wso2das in Spark client mode on
>> Mesos due to these complexities.
>>
>
> +1, if we can't solve above from within DAS.
>
>
>> There is a DCOS Mesos framework for Spark [3] which can be used to deploy
>> Spark on Mesos very easily. We can even leverage DCOS Spark framework in
>> our deploy scripts.
>>
>> [1] http://spark.apache.org/docs/latest/spark-standalone.html
>> [2] http://spark.apache.org/docs/latest/running-on-mesos.html
>> [3] https://docs.mesosphere.com/1.7/usage/service-guides/spark/
>>
>> Thanks.
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
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] [Gsoc2016] [PC] Web (Javascript / D3) based BPMN editor to support a subset of commonly used BPMN constructs

[Heshan Jayasinghe]

Hi,
As we discussed in last meeting this week we plan to finish

   - flow reposition when BPMN element position changes.
   - task resizing
   - text attaching
   - changing task/event/gateway type using property (element icon changed
   with property)


I created "flow reposition when BPMN element position changes" and "task
resizing" but not totally completed.I think i can finish it with in this
week.Can you please send me what are the properties you need for each
element.Then i can complete it with in this week.

github url = https://github.com/heshanjse/BPMNEditor  ( last week update)

Thank You!
regards,
Heshan Jayasinghe

On Tue, Jun 21, 2016 at 6:59 AM, Heshan Jayasinghe 
wrote:

> github url - https://github.com/heshanjse/BPMNEditor
>
> On Tue, Jun 21, 2016 at 6:57 AM, Heshan Jayasinghe 
> wrote:
>
>> Hi Isuru,
>>
>> This is the milestone plan we discussed in the last week.
>>
>> 24/6  - draw flows when moving a node
>>  - add properties to the flow
>>  - create delete functionality to every node.
>>  - add arrow and text to the toolbox
>> 1/7- add text to the task
>>  - task resizing
>>  - change task/event/gateway icon according to the selected
>> property type
>> 8/7- change flow shape from start and end point
>>  - add mutiple connection points in the nodes
>> 15/7  - add zoom event to svg and scroll
>> 29/7  - create property list
>> 5/8- export json in to BPMN
>> 19/8  - redraw element using json array after upload a BPMN file
>>
>> Thanks
>> regards,
>> Heshan Jayasinghe
>>
>>
>>
>> On Mon, Jun 20, 2016 at 2:32 PM, Isuru Wijesinghe 
>> wrote:
>>
>>> Hi Heshan,
>>>
>>> Please update the meeting notes. In addition to that can you please
>>> share with us the milestone plan as we discussed in the last week.
>>>
>>> Thanks,
>>> Isuru.
>>>
>>> On Thu, May 26, 2016 at 11:04 PM, Heshan Jayasinghe 
>>> wrote:
>>>
 github url - https://github.com/heshanjse/BPMNEditor

 On Thu, May 19, 2016 at 12:52 PM, Heshan Jayasinghe  wrote:

> Hi Isuru,
> I completed Start Event,End Event,Gateways and Task.Currently these
> component can move in the canvas.As we discussed in our last meeting I am
> working for packaging the current source code,drawing flows,component
> re-sizing,creating property window and adding text areas to Task
> component.After I applying packaging structure i will share my github
> code.Hope I can send it soon.
> Thank you,
> Regards,
> Heshan Jayasinghe
>
> On Wed, May 18, 2016 at 10:04 AM, Isuru Wijesinghe 
> wrote:
>
>> Hi Heshan,
>>
>> Any update on your progress? Could you please share with us your code
>> through github. Then we can give some feedback.
>>
>> Thanks,
>> Isuru
>>
>> On Thu, Mar 24, 2016 at 1:23 PM, Heshan Jayasinghe <
>> shanu...@gmail.com> wrote:
>>
>>> Hi,
>>> I submit my final proposal through GSOC site.Could you please read
>>> my proposal and add some comments.
>>> Thank you!
>>> regards,
>>> Heshan Jayasinghe
>>>
>>> On Wed, Mar 23, 2016 at 8:38 AM, Isuru Wijesinghe 
>>> wrote:
>>>
 Hi Heshan,

 We have already added few comments. Could you please fix them and
 share the updated proposal ?

 Thanks and Best Regards,

 On Fri, Mar 18, 2016 at 9:48 PM, Isuru Wijesinghe  wrote:

> Hi Heshan,
>
> We appreciate your quick response. The main deliverable of this
> project is a javascript/D3 based BPMN editor which allows Process 
> Center
> users to define business processes using a graphical notation from 
> the *web
> UI*. (No server side involvement). Keep on progressing on the
> project and if you get stuck at any point, don't hesitate to contact 
> us.
>
> Thanks and Best Regards,
>
>
> On Fri, Mar 18, 2016 at 11:35 AM, Heshan Jayasinghe <
> shanu...@gmail.com> wrote:
>
>> HI,
>> Could you please tell me how server side involve in this project?
>> Web Editor can developed as a single page application and we can run 
>> it in
>> java server.hope this application haven't any server side
>> development.Please let me know if there server side development 
>> involve.if
>> there any server side development i willing to complete that task 
>> too.
>>
>> I already complete my proposal and now I am doing final fine
>> tuning of my proposal.I will send it tomorrow.from today onwards I 
>> start my
>> development  for first iteration.
>>
>> Thank you!
>> 

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi,

On Tue, Jul 5, 2016 at 11:38 AM, Osura Rathnayake 
wrote:

> Hi Akila,
>
> Please check the modified code. It now takes the value which is specified
> as localMemberPort in axis2.xml.
>

I still don't see any change to the logic of how member address is
calculated. Can you double check?

Please make sure "target/**" directories are ignored from .gitignore. These
shouldn't be in the repo [1]. You might also need to ignore any IDE
specific files. Have a look at .gitignore in Kubernetes artifacts [2].

I see that you have committed some test cases based on JUnit. Please note
that as a platform we are moving to testng framework so better to use that.
@Imesh, Isuru: Please correct me if I'm wrong.

Shall we get a repo created under wso2-incubator for this?

[1] https://github.com/osuran/azure-membership-scheme/tree/master/target
[2] https://github.com/wso2/kubernetes-artifacts/blob/master/.gitignore

Thanks.
-- 
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] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

On Tue, Jul 5, 2016 at 11:33 AM, Akila Ravihansa Perera 
wrote:

> Hi Osura,
>
> As Isuru mentioned you need to be clear about tenantId since it might
> conflict with Carbon tenantId. As suggested, please rename it to something
> like AZURE_TENANT_ID or something like that.
>
> Regarding localMemberPort in axis2.xml, the value of this parameter should
> be same in all nodes by convention therefore no need read localMemberPort
> parameter value in each member's axis2.xml. When adding members to
> Hazelcast config context you need to take the value of this parameter.
> Because we cannot guarantee that it will be 4000 in every deployment. There
> are some special cases in which we need to change this. Have a look at [1]
> to see how this is handled in Mesos membership scheme.
>
Great! +1 for this approach of considering the Hz port same for a cluster.

>
> [1]
> https://github.com/wso2/mesos-artifacts/blob/master/common/mesos-membership-scheme/src/main/java/org/wso2/carbon/clustering/mesos/MesosMembershipScheme.java#L247
>
> Thanks.
>



-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploying wso2das 3.x.x on Mesos

[Nirmal Fernando]

[Looping Niranda]

On Tue, Jul 5, 2016 at 10:22 PM, Akila Ravihansa Perera 
wrote:

> Hi,
>
> Deploying wso2das in Mesos is bit tricky due to lack of overlay network
> support in Mesos OOTB. This is mainly because Spark cluster (when running
> in Spark cluster mode) is unable to communicate through Docker IP addresses
> when they are assigned to different host machines in a multi-node Mesos
> deployment. I checked the config options in [1] and tried setting
> SPARK_PUBLIC_DNS parameter to Mesos host IP without any success.
>
> The main problem is there is no way to instruct Spark members to bind to
> the local Docker IP and advertise a different IP (Mesos slave host IP) to
> other members.
>
> @Niranda, Nirmal: is this something we can fix from our side? AFAIU, we
> are using Hazelcast to discover Spark/wso2das members and adding them to
> Spark context, right?
>
> On a side note, there is a Wiki page explaining how Spark should be used
> with Mesos in [2]. This is available after Spark 1.2.0. In this approach,
> we treat each Mesos slave as a Spark member and Spark/Mesos driver can
> directly schedule tasks on Mesos slaves instead of running Spark itself as
> a container. We should consider this approach in our C5 based efforts. We
> can leverage Kubernetes in the same way.
>
> IMO, we should recommend users to use wso2das in Spark client mode on
> Mesos due to these complexities.
>

+1, if we can't solve above from within DAS.


> There is a DCOS Mesos framework for Spark [3] which can be used to deploy
> Spark on Mesos very easily. We can even leverage DCOS Spark framework in
> our deploy scripts.
>
> [1] http://spark.apache.org/docs/latest/spark-standalone.html
> [2] http://spark.apache.org/docs/latest/running-on-mesos.html
> [3] https://docs.mesosphere.com/1.7/usage/service-guides/spark/
>
> Thanks.
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] To change theme per product

[Harsha Thirimanna]

Hi Sameera,

Do we have any documentation or blogs to find a way to change complete
theme as product wants ?
Is that possible to write a fragment bundle to org.wso2.carbon.ui to change
theme ?

Now we had a requirement to change footer as in [1], because there will not
be a kernal release before to the next release of IS. But we need to change
this footer before that.

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

thanks

*Harsha Thirimanna*
Associate Tech Lead; WSO2, Inc.; http://wso2.com
* *
*email: **hars...@wso2.com* * cell: +94 71 5186770 *
*twitter: **http://twitter.com/ *
*harshathirimannlinked-in: **http:
**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
*

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

[Dev] [Mesos artifacts] Deploying wso2das 3.x.x on Mesos

[Akila Ravihansa Perera]

Hi,

Deploying wso2das in Mesos is bit tricky due to lack of overlay network
support in Mesos OOTB. This is mainly because Spark cluster (when running
in Spark cluster mode) is unable to communicate through Docker IP addresses
when they are assigned to different host machines in a multi-node Mesos
deployment. I checked the config options in [1] and tried setting
SPARK_PUBLIC_DNS parameter to Mesos host IP without any success.

The main problem is there is no way to instruct Spark members to bind to
the local Docker IP and advertise a different IP (Mesos slave host IP) to
other members.

@Niranda, Nirmal: is this something we can fix from our side? AFAIU, we are
using Hazelcast to discover Spark/wso2das members and adding them to Spark
context, right?

On a side note, there is a Wiki page explaining how Spark should be used
with Mesos in [2]. This is available after Spark 1.2.0. In this approach,
we treat each Mesos slave as a Spark member and Spark/Mesos driver can
directly schedule tasks on Mesos slaves instead of running Spark itself as
a container. We should consider this approach in our C5 based efforts. We
can leverage Kubernetes in the same way.

IMO, we should recommend users to use wso2das in Spark client mode on Mesos
due to these complexities. There is a DCOS Mesos framework for Spark [3]
which can be used to deploy Spark on Mesos very easily. We can even
leverage DCOS Spark framework in our deploy scripts.

[1] http://spark.apache.org/docs/latest/spark-standalone.html
[2] http://spark.apache.org/docs/latest/running-on-mesos.html
[3] https://docs.mesosphere.com/1.7/usage/service-guides/spark/

Thanks.

-- 
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] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)

[Prabath Siriwardana]

When we are implementing the REST profile XACML - can we implement it as a
microservice on MSF4J? It needs to be an independent deployable unit -
which should function with a set of policies loaded from the filesystem...
Can we do this..?

Thanks & regards,
-Prbath

On Mon, Jul 4, 2016 at 11:44 PM, Pushpalanka Jayawardhana 
wrote:

> Hi Manujith,
>
> Please find the comments in line.
>
> On Mon, Jul 4, 2016 at 8:11 PM, Manujith Pallewatte  > wrote:
>
>> Hi all,
>>
>> So to start working on the points discussed in the mid evaluation, first
>> is to align the service with the REST profile of XACML 3.0 [1]
>> But according to the spec only the following 2 resources are defined
>>
>> 1) home - entry point for REST service, returns links to other resources
>> 2) pdp - resource that given a XACML request presents the XACML response
>>
>> but since the existing SOAP entitlement service exposes additional
>> services such as
>> getBooleanDecision, getDecisionByAttributes etc. there arises 2 issues
>>
>> 1) how to name those additional resources?
>>
> Let's have some convincing names for you as of now. We can refine them
> later in review. Try to have inputs from the topic "5.1 PROPER NAMING" from
> the rest api guideline while paper we pointed before.
>
>> 2) how to let the clients accessing the service know of the required
>> structure of each of these requests that are not defined in the XACML spec?
>>
> Please have a look at the possibility of using swagger for this. This is
> already used in WSO2 Api Manager[1], but not yet in WSO2 IS. Would be great
> if you can evaluate the possibility of using it.  Basic idea is to
> represent the REST API according to Swagger specification similar to WSDL
> we have for SOAP.
>
> [1] -
> https://docs.wso2.com/display/AM1100/Edit+an+API+Using+the+Swagger+UI
>
>>
>> Please provide your suggestions on this
>>
>> Thank You
>> Best Regards,
>> Manujith
>>
>> [1]
>> http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html
>>
>> On Thu, Jun 23, 2016 at 3:42 PM, Omindu Rathnaweera 
>> wrote:
>>
>>> Good Work Manujith!
>>>
>>> Adding to this. Figure out a way to drop null values from the JSON
>>> response with Jackson level configurations. Also have a look at XACML JSON
>>> profile [1]. It will have guidelines on dealing with JSON inputs/outputs.
>>>
>>> [1] -
>>> http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html
>>>
>>> Regards,
>>> Omindu.
>>>
>>> On Thu, Jun 23, 2016 at 3:31 PM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi all,

 We had the mid-evaluation review, and I've summarized the key points
 discussed here

 1) Prioritize on the complete JSON implementation for all 5 services
 methods
 2) Comply the service fully with XACML 3.0 REST specification (Read on
 the spec and get a firm understanding on all key concepts)
 3) Leave the hard coded authenticators as it is for now
 4) Using custom client / server exception to be returned in a case of
 an exception
 5) Follow the code quality guidelines (specially in the cases of
 improper exception handling)

 Special thanks to everyone for their time in reviewing.

 Thank You,
 Manujith

 On Sun, Jun 12, 2016 at 10:43 PM, Manujith Pallewatte <
 manujith...@gmail.com> wrote:

> Hi all,
>
> After refactoring and reviewing code using above suggestions, I added
> a PR, which can be found at [1]
>
> Regards,
> Manujith
>
> [1] https://github.com/wso2/carbon-identity-framework/pull/282
>
> On Sat, Jun 11, 2016 at 12:52 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi Manuranga,
>>
>> I did referred to the guidelines, but was not successful in figuring
>> out suitable end point names. So Pushpalanka suggested to take 
>> community's
>> ideas in naming them. Any pointers as for which I can improve the names?
>> According to the guide it says to identify the resources first
>> Going on that, I identified the Policy Decision, Entitlement
>> Attributes and Entitlements as resources, but since some resources have
>> only one methods call in it, having a separate path seem redundant. And
>> didnt follow much from there, please let me know your ideas on the 
>> resource
>> identification
>>
>> Thank You
>> Regards,
>> Manujith
>>
>> On Sat, Jun 11, 2016 at 12:21 AM, Manuranga Perera 
>> wrote:
>>
>>> Hi Manujith,
>>>
>>> Please have a look at WSO2 REST API guideline [1]. This will help
>>> you to improve the URL nameing.
>>>
>>> [1] http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/
>>>
>>> On Thu, Jun 9, 2016 at 3:49 PM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi Pushpalanka,

Re: [Dev] [BPS][BPMN-Explorer][UI/UX] How to get Time input from user using daterangepicker

[Dakshika Jayathilaka]

Hi Malinda,

change format attribute as you want to get time values on text input.

ex: format: 'MM/DD/ h:mm A'

  $(function() {
$('input[name="daterange"]').daterangepicker({ timePicker: true,
timePickerIncrement: 30, locale: { format: 'MM/DD/ h:mm A' } }); });



Regards,

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

On Tue, Jul 5, 2016 at 6:37 PM, Milinda Perera  wrote:

> Hi UI/UX team,
>
> In our BPS BPMN Explorer We need to add Start time (Date and time) and End
> time (Date and time) for substitution UI. I used daterangepicker as
> follows
>
> In HTML:
>
>   onfocus="setDatePicker('subStartDate')">
>
> In JS setDatePicker(dateElement) function
> var elementID = '#' + dateElement;
> $(elementID).daterangepicker({
> singleDatePicker: true,
> showDropdowns: true,
> timePicker: true,
> parentEl: '#addSubstituteModalContent',
> locale: {
> format: 'MM/DD/'
> }
> });
>
> but when we select relevant time and date in pop-up, and click apply, only
> the date appears in the text input. I have attached screenshot also. What
> is the proper recommended way to get time input?
>
> Are there any recommened other options ?
>
> Thanks,
> Milinda
>
> --
> Milinda Perera
> Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Inclusion of available APIs under Deleted APIs list in API Deployment Stats in Log Analyzer

[Ruwan Abeykoon]

Hi Nuwan, Maneesha,
I am totally agree that now we have this information and can be provided in
another dashboard.

However, Current analytics is based on normal logs, not based on audit log.
I do not think it is right time to add the feature to read the audit logs,
since it is time to stabilise the code and do any bug fixes in current
code, before the APIM 2.0.0 GA.

I do not agree the $subject as a bug. But I would certainly want to add the
feature in the next proper release.

Cheers,
Ruwan

On Tue, Jul 5, 2016 at 3:35 PM, Nuwan Dias  wrote:

> Yes, we now have audit logs on the API Manager for API create, update and
> remove. The ideal solution is to use these logs to derive those data.
>
> On Tue, Jul 5, 2016 at 1:42 PM, Maneesha Wijesekara 
> wrote:
>
>> Hi Sajith,
>>
>> Agreed with how the log analyzer works when an API is updated. But when
>> considering the user point of view, an API shouldn't be listed in 'Deleted
>> APIs' list if it's still available. Because a user might get confused when
>> the statistics in 'Deleted APIs' shows some API that he/she used right now.
>>
>> Any suggestion to overcome this ? Probably a change in logs when editing
>> an API might be a solution for this.
>>
>> Regards
>> Maneesha
>>
>> On Tue, Jul 5, 2016 at 1:11 PM, Sajith Perera  wrote:
>>
>>>
>>> Hi Maneesha,
>>>
>>> Log analyzer purely based on the log events which are generated by a
>>> particular product. For each stat, there are set of keywords and rules in
>>> log lines, which we are identifying as unique for that scenario.
>>>
>>> Regarding the above mentioned scenario, if there is an update on an API
>>> in given time frame, there will be two log lines printed with "Destroying"
>>> and "Initiating" keywords.
>>>
>>> 1. Deleted Artifact X
>>> 2. Created Artifact X
>>>
>>> These events are listed as "Deployed Api X" and "Deleted Api X" tables
>>> in the given time frame, as they are the "facts" within the given time
>>> frame.
>>>
>>> Thanks,
>>> SajithD
>>>
>>> On Tue, Jul 5, 2016 at 12:44 PM, Maneesha Wijesekara 
>>> wrote:
>>>
 Hi all,

 Currently 'API Deployment Stats' in Log Analyzer listed both Deployed
 APIs and Deleted APIs. But I've noticed that some available APIs (not yet
 deleted) are also listed under 'Deleted APIs' [1]. The reason behind this
 is when an API is edited, it will destroyed and again re-deployed. That log
 will cause to include an available API under 'Deleted APIs'. But when it
 comes to the function 'Deleted APIs', it should only list the names of APIs
 which are actually deleted.

 Any thoughts on this ?

 [1] https://wso2.org/jira/browse/ANLYAPIM-79

 --
 Maneesha Wijesekara
 Software Engineer - QA Team
 WSO2 Inc.

 Email: manee...@wso2.com
 Linkedin: http://linkedin.com/in/maneeshawijesekara
 Mobile: +94712443119

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


>>>
>>>
>>> --
>>> Sajith Dimal
>>> Software Engineer
>>> Mobile : +94783101496
>>> WSO2 Inc. | http://wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> Maneesha Wijesekara
>> Software Engineer - QA Team
>> WSO2 Inc.
>>
>> Email: manee...@wso2.com
>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>> Mobile: +94712443119
>>
>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 

*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

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

Re: [Dev] Getting Error while installing iOS features to EMM 2.1.0

[Geeth Munasinghe]

Hi Chathura,

Please refer the following mail [1]. You can find the answer.

[1] [EMM][iOS] Getting exceptions while installing iOS features

Thanks
Geeth


*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226

On Tue, Jul 5, 2016 at 2:21 PM, Chathura Dilan  wrote:

> Hi All,
>
> I'm getting the following error while installing iOS features to EMM
> 2.1.0. Anyone know what's the reason for the issue?
>
>
> Error creating bean with name 'enrollmentServiceBean' defined in URL
> [jndi:/localhost/ios-enrollment/WEB-INF/cxf-servlet.xml]: Instantiation of
> bean failed; nested exception is java.lang.NoClassDefFoundError:
> org/wso2/carbon/device/mgt/ios/core/exception/IOSEnrollmentException
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1327)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
> at
> org.apache.cxf.transport.servlet.CXFServlet.createSpringContext(CXFServlet.java:151)
> at org.apache.cxf.transport.servlet.CXFServlet.loadBus(CXFServlet.java:74)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:76)
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5262)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5550)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
> at
> org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:290)
> at
> org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:198)
> at
> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWebappDeployment(TomcatGenericWebappsDeployer.java:258)
> at
> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWarWebappDeployment(TomcatGenericWebappsDeployer.java:208)
> at
> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleHotDeployment(TomcatGenericWebappsDeployer.java:175)
> at
> org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.deploy(TomcatGenericWebappsDeployer.java:140)
> at
> org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deployThisWebApp(AbstractWebappDeployer.java:224)
> at
> org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deploy(AbstractWebappDeployer.java:114)
> at
> org.wso2.carbon.webapp.deployer.WebappDeployer.deploy(WebappDeployer.java:42)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
> at
> 

[Dev] FILE UPLOAD FROM ESB

[John Q]

Hello folks,
can any body tell me hot to upload a file from a sequence in the ESB? I
mean, there's an HTTP endpoint waiting for a multipart/form-data request
coming with a file, just the same way we do from an HTTP form, but I need
to do it from the ESB.

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

Re: [Dev] [Architecture] [C5] Upgrading Kernel Equinox version to Neon Releases

[Niranjan Karunanandham]

+1 to upgrade the tycho plugin. Currently we are using 0.13.0 and AFAIR the
latest one is 0.25.0.

Regards,
Nira

On Tue, Jul 5, 2016 at 3:11 PM, Sameera Jayasoma  wrote:

> +1 for this.
>
> On Tue, Jul 5, 2016 at 2:48 PM, Chanaka Cooray  wrote:
>
>> [+architecture]
>>
>> On Tue, Jul 5, 2016 at 1:53 PM, Chanaka Cooray  wrote:
>>
>>> Hi all,
>>>
>>> We have decided to upgrade the equinox version in kernel to Neon release
>>> which is the latest release of the equinox[1]. This has to be done due to
>>> several issues in kernel including [2] with the current equinox version.
>>> Addition to that, it is also required to upgrade tycho versions in
>>> carbon-maven-plugins [3] because of a jarsigner issue with the JDK 7, 8.
>>>
>>> [1] http://download.eclipse.org/equinox/
>>> [2] https://wso2.org/jira/browse/CARBON-15976
>>> [3] https://github.com/wso2/carbon-maven-plugins
>>>
>>> Thanks,
>>> Chanaka.
>>> --
>>> Chanaka Cooray
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> Email: chana...@wso2.com
>>> Mobile: +94713149860
>>>
>>>
>>
>>
>> --
>> Chanaka Cooray
>> Software Engineer, WSO2 Inc. http://wso2.com
>> Email: chana...@wso2.com
>> Mobile: +94713149860
>>
>>
>
>
> --
> 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
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 


*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

[Uvindra Dias Jayasinha]

Thanks Viraj

On 5 July 2016 at 15:52, Viraj Senevirathne  wrote:

> PR is merged https://github.com/wso2/carbon-mediation/pull/671.
>
> On Tue, Jul 5, 2016 at 3:44 PM, Uvindra Dias Jayasinha 
> wrote:
>
>> Ping!
>>
>> ESB Team can we get the above PR merged please?
>>
>> On 27 June 2016 at 19:26, Uvindra Dias Jayasinha 
>> wrote:
>>
>>> Thanks Kishanthan
>>>
>>> If we were to fix this by calling startTenantFlow() the fix would be a
>>> lot more complicated and may lead to other issues. So I have tested the
>>> original fix done by Jagath in this case and didn't run into any issues
>>> functional wise. Though I could not recreate the issue in the first place
>>> so we still dont know what causes this exactly.
>>>
>>> @ChanakaF, I have sent the PR with the fix that I tested[1], please merge
>>>
>>> [1] https://github.com/wso2/carbon-mediation/pull/671
>>>
>>> On 27 June 2016 at 17:15, Kishanthan Thangarajah 
>>> wrote:
>>>


 On Mon, Jun 27, 2016 at 12:13 PM, Uvindra Dias Jayasinha <
 uvin...@wso2.com> wrote:

> Before I just apply the stated fix I would like some feedback from the
> Carbon team regarding what maybe causing this issue.
>
> So here is what we are seeing so far,
>
> 1. IllegalStateException is being thrown by
> CarbonContextDataHolder.setTenantDomain()
>
> 2. The logic in setTenantDomain() is as follows,
>   a) If the this.tenantDomain of the CarbonContextDataHolder is
> null or is equal to the super tenant domain then its fine
>
>   b) But if the this.tenantDomain of the CarbonContextDataHolder
> is Not Equal to the tenant domain value that is being set then there is a
> chance for the IllegalStateException to be thrown.
>
> So what this seems to indicate is that you cannot call
> setTenantDomain() if the current tenantDomain within the carbon context is
> already set to another tenants domain. This could be due to
> startTenantFlow() not being called before setting the tenant domain. Could
> this be the cause?
>

 If the tenant domain is already set, then it can not be set again
 within the same thread flow, unless you start a new tenant flow or setting
 a tenant domain other than super tenant.

 Starting a new tenant flow means, the current ContextHolder instance
 will be pushed onto the stack and then the thread would see a new
 ContextHolder instance until that tenant flow is properly ended (popped
 from the stack), which then the thread would see the previous ContextHolder
 instance which was there before starting the tenant flow.


> On 24 June 2016 at 14:44, Uvindra Dias Jayasinha 
> wrote:
>
>> Problem is the issue is intermittent so its difficult to verify but I
>> will test the fix out and send a PR
>>
>> On 24 June 2016 at 13:52, Chanaka Fernando  wrote:
>>
>>> Hi Uvindra,
>>>
>>> Could you please verify the fix and send us a PR so that we can
>>> merge it?
>>>
>>> On Fri, Jun 24, 2016 at 1:02 PM, Uvindra Dias Jayasinha <
>>> uvin...@wso2.com> wrote:
>>>
 Hi All,

 The original issue encountered in [1] was fixed via the resolution
 of [2].

 But now this has been reopened and in this case the same issue has
 got exposed, but on this occasion the call stack is different. This is
 happening when setting the tenant info at [3]. So we need to apply the 
 same
 fix that was done in resolving [2] to the WSO2Registry class when 
 setting
 the tenant info.

 Can we get this fixed?


 [1] https://wso2.org/jira/browse/APIMANAGER-4202
 [2] https://wso2.org/jira/browse/ESBJAVA-4333
 [3]
 https://github.com/wso2/carbon-mediation/blob/v4.6.1-BETA3/components/mediation-registry/org.wso2.carbon.mediation.registry/src/main/java/org/wso2/carbon/mediation/registry/WSO2Registry.java#L747


 --
 Regards,
 Uvindra

 Mobile: 33962

>>>
>>>
>>>
>>> --
>>> Thank you and Best Regards,
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>> Uvindra
>>
>> Mobile: 33962
>>
>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>



 --
 *Kishanthan Thangarajah*
 Technical Lead,
 Platform 

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

[Viraj Senevirathne]

PR is merged https://github.com/wso2/carbon-mediation/pull/671.

On Tue, Jul 5, 2016 at 3:44 PM, Uvindra Dias Jayasinha 
wrote:

> Ping!
>
> ESB Team can we get the above PR merged please?
>
> On 27 June 2016 at 19:26, Uvindra Dias Jayasinha  wrote:
>
>> Thanks Kishanthan
>>
>> If we were to fix this by calling startTenantFlow() the fix would be a
>> lot more complicated and may lead to other issues. So I have tested the
>> original fix done by Jagath in this case and didn't run into any issues
>> functional wise. Though I could not recreate the issue in the first place
>> so we still dont know what causes this exactly.
>>
>> @ChanakaF, I have sent the PR with the fix that I tested[1], please merge
>>
>> [1] https://github.com/wso2/carbon-mediation/pull/671
>>
>> On 27 June 2016 at 17:15, Kishanthan Thangarajah 
>> wrote:
>>
>>>
>>>
>>> On Mon, Jun 27, 2016 at 12:13 PM, Uvindra Dias Jayasinha <
>>> uvin...@wso2.com> wrote:
>>>
 Before I just apply the stated fix I would like some feedback from the
 Carbon team regarding what maybe causing this issue.

 So here is what we are seeing so far,

 1. IllegalStateException is being thrown by
 CarbonContextDataHolder.setTenantDomain()

 2. The logic in setTenantDomain() is as follows,
   a) If the this.tenantDomain of the CarbonContextDataHolder is
 null or is equal to the super tenant domain then its fine

   b) But if the this.tenantDomain of the CarbonContextDataHolder is
 Not Equal to the tenant domain value that is being set then there is a
 chance for the IllegalStateException to be thrown.

 So what this seems to indicate is that you cannot call
 setTenantDomain() if the current tenantDomain within the carbon context is
 already set to another tenants domain. This could be due to
 startTenantFlow() not being called before setting the tenant domain. Could
 this be the cause?

>>>
>>> If the tenant domain is already set, then it can not be set again within
>>> the same thread flow, unless you start a new tenant flow or setting a
>>> tenant domain other than super tenant.
>>>
>>> Starting a new tenant flow means, the current ContextHolder instance
>>> will be pushed onto the stack and then the thread would see a new
>>> ContextHolder instance until that tenant flow is properly ended (popped
>>> from the stack), which then the thread would see the previous ContextHolder
>>> instance which was there before starting the tenant flow.
>>>
>>>
 On 24 June 2016 at 14:44, Uvindra Dias Jayasinha 
 wrote:

> Problem is the issue is intermittent so its difficult to verify but I
> will test the fix out and send a PR
>
> On 24 June 2016 at 13:52, Chanaka Fernando  wrote:
>
>> Hi Uvindra,
>>
>> Could you please verify the fix and send us a PR so that we can merge
>> it?
>>
>> On Fri, Jun 24, 2016 at 1:02 PM, Uvindra Dias Jayasinha <
>> uvin...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> The original issue encountered in [1] was fixed via the resolution
>>> of [2].
>>>
>>> But now this has been reopened and in this case the same issue has
>>> got exposed, but on this occasion the call stack is different. This is
>>> happening when setting the tenant info at [3]. So we need to apply the 
>>> same
>>> fix that was done in resolving [2] to the WSO2Registry class when 
>>> setting
>>> the tenant info.
>>>
>>> Can we get this fixed?
>>>
>>>
>>> [1] https://wso2.org/jira/browse/APIMANAGER-4202
>>> [2] https://wso2.org/jira/browse/ESBJAVA-4333
>>> [3]
>>> https://github.com/wso2/carbon-mediation/blob/v4.6.1-BETA3/components/mediation-registry/org.wso2.carbon.mediation.registry/src/main/java/org/wso2/carbon/mediation/registry/WSO2Registry.java#L747
>>>
>>>
>>> --
>>> Regards,
>>> Uvindra
>>>
>>> Mobile: 33962
>>>
>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>



 --
 Regards,
 Uvindra

 Mobile: 33962

>>>
>>>
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Technical Lead,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com
>>> *
>>> Twitter - *http://twitter.com/kishanthan
>>> 

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

[Uvindra Dias Jayasinha]

Ping!

ESB Team can we get the above PR merged please?

On 27 June 2016 at 19:26, Uvindra Dias Jayasinha  wrote:

> Thanks Kishanthan
>
> If we were to fix this by calling startTenantFlow() the fix would be a lot
> more complicated and may lead to other issues. So I have tested the
> original fix done by Jagath in this case and didn't run into any issues
> functional wise. Though I could not recreate the issue in the first place
> so we still dont know what causes this exactly.
>
> @ChanakaF, I have sent the PR with the fix that I tested[1], please merge
>
> [1] https://github.com/wso2/carbon-mediation/pull/671
>
> On 27 June 2016 at 17:15, Kishanthan Thangarajah 
> wrote:
>
>>
>>
>> On Mon, Jun 27, 2016 at 12:13 PM, Uvindra Dias Jayasinha <
>> uvin...@wso2.com> wrote:
>>
>>> Before I just apply the stated fix I would like some feedback from the
>>> Carbon team regarding what maybe causing this issue.
>>>
>>> So here is what we are seeing so far,
>>>
>>> 1. IllegalStateException is being thrown by
>>> CarbonContextDataHolder.setTenantDomain()
>>>
>>> 2. The logic in setTenantDomain() is as follows,
>>>   a) If the this.tenantDomain of the CarbonContextDataHolder is null
>>> or is equal to the super tenant domain then its fine
>>>
>>>   b) But if the this.tenantDomain of the CarbonContextDataHolder is
>>> Not Equal to the tenant domain value that is being set then there is a
>>> chance for the IllegalStateException to be thrown.
>>>
>>> So what this seems to indicate is that you cannot call setTenantDomain()
>>> if the current tenantDomain within the carbon context is already set to
>>> another tenants domain. This could be due to startTenantFlow() not being
>>> called before setting the tenant domain. Could this be the cause?
>>>
>>
>> If the tenant domain is already set, then it can not be set again within
>> the same thread flow, unless you start a new tenant flow or setting a
>> tenant domain other than super tenant.
>>
>> Starting a new tenant flow means, the current ContextHolder instance will
>> be pushed onto the stack and then the thread would see a new ContextHolder
>> instance until that tenant flow is properly ended (popped from the stack),
>> which then the thread would see the previous ContextHolder instance which
>> was there before starting the tenant flow.
>>
>>
>>> On 24 June 2016 at 14:44, Uvindra Dias Jayasinha 
>>> wrote:
>>>
 Problem is the issue is intermittent so its difficult to verify but I
 will test the fix out and send a PR

 On 24 June 2016 at 13:52, Chanaka Fernando  wrote:

> Hi Uvindra,
>
> Could you please verify the fix and send us a PR so that we can merge
> it?
>
> On Fri, Jun 24, 2016 at 1:02 PM, Uvindra Dias Jayasinha <
> uvin...@wso2.com> wrote:
>
>> Hi All,
>>
>> The original issue encountered in [1] was fixed via the resolution of
>> [2].
>>
>> But now this has been reopened and in this case the same issue has
>> got exposed, but on this occasion the call stack is different. This is
>> happening when setting the tenant info at [3]. So we need to apply the 
>> same
>> fix that was done in resolving [2] to the WSO2Registry class when setting
>> the tenant info.
>>
>> Can we get this fixed?
>>
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-4202
>> [2] https://wso2.org/jira/browse/ESBJAVA-4333
>> [3]
>> https://github.com/wso2/carbon-mediation/blob/v4.6.1-BETA3/components/mediation-registry/org.wso2.carbon.mediation.registry/src/main/java/org/wso2/carbon/mediation/registry/WSO2Registry.java#L747
>>
>>
>> --
>> Regards,
>> Uvindra
>>
>> Mobile: 33962
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>


 --
 Regards,
 Uvindra

 Mobile: 33962

>>>
>>>
>>>
>>> --
>>> Regards,
>>> Uvindra
>>>
>>> Mobile: 33962
>>>
>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan *
>>
>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>



-- 
Regards,
Uvindra

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

Re: [Dev] [APIM] Inclusion of available APIs under Deleted APIs list in API Deployment Stats in Log Analyzer

[Nuwan Dias]

Yes, we now have audit logs on the API Manager for API create, update and
remove. The ideal solution is to use these logs to derive those data.

On Tue, Jul 5, 2016 at 1:42 PM, Maneesha Wijesekara 
wrote:

> Hi Sajith,
>
> Agreed with how the log analyzer works when an API is updated. But when
> considering the user point of view, an API shouldn't be listed in 'Deleted
> APIs' list if it's still available. Because a user might get confused when
> the statistics in 'Deleted APIs' shows some API that he/she used right now.
>
> Any suggestion to overcome this ? Probably a change in logs when editing
> an API might be a solution for this.
>
> Regards
> Maneesha
>
> On Tue, Jul 5, 2016 at 1:11 PM, Sajith Perera  wrote:
>
>>
>> Hi Maneesha,
>>
>> Log analyzer purely based on the log events which are generated by a
>> particular product. For each stat, there are set of keywords and rules in
>> log lines, which we are identifying as unique for that scenario.
>>
>> Regarding the above mentioned scenario, if there is an update on an API
>> in given time frame, there will be two log lines printed with "Destroying"
>> and "Initiating" keywords.
>>
>> 1. Deleted Artifact X
>> 2. Created Artifact X
>>
>> These events are listed as "Deployed Api X" and "Deleted Api X" tables in
>> the given time frame, as they are the "facts" within the given time frame.
>>
>> Thanks,
>> SajithD
>>
>> On Tue, Jul 5, 2016 at 12:44 PM, Maneesha Wijesekara 
>> wrote:
>>
>>> Hi all,
>>>
>>> Currently 'API Deployment Stats' in Log Analyzer listed both Deployed
>>> APIs and Deleted APIs. But I've noticed that some available APIs (not yet
>>> deleted) are also listed under 'Deleted APIs' [1]. The reason behind this
>>> is when an API is edited, it will destroyed and again re-deployed. That log
>>> will cause to include an available API under 'Deleted APIs'. But when it
>>> comes to the function 'Deleted APIs', it should only list the names of APIs
>>> which are actually deleted.
>>>
>>> Any thoughts on this ?
>>>
>>> [1] https://wso2.org/jira/browse/ANLYAPIM-79
>>>
>>> --
>>> Maneesha Wijesekara
>>> Software Engineer - QA Team
>>> WSO2 Inc.
>>>
>>> Email: manee...@wso2.com
>>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>>> Mobile: +94712443119
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sajith Dimal
>> Software Engineer
>> Mobile : +94783101496
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Maneesha Wijesekara
> Software Engineer - QA Team
> WSO2 Inc.
>
> Email: manee...@wso2.com
> Linkedin: http://linkedin.com/in/maneeshawijesekara
> Mobile: +94712443119
>



-- 
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] [C5] Upgrading Kernel Equinox version to Neon Releases

[Sameera Jayasoma]

+1 for this.

On Tue, Jul 5, 2016 at 2:48 PM, Chanaka Cooray  wrote:

> [+architecture]
>
> On Tue, Jul 5, 2016 at 1:53 PM, Chanaka Cooray  wrote:
>
>> Hi all,
>>
>> We have decided to upgrade the equinox version in kernel to Neon release
>> which is the latest release of the equinox[1]. This has to be done due to
>> several issues in kernel including [2] with the current equinox version.
>> Addition to that, it is also required to upgrade tycho versions in
>> carbon-maven-plugins [3] because of a jarsigner issue with the JDK 7, 8.
>>
>> [1] http://download.eclipse.org/equinox/
>> [2] https://wso2.org/jira/browse/CARBON-15976
>> [3] https://github.com/wso2/carbon-maven-plugins
>>
>> Thanks,
>> Chanaka.
>> --
>> Chanaka Cooray
>> Software Engineer, WSO2 Inc. http://wso2.com
>> Email: chana...@wso2.com
>> Mobile: +94713149860
>>
>>
>
>
> --
> Chanaka Cooray
> Software Engineer, WSO2 Inc. http://wso2.com
> Email: chana...@wso2.com
> Mobile: +94713149860
>
>


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

[Dev] Getting Error while installing iOS features to EMM 2.1.0

[Chathura Dilan]

Getting  following error while restarting the server after install the
features

ERROR {org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer} -
 org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
java.lang.NullPointerException (/emm/modules/utility.js#26)
(/emm/config/init.js#27)
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
java.lang.NullPointerException (/emm/modules/utility.js#26)
(/emm/config/init.js#27)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)
at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
at
org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer.executeScripts(TomcatJaggeryWebappsDeployer.java:501)
at
org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer.access$500(TomcatJaggeryWebappsDeployer.java:64)
at
org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer$JaggeryConfListener.lifecycleEvent(TomcatJaggeryWebappsDeployer.java:316)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:347)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5591)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at
org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:290)
at
org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:212)
at
org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer.handleWebappDeployment(TomcatJaggeryWebappsDeployer.java:213)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleExplodedWebappDeployment(TomcatGenericWebappsDeployer.java:247)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleHotDeployment(TomcatGenericWebappsDeployer.java:173)
at
org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer.deploy(TomcatJaggeryWebappsDeployer.java:116)
at
org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deployThisWebApp(AbstractWebappDeployer.java:224)
at
org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deploy(AbstractWebappDeployer.java:114)
at
org.jaggeryjs.jaggery.deployer.JaggeryDeployer.deploy(JaggeryDeployer.java:59)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.synapse.Axis2SynapseController.deployMediatorExtensions(Axis2SynapseController.java:743)
at
org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:388)
at org.apache.synapse.ServerManager.start(ServerManager.java:181)
at
org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:452)
at
org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:196)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at

Re: [Dev] [C5] Upgrading Kernel Equinox version to Neon Releases

[Chanaka Cooray]

[+architecture]

On Tue, Jul 5, 2016 at 1:53 PM, Chanaka Cooray  wrote:

> Hi all,
>
> We have decided to upgrade the equinox version in kernel to Neon release
> which is the latest release of the equinox[1]. This has to be done due to
> several issues in kernel including [2] with the current equinox version.
> Addition to that, it is also required to upgrade tycho versions in
> carbon-maven-plugins [3] because of a jarsigner issue with the JDK 7, 8.
>
> [1] http://download.eclipse.org/equinox/
> [2] https://wso2.org/jira/browse/CARBON-15976
> [3] https://github.com/wso2/carbon-maven-plugins
>
> Thanks,
> Chanaka.
> --
> Chanaka Cooray
> Software Engineer, WSO2 Inc. http://wso2.com
> Email: chana...@wso2.com
> Mobile: +94713149860
>
>


-- 
Chanaka Cooray
Software Engineer, WSO2 Inc. http://wso2.com
Email: chana...@wso2.com
Mobile: +94713149860
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Jayanga Dissanayake]

Hi all,

Thanks for testing and verifying Carbon Kernel 4.4.7 RC1.

We are closing this vote now. This vote has passed with 10 +1s and 0 -1s.
The only reported issue is (viewing issues of the P2 repo)[1], which is not
a blocker. Hence, we will proceed with the Carbon Kernel 4.4.7 release.

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

Thanks,
Jayanga.

*Jayanga Dissanayake*
Associate Technical Lead
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259

On Tue, Jul 5, 2016 at 2:13 PM, Rajith Roshan  wrote:

> Hi all,
>
> Tested G-Reg 5.3.0 Snapshot with kernel 4.4.7 and ran integration test
> without any issues.
>
> [x] Stable - go ahead and release
>
>
> Thanks!
> Rajith
>
> On Tue, Jul 5, 2016 at 1:19 PM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> Hi,
>>
>> Tested with ESB 5.0.0-SNAPSHOT and executed integrated tests. No issues
>> observed.
>>
>> [x] Stable - go ahead and release.
>>
>> Thanks.
>>
>> On Mon, Jul 4, 2016 at 10:56 PM, Hasitha Aravinda 
>> wrote:
>>
>>> Tested with BPS 3.6.0-SNAPSHOT. No issue found.
>>>
>>> [x] Stable - go ahead and release.
>>>
>>> Thanks,
>>> Hasitha.
>>>
>>> On Mon, Jul 4, 2016 at 6:42 PM, Kasun Bandara  wrote:
>>>
 Hi all,

 I could successfully run IS test suit with the upgraded Kernel 4.4.7-
 RC1. Hence +1 for the release.

 Thanks,
 Kasun

 On Mon, Jul 4, 2016 at 5:35 PM, Chamalee De Silva 
 wrote:

> P.S. Test done base done API Manager 2.0.0 beta-2
>
> On Mon, Jul 4, 2016 at 5:33 PM, Chamalee De Silva 
> wrote:
>
>> Hi,
>> I tested the kernel 4.4.7 RC1 with
>>
>> MySQL 5.6 and  5.7,
>> Oracle 11g,
>> PostgreSQL 9.3
>>
>> and they worked without an issue.
>>
>> [x] Stable - go ahead and release.
>>
>>
>>
>> Thanks,
>> Chamalee
>>
>> On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage 
>> wrote:
>>
>>> Hi,
>>>
>>> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find
>>> any issue related to this RC.
>>>
>>> *Note :* Feature repo not shown issue [1], introduced with kernel
>>> 4.4.6 is observed. Hope this will be fixed in a future release.
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-15973
>>>
>>> Regards,
>>> Anupama
>>>
>>> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne <
>>> shash...@wso2.com> wrote:
>>>
 Hi,

 I tested the kernal with following databases and no issues observed.

 Test Area:
 Add/ Delete resource (inline text) and collection
 Add/Remove user and role

 Databases:
 mysql 5.5.
 mysql 5.7
 postgres 9.3
 oracle 12c

 Regards,
 Shashika

 Shashika Ubhayaratne
 Associate Technical Lead - QA
 WSO2 Inc: http://www.wso2.com/
 Mobile: *+94773383831*

 On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna 
 wrote:

> Hi all,
>
> I've tested the kernel with following databases and found no
> issues.
> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>
> [x] Stable - go ahead and release.
>
> Regards,
> Aruna
> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake <
> jaya...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=13113
>>
>> Please download and test your products with kernel 4.4.7 RC1 and
>> vote. Vote will be open for 72 hours or as longer as needed.
>>
>> Source and binary distribution files:
>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>>
>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>>
>> Maven staging repository
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>>
>> The tag to be voted upon :
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you
>> Carbon Team​
>>
>>
>> *Jayanga Dissanayake*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.com/
>> lean . enterprise . middleware
>> email: jaya...@wso2.com
>> mobile: +94772207259
>>
>> 

[Dev] Getting Error while installing iOS features to EMM 2.1.0

[Chathura Dilan]

Hi All,

I'm getting the following error while installing iOS features to EMM 2.1.0.
Anyone know what's the reason for the issue?


Error creating bean with name 'enrollmentServiceBean' defined in URL
[jndi:/localhost/ios-enrollment/WEB-INF/cxf-servlet.xml]: Instantiation of
bean failed; nested exception is java.lang.NoClassDefFoundError:
org/wso2/carbon/device/mgt/ios/core/exception/IOSEnrollmentException
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1327)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at
org.apache.cxf.transport.servlet.CXFServlet.createSpringContext(CXFServlet.java:151)
at org.apache.cxf.transport.servlet.CXFServlet.loadBus(CXFServlet.java:74)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:76)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5262)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5550)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at
org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:290)
at
org.wso2.carbon.tomcat.internal.CarbonTomcat.addWebApp(CarbonTomcat.java:198)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWebappDeployment(TomcatGenericWebappsDeployer.java:258)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleWarWebappDeployment(TomcatGenericWebappsDeployer.java:208)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleHotDeployment(TomcatGenericWebappsDeployer.java:175)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.deploy(TomcatGenericWebappsDeployer.java:140)
at
org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deployThisWebApp(AbstractWebappDeployer.java:224)
at
org.wso2.carbon.webapp.mgt.AbstractWebappDeployer.deploy(AbstractWebappDeployer.java:114)
at
org.wso2.carbon.webapp.deployer.WebappDeployer.deploy(WebappDeployer.java:42)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
at

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

[Rajith Roshan]

Hi all,

Tested G-Reg 5.3.0 Snapshot with kernel 4.4.7 and ran integration test
without any issues.

[x] Stable - go ahead and release


Thanks!
Rajith

On Tue, Jul 5, 2016 at 1:19 PM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi,
>
> Tested with ESB 5.0.0-SNAPSHOT and executed integrated tests. No issues
> observed.
>
> [x] Stable - go ahead and release.
>
> Thanks.
>
> On Mon, Jul 4, 2016 at 10:56 PM, Hasitha Aravinda 
> wrote:
>
>> Tested with BPS 3.6.0-SNAPSHOT. No issue found.
>>
>> [x] Stable - go ahead and release.
>>
>> Thanks,
>> Hasitha.
>>
>> On Mon, Jul 4, 2016 at 6:42 PM, Kasun Bandara  wrote:
>>
>>> Hi all,
>>>
>>> I could successfully run IS test suit with the upgraded Kernel 4.4.7-
>>> RC1. Hence +1 for the release.
>>>
>>> Thanks,
>>> Kasun
>>>
>>> On Mon, Jul 4, 2016 at 5:35 PM, Chamalee De Silva 
>>> wrote:
>>>
 P.S. Test done base done API Manager 2.0.0 beta-2

 On Mon, Jul 4, 2016 at 5:33 PM, Chamalee De Silva 
 wrote:

> Hi,
> I tested the kernel 4.4.7 RC1 with
>
> MySQL 5.6 and  5.7,
> Oracle 11g,
> PostgreSQL 9.3
>
> and they worked without an issue.
>
> [x] Stable - go ahead and release.
>
>
>
> Thanks,
> Chamalee
>
> On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage 
> wrote:
>
>> Hi,
>>
>> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
>> issue related to this RC.
>>
>> *Note :* Feature repo not shown issue [1], introduced with kernel
>> 4.4.6 is observed. Hope this will be fixed in a future release.
>>
>> [1] https://wso2.org/jira/browse/CARBON-15973
>>
>> Regards,
>> Anupama
>>
>> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne <
>> shash...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I tested the kernal with following databases and no issues observed.
>>>
>>> Test Area:
>>> Add/ Delete resource (inline text) and collection
>>> Add/Remove user and role
>>>
>>> Databases:
>>> mysql 5.5.
>>> mysql 5.7
>>> postgres 9.3
>>> oracle 12c
>>>
>>> Regards,
>>> Shashika
>>>
>>> Shashika Ubhayaratne
>>> Associate Technical Lead - QA
>>> WSO2 Inc: http://www.wso2.com/
>>> Mobile: *+94773383831*
>>>
>>> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna 
>>> wrote:
>>>
 Hi all,

 I've tested the kernel with following databases and found no issues.
 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1

 [x] Stable - go ahead and release.

 Regards,
 Aruna
 On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake <
 jaya...@wso2.com> wrote:

> Hi Devs,
>
> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=13113
>
> Please download and test your products with kernel 4.4.7 RC1 and
> vote. Vote will be open for 72 hours or as longer as needed.
>
> Source and binary distribution files:
> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>
> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>
> Maven staging repository
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>
> The tag to be voted upon :
> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you
> Carbon Team​
>
>
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 *Aruna Sujith Karunarathna *
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 9040362 | Work: +94 112145345
 Email: ar...@wso2.com | Web: www.wso2.com


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


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> 

[Dev] [C5] Upgrading Kernel Equinox version to Neon Releases

[Chanaka Cooray]

Hi all,

We have decided to upgrade the equinox version in kernel to Neon release
which is the latest release of the equinox[1]. This has to be done due to
several issues in kernel including [2] with the current equinox version.
Addition to that, it is also required to upgrade tycho versions in
carbon-maven-plugins [3] because of a jarsigner issue with the JDK 7, 8.

[1] http://download.eclipse.org/equinox/
[2] https://wso2.org/jira/browse/CARBON-15976
[3] https://github.com/wso2/carbon-maven-plugins

Thanks,
Chanaka.
-- 
Chanaka Cooray
Software Engineer, WSO2 Inc. http://wso2.com
Email: chana...@wso2.com
Mobile: +94713149860
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Inclusion of available APIs under Deleted APIs list in API Deployment Stats in Log Analyzer

[Maneesha Wijesekara]

Hi Sajith,

Agreed with how the log analyzer works when an API is updated. But when
considering the user point of view, an API shouldn't be listed in 'Deleted
APIs' list if it's still available. Because a user might get confused when
the statistics in 'Deleted APIs' shows some API that he/she used right now.

Any suggestion to overcome this ? Probably a change in logs when editing an
API might be a solution for this.

Regards
Maneesha

On Tue, Jul 5, 2016 at 1:11 PM, Sajith Perera  wrote:

>
> Hi Maneesha,
>
> Log analyzer purely based on the log events which are generated by a
> particular product. For each stat, there are set of keywords and rules in
> log lines, which we are identifying as unique for that scenario.
>
> Regarding the above mentioned scenario, if there is an update on an API in
> given time frame, there will be two log lines printed with "Destroying" and
> "Initiating" keywords.
>
> 1. Deleted Artifact X
> 2. Created Artifact X
>
> These events are listed as "Deployed Api X" and "Deleted Api X" tables in
> the given time frame, as they are the "facts" within the given time frame.
>
> Thanks,
> SajithD
>
> On Tue, Jul 5, 2016 at 12:44 PM, Maneesha Wijesekara 
> wrote:
>
>> Hi all,
>>
>> Currently 'API Deployment Stats' in Log Analyzer listed both Deployed
>> APIs and Deleted APIs. But I've noticed that some available APIs (not yet
>> deleted) are also listed under 'Deleted APIs' [1]. The reason behind this
>> is when an API is edited, it will destroyed and again re-deployed. That log
>> will cause to include an available API under 'Deleted APIs'. But when it
>> comes to the function 'Deleted APIs', it should only list the names of APIs
>> which are actually deleted.
>>
>> Any thoughts on this ?
>>
>> [1] https://wso2.org/jira/browse/ANLYAPIM-79
>>
>> --
>> Maneesha Wijesekara
>> Software Engineer - QA Team
>> WSO2 Inc.
>>
>> Email: manee...@wso2.com
>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>> Mobile: +94712443119
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sajith Dimal
> Software Engineer
> Mobile : +94783101496
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



-- 
Maneesha Wijesekara
Software Engineer - QA Team
WSO2 Inc.

Email: manee...@wso2.com
Linkedin: http://linkedin.com/in/maneeshawijesekara
Mobile: +94712443119
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Inclusion of available APIs under Deleted APIs list in API Deployment Stats in Log Analyzer

[Miyuru Dayarathna]

Adding Isabelle and Srinath to the email thread.

-- 
Thanks,
Miyuru Dayarathna
Senior Technical Lead
Mobile: +94713527783
Blog: http://miyurublog.blogspot.com

On Tue, Jul 5, 2016 at 1:11 PM, Sajith Perera  wrote:

>
> Hi Maneesha,
>
> Log analyzer purely based on the log events which are generated by a
> particular product. For each stat, there are set of keywords and rules in
> log lines, which we are identifying as unique for that scenario.
>
> Regarding the above mentioned scenario, if there is an update on an API in
> given time frame, there will be two log lines printed with "Destroying" and
> "Initiating" keywords.
>
> 1. Deleted Artifact X
> 2. Created Artifact X
>
> These events are listed as "Deployed Api X" and "Deleted Api X" tables in
> the given time frame, as they are the "facts" within the given time frame.
>
> Thanks,
> SajithD
>
> On Tue, Jul 5, 2016 at 12:44 PM, Maneesha Wijesekara 
> wrote:
>
>> Hi all,
>>
>> Currently 'API Deployment Stats' in Log Analyzer listed both Deployed
>> APIs and Deleted APIs. But I've noticed that some available APIs (not yet
>> deleted) are also listed under 'Deleted APIs' [1]. The reason behind this
>> is when an API is edited, it will destroyed and again re-deployed. That log
>> will cause to include an available API under 'Deleted APIs'. But when it
>> comes to the function 'Deleted APIs', it should only list the names of APIs
>> which are actually deleted.
>>
>> Any thoughts on this ?
>>
>> [1] https://wso2.org/jira/browse/ANLYAPIM-79
>>
>> --
>> Maneesha Wijesekara
>> Software Engineer - QA Team
>> WSO2 Inc.
>>
>> Email: manee...@wso2.com
>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>> Mobile: +94712443119
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sajith Dimal
> Software Engineer
> Mobile : +94783101496
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



-- 
Thanks,
Miyuru Dayarathna
Senior Technical Lead
Mobile: +94713527783
Blog: http://miyurublog.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Jagath Sisirakumara Ariyarathne]

Hi,

Tested with ESB 5.0.0-SNAPSHOT and executed integrated tests. No issues
observed.

[x] Stable - go ahead and release.

Thanks.

On Mon, Jul 4, 2016 at 10:56 PM, Hasitha Aravinda  wrote:

> Tested with BPS 3.6.0-SNAPSHOT. No issue found.
>
> [x] Stable - go ahead and release.
>
> Thanks,
> Hasitha.
>
> On Mon, Jul 4, 2016 at 6:42 PM, Kasun Bandara  wrote:
>
>> Hi all,
>>
>> I could successfully run IS test suit with the upgraded Kernel 4.4.7-
>> RC1. Hence +1 for the release.
>>
>> Thanks,
>> Kasun
>>
>> On Mon, Jul 4, 2016 at 5:35 PM, Chamalee De Silva 
>> wrote:
>>
>>> P.S. Test done base done API Manager 2.0.0 beta-2
>>>
>>> On Mon, Jul 4, 2016 at 5:33 PM, Chamalee De Silva 
>>> wrote:
>>>
 Hi,
 I tested the kernel 4.4.7 RC1 with

 MySQL 5.6 and  5.7,
 Oracle 11g,
 PostgreSQL 9.3

 and they worked without an issue.

 [x] Stable - go ahead and release.



 Thanks,
 Chamalee

 On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage 
 wrote:

> Hi,
>
> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
> issue related to this RC.
>
> *Note :* Feature repo not shown issue [1], introduced with kernel
> 4.4.6 is observed. Hope this will be fixed in a future release.
>
> [1] https://wso2.org/jira/browse/CARBON-15973
>
> Regards,
> Anupama
>
> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne <
> shash...@wso2.com> wrote:
>
>> Hi,
>>
>> I tested the kernal with following databases and no issues observed.
>>
>> Test Area:
>> Add/ Delete resource (inline text) and collection
>> Add/Remove user and role
>>
>> Databases:
>> mysql 5.5.
>> mysql 5.7
>> postgres 9.3
>> oracle 12c
>>
>> Regards,
>> Shashika
>>
>> Shashika Ubhayaratne
>> Associate Technical Lead - QA
>> WSO2 Inc: http://www.wso2.com/
>> Mobile: *+94773383831*
>>
>> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Hi all,
>>>
>>> I've tested the kernel with following databases and found no issues.
>>> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
>>> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>>>
>>> [x] Stable - go ahead and release.
>>>
>>> Regards,
>>> Aruna
>>> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake <
>>> jaya...@wso2.com> wrote:
>>>
 Hi Devs,

 This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.

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

 Please download and test your products with kernel 4.4.7 RC1 and
 vote. Vote will be open for 72 hours or as longer as needed.

 Source and binary distribution files:
 https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip

 http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip

 Maven staging repository
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025

 The tag to be voted upon :
 https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1

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

 Thank you
 Carbon Team​


 *Jayanga Dissanayake*
 Associate Technical Lead
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

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


>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Anupama Pathirage
> Associate Technical Lead
> WSO2, Inc.  http://wso2.com/
> Email: anup...@wso2.com
> Mobile:+94 71 8273 979
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 

Re: [Dev] [APIM] Inclusion of available APIs under Deleted APIs list in API Deployment Stats in Log Analyzer

[Sajith Perera]

Hi Maneesha,

Log analyzer purely based on the log events which are generated by a
particular product. For each stat, there are set of keywords and rules in
log lines, which we are identifying as unique for that scenario.

Regarding the above mentioned scenario, if there is an update on an API in
given time frame, there will be two log lines printed with "Destroying" and
"Initiating" keywords.

1. Deleted Artifact X
2. Created Artifact X

These events are listed as "Deployed Api X" and "Deleted Api X" tables in
the given time frame, as they are the "facts" within the given time frame.

Thanks,
SajithD

On Tue, Jul 5, 2016 at 12:44 PM, Maneesha Wijesekara 
wrote:

> Hi all,
>
> Currently 'API Deployment Stats' in Log Analyzer listed both Deployed APIs
> and Deleted APIs. But I've noticed that some available APIs (not yet
> deleted) are also listed under 'Deleted APIs' [1]. The reason behind this
> is when an API is edited, it will destroyed and again re-deployed. That log
> will cause to include an available API under 'Deleted APIs'. But when it
> comes to the function 'Deleted APIs', it should only list the names of APIs
> which are actually deleted.
>
> Any thoughts on this ?
>
> [1] https://wso2.org/jira/browse/ANLYAPIM-79
>
> --
> Maneesha Wijesekara
> Software Engineer - QA Team
> WSO2 Inc.
>
> Email: manee...@wso2.com
> Linkedin: http://linkedin.com/in/maneeshawijesekara
> Mobile: +94712443119
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] [APIM] Inclusion of available APIs under Deleted APIs list in API Deployment Stats in Log Analyzer

[Maneesha Wijesekara]

Hi all,

Currently 'API Deployment Stats' in Log Analyzer listed both Deployed APIs
and Deleted APIs. But I've noticed that some available APIs (not yet
deleted) are also listed under 'Deleted APIs' [1]. The reason behind this
is when an API is edited, it will destroyed and again re-deployed. That log
will cause to include an available API under 'Deleted APIs'. But when it
comes to the function 'Deleted APIs', it should only list the names of APIs
which are actually deleted.

Any thoughts on this ?

[1] https://wso2.org/jira/browse/ANLYAPIM-79

-- 
Maneesha Wijesekara
Software Engineer - QA Team
WSO2 Inc.

Email: manee...@wso2.com
Linkedin: http://linkedin.com/in/maneeshawijesekara
Mobile: +94712443119
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ES]Error when Importing Users in Bulk through management console

[Kasun Thennakoon]

Hi all,

I tried to create multiple user accounts in Entreprise store at once,
rather than creating users one by one. I have tried to use *Bulk Import
Users *option available in the management console.But I couldn't find the
correct format of the file which I need to upload there.I search through
the documentations and found these articles(Importing Users in Bulk [1
] and Bulk
Import of Users [2
] ).There
is a slight different in the documentation and what I'm having(Please see
the attachment) in the management console , that there is no field to set a
default password for the users.despite the issue, I just upload a CSV, with
one column containing a list of usernames.But then got the following error:

[2016-07-05 10:44:25,316] ERROR
> {org.wso2.carbon.user.mgt.ui.UserAdminClient} -  Error occurs while
> importing user names. All user names were not imported. Last error was :
> Ask Password Feature is disabled
> org.apache.axis2.AxisFault: Error occurs while importing user names. All
> user names were not imported. Last error was : Ask Password Feature is
> disabled
> at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
> at
> org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnlyOperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.user.mgt.stub.UserAdminStub.bulkImportUsers(UserAdminStub.java:6887)
> at
> org.wso2.carbon.user.mgt.ui.UserAdminClient.bulkImportUsers(UserAdminClient.java:236)
> at
> org.apache.jsp.user.bulk_002dimport_002dfinish_jsp._jspService(bulk_002dimport_002dfinish_jsp.java:138)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543)
> at
> org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
> at
> org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
> at
> org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:954)
> at
> org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:688)
> at
> org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:682)
> at sun.reflect.GeneratedMethodAccessor246.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
> at
> org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
> at
> org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
> at
> org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
> at
> org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
> at
> org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
> at
> 

Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)

[Pushpalanka Jayawardhana]

Hi Manujith,

Please find the comments in line.

On Mon, Jul 4, 2016 at 8:11 PM, Manujith Pallewatte 
wrote:

> Hi all,
>
> So to start working on the points discussed in the mid evaluation, first
> is to align the service with the REST profile of XACML 3.0 [1]
> But according to the spec only the following 2 resources are defined
>
> 1) home - entry point for REST service, returns links to other resources
> 2) pdp - resource that given a XACML request presents the XACML response
>
> but since the existing SOAP entitlement service exposes additional
> services such as
> getBooleanDecision, getDecisionByAttributes etc. there arises 2 issues
>
> 1) how to name those additional resources?
>
Let's have some convincing names for you as of now. We can refine them
later in review. Try to have inputs from the topic "5.1 PROPER NAMING" from
the rest api guideline while paper we pointed before.

> 2) how to let the clients accessing the service know of the required
> structure of each of these requests that are not defined in the XACML spec?
>
Please have a look at the possibility of using swagger for this. This is
already used in WSO2 Api Manager[1], but not yet in WSO2 IS. Would be great
if you can evaluate the possibility of using it.  Basic idea is to
represent the REST API according to Swagger specification similar to WSDL
we have for SOAP.

[1] - https://docs.wso2.com/display/AM1100/Edit+an+API+Using+the+Swagger+UI

>
> Please provide your suggestions on this
>
> Thank You
> Best Regards,
> Manujith
>
> [1]
> http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html
>
> On Thu, Jun 23, 2016 at 3:42 PM, Omindu Rathnaweera 
> wrote:
>
>> Good Work Manujith!
>>
>> Adding to this. Figure out a way to drop null values from the JSON
>> response with Jackson level configurations. Also have a look at XACML JSON
>> profile [1]. It will have guidelines on dealing with JSON inputs/outputs.
>>
>> [1] -
>> http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html
>>
>> Regards,
>> Omindu.
>>
>> On Thu, Jun 23, 2016 at 3:31 PM, Manujith Pallewatte <
>> manujith...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> We had the mid-evaluation review, and I've summarized the key points
>>> discussed here
>>>
>>> 1) Prioritize on the complete JSON implementation for all 5 services
>>> methods
>>> 2) Comply the service fully with XACML 3.0 REST specification (Read on
>>> the spec and get a firm understanding on all key concepts)
>>> 3) Leave the hard coded authenticators as it is for now
>>> 4) Using custom client / server exception to be returned in a case of an
>>> exception
>>> 5) Follow the code quality guidelines (specially in the cases of
>>> improper exception handling)
>>>
>>> Special thanks to everyone for their time in reviewing.
>>>
>>> Thank You,
>>> Manujith
>>>
>>> On Sun, Jun 12, 2016 at 10:43 PM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi all,

 After refactoring and reviewing code using above suggestions, I added a
 PR, which can be found at [1]

 Regards,
 Manujith

 [1] https://github.com/wso2/carbon-identity-framework/pull/282

 On Sat, Jun 11, 2016 at 12:52 PM, Manujith Pallewatte <
 manujith...@gmail.com> wrote:

> Hi Manuranga,
>
> I did referred to the guidelines, but was not successful in figuring
> out suitable end point names. So Pushpalanka suggested to take community's
> ideas in naming them. Any pointers as for which I can improve the names?
> According to the guide it says to identify the resources first
> Going on that, I identified the Policy Decision, Entitlement
> Attributes and Entitlements as resources, but since some resources have
> only one methods call in it, having a separate path seem redundant. And
> didnt follow much from there, please let me know your ideas on the 
> resource
> identification
>
> Thank You
> Regards,
> Manujith
>
> On Sat, Jun 11, 2016 at 12:21 AM, Manuranga Perera 
> wrote:
>
>> Hi Manujith,
>>
>> Please have a look at WSO2 REST API guideline [1]. This will help you
>> to improve the URL nameing.
>>
>> [1] http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/
>>
>> On Thu, Jun 9, 2016 at 3:49 PM, Manujith Pallewatte <
>> manujith...@gmail.com> wrote:
>>
>>> Hi Pushpalanka,
>>>
>>> Was confused in the PR procedure, and figured that I forgot to
>>> initialize the github repo as you have mentioned in a previous message.
>>> So the new location of the codebase is at [1]
>>> Over the weekend, I'll fix any remaining issues and send the PR
>>> For now I have used the wso2-codestyle given by Omindu and
>>> reformatted the code
>>> and added Findbug as well.
>>>
>>> Thank You
>>> Manujith
>>>
>>> [1]
>>> 

Re: [Dev] Regarding APPM-1160

[Chathura Dilan]

Hi Dinusha,

EMM supports multi-tenancy it is designed to work with one instance of App
Manager via OSGI services. When they work together they function as one
product, hence EMM and App Manager share same tenants across the multi
tenanted environment.

This is a special scenario where AppM connects to EMM via  EMM REST
APIs. According to how we have developed the plugin tenant admin and
password needs to be stored in the plugin configuration. This is a
plugin specific configuration, therefore, the plugin developer has
flexibility to store those configurations in any way he prefers.

When it's comes to multi tenancy, +1 we have to store those
configurations in the registry for the rest connector plugin . But how we
store those values are plugin specific.


On Tue, Jul 5, 2016 at 10:51 AM, Dinusha Senanayaka 
wrote:

> Hi Chathura,
>
> Does multi-tenancy supports in EMM for device management ? If yes, we need
> to fix [1] as well, which means we cannot keep this configuration in the
> app-manager.xml. Need to take it to registry.
>
> [1] https://wso2.org/jira/browse/APPM-1160
>
> Regards,
> Dinsuha.
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Regards,

Chatura Dilan Perera
*Associate Tech Lead** - WSO2 Inc.*
www.dilan.me
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon-Registry 4.5.5 is Staged

[Anupama Pathirage]

Hi,

I have tested Carbon registry 4.5.5 with WSO2 DSS 3.5.1-SNAPSHOT and didn't
find any issue.

Regards,
Anupama

On Sat, Jul 2, 2016 at 8:45 AM, Rajith Roshan  wrote:

> Hi all,
>
> Carbon registry 4.5.5 is staged at
> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonregistry-1005/
>
> This release is with kernel version 4.4.6. Please test and verify staging
> repo with products.
>
> *Note : *In order to access the remote registry please exclude the sub
> context URL [1] in the "Owasp.CsrfGuard.Carbon.properties" file in
> $SERVER_HOME/repository/conf/security directory.
>
> [1] - org.owasp.csrfguard.unprotected.Registry=%servletContext%/registry/*
>
> Thanks!
> Rajith
>
> --
> Rajith Roshan
> Software Engineer, WSO2 Inc.
> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>



-- 
Anupama Pathirage
Associate Technical Lead
WSO2, Inc.  http://wso2.com/
Email: anup...@wso2.com
Mobile:+94 71 8273 979
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Akila,

Please check the modified code. It now takes the value which is specified
as localMemberPort in axis2.xml.

Thanks,

On Tuesday, July 5, 2016, Akila Ravihansa Perera  wrote:

> Hi Osura,
>
> As Isuru mentioned you need to be clear about tenantId since it might
> conflict with Carbon tenantId. As suggested, please rename it to something
> like AZURE_TENANT_ID or something like that.
>
> Regarding localMemberPort in axis2.xml, the value of this parameter should
> be same in all nodes by convention therefore no need read localMemberPort
> parameter value in each member's axis2.xml. When adding members to
> Hazelcast config context you need to take the value of this parameter.
> Because we cannot guarantee that it will be 4000 in every deployment. There
> are some special cases in which we need to change this. Have a look at [1]
> to see how this is handled in Mesos membership scheme.
>
> [1]
> https://github.com/wso2/mesos-artifacts/blob/master/common/mesos-membership-scheme/src/main/java/org/wso2/carbon/clustering/mesos/MesosMembershipScheme.java#L247
>
> Thanks.
>


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

Re: [Dev] [GSOC 16] Initial Project Progress

[Akila Ravihansa Perera]

Hi Osura,

As Isuru mentioned you need to be clear about tenantId since it might
conflict with Carbon tenantId. As suggested, please rename it to something
like AZURE_TENANT_ID or something like that.

Regarding localMemberPort in axis2.xml, the value of this parameter should
be same in all nodes by convention therefore no need read localMemberPort
parameter value in each member's axis2.xml. When adding members to
Hazelcast config context you need to take the value of this parameter.
Because we cannot guarantee that it will be 4000 in every deployment. There
are some special cases in which we need to change this. Have a look at [1]
to see how this is handled in Mesos membership scheme.

[1]
https://github.com/wso2/mesos-artifacts/blob/master/common/mesos-membership-scheme/src/main/java/org/wso2/carbon/clustering/mesos/MesosMembershipScheme.java#L247

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