Re: [Dev] [APPFAC] Appfactory plugin build failures due to corrupted poms in nexus repo

[Samith Dassanayake]

Hi Rumesh,
Still getting the old corrupted pom files from the above links.

Thanks,
Samith


On Thu, Sep 4, 2014 at 9:44 AM, Rumesh Bandara  wrote:

> Uploaded the given pom. Please check now.
>
> Regards,
> Rumesh
>
>
> On Wed, Sep 3, 2014 at 3:05 PM, Samith Dassanayake 
> wrote:
>
>> Hi Rumesh,
>>
>> Following pom file is also corrupted. I have attached the corrected pom
>> file. Could you please commit it as well.
>> wstx-asl-3.1.0:
>> http://maven.wso2.org/nexus/content/groups/wso2-public/woodstox/wstx-asl/3.1.0/wstx-asl-3.1.0.pom
>>
>> Thanks,
>> Samith.
>>
>>
>>
>> On Tue, Sep 2, 2014 at 10:55 AM, Rumesh Bandara  wrote:
>>
>>> Hi Anuruddha,
>>>
>>> Please re-check after some time because there is an ongoing syncing
>>> process with maven.
>>>
>>> Thanks,
>>> Rumesh
>>>
>>>
>>> On Tue, Sep 2, 2014 at 10:43 AM, Anuruddha Premalal 
>>> wrote:
>>>
 Hi Rumesh,

 I'm still getting the old pom files from the previous links.

 Regards,
 Anuruddha.


 On Tue, Sep 2, 2014 at 10:35 AM, Rumesh Bandara 
 wrote:

> Uploaded the given pom files. Please check now.
>
> Thanks,
> Rumesh
>
>
> On Wed, Aug 20, 2014 at 10:24 AM, Anuruddha Premalal <
> anurud...@wso2.com> wrote:
>
>> Hi,
>>
>> We are facing build failures due to the following corrupted pom
>> files. Can some authorized person commit the following corrected poms to
>> wso2 nexus repo?.
>>
>> uddi4j :
>> http://maven.wso2.org/nexus/content/groups/wso2-public/uddi/uddi4j/1.0.1/uddi4j-1.0.1.pom
>>
>> org.eclipse.core.runtime :
>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/eclipse/core/org.eclipse.core.runtime/3.5.0.v20090429-1800/org.eclipse.core.runtime-3.5.0.v20090429-1800.pom
>>
>>
>> Thanks & Regards,
>> --
>> *Anuruddha Premalal*
>> Software Eng. | WSO2 Inc.
>> Mobile : +94710461070
>> Web site : www.regilandvalley.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


 --
 *Anuruddha Premalal*
 Software Eng. | WSO2 Inc.
 Mobile : +94710461070
 Web site : www.regilandvalley.com


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Best Regards
>>
>> Samith Dassanayake
>> Software Engineer, WSO2 Inc.
>>
>>
>


-- 
Best Regards

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

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi Chamila

I cannot find the mentioned resource in the 04/09/2014 pack. I followed the
steps given in the README.txt to migrate the database.

Thank You
Erandi


On Fri, Sep 5, 2014 at 11:57 AM, Chamila Adhikarinayake 
wrote:

> Hi Chathurika,
> There is a new resource "migration-1.7.0_to_1.7.1" to modify the database.
> it creates the related column "SUBS_CREATE_STATE" (which is mentioned in
> the error log). Did you use that one? I think this might be the problem.
>
>
> On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva  > wrote:
>
>> Hi All
>>
>> The migration cannot be tested in the 04/09/2014 due to the following
>> issue, since none of the migrated APIs can be retrieved. Testing is
>> currently blocking.
>>
>> https://wso2.org/jira/browse/APIMANAGER-2799
>>
>> Thank You
>> Erandi
>>
>>
>>
>> On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi Chamila
>>>
>>> I have reopened the issue APIMANAGER-2662 because this issue should be
>>> fixed and shipped in a newer revision or as a patch itself.
>>>
>>> Thank You
>>>
>>>
>>>
>>>
>>> On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake <
>>> chami...@wso2.com> wrote:
>>>
 I'll create a small java client to modify the apis in the
 synapse-config/default/api folder.
 Thanks,
 Chamila.


 On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias  wrote:

> We should be able to write a simple script or java client to do this
> right?
>
> Thanks,
> NuwanD.
>
>
> On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi Chamila
>>
>> As i understand regarding APIMANAGER-2662
>>  following are the two
>> workarounds.
>>
>> 1. As mentioned in the readme.txt., edit *each* api xml in the
>> APIM_1.7.0/repository/deployment/server/synapse-config/default/api
>> directory.
>>Replace
>> > class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler"/>
>>with
>> > class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler">
>> > value="gov:/apimgt/statistics/ga-config.xml"/>
>> 
>>
>> 2. Manually go to implement tab in the edit mode of *each* of the
>> APIs and click manage
>>
>> If a customer wants to migrate hundreds of APIs, is it a feasible
>> solution from the customer's perspective? Ideally when a customer 
>> migrates
>> from an older version, they should be able to work with their data as 
>> they
>> worked before the migration. Since invoking an API is the core
>> functionality of API Manager, is it really feasible in asking the 
>> customer
>> to follow above 1st or 2nd method?
>>
>> From the customer/user perspective above given solution cannot be
>> accepted. In my opinion this should be handled by our side without asking
>> the customer/user to take extra effort in bringing his migrated data to
>> work properly.
>>
>> Thank You
>> Erandi
>>
>>
>>
>> On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Hi Chathurika,
>>>
>>> Issues mentioned in the previous mail are fixed in the latest
>>> 17/08/2014 pack[1]. There are some updates done to the migration tool
>>> readme.txt file as well. You can proceed with the migration testing. For
>>> the issue APIMANAGER-2662
>>>  please read the
>>> comments in the jira (these instructions are added to the readme.txt).
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
>>> Thanks,
>>> Chamila.
>>>
>>>
>>> On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva <
>>> chathuri...@wso2.com> wrote:
>>>
 Hi All

 As per the pack released on 05/08/2014 following is the status

 1. APIMANAGER-2662 
 - issue status - inprogress. This is the main scenario of the 
 migration.
 Thus the fix for this is crucial to proceed with the proper user 
 scenario
 based testing
 2. APIMANAGER-2698 
 - issue status - reopened. This issue corrupts the entire database.
 3. APIMANAGER-2669 
 - issue status - reopened. The resources added before the migration is 
 not
 copied correctly
 3. APIMANAGER-2672 
 - issue status - reopened (due to APIMANAGER-2669
 ) . This issue
 cannot be verified until APIMANAGER-2698
 

Re: [Dev] {chunk-13 packs}

[Evanthika Amarasiri]

Thanks Chanika

​Regards,
Evanthika

On Fri, Sep 5, 2014 at 12:01 PM, Chanika Geeganage  wrote:

> Hi Evanthika,
>
> DSS pack is also available now in the above location.
>
> Thanks
>
>
> On Fri, Sep 5, 2014 at 10:35 AM, Evanthika Amarasiri 
> wrote:
>
>> Thanks Ratha,
>>
>> Can we have a DSS pack as well?
>>
>> ​Regards,
>> Evanthika
>>
>> On Fri, Sep 5, 2014 at 10:33 AM, Vijayaratha Vijayasingam <
>> rat...@wso2.com> wrote:
>>
>>> Hi Evanthika,
>>> Use this packs fro testing;
>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/04-09-2014/
>>>
>>> Thanks.
>>>
>>> --
>>> -Ratha
>>>
>>
>>
>
>
> --
> Best Regards..
>
> Chanika Geeganage
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] chunk-13 packs 03/09/2014

[Chanika Geeganage]

Hi Evanthika,

The DSS pack is committed to the same location

Thanks


On Fri, Sep 5, 2014 at 10:16 AM, Evanthika Amarasiri 
wrote:

> Hi Chanika,
>
> Can we get a DSS pack as well? We are planning to do a setup with API-M &
> DSS.
>
> ​Regards,
> Evanthika
>
> On Wed, Sep 3, 2014 at 4:56 PM, Vijayaratha Vijayasingam 
> wrote:
>
>> Hi all;
>> Please find packs here
>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/
>>
>> --
>> -Ratha
>>
>
>


-- 
Best Regards..

Chanika Geeganage
Software Engineer
WSO2, Inc.; http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] {chunk-13 packs}

[Chanika Geeganage]

Hi Evanthika,

DSS pack is also available now in the above location.

Thanks


On Fri, Sep 5, 2014 at 10:35 AM, Evanthika Amarasiri 
wrote:

> Thanks Ratha,
>
> Can we have a DSS pack as well?
>
> ​Regards,
> Evanthika
>
> On Fri, Sep 5, 2014 at 10:33 AM, Vijayaratha Vijayasingam  > wrote:
>
>> Hi Evanthika,
>> Use this packs fro testing;
>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/04-09-2014/
>>
>> Thanks.
>>
>> --
>> -Ratha
>>
>
>


-- 
Best Regards..

Chanika Geeganage
Software Engineer
WSO2, Inc.; http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chamila Adhikarinayake]

Hi Chathurika,
There is a new resource "migration-1.7.0_to_1.7.1" to modify the database.
it creates the related column "SUBS_CREATE_STATE" (which is mentioned in
the error log). Did you use that one? I think this might be the problem.


On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva 
wrote:

> Hi All
>
> The migration cannot be tested in the 04/09/2014 due to the following
> issue, since none of the migrated APIs can be retrieved. Testing is
> currently blocking.
>
> https://wso2.org/jira/browse/APIMANAGER-2799
>
> Thank You
> Erandi
>
>
>
> On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva  > wrote:
>
>> Hi Chamila
>>
>> I have reopened the issue APIMANAGER-2662 because this issue should be
>> fixed and shipped in a newer revision or as a patch itself.
>>
>> Thank You
>>
>>
>>
>>
>> On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> I'll create a small java client to modify the apis in the
>>> synapse-config/default/api folder.
>>> Thanks,
>>> Chamila.
>>>
>>>
>>> On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias  wrote:
>>>
 We should be able to write a simple script or java client to do this
 right?

 Thanks,
 NuwanD.


 On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva <
 chathuri...@wso2.com> wrote:

> Hi Chamila
>
> As i understand regarding APIMANAGER-2662
>  following are the two
> workarounds.
>
> 1. As mentioned in the readme.txt., edit *each* api xml in the
> APIM_1.7.0/repository/deployment/server/synapse-config/default/api
> directory.
>Replace
>  class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler"/>
>with
>  class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler">
>  value="gov:/apimgt/statistics/ga-config.xml"/>
> 
>
> 2. Manually go to implement tab in the edit mode of *each* of the
> APIs and click manage
>
> If a customer wants to migrate hundreds of APIs, is it a feasible
> solution from the customer's perspective? Ideally when a customer migrates
> from an older version, they should be able to work with their data as they
> worked before the migration. Since invoking an API is the core
> functionality of API Manager, is it really feasible in asking the customer
> to follow above 1st or 2nd method?
>
> From the customer/user perspective above given solution cannot be
> accepted. In my opinion this should be handled by our side without asking
> the customer/user to take extra effort in bringing his migrated data to
> work properly.
>
> Thank You
> Erandi
>
>
>
> On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake <
> chami...@wso2.com> wrote:
>
>> Hi Chathurika,
>>
>> Issues mentioned in the previous mail are fixed in the latest
>> 17/08/2014 pack[1]. There are some updates done to the migration tool
>> readme.txt file as well. You can proceed with the migration testing. For
>> the issue APIMANAGER-2662
>>  please read the
>> comments in the jira (these instructions are added to the readme.txt).
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
>> Thanks,
>> Chamila.
>>
>>
>> On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi All
>>>
>>> As per the pack released on 05/08/2014 following is the status
>>>
>>> 1. APIMANAGER-2662  -
>>> issue status - inprogress. This is the main scenario of the migration. 
>>> Thus
>>> the fix for this is crucial to proceed with the proper user scenario 
>>> based
>>> testing
>>> 2. APIMANAGER-2698  -
>>> issue status - reopened. This issue corrupts the entire database.
>>> 3. APIMANAGER-2669  -
>>> issue status - reopened. The resources added before the migration is not
>>> copied correctly
>>> 3. APIMANAGER-2672  -
>>> issue status - reopened (due to APIMANAGER-2669
>>> ) . This issue cannot
>>> be verified until APIMANAGER-2698
>>>  is fixed.
>>>
>>> Since the above mentioned issues are blocking, the migration testing
>>> cannot be proceeded for the 05/08/2014 pack
>>>
>>> Thank You
>>>
>>>
>>> On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha <
>>> uvin...@wso2.com> wrote:
>>>
 The ticket has been resolved, please continue with testing


 On 

Re: [Dev] Deploying a custom Axis2 handler in ELB

[Uvindra Dias Jayasinha]

Okay so the issue was the use of the package name
*org.apache.axis2.handlers* for my Axis2 handler, apparently using this
package name can lead to conflicts. I used a different package name
*org.wso2.custom.handlers* as suggested by Isuru and this solved the issue,
Thanks Isuru.


On 5 September 2014 10:45, Uvindra Dias Jayasinha  wrote:

> Thanks Isuru,
>
> okay I've made sure that the proxy handler is only in the lib folder,
>
> uvindra@uvindra-ThinkPad-T530:~/SkyTV_Dev_Service/handler_elb_esb_cluster/ELB_1$
> *find -iname EchoProxyHandler**
> ./repository/components/lib/EchoProxyHandler_1.0.0.jar
>
> no other entries exist in the pack. But still I get the same exception
> when I start,
>
> TID: [0] [ELB] [2014-09-05 10:39:31,009] FATAL
> {org.wso2.carbon.core.init.CarbonServerManager} -  WSO2 Carbon
> initialization Failed {org.wso2.carbon.core.init.CarbonServerManager}
> org.apache.axis2.AxisFault: Exception occured while loading the Axis
> configuration from
> /home/uvindra/SkyTV_Dev_Service/handler_elb_esb_cluster/ELB_1/repository/conf/axis2/axis2.xml
> at
> org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:190)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
> at
> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
> at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurr

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi All

The migration cannot be tested in the 04/09/2014 due to the following
issue, since none of the migrated APIs can be retrieved. Testing is
currently blocking.

https://wso2.org/jira/browse/APIMANAGER-2799

Thank You
Erandi



On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva 
wrote:

> Hi Chamila
>
> I have reopened the issue APIMANAGER-2662 because this issue should be
> fixed and shipped in a newer revision or as a patch itself.
>
> Thank You
>
>
>
>
> On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake  > wrote:
>
>> I'll create a small java client to modify the apis in the
>> synapse-config/default/api folder.
>> Thanks,
>> Chamila.
>>
>>
>> On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias  wrote:
>>
>>> We should be able to write a simple script or java client to do this
>>> right?
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>>
>>> On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva <
>>> chathuri...@wso2.com> wrote:
>>>
 Hi Chamila

 As i understand regarding APIMANAGER-2662
  following are the two
 workarounds.

 1. As mentioned in the readme.txt., edit *each* api xml in the
 APIM_1.7.0/repository/deployment/server/synapse-config/default/api
 directory.
Replace
 >>> class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler"/>
with
 >>> class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler">
 >>> value="gov:/apimgt/statistics/ga-config.xml"/>
 

 2. Manually go to implement tab in the edit mode of *each* of the APIs
 and click manage

 If a customer wants to migrate hundreds of APIs, is it a feasible
 solution from the customer's perspective? Ideally when a customer migrates
 from an older version, they should be able to work with their data as they
 worked before the migration. Since invoking an API is the core
 functionality of API Manager, is it really feasible in asking the customer
 to follow above 1st or 2nd method?

 From the customer/user perspective above given solution cannot be
 accepted. In my opinion this should be handled by our side without asking
 the customer/user to take extra effort in bringing his migrated data to
 work properly.

 Thank You
 Erandi



 On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake <
 chami...@wso2.com> wrote:

> Hi Chathurika,
>
> Issues mentioned in the previous mail are fixed in the latest
> 17/08/2014 pack[1]. There are some updates done to the migration tool
> readme.txt file as well. You can proceed with the migration testing. For
> the issue APIMANAGER-2662
>  please read the
> comments in the jira (these instructions are added to the readme.txt).
>
> [1]
> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
> Thanks,
> Chamila.
>
>
> On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi All
>>
>> As per the pack released on 05/08/2014 following is the status
>>
>> 1. APIMANAGER-2662  -
>> issue status - inprogress. This is the main scenario of the migration. 
>> Thus
>> the fix for this is crucial to proceed with the proper user scenario 
>> based
>> testing
>> 2. APIMANAGER-2698  -
>> issue status - reopened. This issue corrupts the entire database.
>> 3. APIMANAGER-2669  -
>> issue status - reopened. The resources added before the migration is not
>> copied correctly
>> 3. APIMANAGER-2672  -
>> issue status - reopened (due to APIMANAGER-2669
>> ) . This issue cannot
>> be verified until APIMANAGER-2698
>>  is fixed.
>>
>> Since the above mentioned issues are blocking, the migration testing
>> cannot be proceeded for the 05/08/2014 pack
>>
>> Thank You
>>
>>
>> On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha <
>> uvin...@wso2.com> wrote:
>>
>>> The ticket has been resolved, please continue with testing
>>>
>>>
>>> On 11 August 2014 12:49, Uvindra Dias Jayasinha 
>>> wrote:
>>>
 Seems the stack trace is different from what was originally
 reported for this ticket, can we have a closer look at this? Please 
 ping me
 when you get back to your seat. Thanks


 On 11 August 2014 12:30, Chathurika De Silva 
 wrote:

> Hi
>
> We started to test the migration with the 05/08/2014 pack 

Re: [Dev] Compilation failures in Storage Server integration module due to API change.

[Gayashan Amarasinghe]

Thanks Prabath!


On Fri, Sep 5, 2014 at 10:59 AM, Prabath Abeysekera 
wrote:

> Yeah okay. Will do.
>
> Cheers,
> Prabath
>
>
> On Thu, Sep 4, 2014 at 5:48 PM, Gayashan Amarasinghe 
> wrote:
>
>> Hi Prabath,
>>
>> Since the following pull request was merged to product-ss, and the
>> pre-requisite has not been merged to carbon-utils yet, the integration
>> tests would still fail. Can you revert these changes for the moment?
>>
>> https://github.com/wso2-dev/product-ss/pull/23
>>
>> Thanks.
>> /Gayashan
>>
>>
>> On Thu, Sep 4, 2014 at 5:40 PM, Bhathiya Jayasekara 
>> wrote:
>>
>>> Fixed and committed [1].
>>>
>>> [1]
>>> https://github.com/wso2-dev/product-ss/commit/328b51eee71db8aa23649c4e9319a8b06fb896a3
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>>
>>> On Thu, Sep 4, 2014 at 2:41 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 Hi Krishanthan/Prabath,

 I made some API changes when introducing the new Environment concept.
 I'll fix these.

 Thanks,
 Bhathiya


 On Thu, Sep 4, 2014 at 2:39 PM, Prabath Abeysekera 
 wrote:

> Hi Bhathiya,
>
> Would you be able to check on this?
>
>
> Cheers,
> Prabath
>
>
> On Thu, Sep 4, 2014 at 2:31 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi,
>>
>> I got following compilation failures when building integration test
>> module of SS product. This might be due to API changes introduced in
>> CassandraKeyspaceAdmin class recently. I'm trying to build the 
>> integration
>> test module as I'm going to add UI test module to SS product.
>>
>> ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.ss.integration.common.clients:
>> Compilation failure: Compilation failure:
>>
>> [ERROR]
>> /Users/krishantha/git/wso2-dev/product-ss/modules/integration/tests-common/admin-clients/src/main/java/org/wso2/ss/integration/common/clients/CassandraKeyspaceAdminClient.java:[86,37]
>> getClusterName(java.lang.String) in
>> org.wso2.carbon.cassandra.mgt.stub.ks.CassandraKeyspaceAdminStub cannot 
>> be
>> applied to ()
>>
>> [ERROR]
>> /Users/krishantha/git/wso2-dev/product-ss/modules/integration/tests-common/admin-clients/src/main/java/org/wso2/ss/integration/common/clients/CassandraKeyspaceAdminClient.java:[105,37]
>> listKeyspaces(java.lang.String,java.lang.String,java.lang.String,java.lang.String)
>> in org.wso2.carbon.cassandra.mgt.stub.ks.CassandraKeyspaceAdminStub 
>> cannot
>> be applied to (java.lang.String,java.lang.String,java.lang.String)
>>
>> [ERROR]
>> /Users/krishantha/git/wso2-dev/product-ss/modules/integration/tests-common/admin-clients/src/main/java/org/wso2/ss/integration/common/clients/CassandraKeyspaceAdminClient.java:[119,37]
>> listKeyspacesOfCurrentUser(java.lang.String) in
>> org.wso2.carbon.cassandra.mgt.stub.ks.CassandraKeyspaceAdminStub cannot 
>> be
>> applied to ()
>>
>> [ERROR]
>> /Users/krishantha/git/wso2-dev/product-ss/modules/integration/tests-common/admin-clients/src/main/java/org/wso2/ss/integration/common/clients/CassandraKeyspaceAdminClient.java:[136,37]
>> listColumnFamiliesOfCurrentUser(java.lang.String,java.lang.String) in
>> org.wso2.carbon.cassandra.mgt.stub.ks.CassandraKeyspaceAdminStub cannot 
>> be
>> applied to (java.lang.String)
>>
>> Thanks,
>>
>> Krishantha.
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middlewear.
>>
>
>
>
> --
> Prabath Abeysekara
> Associate Technical Lead, Data TG.
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>



 --
 *Bhathiya Jayasekara*
 *Software Engineer,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <%2B94715478185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

>>>
>>>
>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Software Engineer,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185 <%2B94715478185>*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Gayashan Amarasinghe*
>> Softwar

Re: [Dev] WSO2 Committers += Akila Ravihansa Perera

[Ramindu Deshapriya]

Congratulations Akila from your friends at the Sahana Software Foundation.


On Fri, Sep 5, 2014 at 9:25 AM, Senduran Balasubramaniyam [via WSO2 Oxygen
Tank]  wrote:

> Congratulations Akila !!
>
>
> On Fri, Sep 5, 2014 at 7:49 AM, Waruna De Silva <[hidden email]
> > wrote:
>
>> Congrats Akila !!
>>
>>
>> On Thu, Sep 4, 2014 at 11:25 PM, Harsha Kumara <[hidden email]
>> > wrote:
>>
>>> Congratulations Akila!
>>>
>>>
>>> On Thu, Sep 4, 2014 at 5:43 PM, Jenananthan Yogendran <[hidden email]
>>> > wrote:
>>>
 Congrats Akila


 On Thu, Sep 4, 2014 at 4:31 PM, Gayashan Amarasinghe <[hidden email]
 > wrote:

> Congratulations Akila!!!
>
>
> On Thu, Sep 4, 2014 at 2:41 PM, Sajith Kariyawasam <[hidden email]
> > wrote:
>
>> Congratulations Akila !
>>
>>
>> On Thu, Sep 4, 2014 at 2:36 PM, Nirmal Fernando <[hidden email]
>> > wrote:
>>
>>> Congratz Akila!
>>>
>>>
>>> On Thu, Sep 4, 2014 at 2:30 PM, Milinda Perera <[hidden email]
>>> > wrote:
>>>
 Congratulations Akila 


 On Thu, Sep 4, 2014 at 2:15 PM, Vijitha Ekanayake <[hidden email]
 > wrote:

> Congratulations Akila ..!!!
>
>
> On Thu, Sep 4, 2014 at 1:19 PM, Lakmal Warusawithana <[hidden
> email] >
> wrote:
>
>> Hi all,
>>
>> It's my pleasure to announce Akila as a WSO2 Committer. Akila has
>> done great contributions to Apache Stratos and WSO2 Private PaaS 
>> products.
>> And in recognition of his contribution he has been voted as a WSO2 
>> commiter.
>>
>> Akila, welcome aboard and keep up the good work!.
>>
>> --
>> Lakmal Warusawithana
>> Vice President, Apache Stratos
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : > target="_blank">+94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> [hidden email]
>> 
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vijitha Ekanayake
> *Software Engineer*
> Mobile : +94 (0) 777 247339
> [hidden email]
> 
>
> ___
> Dev mailing list
> [hidden email]
> 
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Milinda Perera
 Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 115 032


 ___
 Dev mailing list
 [hidden email]
 
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> Mobile: >> target="_blank">+94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> [hidden email]
>>> 
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *--*
>> *Sajith Kariyawasam*
>> *Mobile: +94772269575 <%2B94772269575>*
>>
>> ___
>> Dev mailing list
>> [hidden email] 
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Gayashan Amarasinghe*
> Software Engineer | Platform TG
> WSO2, Inc. | http://wso2.com
> lean. enterprise. middleware
>
> Mobile :  target="_blank">+94718314517
> Blog : gayashan-a.blogspot.com
>
> ___
> Dev mailing list
> [hidden email] 
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

Re: [Dev] Deploying a custom Axis2 handler in ELB

[Uvindra Dias Jayasinha]

Thanks Isuru,

okay I've made sure that the proxy handler is only in the lib folder,

uvindra@uvindra-ThinkPad-T530:~/SkyTV_Dev_Service/handler_elb_esb_cluster/ELB_1$
*find -iname EchoProxyHandler**
./repository/components/lib/EchoProxyHandler_1.0.0.jar

no other entries exist in the pack. But still I get the same exception when
I start,

TID: [0] [ELB] [2014-09-05 10:39:31,009] FATAL
{org.wso2.carbon.core.init.CarbonServerManager} -  WSO2 Carbon
initialization Failed {org.wso2.carbon.core.init.CarbonServerManager}
org.apache.axis2.AxisFault: Exception occured while loading the Axis
configuration from
/home/uvindra/SkyTV_Dev_Service/handler_elb_esb_cluster/ELB_1/repository/conf/axis2/axis2.xml
at
org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:190)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
at
org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.axis2.deployment.DeploymentException:
org.apache.axis2.handlers.EchoProxyHandler
at org.apache.axis2.deployment.util.Utils.loadHandler(Utils.java:149)
at
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseList(AxisConfigB

Re: [Dev] Compilation failures in Storage Server integration module due to API change.

[Prabath Abeysekera]

Yeah okay. Will do.

Cheers,
Prabath


On Thu, Sep 4, 2014 at 5:48 PM, Gayashan Amarasinghe 
wrote:

> Hi Prabath,
>
> Since the following pull request was merged to product-ss, and the
> pre-requisite has not been merged to carbon-utils yet, the integration
> tests would still fail. Can you revert these changes for the moment?
>
> https://github.com/wso2-dev/product-ss/pull/23
>
> Thanks.
> /Gayashan
>
>
> On Thu, Sep 4, 2014 at 5:40 PM, Bhathiya Jayasekara 
> wrote:
>
>> Fixed and committed [1].
>>
>> [1]
>> https://github.com/wso2-dev/product-ss/commit/328b51eee71db8aa23649c4e9319a8b06fb896a3
>>
>> Thanks,
>> Bhathiya
>>
>>
>> On Thu, Sep 4, 2014 at 2:41 PM, Bhathiya Jayasekara 
>> wrote:
>>
>>> Hi Krishanthan/Prabath,
>>>
>>> I made some API changes when introducing the new Environment concept.
>>> I'll fix these.
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>>
>>> On Thu, Sep 4, 2014 at 2:39 PM, Prabath Abeysekera 
>>> wrote:
>>>
 Hi Bhathiya,

 Would you be able to check on this?


 Cheers,
 Prabath


 On Thu, Sep 4, 2014 at 2:31 PM, Krishantha Samaraweera <
 krishan...@wso2.com> wrote:

> Hi,
>
> I got following compilation failures when building integration test
> module of SS product. This might be due to API changes introduced in
> CassandraKeyspaceAdmin class recently. I'm trying to build the integration
> test module as I'm going to add UI test module to SS product.
>
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.ss.integration.common.clients:
> Compilation failure: Compilation failure:
>
> [ERROR]
> /Users/krishantha/git/wso2-dev/product-ss/modules/integration/tests-common/admin-clients/src/main/java/org/wso2/ss/integration/common/clients/CassandraKeyspaceAdminClient.java:[86,37]
> getClusterName(java.lang.String) in
> org.wso2.carbon.cassandra.mgt.stub.ks.CassandraKeyspaceAdminStub cannot be
> applied to ()
>
> [ERROR]
> /Users/krishantha/git/wso2-dev/product-ss/modules/integration/tests-common/admin-clients/src/main/java/org/wso2/ss/integration/common/clients/CassandraKeyspaceAdminClient.java:[105,37]
> listKeyspaces(java.lang.String,java.lang.String,java.lang.String,java.lang.String)
> in org.wso2.carbon.cassandra.mgt.stub.ks.CassandraKeyspaceAdminStub cannot
> be applied to (java.lang.String,java.lang.String,java.lang.String)
>
> [ERROR]
> /Users/krishantha/git/wso2-dev/product-ss/modules/integration/tests-common/admin-clients/src/main/java/org/wso2/ss/integration/common/clients/CassandraKeyspaceAdminClient.java:[119,37]
> listKeyspacesOfCurrentUser(java.lang.String) in
> org.wso2.carbon.cassandra.mgt.stub.ks.CassandraKeyspaceAdminStub cannot be
> applied to ()
>
> [ERROR]
> /Users/krishantha/git/wso2-dev/product-ss/modules/integration/tests-common/admin-clients/src/main/java/org/wso2/ss/integration/common/clients/CassandraKeyspaceAdminClient.java:[136,37]
> listColumnFamiliesOfCurrentUser(java.lang.String,java.lang.String) in
> org.wso2.carbon.cassandra.mgt.stub.ks.CassandraKeyspaceAdminStub cannot be
> applied to (java.lang.String)
>
> Thanks,
>
> Krishantha.
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>



 --
 Prabath Abeysekara
 Associate Technical Lead, Data TG.
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471

>>>
>>>
>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Software Engineer,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185 <%2B94715478185>*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <%2B94715478185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Gayashan Amarasinghe*
> Software Engineer | Platform TG
> WSO2, Inc. | http://wso2.com
> lean. enterprise. middleware
>
> Mobile : +94718314517
> Blog : gayashan-a.blogspot.com
>



-- 
Prabath Abeysekara
Associate Technical Lead, Data TG.
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
_

Re: [Dev] WSO2 Committers += Akila Ravihansa Perera

[Pamod Sylvester]

Congratulations Akila !


On Fri, Sep 5, 2014 at 9:07 AM, Dinesh Bandara  wrote:

> Congrats Akila
>
>
> On Thu, Sep 4, 2014 at 1:19 PM, Lakmal Warusawithana 
> wrote:
>
>> Hi all,
>>
>> It's my pleasure to announce Akila as a WSO2 Committer. Akila has done
>> great contributions to Apache Stratos and WSO2 Private PaaS products. And
>> in recognition of his contribution he has been voted as a WSO2 commiter.
>>
>> Akila, welcome aboard and keep up the good work!.
>>
>> --
>> Lakmal Warusawithana
>> Vice President, Apache Stratos
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinesh Bandara*
>
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pamod Sylvester *
 *Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] {chunk-13 packs}

[Evanthika Amarasiri]

Thanks Ratha,

Can we have a DSS pack as well?

​Regards,
Evanthika

On Fri, Sep 5, 2014 at 10:33 AM, Vijayaratha Vijayasingam 
wrote:

> Hi Evanthika,
> Use this packs fro testing;
> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/04-09-2014/
>
> Thanks.
>
> --
> -Ratha
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Looks like access token persistance stopped working with new improvements

[Vijayaratha Vijayasingam]

Thanks this works.


On 4 September 2014 13:34, Prasad Tissera  wrote:

> Fixed with r206858. Please verify. Thanks.
>
>
>
> On Wed, Sep 3, 2014 at 7:30 PM, Prasad Tissera  wrote:
>
>> We will look into this. Thanks.
>>
>> Regards,
>> Prasad.
>> On Sep 3, 2014 5:55 PM, "Vijayaratha Vijayasingam" 
>> wrote:
>>
>>>  IS team;
>>>
>>> The new perf improvement we did at Oauth component has broken the token
>>> persistency.
>>> In the new implementation, we save the tokens in a queue and allowing BE
>>> task to persist tokens.
>>> Looks like now, tokens are not persisting at all. I have waited more
>>> than 20 mins..DB is not getting updated..
>>> You can check the behavior in AM pack[2], when you regenerate token for
>>> an application.
>>>
>>> [1]
>>>
>>>   if (maxPoolSize > 0){
>>>
>>> accessContextTokenQueue.push(new AccessContextTokenDO(
>>> accessToken, consumerKey, accessTokenDO, userStoreDomain));
>>>
>>> } else {
>>>
>>> persistAccessToken(accessToken, consumerKey, accessTokenDO,
>>> userStoreDomain);
>>>
>>> }
>>> [2]
>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/
>>>
>>> Thanks.
>>> --
>>> -Ratha
>>>
>>
>
>
> --
> Prasad Tissera
> Software Engineer.
> Mobile : +94777223444
>



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

[Dev] {chunk-13 packs}

[Vijayaratha Vijayasingam]

Hi Evanthika,
Use this packs fro testing;
https://svn.wso2.org/repos/wso2/scratch/chunk13-release/04-09-2014/

Thanks.

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

Re: [Dev] Deploying a custom Axis2 handler in ELB

[Isuru Udana]

Hi Uvindra,


On Fri, Sep 5, 2014 at 9:08 AM, Uvindra Dias Jayasinha 
wrote:

> Hi All,
>
> So I need to deploy a custom Axis2 handler in ELB 2.1.1.
>
> So I wrote a handler which extends the AbstractHandler interface and then
> copied the jar file to the ELB repository/components/plugins folder.
>
If it is jar, you need to copy into repository/components/lib directory,
else if it is an osgi bundle you need to copy into
repository/components/dropins


> Then I modified the axis2.xml to include the handler as part of the
> "InFlow" phase.
>
> Then when I start the ELB I get a axis2 DeploymentException referring to
> my custom handler due to a classNotFoundException.
>
> Any idea what I'm missing here? Or do I need to develop a full blown Axis2
> module with my handler embedded to make this work?
>
> Sorry I cant include the actual output because I do not have internet
> access from my machine at the moment.
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] chunk-13 packs 03/09/2014

[Evanthika Amarasiri]

Hi Chanika,

Can we get a DSS pack as well? We are planning to do a setup with API-M &
DSS.

​Regards,
Evanthika

On Wed, Sep 3, 2014 at 4:56 PM, Vijayaratha Vijayasingam 
wrote:

> Hi all;
> Please find packs here
> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/
>
> --
> -Ratha
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Akila Ravihansa Perera

[Dinesh Bandara]

Congrats Akila


On Thu, Sep 4, 2014 at 1:19 PM, Lakmal Warusawithana 
wrote:

> Hi all,
>
> It's my pleasure to announce Akila as a WSO2 Committer. Akila has done
> great contributions to Apache Stratos and WSO2 Private PaaS products. And
> in recognition of his contribution he has been voted as a WSO2 commiter.
>
> Akila, welcome aboard and keep up the good work!.
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Dinesh Bandara*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [App Factory Training Project] Build a development statistics Dashboard for Apps in App Factory

[Gayan Dhanushka]

Hi Iqbal,

Currently we have START, SUCCESS and FAIL status. If you closely have a
look you can see that *appBuildStream *is a private variable which defines
a data stream, not a method. For each of these data stream definitions,
there are publish methods in the BamDataPublisher.java class.

Thanks
Gayan


On Thu, Sep 4, 2014 at 2:22 PM, Iqbal Irham  wrote:

> Hi Gayan,
>
> Thank you very much for the reply.
> We are in the process of identifying the Build statuses which we are going
> to get from BAM.
> In the java code(BamDataPublisher.java) i found a method *appBuildStream.*
> As i highlighted below there is a String for Status.
> Please help us to find out what are the status values(i.e
> success,fail,Pending,Aborted) it's publishing.
>
> 'payloadData':["+
> "{'name':'applicationName','type':'string'},"+
> "{'name':'applicationKey','type':'string'},"+
> "{'name':'applicationVersion','type':'string'},"+
> "{'name':'timeStamp','type':'double'},"+
> "{'name':'tenantId', 'type':'string'},"+
> "*{'name':'status', 'type':'string'}*,"+
> "{'name':'buildId', 'type':'string'},"+
> "{'name':'revision', 'type':'string'},"+
> "{'name':'user',  'type':'string' }"+
> "];
>
> Thanks
>
>
>
> On Thu, Sep 4, 2014 at 1:57 PM, Gayan Dhanushka  wrote:
>
>> Hi Pirinthapan,
>>
>> I believe you want to visualize the number of builds and commits in the
>> per each day inside an application in App Factory. For this we already
>> collect the build and commit data. We collect the build data through App
>> Factory and commits data through a git post commit hook [1]. Please note
>> that we have multiple activity points in App Factory from where the events
>> are published to BAM. So the data that you are looking for is already being
>> published.
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/scratch/appfactory_2.0.0/products/appfactory/2.0.1/vmware/appfactory_deployment_s4/resources/configs/jenkins.groovy
>>
>> Regards
>> Gayan
>>
>>
>> On Thu, Sep 4, 2014 at 11:11 AM, Pirinthapan Mahendran <
>> pirintha...@wso2.com> wrote:
>>
>>> Hi Gayan,
>>>
>>> We went through the 'BamDataPublisher' class [1]. In this class the
>>> publish events are available for App creation, App version, Tenant user,
>>> App user, App issue and App build. But we need the data for 'Commit logs'
>>> as well. So do we need to create an event to publish these commit logs?
>>>
>>> 1.
>>> https://svn.wso2.org/repos/wso2/scratch/appfactory_2.0.0/components/appfac/org.wso2.carbon.appfactory.bam.integration/2.0.1/src/main/java/org/wso2/carbon/appfactory/bam/integration/BamDataPublisher.java
>>>
>>> Thanks.
>>>
>>> Mahendran Pirinthapan
>>> Software Engineer | WSO2 Inc.
>>> Mobile +94772378732.
>>>
>>
>>
>>
>> --
>> Gayan Dhanuska
>> Software Engineer
>> http://wso2.com/
>> Lean Enterprise Middleware
>>
>> Mobile
>> 071 666 2327
>>
>> Office
>> Tel   : 94 11 214 5345
>> Fax  : 94 11 214 5300
>>
>> Twitter : https://twitter.com/gayanlggd
>>
>
>
>
> --
> Irham Iqbal
> Software Engineer - Test Automation
>  WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
> phone: +94 777888452
>



-- 
Gayan Dhanuska
Software Engineer
http://wso2.com/
Lean Enterprise Middleware

Mobile
071 666 2327

Office
Tel   : 94 11 214 5345
Fax  : 94 11 214 5300

Twitter : https://twitter.com/gayanlggd
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Akila Ravihansa Perera

[Senduran Balasubramaniyam]

Congratulations Akila !!


On Fri, Sep 5, 2014 at 7:49 AM, Waruna De Silva  wrote:

> Congrats Akila !!
>
>
> On Thu, Sep 4, 2014 at 11:25 PM, Harsha Kumara  wrote:
>
>> Congratulations Akila!
>>
>>
>> On Thu, Sep 4, 2014 at 5:43 PM, Jenananthan Yogendran <
>> jenanant...@wso2.com> wrote:
>>
>>> Congrats Akila
>>>
>>>
>>> On Thu, Sep 4, 2014 at 4:31 PM, Gayashan Amarasinghe 
>>> wrote:
>>>
 Congratulations Akila!!!


 On Thu, Sep 4, 2014 at 2:41 PM, Sajith Kariyawasam 
 wrote:

> Congratulations Akila !
>
>
> On Thu, Sep 4, 2014 at 2:36 PM, Nirmal Fernando 
> wrote:
>
>> Congratz Akila!
>>
>>
>> On Thu, Sep 4, 2014 at 2:30 PM, Milinda Perera 
>> wrote:
>>
>>> Congratulations Akila 
>>>
>>>
>>> On Thu, Sep 4, 2014 at 2:15 PM, Vijitha Ekanayake >> > wrote:
>>>
 Congratulations Akila ..!!!


 On Thu, Sep 4, 2014 at 1:19 PM, Lakmal Warusawithana <
 lak...@wso2.com> wrote:

> Hi all,
>
> It's my pleasure to announce Akila as a WSO2 Committer. Akila has
> done great contributions to Apache Stratos and WSO2 Private PaaS 
> products.
> And in recognition of his contribution he has been voted as a WSO2 
> commiter.
>
> Akila, welcome aboard and keep up the good work!.
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Vijitha Ekanayake
 *Software Engineer*
 Mobile : +94 (0) 777 247339
 vijit...@wso2.com

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


>>>
>>>
>>> --
>>> Milinda Perera
>>> Software Engineer;
>>> WSO2 Inc. http://wso2.com ,
>>> Mobile: (+94) 714 115 032
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *--*
> *Sajith Kariyawasam*
> *Mobile: +94772269575 <%2B94772269575>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Gayashan Amarasinghe*
 Software Engineer | Platform TG
 WSO2, Inc. | http://wso2.com
 lean. enterprise. middleware

 Mobile : +94718314517
 Blog : gayashan-a.blogspot.com

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


>>>
>>>
>>> --
>>> Jenananthan Yogendran
>>> *Software Engineer,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Harsha Kumara
>> Software Engineer, WSO2 Inc.
>> Mobile: +94775505618
>> Blog:harshcreationz.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> --
> Waruna De Silva.
> Director of Engineering ; WSO2, Inc.;  http://wso2.com/
> cell +94 777 316866
>
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] Deploying a custom Axis2 handler in ELB

[Uvindra Dias Jayasinha]

Hi All,

So I need to deploy a custom Axis2 handler in ELB 2.1.1.

So I wrote a handler which extends the AbstractHandler interface and then
copied the jar file to the ELB repository/components/plugins folder.

Then I modified the axis2.xml to include the handler as part of the
"InFlow" phase.

Then when I start the ELB I get a axis2 DeploymentException referring to my
custom handler due to a classNotFoundException.

Any idea what I'm missing here? Or do I need to develop a full blown Axis2
module with my handler embedded to make this work?

Sorry I cant include the actual output because I do not have internet
access from my machine at the moment.

-- 
Regards,
Uvindra

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

Re: [Dev] WSO2 Committers += Akila Ravihansa Perera

[Waruna De Silva]

Congrats Akila !!


On Thu, Sep 4, 2014 at 11:25 PM, Harsha Kumara  wrote:

> Congratulations Akila!
>
>
> On Thu, Sep 4, 2014 at 5:43 PM, Jenananthan Yogendran <
> jenanant...@wso2.com> wrote:
>
>> Congrats Akila
>>
>>
>> On Thu, Sep 4, 2014 at 4:31 PM, Gayashan Amarasinghe 
>> wrote:
>>
>>> Congratulations Akila!!!
>>>
>>>
>>> On Thu, Sep 4, 2014 at 2:41 PM, Sajith Kariyawasam 
>>> wrote:
>>>
 Congratulations Akila !


 On Thu, Sep 4, 2014 at 2:36 PM, Nirmal Fernando 
 wrote:

> Congratz Akila!
>
>
> On Thu, Sep 4, 2014 at 2:30 PM, Milinda Perera 
> wrote:
>
>> Congratulations Akila 
>>
>>
>> On Thu, Sep 4, 2014 at 2:15 PM, Vijitha Ekanayake 
>> wrote:
>>
>>> Congratulations Akila ..!!!
>>>
>>>
>>> On Thu, Sep 4, 2014 at 1:19 PM, Lakmal Warusawithana <
>>> lak...@wso2.com> wrote:
>>>
 Hi all,

 It's my pleasure to announce Akila as a WSO2 Committer. Akila has
 done great contributions to Apache Stratos and WSO2 Private PaaS 
 products.
 And in recognition of his contribution he has been voted as a WSO2 
 commiter.

 Akila, welcome aboard and keep up the good work!.

 --
 Lakmal Warusawithana
 Vice President, Apache Stratos
 Director - Cloud Architecture; WSO2 Inc.
 Mobile : +94714289692
 Blog : http://lakmalsview.blogspot.com/


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


>>>
>>>
>>> --
>>> Vijitha Ekanayake
>>> *Software Engineer*
>>> Mobile : +94 (0) 777 247339
>>> vijit...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Milinda Perera
>> Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *--*
 *Sajith Kariyawasam*
 *Mobile: +94772269575 <%2B94772269575>*

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


>>>
>>>
>>> --
>>> *Gayashan Amarasinghe*
>>> Software Engineer | Platform TG
>>> WSO2, Inc. | http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> Mobile : +94718314517
>>> Blog : gayashan-a.blogspot.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Jenananthan Yogendran
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

-- 
Waruna De Silva.
Director of Engineering ; WSO2, Inc.;  http://wso2.com/
cell +94 777 316866

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

Re: [Dev] Exception when invoking the Stanford NLP Library packaged into a OSGI bundle from a CEP extension

[Malithi Edirisinghe]

Hi All,

Once I added the jollyday and joda-time as dependecies to the pom and
embedded those dependencies from the felix plugin this problem got solved.

dependencies:


de.jollyday
jollyday
0.4.7


joda-time
joda-time
2.1


felix plugin:

 
org.apache.felix
maven-bundle-plugin
1.4.0
true



${project.artifactId}
${project.artifactId}

edu.stanford.nlp.*; version="3.4",


*;resolution:=optional


*


jollyday,joda-time




It seems to me that we have to embed any dependency used by the library at
the invocation.

Welcome any comments or thoughts on this solution.

Thank You.
Malithi.


On Thu, Sep 4, 2014 at 9:19 PM, Malithi Edirisinghe 
wrote:

> Hi All,
>
> I'm working with some CEP extensions the provide NLP support and I want to
> use Stanford NLP library with my extensions.
> So I'm using following three dependencies
> stanford-corenlp-3.4.jar
> stanford-corenlp-3.4-models.jar
> stanford-tregex-3.4.1.jar
>
> I packaged my extension to a jar and also bundled above three dependencies
> to a one osgi bundle since they contain similar packages.
> But when my extension is being called I get the following exception.
>
> Caused by:
> org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
> Invalid query specified, Error creating
> edu.stanford.nlp.time.TimeExpressionExtractorImpl
>  at
> org.wso2.carbon.event.processor.core.internal.CarbonEventProcessorService.addExecutionPlanConfiguration(CarbonEventProcessorService.java:311)
>  at
> org.wso2.carbon.event.processor.core.EventProcessorDeployer.processDeploy(EventProcessorDeployer.java:138)
> ... 50 more
> Caused by:
> edu.stanford.nlp.util.ReflectionLoading$ReflectionLoadingException: Error
> creating edu.stanford.nlp.time.TimeExpressionExtractorImpl
> at
> edu.stanford.nlp.util.ReflectionLoading.loadByReflection(ReflectionLoading.java:40)
>  at
> edu.stanford.nlp.time.TimeExpressionExtractorFactory.create(TimeExpressionExtractorFactory.java:57)
> at
> edu.stanford.nlp.time.TimeExpressionExtractorFactory.createExtractor(TimeExpressionExtractorFactory.java:38)
>  at
> edu.stanford.nlp.ie.regexp.NumberSequenceClassifier.(NumberSequenceClassifier.java:79)
> at
> edu.stanford.nlp.ie.NERClassifierCombiner.(NERClassifierCombiner.java:67)
>  at
> edu.stanford.nlp.pipeline.StanfordCoreNLP$6.create(StanfordCoreNLP.java:617)
> at edu.stanford.nlp.pipeline.AnnotatorPool.get(AnnotatorPool.java:85)
>  at
> edu.stanford.nlp.pipeline.StanfordCoreNLP.construct(StanfordCoreNLP.java:267)
> at
> edu.stanford.nlp.pipeline.StanfordCoreNLP.(StanfordCoreNLP.java:129)
>  at
> edu.stanford.nlp.pipeline.StanfordCoreNLP.(StanfordCoreNLP.java:125)
> at
> org.wso2.siddhi.extension.nlp.TokensRegexPatternTransformProcessor.initPipeline(TokensRegexPatternTransformProcessor.java:131)
>  at
> org.wso2.siddhi.extension.nlp.TokensRegexPatternTransformProcessor.init(TokensRegexPatternTransformProcessor.java:72)
> at
> org.wso2.siddhi.core.query.processor.transform.TransformProcessor.initTransformProcessor(TransformProcessor.java:117)
>  at
> org.wso2.siddhi.core.util.parser.StreamParser.updateQueryEventSourceOutDefinition(StreamParser.java:512)
> at
> org.wso2.siddhi.core.query.creator.BasicQueryCreator.updateQueryEventSourceList(BasicQueryCreator.java:46)
>  at
> org.wso2.siddhi.core.query.creator.QueryCreator.init(QueryCreator.java:66)
> at
> org.wso2.siddhi.core.query.creator.BasicQueryCreator.(BasicQueryCreator.java:40)
>  at
> org.wso2.siddhi.core.query.creator.QueryCreatorFactiory.constructQueryCreator(QueryCreatorFactiory.java:40)
> at org.wso2.siddhi.core.query.QueryManager.(QueryManager.java:72)
>  at org.wso2.siddhi.core.SiddhiManager.addQuery(SiddhiManager.java:289)
> at
> org.wso2.siddhi.core.SiddhiManager.addExecutionPlan(SiddhiManager.java:304)
>  at
> org.wso2.carbon.event.processor.core.internal.CarbonEventProcessorService.addExecutionPlanConfiguration(CarbonEventProcessorService.java:309)
>  ... 51 more
> Caused by: edu.stanford.nlp.util.MetaClass$ClassCreationException:
> MetaClass couldn't create public
> edu.stanford.nlp.time.TimeExpressionExtractorImpl(java.lang.String,java.util.Properties)
> with args [sutime, {annotators=tokenize, ssplit, pos, lemma, ner, parse}]
>  at
> edu.stanford.nlp.util.MetaClass$ClassFactory.createInstance(MetaClass.java:233)
> at edu.stanford.nlp.util.MetaClass.createInstance(MetaClass.java:378)
>  at
> edu.stanford.nlp.util.ReflectionLoading.loadByReflection(ReflectionLoading.java:38)
> ... 72 more
> Caused by: java.lang.r

Re: [Dev] Moving AS HTTP Monitoring dashboard to a WSO2 repo

[Dakshika Jayathilaka]

+1

*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911


On Thu, Sep 4, 2014 at 6:22 PM, Manuranga Perera  wrote:

> +1
>
>
> On Thu, Sep 4, 2014 at 6:45 PM, Kalpa Welivitigoda 
> wrote:
>
>> Hi,
>>
>> AS HTTP Monitoring Dashboard which is a jaggery app and planned to be
>> shipped with AS 6 is completed. We need to move the code base under a WSO2
>> repo. It is suggested to be placed at
>> *carbon-deployment/apps/monitoring/*.
>>
>> This will be packaged by a feature in the p2-profile-gen.
>>
>> What do you guys think?
>>
>> --
>> Best Regards,
>>
>> Kalpa Welivitigoda
>> Software Engineer, WSO2 Inc. http://wso2.com
>> Email: kal...@wso2.com
>> Mobile: +94776509215
>>
>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Moving AS HTTP Monitoring dashboard to a WSO2 repo

[Manuranga Perera]

+1


On Thu, Sep 4, 2014 at 6:45 PM, Kalpa Welivitigoda  wrote:

> Hi,
>
> AS HTTP Monitoring Dashboard which is a jaggery app and planned to be
> shipped with AS 6 is completed. We need to move the code base under a WSO2
> repo. It is suggested to be placed at *carbon-deployment/apps/monitoring/*
> .
>
> This will be packaged by a feature in the p2-profile-gen.
>
> What do you guys think?
>
> --
> Best Regards,
>
> Kalpa Welivitigoda
> Software Engineer, WSO2 Inc. http://wso2.com
> Email: kal...@wso2.com
> Mobile: +94776509215
>



-- 
With regards,
*Manu*ranga Perera.

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

Re: [Dev] WSO2 Committers += Akila Ravihansa Perera

[Harsha Kumara]

Congratulations Akila!


On Thu, Sep 4, 2014 at 5:43 PM, Jenananthan Yogendran 
wrote:

> Congrats Akila
>
>
> On Thu, Sep 4, 2014 at 4:31 PM, Gayashan Amarasinghe 
> wrote:
>
>> Congratulations Akila!!!
>>
>>
>> On Thu, Sep 4, 2014 at 2:41 PM, Sajith Kariyawasam 
>> wrote:
>>
>>> Congratulations Akila !
>>>
>>>
>>> On Thu, Sep 4, 2014 at 2:36 PM, Nirmal Fernando  wrote:
>>>
 Congratz Akila!


 On Thu, Sep 4, 2014 at 2:30 PM, Milinda Perera 
 wrote:

> Congratulations Akila 
>
>
> On Thu, Sep 4, 2014 at 2:15 PM, Vijitha Ekanayake 
> wrote:
>
>> Congratulations Akila ..!!!
>>
>>
>> On Thu, Sep 4, 2014 at 1:19 PM, Lakmal Warusawithana > > wrote:
>>
>>> Hi all,
>>>
>>> It's my pleasure to announce Akila as a WSO2 Committer. Akila has
>>> done great contributions to Apache Stratos and WSO2 Private PaaS 
>>> products.
>>> And in recognition of his contribution he has been voted as a WSO2 
>>> commiter.
>>>
>>> Akila, welcome aboard and keep up the good work!.
>>>
>>> --
>>> Lakmal Warusawithana
>>> Vice President, Apache Stratos
>>> Director - Cloud Architecture; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Vijitha Ekanayake
>> *Software Engineer*
>> Mobile : +94 (0) 777 247339
>> vijit...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Milinda Perera
> Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 Thanks & regards,
 Nirmal

 Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



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


>>>
>>>
>>> --
>>> *--*
>>> *Sajith Kariyawasam*
>>> *Mobile: +94772269575 <%2B94772269575>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Gayashan Amarasinghe*
>> Software Engineer | Platform TG
>> WSO2, Inc. | http://wso2.com
>> lean. enterprise. middleware
>>
>> Mobile : +94718314517
>> Blog : gayashan-a.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Jenananthan Yogendran
> *Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] Exception when invoking the Stanford NLP Library packaged into a OSGI bundle from a CEP extension

[Malithi Edirisinghe]

Hi All,

I'm working with some CEP extensions the provide NLP support and I want to
use Stanford NLP library with my extensions.
So I'm using following three dependencies
stanford-corenlp-3.4.jar
stanford-corenlp-3.4-models.jar
stanford-tregex-3.4.1.jar

I packaged my extension to a jar and also bundled above three dependencies
to a one osgi bundle since they contain similar packages.
But when my extension is being called I get the following exception.

Caused by:
org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException:
Invalid query specified, Error creating
edu.stanford.nlp.time.TimeExpressionExtractorImpl
at
org.wso2.carbon.event.processor.core.internal.CarbonEventProcessorService.addExecutionPlanConfiguration(CarbonEventProcessorService.java:311)
at
org.wso2.carbon.event.processor.core.EventProcessorDeployer.processDeploy(EventProcessorDeployer.java:138)
... 50 more
Caused by:
edu.stanford.nlp.util.ReflectionLoading$ReflectionLoadingException: Error
creating edu.stanford.nlp.time.TimeExpressionExtractorImpl
at
edu.stanford.nlp.util.ReflectionLoading.loadByReflection(ReflectionLoading.java:40)
at
edu.stanford.nlp.time.TimeExpressionExtractorFactory.create(TimeExpressionExtractorFactory.java:57)
at
edu.stanford.nlp.time.TimeExpressionExtractorFactory.createExtractor(TimeExpressionExtractorFactory.java:38)
at
edu.stanford.nlp.ie.regexp.NumberSequenceClassifier.(NumberSequenceClassifier.java:79)
at
edu.stanford.nlp.ie.NERClassifierCombiner.(NERClassifierCombiner.java:67)
at
edu.stanford.nlp.pipeline.StanfordCoreNLP$6.create(StanfordCoreNLP.java:617)
at edu.stanford.nlp.pipeline.AnnotatorPool.get(AnnotatorPool.java:85)
at
edu.stanford.nlp.pipeline.StanfordCoreNLP.construct(StanfordCoreNLP.java:267)
at
edu.stanford.nlp.pipeline.StanfordCoreNLP.(StanfordCoreNLP.java:129)
at
edu.stanford.nlp.pipeline.StanfordCoreNLP.(StanfordCoreNLP.java:125)
at
org.wso2.siddhi.extension.nlp.TokensRegexPatternTransformProcessor.initPipeline(TokensRegexPatternTransformProcessor.java:131)
at
org.wso2.siddhi.extension.nlp.TokensRegexPatternTransformProcessor.init(TokensRegexPatternTransformProcessor.java:72)
at
org.wso2.siddhi.core.query.processor.transform.TransformProcessor.initTransformProcessor(TransformProcessor.java:117)
at
org.wso2.siddhi.core.util.parser.StreamParser.updateQueryEventSourceOutDefinition(StreamParser.java:512)
at
org.wso2.siddhi.core.query.creator.BasicQueryCreator.updateQueryEventSourceList(BasicQueryCreator.java:46)
at
org.wso2.siddhi.core.query.creator.QueryCreator.init(QueryCreator.java:66)
at
org.wso2.siddhi.core.query.creator.BasicQueryCreator.(BasicQueryCreator.java:40)
at
org.wso2.siddhi.core.query.creator.QueryCreatorFactiory.constructQueryCreator(QueryCreatorFactiory.java:40)
at org.wso2.siddhi.core.query.QueryManager.(QueryManager.java:72)
at org.wso2.siddhi.core.SiddhiManager.addQuery(SiddhiManager.java:289)
at
org.wso2.siddhi.core.SiddhiManager.addExecutionPlan(SiddhiManager.java:304)
at
org.wso2.carbon.event.processor.core.internal.CarbonEventProcessorService.addExecutionPlanConfiguration(CarbonEventProcessorService.java:309)
... 51 more
Caused by: edu.stanford.nlp.util.MetaClass$ClassCreationException:
MetaClass couldn't create public
edu.stanford.nlp.time.TimeExpressionExtractorImpl(java.lang.String,java.util.Properties)
with args [sutime, {annotators=tokenize, ssplit, pos, lemma, ner, parse}]
at
edu.stanford.nlp.util.MetaClass$ClassFactory.createInstance(MetaClass.java:233)
at edu.stanford.nlp.util.MetaClass.createInstance(MetaClass.java:378)
at
edu.stanford.nlp.util.ReflectionLoading.loadByReflection(ReflectionLoading.java:38)
... 72 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
edu.stanford.nlp.util.MetaClass$ClassFactory.createInstance(MetaClass.java:229)
... 74 more
Caused by: java.lang.RuntimeException: Error initializing binder 1
at edu.stanford.nlp.time.Options.(Options.java:92)
at
edu.stanford.nlp.time.TimeExpressionExtractorImpl.init(TimeExpressionExtractorImpl.java:48)
at
edu.stanford.nlp.time.TimeExpressionExtractorImpl.(TimeExpressionExtractorImpl.java:42)
... 79 more
*Caused by: java.lang.NullPointerException*
* at
de.jollyday.configuration.internal.DefaultConfigurationProvider.putConfiguration(DefaultConfigurationProvider.java:53)*
* at
de.jollyday.configuration.ConfigurationProviderManager.addInternalConfigurationProviderProperies(ConfigurationProviderManager.java:64)*
* at
de.jollyday.configuration.ConfigurationProviderManager.getConfigurationProperties(ConfigurationProviderManager.java:55)*
* at de.jollyday.HolidayManager.createManager(HolidayManager.java:274)*
* at de.jollyday.HolidayManager.getI

Re: [Dev] calling javascript methods in an external js file from gwt JSNI native mthods

[Awanthika Senarath]

Hi all,

I have successfully achieved this with GWT script injection and JSNI native
methods. Thanks for the input.

thanks and regards
Awanthika


On Thu, Sep 4, 2014 at 7:55 AM, Awanthika Senarath 
wrote:

> Hi Danushka,
>
> I don't think Jaggery is an option as we are using this to implement a
> jQuery, JavaScript and jsplumb based application in GWT. I am having the
> problem in calling the js page functions from the JSNI native Java methods.
> The js file is imported from html page. GWT compiles my Java code to
> JavaScript and calls the js page. But the error to my understanding states
> that the source js file is unknown in gwt context.
>
> thanks and regards
> Awanthika
>
>
>
> On Wed, Sep 3, 2014 at 9:01 PM, Danushka Fernando 
> wrote:
>
>> Hi
>> When I read your description and code segments [2] what I understood was
>> you are having a problem with referring to a separate js file from a html
>> page. When I read the [1] and exception trace what I understood was when
>> you referred to an external js file you are having some troubles calling
>> the java method. However assuming latter is the case, may be changing the
>> order of your js imports will help.
>> BTW jaggery facilitates the same thing you are trying to achieve here.
>> Can't you use jaggery for your implementation?
>>
>> Thanks & Regards
>> Danushka Fernando
>> Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>>
>> On Wed, Sep 3, 2014 at 6:10 PM, Sohani Weerasinghe 
>> wrote:
>>
>>> Can you try the option available at [1] where it uses ScriptResources
>>> for ClientBundle instead of  tags.
>>>
>>> [1] https://plus.google.com/u/0/+RayCromwell/posts/g3TmFeao8kK
>>>
>>> Thanks,
>>> Sohani
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>>
>>> On Wed, Sep 3, 2014 at 4:41 PM, Awanthika Senarath 
>>> wrote:
>>>
 Hi all,

 I am trying to do $Subject.

  When the JavaScript method is in the  of html file itself  I can
 call the method from module load as a native method using JSN [1]I. But
 when i refer to the js file from html page [2]  and put the method in to
 the js file i get the following gwt error[3]. Has anyone ever attempted
 anything similar and achieved it successfully?

 [1]   in java class
 public static native void gwtjsPlumbDemo() /*-{

   $wnd.gwtjsplumbdemo();

  }-*/;


 [2] in gwtjsplumbdemo.js file
  function gwtjsplumbdemo() {
 alert("Success!!!");
 }
  in html