Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

[Ajith Vitharana]

Other issue is,

1. According to the sample I'm shutting down the backend-1  and send a
request.
2. Now I can see the message store has one message.
3. Before 50 delivery attempts , start the backend-1
4. Now I  can see the message processor executed and message delivered  to
backed-1

But just after sending the message, the  message processor going to
deactivate state and printing following exception.

[2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
message through the fault sequence. Sequence name does not Exist.
*[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
message through the deactivate sequence. Sequence name does not Exist.*
[2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
deactivated the message processor [send_pending_message]
*[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the out
message. Reply sequence does not Exist. Deactivated the message processor*


1. According to the WARN log , what is the deactivate sequence should
define ?
2. Why message processor is deactivate just after sending message to back
end ?

-Ajith


On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana  wrote:

> Hi Yasassri.
>
> Yes. According to the carbon commits it has renamed. Then those configs
> never tested after 2012 :)
>
> [1] https://wso2.org/jira/browse/CARBON-13114
>
> -Ajith
>
>
> Author: ishan
> Date: Fri Jun 15 02:00:53 2012
> New Revision: 130164
> URL: http://wso2.org/svn/browse/wso2?view=rev=130164
>
> Log:
> Fixing CARBON-13114 with the patch of CharithaM.
>
> Modified:
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jsp
>carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>
> Modified: carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164=130163=130164=diff
> 
> ==
> --- carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
> (original)
> +++ carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
> Fri Jun 15 02:00:53 2012
> @@ -24,7 +24,9 @@
>  size=Size
>  action=Actions
>  deactivate=Deactivate
> -activate=activate
> +activate=Activate
> +inactive=Inactive
> +active=Active
>  no.messageProcessors.are.currently.defined=No Message Processors are
> currently defined.
>  message.Processor= Message Processor
>  name=Name
> @@ -104,7 +106,7 @@
>  message.sampling.processor.parameters=Message Sampling Processor
> Parameters
>  message.context.properties=Message Context Properties
>  interval=Message retry interval (Millis)
>
>
> *-max.deliver.attempts=Maximum delivery 
> attempts+max.delivery.attempts=Maximum delivery attempts*
>  axis2.repo=Axis2 Client repository
>  axis2.config=Axis2 Configuration
>  message.processor.reply.sequence=Reply sequence name
> @@ -112,4 +114,4 @@
>  quartz.conf=Quartz configuration file path
>  cronExpression=Cron Expression
>  target.endpoint=Address Endpoint name
> -out_only=Out-only message
> \ No newline at end of file
> +out_only=Out-only message
>
> Modified: carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jsp
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/web/message_processor/index.jsp?rev=130164=130163=130164=diff
> 
> ==
> --- carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jsp(original)
> +++ carbon/platform/trunk/components/mediation/message-
> processor/org.wso2.carbon.message.processor.ui/src/main/
> resources/web/message_processor/index.jspFri Jun 15 02:00:53 2012
> @@ -290,11 +290,14 @@
> id="delete_link" class="icon-link"

Re: [Dev] Is "defaultValue" field in the Publish Event Mediator always expected to be Empty?

[Awanthika Senarath]

In that case we have a bug in developer studio! :) as we have not
introduced a filed for defaultValue in our graphical view, hence on adding
a value for defaultValue in the source view in switching to graphical view
will remove the saved value.

I will create the relevant JIRA after discussing with the team.

Regards
Awanthika


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



On Wed, Oct 7, 2015 at 9:57 AM, Nuwan Pallewela  wrote:

> Hi Awanthika,
>
> I think this defaultValue can be any value. It is assigned for the
> attribute if the expression can not find a property value.
>
> Thanks,
> Nuwan
>
> On Wed, Oct 7, 2015 at 9:29 AM, Awanthika Senarath 
> wrote:
>
>> Hi all,
>>
>> On testing the developer studio 3.8.0 I could observe that the
>> "defaultValue" field for attribute parameters in the Publish Event Mediator
>> [1] is always empty and will not store any values.
>>
>> On referring the documentation [2] for ESB 4.9.0 in the sample displayed
>> also I could observe the same. Could you please explain the purpose of
>> having this field in the said mediator and whether this is the correct
>> use-case to be implemented from Developer Studio end?
>>
>>
>> [1]  
>>   
>> >   expression="get-property('axis2', 'HTTP_METHOD')"
>>   name="http_method" type="STRING"/>
>> >   name="destination" type="STRING"/>
>>   
>>   
>> >   expression="get-property('SYSTEM_DATE')" name="date"
>> type="STRING"/>
>>   
>>   
>> >   expression="$body/m0:getQuote/m0:request/m0:symbol"
>>   name="symbol" type="STRING" xmlns:m0="
>> http://services.samples"/>
>>   
>>   
>> 
>>
>> [2] https://docs.wso2.com/display/ESB490/Publish+Event+Mediator
>>
>> Regards
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>*
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

[Yasassri Ratnayake]

According to [1]  "*The deactivate sequence that will be executed when the
processor is deactivated automatically. Automatic deactivation occurs when
the maximum delivery attempts is exceeded and the Drop message after
maximum delivery attempts parameter is disabled.*"

[1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor

On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana  wrote:

> Other issue is,
>
> 1. According to the sample I'm shutting down the backend-1  and send a
> request.
> 2. Now I can see the message store has one message.
> 3. Before 50 delivery attempts , start the backend-1
> 4. Now I  can see the message processor executed and message delivered  to
> backed-1
>
> But just after sending the message, the  message processor going to
> deactivate state and printing following exception.
>
> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
> message through the fault sequence. Sequence name does not Exist.
> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
> message through the deactivate sequence. Sequence name does not Exist.*
> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
> deactivated the message processor [send_pending_message]
> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the
> out message. Reply sequence does not Exist. Deactivated the message
> processor*
>
>
> 1. According to the WARN log , what is the deactivate sequence should
> define ?
> 2. Why message processor is deactivate just after sending message to back
> end ?
>
> -Ajith
>
>
> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana  wrote:
>
>> Hi Yasassri.
>>
>> Yes. According to the carbon commits it has renamed. Then those configs
>> never tested after 2012 :)
>>
>> [1] https://wso2.org/jira/browse/CARBON-13114
>>
>> -Ajith
>>
>>
>> Author: ishan
>> Date: Fri Jun 15 02:00:53 2012
>> New Revision: 130164
>> URL: http://wso2.org/svn/browse/wso2?view=rev=130164
>>
>> Log:
>> Fixing CARBON-13114 with the patch of CharithaM.
>>
>> Modified:
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/index.jsp
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>
>> Modified: carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>> URL:
>> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164=130163=130164=diff
>> 
>> ==
>> --- carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>> (original)
>> +++ carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>> Fri Jun 15 02:00:53 2012
>> @@ -24,7 +24,9 @@
>>  size=Size
>>  action=Actions
>>  deactivate=Deactivate
>> -activate=activate
>> +activate=Activate
>> +inactive=Inactive
>> +active=Active
>>  no.messageProcessors.are.currently.defined=No Message Processors are
>> currently defined.
>>  message.Processor= Message Processor
>>  name=Name
>> @@ -104,7 +106,7 @@
>>  message.sampling.processor.parameters=Message Sampling Processor
>> Parameters
>>  message.context.properties=Message Context Properties
>>  interval=Message retry interval (Millis)
>>
>>
>> *-max.deliver.attempts=Maximum delivery 
>> attempts+max.delivery.attempts=Maximum delivery attempts*
>>  axis2.repo=Axis2 Client repository
>>  axis2.config=Axis2 Configuration
>>  message.processor.reply.sequence=Reply sequence name
>> @@ -112,4 +114,4 @@
>>  quartz.conf=Quartz configuration file path
>>  cronExpression=Cron Expression
>>  target.endpoint=Address Endpoint name
>> -out_only=Out-only message
>> \ No newline at end of file
>> +out_only=Out-only message
>>
>> Modified: carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/index.jsp
>> URL:
>> 

Re: [Dev] Sending custom responses in automation test

[Senduran Balasubramaniyam]

Hi Krishantha,

Following are the steps I followed to verify the scenario.

   - Created a mock service to respond with status code 202, empty body
   with content-type text/html
   - Invoked the service from ESB and added a log full after calling the
   endpoint

since there is a content type available ESB will try to build the message
but since the message body is empty it will throw an exception

Thanks
Senduran

On Wed, Oct 7, 2015 at 10:11 AM, Krishantha Samaraweera  wrote:

> Hi Senduran,
>
> Can you list the steps that you have followed to verify the scenario
> manually.
>
> Thanks,
> Krishantha.
>
> On Tue, Oct 6, 2015 at 10:05 AM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Hi Krishantha,
>>
>> I need to write a test for ESB where my proxy service should receive some
>> custom responses.
>> For example
>> Empty body with status code 202 and content type text/html.
>> Could you please guide me to do this
>>
>> Thank you
>> Senduran
>>
>> --
>> *Senduran *
>> Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ 
>> Mobile: +94 77 952 6548
>>
>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>



-- 
*Senduran *
Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Gimantha Bandara]

Please use the request body mentioned in the documentation jira I sent
previously.

On Wed, Oct 7, 2015 at 1:12 AM, Isuru Wijesinghe  wrote:

> Hi Gimantha,
>
> using the aggregate API [1], I passed the below lucene object. But it
> gives me an error (Internal server error). Does the COUNT function disable
> from a configuration file due to performance issues?
>
> {
> "tableName": "PROCESS_USAGE_SUMMARY_DATA",
> "groupByField": "processDefKey",
> "aggregateFields": [
> {
> "fieldName": "processInstanceId",
> "aggregate": "COUNT",
> "alias": "processInstanceCount"
> }
> ]
> }
>
> [1]
> https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API
>
> On Wed, Oct 7, 2015 at 10:06 AM, Nirmal Fernando  wrote:
>
>> Hi Isuru,
>>
>> Just happened to see that you are using "???" :-) You can easily save
>> some time by using "?" :-)
>>
>> On Tue, Oct 6, 2015 at 10:59 PM, Isuru Wijesinghe 
>> wrote:
>>
>>> Hi Anjana,
>>>
>>> I think the link [1] given something similar to *where* clause in sql
>>> (I mean the *query *part is something similar to *where *clause). Here
>>> what I really need to do is, use the count operation with *group by. *
>>> In addition to that does luicene support for ascending and descending order
>>> ???
>>>
>>> On Tue, Oct 6, 2015 at 3:54 PM, Anjana Fernando  wrote:
>>>
 Hi Isuru,

 You can use the REST APIs search count [1] operation.

 [1]
 https://docs.wso2.com/display/DAS300/Retrieving+the+Number+of+Records+Matching+the+Given+Search+Query+via+REST+API

 Cheers,
 Anjana.

 On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe 
 wrote:

> Hi,
>
> I need to perform COUNT() operation through DAS REST API (an example
> is shown below). I tried to pass COUNT() from a luciene object. But it
> didn't work for me. Does DAS support COUNT operation through luciene ???
> if not how can I enable it in DAS side???
>
> eg: *SELECT startedTime, processDefinitionId,
> COUNT(processInstanceId) AS processInstanceCount FROM 
> PROCESS_USAGE_SUMMARY
> GROUP BY startedTime, processDefinitionId;*
>
> In addition to that, is that possible to pass more than one parameter
> to the query part in luicene object, because most graphs have to provide a
> secondary filter to get the result. As an example I need to filter the
> result from date range as well as process id.  I need something like this.
>
>  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
> 10035" *
>
> Any help will be appreciated.
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Anjana Fernando*
 Senior Technical Lead
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

>>>
>>>
>>>
>>> --
>>> Isuru Wijesinghe
>>> *Software Engineer*
>>> Mobile: 0710933706
>>> isur...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>



-- 
Gimantha Bandara
Software Engineer
WSO2. Inc : http://wso2.com
Mobile : +94714961919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

[Yasassri Ratnayake]

And also If you are receiving a reply you need to define a on-reply
sequence.

On Wed, Oct 7, 2015 at 10:13 AM, Yasassri Ratnayake 
wrote:

> According to [1]  "*The deactivate sequence that will be executed when
> the processor is deactivated automatically. Automatic deactivation occurs
> when the maximum delivery attempts is exceeded and the Drop message after
> maximum delivery attempts parameter is disabled.*"
>
> [1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor
>
> On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana  wrote:
>
>> Other issue is,
>>
>> 1. According to the sample I'm shutting down the backend-1  and send a
>> request.
>> 2. Now I can see the message store has one message.
>> 3. Before 50 delivery attempts , start the backend-1
>> 4. Now I  can see the message processor executed and message delivered
>>  to backed-1
>>
>> But just after sending the message, the  message processor going to
>> deactivate state and printing following exception.
>>
>> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
>> message through the fault sequence. Sequence name does not Exist.
>> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
>> message through the deactivate sequence. Sequence name does not Exist.*
>> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
>> deactivated the message processor [send_pending_message]
>> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the
>> out message. Reply sequence does not Exist. Deactivated the message
>> processor*
>>
>>
>> 1. According to the WARN log , what is the deactivate sequence should
>> define ?
>> 2. Why message processor is deactivate just after sending message to back
>> end ?
>>
>> -Ajith
>>
>>
>> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana  wrote:
>>
>>> Hi Yasassri.
>>>
>>> Yes. According to the carbon commits it has renamed. Then those configs
>>> never tested after 2012 :)
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-13114
>>>
>>> -Ajith
>>>
>>>
>>> Author: ishan
>>> Date: Fri Jun 15 02:00:53 2012
>>> New Revision: 130164
>>> URL: http://wso2.org/svn/browse/wso2?view=rev=130164
>>>
>>> Log:
>>> Fixing CARBON-13114 with the patch of CharithaM.
>>>
>>> Modified:
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/web/message_processor/index.jsp
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>>
>>> Modified: carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> URL:
>>> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164=130163=130164=diff
>>> 
>>> ==
>>> --- carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> (original)
>>> +++ carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> Fri Jun 15 02:00:53 2012
>>> @@ -24,7 +24,9 @@
>>>  size=Size
>>>  action=Actions
>>>  deactivate=Deactivate
>>> -activate=activate
>>> +activate=Activate
>>> +inactive=Inactive
>>> +active=Active
>>>  no.messageProcessors.are.currently.defined=No Message Processors are
>>> currently defined.
>>>  message.Processor= Message Processor
>>>  name=Name
>>> @@ -104,7 +106,7 @@
>>>  message.sampling.processor.parameters=Message Sampling Processor
>>> Parameters
>>>  message.context.properties=Message Context Properties
>>>  interval=Message retry interval (Millis)
>>>
>>>
>>> *-max.deliver.attempts=Maximum delivery 
>>> attempts+max.delivery.attempts=Maximum delivery attempts*
>>>  axis2.repo=Axis2 Client repository
>>>  axis2.config=Axis2 Configuration
>>>  message.processor.reply.sequence=Reply sequence name
>>> @@ -112,4 +114,4 @@
>>>  quartz.conf=Quartz configuration file path
>>>  cronExpression=Cron Expression
>>>  target.endpoint=Address Endpoint name
>>> -out_only=Out-only message
>>> \ No newline at end of file
>>> +out_only=Out-only message
>>>
>>> Modified: carbon/platform/trunk/components/mediation/message-
>>> 

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

[Ajith Vitharana]

On Wed, Oct 7, 2015 at 12:43 AM, Yasassri Ratnayake 
wrote:

> According to [1]  "*The deactivate sequence that will be executed when
> the processor is deactivated automatically. Automatic deactivation occurs
> when the maximum delivery attempts is exceeded and the Drop message after
> maximum delivery attempts parameter is disabled.*"
>
> [1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor
>


The backed is available *BEFORE* exceed the max delivery attempts. But
still message processor going to deactivate ?

-Ajith

>
> On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana  wrote:
>
>> Other issue is,
>>
>> 1. According to the sample I'm shutting down the backend-1  and send a
>> request.
>> 2. Now I can see the message store has one message.
>> 3. Before 50 delivery attempts , start the backend-1
>> 4. Now I  can see the message processor executed and message delivered
>>  to backed-1
>>
>> But just after sending the message, the  message processor going to
>> deactivate state and printing following exception.
>>
>> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
>> message through the fault sequence. Sequence name does not Exist.
>> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send the
>> message through the deactivate sequence. Sequence name does not Exist.*
>> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor Successfully
>> deactivated the message processor [send_pending_message]
>> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send the
>> out message. Reply sequence does not Exist. Deactivated the message
>> processor*
>>
>>
>> 1. According to the WARN log , what is the deactivate sequence should
>> define ?
>> 2. Why message processor is deactivate just after sending message to back
>> end ?
>>
>> -Ajith
>>
>>
>> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana  wrote:
>>
>>> Hi Yasassri.
>>>
>>> Yes. According to the carbon commits it has renamed. Then those configs
>>> never tested after 2012 :)
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-13114
>>>
>>> -Ajith
>>>
>>>
>>> Author: ishan
>>> Date: Fri Jun 15 02:00:53 2012
>>> New Revision: 130164
>>> URL: http://wso2.org/svn/browse/wso2?view=rev=130164
>>>
>>> Log:
>>> Fixing CARBON-13114 with the patch of CharithaM.
>>>
>>> Modified:
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/web/message_processor/index.jsp
>>>carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>>
>>> Modified: carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> URL:
>>> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164=130163=130164=diff
>>> 
>>> ==
>>> --- carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> (original)
>>> +++ carbon/platform/trunk/components/mediation/message-
>>> processor/org.wso2.carbon.message.processor.ui/src/main/
>>> resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
>>> Fri Jun 15 02:00:53 2012
>>> @@ -24,7 +24,9 @@
>>>  size=Size
>>>  action=Actions
>>>  deactivate=Deactivate
>>> -activate=activate
>>> +activate=Activate
>>> +inactive=Inactive
>>> +active=Active
>>>  no.messageProcessors.are.currently.defined=No Message Processors are
>>> currently defined.
>>>  message.Processor= Message Processor
>>>  name=Name
>>> @@ -104,7 +106,7 @@
>>>  message.sampling.processor.parameters=Message Sampling Processor
>>> Parameters
>>>  message.context.properties=Message Context Properties
>>>  interval=Message retry interval (Millis)
>>>
>>>
>>> *-max.deliver.attempts=Maximum delivery 
>>> attempts+max.delivery.attempts=Maximum delivery attempts*
>>>  axis2.repo=Axis2 Client repository
>>>  axis2.config=Axis2 Configuration
>>>  message.processor.reply.sequence=Reply sequence name
>>> @@ -112,4 +114,4 @@
>>>  quartz.conf=Quartz configuration file path
>>>  cronExpression=Cron Expression
>>>  target.endpoint=Address Endpoint name
>>> -out_only=Out-only message
>>> \ No newline at end of file
>>> +out_only=Out-only message
>>>
>>> Modified: 

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Isuru Wijesinghe]

Hi Gimantha,

using the aggregate API [1], I passed the below lucene object. But it gives
me an error (Internal server error). Does the COUNT function disable from a
configuration file due to performance issues?

{
"tableName": "PROCESS_USAGE_SUMMARY_DATA",
"groupByField": "processDefKey",
"aggregateFields": [
{
"fieldName": "processInstanceId",
"aggregate": "COUNT",
"alias": "processInstanceCount"
}
]
}

[1]
https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API

On Wed, Oct 7, 2015 at 10:06 AM, Nirmal Fernando  wrote:

> Hi Isuru,
>
> Just happened to see that you are using "???" :-) You can easily save some
> time by using "?" :-)
>
> On Tue, Oct 6, 2015 at 10:59 PM, Isuru Wijesinghe 
> wrote:
>
>> Hi Anjana,
>>
>> I think the link [1] given something similar to *where* clause in sql (I
>> mean the *query *part is something similar to *where *clause). Here what
>> I really need to do is, use the count operation with *group by. * In
>> addition to that does luicene support for ascending and descending order
>> ???
>>
>> On Tue, Oct 6, 2015 at 3:54 PM, Anjana Fernando  wrote:
>>
>>> Hi Isuru,
>>>
>>> You can use the REST APIs search count [1] operation.
>>>
>>> [1]
>>> https://docs.wso2.com/display/DAS300/Retrieving+the+Number+of+Records+Matching+the+Given+Search+Query+via+REST+API
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe 
>>> wrote:
>>>
 Hi,

 I need to perform COUNT() operation through DAS REST API (an example is
 shown below). I tried to pass COUNT() from a luciene object. But it didn't
 work for me. Does DAS support COUNT operation through luciene ???  if not
 how can I enable it in DAS side???

 eg: *SELECT startedTime, processDefinitionId, COUNT(processInstanceId)
 AS processInstanceCount FROM PROCESS_USAGE_SUMMARY GROUP BY startedTime,
 processDefinitionId;*

 In addition to that, is that possible to pass more than one parameter
 to the query part in luicene object, because most graphs have to provide a
 secondary filter to get the result. As an example I need to filter the
 result from date range as well as process id.  I need something like this.

  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
 10035" *

 Any help will be appreciated.

 --
 Isuru Wijesinghe
 *Software Engineer*
 Mobile: 0710933706
 isur...@wso2.com

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


>>>
>>>
>>> --
>>> *Anjana Fernando*
>>> Senior Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> Isuru Wijesinghe
>> *Software Engineer*
>> Mobile: 0710933706
>> isur...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
Isuru Wijesinghe
*Software Engineer*
Mobile: 0710933706
isur...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Sending custom responses in automation test

[Nuwan Wimalasekara]

Hi Senduran,

You can simply create another proxy service or API to send the empty body
response with 202 status code. if not you can create a axis2 service which
return the response as you expected and deploy it on ESB or axis2 server.

Thanks,
Nuwanw

On Wed, Oct 7, 2015 at 10:20 AM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:

> Hi Krishantha,
>
> Following are the steps I followed to verify the scenario.
>
>- Created a mock service to respond with status code 202, empty body
>with content-type text/html
>- Invoked the service from ESB and added a log full after calling the
>endpoint
>
> since there is a content type available ESB will try to build the message
> but since the message body is empty it will throw an exception
>
> Thanks
> Senduran
>
> On Wed, Oct 7, 2015 at 10:11 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi Senduran,
>>
>> Can you list the steps that you have followed to verify the scenario
>> manually.
>>
>> Thanks,
>> Krishantha.
>>
>> On Tue, Oct 6, 2015 at 10:05 AM, Senduran Balasubramaniyam <
>> sendu...@wso2.com> wrote:
>>
>>> Hi Krishantha,
>>>
>>> I need to write a test for ESB where my proxy service should receive
>>> some custom responses.
>>> For example
>>> Empty body with status code 202 and content type text/html.
>>> Could you please guide me to do this
>>>
>>> Thank you
>>> Senduran
>>>
>>> --
>>> *Senduran *
>>> Software Engineer,
>>> WSO2, Inc.;  http://wso2.com/ 
>>> Mobile: +94 77 952 6548
>>>
>>
>>
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>
>
>
> --
> *Senduran *
> Software Engineer,
> WSO2, Inc.;  http://wso2.com/ 
> Mobile: +94 77 952 6548
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge

[Ayesha Dissanayaka]

Hi Sajith,

I am referring to user not logged in sate. In that case if we directly
access
https://10.100.7.19:9443/portal/dashboards/ano-db01/landing?isAnonView=false
URL then we will see the default view.

And when there a logged in user viewing
https://10.100.7.19:9443/portal/dashboards/ano-db01/landing?isAnonView=false
and logout then also default view is shown since the URL has
isAnonView=false

Thanks!
-Ayesha


On Wed, Oct 7, 2015 at 11:02 AM, Sajith Abeywardhana 
wrote:

> If the user removes the isAnonView param from the url, next time browser
> will show url as 
> *https://10.100.7.19:9443/portal/dashboards/ano-db01/landing?isAnonView=null
> .
> *Since null value is a bit ugly I fixed it and committed it to the PR.
>
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>
> On Wed, Oct 7, 2015 at 10:50 AM, Udara Rathnayake  wrote:
>
>> Had a chat with Sajith. Current implementation seems fine..
>>
>> On Wed, Oct 7, 2015 at 10:40 AM, Sajith Abeywardhana 
>> wrote:
>>
>>> Hi Ayesha,
>>>
>>> Small clarification?
>>>
>>>
 I observed that even *anonymous users* can view the logged in view by
 setting query parameter "isAnonView=false" or without setting it at all in
 the browser.

>>>
>>> I think you mean in here when the *logged in user* viewing anonymous
>>> view he can view logged in view by setting query parameter
>>> "isAnonView=false" or without setting it at all in the browser.
>>>
>>> Anonymous user(with out logging) never able to view logged in view. Am I
>>> right?
>>>
>>>
>>> *Sajith Abeywardhana* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka.
>>> Mobile: +94772260485
>>> Email: saji...@wso2.com | Web: www.wso2.com
>>>
>>>
>>>
 Can you check this.

 Further, instead of having this reflected in the URL can we try keep it
 internally?

 Thanks!
 -Ayesha


 On Tue, Oct 6, 2015 at 6:42 PM, Sajith Abeywardhana 
 wrote:

> Both jira's[1][2] which relevant  to anon view committed under one
> PR[3]. Please review and merge.
>
> [1]. https://wso2.org/jira/browse/UES-597
> [2]. https://wso2.org/jira/browse/UES-599
> [3]. https://github.com/wso2/carbon-dashboards/pull/66
>
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>
> On Tue, Oct 6, 2015 at 2:16 PM, Sajith Abeywardhana 
> wrote:
>
>> Fixed the code according to [Dev] [UES][Dashboard Server] Dashboard
>> anonymous view landing page. Please merge the PR.
>>
>> *Sajith Abeywardhana* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka.
>> Mobile: +94772260485
>> Email: saji...@wso2.com | Web: www.wso2.com
>>
>> On Tue, Oct 6, 2015 at 10:59 AM, Sajith Abeywardhana <
>> saji...@wso2.com> wrote:
>>
>>> Please hold this merge. Page link rendering logic should be changed.
>>> We can't check *!user *after the jira -
>>> https://wso2.org/jira/browse/UES-597
>>>
>>> *Sajith Abeywardhana* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka.
>>> Mobile: +94772260485
>>> Email: saji...@wso2.com | Web: www.wso2.com
>>>
>>> On Tue, Oct 6, 2015 at 10:38 AM, Sajith Abeywardhana <
>>> saji...@wso2.com> wrote:
>>>
 Please review and merge
 https://github.com/wso2/carbon-dashboards/pull/66 for
 https://wso2.org/jira/browse/UES-599


 *Sajith Abeywardhana* | Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka.
 Mobile: +94772260485
 Email: saji...@wso2.com | Web: www.wso2.com

>>>
>>>
>>
>


 --
 *Ayesha Dissanayaka*
 Software Engineer,
 WSO2, Inc : http://wso2.com
 
 20, Palmgrove Avenue, Colombo 3
 E-Mail: aye...@wso2.com 

>>>
>>>
>>
>


-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge

[Sajith Abeywardhana]

Hi Ayesha,

Small clarification?


> I observed that even *anonymous users* can view the logged in view by
> setting query parameter "isAnonView=false" or without setting it at all in
> the browser.
>

I think you mean in here when the *logged in user* viewing anonymous view
he can view logged in view by setting query parameter "isAnonView=false" or
without setting it at all in the browser.

Anonymous user(with out logging) never able to view logged in view. Am I
right?


*Sajith Abeywardhana* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka.
Mobile: +94772260485
Email: saji...@wso2.com | Web: www.wso2.com



> Can you check this.
>
> Further, instead of having this reflected in the URL can we try keep it
> internally?
>
> Thanks!
> -Ayesha
>
>
> On Tue, Oct 6, 2015 at 6:42 PM, Sajith Abeywardhana 
> wrote:
>
>> Both jira's[1][2] which relevant  to anon view committed under one PR[3].
>> Please review and merge.
>>
>> [1]. https://wso2.org/jira/browse/UES-597
>> [2]. https://wso2.org/jira/browse/UES-599
>> [3]. https://github.com/wso2/carbon-dashboards/pull/66
>>
>> *Sajith Abeywardhana* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka.
>> Mobile: +94772260485
>> Email: saji...@wso2.com | Web: www.wso2.com
>>
>> On Tue, Oct 6, 2015 at 2:16 PM, Sajith Abeywardhana 
>> wrote:
>>
>>> Fixed the code according to [Dev] [UES][Dashboard Server] Dashboard
>>> anonymous view landing page. Please merge the PR.
>>>
>>> *Sajith Abeywardhana* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka.
>>> Mobile: +94772260485
>>> Email: saji...@wso2.com | Web: www.wso2.com
>>>
>>> On Tue, Oct 6, 2015 at 10:59 AM, Sajith Abeywardhana 
>>> wrote:
>>>
 Please hold this merge. Page link rendering logic should be changed. We
 can't check *!user *after the jira -
 https://wso2.org/jira/browse/UES-597

 *Sajith Abeywardhana* | Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka.
 Mobile: +94772260485
 Email: saji...@wso2.com | Web: www.wso2.com

 On Tue, Oct 6, 2015 at 10:38 AM, Sajith Abeywardhana 
 wrote:

> Please review and merge
> https://github.com/wso2/carbon-dashboards/pull/66 for
> https://wso2.org/jira/browse/UES-599
>
>
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>


>>>
>>
>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] STS functionality broken due to opensaml upgrade

[Hasintha Indrajee]

STS functionality has been broken due to the upgrade of the opensaml
version (from 2.4.1 to 2.6.4) in carbon-identity. Error [1], can be
observed while invoking sts service with UT policy engaged. Further the
issue seems to be a failure to find class org.opensaml,XML from one of the
classes which resides in opensaml itself (org.opensaml.SAMLNameIdentifier).

[1] http://schemas.xmlsoap.org/soap/envelope/;>http://www.w3.org/2005/08/addressing;>http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
soapenv:mustUnderstand="1">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
wsu:Id="Timestamp-136">2015-10-06T11:47:27.145Z2015-10-06T11:52:27.145Z
http://www.w3.org/2005/08/addressing/soap/faultuuid:29736852-243e-40cb-9860-68d2db234e6fsoapenv:Serverjava.lang.NoClassDefFoundError:
Could not initialize class
org.opensaml.XML
-- 
Hasintha Indrajee
Software Engineer
WSO2, Inc.
Mobile:+94 771892453
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Sending custom responses in automation test

[Krishantha Samaraweera]

Hi Senduran,

Can you list the steps that you have followed to verify the scenario
manually.

Thanks,
Krishantha.

On Tue, Oct 6, 2015 at 10:05 AM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:

> Hi Krishantha,
>
> I need to write a test for ESB where my proxy service should receive some
> custom responses.
> For example
> Empty body with status code 202 and content type text/html.
> Could you please guide me to do this
>
> Thank you
> Senduran
>
> --
> *Senduran *
> Software Engineer,
> WSO2, Inc.;  http://wso2.com/ 
> Mobile: +94 77 952 6548
>



-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge

[Udara Rathnayake]

Had a chat with Sajith. Current implementation seems fine..

On Wed, Oct 7, 2015 at 10:40 AM, Sajith Abeywardhana 
wrote:

> Hi Ayesha,
>
> Small clarification?
>
>
>> I observed that even *anonymous users* can view the logged in view by
>> setting query parameter "isAnonView=false" or without setting it at all in
>> the browser.
>>
>
> I think you mean in here when the *logged in user* viewing anonymous view
> he can view logged in view by setting query parameter "isAnonView=false" or
> without setting it at all in the browser.
>
> Anonymous user(with out logging) never able to view logged in view. Am I
> right?
>
>
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>
>
>
>> Can you check this.
>>
>> Further, instead of having this reflected in the URL can we try keep it
>> internally?
>>
>> Thanks!
>> -Ayesha
>>
>>
>> On Tue, Oct 6, 2015 at 6:42 PM, Sajith Abeywardhana 
>> wrote:
>>
>>> Both jira's[1][2] which relevant  to anon view committed under one
>>> PR[3]. Please review and merge.
>>>
>>> [1]. https://wso2.org/jira/browse/UES-597
>>> [2]. https://wso2.org/jira/browse/UES-599
>>> [3]. https://github.com/wso2/carbon-dashboards/pull/66
>>>
>>> *Sajith Abeywardhana* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka.
>>> Mobile: +94772260485
>>> Email: saji...@wso2.com | Web: www.wso2.com
>>>
>>> On Tue, Oct 6, 2015 at 2:16 PM, Sajith Abeywardhana 
>>> wrote:
>>>
 Fixed the code according to [Dev] [UES][Dashboard Server] Dashboard
 anonymous view landing page. Please merge the PR.

 *Sajith Abeywardhana* | Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka.
 Mobile: +94772260485
 Email: saji...@wso2.com | Web: www.wso2.com

 On Tue, Oct 6, 2015 at 10:59 AM, Sajith Abeywardhana 
 wrote:

> Please hold this merge. Page link rendering logic should be changed.
> We can't check *!user *after the jira -
> https://wso2.org/jira/browse/UES-597
>
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>
> On Tue, Oct 6, 2015 at 10:38 AM, Sajith Abeywardhana  > wrote:
>
>> Please review and merge
>> https://github.com/wso2/carbon-dashboards/pull/66 for
>> https://wso2.org/jira/browse/UES-599
>>
>>
>> *Sajith Abeywardhana* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka.
>> Mobile: +94772260485
>> Email: saji...@wso2.com | Web: www.wso2.com
>>
>
>

>>>
>>
>>
>> --
>> *Ayesha Dissanayaka*
>> Software Engineer,
>> WSO2, Inc : http://wso2.com
>> 
>> 20, Palmgrove Avenue, Colombo 3
>> E-Mail: aye...@wso2.com 
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] STS functionality broken due to opensaml upgrade

[Maduranga Siriwardena]

Hi all,

We are having a web app deployment issue possibly due to the new opensaml
orbit bundle (because of having two opensaml versions). So until we find a
proper solution we are downgrading the opensaml version back to 2.4.1.

Thanks,
Maduranga.

On Wed, Oct 7, 2015 at 11:09 AM, Hasintha Indrajee 
wrote:

> STS functionality has been broken due to the upgrade of the opensaml
> version (from 2.4.1 to 2.6.4) in carbon-identity. Error [1], can be
> observed while invoking sts service with UT policy engaged. Further the
> issue seems to be a failure to find class org.opensaml,XML from one of the
> classes which resides in opensaml itself (org.opensaml.SAMLNameIdentifier).
>
> [1] http://schemas.xmlsoap.org/soap/envelope/;>http://www.w3.org/2005/08/addressing;>http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
> soapenv:mustUnderstand="1">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
> wsu:Id="Timestamp-136">2015-10-06T11:47:27.145Z2015-10-06T11:52:27.145Z
> http://www.w3.org/2005/08/addressing/soap/faultuuid:29736852-243e-40cb-9860-68d2db234e6fsoapenv:Serverjava.lang.NoClassDefFoundError:
> Could not initialize class
> org.opensaml.XML
> --
> Hasintha Indrajee
> Software Engineer
> WSO2, Inc.
> Mobile:+94 771892453
>
>


-- 
Maduranga Siriwardena
Software Engineer
WSO2 Inc.

email: madura...@wso2.com
mobile: +94718990591
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] dockersupport-1.1 branch building issue with workflow extensions changes

[Danushka Fernando]

IMO get stages from appfactory.xml and create tenant in all stages makes
sense. But IIRC we added stages to the bpel in case we need to do some
special thing for some stage such as production. @Manjula: Is it a valid
requirement still?

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Tue, Oct 6, 2015 at 8:28 PM, Amalka Subasinghe  wrote:

>
>
> On Tue, Oct 6, 2015 at 8:26 PM, Amalka Subasinghe  wrote:
>
>> Yes, we need 3 messages in MB, that we are creating within the
>> initializeCloudManager method.
>> see the sequence diagram I have shared in @architecture: [Architecture]
>> [AppFactory]New governance and tenant creation changes to AppFactory
>> deployment with single Stratos
>>
>
> within the  initializeCloudManager method, get the stages defined in
> appfactory.xml file (in our case, dev, test n prod), create 3 messages to
> create tenant in 3 Greg instances and put in MB
>
>>
>> On Tue, Oct 6, 2015 at 8:03 PM, Punnadi Gunarathna 
>> wrote:
>>
>>> Hi,
>>>
>>> I think since we are going to introduce 3 GReg servers for each stage,
>>> we will have to have 3 topics in MB and subscribe to relevant one based on
>>> the stage as it was done before.
>>>
>>> On Tue, Oct 6, 2015 at 9:07 AM, Amalka Subasinghe 
>>> wrote:
>>>
 As I know what you are doing is, implementing a extension class to
 invoke the methods defined in
 AppFactoryTenantInfraStructureInitializerService class. Now with the new
 implementation we have removed calling initializeCloudManager method 3
 times for 3 stages. Instead of that we call initializeCloudManager methods
 only once and within that method we create tenant in all stages.

 So you need to update your extension class to invoke
 initializeCloudManager method once. No need to revert the changes done by
 Punnadi.

 On Tue, Oct 6, 2015 at 5:43 PM, Punnadi Gunarathna 
 wrote:

> Hi Lahiru,
>
>
> Please find the changes made by me in [1]. I think you will have to
> revert it back to it's initial state.
>
> [1]
> https://github.com/punnadih/product-af/commit/c58f448a61f42d1ba8f6e5206e437076926267f8
>
> On Tue, Oct 6, 2015 at 6:49 AM, Lahiru Manohara 
> wrote:
>
>> Now cloud manager initialization is happening inside the 
>> initializeCloudManager
>> method and also initializeCloudManager method calls for three stages  are
>> removed from the BPEL as well.
>>
>> On Tue, Oct 6, 2015 at 4:25 PM, Anuruddha Premalal <
>> anurud...@wso2.com> wrote:
>>
>>> Hi Lahiru,
>>>
>>> Tenant creation was done by (+ punnadi). Since we had a single
>>> stratos, didn't want stage parameter to create tenant in separate
>>> registries, however once we move tenant creation to greg's you might 
>>> have
>>> to bring the stage parameter back or you could use multiple subscriber 
>>> on
>>> the tenant creation message.
>>>
>>> Regards,
>>> Anuruddha.
>>>
>>> On Tue, Oct 6, 2015 at 2:49 PM, Lahiru Manohara 
>>> wrote:
>>>
 Hi Anuruddha,

 According to this full request[1]. The stage parameter was removed
 from the initializeCloudManager method in
 the AppFactoryTenantInfraStructureInitializerService class. In
 Tenantcreation BPEL and default workflow is calling 
 initializeCloudManager
 for three stages (development, testing and production). But how could 
 i do
 this from updated code?

 [1]. https://github.com/wso2/product-af/pull/526/files

 Thanks.
 --
 Best regards,

 *Lahiru Manohara*
 *Software Engineer*
 Mobile: +94716561576
 WSO2 Inc. | http://wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>> *Anuruddha Premalal*
>>> Software Eng. | WSO2 Inc.
>>> Mobile : +94717213122
>>> Web site : www.anuruddha.org
>>>
>>>
>>
>>
>> --
>> Best regards,
>>
>> *Lahiru Manohara*
>> *Software Engineer*
>> Mobile: +94716561576
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
>
> Thanks and Regards,
>
> Punnadi Gunarathna
> Senior Software Engineer,
> WSO2, Inc.; http://wso2.com 
> Blog: http://hi-my-world.blogspot.com/
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Amalka Subasinghe
 Senior Software Engineer
 WSO2 Inc.
 Mobile: +94 77 

Re: [Dev] [AF] dockersupport-1.1 branch building issue with workflow extensions changes

[Amalka Subasinghe]

Yes, we need 3 messages in MB, that we are creating within the
initializeCloudManager method.
see the sequence diagram I have shared in @architecture: [Architecture]
[AppFactory]New governance and tenant creation changes to AppFactory
deployment with single Stratos

On Tue, Oct 6, 2015 at 8:03 PM, Punnadi Gunarathna  wrote:

> Hi,
>
> I think since we are going to introduce 3 GReg servers for each stage, we
> will have to have 3 topics in MB and subscribe to relevant one based on the
> stage as it was done before.
>
> On Tue, Oct 6, 2015 at 9:07 AM, Amalka Subasinghe  wrote:
>
>> As I know what you are doing is, implementing a extension class to invoke
>> the methods defined in AppFactoryTenantInfraStructureInitializerService
>> class. Now with the new implementation we have removed calling
>> initializeCloudManager method 3 times for 3 stages. Instead of that we call
>> initializeCloudManager methods only once and within that method we create
>> tenant in all stages.
>>
>> So you need to update your extension class to invoke
>> initializeCloudManager method once. No need to revert the changes done by
>> Punnadi.
>>
>> On Tue, Oct 6, 2015 at 5:43 PM, Punnadi Gunarathna 
>> wrote:
>>
>>> Hi Lahiru,
>>>
>>>
>>> Please find the changes made by me in [1]. I think you will have to
>>> revert it back to it's initial state.
>>>
>>> [1]
>>> https://github.com/punnadih/product-af/commit/c58f448a61f42d1ba8f6e5206e437076926267f8
>>>
>>> On Tue, Oct 6, 2015 at 6:49 AM, Lahiru Manohara 
>>> wrote:
>>>
 Now cloud manager initialization is happening inside the 
 initializeCloudManager
 method and also initializeCloudManager method calls for three stages  are
 removed from the BPEL as well.

 On Tue, Oct 6, 2015 at 4:25 PM, Anuruddha Premalal 
 wrote:

> Hi Lahiru,
>
> Tenant creation was done by (+ punnadi). Since we had a single
> stratos, didn't want stage parameter to create tenant in separate
> registries, however once we move tenant creation to greg's you might have
> to bring the stage parameter back or you could use multiple subscriber on
> the tenant creation message.
>
> Regards,
> Anuruddha.
>
> On Tue, Oct 6, 2015 at 2:49 PM, Lahiru Manohara 
> wrote:
>
>> Hi Anuruddha,
>>
>> According to this full request[1]. The stage parameter was removed
>> from the initializeCloudManager method in
>> the AppFactoryTenantInfraStructureInitializerService class. In
>> Tenantcreation BPEL and default workflow is calling 
>> initializeCloudManager
>> for three stages (development, testing and production). But how could i 
>> do
>> this from updated code?
>>
>> [1]. https://github.com/wso2/product-af/pull/526/files
>>
>> Thanks.
>> --
>> Best regards,
>>
>> *Lahiru Manohara*
>> *Software Engineer*
>> Mobile: +94716561576
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> *Anuruddha Premalal*
> Software Eng. | WSO2 Inc.
> Mobile : +94717213122
> Web site : www.anuruddha.org
>
>


 --
 Best regards,

 *Lahiru Manohara*
 *Software Engineer*
 Mobile: +94716561576
 WSO2 Inc. | http://wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>>
>>> Thanks and Regards,
>>>
>>> Punnadi Gunarathna
>>> Senior Software Engineer,
>>> WSO2, Inc.; http://wso2.com 
>>> Blog: http://hi-my-world.blogspot.com/
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Amalka Subasinghe
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile: +94 77 9401267
>>
>
>
>
> --
>
> Thanks and Regards,
>
> Punnadi Gunarathna
> Senior Software Engineer,
> WSO2, Inc.; http://wso2.com 
> Blog: http://hi-my-world.blogspot.com/
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
> 
>



-- 
Amalka Subasinghe
Senior Software Engineer
WSO2 Inc.
Mobile: +94 77 9401267
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] dockersupport-1.1 branch building issue with workflow extensions changes

[Punnadi Gunarathna]

Hi,

I think since we are going to introduce 3 GReg servers for each stage, we
will have to have 3 topics in MB and subscribe to relevant one based on the
stage as it was done before.

On Tue, Oct 6, 2015 at 9:07 AM, Amalka Subasinghe  wrote:

> As I know what you are doing is, implementing a extension class to invoke
> the methods defined in AppFactoryTenantInfraStructureInitializerService
> class. Now with the new implementation we have removed calling
> initializeCloudManager method 3 times for 3 stages. Instead of that we call
> initializeCloudManager methods only once and within that method we create
> tenant in all stages.
>
> So you need to update your extension class to invoke
> initializeCloudManager method once. No need to revert the changes done by
> Punnadi.
>
> On Tue, Oct 6, 2015 at 5:43 PM, Punnadi Gunarathna 
> wrote:
>
>> Hi Lahiru,
>>
>>
>> Please find the changes made by me in [1]. I think you will have to
>> revert it back to it's initial state.
>>
>> [1]
>> https://github.com/punnadih/product-af/commit/c58f448a61f42d1ba8f6e5206e437076926267f8
>>
>> On Tue, Oct 6, 2015 at 6:49 AM, Lahiru Manohara 
>> wrote:
>>
>>> Now cloud manager initialization is happening inside the 
>>> initializeCloudManager
>>> method and also initializeCloudManager method calls for three stages  are
>>> removed from the BPEL as well.
>>>
>>> On Tue, Oct 6, 2015 at 4:25 PM, Anuruddha Premalal 
>>> wrote:
>>>
 Hi Lahiru,

 Tenant creation was done by (+ punnadi). Since we had a single stratos,
 didn't want stage parameter to create tenant in separate registries,
 however once we move tenant creation to greg's you might have to bring the
 stage parameter back or you could use multiple subscriber on the tenant
 creation message.

 Regards,
 Anuruddha.

 On Tue, Oct 6, 2015 at 2:49 PM, Lahiru Manohara 
 wrote:

> Hi Anuruddha,
>
> According to this full request[1]. The stage parameter was removed
> from the initializeCloudManager method in
> the AppFactoryTenantInfraStructureInitializerService class. In
> Tenantcreation BPEL and default workflow is calling initializeCloudManager
> for three stages (development, testing and production). But how could i do
> this from updated code?
>
> [1]. https://github.com/wso2/product-af/pull/526/files
>
> Thanks.
> --
> Best regards,
>
> *Lahiru Manohara*
> *Software Engineer*
> Mobile: +94716561576
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



 --
 *Anuruddha Premalal*
 Software Eng. | WSO2 Inc.
 Mobile : +94717213122
 Web site : www.anuruddha.org


>>>
>>>
>>> --
>>> Best regards,
>>>
>>> *Lahiru Manohara*
>>> *Software Engineer*
>>> Mobile: +94716561576
>>> WSO2 Inc. | http://wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>>
>> Thanks and Regards,
>>
>> Punnadi Gunarathna
>> Senior Software Engineer,
>> WSO2, Inc.; http://wso2.com 
>> Blog: http://hi-my-world.blogspot.com/
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Amalka Subasinghe
> Senior Software Engineer
> WSO2 Inc.
> Mobile: +94 77 9401267
>



-- 

Thanks and Regards,

Punnadi Gunarathna
Senior Software Engineer,
WSO2, Inc.; http://wso2.com 
Blog: http://hi-my-world.blogspot.com/
Tel : 94 11 214 5345
Fax :94 11 2145300


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

Re: [Dev] Please review and merge

[Sajith Abeywardhana]

If the user removes the isAnonView param from the url, next time browser
will show url as
*https://10.100.7.19:9443/portal/dashboards/ano-db01/landing?isAnonView=null
.
*Since null value is a bit ugly I fixed it and committed it to the PR.

*Sajith Abeywardhana* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka.
Mobile: +94772260485
Email: saji...@wso2.com | Web: www.wso2.com

On Wed, Oct 7, 2015 at 10:50 AM, Udara Rathnayake  wrote:

> Had a chat with Sajith. Current implementation seems fine..
>
> On Wed, Oct 7, 2015 at 10:40 AM, Sajith Abeywardhana 
> wrote:
>
>> Hi Ayesha,
>>
>> Small clarification?
>>
>>
>>> I observed that even *anonymous users* can view the logged in view by
>>> setting query parameter "isAnonView=false" or without setting it at all in
>>> the browser.
>>>
>>
>> I think you mean in here when the *logged in user* viewing anonymous
>> view he can view logged in view by setting query parameter
>> "isAnonView=false" or without setting it at all in the browser.
>>
>> Anonymous user(with out logging) never able to view logged in view. Am I
>> right?
>>
>>
>> *Sajith Abeywardhana* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka.
>> Mobile: +94772260485
>> Email: saji...@wso2.com | Web: www.wso2.com
>>
>>
>>
>>> Can you check this.
>>>
>>> Further, instead of having this reflected in the URL can we try keep it
>>> internally?
>>>
>>> Thanks!
>>> -Ayesha
>>>
>>>
>>> On Tue, Oct 6, 2015 at 6:42 PM, Sajith Abeywardhana 
>>> wrote:
>>>
 Both jira's[1][2] which relevant  to anon view committed under one
 PR[3]. Please review and merge.

 [1]. https://wso2.org/jira/browse/UES-597
 [2]. https://wso2.org/jira/browse/UES-599
 [3]. https://github.com/wso2/carbon-dashboards/pull/66

 *Sajith Abeywardhana* | Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka.
 Mobile: +94772260485
 Email: saji...@wso2.com | Web: www.wso2.com

 On Tue, Oct 6, 2015 at 2:16 PM, Sajith Abeywardhana 
 wrote:

> Fixed the code according to [Dev] [UES][Dashboard Server] Dashboard
> anonymous view landing page. Please merge the PR.
>
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>
> On Tue, Oct 6, 2015 at 10:59 AM, Sajith Abeywardhana  > wrote:
>
>> Please hold this merge. Page link rendering logic should be changed.
>> We can't check *!user *after the jira -
>> https://wso2.org/jira/browse/UES-597
>>
>> *Sajith Abeywardhana* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka.
>> Mobile: +94772260485
>> Email: saji...@wso2.com | Web: www.wso2.com
>>
>> On Tue, Oct 6, 2015 at 10:38 AM, Sajith Abeywardhana <
>> saji...@wso2.com> wrote:
>>
>>> Please review and merge
>>> https://github.com/wso2/carbon-dashboards/pull/66 for
>>> https://wso2.org/jira/browse/UES-599
>>>
>>>
>>> *Sajith Abeywardhana* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka.
>>> Mobile: +94772260485
>>> Email: saji...@wso2.com | Web: www.wso2.com
>>>
>>
>>
>

>>>
>>>
>>> --
>>> *Ayesha Dissanayaka*
>>> Software Engineer,
>>> WSO2, Inc : http://wso2.com
>>> 
>>> 20, Palmgrove Avenue, Colombo 3
>>> E-Mail: aye...@wso2.com 
>>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Isuru Wijesinghe]

Hi Thanuja,

The problem is not in the luciene *group by. *It works perfectly with
aggregate functions such as*  SUM, MIN, MAX, AVG . *But actually it didn't
work with *COUNT *function.

Thanks and Regards,

On Wed, Oct 7, 2015 at 12:07 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi Isuru,
>
> I think Gimantha has already discussed about this in this thread [1]. The
> link suggests to do lucene 'group by' queries using writing a custom facet
> collector.
>
> [1].
> http://mail-archives.apache.org/mod_mbox/lucene-java-user/201508.mbox/%3CCAPz8bx2j3eM9L6q=r0_XV-8=rskwct84+m3vkchhwk-hopc...@mail.gmail.com%3E
>
> Thanks.
>
> On Tue, Oct 6, 2015 at 10:59 PM, Isuru Wijesinghe 
> wrote:
>
>> Hi Anjana,
>>
>> I think the link [1] given something similar to *where* clause in sql (I
>> mean the *query *part is something similar to *where *clause). Here what
>> I really need to do is, use the count operation with *group by. * In
>> addition to that does luicene support for ascending and descending order
>> ???
>>
>> On Tue, Oct 6, 2015 at 3:54 PM, Anjana Fernando  wrote:
>>
>>> Hi Isuru,
>>>
>>> You can use the REST APIs search count [1] operation.
>>>
>>> [1]
>>> https://docs.wso2.com/display/DAS300/Retrieving+the+Number+of+Records+Matching+the+Given+Search+Query+via+REST+API
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe 
>>> wrote:
>>>
 Hi,

 I need to perform COUNT() operation through DAS REST API (an example is
 shown below). I tried to pass COUNT() from a luciene object. But it didn't
 work for me. Does DAS support COUNT operation through luciene ???  if not
 how can I enable it in DAS side???

 eg: *SELECT startedTime, processDefinitionId, COUNT(processInstanceId)
 AS processInstanceCount FROM PROCESS_USAGE_SUMMARY GROUP BY startedTime,
 processDefinitionId;*

 In addition to that, is that possible to pass more than one parameter
 to the query part in luicene object, because most graphs have to provide a
 secondary filter to get the result. As an example I need to filter the
 result from date range as well as process id.  I need something like this.

  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
 10035" *

 Any help will be appreciated.

 --
 Isuru Wijesinghe
 *Software Engineer*
 Mobile: 0710933706
 isur...@wso2.com

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


>>>
>>>
>>> --
>>> *Anjana Fernando*
>>> Senior Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> Isuru Wijesinghe
>> *Software Engineer*
>> Mobile: 0710933706
>> isur...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
Isuru Wijesinghe
*Software Engineer*
Mobile: 0710933706
isur...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

[Yasassri Ratnayake]

Hi Ajith,

It seems the configs are not correct in the sample, Also in your second
step the parameter name is *4 *which is correct, but in the
sample the Property is given *50. *This must be causing the
inconsistent behavior.

With Regards,

On Wed, Oct 7, 2015 at 8:27 AM, Ajith Vitharana  wrote:

> Hi All,
>
> I updated source view from the configuration mentioned in sample [1].
>
> i) When I double check the message processor configs from source view, I
>  noticed same config as the sample (expected behavior).
>
>  class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
> messageStore="*pending_subscriptions*" name="send_pending_message"
> targetEndpoint="DurableSubscriberEndpoint">
> 1000
> false
>  name="target.endpoint">DurableSubscriberEndpoint
> *50*
> 
>
> ii) When I go to the "Message Processors" UI and edit the config (wrong
> configurations)
>
>  class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
> targetEndpoint="DurableSubscriberEndpoint" messageStore="
> *pending_subscriptions*" xmlns="http://ws.apache.org/ns/synapse;>
>1000
>1000
>   * 4*
>true
>Disabled
>1
> 
>
> iii) According to the sample ,  I noticed  the message processor is
> deactivating after the 4 attempts, that means the second config executing
> at mediation.
>
>
> iv) When I check the file in synapse-configs/default/message-processors
> that is updated with my new configs.
>
> 
> http://ws.apache.org/ns/synapse;
>
> class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
>   name="*send_pending_message*"
>   targetEndpoint="DurableSubscriberEndpoint"
>   messageStore="pending_subscriptions">
>1000
>false
>DurableSubscriberEndpoint
>   * 50*
> 
>
>
> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>


-- 
Yasassri Ratnayake
Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

[Ajith Vitharana]

Hi Yasassri.

Yes. According to the carbon commits it has renamed. Then those configs
never tested after 2012 :)

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

-Ajith


Author: ishan
Date: Fri Jun 15 02:00:53 2012
New Revision: 130164
URL: http://wso2.org/svn/browse/wso2?view=rev=130164

Log:
Fixing CARBON-13114 with the patch of CharithaM.

Modified:
   carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
   carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/index.jsp
   carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/manageMessageForwardingProcessor.jsp

Modified: carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties?rev=130164=130163=130164=diff

==
--- carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
(original)
+++ carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/org/wso2/carbon/message/processor/ui/i18n/Resources.properties
Fri Jun 15 02:00:53 2012
@@ -24,7 +24,9 @@
 size=Size
 action=Actions
 deactivate=Deactivate
-activate=activate
+activate=Activate
+inactive=Inactive
+active=Active
 no.messageProcessors.are.currently.defined=No Message Processors are
currently defined.
 message.Processor= Message Processor
 name=Name
@@ -104,7 +106,7 @@
 message.sampling.processor.parameters=Message Sampling Processor Parameters
 message.context.properties=Message Context Properties
 interval=Message retry interval (Millis)

*-max.deliver.attempts=Maximum delivery
attempts+max.delivery.attempts=Maximum delivery attempts*
 axis2.repo=Axis2 Client repository
 axis2.config=Axis2 Configuration
 message.processor.reply.sequence=Reply sequence name
@@ -112,4 +114,4 @@
 quartz.conf=Quartz configuration file path
 cronExpression=Cron Expression
 target.endpoint=Address Endpoint name
-out_only=Out-only message
\ No newline at end of file
+out_only=Out-only message

Modified: carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/index.jsp
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/web/message_processor/index.jsp?rev=130164=130163=130164=diff

==
--- carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/index.jsp(original)
+++ carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/index.jspFri Jun 15 02:00:53 2012
@@ -290,11 +290,14 @@
id="delete_link" class="icon-link"
style="background-image:url(..
/admin/images/delete.gif);">
-
+
+[
+
+]
+
 
 <%
 } else if ("Scheduled Message Forwarding Processor".
@@ -308,11 +311,14 @@
id="delete_link" class="icon-link"
style="background-image:url(..
/admin/images/delete.gif);">
-
+
+[
+
+]
+
 
 <%
 } else if ("Message Sampling Processor".
@@ -326,11 +332,15 @@
id="delete_link" class="icon-link"
style="background-image:url(..
/admin/images/delete.gif);">
-
+ 
+[
+
+]
+
 
 <%} else { %>
 
-
\ No newline at end of file
+

Modified: carbon/platform/trunk/components/mediation/message-
processor/org.wso2.carbon.message.processor.ui/src/main/
resources/web/message_processor/manageMessageForwardingProcessor.jsp
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/mediation/message-processor/org.wso2.carbon.message.processor.ui/src/main/resources/web/message_processor/manageMessageForwardingProcessor.jsp?rev=130164=130163=130164=diff

[Dev] Is "defaultValue" field in the Publish Event Mediator always expected to be Empty?

[Awanthika Senarath]

Hi all,

On testing the developer studio 3.8.0 I could observe that the
"defaultValue" field for attribute parameters in the Publish Event Mediator
[1] is always empty and will not store any values.

On referring the documentation [2] for ESB 4.9.0 in the sample displayed
also I could observe the same. Could you please explain the purpose of
having this field in the said mediator and whether this is the correct
use-case to be implemented from Developer Studio end?


[1]  
  


  
  

  
  
http://services.samples
"/>
  
  


[2] https://docs.wso2.com/display/ESB490/Publish+Event+Mediator

Regards
Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Gimantha Bandara]

Hi Isuru,

Please refer to this[1] for equivalent COUNT in DAS. You can use aggregate
API for your case. But it may have some performance issues which I am
currently working on.

[1] https://wso2.org/jira/browse/DOCUMENTATION-2438

On Tue, Oct 6, 2015 at 2:37 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi Isuru,
>
> I think Gimantha has already discussed about this in this thread [1]. The
> link suggests to do lucene 'group by' queries using writing a custom facet
> collector.
>
> [1].
> http://mail-archives.apache.org/mod_mbox/lucene-java-user/201508.mbox/%3CCAPz8bx2j3eM9L6q=r0_XV-8=rskwct84+m3vkchhwk-hopc...@mail.gmail.com%3E
>
> Thanks.
>
> On Tue, Oct 6, 2015 at 10:59 PM, Isuru Wijesinghe 
> wrote:
>
>> Hi Anjana,
>>
>> I think the link [1] given something similar to *where* clause in sql (I
>> mean the *query *part is something similar to *where *clause). Here what
>> I really need to do is, use the count operation with *group by. * In
>> addition to that does luicene support for ascending and descending order
>> ???
>>
>> On Tue, Oct 6, 2015 at 3:54 PM, Anjana Fernando  wrote:
>>
>>> Hi Isuru,
>>>
>>> You can use the REST APIs search count [1] operation.
>>>
>>> [1]
>>> https://docs.wso2.com/display/DAS300/Retrieving+the+Number+of+Records+Matching+the+Given+Search+Query+via+REST+API
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe 
>>> wrote:
>>>
 Hi,

 I need to perform COUNT() operation through DAS REST API (an example is
 shown below). I tried to pass COUNT() from a luciene object. But it didn't
 work for me. Does DAS support COUNT operation through luciene ???  if not
 how can I enable it in DAS side???

 eg: *SELECT startedTime, processDefinitionId, COUNT(processInstanceId)
 AS processInstanceCount FROM PROCESS_USAGE_SUMMARY GROUP BY startedTime,
 processDefinitionId;*

 In addition to that, is that possible to pass more than one parameter
 to the query part in luicene object, because most graphs have to provide a
 secondary filter to get the result. As an example I need to filter the
 result from date range as well as process id.  I need something like this.

  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
 10035" *

 Any help will be appreciated.

 --
 Isuru Wijesinghe
 *Software Engineer*
 Mobile: 0710933706
 isur...@wso2.com

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


>>>
>>>
>>> --
>>> *Anjana Fernando*
>>> Senior Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> Isuru Wijesinghe
>> *Software Engineer*
>> Mobile: 0710933706
>> isur...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
Gimantha Bandara
Software Engineer
WSO2. Inc : http://wso2.com
Mobile : +94714961919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] carbon-commons-4.5.0 released!

[Kalpa Welivitigoda]

Hi folks,

$subject,

org.wso2.carbon.commons
carbon-commons
4.5.0

-- 
Best Regards,

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

Re: [Dev] Is "defaultValue" field in the Publish Event Mediator always expected to be Empty?

[Nuwan Pallewela]

Hi Awanthika,

I think this defaultValue can be any value. It is assigned for the
attribute if the expression can not find a property value.

Thanks,
Nuwan

On Wed, Oct 7, 2015 at 9:29 AM, Awanthika Senarath 
wrote:

> Hi all,
>
> On testing the developer studio 3.8.0 I could observe that the
> "defaultValue" field for attribute parameters in the Publish Event Mediator
> [1] is always empty and will not store any values.
>
> On referring the documentation [2] for ESB 4.9.0 in the sample displayed
> also I could observe the same. Could you please explain the purpose of
> having this field in the said mediator and whether this is the correct
> use-case to be implemented from Developer Studio end?
>
>
> [1]  
>   
>expression="get-property('axis2', 'HTTP_METHOD')"
>   name="http_method" type="STRING"/>
>name="destination" type="STRING"/>
>   
>   
>expression="get-property('SYSTEM_DATE')" name="date"
> type="STRING"/>
>   
>   
>expression="$body/m0:getQuote/m0:request/m0:symbol"
>   name="symbol" type="STRING" xmlns:m0="
> http://services.samples"/>
>   
>   
> 
>
> [2] https://docs.wso2.com/display/ESB490/Publish+Event+Mediator
>
> Regards
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

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

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge

[Ayesha Dissanayaka]

Hi Sajith,

Thanks for the fixes. I've merged the changes locally and testing the
functionality.

I observed that even anonymous users can view the logged in view by setting
query parameter "isAnonView=false" or without setting it at all in the
browser.

Can you check this.

Further, instead of having this reflected in the URL can we try keep it
internally?

Thanks!
-Ayesha


On Tue, Oct 6, 2015 at 6:42 PM, Sajith Abeywardhana 
wrote:

> Both jira's[1][2] which relevant  to anon view committed under one PR[3].
> Please review and merge.
>
> [1]. https://wso2.org/jira/browse/UES-597
> [2]. https://wso2.org/jira/browse/UES-599
> [3]. https://github.com/wso2/carbon-dashboards/pull/66
>
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>
> On Tue, Oct 6, 2015 at 2:16 PM, Sajith Abeywardhana 
> wrote:
>
>> Fixed the code according to [Dev] [UES][Dashboard Server] Dashboard
>> anonymous view landing page. Please merge the PR.
>>
>> *Sajith Abeywardhana* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka.
>> Mobile: +94772260485
>> Email: saji...@wso2.com | Web: www.wso2.com
>>
>> On Tue, Oct 6, 2015 at 10:59 AM, Sajith Abeywardhana 
>> wrote:
>>
>>> Please hold this merge. Page link rendering logic should be changed. We
>>> can't check *!user *after the jira -
>>> https://wso2.org/jira/browse/UES-597
>>>
>>> *Sajith Abeywardhana* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka.
>>> Mobile: +94772260485
>>> Email: saji...@wso2.com | Web: www.wso2.com
>>>
>>> On Tue, Oct 6, 2015 at 10:38 AM, Sajith Abeywardhana 
>>> wrote:
>>>
 Please review and merge
 https://github.com/wso2/carbon-dashboards/pull/66 for
 https://wso2.org/jira/browse/UES-599


 *Sajith Abeywardhana* | Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka.
 Mobile: +94772260485
 Email: saji...@wso2.com | Web: www.wso2.com

>>>
>>>
>>
>


-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Gimantha Bandara]

Hi Isuru,

On Tue, Oct 6, 2015 at 11:13 PM, Isuru Wijesinghe  wrote:

> Hi Thanuja,
>
> The problem is not in the luciene *group by. *It works perfectly with
> aggregate functions such as*  SUM, MIN, MAX, AVG . *But actually it
> didn't work with *COUNT *function.
>
> What do you mean by Count is not working? Does it return 0 as the count
per each group or does it return a wrong value as the count per each group?

Thanks and Regards,
>
> On Wed, Oct 7, 2015 at 12:07 AM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi Isuru,
>>
>> I think Gimantha has already discussed about this in this thread [1]. The
>> link suggests to do lucene 'group by' queries using writing a custom facet
>> collector.
>>
>> [1].
>> http://mail-archives.apache.org/mod_mbox/lucene-java-user/201508.mbox/%3CCAPz8bx2j3eM9L6q=r0_XV-8=rskwct84+m3vkchhwk-hopc...@mail.gmail.com%3E
>>
>> Thanks.
>>
>> On Tue, Oct 6, 2015 at 10:59 PM, Isuru Wijesinghe 
>> wrote:
>>
>>> Hi Anjana,
>>>
>>> I think the link [1] given something similar to *where* clause in sql
>>> (I mean the *query *part is something similar to *where *clause). Here
>>> what I really need to do is, use the count operation with *group by. *
>>> In addition to that does luicene support for ascending and descending order
>>> ???
>>>
>>> On Tue, Oct 6, 2015 at 3:54 PM, Anjana Fernando  wrote:
>>>
 Hi Isuru,

 You can use the REST APIs search count [1] operation.

 [1]
 https://docs.wso2.com/display/DAS300/Retrieving+the+Number+of+Records+Matching+the+Given+Search+Query+via+REST+API

 Cheers,
 Anjana.

 On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe 
 wrote:

> Hi,
>
> I need to perform COUNT() operation through DAS REST API (an example
> is shown below). I tried to pass COUNT() from a luciene object. But it
> didn't work for me. Does DAS support COUNT operation through luciene ???
> if not how can I enable it in DAS side???
>
> eg: *SELECT startedTime, processDefinitionId,
> COUNT(processInstanceId) AS processInstanceCount FROM 
> PROCESS_USAGE_SUMMARY
> GROUP BY startedTime, processDefinitionId;*
>
> In addition to that, is that possible to pass more than one parameter
> to the query part in luicene object, because most graphs have to provide a
> secondary filter to get the result. As an example I need to filter the
> result from date range as well as process id.  I need something like this.
>
>  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
> 10035" *
>
> Any help will be appreciated.
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Anjana Fernando*
 Senior Technical Lead
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

>>>
>>>
>>>
>>> --
>>> Isuru Wijesinghe
>>> *Software Engineer*
>>> Mobile: 0710933706
>>> isur...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>
>
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>



-- 
Gimantha Bandara
Software Engineer
WSO2. Inc : http://wso2.com
Mobile : +94714961919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SSO Authentication Error

[Gayan Gunawardana]

Hi Darshana,

I also experienced NPE in federated SAML SSO use case. Should be fixed with
following changes you have added.

- cacheEntry = new SessionContextCacheEntry(sessionContextDO); + if
(sessionContextDO != null) { + cacheEntry = new SessionContextCacheEntry
(sessionContextDO); + }

Thanks,
Gayan

On Tue, Oct 6, 2015 at 6:44 PM, Charitha Goonetilleke 
wrote:

> Hi All,
>
> I tried with latest commits and seems, $subject is solved with latest
> changes.
>
> Thanks,
> /charithag
>
> On Tue, Oct 6, 2015 at 3:20 PM, Darshana Gunawardana 
> wrote:
>
>>
>>
>> On Tue, Oct 6, 2015 at 2:21 PM, Hasintha Indrajee 
>> wrote:
>>
>>> Seems like this issue occurs since the session key you send with your
>>> second request  is no longer there in the server side and it gives this
>>> error. Did you check this in the latest code base ? Can you confirm that
>>> this is still there in the latest code base.
>>>
>>
>> Yes this is fixed with :
>> https://github.com/wso2/carbon-identity/commit/1d9bb6763c740c0e39b741f30a0d11d88c37bebc
>>
>>
>>> If this is still there, please open a jira for this issue.
>>>
>>
>> +1 Create a L1 if you see any NPEs on this flow.
>>
>> Thanks,
>> Darshana
>>
>>>
>>> On Tue, Oct 6, 2015 at 1:34 PM, Charitha Goonetilleke <
>>> charit...@wso2.com> wrote:
>>>
 Hi All,

 I'm using carbon.identity.version 4.6.0-SNAPSHOT with IoT Server for
 testing. $subject occurred when I tried to login in to store/publisher. It
 further saying, "Something went wrong during the authentication process.
 Please try signing in again." Also in console printing a Null Pointer
 Exception[1].

 This is the way to reproduce the issue.

- Extract a pack with carbon.identity.version 4.6.0-SNAPSHOT from
zip archive.
- Run pack and try to login as admin
- Shutdown the pack and delete all files of pack.
- Extract pack again from zip archive.
- Run pack and try to login.

 Exception [1]

 [2015-10-06 12:38:23,902] ERROR
 {org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
 -  Exception in Authentication Framework
 java.lang.NullPointerException
 at
 org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCacheEntry.(SessionContextCacheEntry.java:40)
 at
 org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCache.getValueFromCache(SessionContextCache.java:95)
 at
 org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils.getSessionContextFromCache(FrameworkUtils.java:592)
 at
 org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.findPreviousAuthenticatedSession(DefaultRequestCoordinator.java:284)
 at
 org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.initializeFlow(DefaultRequestCoordinator.java:222)
 at
 org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.handle(DefaultRequestCoordinator.java:103)
 at
 org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doPost(CommonAuthenticationServlet.java:53)
 at
 org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doGet(CommonAuthenticationServlet.java:43)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 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:60)
 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.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at
 org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
 at
 

Re: [Dev] SSO Authentication Error

[Darshana Gunawardana]

Hi Gayan,

On Tue, Oct 6, 2015 at 11:17 PM, Gayan Gunawardana  wrote:

> Hi Darshana,
>
> I also experienced NPE in federated SAML SSO use case. Should be fixed
> with following changes you have added.
>

Yes, we had this NPE earlier and as mentioned above its fixed with
https://github.com/wso2/carbon-identity/commit/1d9bb6763c740c0e39b741f30a0d11d88c37bebc


If you see any other NPEs in any authenication flow, please raise a JIRA.

Thanks,
Darshana.


> - cacheEntry = new SessionContextCacheEntry(sessionContextDO); + if
> (sessionContextDO != null) { + cacheEntry = new SessionContextCacheEntry
> (sessionContextDO); + }
>
> Thanks,
> Gayan
>
> On Tue, Oct 6, 2015 at 6:44 PM, Charitha Goonetilleke 
> wrote:
>
>> Hi All,
>>
>> I tried with latest commits and seems, $subject is solved with latest
>> changes.
>>
>> Thanks,
>> /charithag
>>
>> On Tue, Oct 6, 2015 at 3:20 PM, Darshana Gunawardana 
>> wrote:
>>
>>>
>>>
>>> On Tue, Oct 6, 2015 at 2:21 PM, Hasintha Indrajee 
>>> wrote:
>>>
 Seems like this issue occurs since the session key you send with your
 second request  is no longer there in the server side and it gives this
 error. Did you check this in the latest code base ? Can you confirm that
 this is still there in the latest code base.

>>>
>>> Yes this is fixed with :
>>> https://github.com/wso2/carbon-identity/commit/1d9bb6763c740c0e39b741f30a0d11d88c37bebc
>>>
>>>
 If this is still there, please open a jira for this issue.

>>>
>>> +1 Create a L1 if you see any NPEs on this flow.
>>>
>>> Thanks,
>>> Darshana
>>>

 On Tue, Oct 6, 2015 at 1:34 PM, Charitha Goonetilleke <
 charit...@wso2.com> wrote:

> Hi All,
>
> I'm using carbon.identity.version 4.6.0-SNAPSHOT with IoT Server for
> testing. $subject occurred when I tried to login in to store/publisher. It
> further saying, "Something went wrong during the authentication process.
> Please try signing in again." Also in console printing a Null Pointer
> Exception[1].
>
> This is the way to reproduce the issue.
>
>- Extract a pack with carbon.identity.version 4.6.0-SNAPSHOT from
>zip archive.
>- Run pack and try to login as admin
>- Shutdown the pack and delete all files of pack.
>- Extract pack again from zip archive.
>- Run pack and try to login.
>
> Exception [1]
>
> [2015-10-06 12:38:23,902] ERROR
> {org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
> -  Exception in Authentication Framework
> java.lang.NullPointerException
> at
> org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCacheEntry.(SessionContextCacheEntry.java:40)
> at
> org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCache.getValueFromCache(SessionContextCache.java:95)
> at
> org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils.getSessionContextFromCache(FrameworkUtils.java:592)
> at
> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.findPreviousAuthenticatedSession(DefaultRequestCoordinator.java:284)
> at
> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.initializeFlow(DefaultRequestCoordinator.java:222)
> at
> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.handle(DefaultRequestCoordinator.java:103)
> at
> org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doPost(CommonAuthenticationServlet.java:53)
> at
> org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doGet(CommonAuthenticationServlet.java:43)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
> 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:60)
> 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
> 

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Thanuja Uruththirakodeeswaran]

Hi Isuru,

I think Gimantha has already discussed about this in this thread [1]. The
link suggests to do lucene 'group by' queries using writing a custom facet
collector.

[1].
http://mail-archives.apache.org/mod_mbox/lucene-java-user/201508.mbox/%3CCAPz8bx2j3eM9L6q=r0_XV-8=rskwct84+m3vkchhwk-hopc...@mail.gmail.com%3E

Thanks.

On Tue, Oct 6, 2015 at 10:59 PM, Isuru Wijesinghe  wrote:

> Hi Anjana,
>
> I think the link [1] given something similar to *where* clause in sql (I
> mean the *query *part is something similar to *where *clause). Here what
> I really need to do is, use the count operation with *group by. * In
> addition to that does luicene support for ascending and descending order
> ???
>
> On Tue, Oct 6, 2015 at 3:54 PM, Anjana Fernando  wrote:
>
>> Hi Isuru,
>>
>> You can use the REST APIs search count [1] operation.
>>
>> [1]
>> https://docs.wso2.com/display/DAS300/Retrieving+the+Number+of+Records+Matching+the+Given+Search+Query+via+REST+API
>>
>> Cheers,
>> Anjana.
>>
>> On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe 
>> wrote:
>>
>>> Hi,
>>>
>>> I need to perform COUNT() operation through DAS REST API (an example is
>>> shown below). I tried to pass COUNT() from a luciene object. But it didn't
>>> work for me. Does DAS support COUNT operation through luciene ???  if not
>>> how can I enable it in DAS side???
>>>
>>> eg: *SELECT startedTime, processDefinitionId, COUNT(processInstanceId)
>>> AS processInstanceCount FROM PROCESS_USAGE_SUMMARY GROUP BY startedTime,
>>> processDefinitionId;*
>>>
>>> In addition to that, is that possible to pass more than one parameter to
>>> the query part in luicene object, because most graphs have to provide a
>>> secondary filter to get the result. As an example I need to filter the
>>> result from date range as well as process id.  I need something like this.
>>>
>>>  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
>>> 10035" *
>>>
>>> Any help will be appreciated.
>>>
>>> --
>>> Isuru Wijesinghe
>>> *Software Engineer*
>>> Mobile: 0710933706
>>> isur...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Anjana Fernando*
>> Senior Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>
>
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

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

[Dev] USE-597 Use case update

[Sajith Abeywardhana]

Hi All,

As discussed with Udara, I update the use case of the jirs[1]. If you got
any suggestion please let me know.

Updated use case : When the user designing a dashboard he can click on the
view button. Then dashboard preview should be displayed. If the user
designing the anonymous page, then the anonymous preview should be
displayed. Otherwise, if the user designing the default page, then the
default preview should be displayed.

[1]. https://wso2.org/jira/browse/UES-597

*Sajith Abeywardhana* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka.
Mobile: +94772260485
Email: saji...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Code Styling - Throwing Exceptions

[Nuwan Wimalasekara]

Hi Manuranga,

We have discussed the subject in the mail thread "Best Practice in Throwing
Exceptions in test methods signature"@d...@wso2.com as well. You can get
some information from the thread.

Thanks,
Nuwanw

On Tue, Oct 6, 2015 at 12:01 PM, Manuranga Perera  wrote:

> Following issue came up during a code review. when writing tests should we
> throw individual Exception types [1] or should we just throw Exception
> super class.
>
> I though the best practice is to throw individual classes. But I got to
> know that there is a common practice to throw Exception class in this case.
> Is this correct. Should we follow the same?
>
> [1]
> https://github.com/wso2/product-ues/pull/25/files#diff-c64bcb3f71c33d2ce7a50ad8f39f6c38R41
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EJB Mediator] SequenceMediator object is not an instance of declaring class

[Malaka Silva]

Hi Rajjaz,

Seems like you have specified invalid method or invalid number of
arguments. Try debugging this case [1]

[1]
https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/mediators/bean/BeanUtils.java

On Tue, Oct 6, 2015 at 12:32 PM, Rajjaz Mohammed  wrote:

> Hi Dev,
> I’m trying simple helloworld sample using EJB Mediator . while I’m running
> the sample I’m getting below error. can anyone guide me on this
> error?(Jboss-5.1)
>
> [2015-10-06 12:24:01,082] DEBUG - wire >> "POST /services/ejb
> HTTP/1.1[\r][\n]"
> [2015-10-06 12:24:01,083] DEBUG - wire >> "Accept-Encoding:
> gzip,deflate[\r][\n]"
> [2015-10-06 12:24:01,083] DEBUG - wire >> "Content-Type:
> text/xml;charset=UTF-8[\r][\n]"
> [2015-10-06 12:24:01,083] DEBUG - wire >> "SOAPAction:
> "urn:mediate"[\r][\n]"
> [2015-10-06 12:24:01,083] DEBUG - wire >> "Content-Length: 214[\r][\n]"
> [2015-10-06 12:24:01,083] DEBUG - wire >> "Host:
> rajjaz-ThinkPad-T540p:8280[\r][\n]"
> [2015-10-06 12:24:01,083] DEBUG - wire >> "Connection: Keep-Alive[\r][\n]"
> [2015-10-06 12:24:01,083] DEBUG - wire >> "User-Agent:
> Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]"
> [2015-10-06 12:24:01,083] DEBUG - wire >> "[\r][\n]"
> [2015-10-06 12:24:01,084] DEBUG - wire >> " xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;>[\n]"
> [2015-10-06 12:24:01,084] DEBUG - wire >> "   [\n]"
> [2015-10-06 12:24:01,084] DEBUG - wire >> "   [\n]"
> [2015-10-06 12:24:01,084] DEBUG - wire >> "   [\n]"
> [2015-10-06 12:24:01,084] DEBUG - wire >> "
> rajjaz[\n]"
> [2015-10-06 12:24:01,084] DEBUG - wire >> "[\n]"
> [2015-10-06 12:24:01,084] DEBUG - wire >> "[\n]"
> [2015-10-06 12:24:01,084] DEBUG - wire >> ""
> [2015-10-06 12:24:01,092] ERROR - SequenceMediator object is not an
> instance of declaring class
> java.lang.IllegalArgumentException: object is not an instance of declaring
> class
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.apache.synapse.mediators.bean.BeanUtils.invokeInstanceMethod(BeanUtils.java:74)
> at
> org.apache.synapse.mediators.bean.enterprise.EJBMediator.mediate(EJBMediator.java:132)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
> at
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:185)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:395)
> at
> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> [2015-10-06 12:24:01,094]  INFO - LogMediator To: /services/ejb, WSAction:
> urn:mediate, SOAPAction: urn:mediate, MessageID:
> urn:uuid:172f58fa-9099-432e-b48d-d013c59796d5, Direction: request, MESSAGE
> = Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE =
> object is not an instance of declaring class, Envelope:  encoding='utf-8'?>http://schemas.xmlsoap.org/soap/envelope/;>
>
>  rajjaz
> 
> 
> [2015-10-06 12:24:01,094]  INFO - LogMediator To: /services/ejb, WSAction:
> urn:mediate, SOAPAction: urn:mediate, MessageID:
> urn:uuid:172f58fa-9099-432e-b48d-d013c59796d5, Direction: request,
> Envelope:  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;>
>
>  rajjaz
> 
> 
> [2015-10-06 12:24:01,095] DEBUG - wire << "HTTP/1.1 202 Accepted[\r][\n]"
> [2015-10-06 12:24:01,096] DEBUG - wire << "Date: Tue, 06 Oct 2015 06:54:01
> GMT[\r][\n]"
> [2015-10-06 12:24:01,096] DEBUG - wire << "Transfer-Encoding:
> chunked[\r][\n]"
> [2015-10-06 12:24:01,096] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
> [2015-10-06 12:24:01,096] DEBUG - wire << "[\r][\n]"
> [2015-10-06 12:24:01,096] DEBUG - wire << "0[\r][\n]"
> [2015-10-06 12:24:01,096] DEBUG - wire << "[\r][\n]"
>
>
>
>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile | +94752833834
> Email   | raj...@wso2.com
> LinkedIn | Blogger | WSO2 Profile
> 
>



-- 

Best Regards,

Malaka 

Re: [Dev] [UES][Dashboard Server] Dashboard anonymous view landing page

[Udara Rathnayake]

Hi Ayesha,

frankly I haven't tested any tenant scenarios with this implementation.

*few points to consider*
If user (not authenticated) browses the dashboard
https://:/portal/dashboards/
this should render the anon view. Once user logged in we should render the
default view. In this default view we DON'T need to provide a link to anon
view. (this should be available during the design phase for developer to
review)

We don't need to think about user level customization within the anon
view(since no real user exists at this time, no edit stuff in anon view).

I discussed above with Sajith today.

Regards,
UdaraR

On Tue, Oct 6, 2015 at 12:56 PM, Ayesha Dissanayaka  wrote:

> Hi Udara/Manu,
>
> Have we considered multi-tenant scenarios while designing anonymous view
> of dashboards.
>
> For instance what will be the dashboard view rendered for an user who has
> logged into super tenant and trying to access a dashboard view URL of
> another tenant domain.( ex. wso2.com).
>
> In that case should we still show the anonymous view of the dashboard or
> default view?
>
> In my opinion we should show the anonymous view and disable the dashboard
> edit options. WDYT?
>
> Thanks!
> -Ayesha
>
>
> On Fri, Oct 2, 2015 at 6:43 PM, Udara Rathnayake  wrote:
>
>> Thanks for the feedback lasantha and nipuna.
>> I'm +1 to make the landing page anon if there are any anon views defined
>> in other pages. Let's stick to that.
>>
>> On Fri, Oct 2, 2015 at 9:15 AM, Nipuna Chandradasa 
>> wrote:
>>
>>> Hi Udara,
>>>
>>> As Lasantha said that making the landing page an anon view should be
>>> mandatory if there are anon views available under the that landing page
>>> even the landing page doesn't have anon content to view.
>>>
>>> I think this is a good idea because it is not that great to have child
>>> pages which has anon view but the user cannot access the main view. At
>>> Least if there are no content to show under the landing page to a user (
>>> Which is not that great if it mandatory to make the landing page anon view)
>>> at least we can show a message saying which pages are anon views and have
>>> the anon content.
>>>
>>> Thanks.
>>>
>>> On Fri, Oct 2, 2015 at 8:46 AM, Lasantha Samarakoon 
>>> wrote:
>>>
 Hi Udara,

 Can't we show the actual landing page even though the anon view is not
 defined? So if the landing page doesn't have a anon view, then we can show
 some message with all other links to accessible pages (Same as what we have
 in regular websites. Once you logged in you have more features, otherwise
 limited. But the home page is home page).

 In your first option, the problem is that if the developer couldn't
 define the anon view landing page, ultimately the dashboard is not
 accessible for any anon user unless he knows the direct url for a page.
 Then there's no point of introducing the anon view for such scenarios.

 In the second option, as you mentioned it actually breaks the concept
 behind a landing page. And know one can define what will be the actual
 landing page in such situation.

 Or else we can emphasis (or make it mandatory) the developer to define
 a anon view for the landing page in the designer if there are any anon
 pages for the dashboard.


 Regards,


 *Lasantha Samarakoon* | Software Engineer
 WSO2, Inc.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 (71) 214 1576
 Email:  lasant...@wso2.com
 Web:www.wso2.com

 lean . enterprise . middleware

 On Thu, Oct 1, 2015 at 8:10 PM, Udara Rathnayake 
 wrote:

> Hi All,
>
> At the moment we have a landing page (which developer can select while
> creating the dashboard) and this is the page end-user will initially get
> once he/she browse the dashboard.
>
> So for the anonymous view of the dashboard, we are going to use the
> same landing page's anon view(if exists) else user will be redirected to
> the login page.
> This approach will basically need developer to have a anon view within
> the landing page if there are anon views for other pages.
>
> Otherwise we can go through existing pages and check existence of anon
> views first and then render. This approach will deviate from the landing
> page concept a bit.
>
> Any thoughts?
>
> Regards,
> UdaraR
>


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


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

[Dev] [BRS] Upgrading the Drools and its Dependencies

[Natasha Wijesekara]

Hi All,

I am trying to upgrade the Drools version of BRS to 6.2.0 and for this I
need the following drool jars:
drools-core
drools-complier
drools-jsr94
knowledge-api
kie-api
kie-internal

I was able to find out that out of the above all are osgi bundles except
for* drools-jsr94 *and* knowledge-api.*

Should I pack  all the drool jars as one orbit bundle or should I have
separate orbit bundles for each of them
Could you please let me know which is preferred?

Apart from the above , I'm bundling the following jars as separate orbit
bundles  which are dependencies of drools:
mvel2   : 2.2.4
janino   : 2.5.15
jsr94 : 1.1
joda-time : 2.8.2
jxl  : 2.6.12

Thanks,
-- 
*Natasha Wijesekare*

*Software Engineering Intern, WSO2  Inc:  http://wso2.com
*
*email  : nata...@wso2.com *
*mobile: +94 771358651*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Allowing jms publishers to create queues when publishing

[Hemika Kodikara]

Hi,

My concern is, as long as we don't break anything in the
specifications(AMQP, JMS), we can allow creation of queues from publishers.

Regards,
Hemika

Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com

Mobile : +9477762

On Tue, Oct 6, 2015 at 11:18 AM, Sasikala Kottegoda 
wrote:

> Hi all,
>
> According to the current implementation of WSO2 MB, publishers cannot
> create queues when publishing even though the subscribers can.
>
> Also, even though the queue is not internally getting created, messages
> published for a new queue are written into the database with the published
> queue name and therefore are stored. An issue regarding this situation can
> be found at [1].
>
> My concern is whether we should allow the creation of queues by publishers
> or whether we should restrict it so that message publishing to a
> non-existing queue is not allowed.
>
> Any comment will be highly appreciated.
>
> [1] https://wso2.org/jira/browse/MB-1433
>
> Thank you
> --
> Sasikala Kottegoda
> *Software Engineer*
> WSO2 Inc., http://wso2.com/
> lean. enterprise. middleware
> Mobile: +94 774835928/712792401
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Code Styling - Throwing Exceptions

[Manuranga Perera]

Following issue came up during a code review. when writing tests should we
throw individual Exception types [1] or should we just throw Exception
super class.

I though the best practice is to throw individual classes. But I got to
know that there is a common practice to throw Exception class in this case.
Is this correct. Should we follow the same?

[1]
https://github.com/wso2/product-ues/pull/25/files#diff-c64bcb3f71c33d2ce7a50ad8f39f6c38R41


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Is there any method which can checks the resource exists or not in registry

[Rajeenthini Satkunam]

Hi all,

I am writing UI test cases for UES/Dashboard Server(DS).I have tried to
write a test class for adding and deleting dashboard for the Dashboard
Server.Here I need to check the resource is existing or not at the
registry.You can have a look for the class[1] I have wrote for adding and
deleting dashboard.
[1] -
https://github.com/rajeenthini/product-ues/commit/e642d50edf08cc21d2b0a2b21463e4b3aadc587a

BTW I have modified my code in some ways .Those are I have included below
- Deleted deleteResource method from here
resourceAdminServiceClient.deleteResource(resourcePath);

@AfterClass(alwaysRun = true)
public void tearDown() throws MalformedURLException,
XPathExpressionException, RemoteException,
ResourceAdminServiceExceptionException {
try{
UESUIIntegrationTest.logout(getDriver(), getBaseUrl(),
getCurrentUsername());
}finally {
getDriver().quit();
}
}

- Added some code segment to the method deleteDashboard

@Test(groups = "wso2.ues.dashboard", description = "Deleting added
dashboard", dependsOnMethods = "testAddDashboardNew")
public void testDeleteDashboardNew() throws MalformedURLException,
XPathExpressionException, RemoteException,
ResourceAdminServiceExceptionException {
webElement = getDriver().findElement(By.id(dashboardTitle));
webElement.findElement(By.cssSelector("i.fw-delete")).click();
getDriver().findElement(By.cssSelector("span.ladda-label")).click();
assertFalse(getDriver().isElementPresent(By.id(dashboardTitle)),
"Error occurred while deleting dashboard" + dashboardTitle);
ResourceData[] resourceData =
resourceAdminServiceClient.getResourceData(resourcePath);
assertTrue(resourceData.length == 0,"Registry resource could not
be deleted due to some errors");
}

Now it's giving me exception when there is no such registry resource after
dashboard was deleted by UI testcase.

org.apache.axis2.AxisFault: Resource does not exist at path
/_system/config/ues/dashboards/sampledashboard1

So can anyone give some suggestions on $subject? Thanks in advance.
-- 

*Thank You.*

*Rajeenthini Satkunam*

*Associate Software Engineer | WSO2*


*E:rajeenth...@wso2.com *

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

[Dev] WSO2 Governance Registry 5.0.1 Released !!

[Sameera Kannangara]

WSO2 Governance Registry team is pleased to announce the release of WSO2
Governance Registry 5.0.1.!!

WSO2 Governance Registry provides end-to-end governance for enterprises. IT
professionals can streamline application development, testing and
deployment processes, as well as manage service lifecycles and assets using
WSO2 Governance Registry. The community and social aspects of WSO2
Governance Registry will act as an enabler for collaboration between
distributed teams, converting traditional human-centric tasks into key
assets of the governance process. It also includes business runtime
governance requirements through its interoperability with well-known
external monitoring and reporting applications.

For more information on WSO2 Governance Registry and to download the
product please visit http://wso2.com/products/governance-registry. Also
take a look at the online product documentation.

*How to Run*

1. Extract the downloaded zip
2. Go to the bin directory in the extracted folder
3. Run the wso2server.sh or wso2server.bat as appropriate
4. Launch a web browser and navigate to https://localhost:9443/carbon to
access the admin console
5. Navigate to https://localhost:9443/publisher to access the publisher
webapp
6. Navigate to https://localhost:9443/store to access the store webapp
7. Use "admin", "admin" as the username and password to login as an
admin

WSO2 Governance Registry 5.0.1 includes following improvements and bug
fixes.Improvement

   - Improvements 

Bug Fixes

   - Bug Fixes 


*Key Features of WSO2 Governance Registry*Registry & Repository for Anything

   - Store any type of data or metadata as resources including contracts,
   models, workflows, WSDLs, Word documents, server configurations and more
   - Revisions, versions with checkpointing and rollback for any resource
   or resource collections
   - Full-text search, metadata search, tagging
   - Register externally stored resources including via Microsoft Sharepoint
   - Define behaviors that trigger automatically based on resource type
   - Out of the box versioning support for WSDL, WADL and XSD
   - Out of the box support for Swagger imports, with facility to upload
   via a file or import using a link
   - Ability to specify custom storage paths for any RXT

SOA Governance

   - Flexible service registry for any type of services including REST
   services, JSON services, SOAP services and Thrift services
   - Govern all aspects of services including service descriptions, service
   consumption, service usage, service discovery, service lifecycle management
   and service policies
   - Service and application discovery for third-party servers
   - Dependency management and impact analysis
   - Graphical visualization (dependency graphs) of artifacts with
   associated resources and dependent artifacts enabling users to perform
   impact analysis when changes are made to an artifact
   - Policy management for both design-time and run-time
   - Comprehensive lifecycle management
   - Act as a policy store for any Policy Enforcement Point (PEP)
including WSO2
   Enterprise Service Bus 
and WSO2 Application Server
   
   - User notification and alert management supported with the ability to
   use email templates
   - Role based authentication and authorization leveraging information
   stored in common user repositories such as LDAP or MS Active Directory
   - Auditing, logging and reporting

Configuration Governance

   - Govern any kind of server/system configuration
   - Version and revision management with checkpointing & rollback
   - Full lifecycle management spanning across development, testing,
   staging and production environments
   - Integrates to any 3rd party product via command-line clients
   - Deeply integrated to all WSO2 Carbon middleware products

Development Process Governance

   - Govern all aspects of the develop-build-test-stage-production process
   - Integration with source code control systems such as SVN
   - Integration with 3rd party continuous integration (CI) systems such as
   Jenkins or Atlassian Bamboo
   - Integration with popular build systems such as Maven or Ant
   - Comprehensive end-to-end application lifecycle management and
   governance

Framework for Governing Anything

   - Define any type of governance asset
   - Customizable repository extension points, executable via manual
   intervention (aspects) and by the framework (handlers) along with relevant
   evaluation criteria (filters)
   - Integrated with 3rd party products and external systems
   - Repository APIs: JCR
   - Registry APIs: REST, JAXR
   - Governance APIs: REST, Atom/AtomPP, SOAP
   - Centrally integrated with the latest version of WSO2 Enterprise Store
   2.0  

Re: [Dev] [UES][Dashboard Server] Dashboard anonymous view landing page

[Ayesha Dissanayaka]

Hi Udara/Manu,

Have we considered multi-tenant scenarios while designing anonymous view of
dashboards.

For instance what will be the dashboard view rendered for an user who has
logged into super tenant and trying to access a dashboard view URL of
another tenant domain.( ex. wso2.com).

In that case should we still show the anonymous view of the dashboard or
default view?

In my opinion we should show the anonymous view and disable the dashboard
edit options. WDYT?

Thanks!
-Ayesha


On Fri, Oct 2, 2015 at 6:43 PM, Udara Rathnayake  wrote:

> Thanks for the feedback lasantha and nipuna.
> I'm +1 to make the landing page anon if there are any anon views defined
> in other pages. Let's stick to that.
>
> On Fri, Oct 2, 2015 at 9:15 AM, Nipuna Chandradasa 
> wrote:
>
>> Hi Udara,
>>
>> As Lasantha said that making the landing page an anon view should be
>> mandatory if there are anon views available under the that landing page
>> even the landing page doesn't have anon content to view.
>>
>> I think this is a good idea because it is not that great to have child
>> pages which has anon view but the user cannot access the main view. At
>> Least if there are no content to show under the landing page to a user (
>> Which is not that great if it mandatory to make the landing page anon view)
>> at least we can show a message saying which pages are anon views and have
>> the anon content.
>>
>> Thanks.
>>
>> On Fri, Oct 2, 2015 at 8:46 AM, Lasantha Samarakoon 
>> wrote:
>>
>>> Hi Udara,
>>>
>>> Can't we show the actual landing page even though the anon view is not
>>> defined? So if the landing page doesn't have a anon view, then we can show
>>> some message with all other links to accessible pages (Same as what we have
>>> in regular websites. Once you logged in you have more features, otherwise
>>> limited. But the home page is home page).
>>>
>>> In your first option, the problem is that if the developer couldn't
>>> define the anon view landing page, ultimately the dashboard is not
>>> accessible for any anon user unless he knows the direct url for a page.
>>> Then there's no point of introducing the anon view for such scenarios.
>>>
>>> In the second option, as you mentioned it actually breaks the concept
>>> behind a landing page. And know one can define what will be the actual
>>> landing page in such situation.
>>>
>>> Or else we can emphasis (or make it mandatory) the developer to define a
>>> anon view for the landing page in the designer if there are any anon pages
>>> for the dashboard.
>>>
>>>
>>> Regards,
>>>
>>>
>>> *Lasantha Samarakoon* | Software Engineer
>>> WSO2, Inc.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 (71) 214 1576
>>> Email:  lasant...@wso2.com
>>> Web:www.wso2.com
>>>
>>> lean . enterprise . middleware
>>>
>>> On Thu, Oct 1, 2015 at 8:10 PM, Udara Rathnayake 
>>> wrote:
>>>
 Hi All,

 At the moment we have a landing page (which developer can select while
 creating the dashboard) and this is the page end-user will initially get
 once he/she browse the dashboard.

 So for the anonymous view of the dashboard, we are going to use the
 same landing page's anon view(if exists) else user will be redirected to
 the login page.
 This approach will basically need developer to have a anon view within
 the landing page if there are anon views for other pages.

 Otherwise we can go through existing pages and check existence of anon
 views first and then render. This approach will deviate from the landing
 page concept a bit.

 Any thoughts?

 Regards,
 UdaraR

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


-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EJB Mediator] SequenceMediator object is not an instance of declaring class

[Rajjaz Mohammed]

Hi Dev,
I’m trying simple helloworld sample using EJB Mediator . while I’m running
the sample I’m getting below error. can anyone guide me on this
error?(Jboss-5.1)

[2015-10-06 12:24:01,082] DEBUG - wire >> "POST /services/ejb
HTTP/1.1[\r][\n]"
[2015-10-06 12:24:01,083] DEBUG - wire >> "Accept-Encoding:
gzip,deflate[\r][\n]"
[2015-10-06 12:24:01,083] DEBUG - wire >> "Content-Type:
text/xml;charset=UTF-8[\r][\n]"
[2015-10-06 12:24:01,083] DEBUG - wire >> "SOAPAction:
"urn:mediate"[\r][\n]"
[2015-10-06 12:24:01,083] DEBUG - wire >> "Content-Length: 214[\r][\n]"
[2015-10-06 12:24:01,083] DEBUG - wire >> "Host:
rajjaz-ThinkPad-T540p:8280[\r][\n]"
[2015-10-06 12:24:01,083] DEBUG - wire >> "Connection: Keep-Alive[\r][\n]"
[2015-10-06 12:24:01,083] DEBUG - wire >> "User-Agent:
Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]"
[2015-10-06 12:24:01,083] DEBUG - wire >> "[\r][\n]"
[2015-10-06 12:24:01,084] DEBUG - wire >> "http://schemas.xmlsoap.org/soap/envelope/;>[\n]"
[2015-10-06 12:24:01,084] DEBUG - wire >> "   [\n]"
[2015-10-06 12:24:01,084] DEBUG - wire >> "   [\n]"
[2015-10-06 12:24:01,084] DEBUG - wire >> "   [\n]"
[2015-10-06 12:24:01,084] DEBUG - wire >> " rajjaz[\n]"
[2015-10-06 12:24:01,084] DEBUG - wire >> "[\n]"
[2015-10-06 12:24:01,084] DEBUG - wire >> "[\n]"
[2015-10-06 12:24:01,084] DEBUG - wire >> ""
[2015-10-06 12:24:01,092] ERROR - SequenceMediator object is not an
instance of declaring class
java.lang.IllegalArgumentException: object is not an instance of declaring
class
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.apache.synapse.mediators.bean.BeanUtils.invokeInstanceMethod(BeanUtils.java:74)
at
org.apache.synapse.mediators.bean.enterprise.EJBMediator.mediate(EJBMediator.java:132)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:185)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:395)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[2015-10-06 12:24:01,094]  INFO - LogMediator To: /services/ejb, WSAction:
urn:mediate, SOAPAction: urn:mediate, MessageID:
urn:uuid:172f58fa-9099-432e-b48d-d013c59796d5, Direction: request, MESSAGE
= Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE =
object is not an instance of declaring class, Envelope: http://schemas.xmlsoap.org/soap/envelope/;>
   
 rajjaz


[2015-10-06 12:24:01,094]  INFO - LogMediator To: /services/ejb, WSAction:
urn:mediate, SOAPAction: urn:mediate, MessageID:
urn:uuid:172f58fa-9099-432e-b48d-d013c59796d5, Direction: request,
Envelope: http://schemas.xmlsoap.org/soap/envelope/;>
   
 rajjaz


[2015-10-06 12:24:01,095] DEBUG - wire << "HTTP/1.1 202 Accepted[\r][\n]"
[2015-10-06 12:24:01,096] DEBUG - wire << "Date: Tue, 06 Oct 2015 06:54:01
GMT[\r][\n]"
[2015-10-06 12:24:01,096] DEBUG - wire << "Transfer-Encoding:
chunked[\r][\n]"
[2015-10-06 12:24:01,096] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2015-10-06 12:24:01,096] DEBUG - wire << "[\r][\n]"
[2015-10-06 12:24:01,096] DEBUG - wire << "0[\r][\n]"
[2015-10-06 12:24:01,096] DEBUG - wire << "[\r][\n]"






-- 
Thank you
Best Regards

*Rajjaz HM*
Associate Software Engineer
WSO2 Inc. 
lean | enterprise | middleware
Mobile | +94752833834
Email   | raj...@wso2.com
LinkedIn | Blogger | WSO2 Profile


http://ws.apache.org/ns/synapse;
   name="ejb"
   transports="https http"
   startOnLoad="true"
   trace="disable">
   
   
  
 
 

   

 
 

 
 

   
  $ctx.response
   


 
 
  
   

/*
 * To change this license header, choose License Headers in Project Properties.
 * To change this template file, choose Tools | Templates
 * and open the template in the editor.
 */
package org;

import 

[Dev] [DAS] Performing SQL COUNT() operation through luciene

[Isuru Wijesinghe]

Hi,

I need to perform COUNT() operation through DAS REST API (an example is
shown below). I tried to pass COUNT() from a luciene object. But it didn't
work for me. Does DAS support COUNT operation through luciene ???  if not
how can I enable it in DAS side???

eg: *SELECT startedTime, processDefinitionId, COUNT(processInstanceId) AS
processInstanceCount FROM PROCESS_USAGE_SUMMARY GROUP BY startedTime,
processDefinitionId;*

In addition to that, is that possible to pass more than one parameter to
the query part in luicene object, because most graphs have to provide a
secondary filter to get the result. As an example I need to filter the
result from date range as well as process id.  I need something like this.

 *"query" : "timestamp : [1243214324532 TO 4654365223], processId : 10035" *

Any help will be appreciated.

-- 
Isuru Wijesinghe
*Software Engineer*
Mobile: 0710933706
isur...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] PPaaS 4.1.0 installer

[Lasindu Charith]

Hi Imesh,

On Mon, Oct 5, 2015 at 11:03 PM, Imesh Gunaratne  wrote:

> On Tue, Oct 6, 2015 at 12:09 AM, Gayan Gunarathne  wrote:
>>
>>
>> PPaaS installer will setup the private paas. Main responsibility of that
>> installer will be setup the db, ActiveMQ and Private PaaS and start the
>> Private PaaS server.
>>
>
> We may also need to configure CEP and DAS.
>

Yes, there should be an option to have CEP/DAS separately. From the
installer do we only ask to point the external CEP/DAS ip addresses or will
the installer take care of the configuration of CEP/DAS as well? (similar
to configuring puppet master)


> Thanks
>
> On Tue, Oct 6, 2015 at 12:09 AM, Gayan Gunarathne  wrote:
>
>>
>> Hi All,
>>
>> We are planing to have two installers with the PPaaS 4.1.0. Our idea
>> behind that is to make the PPaaS setup and the cartridge deployment to be
>> loosely coupled.
>>
>> +1

> PPaaS installer will setup the private paas. Main responsibility of that
>> installer will be setup the db, ActiveMQ and Private PaaS and start the
>> Private PaaS server.
>>
>
I think this is for PPaaS running in a single instance. Since we may not
recommend to use installer in production, we need not to support
distributed deployment of PPaaS in the installer. But as Imesh has
mentioned, we would need to support CEP/DAS running externally.


>
>> PPaaS cartridges installer will be to deploy the Private PaaS
>> cartridges.Main responsibility of this will be deploy the cartridges.Mainly
>> It will carry out the following tasks,
>>
>> - Obtain the user input on deployment product and environment
>> - If it is vm,
>>   set up the puppet master ,set up the packs , template module and
>> plugins to right location
>> - If it is kubenetes cluster,
>>pull the docker images for nodes/or build the docker image locally
>> and transfer to the Kubernetes cluster nodes based on the user input
>> - Execute configurator to configure the samples
>> - Update the deployment artifacts based on the user inputs and
>> initialized the deployment process through Rest API.
>>
>> We will maintain and release those two installers separately.
>>
>> Please share your thoughts and suggestions on this.
>>
>> Thanks,
>> Gayan
>>
>>
>>
>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

Thanks,
-- 
*Lasindu Charith*
Software Engineer, WSO2 Inc.
Committer & PMC Member, Apache Stratos
Mobile: +94714427192 | Web: blog.lasindu.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Lasindu Charith]

Hi Akila/Imesh,

Any reason why we moved common samples (network partitions, autoscale
policies, deployment policies, application policies) inside each cartridge?

If those artifacts are similar, what if we keep them in a common place?
(say inside common/samples/..). Once we introduce more cartridges, we will
have to add them again and if there's a new change we'll have to change it
everywhere(maintainability?)

WDYT?
If the priority/concern was regarding modularity, this approach is totally
fine for me.

Thanks,

On Sun, Oct 4, 2015 at 1:33 PM, Imesh Gunaratne  wrote:

> It looks good Akila!
>
> On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi,
>>
>> I've restructured the repo considering what we discussed here. I've also
>> added a distribution for VM related files.
>>
>> Final directory structure as follows;
>>
>> ├── common
>> │   ├── configurator
>> │   │   ├── live-test
>> │   │   │   ├── src
>> │   │   ├── src
>> │   │   │   ├── assembly
>> │   │   │   └── main
>> │   ├── docker
>> │   │   ├── base-image
>> │   │   │   ├── packages
>> │   │   │   └── scripts
>> │   │   └── scripts
>> │   ├── plugins
>> │   └── vm
>> │   ├── assembly
>> │   ├── init-scripts
>> │   │   ├── ec2
>> │   │   ├── gce
>> │   │   ├── openstack
>> │   │   └── vcloud
>> │   ├── puppet
>> │   │   ├── manifests
>> │   │   └── modules
>> ├── wso2am
>> │   ├── 1.9.0
>> │   │   ├── assembly
>> │   │   ├── docker
>> │   │   │   ├── packages
>> │   │   │   ├── plugins
>> │   │   │   └── scripts
>> │   │   ├── plugins
>> │   │   ├── samples
>> │   │   │   ├── application-policies
>> │   │   │   ├── applications
>> │   │   │   ├── autoscaling-policies
>> │   │   │   ├── cartridge-groups
>> │   │   │   ├── cartridges
>> │   │   │   ├── deployment-policies
>> │   │   │   ├── kubernetes-clusters
>> │   │   │   ├── network-partitions
>> │   │   │   └── template-modules
>> │   │   └── template-module
>> │   │   ├── files
>> │   │   ├── src
>> │   │   └── templates
>> ├── wso2as
>> │   ├── 5.2.1
>> │   │   ├── assembly
>> │   │   ├── docker
>> │   │   │   ├── packages
>> │   │   │   ├── plugins
>> │   │   │   └── scripts
>> │   │   ├── plugins
>> │   │   ├── samples
>> │   │   │   ├── application-policies
>> │   │   │   ├── applications
>> │   │   │   ├── autoscaling-policies
>> │   │   │   ├── cartridge-groups
>> │   │   │   ├── cartridges
>> │   │   │   ├── deployment-policies
>> │   │   │   ├── kubernetes-clusters
>> │   │   │   ├── network-partitions
>> │   │   │   ├── signups
>> │   │   │   └── template-modules
>> │   │   └── template-module
>> │   │   ├── files
>> │   │   ├── src
>> │   │   └── templates
>> ├── wso2esb
>> │   ├── 4.8.1
>> │   │   ├── assembly
>> │   │   ├── docker
>> │   │   │   ├── packages
>> │   │   │   ├── plugins
>> │   │   │   └── scripts
>> │   │   ├── plugins
>> │   │   ├── samples
>> │   │   │   ├── application-policies
>> │   │   │   ├── applications
>> │   │   │   ├── autoscaling-policies
>> │   │   │   ├── cartridge-groups
>> │   │   │   ├── cartridges
>> │   │   │   ├── deployment-policies
>> │   │   │   ├── kubernetes-clusters
>> │   │   │   ├── network-partitions
>> │   │   │   ├── signups
>> │   │   │   └── template-modules
>> │   │   │   ├── archive-tmp
>> │   │   │   └── maven-shared-archive-resources
>> │   │   └── template-module
>> │   │   ├── files
>> │   │   ├── src
>> │   │   └── templates
>> └── wso2is
>> ├── 5.0.0
>> │   ├── assembly
>> │   ├── docker
>> │   │   ├── packages
>> │   │   ├── plugins
>> │   │   └── scripts
>> │   ├── plugins
>> │   ├── samples
>> │   │   ├── application-policies
>> │   │   ├── applications
>> │   │   ├── autoscaling-policies
>> │   │   ├── cartridge-groups
>> │   │   ├── cartridges
>> │   │   ├── deployment-policies
>> │   │   ├── kubernetes-clusters
>> │   │   ├── network-partitions
>> │   │   ├── signups
>> │   │   └── template-modules
>> │   └── template-module
>> │   ├── files
>> │   ├── src
>> │   └── templates
>>
>>
>> On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne  wrote:
>>
>>> On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
>>> thanu...@wso2.com> wrote:
>>>
 Hi All,

 We have folder for base-image and inside that we have a folder called
 'docker' for docker base image. In the VM scenario, we are using
 init-scripts to create the vm base image. So what if we move the
 init-scripts folder inside /common/base-image/vm/ path?

>>>
>>> Yes, a good point! May be we can do the necessary changes.
>>>
>>> Thanks
>>>
>>> On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
>>> thanu...@wso2.com> wrote:
>>>
 Hi All,

 We have folder for base-image and inside that we have a folder called
 'docker' for docker base image. In the VM scenario, we are 

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Rajkumar Rajaratnam]

On Wed, Oct 7, 2015 at 9:38 AM, Lasindu Charith  wrote:

> Hi Akila/Imesh,
>
> Any reason why we moved common samples (network partitions, autoscale
> policies, deployment policies, application policies) inside each cartridge?
>
> If those artifacts are similar, what if we keep them in a common place?
> (say inside common/samples/..). Once we introduce more cartridges, we will
> have to add them again and if there's a new change we'll have to change it
> everywhere(maintainability?)
>

​+1 to keep them in a common place. Why we are duplicating these common
artifacts across all the cartridges?
​


>
> WDYT?
> If the priority/concern was regarding modularity, this approach is totally
> fine for me.
>
> Thanks,
>
> On Sun, Oct 4, 2015 at 1:33 PM, Imesh Gunaratne  wrote:
>
>> It looks good Akila!
>>
>> On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I've restructured the repo considering what we discussed here. I've also
>>> added a distribution for VM related files.
>>>
>>> Final directory structure as follows;
>>>
>>> ├── common
>>> │   ├── configurator
>>> │   │   ├── live-test
>>> │   │   │   ├── src
>>> │   │   ├── src
>>> │   │   │   ├── assembly
>>> │   │   │   └── main
>>> │   ├── docker
>>> │   │   ├── base-image
>>> │   │   │   ├── packages
>>> │   │   │   └── scripts
>>> │   │   └── scripts
>>> │   ├── plugins
>>> │   └── vm
>>> │   ├── assembly
>>> │   ├── init-scripts
>>> │   │   ├── ec2
>>> │   │   ├── gce
>>> │   │   ├── openstack
>>> │   │   └── vcloud
>>> │   ├── puppet
>>> │   │   ├── manifests
>>> │   │   └── modules
>>> ├── wso2am
>>> │   ├── 1.9.0
>>> │   │   ├── assembly
>>> │   │   ├── docker
>>> │   │   │   ├── packages
>>> │   │   │   ├── plugins
>>> │   │   │   └── scripts
>>> │   │   ├── plugins
>>> │   │   ├── samples
>>> │   │   │   ├── application-policies
>>> │   │   │   ├── applications
>>> │   │   │   ├── autoscaling-policies
>>> │   │   │   ├── cartridge-groups
>>> │   │   │   ├── cartridges
>>> │   │   │   ├── deployment-policies
>>> │   │   │   ├── kubernetes-clusters
>>> │   │   │   ├── network-partitions
>>> │   │   │   └── template-modules
>>> │   │   └── template-module
>>> │   │   ├── files
>>> │   │   ├── src
>>> │   │   └── templates
>>> ├── wso2as
>>> │   ├── 5.2.1
>>> │   │   ├── assembly
>>> │   │   ├── docker
>>> │   │   │   ├── packages
>>> │   │   │   ├── plugins
>>> │   │   │   └── scripts
>>> │   │   ├── plugins
>>> │   │   ├── samples
>>> │   │   │   ├── application-policies
>>> │   │   │   ├── applications
>>> │   │   │   ├── autoscaling-policies
>>> │   │   │   ├── cartridge-groups
>>> │   │   │   ├── cartridges
>>> │   │   │   ├── deployment-policies
>>> │   │   │   ├── kubernetes-clusters
>>> │   │   │   ├── network-partitions
>>> │   │   │   ├── signups
>>> │   │   │   └── template-modules
>>> │   │   └── template-module
>>> │   │   ├── files
>>> │   │   ├── src
>>> │   │   └── templates
>>> ├── wso2esb
>>> │   ├── 4.8.1
>>> │   │   ├── assembly
>>> │   │   ├── docker
>>> │   │   │   ├── packages
>>> │   │   │   ├── plugins
>>> │   │   │   └── scripts
>>> │   │   ├── plugins
>>> │   │   ├── samples
>>> │   │   │   ├── application-policies
>>> │   │   │   ├── applications
>>> │   │   │   ├── autoscaling-policies
>>> │   │   │   ├── cartridge-groups
>>> │   │   │   ├── cartridges
>>> │   │   │   ├── deployment-policies
>>> │   │   │   ├── kubernetes-clusters
>>> │   │   │   ├── network-partitions
>>> │   │   │   ├── signups
>>> │   │   │   └── template-modules
>>> │   │   │   ├── archive-tmp
>>> │   │   │   └── maven-shared-archive-resources
>>> │   │   └── template-module
>>> │   │   ├── files
>>> │   │   ├── src
>>> │   │   └── templates
>>> └── wso2is
>>> ├── 5.0.0
>>> │   ├── assembly
>>> │   ├── docker
>>> │   │   ├── packages
>>> │   │   ├── plugins
>>> │   │   └── scripts
>>> │   ├── plugins
>>> │   ├── samples
>>> │   │   ├── application-policies
>>> │   │   ├── applications
>>> │   │   ├── autoscaling-policies
>>> │   │   ├── cartridge-groups
>>> │   │   ├── cartridges
>>> │   │   ├── deployment-policies
>>> │   │   ├── kubernetes-clusters
>>> │   │   ├── network-partitions
>>> │   │   ├── signups
>>> │   │   └── template-modules
>>> │   └── template-module
>>> │   ├── files
>>> │   ├── src
>>> │   └── templates
>>>
>>>
>>> On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne  wrote:
>>>
 On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
 thanu...@wso2.com> wrote:

> Hi All,
>
> We have folder for base-image and inside that we have a folder called
> 'docker' for docker base image. In the VM scenario, we are using
> init-scripts to create the vm base image. So what if we move the
> init-scripts folder inside 

Re: [Dev] USE-597 Use case update

[Udara Rathnayake]

Hi,

+1. I don't see real use case to have a toggle between default/anon during
the actual preview window hence suggested above. And we are not going to
have the same toggle within the actual dashboard view for the end-user(NOT
the design view).

Simply authenticated user will get the default view, others the anon view.
within the anon view we have the login option so once authenticated they ll
have the default view.

Regards,
UdaraR

On Tue, Oct 6, 2015 at 12:41 PM, Sajith Abeywardhana 
wrote:

> Hi All,
>
> As discussed with Udara, I update the use case of the jirs[1]. If you got
> any suggestion please let me know.
>
> Updated use case : When the user designing a dashboard he can click on the
> view button. Then dashboard preview should be displayed. If the user
> designing the anonymous page, then the anonymous preview should be
> displayed. Otherwise, if the user designing the default page, then the
> default preview should be displayed.
>
> [1]. https://wso2.org/jira/browse/UES-597
>
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BRS] Upgrading the Drools and its Dependencies

[KasunG Gajasinghe]

Hi,

You can include drools jars under one orbit. Its dependencies will need
separate orbit bundles.

On Tue, Oct 6, 2015 at 11:33 AM, Natasha Wijesekara 
wrote:

> Hi All,
>
> I am trying to upgrade the Drools version of BRS to 6.2.0 and for this I
> need the following drool jars:
> drools-core
> drools-complier
> drools-jsr94
> knowledge-api
> kie-api
> kie-internal
>
> I was able to find out that out of the above all are osgi bundles except
> for* drools-jsr94 *and* knowledge-api.*
>
> Should I pack  all the drool jars as one orbit bundle or should I have
> separate orbit bundles for each of them
> Could you please let me know which is preferred?
>
> Apart from the above , I'm bundling the following jars as separate orbit
> bundles  which are dependencies of drools:
> mvel2   : 2.2.4
> janino   : 2.5.15
> jsr94 : 1.1
> joda-time : 2.8.2
> jxl  : 2.6.12
>
> Thanks,
> --
> *Natasha Wijesekare*
>
> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
> *
> *email  : nata...@wso2.com *
> *mobile: +94 771358651 <%2B94%20771358651>*
>



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] NPE with EIP guide sample.

[Chanaka Fernando]

Hi Ajith,

The scenario which you have tested is not correct. If you put 
mediator in the outSequence, since you are cloning the request and send to
2 back ends, ESB will get 2 responses and tries to send back 2 responses to
client and that is causing this exception. What happens is that ESB will
send back the first response and then release the connection. When it tries
to send back the 2nd response, If some other thread has already reused that
connection, the "request" will be null and that is causing the NPE.

If you are putting a  mediator in the outSequence, make sure you
aggregate the responses before sending the response back.

On Mon, Oct 5, 2015 at 9:23 PM, Ajith Vitharana  wrote:

>
>
> On Mon, Oct 5, 2015 at 5:59 AM, Chanaka Fernando 
> wrote:
>
>> Hi Ajith,
>>
>> We have already identified this issue and currently working on a fix.
>> Thanks for reporting this issue.
>>
>
> Thanks for looking to this.
>
> -Ajith
>
>>
>> On Mon, Oct 5, 2015 at 12:56 AM, Ajith Vitharana  wrote:
>>
>>> Hi All
>>>
>>> I did a slight change to sample [1] (used  instead of  at
>>> the outSequence) , now I'm getting following exception.
>>>
>>> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>>>
>>>
>>>
>>> [2015-10-04 15:19:30,891] DEBUG - wire << "[\r][\n]"
>>> [2015-10-04 15:19:30,892] ERROR - PassThroughHttpSender Failed to submit
>>> the response
>>> j*ava.lang.NullPointerException*
>>> * at
>>> org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)*
>>> * at
>>> org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)*
>>> * at
>>> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)*
>>> * at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)*
>>> at
>>> org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
>>> at
>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
>>> at
>>> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>>> at
>>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>>> at
>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:297)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>> [2015-10-04 15:19:30,894] ERROR - Axis2Sender
>>> Content-Type:application/soap+xml; charset=UTF-8;
>>> action="urn:getQuoteResponse",>> encoding='utf-8'?>http://www.w3.org/2003/05/soap-envelope;>
>>> Unexpected error sending message back
>>> org.apache.axis2.AxisFault: Failed to submit the response
>>> at
>>> org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:610)
>>> at
>>> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:269)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at
>>> org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
>>> at
>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
>>> at
>>> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>>> at
>>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>>> at
>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:297)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
>>> at
>>> 

[Dev] SSO Authentication Error

[Charitha Goonetilleke]

Hi All,

I'm using carbon.identity.version 4.6.0-SNAPSHOT with IoT Server for
testing. $subject occurred when I tried to login in to store/publisher. It
further saying, "Something went wrong during the authentication process.
Please try signing in again." Also in console printing a Null Pointer
Exception[1].

This is the way to reproduce the issue.

   - Extract a pack with carbon.identity.version 4.6.0-SNAPSHOT from zip
   archive.
   - Run pack and try to login as admin
   - Shutdown the pack and delete all files of pack.
   - Extract pack again from zip archive.
   - Run pack and try to login.

Exception [1]

[2015-10-06 12:38:23,902] ERROR
{org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
-  Exception in Authentication Framework
java.lang.NullPointerException
at
org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCacheEntry.(SessionContextCacheEntry.java:40)
at
org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCache.getValueFromCache(SessionContextCache.java:95)
at
org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils.getSessionContextFromCache(FrameworkUtils.java:592)
at
org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.findPreviousAuthenticatedSession(DefaultRequestCoordinator.java:284)
at
org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.initializeFlow(DefaultRequestCoordinator.java:222)
at
org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.handle(DefaultRequestCoordinator.java:103)
at
org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doPost(CommonAuthenticationServlet.java:53)
at
org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doGet(CommonAuthenticationServlet.java:43)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
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:60)
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.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at
org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationHandler.invoke(WebappAuthenticationHandler.java:43)
at
org.wso2.carbon.event.receiver.core.internal.tenantmgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:48)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at

Re: [Dev] [UES][Dashboard Server] Dashboard anonymous view landing page

[Manuranga Perera]

let's consider tenanted URLs after M5.

On Tue, Oct 6, 2015 at 1:10 PM, Udara Rathnayake  wrote:

> Hi Ayesha,
>
> frankly I haven't tested any tenant scenarios with this implementation.
>
> *few points to consider*
> If user (not authenticated) browses the dashboard 
> https://:/portal/dashboards/
> this should render the anon view. Once user logged in we should render the
> default view. In this default view we DON'T need to provide a link to anon
> view. (this should be available during the design phase for developer to
> review)
>
> We don't need to think about user level customization within the anon
> view(since no real user exists at this time, no edit stuff in anon view).
>
> I discussed above with Sajith today.
>
> Regards,
> UdaraR
>
> On Tue, Oct 6, 2015 at 12:56 PM, Ayesha Dissanayaka 
> wrote:
>
>> Hi Udara/Manu,
>>
>> Have we considered multi-tenant scenarios while designing anonymous view
>> of dashboards.
>>
>> For instance what will be the dashboard view rendered for an user who has
>> logged into super tenant and trying to access a dashboard view URL of
>> another tenant domain.( ex. wso2.com).
>>
>> In that case should we still show the anonymous view of the dashboard or
>> default view?
>>
>> In my opinion we should show the anonymous view and disable the dashboard
>> edit options. WDYT?
>>
>> Thanks!
>> -Ayesha
>>
>>
>> On Fri, Oct 2, 2015 at 6:43 PM, Udara Rathnayake  wrote:
>>
>>> Thanks for the feedback lasantha and nipuna.
>>> I'm +1 to make the landing page anon if there are any anon views defined
>>> in other pages. Let's stick to that.
>>>
>>> On Fri, Oct 2, 2015 at 9:15 AM, Nipuna Chandradasa 
>>> wrote:
>>>
 Hi Udara,

 As Lasantha said that making the landing page an anon view should be
 mandatory if there are anon views available under the that landing page
 even the landing page doesn't have anon content to view.

 I think this is a good idea because it is not that great to have child
 pages which has anon view but the user cannot access the main view. At
 Least if there are no content to show under the landing page to a user (
 Which is not that great if it mandatory to make the landing page anon view)
 at least we can show a message saying which pages are anon views and have
 the anon content.

 Thanks.

 On Fri, Oct 2, 2015 at 8:46 AM, Lasantha Samarakoon  wrote:

> Hi Udara,
>
> Can't we show the actual landing page even though the anon view is not
> defined? So if the landing page doesn't have a anon view, then we can show
> some message with all other links to accessible pages (Same as what we 
> have
> in regular websites. Once you logged in you have more features, otherwise
> limited. But the home page is home page).
>
> In your first option, the problem is that if the developer couldn't
> define the anon view landing page, ultimately the dashboard is not
> accessible for any anon user unless he knows the direct url for a page.
> Then there's no point of introducing the anon view for such scenarios.
>
> In the second option, as you mentioned it actually breaks the concept
> behind a landing page. And know one can define what will be the actual
> landing page in such situation.
>
> Or else we can emphasis (or make it mandatory) the developer to define
> a anon view for the landing page in the designer if there are any anon
> pages for the dashboard.
>
>
> Regards,
>
>
> *Lasantha Samarakoon* | Software Engineer
> WSO2, Inc.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 (71) 214 1576
> Email:  lasant...@wso2.com
> Web:www.wso2.com
>
> lean . enterprise . middleware
>
> On Thu, Oct 1, 2015 at 8:10 PM, Udara Rathnayake 
> wrote:
>
>> Hi All,
>>
>> At the moment we have a landing page (which developer can select
>> while creating the dashboard) and this is the page end-user will 
>> initially
>> get once he/she browse the dashboard.
>>
>> So for the anonymous view of the dashboard, we are going to use the
>> same landing page's anon view(if exists) else user will be redirected to
>> the login page.
>> This approach will basically need developer to have a anon view
>> within the landing page if there are anon views for other pages.
>>
>> Otherwise we can go through existing pages and check existence of
>> anon views first and then render. This approach will deviate from the
>> landing page concept a bit.
>>
>> Any thoughts?
>>
>> Regards,
>> UdaraR
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 

Re: [Dev] SSO Authentication Error

[Hasintha Indrajee]

Seems like this issue occurs since the session key you send with your
second request  is no longer there in the server side and it gives this
error. Did you check this in the latest code base ? Can you confirm that
this is still there in the latest code base. If this is still there, please
open a jira for this issue.

On Tue, Oct 6, 2015 at 1:34 PM, Charitha Goonetilleke 
wrote:

> Hi All,
>
> I'm using carbon.identity.version 4.6.0-SNAPSHOT with IoT Server for
> testing. $subject occurred when I tried to login in to store/publisher. It
> further saying, "Something went wrong during the authentication process.
> Please try signing in again." Also in console printing a Null Pointer
> Exception[1].
>
> This is the way to reproduce the issue.
>
>- Extract a pack with carbon.identity.version 4.6.0-SNAPSHOT from zip
>archive.
>- Run pack and try to login as admin
>- Shutdown the pack and delete all files of pack.
>- Extract pack again from zip archive.
>- Run pack and try to login.
>
> Exception [1]
>
> [2015-10-06 12:38:23,902] ERROR
> {org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
> -  Exception in Authentication Framework
> java.lang.NullPointerException
> at
> org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCacheEntry.(SessionContextCacheEntry.java:40)
> at
> org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCache.getValueFromCache(SessionContextCache.java:95)
> at
> org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils.getSessionContextFromCache(FrameworkUtils.java:592)
> at
> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.findPreviousAuthenticatedSession(DefaultRequestCoordinator.java:284)
> at
> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.initializeFlow(DefaultRequestCoordinator.java:222)
> at
> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.handle(DefaultRequestCoordinator.java:103)
> at
> org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doPost(CommonAuthenticationServlet.java:53)
> at
> org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doGet(CommonAuthenticationServlet.java:43)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
> 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:60)
> 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.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
> at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
> at
> org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationHandler.invoke(WebappAuthenticationHandler.java:43)
> at
> org.wso2.carbon.event.receiver.core.internal.tenantmgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:48)
> at
> 

Re: [Dev] Web app class loading issue

[Charitha Goonetilleke]

Hi all,

Thanks for the suggestions, I removed *json_3.0.0.wso2v1* from
org.wso2.carbon.device.mgt.iot.common and modified code to comply with
*json_2.0.0.wso2v1*. Since org.wso2.carbon.event.simulator.core not used
any specific classes only provided by *json_3.0.0.wso2v1*, I was able to
solve the issue with only above modification.

Thanks,
/charithag

On Mon, Oct 5, 2015 at 5:56 PM, Madusanka Premaratne 
wrote:

> Hi Charitha,
> As per our findings, multiple versions from same bundle does not cause
> this issue. Usually this happens due to multiple jars which exports same
> package / incorrectly designed orbit bundles. Please find out those and
> exclude those.
>
> In APIM we have removed some jars to resolve the issue. Please refer [1]
>
> [1] -
> https://github.com/wso2/product-apim/blob/1.10.x/modules/distribution/product/src/main/assembly/bin.xml#L66
>
> Thanks,
> Madusanka
>
> On Mon, Oct 5, 2015 at 2:17 PM, Charitha Goonetilleke 
> wrote:
>
>> Hi Manoj,
>>
>> Thanks for the response. Actually, we can't eliminate one bundle version
>> from above since, both of them have their own dependencies. Actually we
>> tried to do that by removing *json_3.0.0.wso2v1.* But without that
>> bundle, org.wso2.carbon.event.simulator.core and
>> org.wso2.carbon.device.mgt.iot.common bundles throwing class not founds.
>> BTW, I can change json version dependency for 
>> org.wso2.carbon.device.mgt.iot.common
>> bundle. But still we need to change version for  
>> org.wso2.carbon.event.simulator.core
>> in that scenario.
>>
>> Anyway I think it would be better if we cloud upgrade
>> v2.0.0 dependent bundles to v3.0.0. WDYT?
>>
>> On Mon, Oct 5, 2015 at 1:34 PM, Manoj Kumara  wrote:
>>
>>> Hi Charitha,
>>>
>>> The reason here is that you have packed two versions of the same bundle.
>>> Please check the features they get added and remove unnecessary one.
>>>
>>> Regards,
>>> Manoj
>>>
>>> *Manoj Kumara*
>>> WSO2 Inc. *| **lean. enterprise. middleware.*
>>> *Mobile:* +94 713 448188
>>>
>>> On Mon, Oct 5, 2015 at 12:46 PM, Charitha Goonetilleke <
>>> charit...@wso2.com> wrote:
>>>
 Hi All,

 In IoT server we have the same issue, which occurred to Geeth
 initially. Thanks to RuwanA's tool, I figured out the conflicting bundles.

 Packages
 org.json
   Exported By
 json_2.0.0.wso2v1.jar at the location
 /repository/components/plugins/json_2.0.0.wso2v1.jar
 json_3.0.0.wso2v1.jar at the location
 /repository/components/plugins/json_3.0.0.wso2v1.jar

 When issue is occurred, tomcat imports org.json from
 json_3.0.0.wso2v1.jar as follows:

 osgi> p org.json
 org.json; version="2.0.0.wso2v1"<*json_2.0.0.wso2v1* [102]>
   oltu_1.0.0.wso2v2 [123] imports
   org.wso2.carbon.apimgt.impl_4.3.0.SNAPSHOT [264] imports
   org.wso2.carbon.apimgt.keymgt_4.3.0.SNAPSHOT [265] imports
   org.wso2.carbon.databridge.commons_4.4.7 [299] imports
   org.wso2.carbon.databridge.commons_5.0.2 [300] imports
   org.wso2.carbon.event.receiver.core_5.0.2 [379] imports
   org.wso2.carbon.event.simulator.admin_2.0.5 [382] imports
   org.wso2.carbon.registry.core_4.4.1 [534] imports
   org.wso2.carbon.social.core_2.3.9.SNAPSHOT [584] imports
   org.wso2.carbon.tenant.mgt.ui_4.5.0.m1 [603] imports
 org.json; version="3.0.0.wso2v1"<*json_3.0.0.wso2v1* [103]>
   org.wso2.carbon.device.mgt.iot.common_1.0.0.SNAPSHOT [315] imports
   org.wso2.carbon.event.simulator.core_2.0.5 [383] imports
   *tomcat_7.0.59.wso2v3* [692] imports

 If issue doesn't appear, tomcat imports org.json from json_2.0.0.wso2v1
 as follows:

 osgi> p org.json
 org.json; version="2.0.0.wso2v1"<*json_2.0.0.wso2v1* [102]>
   oltu_1.0.0.wso2v2 [123] imports
   org.wso2.carbon.apimgt.impl_4.3.0.SNAPSHOT [264] imports
   org.wso2.carbon.apimgt.keymgt_4.3.0.SNAPSHOT [265] imports
   org.wso2.carbon.databridge.commons_4.4.7 [299] imports
   org.wso2.carbon.databridge.commons_5.0.2 [300] imports
   org.wso2.carbon.event.receiver.core_5.0.2 [379] imports
   org.wso2.carbon.event.simulator.admin_2.0.5 [382] imports
   org.wso2.carbon.registry.core_4.4.1 [534] imports
   org.wso2.carbon.social.core_2.3.9.SNAPSHOT [584] imports
   org.wso2.carbon.tenant.mgt.ui_4.5.0.m1 [603] imports
   *tomcat_7.0.59.wso2v3* [692] imports
 org.json; version="3.0.0.wso2v1"<*json_3.0.0.wso2v1* [103]>
   org.wso2.carbon.device.mgt.iot.common_1.0.0.SNAPSHOT [315] imports
   org.wso2.carbon.event.simulator.core_2.0.5 [383] imports

 Is there any known workaround to fix this issue?


 On Wed, Aug 5, 2015 at 8:10 PM, Ruwan Abeykoon  wrote:

> Hi Madushanka,
> You can exclude the duplicate (unwanted) jar being bundled by your
> assembly bin.xml (or relevant file) in "maven-assembly-plugin"
>
> 

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Akila Ravihansa Perera]

Hi,

We are planning to create a single set of templates for samples using Jinja
templating language. Once it is done we can remove individual sample
artifacts.

Thanks.

On Wednesday, 7 October 2015, Imesh Gunaratne  wrote:

> On Wed, Oct 7, 2015 at 2:08 AM, Lasindu Charith  > wrote:
>
>> Hi Akila/Imesh,
>>
>> Any reason why we moved common samples (network partitions, autoscale
>> policies, deployment policies, application policies) inside each cartridge?
>>
>> If those artifacts are similar, what if we keep them in a common place?
>> (say inside common/samples/..).
>>
>
> +1 A good suggestion! Yes we could move above artifacts to common/samples
> folder. However when we are creating the cartridge distribution we may need
> to copy them to the cartridge/samples folder similar to common/plugins.
>
> Thanks
>
> On Wed, Oct 7, 2015 at 2:50 AM, Rajkumar Rajaratnam  > wrote:
>
>>
>>
>> On Wed, Oct 7, 2015 at 9:38 AM, Lasindu Charith > > wrote:
>>
>>> Hi Akila/Imesh,
>>>
>>> Any reason why we moved common samples (network partitions, autoscale
>>> policies, deployment policies, application policies) inside each cartridge?
>>>
>>> If those artifacts are similar, what if we keep them in a common place?
>>> (say inside common/samples/..). Once we introduce more cartridges, we will
>>> have to add them again and if there's a new change we'll have to change it
>>> everywhere(maintainability?)
>>>
>>
>> ​+1 to keep them in a common place. Why we are duplicating these common
>> artifacts across all the cartridges?
>> ​
>>
>>
>>>
>>> WDYT?
>>> If the priority/concern was regarding modularity, this approach is
>>> totally fine for me.
>>>
>>> Thanks,
>>>
>>> On Sun, Oct 4, 2015 at 1:33 PM, Imesh Gunaratne >> > wrote:
>>>
 It looks good Akila!

 On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera <
 raviha...@wso2.com 
 > wrote:

> Hi,
>
> I've restructured the repo considering what we discussed here. I've
> also added a distribution for VM related files.
>
> Final directory structure as follows;
>
> ├── common
> │   ├── configurator
> │   │   ├── live-test
> │   │   │   ├── src
> │   │   ├── src
> │   │   │   ├── assembly
> │   │   │   └── main
> │   ├── docker
> │   │   ├── base-image
> │   │   │   ├── packages
> │   │   │   └── scripts
> │   │   └── scripts
> │   ├── plugins
> │   └── vm
> │   ├── assembly
> │   ├── init-scripts
> │   │   ├── ec2
> │   │   ├── gce
> │   │   ├── openstack
> │   │   └── vcloud
> │   ├── puppet
> │   │   ├── manifests
> │   │   └── modules
> ├── wso2am
> │   ├── 1.9.0
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   └── template-modules
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> ├── wso2as
> │   ├── 5.2.1
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   ├── signups
> │   │   │   └── template-modules
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> ├── wso2esb
> │   ├── 4.8.1
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │  

[Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

[Ajith Vitharana]

Hi All,

I updated source view from the configuration mentioned in sample [1].

i) When I double check the message processor configs from source view, I
 noticed same config as the sample (expected behavior).


1000
false
DurableSubscriberEndpoint
*50*


ii) When I go to the "Message Processors" UI and edit the config (wrong
configurations)

http://ws.apache.org/ns/synapse;>
   1000
   1000
  * 4*
   true
   Disabled
   1


iii) According to the sample ,  I noticed  the message processor is
deactivating after the 4 attempts, that means the second config executing
at mediation.


iv) When I check the file in synapse-configs/default/message-processors
that is updated with my new configs.


http://ws.apache.org/ns/synapse;

class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
  name="*send_pending_message*"
  targetEndpoint="DurableSubscriberEndpoint"
  messageStore="pending_subscriptions">
   1000
   false
   DurableSubscriberEndpoint
  * 50*



[1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber

-- 
Ajith Vitharana.

WSO2 Inc. - http://wso2.com
Email  : aji...@wso2.com
Blog: http://vitharana.org
Mobile : +1-812-360-5335
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Imesh Gunaratne]

On Wed, Oct 7, 2015 at 2:08 AM, Lasindu Charith  wrote:

> Hi Akila/Imesh,
>
> Any reason why we moved common samples (network partitions, autoscale
> policies, deployment policies, application policies) inside each cartridge?
>
> If those artifacts are similar, what if we keep them in a common place?
> (say inside common/samples/..).
>

+1 A good suggestion! Yes we could move above artifacts to common/samples
folder. However when we are creating the cartridge distribution we may need
to copy them to the cartridge/samples folder similar to common/plugins.

Thanks

On Wed, Oct 7, 2015 at 2:50 AM, Rajkumar Rajaratnam 
wrote:

>
>
> On Wed, Oct 7, 2015 at 9:38 AM, Lasindu Charith  wrote:
>
>> Hi Akila/Imesh,
>>
>> Any reason why we moved common samples (network partitions, autoscale
>> policies, deployment policies, application policies) inside each cartridge?
>>
>> If those artifacts are similar, what if we keep them in a common place?
>> (say inside common/samples/..). Once we introduce more cartridges, we will
>> have to add them again and if there's a new change we'll have to change it
>> everywhere(maintainability?)
>>
>
> ​+1 to keep them in a common place. Why we are duplicating these common
> artifacts across all the cartridges?
> ​
>
>
>>
>> WDYT?
>> If the priority/concern was regarding modularity, this approach is
>> totally fine for me.
>>
>> Thanks,
>>
>> On Sun, Oct 4, 2015 at 1:33 PM, Imesh Gunaratne  wrote:
>>
>>> It looks good Akila!
>>>
>>> On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi,

 I've restructured the repo considering what we discussed here. I've
 also added a distribution for VM related files.

 Final directory structure as follows;

 ├── common
 │   ├── configurator
 │   │   ├── live-test
 │   │   │   ├── src
 │   │   ├── src
 │   │   │   ├── assembly
 │   │   │   └── main
 │   ├── docker
 │   │   ├── base-image
 │   │   │   ├── packages
 │   │   │   └── scripts
 │   │   └── scripts
 │   ├── plugins
 │   └── vm
 │   ├── assembly
 │   ├── init-scripts
 │   │   ├── ec2
 │   │   ├── gce
 │   │   ├── openstack
 │   │   └── vcloud
 │   ├── puppet
 │   │   ├── manifests
 │   │   └── modules
 ├── wso2am
 │   ├── 1.9.0
 │   │   ├── assembly
 │   │   ├── docker
 │   │   │   ├── packages
 │   │   │   ├── plugins
 │   │   │   └── scripts
 │   │   ├── plugins
 │   │   ├── samples
 │   │   │   ├── application-policies
 │   │   │   ├── applications
 │   │   │   ├── autoscaling-policies
 │   │   │   ├── cartridge-groups
 │   │   │   ├── cartridges
 │   │   │   ├── deployment-policies
 │   │   │   ├── kubernetes-clusters
 │   │   │   ├── network-partitions
 │   │   │   └── template-modules
 │   │   └── template-module
 │   │   ├── files
 │   │   ├── src
 │   │   └── templates
 ├── wso2as
 │   ├── 5.2.1
 │   │   ├── assembly
 │   │   ├── docker
 │   │   │   ├── packages
 │   │   │   ├── plugins
 │   │   │   └── scripts
 │   │   ├── plugins
 │   │   ├── samples
 │   │   │   ├── application-policies
 │   │   │   ├── applications
 │   │   │   ├── autoscaling-policies
 │   │   │   ├── cartridge-groups
 │   │   │   ├── cartridges
 │   │   │   ├── deployment-policies
 │   │   │   ├── kubernetes-clusters
 │   │   │   ├── network-partitions
 │   │   │   ├── signups
 │   │   │   └── template-modules
 │   │   └── template-module
 │   │   ├── files
 │   │   ├── src
 │   │   └── templates
 ├── wso2esb
 │   ├── 4.8.1
 │   │   ├── assembly
 │   │   ├── docker
 │   │   │   ├── packages
 │   │   │   ├── plugins
 │   │   │   └── scripts
 │   │   ├── plugins
 │   │   ├── samples
 │   │   │   ├── application-policies
 │   │   │   ├── applications
 │   │   │   ├── autoscaling-policies
 │   │   │   ├── cartridge-groups
 │   │   │   ├── cartridges
 │   │   │   ├── deployment-policies
 │   │   │   ├── kubernetes-clusters
 │   │   │   ├── network-partitions
 │   │   │   ├── signups
 │   │   │   └── template-modules
 │   │   │   ├── archive-tmp
 │   │   │   └── maven-shared-archive-resources
 │   │   └── template-module
 │   │   ├── files
 │   │   ├── src
 │   │   └── templates
 └── wso2is
 ├── 5.0.0
 │   ├── assembly
 │   ├── docker
 │   │   ├── packages
 │   │   ├── plugins
 │   │   └── scripts
 │   ├── plugins
 │   ├── samples
 │   │   ├── application-policies
 │   │   ├── applications
 │   │   ├── autoscaling-policies
 │   │   ├── 

[Dev] [AF] dockersupport-1.1 branch building issue with workflow extensions changes

[Lahiru Manohara]

Hi Anuruddha,

According to this full request[1]. The stage parameter was removed from
the initializeCloudManager method in
the AppFactoryTenantInfraStructureInitializerService class. In
Tenantcreation BPEL and default workflow is calling initializeCloudManager
for three stages (development, testing and production). But how could i do
this from updated code?

[1]. https://github.com/wso2/product-af/pull/526/files

Thanks.
-- 
Best regards,

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

Re: [Dev] SSO Authentication Error

[Darshana Gunawardana]

On Tue, Oct 6, 2015 at 2:21 PM, Hasintha Indrajee  wrote:

> Seems like this issue occurs since the session key you send with your
> second request  is no longer there in the server side and it gives this
> error. Did you check this in the latest code base ? Can you confirm that
> this is still there in the latest code base.
>

Yes this is fixed with :
https://github.com/wso2/carbon-identity/commit/1d9bb6763c740c0e39b741f30a0d11d88c37bebc


> If this is still there, please open a jira for this issue.
>

+1 Create a L1 if you see any NPEs on this flow.

Thanks,
Darshana

>
> On Tue, Oct 6, 2015 at 1:34 PM, Charitha Goonetilleke 
> wrote:
>
>> Hi All,
>>
>> I'm using carbon.identity.version 4.6.0-SNAPSHOT with IoT Server for
>> testing. $subject occurred when I tried to login in to store/publisher. It
>> further saying, "Something went wrong during the authentication process.
>> Please try signing in again." Also in console printing a Null Pointer
>> Exception[1].
>>
>> This is the way to reproduce the issue.
>>
>>- Extract a pack with carbon.identity.version 4.6.0-SNAPSHOT from zip
>>archive.
>>- Run pack and try to login as admin
>>- Shutdown the pack and delete all files of pack.
>>- Extract pack again from zip archive.
>>- Run pack and try to login.
>>
>> Exception [1]
>>
>> [2015-10-06 12:38:23,902] ERROR
>> {org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
>> -  Exception in Authentication Framework
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCacheEntry.(SessionContextCacheEntry.java:40)
>> at
>> org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCache.getValueFromCache(SessionContextCache.java:95)
>> at
>> org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils.getSessionContextFromCache(FrameworkUtils.java:592)
>> at
>> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.findPreviousAuthenticatedSession(DefaultRequestCoordinator.java:284)
>> at
>> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.initializeFlow(DefaultRequestCoordinator.java:222)
>> at
>> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.handle(DefaultRequestCoordinator.java:103)
>> at
>> org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doPost(CommonAuthenticationServlet.java:53)
>> at
>> org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doGet(CommonAuthenticationServlet.java:43)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
>> 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:60)
>> 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.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>> at
>> 

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Rukshan Premathunga]

Hi Isuru,

You can filter out result on more than one attribute using boolean
operators [1].

ex:
 *"query" : "timestamp : [1243214324532 TO 4654365223] AND "processId"
: 10035 *

[1] https://lucene.apache.org/core/2_9_4/queryparsersyntax.html#Boolean
operators


On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe  wrote:

> Hi,
>
> I need to perform COUNT() operation through DAS REST API (an example is
> shown below). I tried to pass COUNT() from a luciene object. But it didn't
> work for me. Does DAS support COUNT operation through luciene ???  if not
> how can I enable it in DAS side???
>
> eg: *SELECT startedTime, processDefinitionId, COUNT(processInstanceId) AS
> processInstanceCount FROM PROCESS_USAGE_SUMMARY GROUP BY startedTime,
> processDefinitionId;*
>
> In addition to that, is that possible to pass more than one parameter to
> the query part in luicene object, because most graphs have to provide a
> secondary filter to get the result. As an example I need to filter the
> result from date range as well as process id.  I need something like this.
>
>  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
> 10035" *
>
> Any help will be appreciated.
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is there any method which can checks the resource exists or not in registry

[Kasun Bandara]

Hi Rajeenthini,

You can invoke the *boolean resourceExists(String resorcePath)* method
through the Registry class comes with registry core. Returns true if the
resource exists in the specified path & returns false if it's not reside in
the path.

Thanks and Regards.


On Tue, Oct 6, 2015 at 3:42 PM, Kasun Bandara  wrote:

> Hi Rajeenthini,
>
> You can invoke the *boolean resourceExists(String resorcePath)* method
> through the Registry class comes with registry core. Returns true if the
> resource exists in the specified path & returns false if it's not reside in
> the path.
>
> Thanks and Regards.
>
>
> On Tue, Oct 6, 2015 at 12:35 PM, Rajeenthini Satkunam <
> rajeenth...@wso2.com> wrote:
>
>> Hi all,
>>
>> I am writing UI test cases for UES/Dashboard Server(DS).I have tried to
>> write a test class for adding and deleting dashboard for the Dashboard
>> Server.Here I need to check the resource is existing or not at the
>> registry.You can have a look for the class[1] I have wrote for adding and
>> deleting dashboard.
>> [1] -
>> https://github.com/rajeenthini/product-ues/commit/e642d50edf08cc21d2b0a2b21463e4b3aadc587a
>>
>> BTW I have modified my code in some ways .Those are I have included below
>> - Deleted deleteResource method from here
>> resourceAdminServiceClient.deleteResource(resourcePath);
>>
>> @AfterClass(alwaysRun = true)
>> public void tearDown() throws MalformedURLException, 
>> XPathExpressionException, RemoteException, 
>> ResourceAdminServiceExceptionException {
>> try{
>> UESUIIntegrationTest.logout(getDriver(), getBaseUrl(), 
>> getCurrentUsername());
>> }finally {
>> getDriver().quit();
>> }
>> }
>>
>> - Added some code segment to the method deleteDashboard
>>
>> @Test(groups = "wso2.ues.dashboard", description = "Deleting added 
>> dashboard", dependsOnMethods = "testAddDashboardNew")
>> public void testDeleteDashboardNew() throws MalformedURLException, 
>> XPathExpressionException, RemoteException, 
>> ResourceAdminServiceExceptionException {
>> webElement = getDriver().findElement(By.id(dashboardTitle));
>> webElement.findElement(By.cssSelector("i.fw-delete")).click();
>> getDriver().findElement(By.cssSelector("span.ladda-label")).click();
>> assertFalse(getDriver().isElementPresent(By.id(dashboardTitle)), "Error 
>> occurred while deleting dashboard" + dashboardTitle);
>> ResourceData[] resourceData = 
>> resourceAdminServiceClient.getResourceData(resourcePath);
>> assertTrue(resourceData.length == 0,"Registry resource could not be 
>> deleted due to some errors");
>> }
>>
>> Now it's giving me exception when there is no such registry resource
>> after dashboard was deleted by UI testcase.
>>
>> org.apache.axis2.AxisFault: Resource does not exist at path 
>> /_system/config/ues/dashboards/sampledashboard1
>>
>> So can anyone give some suggestions on $subject? Thanks in advance.
>> --
>>
>> *Thank You.*
>>
>> *Rajeenthini Satkunam*
>>
>> *Associate Software Engineer | WSO2*
>>
>>
>> *E:rajeenth...@wso2.com *
>>
>> *M :+94770832823 <%2B94770832823>   *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kasun Bandara
> *Software Engineer*
> Mobile : +94 (0) 718 338 360
> <%2B94%20%280%29%20773%20451194>
> kas...@wso2.com 
>



-- 
Kasun Bandara
*Software Engineer*
Mobile : +94 (0) 718 338 360
<%2B94%20%280%29%20773%20451194>
kas...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] SingelSignOn support in DAS Analytics Dashboard

[Dunith Dhanushka]

Hi Thanuja,

At the moment, DAS Analytics Dashboard doesn't provide SSO facility.

But UES 2.0 M3 was released last week with SSO support. We'll upgrade the
carbon-dashboards version to 1.0.4 in DAS to include UES 2.0 M3 features.

Will update the thread once the upgrade is done.

Regards,
Dunith


On Tue, Oct 6, 2015 at 10:56 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi All,
>
> I'm currently integrating Private PaaS metering dashboard implemented
> using DAS analytics dashboard in Private PaaS UI. In Private PaaS
> applications' topology view, I've added metering dashboard navigation url,
> and when I'm navigating to dashboard, there we again need to log in to see
> the dashboard.
>
> I have already discussed about this with Sinthuja. She mentioned following
> that currently in DAS carbon console UI, there is a navigation to analytics
> dashboard. But there also user has to log in again.
>
> Does DAS analytics dashboard support single-sign-on currently?
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
Regards,

Dunith Dhanushka,
Senior Software Engineer
WSO2 Inc,

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

Re: [Dev] ESB 4.9.0 - NPE occurs in tenant APIs with same context and different versions

[Chanaka Fernando]

Hi Nuwan,

I had a look into the code which is causing this NPE. According to the way
it is written, this NPE can be occurred. I have tried to replicate what
NuwanD has mentioned but couldn't reproduce the same NPE. This can be
occurred due to synapse configuration issue.

@NuwanD: Can you share the configurations which you have used to reproduce
this issue?


Thanks,
Chanaka

On Thu, Oct 1, 2015 at 10:41 AM, Chanaka Fernando  wrote:

> Hi All,
>
> We are looking into this issue.
>
> On Thu, Oct 1, 2015 at 10:37 AM, Sandapa Handakumbura 
> wrote:
>
>> Hi Nuwan,
>>
>> I faced a similar issue during ESB 4.9.0 release testing. First request
>> for proxy services (after tenant unloading/ server restart) failed in
>> tenant mode [1]. Unfortunately ESB team could not reproduce it and I could
>> not identify the exact steps to reproduce it either.
>>
>> Hope the team will look in to this since you have identified steps to
>> reproduce the issue.
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4142
>>
>> Thanks,
>> Sandapa
>>
>>
>> On Thu, Oct 1, 2015 at 4:47 AM, Nuwan Dias  wrote:
>>
>>> Hi,
>>>
>>> I have a scenario on the ESB where I have created two APIs with the same
>>> context in the tenant space. The first API doesn't have a version and the
>>> second API has a version. The first API receives the request and forwards
>>> to the second API. See illustration below.
>>>
>>> Client (/twitter) --> Twitter_API (/twitter/1.0.0) --> Twitter_API_v1.0.0
>>>
>>> This scenario however causes the following [1] NPE on the first request
>>> that's sent to the server. The subsequent requests pass until a server
>>> restart happens.
>>>
>>> I tried logging into the management console of the ESB using tenant
>>> credentials to check whether it was related to tenant loading. The first
>>> request still failed with the same error. Any idea why this is happening?
>>> This issue first occurred to me in API Manager after migrating to the
>>> latest released version of Synapse. And is causing test failures in the
>>> product. It worked fine in the older versions of Synapse (2.1.2- version
>>> range).
>>>
>>> [1]
>>>
>>> [2015-10-01 04:41:39,519] ERROR - PassThroughHttpSender Failed to submit
>>> the response
>>> java.lang.NullPointerException
>>> at
>>> org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)
>>> at
>>> org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)
>>> at
>>> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at
>>> org.wso2.carbon.core.multitenancy.transports.TenantTransportSender.invoke(TenantTransportSender.java:231)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at
>>> org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
>>> at
>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
>>> at
>>> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>>> at
>>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>>> at org.apache.synapse.rest.Resource.process(Resource.java:297)
>>> at org.apache.synapse.rest.API.process(API.java:335)
>>> at
>>> org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:97)
>>> at
>>> org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:52)
>>> at
>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:266)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processResponse(MultitenantMessageReceiver.java:166)
>>> at
>>> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:82)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>> [2015-10-01 04:41:39,521] ERROR - Axis2Sender
>>> 

Re: [Dev] ESB 4.9.0 - NPE occurs in tenant APIs with same context and different versions

[Nuwan Dias]

Attaching the two APIs I used for testing. To reproduce this issue, create
a tenant with the domain as 'wso2.com' and deploy these two APIs within the
tenant space and restart the server.

Then access the API without the version using the following URL.

http://localhost:8280/t/wso2.com/responseapi/weather?q=London

Thanks,
NuwanD.

On Tue, Oct 6, 2015 at 2:53 PM, Chanaka Fernando  wrote:

> Hi Nuwan,
>
> I had a look into the code which is causing this NPE. According to the way
> it is written, this NPE can be occurred. I have tried to replicate what
> NuwanD has mentioned but couldn't reproduce the same NPE. This can be
> occurred due to synapse configuration issue.
>
> @NuwanD: Can you share the configurations which you have used to reproduce
> this issue?
>
>
> Thanks,
> Chanaka
>
> On Thu, Oct 1, 2015 at 10:41 AM, Chanaka Fernando 
> wrote:
>
>> Hi All,
>>
>> We are looking into this issue.
>>
>> On Thu, Oct 1, 2015 at 10:37 AM, Sandapa Handakumbura 
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> I faced a similar issue during ESB 4.9.0 release testing. First request
>>> for proxy services (after tenant unloading/ server restart) failed in
>>> tenant mode [1]. Unfortunately ESB team could not reproduce it and I could
>>> not identify the exact steps to reproduce it either.
>>>
>>> Hope the team will look in to this since you have identified steps to
>>> reproduce the issue.
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-4142
>>>
>>> Thanks,
>>> Sandapa
>>>
>>>
>>> On Thu, Oct 1, 2015 at 4:47 AM, Nuwan Dias  wrote:
>>>
 Hi,

 I have a scenario on the ESB where I have created two APIs with the
 same context in the tenant space. The first API doesn't have a version and
 the second API has a version. The first API receives the request and
 forwards to the second API. See illustration below.

 Client (/twitter) --> Twitter_API (/twitter/1.0.0) -->
 Twitter_API_v1.0.0

 This scenario however causes the following [1] NPE on the first request
 that's sent to the server. The subsequent requests pass until a server
 restart happens.

 I tried logging into the management console of the ESB using tenant
 credentials to check whether it was related to tenant loading. The first
 request still failed with the same error. Any idea why this is happening?
 This issue first occurred to me in API Manager after migrating to the
 latest released version of Synapse. And is causing test failures in the
 product. It worked fine in the older versions of Synapse (2.1.2- version
 range).

 [1]

 [2015-10-01 04:41:39,519] ERROR - PassThroughHttpSender Failed to
 submit the response
 java.lang.NullPointerException
 at
 org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)
 at
 org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)
 at
 org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.wso2.carbon.core.multitenancy.transports.TenantTransportSender.invoke(TenantTransportSender.java:231)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
 at
 org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
 at
 org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
 at
 org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
 at org.apache.synapse.rest.Resource.process(Resource.java:297)
 at org.apache.synapse.rest.API.process(API.java:335)
 at
 org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:97)
 at
 org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:52)
 at
 org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:266)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
 at
 org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processResponse(MultitenantMessageReceiver.java:166)
 at
 org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:82)
 at 

[Dev] [DEV][GREG] Unable to import registry resources from a dump file

[Nuwan Pallewela]

Hi Devs,

I'm trying to test importing registry files using a dump file. I have
created a dump file using following command [1].
[1] sh checkin-client.sh co https://localhost:9443/registry/ -u admin -p
admin -f 10-06-2015_test2.dump

Dump file is successfully created in the bin folder.

Then when I try to import it to another Greg server using [2] command, it
gives following error[3].
[2] sh checkin-client.sh ci https://localhost:9445/registry/ -u admin -p
admin -f 10-06-2015_test2.dump
[3]
Error in restoring the path. Make sure the registry is up and running Or
the username, password is correct! and check the user have the WRITE
permission to the path.
path: /
registry url: https://localhost:9443/registry
username: admin

What would be causing this?

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

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

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][GREG] Unable to import registry resources from a dump file

[Nuwan Pallewela]

Hi,

After i tried to checkout the dump file , following error is show in
command line when i try to browse registry.

[2015-10-06 15:20:27,354]  WARN
{org.wso2.carbon.registry.core.caching.CacheBackedRegistry} -  User admin
is not authorized to read the resource /.

Thanks,
Nuwan

On Tue, Oct 6, 2015 at 3:16 PM, Nuwan Pallewela  wrote:

> Hi Devs,
>
> I'm trying to test importing registry files using a dump file. I have
> created a dump file using following command [1].
> [1] sh checkin-client.sh co https://localhost:9443/registry/ -u admin -p
> admin -f 10-06-2015_test2.dump
>
> Dump file is successfully created in the bin folder.
>
> Then when I try to import it to another Greg server using [2] command, it
> gives following error[3].
> [2] sh checkin-client.sh ci https://localhost:9445/registry/ -u admin -p
> admin -f 10-06-2015_test2.dump
> [3]
> Error in restoring the path. Make sure the registry is up and running Or
> the username, password is correct! and check the user have the WRITE
> permission to the path.
> path: /
> registry url: https://localhost:9443/registry
> username: admin
>
> What would be causing this?
>
> Thanks,
> Nuwan
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>*
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

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

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC

[Susinda Perera]

Hi All
I have tested following areas

AppServer projects (JAX-RS/JAX-WS/Webapp/Axis2Service/Client generation)
creation - in both linux and windows.
AppServer project creation and deployment - in linux.
Registry perspective and registry project operations
(checkout/add-new/commit) in windows and linux.
Referring registry artifacts from a ESBproject.
Creating ESB artifacts, Creating car files, adding connectors inside car
files.
API manager perspective
Did not find blocking issues, therefore +1

Thanks
Susinda


On Mon, Oct 5, 2015 at 3:43 PM, Kavith Lokuhewage  wrote:

> Hi All,
>
> On Mon, Oct 5, 2015 at 12:30 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi All,
>>
>> This is the release candidate of WSO2 Developer Studio 3.8.0.
>>
>> This release fixes following issues:
>> https://wso2.org/jira/browse/TOOLS-3218?filter=12427
>>
>>
> Please ignore above link. Instead, use following link to view issues fixed
> in this version.
> https://wso2.org/jira/issues/?filter=12431
>
> Thanks,
>
> Please download, test and vote. Vote will be open for 72 hours or as
>> needed.
>>
>> *Sources, binary distribution and pre-installed eclipse distributions:*
>> *http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC/
>> *
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/developer-studio/tree/v3.8.0-RC
>>
>> *[+**]* Stable - go ahead and release
>> *[-]*  Broken - do not release (explain why)
>>
>> Thanks,
>> --
>> *Kavith Lokuhewage*
>> Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +9477-9-145-123 | +9471-455-6-401
>> Linkedin 
>> Twitter 
>>
>
>
>
> --
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin 
> Twitter 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC

[Nuwan Pallewela]

Hi All,

I have tested following scenarios.

   - JAX-WS service classes with App Server.
   - JAX-RS service classes with App Server.
   - Created ESB artifacts ,car files and with connectors.
   - Tested most of the security scenarios with proxy services.
   - Tested MMM project creation and building.

I found two main blocking  issues.

[1] Rename refactoring operation on ESB artifacts doesn't update pom file
of the capp and artifact.xml file correctly in some cases.

[2] Validation in source view of ESB artifacts not showing error line
correctly in template and REST-api files.(
https://wso2.org/jira/browse/TOOLS-3225 )

therefore -1

Thanks,

Nuwan

On Mon, Oct 5, 2015 at 3:43 PM, Kavith Lokuhewage  wrote:

> Hi All,
>
> On Mon, Oct 5, 2015 at 12:30 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi All,
>>
>> This is the release candidate of WSO2 Developer Studio 3.8.0.
>>
>> This release fixes following issues:
>> https://wso2.org/jira/browse/TOOLS-3218?filter=12427
>>
>>
> Please ignore above link. Instead, use following link to view issues fixed
> in this version.
> https://wso2.org/jira/issues/?filter=12431
>
> Thanks,
>
> Please download, test and vote. Vote will be open for 72 hours or as
>> needed.
>>
>> *Sources, binary distribution and pre-installed eclipse distributions:*
>> *http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC/
>> *
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/developer-studio/tree/v3.8.0-RC
>>
>> *[+**]* Stable - go ahead and release
>> *[-]*  Broken - do not release (explain why)
>>
>> Thanks,
>> --
>> *Kavith Lokuhewage*
>> Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +9477-9-145-123 | +9471-455-6-401
>> Linkedin 
>> Twitter 
>>
>
>
>
> --
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin 
> Twitter 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

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

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC

[Kavith Lokuhewage]

Hi,

Please refer to my inline comment.

On Tue, Oct 6, 2015 at 3:48 PM, Nuwan Pallewela  wrote:

> Hi All,
>
> I have tested following scenarios.
>
>- JAX-WS service classes with App Server.
>- JAX-RS service classes with App Server.
>- Created ESB artifacts ,car files and with connectors.
>- Tested most of the security scenarios with proxy services.
>- Tested MMM project creation and building.
>
> I found two main blocking  issues.
>
> [1] Rename refactoring operation on ESB artifacts doesn't update pom file
> of the capp and artifact.xml file correctly in some cases.
>
This is reported in below jira.
https://wso2.org/jira/browse/TOOLS-3231

Thanks

> [2] Validation in source view of ESB artifacts not showing error line
> correctly in template and REST-api files.(
> https://wso2.org/jira/browse/TOOLS-3225 )
>
> therefore -1
>
> Thanks,
>
> Nuwan
>
> On Mon, Oct 5, 2015 at 3:43 PM, Kavith Lokuhewage  wrote:
>
>> Hi All,
>>
>> On Mon, Oct 5, 2015 at 12:30 PM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi All,
>>>
>>> This is the release candidate of WSO2 Developer Studio 3.8.0.
>>>
>>> This release fixes following issues:
>>> https://wso2.org/jira/browse/TOOLS-3218?filter=12427
>>>
>>>
>> Please ignore above link. Instead, use following link to view issues
>> fixed in this version.
>> https://wso2.org/jira/issues/?filter=12431
>>
>> Thanks,
>>
>> Please download, test and vote. Vote will be open for 72 hours or as
>>> needed.
>>>
>>> *Sources, binary distribution and pre-installed eclipse distributions:*
>>> *http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC/
>>> *
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/developer-studio/tree/v3.8.0-RC
>>>
>>> *[+**]* Stable - go ahead and release
>>> *[-]*  Broken - do not release (explain why)
>>>
>>> Thanks,
>>> --
>>> *Kavith Lokuhewage*
>>> Software Engineer
>>> WSO2 Inc. - http://wso2.com
>>> lean . enterprise . middleware
>>> Mobile - +9477-9-145-123 | +9471-455-6-401
>>> Linkedin 
>>> Twitter 
>>>
>>
>>
>>
>> --
>> *Kavith Lokuhewage*
>> Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +9477-9-145-123 | +9471-455-6-401
>> Linkedin 
>> Twitter 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>*
>
>
>


-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Anjana Fernando]

Hi Isuru,

You can use the REST APIs search count [1] operation.

[1]
https://docs.wso2.com/display/DAS300/Retrieving+the+Number+of+Records+Matching+the+Given+Search+Query+via+REST+API

Cheers,
Anjana.

On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe  wrote:

> Hi,
>
> I need to perform COUNT() operation through DAS REST API (an example is
> shown below). I tried to pass COUNT() from a luciene object. But it didn't
> work for me. Does DAS support COUNT operation through luciene ???  if not
> how can I enable it in DAS side???
>
> eg: *SELECT startedTime, processDefinitionId, COUNT(processInstanceId) AS
> processInstanceCount FROM PROCESS_USAGE_SUMMARY GROUP BY startedTime,
> processDefinitionId;*
>
> In addition to that, is that possible to pass more than one parameter to
> the query part in luicene object, because most graphs have to provide a
> secondary filter to get the result. As an example I need to filter the
> result from date range as well as process id.  I need something like this.
>
>  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
> 10035" *
>
> Any help will be appreciated.
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC

[Rajeevan Vimalanathan]

Hi,

Please find my comments inline,

On Tue, Oct 6, 2015 at 3:52 PM, Kavith Lokuhewage  wrote:

> Hi,
>
> Please refer to my inline comment.
>
> On Tue, Oct 6, 2015 at 3:48 PM, Nuwan Pallewela  wrote:
>
>> Hi All,
>>
>> I have tested following scenarios.
>>
>>- JAX-WS service classes with App Server.
>>- JAX-RS service classes with App Server.
>>- Created ESB artifacts ,car files and with connectors.
>>- Tested most of the security scenarios with proxy services.
>>- Tested MMM project creation and building.
>>
>> I found two main blocking  issues.
>>
>> [1] Rename refactoring operation on ESB artifacts doesn't update pom file
>> of the capp and artifact.xml file correctly in some cases.
>>
> This is reported in below jira.
> https://wso2.org/jira/browse/TOOLS-3231
>
> Thanks
>
>> [2] Validation in source view of ESB artifacts not showing error line
>> correctly in template and REST-api files.(
>> https://wso2.org/jira/browse/TOOLS-3225 )
>>
> This is fixed now!

> therefore -1
>>
>> Thanks,
>>
>> Nuwan
>>
>


-- 
Vimalanathan Rajeevan
Software Engineer,
WSO2, Inc. *http://wso2.com* 
Lean.Enterprise.Middleware

Mobile:
*+94 773090875*
LinkedIn:
*https://www.linkedin.com/in/RajeevanVimalanathan
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS] How to enable the SVN in IS cluster to sync BPEL and HT artifacts

[Aparna Karunarathna]

Hi Johann and IS team,

How to enable the SVN in IS cluster to sync BPEL and HT artifacts among
nodes?

In Worker/Manager cluster setup, manager node is used to commit artifacts,
but for IS cluster doesn't have manager node, both nodes are behave as
manager nodes. Basically this issue is getting when we configuring
workflows by pointing to the embedded BPS server from manager node.

Furthermore, with external BPS server we don't get this kind problem.

Please clarify.

-- 
*Regards,*

*Aparna Karunarathna.*


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

Re: [Dev] [AF] dockersupport-1.1 branch building issue with workflow extensions changes

[Anuruddha Premalal]

Hi Lahiru,

Tenant creation was done by (+ punnadi). Since we had a single stratos,
didn't want stage parameter to create tenant in separate registries,
however once we move tenant creation to greg's you might have to bring the
stage parameter back or you could use multiple subscriber on the tenant
creation message.

Regards,
Anuruddha.

On Tue, Oct 6, 2015 at 2:49 PM, Lahiru Manohara  wrote:

> Hi Anuruddha,
>
> According to this full request[1]. The stage parameter was removed from
> the initializeCloudManager method in
> the AppFactoryTenantInfraStructureInitializerService class. In
> Tenantcreation BPEL and default workflow is calling initializeCloudManager
> for three stages (development, testing and production). But how could i do
> this from updated code?
>
> [1]. https://github.com/wso2/product-af/pull/526/files
>
> Thanks.
> --
> Best regards,
>
> *Lahiru Manohara*
> *Software Engineer*
> Mobile: +94716561576
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



-- 
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94717213122
Web site : www.anuruddha.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] How to enable the SVN in IS cluster to sync BPEL and HT artifacts

[Nandika Jayawardana]

In the cluster scenario, its better to point to an external BPS cluster.

Regards
Nandika

On Tue, Oct 6, 2015 at 4:06 PM, Aparna Karunarathna  wrote:

> Hi Johann and IS team,
>
> How to enable the SVN in IS cluster to sync BPEL and HT artifacts among
> nodes?
>
> In Worker/Manager cluster setup, manager node is used to commit artifacts,
> but for IS cluster doesn't have manager node, both nodes are behave as
> manager nodes. Basically this issue is getting when we configuring
> workflows by pointing to the embedded BPS server from manager node.
>
> Furthermore, with external BPS server we don't get this kind problem.
>
> Please clarify.
>
> --
> *Regards,*
>
> *Aparna Karunarathna.*
>
>
> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is there any method which can checks the resource exists or not in registry

[Rajith Roshan]

Hi Rajeenthini,

You can get the instance of registry as below and check if the resource
exists.

RegistryProviderUtil provider = new RegistryProviderUtil();
WSRegistryServiceClient registry = provider.getWSRegistry(automationContext);

if(registry.resourceExists(path))


Thanks,

Rajith


On Tue, Oct 6, 2015 at 3:43 PM, Kasun Bandara  wrote:

> Hi Rajeenthini,
>
> You can invoke the *boolean resourceExists(String resorcePath)* method
> through the Registry class comes with registry core. Returns true if the
> resource exists in the specified path & returns false if it's not reside in
> the path.
>
> Thanks and Regards.
>
>
> On Tue, Oct 6, 2015 at 3:42 PM, Kasun Bandara  wrote:
>
>> Hi Rajeenthini,
>>
>> You can invoke the *boolean resourceExists(String resorcePath)* method
>> through the Registry class comes with registry core. Returns true if the
>> resource exists in the specified path & returns false if it's not reside in
>> the path.
>>
>> Thanks and Regards.
>>
>>
>> On Tue, Oct 6, 2015 at 12:35 PM, Rajeenthini Satkunam <
>> rajeenth...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I am writing UI test cases for UES/Dashboard Server(DS).I have tried to
>>> write a test class for adding and deleting dashboard for the Dashboard
>>> Server.Here I need to check the resource is existing or not at the
>>> registry.You can have a look for the class[1] I have wrote for adding and
>>> deleting dashboard.
>>> [1] -
>>> https://github.com/rajeenthini/product-ues/commit/e642d50edf08cc21d2b0a2b21463e4b3aadc587a
>>>
>>> BTW I have modified my code in some ways .Those are I have included below
>>> - Deleted deleteResource method from here
>>> resourceAdminServiceClient.deleteResource(resourcePath);
>>>
>>> @AfterClass(alwaysRun = true)
>>> public void tearDown() throws MalformedURLException, 
>>> XPathExpressionException, RemoteException, 
>>> ResourceAdminServiceExceptionException {
>>> try{
>>> UESUIIntegrationTest.logout(getDriver(), getBaseUrl(), 
>>> getCurrentUsername());
>>> }finally {
>>> getDriver().quit();
>>> }
>>> }
>>>
>>> - Added some code segment to the method deleteDashboard
>>>
>>> @Test(groups = "wso2.ues.dashboard", description = "Deleting added 
>>> dashboard", dependsOnMethods = "testAddDashboardNew")
>>> public void testDeleteDashboardNew() throws MalformedURLException, 
>>> XPathExpressionException, RemoteException, 
>>> ResourceAdminServiceExceptionException {
>>> webElement = getDriver().findElement(By.id(dashboardTitle));
>>> webElement.findElement(By.cssSelector("i.fw-delete")).click();
>>> getDriver().findElement(By.cssSelector("span.ladda-label")).click();
>>> assertFalse(getDriver().isElementPresent(By.id(dashboardTitle)), "Error 
>>> occurred while deleting dashboard" + dashboardTitle);
>>> ResourceData[] resourceData = 
>>> resourceAdminServiceClient.getResourceData(resourcePath);
>>> assertTrue(resourceData.length == 0,"Registry resource could not be 
>>> deleted due to some errors");
>>> }
>>>
>>> Now it's giving me exception when there is no such registry resource
>>> after dashboard was deleted by UI testcase.
>>>
>>> org.apache.axis2.AxisFault: Resource does not exist at path 
>>> /_system/config/ues/dashboards/sampledashboard1
>>>
>>> So can anyone give some suggestions on $subject? Thanks in advance.
>>> --
>>>
>>> *Thank You.*
>>>
>>> *Rajeenthini Satkunam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>>
>>> *E:rajeenth...@wso2.com *
>>>
>>> *M :+94770832823 <%2B94770832823>   *
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kasun Bandara
>> *Software Engineer*
>> Mobile : +94 (0) 718 338 360
>> <%2B94%20%280%29%20773%20451194>
>> kas...@wso2.com 
>>
>
>
>
> --
> Kasun Bandara
> *Software Engineer*
> Mobile : +94 (0) 718 338 360
> <%2B94%20%280%29%20773%20451194>
> kas...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][GREG] Unable to import registry resources from a dump file

[Sameera Kannangara]

Hi Nuwan,

What is the WSO2 server type you are using? and what is the version?

In any case none of the users have ability to check-in to the root
directory.
Therefore you'll have to take the checkout from a collection that is closer
to the resource location you are trying to move.

Ex - sh checkin-client.sh co
https://localhost:9443/registry/_system/governance/trunk/A -u admin -p
admin -f A.dump

What is the use case here,
Are you trying to move an entire repo of a server, into another server?
Or trying to move a part of the repo?

Thank you,
SameeraK.



On Tue, Oct 6, 2015 at 3:23 PM, Nuwan Pallewela  wrote:

> Hi,
>
> After i tried to checkout the dump file , following error is show in
> command line when i try to browse registry.
>
> [2015-10-06 15:20:27,354]  WARN
> {org.wso2.carbon.registry.core.caching.CacheBackedRegistry} -  User admin
> is not authorized to read the resource /.
>
> Thanks,
> Nuwan
>
> On Tue, Oct 6, 2015 at 3:16 PM, Nuwan Pallewela  wrote:
>
>> Hi Devs,
>>
>> I'm trying to test importing registry files using a dump file. I have
>> created a dump file using following command [1].
>> [1] sh checkin-client.sh co https://localhost:9443/registry/ -u admin -p
>> admin -f 10-06-2015_test2.dump
>>
>> Dump file is successfully created in the bin folder.
>>
>> Then when I try to import it to another Greg server using [2] command, it
>> gives following error[3].
>> [2] sh checkin-client.sh ci https://localhost:9445/registry/ -u admin -p
>> admin -f 10-06-2015_test2.dump
>> [3]
>> Error in restoring the path. Make sure the registry is up and running Or
>> the username, password is correct! and check the user have the WRITE
>> permission to the path.
>> path: /
>> registry url: https://localhost:9443/registry
>> username: admin
>>
>> What would be causing this?
>>
>> Thanks,
>> Nuwan
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>>
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>*
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sameera Kannangara*
Software Engineer
Platform TG; WSO2 Inc. http://wso2.com
Contact:
phone: +94719541577
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][GREG] Unable to import registry resources from a dump file

[Nuwan Pallewela]

Hi Sameera,

I'm using 5.0.0 Greg server.
It was the issue. It worked when I mention a different location.
Thanks.

There was an issue, after I tried to invoke it to root directory it gave
the error that admin is not allowed to write for root.
Then I could not browse any file from the management console. Error message
shown as "An unexpected error occurred. Please check the server logs for
more details" every time when trying to browse.

It solved when I restated the server.

Thanks,
Nuwan



On Tue, Oct 6, 2015 at 4:39 PM, Sameera Kannangara 
wrote:

> Hi Nuwan,
>
> What is the WSO2 server type you are using? and what is the version?
>
> In any case none of the users have ability to check-in to the root
> directory.
> Therefore you'll have to take the checkout from a collection that is
> closer to the resource location you are trying to move.
>
> Ex - sh checkin-client.sh co
> https://localhost:9443/registry/_system/governance/trunk/A -u admin -p
> admin -f A.dump
>
> What is the use case here,
> Are you trying to move an entire repo of a server, into another server?
> Or trying to move a part of the repo?
>
> Thank you,
> SameeraK.
>
>
>
> On Tue, Oct 6, 2015 at 3:23 PM, Nuwan Pallewela  wrote:
>
>> Hi,
>>
>> After i tried to checkout the dump file , following error is show in
>> command line when i try to browse registry.
>>
>> [2015-10-06 15:20:27,354]  WARN
>> {org.wso2.carbon.registry.core.caching.CacheBackedRegistry} -  User admin
>> is not authorized to read the resource /.
>>
>> Thanks,
>> Nuwan
>>
>> On Tue, Oct 6, 2015 at 3:16 PM, Nuwan Pallewela  wrote:
>>
>>> Hi Devs,
>>>
>>> I'm trying to test importing registry files using a dump file. I have
>>> created a dump file using following command [1].
>>> [1] sh checkin-client.sh co https://localhost:9443/registry/ -u admin
>>> -p admin -f 10-06-2015_test2.dump
>>>
>>> Dump file is successfully created in the bin folder.
>>>
>>> Then when I try to import it to another Greg server using [2] command,
>>> it gives following error[3].
>>> [2] sh checkin-client.sh ci https://localhost:9445/registry/ -u admin
>>> -p admin -f 10-06-2015_test2.dump
>>> [3]
>>> Error in restoring the path. Make sure the registry is up and running Or
>>> the username, password is correct! and check the user have the WRITE
>>> permission to the path.
>>> path: /
>>> registry url: https://localhost:9443/registry
>>> username: admin
>>>
>>> What would be causing this?
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com *
>>> Mobile  *+94719079739 <%2B94719079739>*
>>>
>>>
>>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sameera Kannangara*
> Software Engineer
> Platform TG; WSO2 Inc. http://wso2.com
> Contact:
> phone: +94719541577
> Lean . Enterprise . Middleware
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

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

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] dockersupport-1.1 branch building issue with workflow extensions changes

[Lahiru Manohara]

Now cloud manager initialization is happening inside the initializeCloudManager
method and also initializeCloudManager method calls for three stages  are
removed from the BPEL as well.

On Tue, Oct 6, 2015 at 4:25 PM, Anuruddha Premalal 
wrote:

> Hi Lahiru,
>
> Tenant creation was done by (+ punnadi). Since we had a single stratos,
> didn't want stage parameter to create tenant in separate registries,
> however once we move tenant creation to greg's you might have to bring the
> stage parameter back or you could use multiple subscriber on the tenant
> creation message.
>
> Regards,
> Anuruddha.
>
> On Tue, Oct 6, 2015 at 2:49 PM, Lahiru Manohara  wrote:
>
>> Hi Anuruddha,
>>
>> According to this full request[1]. The stage parameter was removed from
>> the initializeCloudManager method in
>> the AppFactoryTenantInfraStructureInitializerService class. In
>> Tenantcreation BPEL and default workflow is calling initializeCloudManager
>> for three stages (development, testing and production). But how could i do
>> this from updated code?
>>
>> [1]. https://github.com/wso2/product-af/pull/526/files
>>
>> Thanks.
>> --
>> Best regards,
>>
>> *Lahiru Manohara*
>> *Software Engineer*
>> Mobile: +94716561576
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> *Anuruddha Premalal*
> Software Eng. | WSO2 Inc.
> Mobile : +94717213122
> Web site : www.anuruddha.org
>
>


-- 
Best regards,

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

[Dev] [DAS][APIM] DAS REST API, cApp Deployable URL in Cluster mode

[Rukshan Premathunga]

Hi all,

APIM keep the configuration for Capp deploy server url and Event publisher
URL. Now we have used the REST API to fetch data and we need to keep the
URL for that as well.

We allow users to set them from the APIM UI. But we have a doubt about how
would be the above URLs are change in complex deployment like cluster mode.

In such a mode, what are the distributed component of the DAS and What
Node's URL should be used for the REST API, cApp Deployment and event
publisher.

And also we like to know the descriptive terms used to identify above nodes
for the UI representation in a Distributed environment.

Thanks and Regards.

-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] How to enable the SVN in IS cluster to sync BPEL and HT artifacts

[Harsha Thirimanna]

Hi Aparna,
As Nandika said, I think we don't need to worry about this bps feature in
cluster mode with embeded one. Better to test it with external.


*Harsha Thirimanna*
Senior Software Engineer; 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*


On Tue, Oct 6, 2015 at 4:30 PM, Nandika Jayawardana 
wrote:

> In the cluster scenario, its better to point to an external BPS cluster.
>
> Regards
> Nandika
>
> On Tue, Oct 6, 2015 at 4:06 PM, Aparna Karunarathna 
> wrote:
>
>> Hi Johann and IS team,
>>
>> How to enable the SVN in IS cluster to sync BPEL and HT artifacts among
>> nodes?
>>
>> In Worker/Manager cluster setup, manager node is used to commit
>> artifacts, but for IS cluster doesn't have manager node, both nodes are
>> behave as manager nodes. Basically this issue is getting when we
>> configuring workflows by pointing to the embedded BPS server from manager
>> node.
>>
>> Furthermore, with external BPS server we don't get this kind problem.
>>
>> Please clarify.
>>
>> --
>> *Regards,*
>>
>> *Aparna Karunarathna.*
>>
>>
>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SSO Authentication Error

[Charitha Goonetilleke]

Hi All,

I tried with latest commits and seems, $subject is solved with latest
changes.

Thanks,
/charithag

On Tue, Oct 6, 2015 at 3:20 PM, Darshana Gunawardana 
wrote:

>
>
> On Tue, Oct 6, 2015 at 2:21 PM, Hasintha Indrajee 
> wrote:
>
>> Seems like this issue occurs since the session key you send with your
>> second request  is no longer there in the server side and it gives this
>> error. Did you check this in the latest code base ? Can you confirm that
>> this is still there in the latest code base.
>>
>
> Yes this is fixed with :
> https://github.com/wso2/carbon-identity/commit/1d9bb6763c740c0e39b741f30a0d11d88c37bebc
>
>
>> If this is still there, please open a jira for this issue.
>>
>
> +1 Create a L1 if you see any NPEs on this flow.
>
> Thanks,
> Darshana
>
>>
>> On Tue, Oct 6, 2015 at 1:34 PM, Charitha Goonetilleke > > wrote:
>>
>>> Hi All,
>>>
>>> I'm using carbon.identity.version 4.6.0-SNAPSHOT with IoT Server for
>>> testing. $subject occurred when I tried to login in to store/publisher. It
>>> further saying, "Something went wrong during the authentication process.
>>> Please try signing in again." Also in console printing a Null Pointer
>>> Exception[1].
>>>
>>> This is the way to reproduce the issue.
>>>
>>>- Extract a pack with carbon.identity.version 4.6.0-SNAPSHOT from
>>>zip archive.
>>>- Run pack and try to login as admin
>>>- Shutdown the pack and delete all files of pack.
>>>- Extract pack again from zip archive.
>>>- Run pack and try to login.
>>>
>>> Exception [1]
>>>
>>> [2015-10-06 12:38:23,902] ERROR
>>> {org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
>>> -  Exception in Authentication Framework
>>> java.lang.NullPointerException
>>> at
>>> org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCacheEntry.(SessionContextCacheEntry.java:40)
>>> at
>>> org.wso2.carbon.identity.application.authentication.framework.cache.SessionContextCache.getValueFromCache(SessionContextCache.java:95)
>>> at
>>> org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils.getSessionContextFromCache(FrameworkUtils.java:592)
>>> at
>>> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.findPreviousAuthenticatedSession(DefaultRequestCoordinator.java:284)
>>> at
>>> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.initializeFlow(DefaultRequestCoordinator.java:222)
>>> at
>>> org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.handle(DefaultRequestCoordinator.java:103)
>>> at
>>> org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doPost(CommonAuthenticationServlet.java:53)
>>> at
>>> org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doGet(CommonAuthenticationServlet.java:43)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
>>> 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:60)
>>> 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.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>> at
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>>> at
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>>> at
>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
>>> at
>>> 

Re: [Dev] ESB 4.9.0 - NPE occurs in tenant APIs with same context and different versions

[Chanaka Fernando]

Hi NuwanD,

I can reproduce the issue with the provided configuration. I have already
created a fix for this issue and currently testing it. I'll update the
thread once I finalized the fix and merge the PR.

On Tue, Oct 6, 2015 at 2:59 PM, Nuwan Dias  wrote:

> Attaching the two APIs I used for testing. To reproduce this issue, create
> a tenant with the domain as 'wso2.com' and deploy these two APIs within
> the tenant space and restart the server.
>
> Then access the API without the version using the following URL.
>
> http://localhost:8280/t/wso2.com/responseapi/weather?q=London
>
> Thanks,
> NuwanD.
>
> On Tue, Oct 6, 2015 at 2:53 PM, Chanaka Fernando 
> wrote:
>
>> Hi Nuwan,
>>
>> I had a look into the code which is causing this NPE. According to the
>> way it is written, this NPE can be occurred. I have tried to replicate what
>> NuwanD has mentioned but couldn't reproduce the same NPE. This can be
>> occurred due to synapse configuration issue.
>>
>> @NuwanD: Can you share the configurations which you have used to
>> reproduce this issue?
>>
>>
>> Thanks,
>> Chanaka
>>
>> On Thu, Oct 1, 2015 at 10:41 AM, Chanaka Fernando 
>> wrote:
>>
>>> Hi All,
>>>
>>> We are looking into this issue.
>>>
>>> On Thu, Oct 1, 2015 at 10:37 AM, Sandapa Handakumbura 
>>> wrote:
>>>
 Hi Nuwan,

 I faced a similar issue during ESB 4.9.0 release testing. First request
 for proxy services (after tenant unloading/ server restart) failed in
 tenant mode [1]. Unfortunately ESB team could not reproduce it and I could
 not identify the exact steps to reproduce it either.

 Hope the team will look in to this since you have identified steps to
 reproduce the issue.

 [1] https://wso2.org/jira/browse/ESBJAVA-4142

 Thanks,
 Sandapa


 On Thu, Oct 1, 2015 at 4:47 AM, Nuwan Dias  wrote:

> Hi,
>
> I have a scenario on the ESB where I have created two APIs with the
> same context in the tenant space. The first API doesn't have a version and
> the second API has a version. The first API receives the request and
> forwards to the second API. See illustration below.
>
> Client (/twitter) --> Twitter_API (/twitter/1.0.0) -->
> Twitter_API_v1.0.0
>
> This scenario however causes the following [1] NPE on the first
> request that's sent to the server. The subsequent requests pass until a
> server restart happens.
>
> I tried logging into the management console of the ESB using tenant
> credentials to check whether it was related to tenant loading. The first
> request still failed with the same error. Any idea why this is happening?
> This issue first occurred to me in API Manager after migrating to the
> latest released version of Synapse. And is causing test failures in the
> product. It worked fine in the older versions of Synapse (2.1.2- version
> range).
>
> [1]
>
> [2015-10-01 04:41:39,519] ERROR - PassThroughHttpSender Failed to
> submit the response
> java.lang.NullPointerException
> at
> org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)
> at
> org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)
> at
> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.wso2.carbon.core.multitenancy.transports.TenantTransportSender.invoke(TenantTransportSender.java:231)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
> at
> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
> at org.apache.synapse.rest.Resource.process(Resource.java:297)
> at org.apache.synapse.rest.API.process(API.java:335)
> at
> org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:97)
> at
> org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:52)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:266)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
> at
> 

[Dev] Cannot log to Identity Server Dashboard - NPE in shindig

[Godwin Amila Shrimal]

Hi All,

When we log to Identity Server Dashboard (IS 5.1.0-Alpha) it gives
following error which is reported in [1]

{org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
Permission cache updated for tenant -1234
[2015-09-29 18:10:31,754] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'usera@carbon.super [-1234]' logged in at [2015-09-29 18:10:31,754+0530]
Exception in thread "pool-29-thread-28" java.lang.NullPointerException
at
org.apache.shindig.gadgets.AbstractSpecFactory.fetchFromNetwork(AbstractSpecFactory.java:135)
at
org.apache.shindig.gadgets.AbstractSpecFactory$SpecUpdater.run(AbstractSpecFactory.java:221)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2015-09-29 18:10:49,853] INFO
{org.wso2.carbon.core.internal.permission.update.PermissionUpdater}

Any clue for this ?

https://wso2.org/jira/browse/IDENTITY-3679

Thanks
Godwin


-- 
*Godwin Amila Shrimal*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in verifying the Account locking mechanism

[Isura Karunaratne]

HI Chalitha,

Please refer [1] for latest config changes.

[1] https://wso2.org/jira/browse/DOCUMENTATION-2114

Thanks
Isura

On Tue, Oct 6, 2015 at 6:37 PM, Chalitha Waldeniyage 
wrote:

> Hi Isura,
>
> I am testing the Account locking mechanism in [1] and it doesn't contains
> identity-mgt.properties file in mentioned file path. Instead we can find
> this in repository/conf/identity location. But some of the mentioned
> properties are not in that location. Please let us know what is the correct
> location to refer and any other  addtional changes done to this.
>
> [1] https://docs.wso2.com/display/IS510/Account+Locking
>
>
> Thank you,
> Chalitha.
> --
> *Chalitha Maheshwari*
> Software Engineer-QA,
> WSO2 Inc.
>
> *E-mail:* chali...@wso2.com
> *Mobile: *+94710 411 112
>



-- 
Isura Dilhara Karunaratne
Senior Software Engineer

Mob +94 772 254 810
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] NPE with EIP guide sample.

[Chanaka Fernando]

Hi Ajith,

I have already added a fix to the NPE and currently testing that. Just
wanted to let you know that this is happening due to a configuration issue.
The code was written assuming that this NPE cannot occur in proper
configurations. But there can be some edge cases where this can become
null. I am currently investigating on those.

On Tue, Oct 6, 2015 at 6:52 PM, Ajith Vitharana  wrote:

>
>
> On Tue, Oct 6, 2015 at 5:06 AM, Chanaka Fernando 
> wrote:
>
>> Hi Ajith,
>>
>> The scenario which you have tested is not correct. If you put 
>> mediator in the outSequence, since you are cloning the request and send to
>> 2 back ends, ESB will get 2 responses and tries to send back 2 responses to
>> client and that is causing this exception. What happens is that ESB will
>> send back the first response and then release the connection. When it tries
>> to send back the 2nd response, If some other thread has already reused that
>> connection, the "request" will be null and that is causing the NPE.
>>
>> If you are putting a  mediator in the outSequence, make sure you
>> aggregate the responses before sending the response back.
>>
>
> Yes. I understood the logic.  But my concerns was returning NPE.
>
> -Ajith
>
>>
>> On Mon, Oct 5, 2015 at 9:23 PM, Ajith Vitharana  wrote:
>>
>>>
>>>
>>> On Mon, Oct 5, 2015 at 5:59 AM, Chanaka Fernando 
>>> wrote:
>>>
 Hi Ajith,

 We have already identified this issue and currently working on a fix.
 Thanks for reporting this issue.

>>>
>>> Thanks for looking to this.
>>>
>>> -Ajith
>>>

 On Mon, Oct 5, 2015 at 12:56 AM, Ajith Vitharana 
 wrote:

> Hi All
>
> I did a slight change to sample [1] (used  instead of 
> at the outSequence) , now I'm getting following exception.
>
> [1]
> https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>
>
>
> [2015-10-04 15:19:30,891] DEBUG - wire << "[\r][\n]"
> [2015-10-04 15:19:30,892] ERROR - PassThroughHttpSender Failed to
> submit the response
> j*ava.lang.NullPointerException*
> * at
> org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)*
> * at
> org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)*
> * at
> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)*
> * at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)*
> at
> org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
> at
> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:297)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> [2015-10-04 15:19:30,894] ERROR - Axis2Sender
> Content-Type:application/soap+xml; charset=UTF-8;
> action="urn:getQuoteResponse", encoding='utf-8'?>http://www.w3.org/2003/05/soap-envelope;>
> Unexpected error sending message back
> org.apache.axis2.AxisFault: Failed to submit the response
> at
> org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:610)
> at
> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:269)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
> at
> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
> at
> 

Re: [Dev] Is there any method which can checks the resource exists or not in registry

[Rajeenthini Satkunam]

Hi rajith,

I have tried the way you mentioned.When I use like this

RegistryProviderUtil provider = new RegistryProviderUtil();
WSRegistryServiceClient registry = provider.getWSRegistry(getUesContext());
assertFalse(registry.resourceExists(resourcePath),"Registry resource
could not be deleted due to some errors");

It says like cannot resolve the method getWSRegistry(getUesContext())

But I have tried this way too

WSRegistryServiceClient registry =
provider.getWSRegistry(getCurrentUsername(),getCurrentPassword(),
UESIntegrationTestConstants.UES_PRODUCT_NAME);

But when I run the test cases it is giving me a null pointer exception
at the point when I created registry instance.Could you please advice
me on how can I resolve this issue?




On Tue, Oct 6, 2015 at 4:35 PM, Rajith Roshan  wrote:

> Hi Rajeenthini,
>
> You can get the instance of registry as below and check if the resource
> exists.
>
> RegistryProviderUtil provider = new RegistryProviderUtil();
> WSRegistryServiceClient registry = provider.getWSRegistry(automationContext);
>
> if(registry.resourceExists(path))
>
>
> Thanks,
>
> Rajith
>
>
> On Tue, Oct 6, 2015 at 3:43 PM, Kasun Bandara  wrote:
>
>> Hi Rajeenthini,
>>
>> You can invoke the *boolean resourceExists(String resorcePath)* method
>> through the Registry class comes with registry core. Returns true if the
>> resource exists in the specified path & returns false if it's not reside in
>> the path.
>>
>> Thanks and Regards.
>>
>>
>> On Tue, Oct 6, 2015 at 3:42 PM, Kasun Bandara  wrote:
>>
>>> Hi Rajeenthini,
>>>
>>> You can invoke the *boolean resourceExists(String resorcePath)* method
>>> through the Registry class comes with registry core. Returns true if the
>>> resource exists in the specified path & returns false if it's not reside in
>>> the path.
>>>
>>> Thanks and Regards.
>>>
>>>
>>> On Tue, Oct 6, 2015 at 12:35 PM, Rajeenthini Satkunam <
>>> rajeenth...@wso2.com> wrote:
>>>
 Hi all,

 I am writing UI test cases for UES/Dashboard Server(DS).I have tried to
 write a test class for adding and deleting dashboard for the Dashboard
 Server.Here I need to check the resource is existing or not at the
 registry.You can have a look for the class[1] I have wrote for adding and
 deleting dashboard.
 [1] -
 https://github.com/rajeenthini/product-ues/commit/e642d50edf08cc21d2b0a2b21463e4b3aadc587a

 BTW I have modified my code in some ways .Those are I have included
 below
 - Deleted deleteResource method from here
 resourceAdminServiceClient.deleteResource(resourcePath);

 @AfterClass(alwaysRun = true)
 public void tearDown() throws MalformedURLException, 
 XPathExpressionException, RemoteException, 
 ResourceAdminServiceExceptionException {
 try{
 UESUIIntegrationTest.logout(getDriver(), getBaseUrl(), 
 getCurrentUsername());
 }finally {
 getDriver().quit();
 }
 }

 - Added some code segment to the method deleteDashboard

 @Test(groups = "wso2.ues.dashboard", description = "Deleting added 
 dashboard", dependsOnMethods = "testAddDashboardNew")
 public void testDeleteDashboardNew() throws MalformedURLException, 
 XPathExpressionException, RemoteException, 
 ResourceAdminServiceExceptionException {
 webElement = getDriver().findElement(By.id(dashboardTitle));
 webElement.findElement(By.cssSelector("i.fw-delete")).click();
 getDriver().findElement(By.cssSelector("span.ladda-label")).click();
 assertFalse(getDriver().isElementPresent(By.id(dashboardTitle)), 
 "Error occurred while deleting dashboard" + dashboardTitle);
 ResourceData[] resourceData = 
 resourceAdminServiceClient.getResourceData(resourcePath);
 assertTrue(resourceData.length == 0,"Registry resource could not be 
 deleted due to some errors");
 }

 Now it's giving me exception when there is no such registry resource
 after dashboard was deleted by UI testcase.

 org.apache.axis2.AxisFault: Resource does not exist at path 
 /_system/config/ues/dashboards/sampledashboard1

 So can anyone give some suggestions on $subject? Thanks in advance.
 --

 *Thank You.*

 *Rajeenthini Satkunam*

 *Associate Software Engineer | WSO2*


 *E:rajeenth...@wso2.com *

 *M :+94770832823 <%2B94770832823>   *


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


>>>
>>>
>>> --
>>> Kasun Bandara
>>> *Software Engineer*
>>> Mobile : +94 (0) 718 338 360
>>> <%2B94%20%280%29%20773%20451194>
>>> kas...@wso2.com 
>>>
>>
>>
>>
>> --
>> Kasun Bandara
>> *Software Engineer*
>> Mobile : +94 (0) 718 338 360
>> <%2B94%20%280%29%20773%20451194>
>> 

Re: [Dev] Issue in verifying the Account locking mechanism

[Chalitha Waldeniyage]

Thanks for the information Isura.

[Looping Samuel] since most of the identity management docs needs to be
change.





On Tue, Oct 6, 2015 at 6:45 PM, Isura Karunaratne  wrote:

> HI Chalitha,
>
> Please refer [1] for latest config changes.
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-2114
>
> Thanks
> Isura
>
> On Tue, Oct 6, 2015 at 6:37 PM, Chalitha Waldeniyage 
> wrote:
>
>> Hi Isura,
>>
>> I am testing the Account locking mechanism in [1] and it doesn't contains
>> identity-mgt.properties file in mentioned file path. Instead we can find
>> this in repository/conf/identity location. But some of the mentioned
>> properties are not in that location. Please let us know what is the correct
>> location to refer and any other  addtional changes done to this.
>>
>> [1] https://docs.wso2.com/display/IS510/Account+Locking
>>
>>
>> Thank you,
>> Chalitha.
>> --
>> *Chalitha Maheshwari*
>> Software Engineer-QA,
>> WSO2 Inc.
>>
>> *E-mail:* chali...@wso2.com
>> *Mobile: *+94710 411 112
>>
>
>
>
> --
> Isura Dilhara Karunaratne
> Senior Software Engineer
>
> Mob +94 772 254 810
>
>


-- 
*Chalitha Maheshwari*
Software Engineer-QA,
WSO2 Inc.

*E-mail:* chali...@wso2.com
*Mobile: *+94710 411 112
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] NPE with EIP guide sample.

[Ajith Vitharana]

On Tue, Oct 6, 2015 at 9:31 AM, Chanaka Fernando  wrote:

> Hi Ajith,
>
> I have already added a fix to the NPE and currently testing that. Just
> wanted to let you know that this is happening due to a configuration issue.
> The code was written assuming that this NPE cannot occur in proper
> configurations. But there can be some edge cases where this can become
> null. I am currently investigating on those.
>

Thanks Chanaka !

-Ajith

>
> On Tue, Oct 6, 2015 at 6:52 PM, Ajith Vitharana  wrote:
>
>>
>>
>> On Tue, Oct 6, 2015 at 5:06 AM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Ajith,
>>>
>>> The scenario which you have tested is not correct. If you put 
>>> mediator in the outSequence, since you are cloning the request and send to
>>> 2 back ends, ESB will get 2 responses and tries to send back 2 responses to
>>> client and that is causing this exception. What happens is that ESB will
>>> send back the first response and then release the connection. When it tries
>>> to send back the 2nd response, If some other thread has already reused that
>>> connection, the "request" will be null and that is causing the NPE.
>>>
>>> If you are putting a  mediator in the outSequence, make sure you
>>> aggregate the responses before sending the response back.
>>>
>>
>> Yes. I understood the logic.  But my concerns was returning NPE.
>>
>> -Ajith
>>
>>>
>>> On Mon, Oct 5, 2015 at 9:23 PM, Ajith Vitharana  wrote:
>>>


 On Mon, Oct 5, 2015 at 5:59 AM, Chanaka Fernando 
 wrote:

> Hi Ajith,
>
> We have already identified this issue and currently working on a fix.
> Thanks for reporting this issue.
>

 Thanks for looking to this.

 -Ajith

>
> On Mon, Oct 5, 2015 at 12:56 AM, Ajith Vitharana 
> wrote:
>
>> Hi All
>>
>> I did a slight change to sample [1] (used  instead of 
>> at the outSequence) , now I'm getting following exception.
>>
>> [1]
>> https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>>
>>
>>
>> [2015-10-04 15:19:30,891] DEBUG - wire << "[\r][\n]"
>> [2015-10-04 15:19:30,892] ERROR - PassThroughHttpSender Failed to
>> submit the response
>> j*ava.lang.NullPointerException*
>> * at
>> org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)*
>> * at
>> org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)*
>> * at
>> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)*
>> * at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)*
>> at
>> org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
>> at
>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
>> at
>> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>> at
>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>> at
>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:297)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>> [2015-10-04 15:19:30,894] ERROR - Axis2Sender
>> Content-Type:application/soap+xml; charset=UTF-8;
>> action="urn:getQuoteResponse",> encoding='utf-8'?>http://www.w3.org/2003/05/soap-envelope;>
>> Unexpected error sending message back
>> org.apache.axis2.AxisFault: Failed to submit the response
>> at
>> org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:610)
>> at
>> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:269)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at
>> 

Re: [Dev] [IS] How to enable the SVN in IS cluster to sync BPEL and HT artifacts

[Aparna Karunarathna]

Hi Harsha/ Nandika,

>
>
> As Nandika said, I think we don't need to worry about this bps feature in
> cluster mode with embeded one. Better to test it with external.
>
> I'm not sure whether you understood my question or not. Enabling DepSync
(SVN) in both nodes is not the problem. My question was when we enable
the DepSync in both nodes as committing nodes and fronted by LB , both will
try to commit artifacts,then will get svn conflicts. So how to configure
the DepSync correctly in 2 nodes cluster fronted by LB ?

So your suggestion is to embedded workflow feature cannot be used in
cluster mode and need to configure a external BPS?


>
> In the cluster scenario, its better to point to an external BPS cluster.
>>
> If we use external BPS, what kind of BPS setup suitable for production
setup? Single node or clustered setup?

Regards,
Aparna.



>
>> Regards
>> Nandika
>>
>> On Tue, Oct 6, 2015 at 4:06 PM, Aparna Karunarathna 
>> wrote:
>>
>>> Hi Johann and IS team,
>>>
>>> How to enable the SVN in IS cluster to sync BPEL and HT artifacts among
>>> nodes?
>>>
>>> In Worker/Manager cluster setup, manager node is used to commit
>>> artifacts, but for IS cluster doesn't have manager node, both nodes are
>>> behave as manager nodes. Basically this issue is getting when we
>>> configuring workflows by pointing to the embedded BPS server from manager
>>> node.
>>>
>>> Furthermore, with external BPS server we don't get this kind problem.
>>>
>>> Please clarify.
>>>
>>> --
>>> *Regards,*
>>>
>>> *Aparna Karunarathna.*
>>>
>>>
>>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nandika Jayawardana
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>>
>
>


-- 
*Regards,*

*Aparna Karunarathna.*


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

Re: [Dev] [AF] dockersupport-1.1 branch building issue with workflow extensions changes

[Punnadi Gunarathna]

Hi Lahiru,


Please find the changes made by me in [1]. I think you will have to revert
it back to it's initial state.

[1]
https://github.com/punnadih/product-af/commit/c58f448a61f42d1ba8f6e5206e437076926267f8

On Tue, Oct 6, 2015 at 6:49 AM, Lahiru Manohara  wrote:

> Now cloud manager initialization is happening inside the 
> initializeCloudManager
> method and also initializeCloudManager method calls for three stages  are
> removed from the BPEL as well.
>
> On Tue, Oct 6, 2015 at 4:25 PM, Anuruddha Premalal 
> wrote:
>
>> Hi Lahiru,
>>
>> Tenant creation was done by (+ punnadi). Since we had a single stratos,
>> didn't want stage parameter to create tenant in separate registries,
>> however once we move tenant creation to greg's you might have to bring the
>> stage parameter back or you could use multiple subscriber on the tenant
>> creation message.
>>
>> Regards,
>> Anuruddha.
>>
>> On Tue, Oct 6, 2015 at 2:49 PM, Lahiru Manohara 
>> wrote:
>>
>>> Hi Anuruddha,
>>>
>>> According to this full request[1]. The stage parameter was removed from
>>> the initializeCloudManager method in
>>> the AppFactoryTenantInfraStructureInitializerService class. In
>>> Tenantcreation BPEL and default workflow is calling initializeCloudManager
>>> for three stages (development, testing and production). But how could i do
>>> this from updated code?
>>>
>>> [1]. https://github.com/wso2/product-af/pull/526/files
>>>
>>> Thanks.
>>> --
>>> Best regards,
>>>
>>> *Lahiru Manohara*
>>> *Software Engineer*
>>> Mobile: +94716561576
>>> WSO2 Inc. | http://wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> *Anuruddha Premalal*
>> Software Eng. | WSO2 Inc.
>> Mobile : +94717213122
>> Web site : www.anuruddha.org
>>
>>
>
>
> --
> Best regards,
>
> *Lahiru Manohara*
> *Software Engineer*
> Mobile: +94716561576
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



-- 

Thanks and Regards,

Punnadi Gunarathna
Senior Software Engineer,
WSO2, Inc.; http://wso2.com 
Blog: http://hi-my-world.blogspot.com/
Tel : 94 11 214 5345
Fax :94 11 2145300


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

[Dev] Issue in verifying the Account locking mechanism

[Chalitha Waldeniyage]

Hi Isura,

I am testing the Account locking mechanism in [1] and it doesn't contains
identity-mgt.properties file in mentioned file path. Instead we can find
this in repository/conf/identity location. But some of the mentioned
properties are not in that location. Please let us know what is the correct
location to refer and any other  addtional changes done to this.

[1] https://docs.wso2.com/display/IS510/Account+Locking


Thank you,
Chalitha.
-- 
*Chalitha Maheshwari*
Software Engineer-QA,
WSO2 Inc.

*E-mail:* chali...@wso2.com
*Mobile: *+94710 411 112
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in verifying the Account locking mechanism

[Samuel Gnaniah]

Noted. Adding this as soon as we're done with workflows. :)

Thanks,

*Samuel Gnaniah*
Lead Technical Writer

WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798

On Tue, Oct 6, 2015 at 7:00 PM, Chalitha Waldeniyage 
wrote:

> Thanks for the information Isura.
>
> [Looping Samuel] since most of the identity management docs needs to be
> change.
>
>
>
>
>
> On Tue, Oct 6, 2015 at 6:45 PM, Isura Karunaratne  wrote:
>
>> HI Chalitha,
>>
>> Please refer [1] for latest config changes.
>>
>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2114
>>
>> Thanks
>> Isura
>>
>> On Tue, Oct 6, 2015 at 6:37 PM, Chalitha Waldeniyage 
>> wrote:
>>
>>> Hi Isura,
>>>
>>> I am testing the Account locking mechanism in [1] and it doesn't
>>> contains identity-mgt.properties file in mentioned file path. Instead we
>>> can find this in repository/conf/identity location. But some of the
>>> mentioned properties are not in that location. Please let us know what is
>>> the correct location to refer and any other  addtional changes done to this.
>>>
>>> [1] https://docs.wso2.com/display/IS510/Account+Locking
>>>
>>>
>>> Thank you,
>>> Chalitha.
>>> --
>>> *Chalitha Maheshwari*
>>> Software Engineer-QA,
>>> WSO2 Inc.
>>>
>>> *E-mail:* chali...@wso2.com
>>> *Mobile: *+94710 411 112
>>>
>>
>>
>>
>> --
>> Isura Dilhara Karunaratne
>> Senior Software Engineer
>>
>> Mob +94 772 254 810
>>
>>
>
>
> --
> *Chalitha Maheshwari*
> Software Engineer-QA,
> WSO2 Inc.
>
> *E-mail:* chali...@wso2.com
> *Mobile: *+94710 411 112
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [jaggery] product-jaggery build fail due to version mismatch

[Lalanke Athauda]

Hi,
I'm trying to build product-jaggery, so I updated the carbon versions in
the pom.xml file. I have updated to newest versions. When it builds, it
gives following error and fails the build.

Installation failed.
Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 Carbon - Webapp Management Core Feature
4.5.3 (org.wso2.carbon.webapp.mgt.server.feature.group 4.5.3)
 Missing requirement: org.wso2.carbon.identity.sso.agent 4.5.6
(org.wso2.carbon.identity.sso.agent 4.5.6) requires 'package
org.apache.http.conn.ssl [4.3.1.wso2v2,4.4.0)' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Webapp Management Core Feature 4.5.3
(org.wso2.carbon.webapp.mgt.server.feature.group 4.5.3)
  To: org.wso2.carbon.identity.sso.agent [4.5.6]

Appreciate the suggestions of what should be updated more. Thanks.

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

Re: [Dev] [ESB] NPE with EIP guide sample.

[Ajith Vitharana]

On Tue, Oct 6, 2015 at 5:06 AM, Chanaka Fernando  wrote:

> Hi Ajith,
>
> The scenario which you have tested is not correct. If you put 
> mediator in the outSequence, since you are cloning the request and send to
> 2 back ends, ESB will get 2 responses and tries to send back 2 responses to
> client and that is causing this exception. What happens is that ESB will
> send back the first response and then release the connection. When it tries
> to send back the 2nd response, If some other thread has already reused that
> connection, the "request" will be null and that is causing the NPE.
>
> If you are putting a  mediator in the outSequence, make sure you
> aggregate the responses before sending the response back.
>

Yes. I understood the logic.  But my concerns was returning NPE.

-Ajith

>
> On Mon, Oct 5, 2015 at 9:23 PM, Ajith Vitharana  wrote:
>
>>
>>
>> On Mon, Oct 5, 2015 at 5:59 AM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Ajith,
>>>
>>> We have already identified this issue and currently working on a fix.
>>> Thanks for reporting this issue.
>>>
>>
>> Thanks for looking to this.
>>
>> -Ajith
>>
>>>
>>> On Mon, Oct 5, 2015 at 12:56 AM, Ajith Vitharana 
>>> wrote:
>>>
 Hi All

 I did a slight change to sample [1] (used  instead of  at
 the outSequence) , now I'm getting following exception.

 [1]
 https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber



 [2015-10-04 15:19:30,891] DEBUG - wire << "[\r][\n]"
 [2015-10-04 15:19:30,892] ERROR - PassThroughHttpSender Failed to
 submit the response
 j*ava.lang.NullPointerException*
 * at
 org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)*
 * at
 org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)*
 * at
 org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)*
 * at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)*
 at
 org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
 at
 org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
 at
 org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
 at
 org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
 at
 org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:297)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
 at
 org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
 [2015-10-04 15:19:30,894] ERROR - Axis2Sender
 Content-Type:application/soap+xml; charset=UTF-8;
 action="urn:getQuoteResponse",>>> encoding='utf-8'?>http://www.w3.org/2003/05/soap-envelope;>
 Unexpected error sending message back
 org.apache.axis2.AxisFault: Failed to submit the response
 at
 org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:610)
 at
 org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:269)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
 at
 org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
 at
 org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
 at
 org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
 at
 org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:297)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
 at
 

[Dev] Hazelcast Issue - sequence is too small. the current head sequence...

[Hasitha Hiranya]

Hi Peter,

We are using Hazelcast in our Message Broker project. We are getting
following exception when using a iTopic for syncing data.

Appreciate any idea why this happen? Are we doing something wrong in our
client application?

We found code [1] throwing the exception.

Oct 06, 2015 4:26:44 PM
com.hazelcast.ringbuffer.impl.operations.ReadManyOperation
SEVERE: [192.168.1.50]:4000 [wso2.mb.domain] [3.5] sequence:8 is too small.
The current headSequence is:9
com.hazelcast.ringbuffer.StaleSequenceException: sequence:8 is too small.
The current headSequence is:9
at
com.hazelcast.ringbuffer.impl.RingbufferContainer.checkBlockableReadSequence(RingbufferContainer.java:176)
at
com.hazelcast.ringbuffer.impl.operations.ReadManyOperation.beforeRun(ReadManyOperation.java:55)
at
com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:131)
at
com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processOperation(OperationThread.java:154)
at
com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:110)
at
com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.doRun(OperationThread.java:101)
at
com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.run(OperationThread.java:76)


[1].
https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/ringbuffer/impl/RingbufferContainer.java

Thanks

-- 
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] dockersupport-1.1 branch building issue with workflow extensions changes

[Amalka Subasinghe]

As I know what you are doing is, implementing a extension class to invoke
the methods defined in AppFactoryTenantInfraStructureInitializerService
class. Now with the new implementation we have removed calling
initializeCloudManager method 3 times for 3 stages. Instead of that we call
initializeCloudManager methods only once and within that method we create
tenant in all stages.

So you need to update your extension class to invoke initializeCloudManager
method once. No need to revert the changes done by Punnadi.

On Tue, Oct 6, 2015 at 5:43 PM, Punnadi Gunarathna  wrote:

> Hi Lahiru,
>
>
> Please find the changes made by me in [1]. I think you will have to revert
> it back to it's initial state.
>
> [1]
> https://github.com/punnadih/product-af/commit/c58f448a61f42d1ba8f6e5206e437076926267f8
>
> On Tue, Oct 6, 2015 at 6:49 AM, Lahiru Manohara  wrote:
>
>> Now cloud manager initialization is happening inside the 
>> initializeCloudManager
>> method and also initializeCloudManager method calls for three stages  are
>> removed from the BPEL as well.
>>
>> On Tue, Oct 6, 2015 at 4:25 PM, Anuruddha Premalal 
>> wrote:
>>
>>> Hi Lahiru,
>>>
>>> Tenant creation was done by (+ punnadi). Since we had a single stratos,
>>> didn't want stage parameter to create tenant in separate registries,
>>> however once we move tenant creation to greg's you might have to bring the
>>> stage parameter back or you could use multiple subscriber on the tenant
>>> creation message.
>>>
>>> Regards,
>>> Anuruddha.
>>>
>>> On Tue, Oct 6, 2015 at 2:49 PM, Lahiru Manohara 
>>> wrote:
>>>
 Hi Anuruddha,

 According to this full request[1]. The stage parameter was removed from
 the initializeCloudManager method in
 the AppFactoryTenantInfraStructureInitializerService class. In
 Tenantcreation BPEL and default workflow is calling initializeCloudManager
 for three stages (development, testing and production). But how could i do
 this from updated code?

 [1]. https://github.com/wso2/product-af/pull/526/files

 Thanks.
 --
 Best regards,

 *Lahiru Manohara*
 *Software Engineer*
 Mobile: +94716561576
 WSO2 Inc. | http://wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>> *Anuruddha Premalal*
>>> Software Eng. | WSO2 Inc.
>>> Mobile : +94717213122
>>> Web site : www.anuruddha.org
>>>
>>>
>>
>>
>> --
>> Best regards,
>>
>> *Lahiru Manohara*
>> *Software Engineer*
>> Mobile: +94716561576
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
>
> Thanks and Regards,
>
> Punnadi Gunarathna
> Senior Software Engineer,
> WSO2, Inc.; http://wso2.com 
> Blog: http://hi-my-world.blogspot.com/
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Amalka Subasinghe
Senior Software Engineer
WSO2 Inc.
Mobile: +94 77 9401267
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] - Assertion Signing is displayed in Federated Authenticators > SAML2 Web SSO but not in SAML Service Provider

[Nadeesha Meegoda]

Thanks Dulanja and Gayan for the clarification.

On Tue, Oct 6, 2015 at 11:07 PM, Gayan Gunawardana  wrote:

>
>
> On Tue, Oct 6, 2015 at 10:48 PM, Nadeesha Meegoda 
> wrote:
>
>> Hi Dulanja,
>>
>> In the SAML SP configuration for IS 5.1.0 there is no such option to
>> enable assertion signing.
>>
>
> As Dulanja mentioned, According to SAML spec Assertion Signing is enable
> by default please look [1]
>
> [1] https://wso2.org/jira/browse/IDENTITY-1045
>
>
>> So how can the SP decide whether to validate that or not?
>>
>>
>>
>> On Tue, Oct 6, 2015 at 10:43 PM, Dulanja Liyanage 
>> wrote:
>>
>>> Hi Nadeesha,
>>>
>>> Assertion Signing option in the IdP UI enables/disables Assertion
>>> Signature *validation*. The Assertion coming from the external IS will
>>> be always signed. The IS acting as the SP can decide whether to validate
>>> that or not.
>>>
>>> Thanks
>>> Dulanja
>>>
>>> On Tue, Oct 6, 2015 at 8:35 PM, Nadeesha Meegoda 
>>> wrote:
>>>
 Hi IS team,

 In is 5.1.0 SAML>SAML federated scenario, I just noticed that in the
 IDP I created for external IS includes the *Assertion Signing* option
 where the application registered SAML service provider doesn't have any
 option as such. When the federated scenario works doesn't both IDP and SPs
 need to match with those options. Please clarify!

 Thanks!

 *Nadeesha Meegoda*
 Software Engineer - QA
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 email : nadees...@wso2.com
 mobile: +94783639540
 <%2B94%2077%202273555>

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


>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Dulanja Liyanage
>>> WSO2 Inc.
>>>
>>
>>
>>
>> --
>> *Nadeesha Meegoda*
>> Software Engineer - QA
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> email : nadees...@wso2.com
>> mobile: +94783639540
>> <%2B94%2077%202273555>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Gayan Gunawardana
> Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>



-- 
*Nadeesha Meegoda*
Software Engineer - QA
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
email : nadees...@wso2.com
mobile: +94783639540
<%2B94%2077%202273555>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Table 'is510reg.REG_LOG' doesn't exist" error was thrown when starting the server

[Isuruwan Herath]

Hi Isura,

Is it possible to verify that in QA DB, REG_LOG table has been created in
*is510reg* database and access granted to the DB user which is configured
in IS node, to the same database?

Thanks,
Isuruwan

On Tue, Oct 6, 2015 at 8:26 PM, Isura Karunaratne  wrote:

>
> Hi,
>>
>> QA reported [1] in IS5.1.0 alpha and we observed that the same error was
>> occurred in ESB [2] and APIM[3] products as well. They resolved these
>> issues as "Cannot Reproduce"
>>
>> @Greg team
>>
>> We are also unable to reproduce the issue and what would be the reason
>> for occurring this issue in QA environment?
>>
>>
>> Thanks
>> Isura.
>>
>>
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-3750
>> [2] https://wso2.org/jira/browse/ESBJAVA-2539
>> [3] https://wso2.org/jira/browse/APIMANAGER-2199
>>
>>
>>
>> --
>> Isura Dilhara Karunaratne
>> Senior Software Engineer
>>
>> Mob +94 772 254 810
>>
>>
>
>
> --
> Isura Dilhara Karunaratne
> Senior Software Engineer
>
> Mob +94 772 254 810
>
>


-- 
Isuruwan Herath
Technical Lead

Contact: +94 776 273 296
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] - Assertion Signing is displayed in Federated Authenticators > SAML2 Web SSO but not in SAML Service Provider

[Dulanja Liyanage]

Hi Nadeesha,

Assertion Signing option in the IdP UI enables/disables Assertion Signature
*validation*. The Assertion coming from the external IS will be always
signed. The IS acting as the SP can decide whether to validate that or not.

Thanks
Dulanja

On Tue, Oct 6, 2015 at 8:35 PM, Nadeesha Meegoda  wrote:

> Hi IS team,
>
> In is 5.1.0 SAML>SAML federated scenario, I just noticed that in the IDP I
> created for external IS includes the *Assertion Signing* option where the
> application registered SAML service provider doesn't have any option as
> such. When the federated scenario works doesn't both IDP and SPs need to
> match with those options. Please clarify!
>
> Thanks!
>
> *Nadeesha Meegoda*
> Software Engineer - QA
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> email : nadees...@wso2.com
> mobile: +94783639540
> <%2B94%2077%202273555>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,
Dulanja Liyanage
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Performing SQL COUNT() operation through luciene

[Isuru Wijesinghe]

Hi Anjana,

I think the link [1] given something similar to *where* clause in sql (I
mean the *query *part is something similar to *where *clause). Here what I
really need to do is, use the count operation with *group by. * In addition
to that does luicene support for ascending and descending order ???

On Tue, Oct 6, 2015 at 3:54 PM, Anjana Fernando  wrote:

> Hi Isuru,
>
> You can use the REST APIs search count [1] operation.
>
> [1]
> https://docs.wso2.com/display/DAS300/Retrieving+the+Number+of+Records+Matching+the+Given+Search+Query+via+REST+API
>
> Cheers,
> Anjana.
>
> On Tue, Oct 6, 2015 at 1:04 PM, Isuru Wijesinghe  wrote:
>
>> Hi,
>>
>> I need to perform COUNT() operation through DAS REST API (an example is
>> shown below). I tried to pass COUNT() from a luciene object. But it didn't
>> work for me. Does DAS support COUNT operation through luciene ???  if not
>> how can I enable it in DAS side???
>>
>> eg: *SELECT startedTime, processDefinitionId, COUNT(processInstanceId)
>> AS processInstanceCount FROM PROCESS_USAGE_SUMMARY GROUP BY startedTime,
>> processDefinitionId;*
>>
>> In addition to that, is that possible to pass more than one parameter to
>> the query part in luicene object, because most graphs have to provide a
>> secondary filter to get the result. As an example I need to filter the
>> result from date range as well as process id.  I need something like this.
>>
>>  *"query" : "timestamp : [1243214324532 TO 4654365223], processId :
>> 10035" *
>>
>> Any help will be appreciated.
>>
>> --
>> Isuru Wijesinghe
>> *Software Engineer*
>> Mobile: 0710933706
>> isur...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>



-- 
Isuru Wijesinghe
*Software Engineer*
Mobile: 0710933706
isur...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [IS] [user-mgt] Clarification for Bulk Import Users

[Kavitha Subramaniyam]

Hi IS team,

I have configured external JDBC R/W-mysql for primary user store and I
could be able to see the 'Bulk Import Users' link, only if JDBC configured
as primary user store and no other secondary user stores configured. When I
have secondary stores configured and disable those stores to check 'Bulk
Import Users' link, then the link appear (as per jira [1]).

But still this requirement is not clear and Appreciate if you can clarify
whether it should be available for JDBC primary store only at all the time.


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

Thanks & Kind regards,
-- 
Kavitha.S
*Software Engineer -QA*
Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
kavi...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev