Re: [Dev] [ML] Wrangler Integration

[Danula Eranjith]

Sure. Ill send the document and the PR

Thanks,
Danula

On Fri, Sep 4, 2015 at 9:01 AM, Nirmal Fernando  wrote:

> Also please send a PR to our repos.
>
> On Fri, Sep 4, 2015 at 8:59 AM, Nirmal Fernando  wrote:
>
>> Thanks Danula.
>>
>> ML team like to do the integration of this, since there're few things we
>> need to clear up in ML side.
>>
>> Can you please come up with a clearly explained document on the project
>> work carried out during the summer?
>>
>> On Wed, Sep 2, 2015 at 12:41 AM, Danula Eranjith 
>> wrote:
>>
>>> Hi,
>>>
>>> I have made the changes you suggested at [1] and created a API to access
>>> the wrangler service at [2].
>>>
>>> Also added a new step in the wizard at [3] with the wrangler interface.
>>> Please have a look.
>>>
>>> How can we create a sample of the dataset to be passed to wrangler? I
>>> couldn't find any current implementation capable of this.
>>>
>>> Another concern is if we are adding the feature selection step after the
>>> cleaning step, we need to reflect the changes done in step one at step two.
>>> But since we do not apply transformations to RDD initially, we need to come
>>> up an alternative approach.
>>>
>>> [1] -
>>> https://github.com/danula/carbon-ml/tree/master/components/ml/org.wso2.carbon.ml.wrangler/src/main/java/org/wso2/carbon/ml/wrangler
>>>
>>> [2] -
>>> https://github.com/danula/carbon-ml/blob/master/components/ml/org.wso2.carbon.ml.rest.api/src/main/java/org/wso2/carbon/ml/rest/api/WranglerApiV10.java
>>> 
>>>
>>> [3] -
>>> https://github.com/danula/carbon-ml/blob/master/apps/ml/site/clean/clean.jag
>>>
>>> Thanks,
>>> Danula
>>>
>>>
>>> On Thu, Aug 27, 2015 at 9:41 AM, Danula Eranjith 
>>> wrote:
>>>
 Basically script exported from Wrangler tool has list of operations.
 Wrangler class parse that script and create WranglerOperation object
 for each operation with its parameters.
 Then when WranglerOperation.executeOperation() is invoked, it creates
 the respective SparkOperation object and then applies operations to the
 JavaRDD

 On Thu, Aug 27, 2015 at 9:35 AM, Nirmal Fernando 
 wrote:

> What does WranglerOperation class do?
>
> On Thu, Aug 27, 2015 at 9:24 AM, Danula Eranjith 
> wrote:
>
>> Currently Wrangler Operation is the class that holds details related
>> to wrangler and SparkOperation contains the relevant Spark 
>> transformation.
>>
>> If we are changing SparkOperation as WranglerOperation, we need to
>> rename the current WranglerOperation into something else.
>>
>> On Thu, Aug 27, 2015 at 9:18 AM, Nirmal Fernando 
>> wrote:
>>
>>> /s/SparkOpration/SparkOperation
>>>
>>> May be as Supun said, I too think we should call them as
>>> 'WranglerOperation'.
>>>
>>> On Thu, Aug 27, 2015 at 7:02 AM, Nirmal Fernando 
>>> wrote:
>>>
 Also, avoid static methods in transformations.

 On Thu, Aug 27, 2015 at 2:48 AM, Supun Sethunga 
 wrote:

> Hi Danula,
>
> Few comments:
>
>- You might have to register the component in the OSGI
>environment, to be able to call the services from a another 
> component.
>Refer [1] on how to do this.
>- Better to introduce an interface for WranglerOperation class.
>- Add class level/ method level comments.
>- Use logger in-place of System.out.println
>
> [1]
> https://github.com/danula/carbon-ml/blob/master/components/ml/org.wso2.carbon.ml.database/src/main/java/org/wso2/carbon/ml/database/internal/ds/MLDatabaseServiceDS.java
>
> Thanks,
> Supun
>
> On Wed, Aug 26, 2015 at 1:32 PM, Danula Eranjith <
> hmdanu...@gmail.com> wrote:
>
>> Hi,
>>
>> I added the component at [1]
>> 
>> Please have a look.
>>
>> [1] -
>> https://github.com/danula/carbon-ml/tree/master/components/ml/org.wso2.carbon.ml.wrangler
>>
>> Danula
>>
>> On Tue, Aug 25, 2015 at 8:35 PM, Danula Eranjith <
>> hmdanu...@gmail.com> wrote:
>>
>>> Thanks Supun
>>>
>>> On Tue, Aug 25, 2015 at 7:25 PM, Supun Sethunga >> > wrote:
>>>
 You can integrate it to [1], by adding a new component
 "org.wso2.carbon.ml.wrangler". Each component is a carbon 
 component.

 Please follow the naming conventions used in the other
 components, for package names and etc..

 [1] https://github.com/wso2/carbon-ml/tree/master/components

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Chaminda Jayawardena]

How about this for apim integration? APIM has dipsync use case. KM needs
the same userstore to be shared with. In a distributed setup which has both
Greg and APIM nodes(may be multiple KM, GW as well), what would be the
suggestion?

On Fri, Sep 4, 2015 at 3:23 PM, Sagara Gunathunga  wrote:

>
>
> On Fri, Sep 4, 2015 at 2:11 PM, Chandana Napagoda 
> wrote:
>
>> Hi Pavithra,
>>
>> As a workaround one can use rsync or copy secondary user store
>> configuration in to other nodes.
>>
>
> I'm not quite sure whether dev or qa team have tested DipSync in G-Reg
> ever, because we don't have any such direct use case, even current context
> DipSync came in to the picture because of secondary user store requirement,
> may be we can test this from next release.
>
> Other concern is enabling DipSync among G-Reg nodes just because of
> secondary user store ( which also not frequently change) support may
> complicate the deployment architecture instead rsync or manual sync of
> secondary user store definition files is much preferable, hence IMHO this
> should be a less priority item.
>
> Thanks !
>
>>
>> Regards,
>> Chandana
>>
>> On Fri, Sep 4, 2015 at 12:39 PM, Pavithra Madurangi 
>> wrote:
>>
>>>
>>>
>>> On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga 
>>> wrote:
>>>


 On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:

> Thanks Prasanna. Please update the JIRA as well.
>
> In between there was a dep sync issue reported with ESB [1] with the
> recent fix from carbon commons. Just want to find out whether this has any
> effect on GREG product for scenarios like secondary user store, API-M
> integration (May not be an issue since we suggest to use APIM 1.9.1 for 
> GW)
> or install WSO2 AS features and use it (which is anyway very unlikely
> scenario).
>

 It's hard to think about DipSync use cases in G-Reg.

>>>
>>> ​Agree to this.
>>>
>>> But our concern was secondary user stores. If we have secondary user
>>> stores in a multi node deployment, won't there be any issues because of
>>> this bug (since it's one place where depSync is needed)?
>>>
>>> There's a possibility of managing secondary user stores without having
>>> depSync. What we wanted to get clarified was whether that's the
>>> approach/workaround we suggest ?
>>>
>>> Regards,
>>> pavithra
>>>

 Thanks !

>
> 1. ESBJAVA-4156 
>
>
>
>
>
> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
> wrote:
>
>> Hi Thayalan,
>>
>> We fixed the issue REGISTRY-2927
>>  . Now users can
>> re-login from the same window in a fresh pack.
>>
>> Thanks
>>
>> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>>
>>> Hi Team,
>>>
>>> I've observed from the standalone pack without any changes user has
>>> not been allowed to re-login  to the store [1]. However this is working
>>> fine for publisher. As per the suggestion in [1] hostname has to be set 
>>> in
>>> carbon.xml. However in the default pack SSO enabled for store/publisher 
>>> and
>>> Hostname tag is commented. Even uncomment them and set to IP or 
>>> localhost
>>> too not working as suggested in the JIRA. From the end user perspective
>>> user should allow to re-login from the same window session from the 
>>> fresh
>>> pack. Is this is something we need to fix before releasing them?
>>>
>>> 1.REGISTRY-2927 
>>>
>>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda >> > wrote:
>>>
 -1,

 We found an issue with solr related logging configuration and this
 issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.

 Step to reproduce this issue:

 Go to Main --> Registry search and search by any value.
 Then navigate to Configure --> Logging section.
 Exceptions are logged in console and "Global Log4J Configuration"
 and "Configure Log4J Appenders" views are not loading due to the above
 issue.

 Created a JIRA[1] to track above issue and will release release
 G-Reg 5.0.0 RC3 pack ASAP.

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

 Regards,
 Chandana


 On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda <
 chand...@wso2.com> wrote:

> Hi Pubudu,
>
> Since we have already released RC2 pack and component repos, we
> can not update above pages now. We will update context specific pages 
> for
> coming up 5.0.1 release. Meantime, you can refer wiki based 
> documentation
> available here [1].
>
> [1].
> https://docs.wso2.com/display/Governance500/WSO2+Governanc

[Dev] [DAS] unable to purge data

[Rukshan Premathunga]

Hi,

i tried data purging function in DAS data_explorer. But i get the following
error.
please find the attached screenshot.


​
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] Tagging the app-manager branch's release commit in carbon-store for app manager release 1.0.0

[Rushmin Fernando]

Thanks Udara ! Verified.

Thanks
Rushmin

Sent from my mobile.
On Sep 5, 2015 8:48 AM, "Udara Rathnayake"  wrote:

> Hi Rushmin,
>
> Tag created here, https://github.com/wso2/carbon-store/releases/tag/v1.1.0
>
> Please verify.
>
> On Sat, Sep 5, 2015 at 7:28 AM, Rushmin Fernando  wrote:
>
>> Hi Udara,
>>
>> We recently moved the app-manager branch from product-es to carbon-store.
>>
>> I think the release commit has not been tagged in that process.
>>
>> Can you please tag the commit #
>> *2fec2e1babbec4a3dcda88a0899c1211a5743c84* as *1.1.0*
>>
>> (The same is there in the product-es branch [1])
>>
>> Thanks
>> Rushmin
>>
>>
>> [1] - https://github.com/wso2/product-es/commits/1.1.0
>>
>>
>>
>> --
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> email : rush...@wso2.com
>> mobile : +94772310855
>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Tagging the app-manager branch's release commit in carbon-store for app manager release 1.0.0

[Udara Rathnayake]

Hi Rushmin,

Tag created here, https://github.com/wso2/carbon-store/releases/tag/v1.1.0

Please verify.

On Sat, Sep 5, 2015 at 7:28 AM, Rushmin Fernando  wrote:

> Hi Udara,
>
> We recently moved the app-manager branch from product-es to carbon-store.
>
> I think the release commit has not been tagged in that process.
>
> Can you please tag the commit # *2fec2e1babbec4a3dcda88a0899c1211a5743c84*
> as *1.1.0*
>
> (The same is there in the product-es branch [1])
>
> Thanks
> Rushmin
>
>
> [1] - https://github.com/wso2/product-es/commits/1.1.0
>
>
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Tagging the app-manager branch's release commit in carbon-store for app manager release 1.0.0

[Rushmin Fernando]

Hi Udara,

We recently moved the app-manager branch from product-es to carbon-store.

I think the release commit has not been tagged in that process.

Can you please tag the commit # *2fec2e1babbec4a3dcda88a0899c1211a5743c84*
as *1.1.0*

(The same is there in the product-es branch [1])

Thanks
Rushmin


[1] - https://github.com/wso2/product-es/commits/1.1.0



-- 
*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

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

Re: [Dev] [Greg 5.0.0 Beta] Can't change the notification settings under options section of store

[Shafreen Anfar]

Hi Chandana,

Any update on this ?


On Tue, Aug 25, 2015 at 9:45 AM, Shafreen Anfar  wrote:

> Hi All,
>
> I just created a Rest service. Then went to the store and tried to change
> the notification settings. Even though I click on the icon (apple like
> button), it does't do anything. In the console I could see the below error.
>
> [2015-08-25 10:36:41,826] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,110] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,114] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,600] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,602] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,603] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,608] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,897] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,902] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,903] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,910] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,912] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,916] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,921] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:43,921] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
> [2015-08-25 10:36:51,895] ERROR {rxt.core} -  Unable to locate
> assetResources for tenant: -1234 and type: undefined
>
>
> --
> Regards,
> *Shafreen*
> Software Engineer
> WSO2 Inc
> Mobile : 077-556-395-1
>



-- 
Regards,
*Shafreen*
Software Engineer
WSO2 Inc
Mobile : 077-556-395-1
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Testing issues with BETA and RC2

[Malaka Silva]

No Elilmatha,

In both cases you are getting the 301.

ESB Beta and RC1 behaving differently is another story.

We should be forcing on identifying why we are getting 301 for the request
sent by connector. (ESB)


On Fri, Sep 4, 2015 at 7:16 PM, Elilmatha Sivanesan 
wrote:

> Hi Keerthika,
>
> yes REQUEST_HOST_HEADER is used ,and its working fine with beta snapshot
> , but not with rc2.
>
> Thanks.
>
> On Fri, Sep 4, 2015 at 7:11 PM, Keerthika Mahendralingam <
> keerth...@wso2.com> wrote:
>
>> Hi Elil,
>> You are getting *302 Moved Temporarily *as the response. Thats why you
>> are getting the above error. Earlier we got the same error and used
>> REQUEST_HOST_HEADER to resolve the issue.
>>
>> Thanks,
>>
>> On Fri, Sep 4, 2015 at 6:49 PM, Elilmatha Sivanesan 
>> wrote:
>>
>>> Hi Malaka,
>>>
>>> No the above failing test case is for positive one (
>>> CreateAccountWithMandatoryParameters ) same behaviour is observed on
>>> all positive test cases.
>>>
>>> Thank you.
>>>
>>> On Fri, Sep 4, 2015 at 4:47 PM, Malaka Silva  wrote:
>>>
 Hi Elilmatha,

 I guess this is due to [1]

 Previously behavior of ESB is invalid it seems and written test cases
 according to that.

 Failing test case is it a negative one?

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

 On Fri, Sep 4, 2015 at 4:30 PM, Elilmatha Sivanesan >>> > wrote:

> Hi all,
>
> Salesbinder connector integration test is running fine with
> wso2esb-4.9.0-BETA-SNAPSHOT ,But not with RC2.
>
> I have shared the wire log of one method, What can be the cause of the
> error.
> Is this the expected behaviour.
>
> with wso2esb-4.9.0-BETA-SNAPSHOT
>
> [2015-09-04 15:08:52,564]  INFO
> {org.wso2.carbon.automation.core.PlatformTestManager} -  Running the test
> method ---
> org.wso2.carbon.connector.integration.test.salesbinder.SalesbinderConnectorIntegrationTest.testCreateAccountWithMandatoryParameters
> 
> [2015-09-04 15:08:52,605]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,605] DEBUG - wire >> "POST /services/salesbinder
> HTTP/1.1[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,605] DEBUG - wire >> "Action:
> urn:createAccount[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept-Charset: UTF-8[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Content-Type:
> application/json[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "User-Agent:
> Java/1.7.0_79[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Host: localhost:8280[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept: text/html, image/gif,
> image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Connection: 
> keep-alive[\r][\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "Content-Length: 115[\r][\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[\r][\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "{[\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"apiUrl":"
> https://yas.salesbinder.com",[\n]";
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >>
> "[0x9]"apiKey":"046c9968e60bfe7853ee5a1f37849caa9d14937a",[\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"contextId":"2"[\n]"
> [2015-09-04 15:08:52,608]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 1

Re: [Dev] Carbon-deployment 4.5.2 released to staging

[Niranjan Karunanandham]

Hi Kasun,

I was successfully able to build the AS pack with the carbon-deployment
4.5.2 (staging url). I did a basic testing by uploading a webapp and
testing it.

Regards,
Nira

On Fri, Sep 4, 2015 at 7:11 PM, KasunG Gajasinghe  wrote:

> Hi,
>
> Please find the staging url -
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbondeployment-044/
>
> Thanks.
>
> --
>
> *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
>
>


-- 

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

Re: [Dev] Testing issues with BETA and RC2

[Elilmatha Sivanesan]

Hi Keerthika,

yes REQUEST_HOST_HEADER is used ,and its working fine with beta snapshot ,
but not with rc2.

Thanks.

On Fri, Sep 4, 2015 at 7:11 PM, Keerthika Mahendralingam  wrote:

> Hi Elil,
> You are getting *302 Moved Temporarily *as the response. Thats why you
> are getting the above error. Earlier we got the same error and used
> REQUEST_HOST_HEADER to resolve the issue.
>
> Thanks,
>
> On Fri, Sep 4, 2015 at 6:49 PM, Elilmatha Sivanesan 
> wrote:
>
>> Hi Malaka,
>>
>> No the above failing test case is for positive one (
>> CreateAccountWithMandatoryParameters ) same behaviour is observed on all
>> positive test cases.
>>
>> Thank you.
>>
>> On Fri, Sep 4, 2015 at 4:47 PM, Malaka Silva  wrote:
>>
>>> Hi Elilmatha,
>>>
>>> I guess this is due to [1]
>>>
>>> Previously behavior of ESB is invalid it seems and written test cases
>>> according to that.
>>>
>>> Failing test case is it a negative one?
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-3698
>>>
>>> On Fri, Sep 4, 2015 at 4:30 PM, Elilmatha Sivanesan 
>>> wrote:
>>>
 Hi all,

 Salesbinder connector integration test is running fine with
 wso2esb-4.9.0-BETA-SNAPSHOT ,But not with RC2.

 I have shared the wire log of one method, What can be the cause of the
 error.
 Is this the expected behaviour.

 with wso2esb-4.9.0-BETA-SNAPSHOT

 [2015-09-04 15:08:52,564]  INFO
 {org.wso2.carbon.automation.core.PlatformTestManager} -  Running the test
 method ---
 org.wso2.carbon.connector.integration.test.salesbinder.SalesbinderConnectorIntegrationTest.testCreateAccountWithMandatoryParameters
 
 [2015-09-04 15:08:52,605]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,605] DEBUG - wire >> "POST /services/salesbinder
 HTTP/1.1[\r][\n]"
 [2015-09-04 15:08:52,606]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,605] DEBUG - wire >> "Action:
 urn:createAccount[\r][\n]"
 [2015-09-04 15:08:52,606]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept-Charset: UTF-8[\r][\n]"
 [2015-09-04 15:08:52,606]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,606] DEBUG - wire >> "Content-Type:
 application/json[\r][\n]"
 [2015-09-04 15:08:52,606]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,606] DEBUG - wire >> "User-Agent:
 Java/1.7.0_79[\r][\n]"
 [2015-09-04 15:08:52,606]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,606] DEBUG - wire >> "Host: localhost:8280[\r][\n]"
 [2015-09-04 15:08:52,606]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept: text/html, image/gif,
 image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
 [2015-09-04 15:08:52,606]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,606] DEBUG - wire >> "Connection: keep-alive[\r][\n]"
 [2015-09-04 15:08:52,607]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,607] DEBUG - wire >> "Content-Length: 115[\r][\n]"
 [2015-09-04 15:08:52,607]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,607] DEBUG - wire >> "[\r][\n]"
 [2015-09-04 15:08:52,607]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,607] DEBUG - wire >> "{[\n]"
 [2015-09-04 15:08:52,607]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"apiUrl":"
 https://yas.salesbinder.com",[\n]";
 [2015-09-04 15:08:52,607]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,607] DEBUG - wire >>
 "[0x9]"apiKey":"046c9968e60bfe7853ee5a1f37849caa9d14937a",[\n]"
 [2015-09-04 15:08:52,607]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"contextId":"2"[\n]"
 [2015-09-04 15:08:52,608]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,608] DEBUG - wire >> "}"
 [2015-09-04 15:08:52,673]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
  [2015-09-04 15:08:52,673] ERROR - SynapseJsonPath #stringValueOf. Error
 evaluating JSON Path <$.id>. Returning empty result. Error>>> invalid path
 [2015-09-04 15:08:52,674]  INFO
 {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -

Re: [Dev] Testing issues with BETA and RC2

[Keerthika Mahendralingam]

Hi Elil,
You are getting *302 Moved Temporarily *as the response. Thats why you are
getting the above error. Earlier we got the same error and used
REQUEST_HOST_HEADER to resolve the issue.

Thanks,

On Fri, Sep 4, 2015 at 6:49 PM, Elilmatha Sivanesan 
wrote:

> Hi Malaka,
>
> No the above failing test case is for positive one (
> CreateAccountWithMandatoryParameters ) same behaviour is observed on all
> positive test cases.
>
> Thank you.
>
> On Fri, Sep 4, 2015 at 4:47 PM, Malaka Silva  wrote:
>
>> Hi Elilmatha,
>>
>> I guess this is due to [1]
>>
>> Previously behavior of ESB is invalid it seems and written test cases
>> according to that.
>>
>> Failing test case is it a negative one?
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-3698
>>
>> On Fri, Sep 4, 2015 at 4:30 PM, Elilmatha Sivanesan 
>> wrote:
>>
>>> Hi all,
>>>
>>> Salesbinder connector integration test is running fine with
>>> wso2esb-4.9.0-BETA-SNAPSHOT ,But not with RC2.
>>>
>>> I have shared the wire log of one method, What can be the cause of the
>>> error.
>>> Is this the expected behaviour.
>>>
>>> with wso2esb-4.9.0-BETA-SNAPSHOT
>>>
>>> [2015-09-04 15:08:52,564]  INFO
>>> {org.wso2.carbon.automation.core.PlatformTestManager} -  Running the test
>>> method ---
>>> org.wso2.carbon.connector.integration.test.salesbinder.SalesbinderConnectorIntegrationTest.testCreateAccountWithMandatoryParameters
>>> 
>>> [2015-09-04 15:08:52,605]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,605] DEBUG - wire >> "POST /services/salesbinder
>>> HTTP/1.1[\r][\n]"
>>> [2015-09-04 15:08:52,606]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,605] DEBUG - wire >> "Action:
>>> urn:createAccount[\r][\n]"
>>> [2015-09-04 15:08:52,606]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept-Charset: UTF-8[\r][\n]"
>>> [2015-09-04 15:08:52,606]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Content-Type:
>>> application/json[\r][\n]"
>>> [2015-09-04 15:08:52,606]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "User-Agent:
>>> Java/1.7.0_79[\r][\n]"
>>> [2015-09-04 15:08:52,606]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Host: localhost:8280[\r][\n]"
>>> [2015-09-04 15:08:52,606]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept: text/html, image/gif,
>>> image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
>>> [2015-09-04 15:08:52,606]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Connection: keep-alive[\r][\n]"
>>> [2015-09-04 15:08:52,607]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "Content-Length: 115[\r][\n]"
>>> [2015-09-04 15:08:52,607]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[\r][\n]"
>>> [2015-09-04 15:08:52,607]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "{[\n]"
>>> [2015-09-04 15:08:52,607]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"apiUrl":"
>>> https://yas.salesbinder.com",[\n]";
>>> [2015-09-04 15:08:52,607]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,607] DEBUG - wire >>
>>> "[0x9]"apiKey":"046c9968e60bfe7853ee5a1f37849caa9d14937a",[\n]"
>>> [2015-09-04 15:08:52,607]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"contextId":"2"[\n]"
>>> [2015-09-04 15:08:52,608]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,608] DEBUG - wire >> "}"
>>> [2015-09-04 15:08:52,673]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,673] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.id>. Returning empty result. Error>>> invalid path
>>> [2015-09-04 15:08:52,674]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
>>> evaluating JSON Path <$.lastName>. Returning empty result. Error>>> invalid
>>> path
>>> [2015-09-04 15:08:52,674]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>>  [2015-09-04 15:08:52,

[Dev] Carbon-deployment 4.5.2 released to staging

[KasunG Gajasinghe]

Hi,

Please find the staging url -
http://maven.wso2.org/nexus/content/repositories/orgwso2carbondeployment-044/

Thanks.

-- 

*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] Testing issues with BETA and RC2

[Elilmatha Sivanesan]

Hi Malaka,

No the above failing test case is for positive one (
CreateAccountWithMandatoryParameters ) same behaviour is observed on all
positive test cases.

Thank you.

On Fri, Sep 4, 2015 at 4:47 PM, Malaka Silva  wrote:

> Hi Elilmatha,
>
> I guess this is due to [1]
>
> Previously behavior of ESB is invalid it seems and written test cases
> according to that.
>
> Failing test case is it a negative one?
>
> [1] https://wso2.org/jira/browse/ESBJAVA-3698
>
> On Fri, Sep 4, 2015 at 4:30 PM, Elilmatha Sivanesan 
> wrote:
>
>> Hi all,
>>
>> Salesbinder connector integration test is running fine with
>> wso2esb-4.9.0-BETA-SNAPSHOT ,But not with RC2.
>>
>> I have shared the wire log of one method, What can be the cause of the
>> error.
>> Is this the expected behaviour.
>>
>> with wso2esb-4.9.0-BETA-SNAPSHOT
>>
>> [2015-09-04 15:08:52,564]  INFO
>> {org.wso2.carbon.automation.core.PlatformTestManager} -  Running the test
>> method ---
>> org.wso2.carbon.connector.integration.test.salesbinder.SalesbinderConnectorIntegrationTest.testCreateAccountWithMandatoryParameters
>> 
>> [2015-09-04 15:08:52,605]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,605] DEBUG - wire >> "POST /services/salesbinder
>> HTTP/1.1[\r][\n]"
>> [2015-09-04 15:08:52,606]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,605] DEBUG - wire >> "Action:
>> urn:createAccount[\r][\n]"
>> [2015-09-04 15:08:52,606]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept-Charset: UTF-8[\r][\n]"
>> [2015-09-04 15:08:52,606]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Content-Type:
>> application/json[\r][\n]"
>> [2015-09-04 15:08:52,606]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "User-Agent:
>> Java/1.7.0_79[\r][\n]"
>> [2015-09-04 15:08:52,606]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Host: localhost:8280[\r][\n]"
>> [2015-09-04 15:08:52,606]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept: text/html, image/gif,
>> image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
>> [2015-09-04 15:08:52,606]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Connection: keep-alive[\r][\n]"
>> [2015-09-04 15:08:52,607]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "Content-Length: 115[\r][\n]"
>> [2015-09-04 15:08:52,607]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[\r][\n]"
>> [2015-09-04 15:08:52,607]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "{[\n]"
>> [2015-09-04 15:08:52,607]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"apiUrl":"
>> https://yas.salesbinder.com",[\n]";
>> [2015-09-04 15:08:52,607]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,607] DEBUG - wire >>
>> "[0x9]"apiKey":"046c9968e60bfe7853ee5a1f37849caa9d14937a",[\n]"
>> [2015-09-04 15:08:52,607]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"contextId":"2"[\n]"
>> [2015-09-04 15:08:52,608]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,608] DEBUG - wire >> "}"
>> [2015-09-04 15:08:52,673]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,673] ERROR - SynapseJsonPath #stringValueOf. Error
>> evaluating JSON Path <$.id>. Returning empty result. Error>>> invalid path
>> [2015-09-04 15:08:52,674]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
>> evaluating JSON Path <$.lastName>. Returning empty result. Error>>> invalid
>> path
>> [2015-09-04 15:08:52,674]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
>> evaluating JSON Path <$.firstName>. Returning empty result. Error>>>
>> invalid path
>> [2015-09-04 15:08:52,674]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>  [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
>> evaluating JSON Path <$.email1>. Returning e

Re: [Dev] Carbon-commons released to staging

[KasunG Gajasinghe]

Released the repo.

Thanks.

On Fri, Sep 4, 2015 at 6:40 PM, Chanaka Fernando  wrote:

> Tested with ESB-490-RC4 with commons 4.4.7 and basic deployment
> syncronization works for proxy,api, sequence, CAR files. Looks fine.
>
> +1.
>
> Thanks,
> Chanaka
>
> On Fri, Sep 4, 2015 at 5:26 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi all,
>>
>> I've built the the product-as 5.3.0 with the commons 4.4.7 and did some
>> basic testing with depsync functionality. Looks good
>>
>> Thanks
>> /Thusitha
>>
>>
>> On Fri, Sep 4, 2015 at 4:54 PM, KasunG Gajasinghe 
>> wrote:
>>
>>> Hi,
>>>
>>> The staging repo url can be found here -
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carboncommons-043/
>>>
>>> Please test and verify.
>>>
>>> Thanks.
>>>
>>> --
>>>
>>> *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
>>>
>>>
>>
>>
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>>
>>
>
>
> --
> --
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>


-- 

*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] Carbon-commons released to staging

[Chanaka Fernando]

Tested with ESB-490-RC4 with commons 4.4.7 and basic deployment
syncronization works for proxy,api, sequence, CAR files. Looks fine.

+1.

Thanks,
Chanaka

On Fri, Sep 4, 2015 at 5:26 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi all,
>
> I've built the the product-as 5.3.0 with the commons 4.4.7 and did some
> basic testing with depsync functionality. Looks good
>
> Thanks
> /Thusitha
>
>
> On Fri, Sep 4, 2015 at 4:54 PM, KasunG Gajasinghe  wrote:
>
>> Hi,
>>
>> The staging repo url can be found here -
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carboncommons-043/
>>
>> Please test and verify.
>>
>> Thanks.
>>
>> --
>>
>> *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
>>
>>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>


-- 
--
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Prioritize requirements for MB

[Nuwan Silva]

We discussed this and hierarchical topics will be added. But, the MQTT
related stuff are not finalized will need to have a chat with Pamod and get
them done.

Regards,
NuwanS.

On Fri, Sep 4, 2015 at 6:33 PM, Ramith Jayasinghe  wrote:

> do we have hierarchical topics (for JMS and MQTT) covered?
>
>
> On Fri, Sep 4, 2015 at 6:30 PM, Indika Sampath  wrote:
>
>> Hi Dilini,
>>
>> We need to add shared durable topic subscription under JMS to this mind
>> map.
>>
>> Cheers!
>>
>> On Fri, Sep 4, 2015 at 5:31 PM, Dilini Gunatilake 
>> wrote:
>>
>>> Hi All,
>>>
>>> Please find the mind map attached herewith which includes the features
>>> of MB at high level. Out of that, we have prioritized the areas (with !
>>> mark) which we believe that should be covered by 25th. More features should
>>> be added to MQTT section and please free to add and share anything you
>>> think important.
>>>
>>> As discussed, we can collaboratively decide who will perform certain
>>> tests as the QA team would not be able to cover all the prioritized areas
>>> by 25th. As for the Alpha2 release, we will select a subset of these areas
>>> by Monday and cover it before the Beta release.
>>>
>>> Please feel free to share your thoughts.
>>>
>>> Thank you.
>>> Regards,
>>>
>>> --
>>>
>>> *Dilini GunatilakeSoftware Engineer - QA Team*
>>> Mobile : +94 (0) 771 162518
>>> dili...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Indika Sampath
>> Senior Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*Nuwan Silva*
*Senior Software Engineer - QA*
Mobile: +9477 980 4543

WSO2 Inc.
lean . enterprise . middlewear.
http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Prioritize requirements for MB

[Ramith Jayasinghe]

do we have hierarchical topics (for JMS and MQTT) covered?


On Fri, Sep 4, 2015 at 6:30 PM, Indika Sampath  wrote:

> Hi Dilini,
>
> We need to add shared durable topic subscription under JMS to this mind
> map.
>
> Cheers!
>
> On Fri, Sep 4, 2015 at 5:31 PM, Dilini Gunatilake 
> wrote:
>
>> Hi All,
>>
>> Please find the mind map attached herewith which includes the features of
>> MB at high level. Out of that, we have prioritized the areas (with ! mark)
>> which we believe that should be covered by 25th. More features should be
>> added to MQTT section and please free to add and share anything you think
>> important.
>>
>> As discussed, we can collaboratively decide who will perform certain
>> tests as the QA team would not be able to cover all the prioritized areas
>> by 25th. As for the Alpha2 release, we will select a subset of these areas
>> by Monday and cover it before the Beta release.
>>
>> Please feel free to share your thoughts.
>>
>> Thank you.
>> Regards,
>>
>> --
>>
>> *Dilini GunatilakeSoftware Engineer - QA Team*
>> Mobile : +94 (0) 771 162518
>> dili...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Indika Sampath
> Senior Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Prioritize requirements for MB

[Indika Sampath]

Hi Dilini,

We need to add shared durable topic subscription under JMS to this mind map.

Cheers!

On Fri, Sep 4, 2015 at 5:31 PM, Dilini Gunatilake  wrote:

> Hi All,
>
> Please find the mind map attached herewith which includes the features of
> MB at high level. Out of that, we have prioritized the areas (with ! mark)
> which we believe that should be covered by 25th. More features should be
> added to MQTT section and please free to add and share anything you think
> important.
>
> As discussed, we can collaboratively decide who will perform certain tests
> as the QA team would not be able to cover all the prioritized areas by
> 25th. As for the Alpha2 release, we will select a subset of these areas by
> Monday and cover it before the Beta release.
>
> Please feel free to share your thoughts.
>
> Thank you.
> Regards,
>
> --
>
> *Dilini GunatilakeSoftware Engineer - QA Team*
> Mobile : +94 (0) 771 162518
> dili...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon-commons released to staging

[Thusitha Thilina Dayaratne]

Hi all,

I've built the the product-as 5.3.0 with the commons 4.4.7 and did some
basic testing with depsync functionality. Looks good

Thanks
/Thusitha


On Fri, Sep 4, 2015 at 4:54 PM, KasunG Gajasinghe  wrote:

> Hi,
>
> The staging repo url can be found here -
> http://maven.wso2.org/nexus/content/repositories/orgwso2carboncommons-043/
>
> Please test and verify.
>
> Thanks.
>
> --
>
> *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
>
>


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

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] Nginx extension is available in Private PaaS 4.1.0

[Imesh Gunaratne]

Thanks Shavindri!! Appreciate your efforts!!

On Fri, Sep 4, 2015 at 3:28 PM, Shavindri Dissanayake 
wrote:

> Hi Imesh,
>
> Thank you! I will work with Reka and add the respective content. Further,
> created a doc JIRA to track the progress of this.
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-2313
>
>
> Thanks & Regards
> Shavindri Dissanayake
> Technical Writer
>
> WSO2 Inc.
> lean.enterprise.middleware
>
> On Fri, Sep 4, 2015 at 3:13 PM, Imesh Gunaratne  wrote:
>
>> It would be better to add this to the documentation.
>>
>> Thanks
>>
>> On Fri, Sep 4, 2015 at 3:11 PM, Reka Thirunavukkarasu 
>> wrote:
>>
>>> Thanks Imesh..!
>>>
>>> In addition to above configurations, when using api store and publisher
>>> fronted by nginx, we will need to install the certificate to client trust
>>> store of api maanger with below command. Then only we will be able to login
>>> to publisher or store.
>>>
>>> keytool -import -file server.cert  -keystore
>>> ../repository/resources/security/client-truststore.jks -alias "nginx"
>>>
>>> Thanks,
>>> Reka
>>>
>>>
>>> On Thu, Sep 3, 2015 at 9:58 PM, Imesh Gunaratne  wrote:
>>>
 Great work Reka on fixing the SSL configuration!!

 On Tue, Sep 1, 2015 at 3:17 PM, Reka Thirunavukkarasu 
 wrote:

> Please find the missing section as below:
>
> - Update /bin/nginx-extension.sh with below
> parameters
> -Dnginx.cert.path=/etc/nginx/ssl/server.cert
> -Dnginx.key.path=/etc/nginx/ssl/server.key
> -Dnginx.server.names.hash.bucket.size=128
> -Dconf.file.path=/etc/nginx/nginx.conf
>
> - Start /bin/nginx-extension.sh
>
> Extension will auto configure the nginx.conf with the members found
> from the Topology and it will start the nginx server.
>
> Thanks,
> Reka
>
>
> On Tue, Sep 1, 2015 at 3:13 PM, Reka Thirunavukkarasu 
> wrote:
>
>> Hi All,
>>
>> Nginx extension has been tested with SSL and made the necessary
>> configuration to be available with the default nginx extension. Please
>> follow below steps to configure nginx extension with PPaaS.
>>
>> - Install nginx with SSL module
>> - Build the niginx extension from [1].
>> - Deploy the built niginx extension
>> apache-stratos-nginx-extension-4.1.0-SNAPSHOT.zip to the machine where
>> nginx is installed to a preferred place
>> - unzip the extension
>> - Setup java
>> - Update /conf/jndi.properties with the
>> activemq ip which is used by PPaaS server
>> - Update /bin/nginx-extension.sh with below
>> parameters
>>
>>
>>
>> [1]
>> https://github.com/wso2/product-private-paas/tree/master/extensions/load-balancer/nginx-extension
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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


>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>


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

[Dev] [VOTE] Release WSO2 Governance Registry 5.0.0 RC3

[Chandana Napagoda]

Hi Devs,

*This is the RC3 release candidate of WSO2 Governance Registry 5.0.0 *

This release fixes the following issues:

https://wso2.org/jira/browse/REGISTRY-2927?filter=12388

Please download, test and vote. Please refer the release verification guide
for detailed information on verifying this release.

*Source & binary distribution files:*
http://maven.wso2.org/nexus/content/repositories/orgwso2greg-042/org/wso2/greg/wso2greg/5.0.0/

*Maven staging repo:*
http://maven.wso2.org/nexus/content/repositories/orgwso2greg-042/

*The tag to be voted upon:*
https://github.com/wso2/product-greg/releases/tag/v5.0.0-rc3


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

Thanks and Regards
G-Reg team

-- 
*Chandana Napagoda*
Senior Software Engineer
WSO2 Inc. - http://wso2.org

*Email  :  chand...@wso2.com **Mobile : +94718169299
<%2B94718169299>*

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

[Dev] Carbon-commons released to staging

[KasunG Gajasinghe]

Hi,

The staging repo url can be found here -
http://maven.wso2.org/nexus/content/repositories/orgwso2carboncommons-043/

Please test and verify.

Thanks.

-- 

*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] Testing issues with BETA and RC2

[Malaka Silva]

Hi Elilmatha,

I guess this is due to [1]

Previously behavior of ESB is invalid it seems and written test cases
according to that.

Failing test case is it a negative one?

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

On Fri, Sep 4, 2015 at 4:30 PM, Elilmatha Sivanesan 
wrote:

> Hi all,
>
> Salesbinder connector integration test is running fine with
> wso2esb-4.9.0-BETA-SNAPSHOT ,But not with RC2.
>
> I have shared the wire log of one method, What can be the cause of the
> error.
> Is this the expected behaviour.
>
> with wso2esb-4.9.0-BETA-SNAPSHOT
>
> [2015-09-04 15:08:52,564]  INFO
> {org.wso2.carbon.automation.core.PlatformTestManager} -  Running the test
> method ---
> org.wso2.carbon.connector.integration.test.salesbinder.SalesbinderConnectorIntegrationTest.testCreateAccountWithMandatoryParameters
> 
> [2015-09-04 15:08:52,605]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,605] DEBUG - wire >> "POST /services/salesbinder
> HTTP/1.1[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,605] DEBUG - wire >> "Action:
> urn:createAccount[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept-Charset: UTF-8[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Content-Type:
> application/json[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "User-Agent:
> Java/1.7.0_79[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Host: localhost:8280[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept: text/html, image/gif,
> image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
> [2015-09-04 15:08:52,606]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,606] DEBUG - wire >> "Connection: keep-alive[\r][\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "Content-Length: 115[\r][\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[\r][\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "{[\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"apiUrl":"
> https://yas.salesbinder.com",[\n]";
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >>
> "[0x9]"apiKey":"046c9968e60bfe7853ee5a1f37849caa9d14937a",[\n]"
> [2015-09-04 15:08:52,607]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"contextId":"2"[\n]"
> [2015-09-04 15:08:52,608]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,608] DEBUG - wire >> "}"
> [2015-09-04 15:08:52,673]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,673] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.id>. Returning empty result. Error>>> invalid path
> [2015-09-04 15:08:52,674]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.lastName>. Returning empty result. Error>>> invalid
> path
> [2015-09-04 15:08:52,674]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.firstName>. Returning empty result. Error>>>
> invalid path
> [2015-09-04 15:08:52,674]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.email1>. Returning empty result. Error>>> invalid
> path
> [2015-09-04 15:08:52,675]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>  [2015-09-04 15:08:52,675] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.price>. Returning empty result. Error>>> invalid
> path
> [2015-09-04 15:08:52,675]  INFO

[Dev] Testing issues with BETA and RC2

[Elilmatha Sivanesan]

Hi all,

Salesbinder connector integration test is running fine with
wso2esb-4.9.0-BETA-SNAPSHOT ,But not with RC2.

I have shared the wire log of one method, What can be the cause of the
error.
Is this the expected behaviour.

with wso2esb-4.9.0-BETA-SNAPSHOT

[2015-09-04 15:08:52,564]  INFO
{org.wso2.carbon.automation.core.PlatformTestManager} -  Running the test
method ---
org.wso2.carbon.connector.integration.test.salesbinder.SalesbinderConnectorIntegrationTest.testCreateAccountWithMandatoryParameters

[2015-09-04 15:08:52,605]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,605] DEBUG - wire >> "POST /services/salesbinder
HTTP/1.1[\r][\n]"
[2015-09-04 15:08:52,606]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,605] DEBUG - wire >> "Action:
urn:createAccount[\r][\n]"
[2015-09-04 15:08:52,606]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept-Charset: UTF-8[\r][\n]"
[2015-09-04 15:08:52,606]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,606] DEBUG - wire >> "Content-Type:
application/json[\r][\n]"
[2015-09-04 15:08:52,606]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,606] DEBUG - wire >> "User-Agent:
Java/1.7.0_79[\r][\n]"
[2015-09-04 15:08:52,606]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,606] DEBUG - wire >> "Host: localhost:8280[\r][\n]"
[2015-09-04 15:08:52,606]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,606] DEBUG - wire >> "Accept: text/html, image/gif,
image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
[2015-09-04 15:08:52,606]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,606] DEBUG - wire >> "Connection: keep-alive[\r][\n]"
[2015-09-04 15:08:52,607]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,607] DEBUG - wire >> "Content-Length: 115[\r][\n]"
[2015-09-04 15:08:52,607]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,607] DEBUG - wire >> "[\r][\n]"
[2015-09-04 15:08:52,607]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,607] DEBUG - wire >> "{[\n]"
[2015-09-04 15:08:52,607]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"apiUrl":"
https://yas.salesbinder.com",[\n]";
[2015-09-04 15:08:52,607]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,607] DEBUG - wire >>
"[0x9]"apiKey":"046c9968e60bfe7853ee5a1f37849caa9d14937a",[\n]"
[2015-09-04 15:08:52,607]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,607] DEBUG - wire >> "[0x9]"contextId":"2"[\n]"
[2015-09-04 15:08:52,608]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,608] DEBUG - wire >> "}"
[2015-09-04 15:08:52,673]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,673] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path <$.id>. Returning empty result. Error>>> invalid path
[2015-09-04 15:08:52,674]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path <$.lastName>. Returning empty result. Error>>> invalid
path
[2015-09-04 15:08:52,674]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path <$.firstName>. Returning empty result. Error>>>
invalid path
[2015-09-04 15:08:52,674]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,674] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path <$.email1>. Returning empty result. Error>>> invalid
path
[2015-09-04 15:08:52,675]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,675] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path <$.price>. Returning empty result. Error>>> invalid
path
[2015-09-04 15:08:52,675]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,675] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path <$.name>. Returning empty result. Error>>> invalid path
[2015-09-04 15:08:52,676]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2015-09-04 15:08:52,676] ERROR - SynapseJsonPath #stringValueOf. Error
evaluating JSON Path <$.page>. Returning empty result. Error>>> in

Re: [Dev] Jenkins build became unstable: wso2-axis2 #840

[Supun Malinga]

So the next build passed successfully. We will keep an eye on the builds if
this happens again.
https://wso2.org/jenkins/job/wso2-axis2/842/

thanks,

On Fri, Sep 4, 2015 at 2:17 PM, Supun Malinga  wrote:

> Resending to dev@ (previous mail rejected cos of too many recipients )
>
>
> On Fri, Sep 4, 2015 at 2:14 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> Here it is not possible to keep the server running for all test cases,
>> cos it starts the server with different configs for each test scenario. So
>> I added an improvement to the server start logic to wait until the server
>> is stopped is its already running. Also I added a log to print any errors
>> at server starting. So if in case the issue come again we have more info..
>> PR:
>> https://github.com/wso2/wso2-axis2/pull/57
>>
>> Let me know if there are any issues/ further suggestions before merging
>> the PR..
>>
>> thanks,
>>
>>
>> On Thu, Sep 3, 2015 at 6:57 PM, Supun Malinga  wrote:
>>
>>> Hi,
>>>
>>> This is a connection refused error.
>>> I looked into the code of the failed test case. Here it uses a random
>>> tcp port to start a http server for testing.
>>> There is a couple of test cases that use the same simple http server
>>> with the derived port, but only one is failing. While digging into it I
>>> found that simple http server is stopped and started back for the separate
>>> test cases. So there can be several causes for this to fail.
>>>
>>> I had a chat with Azeez and best option seems to be keep the server
>>> running for the both test cases. Will look into fixing this.
>>>
>>> thanks,
>>>
>>>
>>> On Thu, Sep 3, 2015 at 12:26 AM,  wrote:
>>>
 See 


>>>
>>>
>>> --
>>> Supun Malinga,
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>> http://wso2.com
>>> email: sup...@wso2.com 
>>> mobile: +94 (0)71 56 91 321
>>>
>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> email: sup...@wso2.com 
>> mobile: +94 (0)71 56 91 321
>>
>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>



-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Sagara Gunathunga]

On Fri, Sep 4, 2015 at 2:11 PM, Chandana Napagoda  wrote:

> Hi Pavithra,
>
> As a workaround one can use rsync or copy secondary user store
> configuration in to other nodes.
>

I'm not quite sure whether dev or qa team have tested DipSync in G-Reg
ever, because we don't have any such direct use case, even current context
DipSync came in to the picture because of secondary user store requirement,
may be we can test this from next release.

Other concern is enabling DipSync among G-Reg nodes just because of
secondary user store ( which also not frequently change) support may
complicate the deployment architecture instead rsync or manual sync of
secondary user store definition files is much preferable, hence IMHO this
should be a less priority item.

Thanks !

>
> Regards,
> Chandana
>
> On Fri, Sep 4, 2015 at 12:39 PM, Pavithra Madurangi 
> wrote:
>
>>
>>
>> On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga 
>> wrote:
>>
>>>
>>>
>>> On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:
>>>
 Thanks Prasanna. Please update the JIRA as well.

 In between there was a dep sync issue reported with ESB [1] with the
 recent fix from carbon commons. Just want to find out whether this has any
 effect on GREG product for scenarios like secondary user store, API-M
 integration (May not be an issue since we suggest to use APIM 1.9.1 for GW)
 or install WSO2 AS features and use it (which is anyway very unlikely
 scenario).

>>>
>>> It's hard to think about DipSync use cases in G-Reg.
>>>
>>
>> ​Agree to this.
>>
>> But our concern was secondary user stores. If we have secondary user
>> stores in a multi node deployment, won't there be any issues because of
>> this bug (since it's one place where depSync is needed)?
>>
>> There's a possibility of managing secondary user stores without having
>> depSync. What we wanted to get clarified was whether that's the
>> approach/workaround we suggest ?
>>
>> Regards,
>> pavithra
>>
>>>
>>> Thanks !
>>>

 1. ESBJAVA-4156 





 On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
 wrote:

> Hi Thayalan,
>
> We fixed the issue REGISTRY-2927
>  . Now users can re-login
> from the same window in a fresh pack.
>
> Thanks
>
> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>
>> Hi Team,
>>
>> I've observed from the standalone pack without any changes user has
>> not been allowed to re-login  to the store [1]. However this is working
>> fine for publisher. As per the suggestion in [1] hostname has to be set 
>> in
>> carbon.xml. However in the default pack SSO enabled for store/publisher 
>> and
>> Hostname tag is commented. Even uncomment them and set to IP or localhost
>> too not working as suggested in the JIRA. From the end user perspective
>> user should allow to re-login from the same window session from the fresh
>> pack. Is this is something we need to fix before releasing them?
>>
>> 1.REGISTRY-2927 
>>
>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
>> wrote:
>>
>>> -1,
>>>
>>> We found an issue with solr related logging configuration and this
>>> issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>>>
>>> Step to reproduce this issue:
>>>
>>> Go to Main --> Registry search and search by any value.
>>> Then navigate to Configure --> Logging section.
>>> Exceptions are logged in console and "Global Log4J Configuration"
>>> and "Configure Log4J Appenders" views are not loading due to the above
>>> issue.
>>>
>>> Created a JIRA[1] to track above issue and will release release
>>> G-Reg 5.0.0 RC3 pack ASAP.
>>>
>>> [1]. https://wso2.org/jira/browse/WSAS-2120
>>>
>>> Regards,
>>> Chandana
>>>
>>>
>>> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda <
>>> chand...@wso2.com> wrote:
>>>
 Hi Pubudu,

 Since we have already released RC2 pack and component repos, we can
 not update above pages now. We will update context specific pages for
 coming up 5.0.1 release. Meantime, you can refer wiki based 
 documentation
 available here [1].

 [1].
 https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation

 Regards,
 Chandana

 On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan >>> > wrote:

> Hi Chandana,
>
> Since the Help page, context specific pages are out-dated we need
> to update those to reflect most recent information. Can you please 
> address
> this issue as required? Please find the relevant ticket below. Thanks.
>
> https://wso2.o

Re: [Dev] [PPaaS] Nginx extension is available in Private PaaS 4.1.0

[Imesh Gunaratne]

It would be better to add this to the documentation.

Thanks

On Fri, Sep 4, 2015 at 3:11 PM, Reka Thirunavukkarasu  wrote:

> Thanks Imesh..!
>
> In addition to above configurations, when using api store and publisher
> fronted by nginx, we will need to install the certificate to client trust
> store of api maanger with below command. Then only we will be able to login
> to publisher or store.
>
> keytool -import -file server.cert  -keystore
> ../repository/resources/security/client-truststore.jks -alias "nginx"
>
> Thanks,
> Reka
>
>
> On Thu, Sep 3, 2015 at 9:58 PM, Imesh Gunaratne  wrote:
>
>> Great work Reka on fixing the SSL configuration!!
>>
>> On Tue, Sep 1, 2015 at 3:17 PM, Reka Thirunavukkarasu 
>> wrote:
>>
>>> Please find the missing section as below:
>>>
>>> - Update /bin/nginx-extension.sh with below
>>> parameters
>>> -Dnginx.cert.path=/etc/nginx/ssl/server.cert
>>> -Dnginx.key.path=/etc/nginx/ssl/server.key
>>> -Dnginx.server.names.hash.bucket.size=128
>>> -Dconf.file.path=/etc/nginx/nginx.conf
>>>
>>> - Start /bin/nginx-extension.sh
>>>
>>> Extension will auto configure the nginx.conf with the members found from
>>> the Topology and it will start the nginx server.
>>>
>>> Thanks,
>>> Reka
>>>
>>>
>>> On Tue, Sep 1, 2015 at 3:13 PM, Reka Thirunavukkarasu 
>>> wrote:
>>>
 Hi All,

 Nginx extension has been tested with SSL and made the necessary
 configuration to be available with the default nginx extension. Please
 follow below steps to configure nginx extension with PPaaS.

 - Install nginx with SSL module
 - Build the niginx extension from [1].
 - Deploy the built niginx extension
 apache-stratos-nginx-extension-4.1.0-SNAPSHOT.zip to the machine where
 nginx is installed to a preferred place
 - unzip the extension
 - Setup java
 - Update /conf/jndi.properties with the activemq
 ip which is used by PPaaS server
 - Update /bin/nginx-extension.sh with below
 parameters



 [1]
 https://github.com/wso2/product-private-paas/tree/master/extensions/load-balancer/nginx-extension

 --
 Reka Thirunavukkarasu
 Senior Software Engineer,
 WSO2, Inc.:http://wso2.com,
 Mobile: +94776442007



>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>


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

Re: [Dev] [PPaaS] Nginx extension is available in Private PaaS 4.1.0

[Reka Thirunavukkarasu]

Thanks Imesh..!

In addition to above configurations, when using api store and publisher
fronted by nginx, we will need to install the certificate to client trust
store of api maanger with below command. Then only we will be able to login
to publisher or store.

keytool -import -file server.cert  -keystore
../repository/resources/security/client-truststore.jks -alias "nginx"

Thanks,
Reka

On Thu, Sep 3, 2015 at 9:58 PM, Imesh Gunaratne  wrote:

> Great work Reka on fixing the SSL configuration!!
>
> On Tue, Sep 1, 2015 at 3:17 PM, Reka Thirunavukkarasu 
> wrote:
>
>> Please find the missing section as below:
>>
>> - Update /bin/nginx-extension.sh with below
>> parameters
>> -Dnginx.cert.path=/etc/nginx/ssl/server.cert
>> -Dnginx.key.path=/etc/nginx/ssl/server.key
>> -Dnginx.server.names.hash.bucket.size=128
>> -Dconf.file.path=/etc/nginx/nginx.conf
>>
>> - Start /bin/nginx-extension.sh
>>
>> Extension will auto configure the nginx.conf with the members found from
>> the Topology and it will start the nginx server.
>>
>> Thanks,
>> Reka
>>
>>
>> On Tue, Sep 1, 2015 at 3:13 PM, Reka Thirunavukkarasu 
>> wrote:
>>
>>> Hi All,
>>>
>>> Nginx extension has been tested with SSL and made the necessary
>>> configuration to be available with the default nginx extension. Please
>>> follow below steps to configure nginx extension with PPaaS.
>>>
>>> - Install nginx with SSL module
>>> - Build the niginx extension from [1].
>>> - Deploy the built niginx extension
>>> apache-stratos-nginx-extension-4.1.0-SNAPSHOT.zip to the machine where
>>> nginx is installed to a preferred place
>>> - unzip the extension
>>> - Setup java
>>> - Update /conf/jndi.properties with the activemq
>>> ip which is used by PPaaS server
>>> - Update /bin/nginx-extension.sh with below
>>> parameters
>>>
>>>
>>>
>>> [1]
>>> https://github.com/wso2/product-private-paas/tree/master/extensions/load-balancer/nginx-extension
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *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
>
>


-- 
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [App Cloud] AF Datasource API takes a long time to respond

[Kavith Lokuhewage]

correction:

* more than 60 seconds.

On Fri, Sep 4, 2015 at 2:21 PM, Kavith Lokuhewage  wrote:

> Hi,
>
> Seems this issue is only there in App Cloud. Tested this in a standalone
> AF deployment and it works without any issue. Sometimes it takes more than
> seconds to get the response from App Cloud API.
>
> Thanks,
>
> On Thu, Sep 3, 2015 at 12:58 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi all,
>>
>> While testing DevStudio with latest app cloud, I could notice that
>> following API  takes a very long time to respond.
>>
>> API :
>> https://apps.cloud.wso2.com/appmgt/site/blocks/resources/datasource/get/ajax/list.jag?action=getDatasources&applicationKey=testapplicationone
>> 
>>
>> This is invoked (along with three other APIs) once a user opens an
>> application from AF Application List View in DevStudio. However, due to
>> this application open doesn't work smoothly.
>>
>> Just wanted to know whether this is something temporary. FYI, this was
>> not experienced in previous testing round with App Cloud ( old version).
>>
>> 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 
>



-- 
*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] [App Cloud] AF Datasource API takes a long time to respond

[Kavith Lokuhewage]

Hi,

Seems this issue is only there in App Cloud. Tested this in a standalone AF
deployment and it works without any issue. Sometimes it takes more than
seconds to get the response from App Cloud API.

Thanks,

On Thu, Sep 3, 2015 at 12:58 PM, Kavith Lokuhewage  wrote:

> Hi all,
>
> While testing DevStudio with latest app cloud, I could notice that
> following API  takes a very long time to respond.
>
> API :
> https://apps.cloud.wso2.com/appmgt/site/blocks/resources/datasource/get/ajax/list.jag?action=getDatasources&applicationKey=testapplicationone
> 
>
> This is invoked (along with three other APIs) once a user opens an
> application from AF Application List View in DevStudio. However, due to
> this application open doesn't work smoothly.
>
> Just wanted to know whether this is something temporary. FYI, this was not
> experienced in previous testing round with App Cloud ( old version).
>
> 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

Re: [Dev] Jenkins build became unstable: wso2-axis2 #840

[Supun Malinga]

Resending to dev@ (previous mail rejected cos of too many recipients )

On Fri, Sep 4, 2015 at 2:14 PM, Supun Malinga  wrote:

> Hi,
>
> Here it is not possible to keep the server running for all test cases, cos
> it starts the server with different configs for each test scenario. So I
> added an improvement to the server start logic to wait until the server is
> stopped is its already running. Also I added a log to print any errors at
> server starting. So if in case the issue come again we have more info..
> PR:
> https://github.com/wso2/wso2-axis2/pull/57
>
> Let me know if there are any issues/ further suggestions before merging
> the PR..
>
> thanks,
>
>
> On Thu, Sep 3, 2015 at 6:57 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> This is a connection refused error.
>> I looked into the code of the failed test case. Here it uses a random tcp
>> port to start a http server for testing.
>> There is a couple of test cases that use the same simple http server with
>> the derived port, but only one is failing. While digging into it I found
>> that simple http server is stopped and started back for the separate test
>> cases. So there can be several causes for this to fail.
>>
>> I had a chat with Azeez and best option seems to be keep the server
>> running for the both test cases. Will look into fixing this.
>>
>> thanks,
>>
>>
>> On Thu, Sep 3, 2015 at 12:26 AM,  wrote:
>>
>>> See 
>>>
>>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> email: sup...@wso2.com 
>> mobile: +94 (0)71 56 91 321
>>
>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>



-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Chandana Napagoda]

Hi Pavithra,

As a workaround one can use rsync or copy secondary user store
configuration in to other nodes.

Regards,
Chandana

On Fri, Sep 4, 2015 at 12:39 PM, Pavithra Madurangi 
wrote:

>
>
> On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga 
> wrote:
>
>>
>>
>> On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:
>>
>>> Thanks Prasanna. Please update the JIRA as well.
>>>
>>> In between there was a dep sync issue reported with ESB [1] with the
>>> recent fix from carbon commons. Just want to find out whether this has any
>>> effect on GREG product for scenarios like secondary user store, API-M
>>> integration (May not be an issue since we suggest to use APIM 1.9.1 for GW)
>>> or install WSO2 AS features and use it (which is anyway very unlikely
>>> scenario).
>>>
>>
>> It's hard to think about DipSync use cases in G-Reg.
>>
>
> ​Agree to this.
>
> But our concern was secondary user stores. If we have secondary user
> stores in a multi node deployment, won't there be any issues because of
> this bug (since it's one place where depSync is needed)?
>
> There's a possibility of managing secondary user stores without having
> depSync. What we wanted to get clarified was whether that's the
> approach/workaround we suggest ?
>
> Regards,
> pavithra
>
>>
>> Thanks !
>>
>>>
>>> 1. ESBJAVA-4156 
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
>>> wrote:
>>>
 Hi Thayalan,

 We fixed the issue REGISTRY-2927
  . Now users can re-login
 from the same window in a fresh pack.

 Thanks

 On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:

> Hi Team,
>
> I've observed from the standalone pack without any changes user has
> not been allowed to re-login  to the store [1]. However this is working
> fine for publisher. As per the suggestion in [1] hostname has to be set in
> carbon.xml. However in the default pack SSO enabled for store/publisher 
> and
> Hostname tag is commented. Even uncomment them and set to IP or localhost
> too not working as suggested in the JIRA. From the end user perspective
> user should allow to re-login from the same window session from the fresh
> pack. Is this is something we need to fix before releasing them?
>
> 1.REGISTRY-2927 
>
> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
> wrote:
>
>> -1,
>>
>> We found an issue with solr related logging configuration and this
>> issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>>
>> Step to reproduce this issue:
>>
>> Go to Main --> Registry search and search by any value.
>> Then navigate to Configure --> Logging section.
>> Exceptions are logged in console and "Global Log4J Configuration" and
>> "Configure Log4J Appenders" views are not loading due to the above issue.
>>
>> Created a JIRA[1] to track above issue and will release release G-Reg
>> 5.0.0 RC3 pack ASAP.
>>
>> [1]. https://wso2.org/jira/browse/WSAS-2120
>>
>> Regards,
>> Chandana
>>
>>
>> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda > > wrote:
>>
>>> Hi Pubudu,
>>>
>>> Since we have already released RC2 pack and component repos, we can
>>> not update above pages now. We will update context specific pages for
>>> coming up 5.0.1 release. Meantime, you can refer wiki based 
>>> documentation
>>> available here [1].
>>>
>>> [1].
>>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>>
>>> Regards,
>>> Chandana
>>>
>>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hi Chandana,

 Since the Help page, context specific pages are out-dated we need
 to update those to reflect most recent information. Can you please 
 address
 this issue as required? Please find the relevant ticket below. Thanks.

 https://wso2.org/jira/browse/REGISTRY-2910

 Cheers,

 Pubudu D.P
 Senior Software Engineer - QA Team | WSO2 inc.
 Mobile : +94775464547

 On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <
 nirde...@wso2.com> wrote:

> The context sensitive help links are in the product UIs. AFAIK,
> these links are component-based rather than product based? Please 
> correct
> me if I am wrong.
>
> If they are component-based, we cannot link to the wiki of a
> specific product from there as many other products might also be 
> using the
> same component.
>
> Maybe we should simply disable these help links until we find a
> better way to maintain them.
>
> 

Re: [Dev] Data Source Capp deployer feature implementation

[Anjana Fernando]

Pull request merged, thanks Rajith.

Cheers,
Anjana.

On Fri, Sep 4, 2015 at 12:43 PM, Rajith Vitharana  wrote:

> Hi All,
>
> Implementation for Data source Capp deployment feature is done and you can
> find the pull request in [1]. Discussion about the implementation happened
> in mail thread [2] in Architecture mailing list. Related jira is in [3] and
> the pull request data and sample car file is attached in the jira. You can
> use this feature once pull request is merged and carbon-commons is released.
>
> [1] - https://github.com/wso2/carbon-commons/pull/160
> [2] - Implementing Datasource Deployer
> [3] - https://wso2.org/jira/browse/DS-907
>
> Thanks,
> --
> Rajith Vitharana
>
> Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94715883223
> Blog : http://lankavitharana.blogspot.com/
>



-- 
*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 G-Reg 5.0.0 RC 2

[Thayalan]

Hi Team,

Could you please let us know the ETA for RC3 pack and planned GA
rescheduled date? This is to reduce the scope and test accordingly.

On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda  wrote:

> -1,
>
> We found an issue with solr related logging configuration and this issue
> is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>
> Step to reproduce this issue:
>
> Go to Main --> Registry search and search by any value.
> Then navigate to Configure --> Logging section.
> Exceptions are logged in console and "Global Log4J Configuration" and
> "Configure Log4J Appenders" views are not loading due to the above issue.
>
> Created a JIRA[1] to track above issue and will release release G-Reg
> 5.0.0 RC3 pack ASAP.
>
> [1]. https://wso2.org/jira/browse/WSAS-2120
>
> Regards,
> Chandana
>
>
> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
> wrote:
>
>> Hi Pubudu,
>>
>> Since we have already released RC2 pack and component repos, we can not
>> update above pages now. We will update context specific pages for coming up
>> 5.0.1 release. Meantime, you can refer wiki based documentation available
>> here [1].
>>
>> [1].
>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>
>> Regards,
>> Chandana
>>
>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Chandana,
>>>
>>> Since the Help page, context specific pages are out-dated we need to
>>> update those to reflect most recent information. Can you please address
>>> this issue as required? Please find the relevant ticket below. Thanks.
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2910
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe 
>>> wrote:
>>>
 The context sensitive help links are in the product UIs. AFAIK, these
 links are component-based rather than product based? Please correct me if I
 am wrong.

 If they are component-based, we cannot link to the wiki of a specific
 product from there as many other products might also be using the same
 component.

 Maybe we should simply disable these help links until we find a better
 way to maintain them.

 Thanks,
 -Nirdesha

 On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
 wrote:

> Hi Nirdesha,
>
> Can we please point the current context sensitive help pages to
> relevant product documentation of GReg 5.0.0 release?
>
> Cheers,
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
> wrote:
>
>>
>>
>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
>> evanth...@wso2.com> wrote:
>>
>>> Ack!
>>>
>>> @Chalitha/Thaya/Pubudu. Please note.
>>>
>>
>> And all the context sensitive help pages  are outdated .
>>
>> -Ajith
>>
>>
>>>
>>> Regards,
>>> Evanthika Amarasiri
>>> Senior Technical Lead  - Quality Assurance
>>> Mobile: +94773125935
>>> Blog: evanthika.blogspot.com
>>>
>>> wso2.com lean.enterprise.middleware
>>>
>>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
>>> wrote:
>>>
 Hi All

 This is non a bug but please fix the about page if possible because
 this is a major release. (find the attached image)

 -Ajith





 On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <
 prasa...@wso2.com> wrote:

> Hi All,
>
> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>
> This release fixes the following issues:
>
> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
> https://wso2.org/jira/browse/REGISTRY-2908
>
> Please download, test and vote. Please refer the release
> verification guide for detailed information on verifying this release.
>
> *Source & binary distribution files:*
>
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>
> *Maven staging repo:*
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>
> *The tag to be voted upon:*
>
> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>
>
>
> [*+*] Stable - go ahead and release
>
> [*-*]  Broken - do not release (explain why)
>
> Thanks and Regards
> G-Reg team
>
> Prasanna Dangalla
> Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
> cell: +94 718 11 27 51
> twitter: @prasa77
>
> _

Re: [Dev] [App Factory] UX/UI Incorporation

[Thusitha Kalugamage]

Hi All,

Build & Deploy pages added to repo [1]
b0c9cab853f96c7f42cbd8fac4f99b66068e


Regards,


On Mon, Aug 24, 2015 at 9:46 AM, Imesh Chandrasiri  wrote:

> The previous page I shared was the modified logs page.
>
>
>
> On Mon, Aug 24, 2015 at 9:44 AM, Imesh Chandrasiri 
> wrote:
>
>> Hi All,
>>
>> We've added a new page to the git.
>>
>> [1] app_logs.html
>> 
>>
>>
>>
>> On Mon, Aug 24, 2015 at 9:39 AM, Dhanuka De Silva 
>> wrote:
>>
>>> Looping Imesh :)
>>>
>>> Cheers
>>>
>>> On Mon, Jul 27, 2015 at 8:22 PM, Mahesh Chinthaka 
>>> wrote:
>>>
 Adding Anuruddha and Samith

 On Mon, Jul 27, 2015 at 5:48 PM, Dakshika Jayathilaka <
 daksh...@wso2.com> wrote:

> Hi All,
>
> We have added custom URL mapping pages to git.
>
> 1. custom_url_initial.html
> 
> 2. custom_url_listing.html
> 
>
> Regards,
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Senior Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Fri, Jul 24, 2015 at 5:32 PM, Dakshika Jayathilaka <
> daksh...@wso2.com> wrote:
>
>> Hi All,
>>
>> We have added another page to git.
>>
>> 4. database_permission_listing.html
>> 
>>
>> Regards,
>>
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Fri, Jul 17, 2015 at 6:03 PM, Dakshika Jayathilaka <
>> daksh...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> We have added few other pages into git.
>>>
>>> 1. database_initial.html
>>> 
>>> 2. database_initial_listing.html
>>> 
>>> 3. database_new.html
>>> 
>>>
>>> Regards,
>>>
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Tue, Jul 14, 2015 at 10:10 AM, Dakshika Jayathilaka <
>>> daksh...@wso2.com> wrote:
>>>
 Hi All,

 We have added  content loading methods to
 cloud_app_details_initial_content_load.html
 
 .
 you can select any div and call 'show'/ 'hide' method.

 *Sample: *

 *$('selector').loading('show/hide');*

 *Preview: *


 https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/cloud_app_details_initial_content_load.html

 Regards,

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

 On Mon, Jul 13, 2015 at 5:00 PM, Mahesh Chinthaka >>> > wrote:

> adding RoshanD. He is doing  009_cloud_app_details_initial.html
> 
>  page.
>
> On Mon, Jul 13, 2015 at 3:53 PM, Dakshika Jayathilaka <
> daksh...@wso2.com> wrote:
>
>> Hi All,
>>
>> We have added notification updates on below pages.
>>
>> 1.  form_notification.html
>> 
>>
>> 2. block type notification - 009_cloud_app_details_initial.html
>> 
>>
>> please be kind enough to merge above changes.
>>
>> Regards,
>>
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Wed, Jul 8, 2015 at 6:19 PM, Dakshika Jayathilaka <
>> daksh...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> W

Re: [Dev] Transaction in JMSMessageProcessor

[John Hawkins]

Hi Folks,

I've just had a customer asking me this question as they are trying to do
the work under a tran as well. I've read the MessageProcessor code and it
appears to do it all under AUTO_ACK. I can't see it reading the axis.xml
file either - but I'm sure it does somewhere. So, maybe I read the code
wrong (wouldn't be the first time !Aalthough the AUTO_ACK  does appear to
be hardcoded.).

Can anyone confirm my findings please - and whether we intend to change
this behaviour (if what I found is correct).

many thanks,
John.

John Hawkins
Director: Solutions Architecture


On Tue, Sep 1, 2015 at 12:05 PM, John Hawkins  wrote:

> Hi All,
>
> I'm trying to figure out if and how I enable transactions on the
> JMSMessageProcessor
>
> I am using QPID as the message broker. I have not set any JMS transports
> properties in conf/axis2.xml. I think that the JMSMessageProcessor is using
> conf/axis2/axis2_blocking_client.xml by default - is that correct ? (I read
> it in a blog but I can't see it specified in the docs).
>
> As I have no jms transports set up in my axis2_blocking_client.xml I'm
> assuming that it's also not being read as my JMSMessageProcess is working
> just fine?
>
> So, I'm therefore assuming that my MessageProcessor is not working under a
> tran (and is probably using AUTO_ACK) which will lose messages in case of a
> failure.
>
>
> If all the above is correct then can I set up axis2_blocking_client.xml so
> that messages are pulled from the queue by JMSMessageProcessor  under a
> true xa or JTA tran?
>
> many thanks for your help,
> John.
>
>
>
> John Hawkins
> Director: Solutions Architecture
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Data Source Capp deployer feature implementation

[Rajith Vitharana]

Hi All,

Implementation for Data source Capp deployment feature is done and you can
find the pull request in [1]. Discussion about the implementation happened
in mail thread [2] in Architecture mailing list. Related jira is in [3] and
the pull request data and sample car file is attached in the jira. You can
use this feature once pull request is merged and carbon-commons is released.

[1] - https://github.com/wso2/carbon-commons/pull/160
[2] - Implementing Datasource Deployer
[3] - https://wso2.org/jira/browse/DS-907

Thanks,
-- 
Rajith Vitharana

Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94715883223
Blog : http://lankavitharana.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Pavithra Madurangi]

On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga  wrote:

>
>
> On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:
>
>> Thanks Prasanna. Please update the JIRA as well.
>>
>> In between there was a dep sync issue reported with ESB [1] with the
>> recent fix from carbon commons. Just want to find out whether this has any
>> effect on GREG product for scenarios like secondary user store, API-M
>> integration (May not be an issue since we suggest to use APIM 1.9.1 for GW)
>> or install WSO2 AS features and use it (which is anyway very unlikely
>> scenario).
>>
>
> It's hard to think about DipSync use cases in G-Reg.
>

​Agree to this.

But our concern was secondary user stores. If we have secondary user stores
in a multi node deployment, won't there be any issues because of this bug
(since it's one place where depSync is needed)?

There's a possibility of managing secondary user stores without having
depSync. What we wanted to get clarified was whether that's the
approach/workaround we suggest ?

Regards,
pavithra

>
> Thanks !
>
>>
>> 1. ESBJAVA-4156 
>>
>>
>>
>>
>>
>> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
>> wrote:
>>
>>> Hi Thayalan,
>>>
>>> We fixed the issue REGISTRY-2927
>>>  . Now users can re-login
>>> from the same window in a fresh pack.
>>>
>>> Thanks
>>>
>>> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>>>
 Hi Team,

 I've observed from the standalone pack without any changes user has not
 been allowed to re-login  to the store [1]. However this is working fine
 for publisher. As per the suggestion in [1] hostname has to be set in
 carbon.xml. However in the default pack SSO enabled for store/publisher and
 Hostname tag is commented. Even uncomment them and set to IP or localhost
 too not working as suggested in the JIRA. From the end user perspective
 user should allow to re-login from the same window session from the fresh
 pack. Is this is something we need to fix before releasing them?

 1.REGISTRY-2927 

 On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
 wrote:

> -1,
>
> We found an issue with solr related logging configuration and this
> issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>
> Step to reproduce this issue:
>
> Go to Main --> Registry search and search by any value.
> Then navigate to Configure --> Logging section.
> Exceptions are logged in console and "Global Log4J Configuration" and
> "Configure Log4J Appenders" views are not loading due to the above issue.
>
> Created a JIRA[1] to track above issue and will release release G-Reg
> 5.0.0 RC3 pack ASAP.
>
> [1]. https://wso2.org/jira/browse/WSAS-2120
>
> Regards,
> Chandana
>
>
> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
> wrote:
>
>> Hi Pubudu,
>>
>> Since we have already released RC2 pack and component repos, we can
>> not update above pages now. We will update context specific pages for
>> coming up 5.0.1 release. Meantime, you can refer wiki based documentation
>> available here [1].
>>
>> [1].
>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>
>> Regards,
>> Chandana
>>
>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Chandana,
>>>
>>> Since the Help page, context specific pages are out-dated we need to
>>> update those to reflect most recent information. Can you please address
>>> this issue as required? Please find the relevant ticket below. Thanks.
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2910
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <
>>> nirde...@wso2.com> wrote:
>>>
 The context sensitive help links are in the product UIs. AFAIK,
 these links are component-based rather than product based? Please 
 correct
 me if I am wrong.

 If they are component-based, we cannot link to the wiki of a
 specific product from there as many other products might also be using 
 the
 same component.

 Maybe we should simply disable these help links until we find a
 better way to maintain them.

 Thanks,
 -Nirdesha

 On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan >>> > wrote:

> Hi Nirdesha,
>
> Can we please point the current context sensitive help pages to
> relevant product documentation of GReg 5.0.0 release?
>
> Cheers,
>
> Pubudu D.P
> Senior Softwar