from:"Ayash"

[Dev] WSO2 Complex Event Processor 4.0.0-M3 Released!

2015-03-09 Thread Ayash

Hi All,

WSO2 CEP Team is pleased to announce the release of WSO2 Complex Event
Processor (Version - 4.0.0 Milestone 3 ).

The Milestone-3 pack is available at [1]

Please follow the documentation for more info (which is working in
progress)  in [2].

You can find a sample to run WSO2 CEP with Apache Storm in [3]

Following are the bug fixes, improvements and the new features.

*Bug*

   - [CEP-953 ] - When deploying an
   custom extension on CEP, 'init' method get invokes twice
   - [CEP-978 ] - Upgrade hazelcast
   version to 3.2.6.wso2v2
   - [CEP-1009 ] - Configuration Not
   Validated when updating Event Builder in source view
   - [CEP-1019 ] -
   [Storm-Intergration][Manager]When more than one node configured as manager,
   all the nodes are trying to submit the topology


*Improvement*

   - [CEP-1010 ] - Enabling event
   simulating via data in database


*New Feature*

   - [CEP-1028 ] - File Based Stream
   Definition Store
   - [CEP-1029 ] - Adding String
   Extension for Siddhi
   - [CEP-1030 ] - Adding Math
   Extension for Siddhi
   - [CEP-1031 ] - Adding Geo/NLP/R
   Extension for Siddhi
   - [CEP-1032 ] - Integrating
   Siddhi 3.0.0
   - [CEP-1033 ] - Adding annotation
   partitioning and query grouping support in Storm


[1] https://svn.wso2.org/repos/wso2/scratch/mohan/cep400/m3

[2]
https://docs.wso2.com/display/CEP400/WSO2+Complex+Event+Processor+Documentation

[3]
https://docs.wso2.com/display/CEP400/Sample+2001+-+Simple+filter+query+with+Apache+Storm+deployment


Thanks,
-WSO2 CEP Team-

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

Re: [Dev] Couldnt start CEP server with samples?

2015-02-09 Thread Ayash

Thanks Rajiv,

This problem is due to command line doesn't support space included paths,
the space should be re formatted as \ or else the full path should
be wrapped with two single or double quotes. Please rename the folder name
starts with CEP... removing spaces in it.

Thanks,
-Ayash

On Tue, Feb 10, 2015 at 11:22 AM, Rajeev Sampath  wrote:

> Hi,
>
> On Tue, Feb 10, 2015 at 9:49 AM, Vijayaratha Vijayasingam  > wrote:
>
>> Hi all;
>> I try sample 0106.
>> I started server like
>>
>>   #./wso2cep-samples.sh -sn 0106,
>>
>> But getting;
>>
>> [2015-02-10 12:14:43,951] FATAL - {CarbonServerManager}  WSO2 Carbon
>> initialization Failed
>>
>> org.wso2.carbon.utils.ServerException: Repository location
>> '/Users/ratha/WSO2/clients/CBA/PoC/CEP/' not found!
>>
>> at
>> org.wso2.carbon.core.CarbonAxisConfigurator.init(CarbonAxisConfigurator.java:151)
>>
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:390)
>>
>> 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)
>>
>>
>> Do i need to create any folder?
>>
>
> There is a known issue when running cep samples with a path with spaces
> [1[. Pls check whether the path where CEP is installed in your machine
> contains spaces.
> (This only affects when running samples.)
>
> [1[ https://wso2.org/jira/browse/CEP-431
>
>
> Thanks
> Rajeev
>
>
>
>> Im using MAC.
>>
>> Thanks.
>>
>> --
>> -Ratha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajeev Sampath
> Senior Software Engineer
> WSO2, Inc.; http://www.wso2.com.
>
> Mobile:
> * +94716265766 <%2B94716265766>*
>
> ___
> 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

Re: [Dev] Couldnt start CEP server with samples?

2015-02-09 Thread Ayash

Sure :)

On Tue, Feb 10, 2015 at 10:55 AM, Sriskandarajah Suhothayan 
wrote:

> Hi
> What version of CEP are you using ?
>
> @Ayashkantha can you look into this please
>
> Suho
>
> On Tue, Feb 10, 2015 at 9:49 AM, Vijayaratha Vijayasingam  > wrote:
>
>> Hi all;
>> I try sample 0106.
>> I started server like
>>
>>   #./wso2cep-samples.sh -sn 0106,
>>
>> But getting;
>>
>> [2015-02-10 12:14:43,951] FATAL - {CarbonServerManager}  WSO2 Carbon
>> initialization Failed
>>
>> org.wso2.carbon.utils.ServerException: Repository location
>> '/Users/ratha/WSO2/clients/CBA/PoC/CEP/' not found!
>>
>> at
>> org.wso2.carbon.core.CarbonAxisConfigurator.init(CarbonAxisConfigurator.java:151)
>>
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:390)
>>
>> 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)
>>
>>
>> Do i need to create any folder?
>>
>> Im using MAC.
>>
>> Thanks.
>>
>> --
>> -Ratha
>>
>
>
>
> --
>
> *S. Suhothayan*
> Technical Lead & Team Lead of WSO2 Complex Event Processor
>  *WSO2 Inc. *http://wso2.com
> * *
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>



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

[Dev] Network failure errors in PR build "ERROR: Could not transfer artifact"

2015-01-16 Thread Ayash

Hi All,

Please refer [1]. This error is due to some network failure. Because the
requested file is there in the nexus [2].

[1] https://wso2.org/jenkins-pr-builder/job/product-cep/131/console
[2]
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.webapp.mgt.server.feature/4.3.0-SNAPSHOT/

This is something unavoidable and we don't have access to re-trigger the
build also. What can we do for that?

Thanks,
-Ayash

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

Re: [Dev] Errors seen while building CDM p2-profile

2015-01-09 Thread Ayash

Hi Prabath,

Sorry for the delayed response. The "carbon-commons" is failing while "WSO2
Carbon - BPEL Applications BE" is being built with the following error,
hence, the data-bridge is not hosted. In BPEL, looks, the carbon components
version should still to be changed.

[ERROR] Failed to execute goal on project
org.wso2.carbon.application.mgt.bpel: Could not resolve dependencies for
project
org.wso2.carbon:org.wso2.carbon.application.mgt.bpel:bundle:4.3.0-SNAPSHOT:
Could not find artifact
org.wso2.carbon:org.wso2.carbon.ndatasource.core:jar:4.3.0-SNAPSHOT in
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
[Help 1]

Thanks,
-Ayash


On Fri, Jan 9, 2015 at 4:26 PM, Prabath Abeysekera 
wrote:

> A gentle reminder!
>
> Cheers,
> Prabath
>
>
> On Thu, Jan 8, 2015 at 12:02 AM, Prabath Abeysekera 
> wrote:
>
>> Hi Folks,
>>
>> Came across the following problem while trying to build the p2 profile of
>> CDM. Data bridge related modules in carbon-commons repository, seem to
>> carry the proper OSGi version ranges, etc already. However, the updated
>> feature archives do not seem to be available in nexus for some reason.
>> Appreciate if someone can urgently have a look and fix this.
>>
>>
>> Installing org.wso2.carbon.identity.relying.party.server.feature.group
>> 4.3.0.SNAPSHOT.
>>
>> Installation failed.
>>
>> Cannot complete the install because one or more required items could not
>> be found.
>>
>>  Software being installed: WSO2 Carbon - Data Bridge - Data Publisher
>> Aggregate Feature 4.3.0.SNAPSHOT
>> (org.wso2.carbon.databridge.datapublisher.feature.group 4.3.0.SNAPSHOT)
>>
>>  Missing requirement: WSO2 Carbon - Data Bridge - Commons Server Feature
>> 4.3.0.SNAPSHOT (org.wso2.carbon.databridge.commons.server.feature.group
>> 4.3.0.SNAPSHOT) requires 'org.wso2.carbon.core.server.feature.group
>> [4.3.0.SNAPSHOT,4.4.0)' but it could not be found
>>
>>  Cannot satisfy dependency:
>>
>>   From: WSO2 Carbon - Data Bridge - Thrift Commons Server Feature
>> 4.3.0.SNAPSHOT
>> (org.wso2.carbon.databridge.commons.thrift.server.feature.group
>> 4.3.0.SNAPSHOT)
>>
>>   To: org.wso2.carbon.databridge.commons.server.feature.group
>> [4.3.0.SNAPSHOT,4.4.0)
>>
>>  Cannot satisfy dependency:
>>
>>   From: WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature
>> 4.3.0.SNAPSHOT (org.wso2.carbon.databridge.datapublisher.feature.group
>> 4.3.0.SNAPSHOT)
>>
>>   To: org.wso2.carbon.databridge.commons.thrift.server.feature.group
>> [4.3.0.SNAPSHOT]
>>
>> Application failed, log file location:
>> /Users/WSO2USER08/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1420654996434.log
>>
>>
>> Cheers,
>>
>> Prabath
>> --
>> Prabath Abeysekara
>> Associate Technical Lead, Data TG.
>> WSO2 Inc.
>> Email: praba...@wso2.com
>> Mobile: +94774171471
>>
>
>
>
> --
> Prabath Abeysekara
> Associate Technical Lead, Data TG.
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> 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

Re: [Dev] BAM PHP data publisher authentication

2014-11-25 Thread Ayash

Hi Omindu,

Hopefully, if the php client library supports TSocket(TTransport), you can
just create SSL php client socket using "fsockopen" and just pass it as a
TSocket. Then, that client might be use to get a thrift session ID from
BAM(using ssl connect method).

What the TSSLTransportFactory(java) class also does is creating
SSLSocket internally
and pass it as TSocket. We may do the same in php also.

Or else the easiest way is, we can create an axis2 service just for thrift
authentication services.(I need others' opinions also about this idea to
know if that is better approach)

Thanks,
-Ayash

On Tue, Nov 25, 2014 at 5:09 PM, Omindu Rathnaweera  wrote:

> Hi,
>
> I am working on a PHP data publisher for BAM. The skeleton php classes and
> Thrift php library can be found at [1].
>
> In order to publish data from the PHP client, a session ID is needed to be
> generated by connecting a *ThriftSecureEventTransmissionServiceClient*. For
> the authentication purpose, the
> *ThriftSecureEventTransmissionServiceClient* requires a secure transport
> wrapped in a *TProtocol* object. Even though Thrift java library provides
> the  *TSSLTransportFactory* class to create a secure transport, the
> Thrift php library does not provide an equivalent method to create a secure
> transport. Because of this, there's a difficulty in authenticating the
> publisher and obtaining a session ID to publish events.
>
> I would like to know your input on overcoming this difficulty or at
> least whether it is possible to obtain the session ID in an alternative way
> without communicating through thrift.
>
>
> [1] - https://github.com/omindu/php-publisher
>
> Thanks,
> Omindu.
> --
> Omindu Rathnaweera
> Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211
>



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

Re: [Dev] Whats bam-data-publishers git repo for ?

2014-11-19 Thread Ayash

Hi Suho,


> Shall we rename this repo as "data-publishers" instead of
> bam-data-publishers and
> Shall we rename "WCF" to dotnet ?
>

Sure, If it doesn't make sense.


> BTW what is Jenkins folder ?
>

That is an unnecessary folder. will remove that.

Thanks,
-Ayash


> Suho
>
> On Mon, Nov 17, 2014 at 12:48 AM, Ayash  wrote:
>
>> Hi Suho,
>>
>> We created that repo to host the non-java data-publisher client
>> libraries. Currently, we have only hosted .net(WCF) data publisher client
>> library. If we'll need some c, c++ data publishers support, we planned to
>> host them all there.
>>
>> Do you think that we have much more relevant place for these to be hosted?
>>
>> Thanks,
>> -Ayash
>>
>> On Sat, Nov 15, 2014 at 9:48 PM, Sriskandarajah Suhothayan > > wrote:
>>
>>> HI
>>>
>>> I found there is a new repo created for bam-data-publishers[1]. And I
>>> also see the content in that is also not relevant.  What is that purpose of
>>> this repo ?
>>>
>>> Regards
>>> Suho
>>>
>>> [1]https://github.com/wso2-dev/bam-data-publishers
>>>
>>> --
>>>
>>> *S. Suhothayan*
>>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>>>  *WSO2 Inc. *http://wso2.com
>>> * <http://wso2.com/>*
>>> lean . enterprise . middleware
>>>
>>>
>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
>>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>>>
>>
>>
>>
>> --
>> Ayashkantha Ramasinghe
>> Software Engineer WSO2, Inc.
>> email: ayashkan...@wso2.com ;
>> TP: +94 77 7 487 669
>>
>
>
>
> --
>
> *S. Suhothayan*
> Technical Lead & Team Lead of WSO2 Complex Event Processor
>  *WSO2 Inc. *http://wso2.com
> * <http://wso2.com/>*
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>



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

Re: [Dev] Whats bam-data-publishers git repo for ?

2014-11-16 Thread Ayash

Hi Suho,

We created that repo to host the non-java data-publisher client libraries.
Currently, we have only hosted .net(WCF) data publisher client library. If
we'll need some c, c++ data publishers support, we planned to host them all
there.

Do you think that we have much more relevant place for these to be hosted?

Thanks,
-Ayash

On Sat, Nov 15, 2014 at 9:48 PM, Sriskandarajah Suhothayan 
wrote:

> HI
>
> I found there is a new repo created for bam-data-publishers[1]. And I also
> see the content in that is also not relevant.  What is that purpose of this
> repo ?
>
> Regards
> Suho
>
> [1]https://github.com/wso2-dev/bam-data-publishers
>
> --
>
> *S. Suhothayan*
> Technical Lead & Team Lead of WSO2 Complex Event Processor
>  *WSO2 Inc. *http://wso2.com
> * <http://wso2.com/>*
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter:
> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>



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

[Dev] JSPException while including path '/archiveui/list_jobs.jsp'

2014-11-08 Thread Ayash

lter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362)
at
org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198)
at
org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370)
at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.IOException: JSPException while including path
'/archiveui/list_jobs.jsp'. ServletException while including page.
at
org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:91)
at
org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
at
org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
at
org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
at
org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
at
org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
... 65 more

Thanks,
-Ayash

-- 
Ayashkantha Ramasinghe
Software Engineer WSO2, Inc.

Re: [Dev] CARBON-14955 please do a brief description

2014-10-29 Thread Ayash

Hi,

For example,

org.wso2.carbon.identity.oauth.stub-4.2.2 should export packages in version
4.2.2. Instead it exports version 4.2.0.

Thanks,
-Ayash

On Thu, Oct 30, 2014 at 7:14 AM, Supun Malinga  wrote:

> Hi,
>
> $subject. Title is not clear what needs to be done. Next time creating a
> jira make sure you add a description to explain what you mean.. :)
>
> https://wso2.org/jira/browse/CARBON-14955
>
> thanks,
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>



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

Re: [Dev] BAM Daily Build - 17/07

2014-07-22 Thread Ayash

Please use the pack hosted here for the tomorrow's testing

https://svn.wso2.org/repos/wso2/scratch/chunk13-release/22_07_2014_new/


On Tue, Jul 22, 2014 at 12:21 AM, Ayash  wrote:

> *find
>
>
> On Tue, Jul 22, 2014 at 12:21 AM, Ayash  wrote:
>
>> Please fine the pack for 22nd of July,
>>
>> https://svn.wso2.org/repos/wso2/people/ayash/BAM/wso2bam-2.4.2.zip
>>
>>
>> On Thu, Jul 17, 2014 at 8:21 PM, Ayash  wrote:
>>
>>> Thanks gokul :)
>>>
>>>
>>> On Thu, Jul 17, 2014 at 6:49 PM, Gokul Balakrishnan 
>>> wrote:
>>>
>>>> Please find the BAM pack built today at [1].
>>>>
>>>> The surefire reports for BAM can also be found in the same localtion.
>>>>
>>>> [1] https://svn.wso2.org/repos/wso2/people/gokul/bam/build/17-07/
>>>>
>>>> Thanks,
>>>>
>>>> --
>>>> *Balakrishnan Gokulakrishnan*
>>>> Software Engineer,
>>>> WSO2, Inc. http://wso2.com
>>>> Mob: +94 77 593 5789 | +1 650 272 9927
>>>>
>>>
>>>
>>>
>>> --
>>> Ayashkantha Ramasinghe
>>> Software Engineer WSO2, Inc.
>>> email: ayashkan...@wso2.com ;
>>> TP: +94 77 7 487 669
>>>
>>
>>
>>
>> --
>> Ayashkantha Ramasinghe
>> Software Engineer WSO2, Inc.
>> email: ayashkan...@wso2.com ;
>> TP: +94 77 7 487 669
>>
>
>
>
> --
> Ayashkantha Ramasinghe
> Software Engineer WSO2, Inc.
> email: ayashkan...@wso2.com ;
> TP: +94 77 7 487 669
>



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

Re: [Dev] BAM Daily Build - 17/07

2014-07-21 Thread Ayash

*find


On Tue, Jul 22, 2014 at 12:21 AM, Ayash  wrote:

> Please fine the pack for 22nd of July,
>
> https://svn.wso2.org/repos/wso2/people/ayash/BAM/wso2bam-2.4.2.zip
>
>
> On Thu, Jul 17, 2014 at 8:21 PM, Ayash  wrote:
>
>> Thanks gokul :)
>>
>>
>> On Thu, Jul 17, 2014 at 6:49 PM, Gokul Balakrishnan 
>> wrote:
>>
>>> Please find the BAM pack built today at [1].
>>>
>>> The surefire reports for BAM can also be found in the same localtion.
>>>
>>> [1] https://svn.wso2.org/repos/wso2/people/gokul/bam/build/17-07/
>>>
>>> Thanks,
>>>
>>> --
>>> *Balakrishnan Gokulakrishnan*
>>> Software Engineer,
>>> WSO2, Inc. http://wso2.com
>>> Mob: +94 77 593 5789 | +1 650 272 9927
>>>
>>
>>
>>
>> --
>> Ayashkantha Ramasinghe
>> Software Engineer WSO2, Inc.
>> email: ayashkan...@wso2.com ;
>> TP: +94 77 7 487 669
>>
>
>
>
> --
> Ayashkantha Ramasinghe
> Software Engineer WSO2, Inc.
> email: ayashkan...@wso2.com ;
> TP: +94 77 7 487 669
>



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

Re: [Dev] BAM Daily Build - 17/07

2014-07-21 Thread Ayash

Please fine the pack for 22nd of July,

https://svn.wso2.org/repos/wso2/people/ayash/BAM/wso2bam-2.4.2.zip


On Thu, Jul 17, 2014 at 8:21 PM, Ayash  wrote:

> Thanks gokul :)
>
>
> On Thu, Jul 17, 2014 at 6:49 PM, Gokul Balakrishnan 
> wrote:
>
>> Please find the BAM pack built today at [1].
>>
>> The surefire reports for BAM can also be found in the same localtion.
>>
>> [1] https://svn.wso2.org/repos/wso2/people/gokul/bam/build/17-07/
>>
>> Thanks,
>>
>> --
>> *Balakrishnan Gokulakrishnan*
>> Software Engineer,
>> WSO2, Inc. http://wso2.com
>> Mob: +94 77 593 5789 | +1 650 272 9927
>>
>
>
>
> --
> Ayashkantha Ramasinghe
> Software Engineer WSO2, Inc.
> email: ayashkan...@wso2.com ;
> TP: +94 77 7 487 669
>



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

Re: [Dev] BAM Daily Build - 17/07

2014-07-17 Thread Ayash

Thanks gokul :)


On Thu, Jul 17, 2014 at 6:49 PM, Gokul Balakrishnan  wrote:

> Please find the BAM pack built today at [1].
>
> The surefire reports for BAM can also be found in the same localtion.
>
> [1] https://svn.wso2.org/repos/wso2/people/gokul/bam/build/17-07/
>
> Thanks,
>
> --
> *Balakrishnan Gokulakrishnan*
> Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>



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

Re: [Dev] [BAM] Optimizing BAM Mediator Data Publishing Logic

2014-06-12 Thread Ayash

Hi Imesh,

While experiencing this problem, do you remember where the BAM Mediators
were in the mediation flow? Have you kept them after calling "send" or
before in the mediation flow?

Thanks,
-Ayash


On Thu, Feb 13, 2014 at 2:18 PM, Imesh Gunaratne  wrote:

> s/comapred/compared/g
> s/millisecods/milliseconds/g
>
>
> On Thu, Feb 13, 2014 at 10:21 AM, Imesh Gunaratne  wrote:
>
>> Hi Sinthuja,
>>
>> Thanks for your response. Absolutely the concern is not with the data
>> publisher but with the bam mediator logic being executed in the mediation
>> flow.
>>
>> This is something I experienced during last couple of days while
>> configuring several BAM mediators in an ESB flow. When a load test was run
>> (with a set of concurrent users) and the ESB mediation latency was
>> monitored, the BAM mediators were taking considerable amount of time
>> comapred with the ESB latency without having the BAM mediators. It was like
>> 90 ms with the BAM mediators and 35 ms without them.
>>
>> What I wanted to highlight here is that, I could not see any reason for
>> executing the above logic in the mediation flow and adding several
>> millisecods to the ESB latency.
>>
>> Thanks
>>
>>
>> On Thu, Feb 13, 2014 at 12:32 AM, Sinthuja Ragendran 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> Publish() method in data publisher is not a blocking call, it's a
>>> asynchronous call. Within data publisher the events are put into a queue
>>> and a separate thread does the real publishing to BAM. Also in BAM
>>> mediator, the AsyncDataPublisher is being used therefore the connection to
>>> BAM is also made asynchronous.  Hence IMHO it's not required to spawn a new
>>> thread externally to publish the events and make it complicated.
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>>
>>> On Thu, Feb 13, 2014 at 2:15 AM, Imesh Gunaratne  wrote:
>>>
>>>> Hi,
>>>>
>>>> This is regarding the BAM Mediator 4.2.0.
>>>> As it looks like currently the BAM Mediator is executing the data
>>>> publishing logic in the same thread which the current message mediation is
>>>> happening:
>>>>
>>>> public class BamMediator:
>>>>
>>>> public boolean mediate(MessageContext messageContext) {
>>>>   ...
>>>>   try {
>>>> stream.sendEvents(messageContext);
>>>>   } catch (BamMediatorException e) {
>>>>   return true;
>>>>   }
>>>>
>>>>}
>>>> }
>>>>
>>>> public class Stream {
>>>>
>>>> ...
>>>>
>>>> public void sendEvents(MessageContext messageContext) throws 
>>>> BamMediatorException {
>>>> ActivityIDSetter activityIDSetter = new ActivityIDSetter();
>>>> activityIDSetter.setActivityIdInTransportHeader(messageContext);
>>>> try {
>>>> if (!isPublisherCreated) {
>>>> initializeDataPublisher(this);
>>>> isPublisherCreated = true;
>>>> }
>>>> this.publishEvent(messageContext);
>>>> } catch (BamMediatorException e) {
>>>> String errorMsg = "Problem occurred while logging events in 
>>>> the BAM Mediator. " + e.getMessage();
>>>> log.error(errorMsg, e);
>>>> throw new BamMediatorException(errorMsg, e);
>>>> }
>>>> }
>>>>
>>>> ...
>>>>
>>>> }
>>>>
>>>> I think if we move this logic to a new thread we could reduce the time
>>>> it takes to execute the data publishing logic from the main message flow.
>>>> WDYT?
>>>>
>>>> Thanks
>>>>
>>>> --
>>>> *Imesh Gunaratne*
>>>> Technical Lead
>>>> WSO2 Inc: http://wso2.com
>>>> T: +94 11 214 5345 M: +94 77 374 2057
>>>> W: http://imesh.gunaratne.org
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Sinthuja Rajendran*
>>> Software Engineer <http://wso2.com/>
>>> WSO2, Inc.:http://wso2.com
>>>
>>> Blog: http://sinthu-rajan.blogspot.com/
>>> Mobile: +94774273955
>>>
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] [BAM] Activity Dashboard search function issue

2014-06-05 Thread Ayash

Hi Inosh,

Why do we have an error like this in UI?

"Query Validation Failed. Please make sure that all properties are filled"

This does make no sense to the user, if there is no error in a search query
or something we are using in UI. We don't have to send an error like that
to the user end. If there is no data indexed as the component expects, we
have to make the user feel the same in UI too. Please tell me if I am wrong.

This is what I understood by chatting with akila, he doesn't have right
error in the UI to tack the error with him.

Thanks,
-Ayash



On Wed, Jun 4, 2014 at 2:34 PM, Inosh Goonewardena  wrote:

> Hi Akila,
>
> As Thayalan explained you have to add indexing properties in-order to use
> activity monitoring dashboard for a generic message tracing use case.
> However, activity dashboard will will not function with kpi-definition
> sample because kpi-definition stream doesn't have correlated data property
> named 'activity_id' which is a mandatory field for activity tracing(refer
> the section "Global activity index" in [1] ) in it. To get a better
> understanding about message tracing, please follow [2].
>
> [1] - https://docs.wso2.org/display/BAM240/Indexing+in+Cassandra
> [2] -
> https://docs.wso2.org/display/BAM241/Setting+up+Message+Tracing+for+WSO2+ESB
>
>
> On Wed, Jun 4, 2014 at 11:07 PM, Thayalan  wrote:
>
>> I guess Activity Dashboard to work you should enable indexing. By default
>> only Message_Tracing.tbox added with indexing. If you want to try the KPI
>> sample please add indxing to streams.properties file of the toolbox and
>> perform the search. Ref [1] & [2]. I'm not quite sure whether Timestamp
>> being indexed by default and can be search with 2.4.0 version.
>>
>
>> 1. https://docs.wso2.org/display/BAM240/Indexing+in+Cassandra
>> 2. https://docs.wso2.org/display/BAM240/Searching+Cassandra+Data
>>
>>
>>
>>
>> On Wed, Jun 4, 2014 at 3:41 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I used kpi-definitions sample to publish events to BAM. Then I added
>>> Phone Retail Store Toolbox in ToolBox list. In analytics section I can
>>> successfully execute the hive scripts for "phone_retail_store_script".
>>>
>>> But when I try to search activities in "Activity Dashboard", it gives
>>> me this error - "* Query Validation Failed. Please make sure that all
>>> properties are filled.". But I've filled all the required fields
>>> (status, start time, end time). What am I doing wrong here? Please
>>> help.
>>>
>>> Thanks.
>>>
>>> PS - I'm using BAM ver. 2.4.0
>>>
>>> --
>>> Akila Ravihansa Perera
>>> Software Engineer
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>> Phone: +94 77 64 154 38
>>> Blog: http://ravihansa3000.blogspot.com
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>>
>> --
>> Regards,
>> Thayalan Sivapaleswararajah
>> Associate Technical Lead - QA
>> Mob: +94(0)777872485
>> Tel : +94(0)(11)2145345
>> Fax : +94(0)(11)2145300
>> Email: thaya...@wso2.com
>>
>>
>> *Disclaimer*: *This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> Inosh Goonewardena
> Associate Technical Lead- WSO2 Inc.
> Mobile: +94779966317
>
> ___
> 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

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

2014-03-18 Thread Ayash

Find the full story,
http://tech-ayash.blogspot.com/2014/03/save-your-code-from-unsafe-commits.html

Thanks,
-Ayash


On Sun, Mar 16, 2014 at 12:39 PM, Ayash  wrote:

>
>
>
> On Fri, Mar 14, 2014 at 6:31 PM, Afkham Azeez  wrote:
>
>>
>>
>>
>> On Fri, Mar 14, 2014 at 12:22 PM, Ayash  wrote:
>>
>>> Hey,
>>>
>>> Which one is the correct repo?
>>> https://github.com/janinko/ghprb
>>>
>>
>> The owner of the above repo has said that he is happy to merge the pull
>> request. Please send him the pull request. Also send the github-api plugin
>> pull request.
>>
>
> How can they manage to have the API level change to their pulgin? Really,
> sending a pull request would be a great idea, but, first, we'll have to
> make the change on kohsuke/github-api and let the plugin(ghprb) install the
> updated plugin(gh-api) too while installing the ghprb plugin for preventing
> them to have the same issue we also got weeks of time, right?
>
> How we use the plugin in home is replacing the gh-api with our updated
> plugin. I am not sure if we can do the same here too. Shall I put a comment
> to get their suggestion? I guess, they could be expertized in handling a
> problem like this.
>
> Thanks,
> -Ayash
>
>
>>
>>
>>
>>> 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?
>>>>>>>>>
>>>>>>>

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

2014-03-16 Thread Ayash

On Fri, Mar 14, 2014 at 6:31 PM, Afkham Azeez  wrote:

>
>
>
> On Fri, Mar 14, 2014 at 12:22 PM, Ayash  wrote:
>
>> Hey,
>>
>> Which one is the correct repo?
>> https://github.com/janinko/ghprb
>>
>
> The owner of the above repo has said that he is happy to merge the pull
> request. Please send him the pull request. Also send the github-api plugin
> pull request.
>

How can they manage to have the API level change to their pulgin? Really,
sending a pull request would be a great idea, but, first, we'll have to
make the change on kohsuke/github-api and let the plugin(ghprb) install the
updated plugin(gh-api) too while installing the ghprb plugin for preventing
them to have the same issue we also got weeks of time, right?

How we use the plugin in home is replacing the gh-api with our updated
plugin. I am not sure if we can do the same here too. Shall I put a comment
to get their suggestion? I guess, they could be expertized in handling a
problem like this.

Thanks,
-Ayash


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

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

2014-03-13 Thread 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/
>>>>>> * <http://www.apache.org/>*
>>>>>> *email: **az...@wso2.com* 
>>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>>>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>>>>> *twitter: 
>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>>>>> <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/
>>>>> * <http://www.apache.org/>*
>>>>> *email: **az...@wso2.com* 
>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>>>> *twitter: 
>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>>>> <http://lk.linkedin.com/in/afkhamazeez>*
>>>>>
>>>>> *Lean . Enterprise . Middleware*
>>>>>
>>>>> ___
>>>>> De

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

2014-03-13 Thread 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/
>>>>>> * <http://www.apache.org/>*
>>>>>> *email: **az...@wso2.com* 
>>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>>>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>>>>> *twitter: 
>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>>>>> <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/
>>>>> * <http://www.apache.org/>*
>>>>> *email: **az...@wso2.com* 
>>>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>>>> *http://blog.afkham.org* <http://blog.afkham.org>
>>>>> *twitter: 
>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>>>> <http://lk.linkedin.com/in/afkhamazeez>*
>>>>>
>>>>> *Lean . Enterprise . Middleware*
>>>>>
>>>>> ___
>>>>> Dev maili

[Dev] WSO2 Complex Event Processor 4.0.0-M3 Released!

Re: [Dev] Couldnt start CEP server with samples?

Re: [Dev] Couldnt start CEP server with samples?

[Dev] Network failure errors in PR build "ERROR: Could not transfer artifact"

Re: [Dev] Errors seen while building CDM p2-profile

Re: [Dev] BAM PHP data publisher authentication

Re: [Dev] Whats bam-data-publishers git repo for ?

Re: [Dev] Whats bam-data-publishers git repo for ?

[Dev] JSPException while including path '/archiveui/list_jobs.jsp'

Re: [Dev] CARBON-14955 please do a brief description

Re: [Dev] BAM Daily Build - 17/07

Re: [Dev] BAM Daily Build - 17/07

Re: [Dev] BAM Daily Build - 17/07

Re: [Dev] BAM Daily Build - 17/07

Re: [Dev] [BAM] Optimizing BAM Mediator Data Publishing Logic

Re: [Dev] [BAM] Activity Dashboard search function issue

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

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

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

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

20 matches

Site Navigation

Mail list logo

Footer information