Re: [Dev] [Build Failure] Could not find artifact org.wso2.carbon:org.wso2.carbon.identity.core.feature:zip:4.3.0-SNAPSHOT

[Chamath Gunawardana]

Hi Subash,

The org.wso2.carbon.identity.core.feature is planned move to
carbon-identity. Since we still haven't stabilize the carbon-identity in
git you'll get this error. However you could use 4.2.0 instead of 4.3.0
until we complete the stabilization which is planned after the IS 4.7.0
release (due in 2nd week of April).




On Thu, Mar 13, 2014 at 11:57 AM, Subash Chaturanga  wrote:

> Hi Asela et al,
> I am getting when building platform on the new GIT repo. This is suppose
> to be available in the snapshot repo. Currently HT,apimgt etc are all
> available in the repo. Any reason why this is not available ? Please note
> this is a blocker for GReg 5 milestone releases.
>
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 3:44.262s
> [INFO] Finished at: Thu Mar 13 11:50:03 IST 2014
> [INFO] Final Memory: 8M/490M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on
> project governance-profile-gen: Error occured when processing the Feature
> Artifact:
> org.wso2.carbon:org.wso2.carbon.identity.core.feature:4.3.0-SNAPSHOT:
> ERROR: Could not find artifact
> org.wso2.carbon:org.wso2.carbon.identity.core.feature:zip:4.3.0-SNAPSHOT in
> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
> [ERROR]
> [ERROR] Try downloading the file manually from the project website.
> [ERROR]
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon
> -DartifactId=org.wso2.carbon.identity.core.feature -Dversion=4.3.0-SNAPSHOT
> -Dpackaging=zip -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon
> -DartifactId=org.wso2.carbon.identity.core.feature -Dversion=4.3.0-SNAPSHOT
> -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR]
> [ERROR]
> [ERROR]
> org.wso2.carbon:org.wso2.carbon.identity.core.feature:zip:4.3.0-SNAPSHOT
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] wso2-nexus (
> http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true,
> snapshots=true),
> [ERROR] wso2.releases (
> http://maven.wso2.org/nexus/content/repositories/releases/,
> releases=true, snapshots=true),
> [ERROR] wso2.snapshots (
> http://maven.wso2.org/nexus/content/repositories/snapshots/,
> releases=false, snapshots=true),
> [ERROR] central (http://repo1.maven.org/maven2, releases=true,
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR]
>
>
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>
> email: sub...@wso2.com
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>



-- 
Thanks,
Best Regards,
Chamath Gunawardana
Technical Lead; WSO2 Inc.
Mobile : +94776322240
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maven Resolving issue

[Aruna Karunarathna]

Hi Iroshan,

Have you tried  mvn idea:idea  command?..

In the terminal go the location of pom.xml file and issue the above command.


Regards,


On Thu, Mar 13, 2014 at 12:10 PM, Iroshan Wickramarathna
wrote:

> Hi all,
>
> I'm writing a carbon component for CEP event simulator , When I writing
> the UI component (org.wso2.carbon.eventsimulator.ui) it can't resolve the
> imported packages. How can I over come this problem ?. Screen shots are
> displayd below. I'm using Intellij idea 13.0.1 not sure if it is a Intellij
> idea issue.
>
> this is the pom.xml
>
> 
> http://maven.apache.org/POM/4.0.0";
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 
> event-simulator
> org.wso2.carbon
> 1.0.0
> 
>
> 4.0.0
>
> org.wso2.carbon.eventsimulator.ui
> 1.0.0
> bundle
>
> WSO2 Carbon - Event Simulator UI
> org.wso2.carbon.eventsimulator.UI provides the front-end
> functionalities
> 
> http://wso2.org
>
> 
>
> 
> org.wso2.carbon
> org.wso2.carbon.eventsimulator.admin
> 1.0.0
> 
>
> 
> org.wso2.carbon
> org.wso2.carbon.utils
> 4.2.0
> 
>
> 
> org.wso2.carbon
> org.wso2.carbon.eventsimulator.stub
> 1.0.1
> 
>
> 
> org.wso2.carbon
> org.wso2.carbon.databridge.core
> 4.2.1
> 
> 
> org.wso2.carbon
> org.wso2.carbon.core
> 4.2.0
> 
> 
> org.wso2.carbon
>
> org.wso2.carbon.event.stream.manager.core
> 1.0.1
> 
> 
> org.wso2.carbon
> org.wso2.carbon.event.processor.api
> 1.0.1
> 
>
> 
>
>
>
>
>
> 
>
>
> --
> Thanx.
> Ujitha Iroshan
> Engineering intern
> WSO2 inc
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] Enhanced GitHub pull request plugin with WSO2 Jenkins

[Chan]

+1 to get the continuos delivery model blogged out. Also this would help
many other organizations and teams if we setup a proper guideline on our
continuos delivery model.

Cheers~


On Thu, Mar 13, 2014 at 12:07 PM, Kasun Gajasinghe  wrote:

> Hi Azeez,
>
> We have not enabled the said plugin in our Jenkins setup yet.
> @Ayashkantha, please send the necessary artifacts (the .spi is enough?) to
> install this plugin.
>
> I think we might need to have another jenkins node (as a slave node) for
> the Pull Request builder plugin ( preferably on a new VM depending on the
> load).  We noticed that when we installed the original jenkins plugin, it
> has messed up the entire jenkins builds, and we had to re-configure a new
> jenkins instance.
>
> Thanks,
> KasunG
>
>
>
> On Thu, Mar 13, 2014 at 11:34 AM, Afkham Azeez  wrote:
>
>> Ping! Need an update ASAP.
>>
>>
>> On Wed, Mar 12, 2014 at 10:59 AM, Afkham Azeez  wrote:
>>
>>> Have we enabled this plugin on our Jenkins setup?
>>>
>>> Where do we maintain this code? Perhaps we have the fork within the WSO2
>>> repo?
>>>
>>> Did we send the enhancements as pull requests to the relevant original
>>> repos? If not, please do so with the proper comments explaining what the
>>> enhancement does.
>>>
>>> Write a blog post about this, Tweet it etc. and make some noise about
>>> this and our vision towards continuous delivery.
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * *
>>> *email: **az...@wso2.com* 
>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: 
>>> **http://twitter.com/afkham_azeez*
>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2Mobile
Lean.Enterprise.Mobileware
 * ~Email   duli...@wso2.com *
*  ~Mobile +94712112165*
*  ~Website   dulitha.me *
*  ~Twitter @dulitharw *
  *~SO @chan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 BAM 2.4.1 Alpha Released!

[Shavantha Weerasinghe]

Hi Evanthika

Due to the below exception, I will continue to test CEP scenarios with
the BAM M1 pack.

[2014-03-13 12:55:53,044]  INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
WSO2 Carbon started in 20 sec
[2014-03-13 12:55:54,725]  INFO
{org.wso2.carbon.dashboard.common.oauth.GSOAuthModule} -  Using random
key for OAuth client-side state encryption
[2014-03-13 12:55:55,415]  INFO
{org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console
URL  : https://10.100.0.94:9443/carbon/
[2014-03-13 12:55:55,415]  INFO
{org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Gadget
Server Default Context : http://10.100.0.94:9763/portal
[2014-03-13 12:55:55,461] ERROR
{org.wso2.carbon.event.builder.core.EventBuilderDeployer} -  Invalid
configuration in event builder configuration file :EventBuilder.xml
java.lang.NullPointerException
at 
org.wso2.carbon.event.input.adaptor.http.HTTPEventEventAdaptorType.subscribe(HTTPEventEventAdaptorType.java:136)
at 
org.wso2.carbon.event.input.adaptor.core.internal.CarbonInputEventAdaptorService.subscribe(CarbonInputEventAdaptorService.java:104)
at 
org.wso2.carbon.event.builder.core.internal.EventBuilder.subscribeToEventAdaptor(EventBuilder.java:153)
at 
org.wso2.carbon.event.builder.core.internal.config.StreamJunctionManager.registerEventSender(StreamJunctionManager.java:72)
at 
org.wso2.carbon.event.builder.core.internal.CarbonEventBuilderService.addEventBuilder(CarbonEventBuilderService.java:198)
at 
org.wso2.carbon.event.builder.core.EventBuilderDeployer.processDeployment(EventBuilderDeployer.java:186)
at 
org.wso2.carbon.event.builder.core.internal.util.helper.EventBuilderConfigurationFileSystemInvoker.reload(EventBuilderConfigurationFileSystemInvoker.java:158)
at 
org.wso2.carbon.event.builder.core.internal.CarbonEventBuilderService.activateInactiveEventBuilderConfigurationsForAdaptor(CarbonEventBuilderService.java:576)
at 
org.wso2.carbon.event.builder.core.internal.InputEventAdaptorNotificationListenerImpl.configurationAdded(InputEventAdaptorNotificationListenerImpl.java:38)
at 
org.wso2.carbon.event.input.adaptor.manager.core.InputEventAdaptorDeployer.processDeploy(InputEventAdaptorDeployer.java:180)
at 
org.wso2.carbon.event.input.adaptor.manager.core.internal.util.helper.InputEventAdaptorConfigurationFilesystemInvoker.reload(InputEventAdaptorConfigurationFilesystemInvoker.java:119)
at 
org.wso2.carbon.event.input.adaptor.manager.core.internal.CarbonInputEventAdaptorManagerService.activateInactiveInputEventAdaptorConfiguration(CarbonInputEventAdaptorManagerService.java:440)
at 
org.wso2.carbon.event.input.adaptor.manager.core.internal.ds.InputEventAdaptorTypeServiceTrackerDS.notifyNewEventAdaptorType(InputEventAdaptorTypeServiceTrackerDS.java:51)
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.ComponentReference.bind(ComponentReference.java:376)
at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:446)
at 
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:416)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:334)
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.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at 
org.wso2.carbon.event.input.adaptor.core.internal.CarbonInputEventAdaptorService.registerEventAdaptor(CarbonInputEventAdaptorService.java:55)
at 
org.wso2.carbon.event.input.adaptor.core.internal.ds.InputEventAdaptorServiceTrackerDS.setEventAdaptorType(InputEventAdaptorService

Re: [Dev] Enhanced GitHub pull request plugin with WSO2 Jenkins

[Sagara Gunathunga]

On Thu, Mar 13, 2014 at 2:14 PM, Ayash  wrote:

> Hi,
>
> To install the plug-in to jenkins,
>
> 1. Install the github-plugin
> 2. Install the plug-ins attached herewith.
> 3. Restart Jenkins
>
> For now, I'll commit the code in the wso2 github repo and will send the
> pull request to original jenkins plug-ins too and will check if they commit
> our change to the original plug-ins. I'll update this thread with git repo
> of the code.
>

Why don't you write a blog post on this ?

Thanks !

>
> Thanks,
> -Ayash
>
>
>
> On Thu, Mar 13, 2014 at 1:09 PM, Chan  wrote:
>
>> +1 to get the continuos delivery model blogged out. Also this would help
>> many other organizations and teams if we setup a proper guideline on our
>> continuos delivery model.
>>
>> Cheers~
>>
>>
>> On Thu, Mar 13, 2014 at 12:07 PM, Kasun Gajasinghe wrote:
>>
>>> Hi Azeez,
>>>
>>> We have not enabled the said plugin in our Jenkins setup yet.
>>> @Ayashkantha, please send the necessary artifacts (the .spi is enough?) to
>>> install this plugin.
>>>
>>> I think we might need to have another jenkins node (as a slave node) for
>>> the Pull Request builder plugin ( preferably on a new VM depending on the
>>> load).  We noticed that when we installed the original jenkins plugin, it
>>> has messed up the entire jenkins builds, and we had to re-configure a new
>>> jenkins instance.
>>>
>>> Thanks,
>>> KasunG
>>>
>>>
>>>
>>> On Thu, Mar 13, 2014 at 11:34 AM, Afkham Azeez  wrote:
>>>
 Ping! Need an update ASAP.


 On Wed, Mar 12, 2014 at 10:59 AM, Afkham Azeez  wrote:

> Have we enabled this plugin on our Jenkins setup?
>
> Where do we maintain this code? Perhaps we have the fork within the
> WSO2 repo?
>
> Did we send the enhancements as pull requests to the relevant original
> repos? If not, please do so with the proper comments explaining what the
> enhancement does.
>
> Write a blog post about this, Tweet it etc. and make some noise about
> this and our vision towards continuous delivery.
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: 
> **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * *
 *email: **az...@wso2.com* 
 * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
 *http://blog.afkham.org* 
 *twitter: 
 **http://twitter.com/afkham_azeez*
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 *

 *Lean . Enterprise . Middleware*

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


>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>>
>>> *twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Chan (Dulitha Wijewantha)
>> Software Engineer - Mobile Development
>>  WSO2Mobile
>> Lean.Enterprise.Mobileware
>>  * ~Email   duli...@wso2.com *
>> *  ~Mobile +94712112165 <%2B94712112165>*
>> *  ~Website   dulitha.me *
>> *  ~Twitter @dulitharw *
>>   *~SO @chan *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ayashkantha Ramasinghe
> Software Engineer WSO2, Inc.
> email: ayashkan...@wso2.com ;
> TP: +94 77 7 487 669
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sagara Gunathunga

Senior Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
__

Re: [Dev] Enhanced GitHub pull request plugin with WSO2 Jenkins

[Ayash]

On Thu, Mar 13, 2014 at 2:19 PM, Sagara Gunathunga  wrote:

>
>
>
> On Thu, Mar 13, 2014 at 2:14 PM, Ayash  wrote:
>
>> Hi,
>>
>> To install the plug-in to jenkins,
>>
>> 1. Install the github-plugin
>> 2. Install the plug-ins attached herewith.
>> 3. Restart Jenkins
>>
>> For now, I'll commit the code in the wso2 github repo and will send the
>> pull request to original jenkins plug-ins too and will check if they commit
>> our change to the original plug-ins. I'll update this thread with git repo
>> of the code.
>>
>
> Why don't you write a blog post on this ?
>

I'll commit the code and publish a blog post. I need to point the code in
the blog post itself.

Thanks,
-Ayash


>
> Thanks !
>
>>
>> Thanks,
>> -Ayash
>>
>>
>>
>> On Thu, Mar 13, 2014 at 1:09 PM, Chan  wrote:
>>
>>> +1 to get the continuos delivery model blogged out. Also this would help
>>> many other organizations and teams if we setup a proper guideline on our
>>> continuos delivery model.
>>>
>>> Cheers~
>>>
>>>
>>> On Thu, Mar 13, 2014 at 12:07 PM, Kasun Gajasinghe wrote:
>>>
 Hi Azeez,

 We have not enabled the said plugin in our Jenkins setup yet.
 @Ayashkantha, please send the necessary artifacts (the .spi is enough?) to
 install this plugin.

 I think we might need to have another jenkins node (as a slave node)
 for the Pull Request builder plugin ( preferably on a new VM depending on
 the load).  We noticed that when we installed the original jenkins plugin,
 it has messed up the entire jenkins builds, and we had to re-configure a
 new jenkins instance.

 Thanks,
 KasunG



 On Thu, Mar 13, 2014 at 11:34 AM, Afkham Azeez  wrote:

> Ping! Need an update ASAP.
>
>
> On Wed, Mar 12, 2014 at 10:59 AM, Afkham Azeez  wrote:
>
>> Have we enabled this plugin on our Jenkins setup?
>>
>> Where do we maintain this code? Perhaps we have the fork within the
>> WSO2 repo?
>>
>> Did we send the enhancements as pull requests to the relevant
>> original repos? If not, please do so with the proper comments explaining
>> what the enhancement does.
>>
>> Write a blog post about this, Tweet it etc. and make some noise about
>> this and our vision towards continuous delivery.
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* 
>> *twitter: 
>> **http://twitter.com/afkham_azeez*
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: 
> **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Kasun Gajasinghe*
 Software Engineer;
 WSO2 Inc.; http://wso2.com


  ,
 *email: *
 *kasung AT spamfree wso2.com    ** cell: **+94 (77)
 678-0813 <%2B94%20%2877%29%20678-0813>*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe



 *blog: **http://kasunbg.org* 



 *twitter: **http://twitter.com/kasunbg* 




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


>>>
>>>
>>> --
>>> Chan (Dulitha Wijewantha)
>>> Software Engineer - Mobile Development
>>>  WSO2Mobile
>>> Lean.Enterprise.Mobileware
>>>  * ~Email   duli...@wso2.com *
>>> *  ~Mobile +94712112165 <%2B94712112165>*
>>> *  ~Website   dulitha.me *
>>> *  ~Twitter @dulitharw *
>>>   *~SO @chan *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ayashkantha Ramasinghe
>> Software Engineer WSO2, Inc.
>> email: ayashkan...@wso2.com ;
>> TP: +94 77 7 487 669
>>
>

[Dev] [GReg P2 Failure] Missing requirement: Carbon Product 4.2.0 (carbon.product.id 4.2.0) requires 'org.wso2.carbon.core.runtime.feature.group [4.2.0]' but it could not be foun

[Subash Chaturanga]

Hi
I am getting this when building product GReg in Git.  Any ideas ?


/bin/sh -c cd
/home/subash/development/git-repo/product-greg/modules/p2-profile-gen &&
/opt/jdk1.6.0_45/jre/bin/java -jar
/home/subash/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
-nosplash -application org.eclipse.equinox.p2.director -metadataRepository
file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/p2-repo
-artifactRepository
file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/p2-repo
-installIU carbon.product.id -profileProperties
org.eclipse.update.install.features=true -profile repository -bundlepool
file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components
-shared
file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/p2
-destination
file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/repository
-p2.os linux -p2.ws gtk -p2.arch x86 -roaming
Installing carbon.product.id 4.2.0.
Installation failed.
Cannot complete the install because one or more required items could not be
found.
 Software being installed: Carbon Product 4.2.0 (carbon.product.id 4.2.0)
* Missing requirement: Carbon Product 4.2.0 (carbon.product.id
 4.2.0) requires
'org.wso2.carbon.core.runtime.feature.group [4.2.0]' but it could not be
found*
Application failed, log file location:
/home/subash/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1394700904679.log

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Governance Registry - P2 Profile Generation .. FAILURE [28.102s]
[INFO] WSO2 Stratos - Cloud Governance Login User Interface  SKIPPED
[INFO] WSO2 API Manager - BAM Toolbox  SKIPPED
[INFO] WSO2 Governance Registry - Distribution ... SKIPPED
[INFO] WSO2 Governance Registry - Integration Tests ..



-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Enhanced GitHub pull request plugin with WSO2 Jenkins

[Sagara Gunathunga]

On Thu, Mar 13, 2014 at 2:59 PM, Ayash  wrote:

>
>
>
> On Thu, Mar 13, 2014 at 2:19 PM, Sagara Gunathunga wrote:
>
>>
>>
>>
>> On Thu, Mar 13, 2014 at 2:14 PM, Ayash  wrote:
>>
>>> Hi,
>>>
>>> To install the plug-in to jenkins,
>>>
>>> 1. Install the github-plugin
>>> 2. Install the plug-ins attached herewith.
>>> 3. Restart Jenkins
>>>
>>> For now, I'll commit the code in the wso2 github repo and will send the
>>> pull request to original jenkins plug-ins too and will check if they commit
>>> our change to the original plug-ins. I'll update this thread with git repo
>>> of the code.
>>>
>>
>> Why don't you write a blog post on this ?
>>
>
> I'll commit the code and publish a blog post. I need to point the code in
> the blog post itself.
>

+1 BTW  please make sure you commit forked code first without your changes
and then  commit your changes otherwise it's hard to merge your changes
into original repo in future.

Thanks !

>
> Thanks,
> -Ayash
>
>
>>
>> Thanks !
>>
>>>
>>> Thanks,
>>> -Ayash
>>>
>>>
>>>
>>> On Thu, Mar 13, 2014 at 1:09 PM, Chan  wrote:
>>>
 +1 to get the continuos delivery model blogged out. Also this would
 help many other organizations and teams if we setup a proper guideline on
 our continuos delivery model.

 Cheers~


 On Thu, Mar 13, 2014 at 12:07 PM, Kasun Gajasinghe wrote:

> Hi Azeez,
>
> We have not enabled the said plugin in our Jenkins setup yet.
> @Ayashkantha, please send the necessary artifacts (the .spi is enough?) to
> install this plugin.
>
> I think we might need to have another jenkins node (as a slave node)
> for the Pull Request builder plugin ( preferably on a new VM depending on
> the load).  We noticed that when we installed the original jenkins plugin,
> it has messed up the entire jenkins builds, and we had to re-configure a
> new jenkins instance.
>
> Thanks,
> KasunG
>
>
>
> On Thu, Mar 13, 2014 at 11:34 AM, Afkham Azeez  wrote:
>
>> Ping! Need an update ASAP.
>>
>>
>> On Wed, Mar 12, 2014 at 10:59 AM, Afkham Azeez wrote:
>>
>>> Have we enabled this plugin on our Jenkins setup?
>>>
>>> Where do we maintain this code? Perhaps we have the fork within the
>>> WSO2 repo?
>>>
>>> Did we send the enhancements as pull requests to the relevant
>>> original repos? If not, please do so with the proper comments explaining
>>> what the enhancement does.
>>>
>>> Write a blog post about this, Tweet it etc. and make some noise
>>> about this and our vision towards continuous delivery.
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * *
>>> *email: **az...@wso2.com* 
>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: 
>>> **http://twitter.com/afkham_azeez*
>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* 
>> *twitter: 
>> **http://twitter.com/afkham_azeez*
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Chan (Dulitha Wijewantha)
 Software Engineer - Mobile Development
  WSO2Mobile
 Lean.Enterprise.Mobileware
  * ~Email   duli...@wso2.com *
 *  ~Mobile +94712112165 <%2B94712112165>*
 *  ~Website   dulitha.me 

[Dev] Kernel commit for patch0006

[Darshana Gunawardana]

Hi Kernel team,

Can you please commit patch in [1] to fix caching issue in user.core.

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

Thanks,


-- 
Regards,


*Darshana Gunawardana*Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com  *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Dev-MB] Guaranteed Message Delivery issue in fail over

[Iranga Muthuthanthri]

Hi All,

In a MB message produce consume scenario for fail over, if the message
producing MB node fails before delivering all the messages it was observed
that there was a message loss(by observing the Cassandra  queue count).

What are the workaround possible for this considering the guaranteed
message delivery model.

Note: The message consuming and producing MB nodes are the same.


-- 
Thanks & Regards

Iranga Muthuthanthri
Technical Lead - QA
(M) -0777-255773
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GReg P2 Failure] Missing requirement: Carbon Product 4.2.0 (carbon.product.id 4.2.0) requires 'org.wso2.carbon.core.runtime.feature.group [4.2.0]' but it could not be foun

[Kasun Gajasinghe]

You might want to update the version in the carbon.product file. It should
reside in your p2-profile-gen

On Thursday, March 13, 2014, Subash Chaturanga  wrote:

> Hi
> I am getting this when building product GReg in Git.  Any ideas ?
>
>
> /bin/sh -c cd
> /home/subash/development/git-repo/product-greg/modules/p2-profile-gen &&
> /opt/jdk1.6.0_45/jre/bin/java -jar
> /home/subash/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/p2-repo
> -artifactRepository
> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/p2-repo
> -installIU carbon.product.id -profileProperties
> org.eclipse.update.install.features=true -profile repository -bundlepool
> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components
> -shared
> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/p2
> -destination
> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/repository
> -p2.os linux -p2.ws gtk -p2.arch x86 -roaming
> Installing carbon.product.id 4.2.0.
> Installation failed.
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: Carbon Product 4.2.0 (carbon.product.id 4.2.0)
> * Missing requirement: Carbon Product 4.2.0 (carbon.product.id
>  4.2.0) requires
> 'org.wso2.carbon.core.runtime.feature.group [4.2.0]' but it could not be
> found*
> Application failed, log file location:
> /home/subash/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1394700904679.log
>
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Governance Registry - P2 Profile Generation .. FAILURE
> [28.102s]
> [INFO] WSO2 Stratos - Cloud Governance Login User Interface  SKIPPED
> [INFO] WSO2 API Manager - BAM Toolbox  SKIPPED
> [INFO] WSO2 Governance Registry - Distribution ... SKIPPED
> [INFO] WSO2 Governance Registry - Integration Tests ..
>
>
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>
> email: sub...@wso2.com 
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>


-- 
*Kasun Gajasinghe*
Software Engineer;
WSO2 Inc.; http://wso2.com


 ,
*email: *
*kasung AT spamfree wso2.com   ** cell: **+94 (77)
678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe



*blog: **http://kasunbg.org* 



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

Re: [Dev] [Dev-MB] Guaranteed Message Delivery issue in fail over

[Ishara Premadasa]

Hi Iranga,

What are the failover options you have used in the connection string? Are
there 'retries' and 'connectdelay' options configured. They determine the
number of times a connection to a broker will be retried and the the length
of time to wait between successive connection attempts before moving on to
the next broker in. Have we tried with setting retires to 1 and
connectdelay to 0 ( which are default values) so then the broker will try
to connect immediately to the next one available?

Thanks!


On Thu, Mar 13, 2014 at 3:59 PM, Iranga Muthuthanthri wrote:

> Hi All,
>
> In a MB message produce consume scenario for fail over, if the message
> producing MB node fails before delivering all the messages it was observed
> that there was a message loss(by observing the Cassandra  queue count).
>
> What are the workaround possible for this considering the guaranteed
> message delivery model.
>
> Note: The message consuming and producing MB nodes are the same.
>
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> Technical Lead - QA
> (M) -0777-255773
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Kernel commit for patch0006

[Manoj Kumara]

Hi,

Committed to patch0006 with 198259. Please merge these changes to git dev
repo [1]

[1] https://github.com/wso2-dev/carbon4-kernel

Thanks,
Manoj


*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188


On Thu, Mar 13, 2014 at 3:35 PM, Darshana Gunawardana wrote:

> Hi Kernel team,
>
> Can you please commit patch in [1] to fix caching issue in user.core.
>
> [1] https://wso2.org/jira/browse/IDENTITY-2056
>
> Thanks,
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com  *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GReg P2 Failure] Missing requirement: Carbon Product 4.2.0 (carbon.product.id 4.2.0) requires 'org.wso2.carbon.core.runtime.feature.group [4.2.0]' but it could not be foun

[Subash Chaturanga]

Thanks Kasun


On Thu, Mar 13, 2014 at 4:14 PM, Kasun Gajasinghe  wrote:

> You might want to update the version in the carbon.product file. It should
> reside in your p2-profile-gen
>
>
> On Thursday, March 13, 2014, Subash Chaturanga  wrote:
>
>> Hi
>> I am getting this when building product GReg in Git.  Any ideas ?
>>
>>
>>  /bin/sh -c cd
>> /home/subash/development/git-repo/product-greg/modules/p2-profile-gen &&
>> /opt/jdk1.6.0_45/jre/bin/java -jar
>> /home/subash/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
>> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
>> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/p2-repo
>> -artifactRepository
>> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/p2-repo
>> -installIU carbon.product.id -profileProperties
>> org.eclipse.update.install.features=true -profile repository -bundlepool
>> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components
>> -shared
>> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/p2
>> -destination
>> file:/home/subash/development/git-repo/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/repository
>> -p2.os linux -p2.ws gtk -p2.arch x86 -roaming
>> Installing carbon.product.id 4.2.0.
>> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: Carbon Product 4.2.0 (carbon.product.id 4.2.0)
>> * Missing requirement: Carbon Product 4.2.0 (carbon.product.id
>>  4.2.0) requires
>> 'org.wso2.carbon.core.runtime.feature.group [4.2.0]' but it could not be
>> found*
>> Application failed, log file location:
>> /home/subash/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1394700904679.log
>>
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 Governance Registry - P2 Profile Generation .. FAILURE
>> [28.102s]
>> [INFO] WSO2 Stratos - Cloud Governance Login User Interface  SKIPPED
>> [INFO] WSO2 API Manager - BAM Toolbox  SKIPPED
>> [INFO] WSO2 Governance Registry - Distribution ... SKIPPED
>> [INFO] WSO2 Governance Registry - Integration Tests ..
>>
>>
>>
>> --
>> Thanks
>> /subash
>>
>> *Subash Chaturanga*
>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>>
>> email: sub...@wso2.com
>> blog:  http://subashsdm.blogspot.com/
>> twitter: @subash89
>> phone: +9477 2225922
>> Lean . Enterprise . Middleware
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>
>


-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Usage of 'AccessTokenDefaultValidityPeriod' in identity.xml

[Nirodha Pramod]

Hi,

What's the usage of  in identity.xml  in
the context of API-M. There is already,
   and
 configurations as well which are
used to configure expiration times of Application Access token and User
Tokens.  So what's the usage of the first one.

thanks,
Nirodha
-- 

*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Dev-MB] Guaranteed Message Delivery issue in fail over

[Supun Malinga]

Hi,

Related to the topic,
I have observed that sometimes (intermittantly and with a load) jms
consumer fails to read the messages from the  response queue even though
the messages *are* in the reply queue with correct correlation id.
Is this a known issue ?.

thanks,


On Thu, Mar 13, 2014 at 6:45 AM, Ishara Premadasa  wrote:

> Hi Iranga,
>
> What are the failover options you have used in the connection string? Are
> there 'retries' and 'connectdelay' options configured. They determine the
> number of times a connection to a broker will be retried and the the length
> of time to wait between successive connection attempts before moving on to
> the next broker in. Have we tried with setting retires to 1 and
> connectdelay to 0 ( which are default values) so then the broker will try
> to connect immediately to the next one available?
>
> Thanks!
>
>
> On Thu, Mar 13, 2014 at 3:59 PM, Iranga Muthuthanthri wrote:
>
>> Hi All,
>>
>> In a MB message produce consume scenario for fail over, if the message
>> producing MB node fails before delivering all the messages it was observed
>> that there was a message loss(by observing the Cassandra  queue count).
>>
>> What are the workaround possible for this considering the guaranteed
>> message delivery model.
>>
>> Note: The message consuming and producing MB nodes are the same.
>>
>>
>> --
>> Thanks & Regards
>>
>> Iranga Muthuthanthri
>> Technical Lead - QA
>> (M) -0777-255773
>>
>
>
>
> --
> Ishara Premasada
> Software Engineer,
> WSO2 Inc. http://wso2.com/
>
>
> *Blog   :  http://isharapremadasa.blogspot.com/
> Twitter   :
> https://twitter.com/ishadil  Mobile   :
> +94 714445832 <%2B94%20714445832>*
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
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] Kernel commit for patch0006

[Darshana Gunawardana]

Thank manoj.

For the git repo, sent a pull request [1].

[1 ]https://github.com/wso2-dev/carbon4-kernel/pull/5


On Thu, Mar 13, 2014 at 4:22 PM, Manoj Kumara  wrote:

> Hi,
>
> Committed to patch0006 with 198259. Please merge these changes to git dev
> repo [1]
>
> [1] https://github.com/wso2-dev/carbon4-kernel
>
> Thanks,
> Manoj
>
>
> *Manoj Kumara*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94713448188
>
>
> On Thu, Mar 13, 2014 at 3:35 PM, Darshana Gunawardana 
> wrote:
>
>> Hi Kernel team,
>>
>> Can you please commit patch in [1] to fix caching issue in user.core.
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-2056
>>
>> Thanks,
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Software Engineer
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com  *
>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>
>
>


-- 
Regards,


*Darshana Gunawardana *Software Engineer
WSO2 Inc.; http://wso2.com

* E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Siddhi Query Issue

[Sriskandarajah Suhothayan]

you are referring to an older version of Siddhi,

try

from cseEventStream [ price >= 50] select *symbol, price* insert into
StockQuote ;



On Thu, Mar 13, 2014 at 4:54 PM, Seshika Fernando  wrote:

>
> Hi Suho,
>
> I get the following error (copied below) when running the Siddhi
> SimpleFilter sample from the latest code path. I noticed that this is
> caused by the query "from cseEventStream [ price >= 50] insert into
> StockQuote *symbol, price*;". I got around it by taking off the part in
> bold.
> However I have seen the same query used in the above format (without any
> errors) in the quick-start-samples from
> https://svn.wso2.org/repos/wso2/people/suho/packs/siddhi/siddhi-1.0.1-wso2v1-samples.zip
> .
> Is there any particular reason why this fails in the latest release?
>
>
> simpleFilter:
>  [java] Exception in thread "main"
> org.wso2.siddhi.query.compiler.exception.SiddhiParserException: line 1:60
> missing EOF at 'symbol'
>  [java] at
> org.wso2.siddhi.query.compiler.SiddhiCompiler.parseQuery(SiddhiCompiler.java:141)
>  [java] at
> org.wso2.siddhi.core.SiddhiManager.addQuery(SiddhiManager.java:273)
>  [java] at org.wso2.siddhi.sample.SimpleFilterSample.main(Unknown
> Source)
>  [java] Caused by:
> org.wso2.siddhi.query.compiler.exception.SiddhiParserException: line 1:60
> missing EOF at 'symbol'
>  [java] at
> org.wso2.siddhi.query.compiler.SiddhiQLGrammarParser.emitErrorMessage(SiddhiQLGrammarParser.java:192)
>  [java] at
> org.antlr.runtime.BaseRecognizer.displayRecognitionError(BaseRecognizer.java:194)
>  [java] at
> org.antlr.runtime.BaseRecognizer.reportError(BaseRecognizer.java:186)
>  [java] at
> org.antlr.runtime.BaseRecognizer.recoverFromMismatchedToken(BaseRecognizer.java:613)
>  [java] at
> org.antlr.runtime.BaseRecognizer.match(BaseRecognizer.java:115)
>  [java] at
> org.wso2.siddhi.query.compiler.SiddhiQLGrammarParser.queryFinal(SiddhiQLGrammarParser.java:1948)
>  [java] at
> org.wso2.siddhi.query.compiler.SiddhiCompiler.parseQuery(SiddhiCompiler.java:133)
>  [java] ... 2 more
>  [java] Java Result: 1
>
>
> Seshika
>
>


-- 

*S. Suhothayan*
Associate Technical Lead,
 *WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Usage of 'AccessTokenDefaultValidityPeriod' in identity.xml

[Sanjeewa Malalgoda]

In oauth component we don't use AccessTokenDefaultValidityPeriod parameter
now. Most probably this might be there because we missed to remove this
while re factoring code.

Thanks,
sanjeewa.


On Thu, Mar 13, 2014 at 4:45 PM, Nirodha Pramod  wrote:

> Hi,
>
> What's the usage of  in identity.xml  in
> the context of API-M. There is already,
>and
>  configurations as well which are
> used to configure expiration times of Application Access token and User
> Tokens.  So what's the usage of the first one.
>
> thanks,
> Nirodha
> --
>
> *Nirodha Gallage*
> Senior Software Engineer, QA.
> WSO2 Inc.: http://wso2.com/
> Mobile: +94716429078
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

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

Re: [Dev] [Dev-MB] Guaranteed Message Delivery issue in fail over

[Iranga Muthuthanthri]

Hi Ishara,

Thanks for the suggestion, the problem is what happens at the wire level in
the message producer when the message broker is down, before the message is
received by the consumer .

@ Supun:  Yes, This has been observed intermittently





On Thu, Mar 13, 2014 at 4:57 PM, Supun Malinga  wrote:

> Hi,
>
> Related to the topic,
> I have observed that sometimes (intermittantly and with a load) jms
> consumer fails to read the messages from the  response queue even though
> the messages *are* in the reply queue with correct correlation id.
> Is this a known issue ?.
>
> thanks,
>
>
> On Thu, Mar 13, 2014 at 6:45 AM, Ishara Premadasa  wrote:
>
>> Hi Iranga,
>>
>> What are the failover options you have used in the connection string? Are
>> there 'retries' and 'connectdelay' options configured. They determine the
>> number of times a connection to a broker will be retried and the the length
>> of time to wait between successive connection attempts before moving on to
>> the next broker in. Have we tried with setting retires to 1 and
>> connectdelay to 0 ( which are default values) so then the broker will try
>> to connect immediately to the next one available?
>>
>> Thanks!
>>
>>
>> On Thu, Mar 13, 2014 at 3:59 PM, Iranga Muthuthanthri wrote:
>>
>>> Hi All,
>>>
>>> In a MB message produce consume scenario for fail over, if the message
>>> producing MB node fails before delivering all the messages it was observed
>>> that there was a message loss(by observing the Cassandra  queue count).
>>>
>>> What are the workaround possible for this considering the guaranteed
>>> message delivery model.
>>>
>>> Note: The message consuming and producing MB nodes are the same.
>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Iranga Muthuthanthri
>>> Technical Lead - QA
>>> (M) -0777-255773
>>>
>>
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> Twitter   :
>> https://twitter.com/ishadil  Mobile   :
>> +94 714445832 <%2B94%20714445832>*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>



-- 
Thanks & Regards

Iranga Muthuthanthri
Technical Lead - QA
(M) -0777-255773
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Committing 4.2.0 kernel patches to 4.3.0 in Git repo

[Isuru Haththotuwa]

Hi Manoj,

Pull request sent [1] to dev repository.

[1]. https://github.com/wso2-dev/carbon4-kernel/pull/6


On Wed, Mar 12, 2014 at 1:34 PM, Shazni Nazeer  wrote:

> Hi Manoj,
>
> Pull request for the change is sent to wso2-dev/carbon4-kernel repo.
> Please review and commit.
>
> regards,
>
> Shazni Nazeer
>
> Senior Software Engineer
>
> Mob : +94 715 440 607
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
>
> On Wed, Mar 12, 2014 at 11:40 AM, Manoj Kumara  wrote:
>
>> Hi Geeth,
>>
>> Along with committing the code changes on the kernel patches we may need
>> to consider the changes on configuration files, dbscripts etc. Please
>> consider them during your process.
>>
>> Thanks,
>> Manoj
>>
>>
>> *Manoj Kumara*
>> Software Engineer
>> WSO2 Inc. http://wso2.com/
>> *lean.enterprise.middleware*
>> Mobile: +94713448188
>>
>>
>> On Tue, Mar 11, 2014 at 11:46 PM, Geeth Munasinghe wrote:
>>
>>> Hi
>>>
>>> I have compared  kernel 4.3.0 git repo with kernel 4.2.0 branch in svn
>>> and merged the changes to of patches to git repo kernel. I have made pull
>>> request to kernel 4.3.0 and axis2 1.6.1-wso2v11-SNAPSHOT in git repo.
>>>
>>> Please review and commit to kernel and axis2 repos in git hub.
>>>
>>> Svn revision used to compare repos is 197947. Any thing committed after
>>> this commit does not include in this patches.
>>>
>>> When committing new patches, Please make sure to commit them to both svn
>>> and git repo.
>>>
>>> Thanks
>>> Geeth
>>>
>>>
>>>
>>> *G. K. S. Munasinghe *
>>> *Software Engineer,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: ge...@wso2.com
>>> phone:(+94) 777911226
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

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

Re: [Dev] Committing 4.2.0 kernel patches to 4.3.0 in Git repo

[Manoj Kumara]

Thanks IsuruH, Shazni. Will merge them.


*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188


On Thu, Mar 13, 2014 at 6:04 PM, Isuru Haththotuwa  wrote:

> Hi Manoj,
>
> Pull request sent [1] to dev repository.
>
> [1]. https://github.com/wso2-dev/carbon4-kernel/pull/6
>
>
> On Wed, Mar 12, 2014 at 1:34 PM, Shazni Nazeer  wrote:
>
>> Hi Manoj,
>>
>> Pull request for the change is sent to wso2-dev/carbon4-kernel repo.
>> Please review and commit.
>>
>> regards,
>>
>>  Shazni Nazeer
>>
>> Senior Software Engineer
>>
>> Mob : +94 715 440 607
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>>
>> On Wed, Mar 12, 2014 at 11:40 AM, Manoj Kumara  wrote:
>>
>>> Hi Geeth,
>>>
>>> Along with committing the code changes on the kernel patches we may need
>>> to consider the changes on configuration files, dbscripts etc. Please
>>> consider them during your process.
>>>
>>> Thanks,
>>> Manoj
>>>
>>>
>>> *Manoj Kumara*
>>> Software Engineer
>>> WSO2 Inc. http://wso2.com/
>>> *lean.enterprise.middleware*
>>> Mobile: +94713448188
>>>
>>>
>>> On Tue, Mar 11, 2014 at 11:46 PM, Geeth Munasinghe wrote:
>>>
 Hi

 I have compared  kernel 4.3.0 git repo with kernel 4.2.0 branch in svn
 and merged the changes to of patches to git repo kernel. I have made pull
 request to kernel 4.3.0 and axis2 1.6.1-wso2v11-SNAPSHOT in git repo.

 Please review and commit to kernel and axis2 repos in git hub.

 Svn revision used to compare repos is 197947. Any thing committed after
 this commit does not include in this patches.

 When committing new patches, Please make sure to commit them to both
 svn and git repo.

 Thanks
 Geeth



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

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

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

[Dev] Error when creating a secondary user store for AD

[Shavantha Weerasinghe]

Hi All

I get the below exception when creating a secondary user store via UI.
The domain name and the file name are same but the system throws the
below error

Regards,
[2014-03-13 18:22:40,989] ERROR
{org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor} -
Error while building user store manager from file
org.wso2.carbon.user.core.UserStoreException: File name is required to
be the user store domain name(eg.: wso2.com-->wso2_com.xml).
at 
org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor.buildUserStoreConfiguration(UserStoreConfigXMLProcessor.java:97)
at 
org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor.buildUserStoreConfigurationFromFile(UserStoreConfigXMLProcessor.java:69)
at 
org.wso2.carbon.user.core.common.UserStoreDeploymentManager.deploy(UserStoreDeploymentManager.java:43)
at 
org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer.deploy(UserStoreConfigurationDeployer.java:58)
at 
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
at 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at 
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
at 
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
at 
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
at 
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
at 
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2014-03-13 18:22:40,991]  INFO
{org.apache.axis2.deployment.DeploymentEngine} -
org.apache.axis2.deployment.DeploymentException: The deployment of
ADDomain2.xml is not valid.
[2014-03-13 18:24:00,003]  INFO
{org.wso2.carbon.analytics.hive.task.HiveScriptExecutorTask} -
Running script executor task for script esb_stats. [Thu Mar 13
18:24:00 IST 2014]
Hive history 
file=/home/shavantha/projects/BAM/241/m1/wso2bam-2.4.1/tmp/hive/malith-querylogs/hive_job_log_shavantha_201403131748_612331295.txt
OK

Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300

  CN=Administrator,CN=Users,DC=wso2,DC=test
  ldaps://10.100.3.131:636
  ADDomain2
  pass#word1
  CN=Users,DC=WSO2,DC=test
  false
  (objectClass=user)
  cn
  (&(objectClass=person)(uid=?))
  user
  group
  100
  100
  true
  false
  true
  CN=Users,DC=WSO2,DC=test
  (objectcategory=group)
  cn
  member
  (&(objectClass=group)(cn=?))
  PLAIN_TEXT
  ^[\S]{5,30}$
  ^[\S]{3,30}$
  [a-zA-Z0-9._-|//]{3,30}$
  ^[\S]{3,30}$
  [a-zA-Z0-9._-|//]{3,30}$
  true
  uid={0},ou=Users,dc=wso2,dc=org
  true
  WSO2.ORG
  false
  cn
  false
  512
  follow
  true
  AD Domain2
  

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

Re: [Dev] Error when creating a secondary user store for AD

[Darshana Gunawardana]

Hi Shavantha,

There are two "DomainName" properties in the given configuration. Please
*remove* following configuration from the *ADDomain2.xml* file and see
whether it works.
  *AD Domain2*

But if you add created this xml using the UI, there should not be two
*DomainName* properties tags in the same file. Does this happens to every
secondary user store in your setup?

Thanks,


On Thu, Mar 13, 2014 at 6:26 PM, Shavantha Weerasinghe
wrote:

> Hi All
>
> I get the below exception when creating a secondary user store via UI.
> The domain name and the file name are same but the system throws the
> below error
>
> Regards,
> [2014-03-13 18:22:40,989] ERROR
> {org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor} -
> Error while building user store manager from file
> org.wso2.carbon.user.core.UserStoreException: File name is required to
> be the user store domain name(eg.: wso2.com-->wso2_com.xml).
> at
> org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor.buildUserStoreConfiguration(UserStoreConfigXMLProcessor.java:97)
> at
> org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor.buildUserStoreConfigurationFromFile(UserStoreConfigXMLProcessor.java:69)
> at
> org.wso2.carbon.user.core.common.UserStoreDeploymentManager.deploy(UserStoreDeploymentManager.java:43)
> at
> org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer.deploy(UserStoreConfigurationDeployer.java:58)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> [2014-03-13 18:22:40,991]  INFO
> {org.apache.axis2.deployment.DeploymentEngine} -
> org.apache.axis2.deployment.DeploymentException: The deployment of
> ADDomain2.xml is not valid.
> [2014-03-13 18:24:00,003]  INFO
> {org.wso2.carbon.analytics.hive.task.HiveScriptExecutorTask} -
> Running script executor task for script esb_stats. [Thu Mar 13
> 18:24:00 IST 2014]
> Hive history
> file=/home/shavantha/projects/BAM/241/m1/wso2bam-2.4.1/tmp/hive/malith-querylogs/hive_job_log_shavantha_201403131748_612331295.txt
> OK
>
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,


*Darshana Gunawardana *Software Engineer
WSO2 Inc.; http://wso2.com

* E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Commit to kernel patch006

[Lakmali Baminiwatta]

Hi Manoj,

Please apply the attached patch fixing a debug log related to [1].
Patch goes to patch0006/core/org.wso2.carbon.user.core/4.2.0

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

Thanks,
Lakmali

-- 
Lakmali Baminiwatta
 Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
blog : lakmali.com
Index: src/main/java/org/wso2/carbon/user/core/ldap/ReadOnlyLDAPUserStoreManager.java
===
--- src/main/java/org/wso2/carbon/user/core/ldap/ReadOnlyLDAPUserStoreManager.java	(revision 198277)
+++ src/main/java/org/wso2/carbon/user/core/ldap/ReadOnlyLDAPUserStoreManager.java	(working copy)
@@ -2111,11 +2111,15 @@
 
 if(debug) {
 if(list != null) {
+	boolean isUserInRole = false;
 for(String item : list) {
 log.debug("Result: " + item);
+if(item.equalsIgnoreCase(roleName)) {
+	isUserInRole = true;
+}
 }
 log.debug("Is user: " + userName + " in role: " + roleName + " ? " +
-  list.contains(roleName));
+		isUserInRole);
 } else {
 log.debug("No results found !");
 }
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS integration test migration

[Krishantha Samaraweera]

I'm in the middle of AS integration test migration and seems
like JaggeryAppAdmin service is not available in AS yet.

I will migrate all jaggery tests and exclude the tests from testng.xml file.

Thanks,
Krishantha.


On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Hi all,
>
> I've started AS integration test migration to new framework, however
> unavailability of TenantMgtAdminService casing errors while framework
> populate test users to the server.
>
> I will try to go ahead with disabling tenant creation. Any time-frame that
> this feature will be available.
>
> Thanks,
> Krishantha.
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>



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

Re: [Dev] Committing 4.2.0 kernel patches to 4.3.0 in Git repo

[Shameera Rathnayaka]

Hi,

I have merged the pull request sent by Geeth to wso2-dev/master.

Thanks
Shameera.


On Thu, Mar 13, 2014 at 6:21 PM, Manoj Kumara  wrote:

> Thanks IsuruH, Shazni. Will merge them.
>
>
> *Manoj Kumara*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94713448188
>
>
> On Thu, Mar 13, 2014 at 6:04 PM, Isuru Haththotuwa wrote:
>
>> Hi Manoj,
>>
>> Pull request sent [1] to dev repository.
>>
>> [1]. https://github.com/wso2-dev/carbon4-kernel/pull/6
>>
>>
>> On Wed, Mar 12, 2014 at 1:34 PM, Shazni Nazeer  wrote:
>>
>>> Hi Manoj,
>>>
>>> Pull request for the change is sent to wso2-dev/carbon4-kernel repo.
>>> Please review and commit.
>>>
>>> regards,
>>>
>>>  Shazni Nazeer
>>>
>>> Senior Software Engineer
>>>
>>> Mob : +94 715 440 607
>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>> Blog : http://shazninazeer.blogspot.com
>>>
>>>
>>> On Wed, Mar 12, 2014 at 11:40 AM, Manoj Kumara  wrote:
>>>
 Hi Geeth,

 Along with committing the code changes on the kernel patches we may
 need to consider the changes on configuration files, dbscripts etc. Please
 consider them during your process.

 Thanks,
 Manoj


 *Manoj Kumara*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 *lean.enterprise.middleware*
 Mobile: +94713448188


 On Tue, Mar 11, 2014 at 11:46 PM, Geeth Munasinghe wrote:

> Hi
>
> I have compared  kernel 4.3.0 git repo with kernel 4.2.0 branch in svn
> and merged the changes to of patches to git repo kernel. I have made pull
> request to kernel 4.3.0 and axis2 1.6.1-wso2v11-SNAPSHOT in git repo.
>
> Please review and commit to kernel and axis2 repos in git hub.
>
> Svn revision used to compare repos is 197947. Any thing committed
> after this commit does not include in this patches.
>
> When committing new patches, Please make sure to commit them to both
> svn and git repo.
>
> Thanks
> Geeth
>
>
>
> *G. K. S. Munasinghe *
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>


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


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


-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT apache.org
*
*phone:  +9471 922 1454*

*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: GSOC 2014 proposal 5 - WSO2 Deployment Engine (GUI Tool)

[Adam Ocsvari]

Hi,

Thank you for the fast reply.

I have a question about the project:
-Is there any restrictions/already used tools/frameworks for the UI what 
these features should implemented with, or it is part of the task to 
discover the right tool for it? ( Like drag&drop support)

(I assume, there are good jQuery based solutions for this)

Regards,
Adam
On 3/13/2014 10:02 AM, Thilina Piyasundara wrote:

Hi,

This is a basic things we need to do [1]. 75% of the effort will on 
UI/UX things.


1. GSoSProposalsWSO2DeploymentEngine.pdf (187K) 





Thanks and regards,

Thilina Piyasundara
Systems Engineer
​
​ (DevOps)
M: 071-775-0006
​
​
Blog: blog.thilina.org 

WSO2, Inc.
​
​ 
lean . enterprise . middleware




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

[Dev] [GSOC14] Student introduction

[Adam Ocsvari]

Hello Everyone,

My name is Adam and I'm currently studying Computer Science in Budapest.
My major is cloud computing and my thesis topic is related to Apache
Hadoop.
I'm really excited about the GSOC14 and I would be really happy to
participate. The topics of WSO2 really got my attention, I would be more
than happy to work on that.
My main interests are the ones connected with cloud computing or Hadoop:
-Proposal 5: WSO2 Deployment Engine (GUI Tool)
-Proposal 6: AMI baker for WSO2 Private PaaS
-Proposal 9: Tooling support for Hive Queries in Developer Studio


I would like to start a discussion about this topic, make contact with
the mentors and first of all I would like to ask some guidance, how to
prepare for my proposal.

If you are interested, I'm happy to introduce myself better.

I'm looking forward to hear from you.

Best Regards:
Adam Ocsvari



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

Re: [Dev] [Dev-MB] Guaranteed Message Delivery issue in fail over

[Supun Malinga]

On Thu, Mar 13, 2014 at 7:45 AM, Iranga Muthuthanthri wrote:

> Hi Ishara,
>
> Thanks for the suggestion, the problem is what happens at the wire level
> in the message producer when the message broker is down, before the message
> is received by the consumer .
>
> @ Supun:  Yes, This has been observed intermittently
>

Have we created a jira?. Is this fixed in 2.1.1 ?.

thanks,

>
>
>
>
>
> On Thu, Mar 13, 2014 at 4:57 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> Related to the topic,
>> I have observed that sometimes (intermittantly and with a load) jms
>> consumer fails to read the messages from the  response queue even though
>> the messages *are* in the reply queue with correct correlation id.
>> Is this a known issue ?.
>>
>> thanks,
>>
>>
>> On Thu, Mar 13, 2014 at 6:45 AM, Ishara Premadasa wrote:
>>
>>> Hi Iranga,
>>>
>>> What are the failover options you have used in the connection string?
>>> Are there 'retries' and 'connectdelay' options configured. They determine
>>> the number of times a connection to a broker will be retried and the the
>>> length of time to wait between successive connection attempts before moving
>>> on to the next broker in. Have we tried with setting retires to 1 and
>>> connectdelay to 0 ( which are default values) so then the broker will try
>>> to connect immediately to the next one available?
>>>
>>> Thanks!
>>>
>>>
>>> On Thu, Mar 13, 2014 at 3:59 PM, Iranga Muthuthanthri 
>>> wrote:
>>>
 Hi All,

 In a MB message produce consume scenario for fail over, if the message
 producing MB node fails before delivering all the messages it was observed
 that there was a message loss(by observing the Cassandra  queue count).

 What are the workaround possible for this considering the guaranteed
 message delivery model.

 Note: The message consuming and producing MB nodes are the same.


 --
 Thanks & Regards

 Iranga Muthuthanthri
 Technical Lead - QA
 (M) -0777-255773

>>>
>>>
>>>
>>> --
>>> Ishara Premasada
>>> Software Engineer,
>>> WSO2 Inc. http://wso2.com/
>>>
>>>
>>> *Blog   :  http://isharapremadasa.blogspot.com/
>>> Twitter   :
>>> https://twitter.com/ishadil  Mobile   :
>>> +94 714445832 <%2B94%20714445832>*
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> email: sup...@wso2.com 
>> mobile: +94 (0)71 56 91 321
>>
>
>
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> Technical Lead - QA
> (M) -0777-255773
>



-- 
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] AS integration test migration

[Madhuka Udantha]

On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera  wrote:

> I'm in the middle of AS integration test migration and seems
> like JaggeryAppAdmin service is not available in AS yet.
>
@AS team: any reason for this.

(If is it due to that kernel patch thing I can skip oath test in jaggery
per now)

>
> I will migrate all jaggery tests and exclude the tests from testng.xml
> file.
>
+1

>
> Thanks,
> Krishantha.
>
>
> On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi all,
>>
>> I've started AS integration test migration to new framework, however
>> unavailability of TenantMgtAdminService casing errors while framework
>> populate test users to the server.
>>
>> I will try to go ahead with disabling tenant creation. Any time-frame
>> that this feature will be available.
>>
>> Thanks,
>> Krishantha.
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middlewear.
>>
>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com

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

Re: [Dev] AS integration test migration

[Kasun Gajasinghe]

Hi Madhuka,

The main reason being that the Jaggery tests have been failing in Jenkins.
The product-as needs to be able to be able to download the dependent
artifacts via the nexus. So, I have disabled the tests for Jaggery in
Jenkins. But currently, the uploading artifacts to nexus snapshots repo is
failing since the project versions set in the pom.xml are not SNAPSHOT
versions.

@Madhuka, can you update the relevant jaggery branch, and append
'-SNAPSHOT' for the project versions in all the poms? I believe the tests
are failing since jaggery is configured to use 4.2.0 based automation
framework. Build #3 contains the related errors. [1]

[1] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/

Thanks,
KasunG




On Fri, Mar 14, 2014 at 12:44 AM, Madhuka Udantha  wrote:

>
>
>
> On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> I'm in the middle of AS integration test migration and seems
>> like JaggeryAppAdmin service is not available in AS yet.
>>
> @AS team: any reason for this.
>
> (If is it due to that kernel patch thing I can skip oath test in jaggery
> per now)
>
>>
>> I will migrate all jaggery tests and exclude the tests from testng.xml
>> file.
>>
> +1
>
>>
>> Thanks,
>> Krishantha.
>>
>>
>> On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I've started AS integration test migration to new framework, however
>>> unavailability of TenantMgtAdminService casing errors while framework
>>> populate test users to the server.
>>>
>>> I will try to go ahead with disabling tenant creation. Any time-frame
>>> that this feature will be available.
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>> --
>>> Krishantha Samaraweera
>>> Senior Technical Lead - Test Automation
>>> Mobile: +94 77 7759918
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middlewear.
>>>
>>
>>
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middlewear.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Madhuka* Udantha
> Senior Software Engineer
> Development Technologies
> WSO2 Inc. : http://wso2.com
>
> *Mobile*: +94774066336
> *Blog*: http://madhukaudantha.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kasun Gajasinghe*
Software Engineer;
WSO2 Inc.; http://wso2.com


 ,
*email: *
*kasung AT spamfree wso2.com    ** cell: **+94 (77)
678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe



*blog: **http://kasunbg.org* 



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

Re: [Dev] WSO2 API Manager 1.6.0 Publisher / Store customization from source code not applied to product distribution

[Cameron, Antonio]

Thanks Joseph for your reply.  I've try to build the API Manager pack for 
chunk-06, but now I'm getting the following compilation error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.
3.1:compile (default-compile) on project org.wso2.carbon.apimgt.impl: Compilatio
n failure: Compilation failure:
[ERROR] ...\components\apimgt\org.wso2.carbon.apimgt.impl\1
.2.1\src\main\java\org\wso2\carbon\apimgt\impl\APIConsumerImpl.java:[362,59] err
or: cannot find symbol

Do I need to build the kernel patch? If so, where is this located?

Antonio

From: Joseph Fonseka [mailto:jos...@wso2.com]
Sent: Thursday, March 13, 2014 12:49 AM
To: Cameron, Antonio
Cc: dev@wso2.org; Joseph Fonseka
Subject: Re: [Dev] WSO2 API Manager 1.6.0 Publisher / Store customization from 
source code not applied to product distribution

Hi Antonio
In the thuring-chunk06 checkout you can find the API Store and API Publisher in 
the following locations.

components/apimgt/api-publisher-web/1.2.1/
components/apimgt/api-store-web/1.2.1/
Once you do the customizations you can build the API Manager pack with those 
changes by building.

product-releases/chunk-06/
Let me know if you need more clarifications.
Regards
Jo



On Thu, Mar 13, 2014 at 12:45 AM, Cameron, Antonio 
mailto:antonio.came...@bankofamerica.com>> 
wrote:
I would like to understand how to modify the API Manager 1.6.0 Publisher / 
Store jaggery apps from source and have those customizations reflected in the 
product distribution.  I have downloaded the source code from: 
https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk06 repository 
location.  Currently, prebuilt artifacts are downloaded from the wso2 maven 
repository for the Publisher / Store and are used in the final product dist.  
Do I need to create a patch for modifying the jaggery / java source code? If 
so, what is the process for creating a patch for this purpose?

Thanks,

Antonio


This message, and any attachments, is for the intended recipient(s) only, may 
contain information that is privileged, confidential and/or proprietary and 
subject to important terms and conditions available at 
http://www.bankofamerica.com/emaildisclaimer. If you are not the intended 
recipient, please delete this message.

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



--

--
Joseph Fonseka
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 772 512 430
skype: jpfonseka


--
This message, and any attachments, is for the intended recipient(s) only, may 
contain information that is privileged, confidential and/or proprietary and 
subject to important terms and conditions available at 
http://www.bankofamerica.com/emaildisclaimer.   If you are not the intended 
recipient, please delete this message.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] CEP 3.1.0 ALPHA Released!

[Sriskandarajah Suhothayan]

WSO2 CEP team is pleased to announce the 3.1.0-ALPHA release. This release
is now available for download at
http://svn.wso2.org/repos/wso2/people/mohan/CEP_3.1.0_Alpha/wso2cep-3.1.0.zip
The documentation site for this release can be found at
https://docs.wso2.org/display/CEP310/WSO2+Complex+Event+Processor+Documentation

WSO2 Complex Event Processor (CEP) can be used to identify the most
meaningful events within an event cloud, analyzes their impacts, and acts
on them in real time. Built to be extremely high performing it offers
significant time saving and affordable acquisition. WSO2 CEP Manager is
released under the Apache Software License
2.0
.

*Key Features*

   - Default XML, JSON, Text and Map mapping for CEP
   - Support HA by letting one CEP node to be actieve while the redundant
   CEP node will drop all notifications till the active node is processing
   - Enable CEP to receive events from Http Call (HTTP Adaptor)
   - Enable CEP to store realtime outputs to an RDBMs data source.
   - Enhance JMS output notifications with header properties so that they
   can be routed better
   - Siddhi event table cache
   - Need a way to print/ inspect current state of CEP Engine
   - Replacing WS-Eventing with soap input/output adapter
   - Kafka Input/Output Adaptor
   - Enable CEP to write its logs for debugging purposes


*Installing*

The only prerequisite required to try this release out is an installation
of JDK 1.6 (Sun/Oracle JDK 1.6.0_23 or higher recommended)

   - Download the WSO2 CEP 3.1.0-ALPHA release from
   http://svn.wso2.org/repos/wso2/people/mohan/CEP_3.1.0_Alpha/wso2cep-3.1.0.zip
   - Extract the downloaded archive
   - Go to the 'bin' directory and execute wso2server.sh (Unix/Linux) or
   wso2server.bat (Windows)
   - Point your web browser to http://localhost:9443/carbon to get started


*How to Run Samples?*

 Following steps explain in the documentation
https://docs.wso2.org/display/CEP310/Samples to get the samples up and
running:


*Bug Fixes and New Features in this Release*
Bug

   - [CEP-433 ] - Renew subscription
   page need "subscription mode" filed
   - [CEP-576 ] - Not forwarding
   thrift events according to tenant ID
   - [CEP-608 ] - Navigates to "Page
   not Found" when clicking on "
   http://docs.wso2.org/display/CEP300/Complex+Event+Processor+Documentation
   "
   - [CEP-624 ] - String attribute
   not working as expected in Rest-API
   - [CEP-629 ] -
   validateStreamDefinition() not working in Datapublisher - only checking the
   stream name not the stream id
   - [CEP-655 ] - Event builder does
   not order properties as defined in configuration when using map mapping
   - [CEP-665 ] - HTTP 500 error
   observed when login as tenant
   - [CEP-667 ] - error message needs
   to be modified when editing event stream
   - [CEP-669 ] - [intermitant] the
   execution plan throws a dead page and exception if we rename the stream and
   version
   - [CEP-670 ] - when creating an
   event formatter for a stream even if we set the advanced configurations
   upon saving null is shown on UI
   - [CEP-671 ] - Error thrown when
   adding event builder / formatter with xml input mapping type for http
   input/ output adapters
   - [CEP-672 ] - an error is thrown
   when we attempt to enable statistics for a stream
   - [CEP-673 ] - null point
   exception is thrown when attempting to send email and jdbc output events
   for an http input event
   - [CEP-674 ] -
   java.lang.NullPointerException: Tenant domain has not been set in
   CarbonContext Exceptions are thrown when attempting to test integration of
   CEP310 with ESB using BAM mediator
   - [CEP-675 ] - a null pointer
   exception is thrown when starting a CEP node with ./wso2server.sh
   -Ddisable.cassandra.server.startup=fals and clustering is enabled
   - [CEP-676 ] - Can't add custom
   output mappings in event formatter
   - [CEP-681 ] - when attempting to
   send a message from CEP via http input to MB via ws-event output adapter
   CEP thrown a Error while dispatching events java.lang.NullPointerException
   - [CEP-682 ] - system does not
   seem to allow an event table to be used as an export stream
   - [CEP-687 ] - "Caused by:
   java.lang.ClassNotFoundExceptio

Re: [Dev] DSS:The input stream for an incoming message is null

[Isuru Perera]

Hi,


On Fri, Mar 14, 2014 at 7:04 AM, stevegyc  wrote:

>  Hi Isuru：
>
> You are right.
> If I do not clicking tryit from the overview page, the error message
> will not occur.
>
Great.

Let's try to get this fixed in future releases. I think the Application
Server team can look into this issue.

>
> Thank you!
>
> --
> stevegyc
>
>  *From:* Isuru Perera 
> *Date:* 2014-03-12 11:17
> *To:* stevegyc 
> *CC:* dev ; Iranga Muthuthanthri 
> *Subject:* Re: [Dev] DSS:The input stream for an incoming message is null
>Yes. This is a known issue due to session timeout.
>
> stevegyc,
>
> I guess you are clicking tryit from Management Console Service overview
> page, which has a chart showing statistics.
>
> When you go to try it page, the session expires on the admin console.
>
> That's why you are seeing the error on the console.
>
> I hope this is clear. There are many issues reported for this also [1]
>
> [1]
> https://wso2.org/jira/browse/WSAS-1549?jql=text%20~%20%22ERROR%20org.wso2.carbon.statistics.ui.StatisticsAdminClient%20Cannot%20get%20service%20stats%22
>
>
> On Wed, Mar 12, 2014 at 7:29 AM, Iranga Muthuthanthri wrote:
>
>> Hi,
>>
>> The  possible reason for this excption could be a session time out, which
>> is not specific to DSS.  Please refer to (1)
>>
>> Regards,
>> Iranga
>>
>> (1) https://wso2.org/jira/WSAS-1214
>>  On Mar 12, 2014 6:54 AM, "stevegyc"  wrote:
>>
>>>   Hi ：
>>>
>>>
>>> When I began to do a query operation of DSS service by tryit tool, it will 
>>> output the following error message on the Mgt Console.
>>>
>>> TID: [0] [DSS] [2014-03-10 12
>>> :57:39,799] ERROR {org.wso2.carbon.statistics.ui.StatisticsAdminClient} -  
>>> Cannot get service stats for service dss_test2. Backend server may be 
>>> unavailable. {org.wso2.carbon.statistics.ui.StatisticsAdminClient}
>>>
>>> org.apache.axis2.AxisFault: The input stream for an incoming message is 
>>> null.
>>>
>>> at 
>>> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:93)
>>>
>>>
>>> But If I continue to do the query operation, it will output the correct 
>>> result.
>>>
>>> I am using DSS3.1.1 and jdk1.6.0_39(32bit).
>>>
>>> The same dbs file will work succesfully in another machine.
>>>
>>> Anyone know why these error message outputted?
>>>
>>>
>>> --
>>> stevegyc
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>



-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

Re: [Dev] Error when creating a secondary user store for AD

[Shavantha Weerasinghe]

Hi Dharshana

Thanks for the reply, the DomainName on top was accidentally added by
me to have duplicate properties. However, If I give the user store
name with a space character as "AD Domain" upon this configuratio been
saved it seems to throw the error as below because the xml file is
saved as AD%20Domain.xml. Note the '%20' in place of the space
character. I think when this and the name within the "DomaiName" does
not match this error comes up



[2014-03-14 09:16:47,833]  INFO
{org.wso2.carbon.stratos.landing.page.deployer.LandingPageWebappDeployer}
-  Deployed product landing page webapp:
StandardEngine[Catalina].StandardHost[localhost].StandardContext[/home]
[2014-03-14 09:16:47,838]  INFO
{org.apache.axis2.transport.tcp.TCPTransportSender} -  TCP Sender
started
[2014-03-14 09:16:47,865] ERROR
{org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor} -
Error while building user store manager from file
org.wso2.carbon.user.core.UserStoreException: File name is required to
be the user store domain name(eg.: wso2.com-->wso2_com.xml).
at 
org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor.buildUserStoreConfiguration(UserStoreConfigXMLProcessor.java:97)
at 
org.wso2.carbon.user.core.config.UserStoreConfigXMLProcessor.buildUserStoreConfigurationFromFile(UserStoreConfigXMLProcessor.java:69)
at 
org.wso2.carbon.user.core.common.UserStoreDeploymentManager.deploy(UserStoreDeploymentManager.java:43)
at 
org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer.deploy(UserStoreConfigurationDeployer.java:58)
at 
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
at 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at 
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:135)
at 
org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:464)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
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 

[Dev] Can not run siddhi quick start samples

[Waruna Perera]

Hi,

I tried to run samples in 2.1.0 and didnt compile. Error is with the sample
classes code has not been updated with latest siddhi code.

BR,

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

Re: [Dev] AS integration test migration

[Madhuka Udantha]

On Fri, Mar 14, 2014 at 1:01 AM, Kasun Gajasinghe  wrote:

> Hi Madhuka,
>
> The main reason being that the Jaggery tests have been failing in Jenkins.
>
Jaggery only had one issue[2] It also have been fixed it build fine[3]
[2] [jaggery][kernel]Missing patch @ dev
[3]
http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/lastSuccessfulBuild/

The product-as needs to be able to be able to download the dependent
> artifacts via the nexus. So, I have disabled the tests for Jaggery in
> Jenkins. But currently, the uploading artifacts to nexus snapshots repo is
> failing since the project versions set in the pom.xml are not SNAPSHOT
> versions.
>
> @Madhuka, can you update the relevant jaggery branch, and append
> '-SNAPSHOT' for the project versions in all the poms? I believe the tests
> are failing since jaggery is configured to use 4.2.0 based automation
> framework. Build #3 contains the related errors. [1]
>
Jaggery was using old  automation framework (ATF) since there was some miss
match with jaggery and ATF. If new ATF is ready we can make that shift I
think

Thanks

>
> [1] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/
>
> Thanks,
>  KasunG
>
>
>
>
> On Fri, Mar 14, 2014 at 12:44 AM, Madhuka Udantha wrote:
>
>>
>>
>>
>> On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> I'm in the middle of AS integration test migration and seems
>>> like JaggeryAppAdmin service is not available in AS yet.
>>>
>> @AS team: any reason for this.
>>
>> (If is it due to that kernel patch thing I can skip oath test in jaggery
>> per now)
>>
>>>
>>> I will migrate all jaggery tests and exclude the tests from testng.xml
>>> file.
>>>
>> +1
>>
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>>
>>> On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
 Hi all,

 I've started AS integration test migration to new framework, however
 unavailability of TenantMgtAdminService casing errors while framework
 populate test users to the server.

 I will try to go ahead with disabling tenant creation. Any time-frame
 that this feature will be available.

 Thanks,
 Krishantha.

 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.

>>>
>>>
>>>
>>> --
>>> Krishantha Samaraweera
>>> Senior Technical Lead - Test Automation
>>> Mobile: +94 77 7759918
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middlewear.
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Madhuka* Udantha
>> Senior Software Engineer
>> Development Technologies
>> WSO2 Inc. : http://wso2.com
>>
>> *Mobile*: +94774066336
>> *Blog*: http://madhukaudantha.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>


-- 
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com

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

Re: [Dev] Regarding W

[Malintha Adikari]

Adding d...@wso2.com

Hi Ruskshan,

I have reviewed you proposal. According to your proposal you are going to
use JBehave as your test case generation engine. We have discussed the
limitation of JBhave in previous mail. I think you have to reconsider you
decision using JBehave as your test generation engine ( research about
extending JBehave rather then use it directly). Also try to describe your
proposal.  Please describe more about the proposed architecture and that
would help us to understand your proposal clearly.  Then we can finalize it
before you start implementing. Also try to clarify any point that is not
clear 100% to you about the project idea.

Note:  If you have any changes to the proposal , make them asap. We have
one more to the deadline.


Regards,
Malintha Adikari


On Tue, Mar 11, 2014 at 3:46 PM, Rukshan Chathuranga
wrote:

> Hi malintha,
>
> Thank you for the replay. I have implemt some very simple testig with BDD
> and JBehave. After that write a blog about it on
> http://rukspot.com/?q=bddJBehaveTesting
>
> Also I will work on testing with WSO2 Application server with your this
> example.
>
> thanks and regards.
>
>
>
> On Tue, Mar 11, 2014 at 1:15 PM, Malintha Adikari wrote:
>
>> Hi Rukshan,
>>
>> Nice to hear your progress on the project. Before prepare the proposal
>> for the project you have to investigate more it with JBehave. When you use
>> JBehave for Behavior Driven Development testing, you have to provide the
>> mapping class for each and every story. As an  example
>>
>> consider this story
>>
>> *Scenario: 2 squared*
>>
>> Given a variable x with value 2
>> When I multiply x by 2
>> Then x should equal 4
>>
>> +++
>>
>> So the *mapping class* should look like
>>
>>
>> public class ExampleSteps extends Steps {
>> int x;
>>
>> @Given("a variable x with value $value")
>> public void givenXValue(@Named("value") int value) {
>> x = value;
>> }
>>
>> @When("I multiply x by $value")
>> public void whenImultiplyXBy(@Named("value") int value) {
>> x = x * value;
>> }
>>
>> @Then("x should equal $value")
>> public void thenXshouldBe(@Named("value") int value) {
>> if (value != x)
>> throw new RuntimeException("x is " + x + ", but should be " +
>> value);
>> }
>> }
>>
>>
>> +
>>
>> Additionally you have to provide a configuration class (one time) class
>> also.
>>
>> What we are worrying is providing mapping class per story. With our case
>> it would make some limitations. (We have hundreds of stories and hundreds
>> would be added in the future).
>>
>> What we want is automatically generate above mapping class (in runtime).
>> I will explain more about this point.
>>
>> Consider following example
>>
>> Test case in natural language
>>
>> 1. *Select* wso2-application *server*
>> 2. *Deploy* the *server*
>> 3. *Select* TestTenant as *tenant*
>> 4. *Deploy*  *tenant*
>> 5. *Login*
>> 6. *Upload* *artifact* abc.aar
>> 7. *Deploy* *artifact* abc.aar
>>
>> User would be able to give above kind of scenario.You can find several
>> keywords there (Select, server, Deploy, server, select,login). This is
>> about the user aspect.
>>
>> Now lets consider about our backend aspect. We have backend API  methods
>> inline with above textual commands. If you look at the following backend
>> class
>>
>> ++
>>
>> package org.wso2.carbon.authenticator.stub;
>>
>> public class *AuthenticationAdminStub* extends
>> org.apache.axis2.client.Stub implements
>> org.wso2.carbon.authenticator.stub.AuthenticationAdmin {
>> protected org.apache.axis2.description.AxisOperation[] _operations;
>> private java.util.HashMap faultExceptionNameMap;
>> private java.util.HashMap faultExceptionClassNameMap;
>> private java.util.HashMap faultMessageMap;
>> private static int counter;
>> private javax.xml.namespace.QName[] opNameArray;
>>
>> private static synchronized java.lang.String getUniqueSuffix() { /*
>> compiled code */ }
>>
>> private void populateAxisService() throws org.apache.axis2.AxisFault
>> { /* compiled code */ }
>>
>> private void populateFaults() { /* compiled code */ }
>>
>> public
>> AuthenticationAdminStub(org.apache.axis2.context.ConfigurationContext
>> configurationContext, java.lang.String targetEndpoint) throws
>> org.apache.axis2.AxisFault { /* compiled code */ }
>>
>>  }
>>
>> public boolean *login*(java.lang.String username42, java.lang.String
>> password43, java.lang.String remoteAddress44) throws
>> java.rmi.RemoteException,
>> org.wso2.carbon.authenticator.stub.LoginAuthenticationExceptionException {
>> /* compiled code */ }
>>
>> public void logout() throws java.rmi.RemoteException,
>> org.wso2.carbon.authenticator.stub.LogoutAuthenticationExceptionException {
>> 

Re: [Dev] WSO2 BAM 2.4.1 Alpha Released!

[Thayalan]

[Re-sending the mail to dev list]

Hi All,

Please find below the BAM test plan for the upcoming v2.4.1 release. Please
let us know if we miss any important areas that we suppose to test for this
release.

1. New Features for v2.4.1

   - Message Console
   - Dep Sync
   - Hive Metastore support for MySQL/Oracle/MSSQL/DB2
   - Server Profile - We will only test server start-up  &
   availability/functionality of related modules specific to the profile.
   - Cassandra upgrade - Check existing functionality working with v1.2.10.
   However as per the discussion with Anjana we will not be testing external
   Cassandra version 1.1.3
   - Remove Toolbox deployment status from UI
   - Toolbox artifacts deployed, should not be editable
   - Incremental Data Processing in Distributed mode

2. Deployment Pattern

   - Partially distributed set-up - Smoke Testing only
   - Fully Distributed set-up - Long running, Load and functional testing

3. Integration scenarios

   - External Task Server 1.1.0 with cluster set-up
   - API Manager - 1.6.0 & 2.0.0
   - ESB - 4.8.1
   - Application Server - 5.2.1

4. Customer Scenarios / Support Issues

   - Selected scenarios will be tested

5. CEP Features in BAM

   - Smoke Test

However due to time and resource constraints we will discuss with Anjana &
Team and will refine the plan when required.

Also QA Test plan  can be accessible from [1].

1. QA Test 
Plan


On Thu, Mar 13, 2014 at 1:01 PM, Sinthuja Ragendran wrote:

> Hi,
>
> IMHO we need include basic testing of all default toolboxes HL7, message
> tracing, etc and Activity Dashboard as there are some changes in the
> data-bridge stream definition and index definition store.
>
> Thanks,
> Sinthuja.
>
>
> On Thu, Mar 13, 2014 at 12:54 PM, Thayalan  wrote:
>
>> Hi All,
>>
>> Please find below the BAM test plan for the upcoming v2.4.1 release.
>> Please let us know if we miss any important areas that we suppose to test
>> for this release.
>>
>> 1. New Features for v2.4.1
>>
>>- Message Console
>>- Dep Sync
>>- Hive Metastore support for MySQL/Oracle/MSSQL/DB2
>>- Server Profile - We will only test server start-up  &
>>availability/functionality of related modules specific to the profile.
>>- Cassandra upgrade - Check existing functionality working with
>>v1.2.10. However as per the discussion with Anjana we will not be testing
>>external Cassandra version 1.1.3
>>- Remove Toolbox deployment status from UI
>>- Toolbox artifacts deployed, should not be editable
>>- Incremental Data Processing in Distributed mode
>>
>> 2. Deployment Pattern
>>
>>- Partially distributed set-up - Smoke Testing only
>>- Fully Distributed set-up - Long running, Load and functional testing
>>
>> 3. Integration scenarios
>>
>>- External Task Server 1.1.0 with cluster set-up
>>- API Manager - 1.6.0 & 2.0.0
>>- ESB - 4.8.1
>>- Application Server - 5.2.1
>>
>> 4. Customer Scenarios / Support Issues
>>
>>- Selected scenarios will be tested
>>
>> 5. CEP Features in BAM
>>
>>- Smoke Test
>>
>> However due to time and resource constraints we will discuss with Anjana
>> & Team and will refine the plan when required.
>>
>> Also QA Test plan  can be accessible from [1].
>>
>> 1. QA Test 
>> Plan
>>
>> Thanks,
>> Thayalan
>>
>> On Thu, Mar 13, 2014 at 10:19 AM, Maninda Edirisooriya 
>> wrote:
>>
>>> Yeah, The same issue was reported in [1] too.
>>>
>>> [1]
>>>
>>>
>>> *Maninda Edirisooriya*
>>> Software Engineer
>>>
>>> *WSO2, Inc. *lean.enterprise.middleware.
>>>
>>> *Blog* : http://maninda.blogspot.com/
>>> *Phone* : +94 777603226
>>>
>>>
>>> On Thu, Mar 13, 2014 at 12:06 AM, Pandula Kariyawasam 
>>> wrote:
>>>
 Hi Ajith,

 Thanks a lot for the quick support. As you mentioned, the svn version
 in node1 was 1.7. We downgraded it to 1.6, and now it works fine with
 svnkit-bundle-1.0.0.jar.
 Thanks again. We'll resolve the issue with mentioning the reason, and
 it's fix.

 Thanks,
 Pandula


 On Wed, Mar 12, 2014 at 11:09 PM, Ajith Vitharana wrote:

> Hi Pandula,
>
> Please check that you have properly copied the SVN library jars.
>
> Thanks.
> Ajith
>
>
> On Wed, Mar 12, 2014 at 10:58 PM, Pandula Kariyawasam <
> pand...@wso2.com> wrote:
>
>> Hi All,
>>
>> We have configured the fully distributed cluster setup with Alpha
>> pack. During the server startup, we have noticed OutOfMemoryError on Java
>> heap, which happened only on node1. [1]
>> Please look in to this.
>>
>> We will keep updating this thread with the progress & problems we
>> will face during this QA cycle.
>>
>> [1] https://wso2.org/jira/br

Re: [Dev] Enhanced GitHub pull request plugin with WSO2 Jenkins

[Afkham Azeez]

Please send pull requests to the 2 original plugins.
https://github.com/janinko/ghprb/issues/118


On Thu, Mar 13, 2014 at 2:14 PM, Ayash  wrote:

> Hi,
>
> To install the plug-in to jenkins,
>
> 1. Install the github-plugin
> 2. Install the plug-ins attached herewith.
> 3. Restart Jenkins
>
>  For now, I'll commit the code in the wso2 github repo and will send the
> pull request to original jenkins plug-ins too and will check if they commit
> our change to the original plug-ins. I'll update this thread with git repo
> of the code.
>
> Thanks,
> -Ayash
>
>
>
> On Thu, Mar 13, 2014 at 1:09 PM, Chan  wrote:
>
>> +1 to get the continuos delivery model blogged out. Also this would help
>> many other organizations and teams if we setup a proper guideline on our
>> continuos delivery model.
>>
>> Cheers~
>>
>>
>> On Thu, Mar 13, 2014 at 12:07 PM, Kasun Gajasinghe wrote:
>>
>>> Hi Azeez,
>>>
>>> We have not enabled the said plugin in our Jenkins setup yet.
>>> @Ayashkantha, please send the necessary artifacts (the .spi is enough?) to
>>> install this plugin.
>>>
>>> I think we might need to have another jenkins node (as a slave node) for
>>> the Pull Request builder plugin ( preferably on a new VM depending on the
>>> load).  We noticed that when we installed the original jenkins plugin, it
>>> has messed up the entire jenkins builds, and we had to re-configure a new
>>> jenkins instance.
>>>
>>> Thanks,
>>> KasunG
>>>
>>>
>>>
>>> On Thu, Mar 13, 2014 at 11:34 AM, Afkham Azeez  wrote:
>>>
 Ping! Need an update ASAP.


 On Wed, Mar 12, 2014 at 10:59 AM, Afkham Azeez  wrote:

> Have we enabled this plugin on our Jenkins setup?
>
> Where do we maintain this code? Perhaps we have the fork within the
> WSO2 repo?
>
> Did we send the enhancements as pull requests to the relevant original
> repos? If not, please do so with the proper comments explaining what the
> enhancement does.
>
> Write a blog post about this, Tweet it etc. and make some noise about
> this and our vision towards continuous delivery.
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: 
> **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * *
 *email: **az...@wso2.com* 
 * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
 *http://blog.afkham.org* 
 *twitter: 
 **http://twitter.com/afkham_azeez*
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 *

 *Lean . Enterprise . Middleware*

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


>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>>
>>> *twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Chan (Dulitha Wijewantha)
>> Software Engineer - Mobile Development
>>  WSO2Mobile
>> Lean.Enterprise.Mobileware
>>  * ~Email   duli...@wso2.com *
>> *  ~Mobile +94712112165 <%2B94712112165>*
>> *  ~Website   dulitha.me *
>> *  ~Twitter @dulitharw *
>>   *~SO @chan *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ayashkantha Ramasinghe
> Software Engineer WSO2, Inc.
> email: ayashkan...@wso2.com ;
> TP: +94 77 7 487 669
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Jmeter scripts for IS load testing.

[Ushani Balasooriya]

Hi All,

Pls find the JMeter script to load test tenants (tenants creation, roles
per tenant and users per role) at [1].

[1]https://svn.wso2.org/repos/wso2/trunk/commons/qa/qa-artifacts/is/IS470/UM/Tenants/


Regards,
Ushani


On Mon, Mar 10, 2014 at 3:42 PM, Evanthika Amarasiri wrote:

> Please find the JMeter script to verify OAuth for grant type *Authorization
> Code *at [1]. The script is written for the Playground app.
>
> [1] -
> https://svn.wso2.org/repos/wso2/trunk/commons/qa/qa-artifacts/is/IS470/OAuth/authorization_code
>
> Regards,
> Evanthika
>
> On Tue, Mar 4, 2014 at 4:27 PM, Ushani Balasooriya wrote:
>
>> Pls find the jmeter script [1] for SSO-SAML2 done for the travelocity/
>> avis.com sample in [2]. This can be used for load testing, suport issues
>> and marketing materials.
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/trunk/commons/qa/qa-artifacts/is/IS470/SSO/SAML2/
>> [2] https://docs.wso2.org/display/IS460/Configuring+SAML2+SSO
>>
>> Thanks and Regards,
>> Ushani
>>
>>
>> On Sat, Mar 1, 2014 at 9:56 PM, Evanthika Amarasiri 
>> wrote:
>>
>>> The script to load test OAuth (for IS 4.7.0) is available at [1]. The
>>> current script support 10 users.
>>>
>>> [1] -
>>> https://svn.wso2.org/repos/wso2/trunk/commons/qa/qa-artifacts/is/IS470/OAuth/
>>>
>>> Regards,
>>> Evanthika
>>>
>>> On Thu, Feb 27, 2014 at 1:44 PM, Pavithra Madurangi 
>>> wrote:
>>> > As part of preparing scripts for IS load testing, the Jmeter script
>>> created
>>> > for STS is available at [1].
>>> >
>>> > This script can be used to check below functionality as well as for
>>> load
>>> > testing.
>>> > - Issue token
>>> > - Validate token
>>> > - Renew token
>>> >
>>> > In addition to that, while creating scripts observed following issues.
>>> >
>>> > There's an error when trying to renew bearer type SAML 2.0 token [2]
>>> and was
>>> > not able to revoke tokens [3].
>>> >
>>> > [1]
>>> >
>>> https://svn.wso2.org/repos/wso2/trunk/commons/qa/qa-artifacts/is/IS470/STS/
>>> > [2] https://wso2.org/jira/browse/IDENTITY-2047
>>> > [3] https://wso2.org/jira/browse/IDENTITY-2048
>>> >
>>> > Regards,
>>> > Pavithra
>>> >
>>> > --
>>> > Pavithra Madurangi
>>> > Senior Software Engineer - QA.
>>> > WSO2 Inc.: http://wso2.com/
>>> > Mobile: +94777207357
>>> >
>>> > ___
>>> > Dev mailing list
>>> > Dev@wso2.org
>>> > http://wso2.org/cgi-bin/mailman/listinfo/dev
>>> >
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>>
>> --
>> *Ushani Balasooriya*
>> Software Engineer - QA;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; +94772636796
>>
>>
>


-- 
*Ushani Balasooriya*
Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; +94772636796
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS integration test migration

[Kasun Gajasinghe]

On Friday, March 14, 2014, Madhuka Udantha  wrote:

>
>
>
> On Fri, Mar 14, 2014 at 1:01 AM, Kasun Gajasinghe 
> 
> > wrote:
>
>> Hi Madhuka,
>>
>> The main reason being that the Jaggery tests have been failing in Jenkins.
>>
> Jaggery only had one issue[2] It also have been fixed it build fine[3]
> [2] [jaggery][kernel]Missing patch @ dev
> [3]
> http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/lastSuccessfulBuild/
>
>
Actually, this last successful build has test failures. Please note that
that build is marked 'unstable' with the yellow color. You can find the
test failure details by clicking on the Console Output link.



> The product-as needs to be able to be able to download the dependent
>> artifacts via the nexus. So, I have disabled the tests for Jaggery in
>> Jenkins. But currently, the uploading artifacts to nexus snapshots repo is
>> failing since the project versions set in the pom.xml are not SNAPSHOT
>> versions.
>>
>> @Madhuka, can you update the relevant jaggery branch, and append
>> '-SNAPSHOT' for the project versions in all the poms? I believe the tests
>> are failing since jaggery is configured to use 4.2.0 based automation
>> framework. Build #3 contains the related errors. [1]
>>
> Jaggery was using old  automation framework (ATF) since there was some
> miss match with jaggery and ATF. If new ATF is ready we can make that shift
> I think
>
>
Yes, in the meanwhile can update the versions as mentioned above please?


> Thanks
>
>
> [1] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/
>
> Thanks,
>  KasunG
>
>
>
>
> On Fri, Mar 14, 2014 at 12:44 AM, Madhuka Udantha wrote:
>
>
>
>
> On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
> I'm in the middle of AS integration test migration and seems
> like JaggeryAppAdmin service is not available in AS yet.
>
> @AS team: any reason for this.
>
> (If is it due to that kernel patch thing I can skip oath test in jaggery
> per now)
>
>
> I will migrate all jaggery tests and exclude the tests from testng.xml
> file.
>
> +1
>
>
> Thanks,
> Krishantha.
>
>
> On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
> Hi all,
>
> I've started AS integration test migration to new framework, however
> unavailability of TenantMgtAdminService casing errors while framework
> populate test users to the server.
>
> I will try to go ahead with disabling tenant creation. Any time-frame that
> this feature will be available.
>
> Thanks,
> Krishantha.
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>
>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
> --
>
>
>
>
> --
> *Madhuka* Udantha
> Senior Software Engineer
> Development Technologies
> WSO2 Inc. : http://wso2.com
>
> *Mobile*: +94774066336
> *Blog*: http://madhukaudantha.blogspot.com/
>


-- 
*Kasun Gajasinghe*
Software Engineer;
WSO2 Inc.; http://wso2.com


 ,
*email: *
*kasung AT spamfree wso2.com   ** cell: **+94 (77)
678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe



*blog: **http://kasunbg.org* 



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

Re: [Dev] AS integration test migration

[Krishantha Samaraweera]

Hi Madhuka,

On Fri, Mar 14, 2014 at 10:13 AM, Madhuka Udantha  wrote:

>
>
>
> On Fri, Mar 14, 2014 at 1:01 AM, Kasun Gajasinghe  wrote:
>
>> Hi Madhuka,
>>
>> The main reason being that the Jaggery tests have been failing in Jenkins.
>>
> Jaggery only had one issue[2] It also have been fixed it build fine[3]
> [2] [jaggery][kernel]Missing patch @ dev
> [3]
> http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/lastSuccessfulBuild/
>
> The product-as needs to be able to be able to download the dependent
>> artifacts via the nexus. So, I have disabled the tests for Jaggery in
>> Jenkins. But currently, the uploading artifacts to nexus snapshots repo is
>> failing since the project versions set in the pom.xml are not SNAPSHOT
>> versions.
>>
>> @Madhuka, can you update the relevant jaggery branch, and append
>> '-SNAPSHOT' for the project versions in all the poms? I believe the tests
>> are failing since jaggery is configured to use 4.2.0 based automation
>> framework. Build #3 contains the related errors. [1]
>>
> Jaggery was using old  automation framework (ATF) since there was some
> miss match with jaggery and ATF. If new ATF is ready we can make that shift
> I think
>

The test framework is ready to be used and available in git repo. I think
you are referring to mismatch with jaggery.sh script. If it is the case,
then you need to write new sever start-up extension and register that class
in our automation.xml

Thanks,
Krishantha.

>
> Thanks
>
>>
>> [1] http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/
>>
>> Thanks,
>>  KasunG
>>
>>
>>
>>
>> On Fri, Mar 14, 2014 at 12:44 AM, Madhuka Udantha wrote:
>>
>>>
>>>
>>>
>>> On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
 I'm in the middle of AS integration test migration and seems
 like JaggeryAppAdmin service is not available in AS yet.

>>> @AS team: any reason for this.
>>>
>>> (If is it due to that kernel patch thing I can skip oath test in jaggery
>>> per now)
>>>

 I will migrate all jaggery tests and exclude the tests from testng.xml
 file.

>>> +1
>>>

 Thanks,
 Krishantha.


 On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera <
 krishan...@wso2.com> wrote:

> Hi all,
>
> I've started AS integration test migration to new framework, however
> unavailability of TenantMgtAdminService casing errors while framework
> populate test users to the server.
>
> I will try to go ahead with disabling tenant creation. Any time-frame
> that this feature will be available.
>
> Thanks,
> Krishantha.
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>



 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.

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


>>>
>>>
>>> --
>>> *Madhuka* Udantha
>>> Senior Software Engineer
>>> Development Technologies
>>> WSO2 Inc. : http://wso2.com
>>>
>>> *Mobile*: +94774066336
>>> *Blog*: http://madhukaudantha.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: **http://kasunbg.org* 
>>
>>
>>
>> *twitter: **http://twitter.com/kasunbg* 
>>
>>
>>
>>
>
>
> --
> *Madhuka* Udantha
> Senior Software Engineer
> Development Technologies
> WSO2 Inc. : http://wso2.com
>
> *Mobile*: +94774066336
> *Blog*: http://madhukaudantha.blogspot.com/
>



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

Re: [Dev] AS integration test migration

[Madhuka Udantha]

On Fri, Mar 14, 2014 at 11:30 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Hi Madhuka,
>
> On Fri, Mar 14, 2014 at 10:13 AM, Madhuka Udantha wrote:
>
>>
>>
>>
>> On Fri, Mar 14, 2014 at 1:01 AM, Kasun Gajasinghe wrote:
>>
>>> Hi Madhuka,
>>>
>>> The main reason being that the Jaggery tests have been failing in
>>> Jenkins.
>>>
>> Jaggery only had one issue[2] It also have been fixed it build fine[3]
>> [2] [jaggery][kernel]Missing patch @ dev
>> [3]
>> http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/lastSuccessfulBuild/
>>
>> The product-as needs to be able to be able to download the dependent
>>> artifacts via the nexus. So, I have disabled the tests for Jaggery in
>>> Jenkins. But currently, the uploading artifacts to nexus snapshots repo is
>>> failing since the project versions set in the pom.xml are not SNAPSHOT
>>> versions.
>>>
>>> @Madhuka, can you update the relevant jaggery branch, and append
>>> '-SNAPSHOT' for the project versions in all the poms? I believe the tests
>>> are failing since jaggery is configured to use 4.2.0 based automation
>>> framework. Build #3 contains the related errors. [1]
>>>
>> Jaggery was using old  automation framework (ATF) since there was some
>> miss match with jaggery and ATF. If new ATF is ready we can make that shift
>> I think
>>
>
> The test framework is ready to be used and available in git repo. I think
> you are referring to mismatch with jaggery.sh script.
>
yes

>  If it is the case, then you need to write new sever start-up extension
> and register that class in our automation.xml
>
will do

>
> Thanks,
> Krishantha.
>
>>
>> Thanks
>>
>>>
>>> [1]
>>> http://54.84.136.218:8080/jenkins/job/jaggery-branch-for-kernel4.3.0/
>>>
>>> Thanks,
>>>  KasunG
>>>
>>>
>>>
>>>
>>> On Fri, Mar 14, 2014 at 12:44 AM, Madhuka Udantha wrote:
>>>



 On Thu, Mar 13, 2014 at 6:57 PM, Krishantha Samaraweera <
 krishan...@wso2.com> wrote:

> I'm in the middle of AS integration test migration and seems
> like JaggeryAppAdmin service is not available in AS yet.
>
 @AS team: any reason for this.

 (If is it due to that kernel patch thing I can skip oath test in
 jaggery per now)

>
> I will migrate all jaggery tests and exclude the tests from testng.xml
> file.
>
 +1

>
> Thanks,
> Krishantha.
>
>
> On Thu, Mar 13, 2014 at 10:50 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi all,
>>
>> I've started AS integration test migration to new framework, however
>> unavailability of TenantMgtAdminService casing errors while framework
>> populate test users to the server.
>>
>> I will try to go ahead with disabling tenant creation. Any time-frame
>> that this feature will be available.
>>
>> Thanks,
>> Krishantha.
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middlewear.
>>
>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Madhuka* Udantha
 Senior Software Engineer
 Development Technologies
 WSO2 Inc. : http://wso2.com

 *Mobile*: +94774066336
 *Blog*: http://madhukaudantha.blogspot.com/

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


>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>>
>>> *twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Madhuka* Udantha
>> Senior Software Engineer
>> Development Technologies
>> WSO2 Inc. : http://wso2.com
>>
>> *Mobile*: +94774066336
>> *Blog*: http://madhukaudantha.blogspot.com/
>>
>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>



-- 
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com

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

Re: [Dev] Enhanced GitHub pull request plugin with WSO2 Jenkins

[Ayash]

Hey,

Which one is the correct repo?
https://github.com/janinko/ghprb
or
https://github.com/jenkinsci/ghprb-plugin

Thanks,


On Fri, Mar 14, 2014 at 11:01 AM, Afkham Azeez  wrote:

> Please send pull requests to the 2 original plugins.
> https://github.com/janinko/ghprb/issues/118
>
>
> On Thu, Mar 13, 2014 at 2:14 PM, Ayash  wrote:
>
>> Hi,
>>
>> To install the plug-in to jenkins,
>>
>> 1. Install the github-plugin
>> 2. Install the plug-ins attached herewith.
>> 3. Restart Jenkins
>>
>>  For now, I'll commit the code in the wso2 github repo and will send the
>> pull request to original jenkins plug-ins too and will check if they commit
>> our change to the original plug-ins. I'll update this thread with git repo
>> of the code.
>>
>> Thanks,
>> -Ayash
>>
>>
>>
>> On Thu, Mar 13, 2014 at 1:09 PM, Chan  wrote:
>>
>>> +1 to get the continuos delivery model blogged out. Also this would help
>>> many other organizations and teams if we setup a proper guideline on our
>>> continuos delivery model.
>>>
>>> Cheers~
>>>
>>>
>>> On Thu, Mar 13, 2014 at 12:07 PM, Kasun Gajasinghe wrote:
>>>
 Hi Azeez,

 We have not enabled the said plugin in our Jenkins setup yet.
 @Ayashkantha, please send the necessary artifacts (the .spi is enough?) to
 install this plugin.

 I think we might need to have another jenkins node (as a slave node)
 for the Pull Request builder plugin ( preferably on a new VM depending on
 the load).  We noticed that when we installed the original jenkins plugin,
 it has messed up the entire jenkins builds, and we had to re-configure a
 new jenkins instance.

 Thanks,
 KasunG



 On Thu, Mar 13, 2014 at 11:34 AM, Afkham Azeez  wrote:

> Ping! Need an update ASAP.
>
>
> On Wed, Mar 12, 2014 at 10:59 AM, Afkham Azeez  wrote:
>
>> Have we enabled this plugin on our Jenkins setup?
>>
>> Where do we maintain this code? Perhaps we have the fork within the
>> WSO2 repo?
>>
>> Did we send the enhancements as pull requests to the relevant
>> original repos? If not, please do so with the proper comments explaining
>> what the enhancement does.
>>
>> Write a blog post about this, Tweet it etc. and make some noise about
>> this and our vision towards continuous delivery.
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* 
>> *twitter: 
>> **http://twitter.com/afkham_azeez*
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: 
> **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Kasun Gajasinghe*
 Software Engineer;
 WSO2 Inc.; http://wso2.com


  ,
 *email: *
 *kasung AT spamfree wso2.com    ** cell: **+94 (77)
 678-0813 <%2B94%20%2877%29%20678-0813>*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe



 *blog: **http://kasunbg.org* 



 *twitter: **http://twitter.com/kasunbg* 




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


>>>
>>>
>>> --
>>> Chan (Dulitha Wijewantha)
>>> Software Engineer - Mobile Development
>>>  WSO2Mobile
>>> Lean.Enterprise.Mobileware
>>>  * ~Email   duli...@wso2.com *
>>> *  ~Mobile +94712112165 <%2B94712112165>*
>>> *  ~Website   dulitha.me *
>>> *  ~Twitter @dulitharw *
>>>   *~SO @chan *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ayashkantha Ramasinghe
>> Software Engineer WSO2, Inc.
>> email: ayashkan..