Re: [Dev] Ws02 emm Help

[Lakshman Udayakantha]

Hi,

It is better if you can point the steps to reproduce the issue. I assume,
you are trying run the project on glassfish server from IDE. In that case,
mention the steps how you have done it? WSO2 EMM coming bundled with tomcat
container by default. So you may run EMM with tomcat without any issue. You
should be able to run the product download from WSO2 site[1] with java 1.7
run time.

[1] http://wso2.com/products/enterprise-mobility-manager/

Thanks

On Tue, May 24, 2016 at 11:46 PM, First NameTangwe Caleb <
tangweca...@yahoo.com> wrote:

> Good Day all
> this is my first run of this projectm I am a newBie so please overlook my
> ignorance.
> My Deve Environment is NetBeans 8
> Apach maven 3.3
> glassfish 3.3.3
> Project-emm 2.0.1 Downloaded from
> https://codeload.github.com/wso2/product-emm/zip/v2.0.1
>
> On Deployment after Succesful Build I get this error
> Please anyHelp or advice would be greatly apreciated
>
> Severe:   Startup of context /mdm-admin failed due to previous errors
> Severe:   ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: java.lang.NoClassDefFoundError:
> org/springframework/context/ApplicationListener
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:5985)
> at com.sun.enterprise.web.WebModule.start(WebModule.java:691)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1041)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:1024)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:747)
> at
> com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:2286)
> at
> com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1932)
> at com.sun.enterprise.web.WebApplication.start(WebApplication.java:139)
> at org.glassfish.internal.data.EngineRef.start(EngineRef.java:122)
> at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:291)
> at
> org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:352)
> at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:500)
> at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219)
> at
> org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:539)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:535)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:534)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:565)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:557)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:556)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1464)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:109)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1846)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1722)
> at
> com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:534)
> at
> com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:224)
> at
> org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:189)
> at
> com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:459)
> at
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:167)
> at
> org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:206)
> at
> org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:180)
> at
> org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:235)
> at
> org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
> at
> org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:283)
> at
> org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:200)
> at
> org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:132)
> at
> org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:111)
> at
> org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
> at
> org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:536)
> at
> org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112)
> at
> 

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Asantha Thilina]

Hi Tharindu,

sure i'll be look forward for that

Thanks,
Asantha

On Thu, May 26, 2016 at 9:37 PM, Tharindu Edirisinghe 
wrote:

> Hi Asantha,
>
> Glad to hear the progress... Sure I'll review over the weekend and provide
> feedback. By next week we'll have a hangout to discuss on how to move
> forward and the difficulties you have faced.  Keep the momentum going !
>
> Regards,
> TharinduE
>
> On Fri, May 27, 2016 at 12:17 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> i been able to fix the mongodb user store intitalizing error now it
>> working successfully it will be registered as a secondary user store in IS
>> and when going to add a new users and roles it will show the domain of
>> mongodb userstore still i having small issues in my json query formats for
>> mongodb i fixing those issues at the moment all the progress so far i made
>> updated to my github repository[1] and i recently updated my blog[2] as
>> well,can you review my code and give me a feedback?
>>
>> [1]https://github.com/asanthamax/mongodbuserstore
>> [2]http://asanthamax.blogspot.com/
>>
>> Thanks,
>> Asantha
>>
>> On Sun, May 22, 2016 at 3:38 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> I have override all the methods in AbstractUserStoreManager in my
>>> MongoDBUserStoreManager class after that when i try to add new secondary
>>> user store in management console i got following error i attached the
>>> screen shot of the error with this mail
>>> i have pushed all the progress upto now to my github repository[1]
>>> can you give me some tips to solve this issue?
>>> any suggestion would be grateful
>>> [1] https://github.com/asanthamax/mongodbuserstore
>>> Thanks,
>>> Asantha
>>>
>>> On Thu, May 19, 2016 at 11:47 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 sorry for the late reply ,as you advised i remove the scr reference and
 its corresponding methods from user store now it's works fine but i having
 another small issue if i wanted to run my mongodb user store as as my
 primary user store how would i do that?
 i added my user store configurations to user-mgt.xml file and comented
 the ldap userstore properties and i added MongoDBUserStore to
 tenant-mgt.xml as well but then i get error as datasource cannot be casted
 to MongoDB db source while deploying thats mean its still referring to
 Default Activator inside carbon core module how would i set it to my
 activator to reffer?
 any suggestion or help would be grateful
 Thanks,
 Asantha

 On Wed, May 18, 2016 at 10:29 PM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Asantha,
>
> Great progress so far !
>
> Since the reference is given to realm service in the bundle activator,
> you should be facing the issue. Can you remove the service reference from
> the bundle activator class. (You can delete the following from the class).
>
> * @scr.reference name="user.realmservice.default"
>  * interface="org.wso2.carbon.user.core.service.RealmService"
> cardinality="1..1"
>  * policy="dynamic" bind="setRealmService"
>  * unbind="unsetRealmService"
>
> Also delete the following methods where realm service is used.
>
> getRealmService()
> setRealmService(RealmService rlmService)
> unsetRealmService(RealmService rlmService)
>
> After that can you try if the userstore manager is working as
> expected. If you face any issues, please get back.
>
> Thank you,
> TharinduE
>
>
>
>
>
>
> On Sun, May 15, 2016 at 7:48 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> I found the issue after debugging into my code ,my service bundle is
>> not get activated because i referring into mongodb-driver which is not 
>> osgi
>> comaptible and i just found another library in here[1] and it is worked 
>> for
>> me ,fixed project i pushed into my github repository [2].
>> i found out that *DefaultRealmService* which is used in Bundle
>> Activator of JDBCUserstoreManager cannot be used for MongoDB since it 
>> used
>> *java.sql.DataSource*.
>> Is their having any DataSource class like that for MongoDB? or would
>> i have to create a different logic to implement that scenario in MongoDB?
>> waiting for your suggestion
>>
>> [1].
>> http://central.maven.org/maven2/org/mongodb/mongo-java-driver/3.2.2/
>> [2]. https://github.com/asanthamax/mongodbuserstore
>> Thanks,
>> Asantha
>>
>> On Sat, May 14, 2016 at 10:53 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> i faced following issue while i developing ,
>>> after adding my new json query support i didn't able to see My
>>> 

Re: [Dev] [UUF] Failing remote debugging the code of UUF v1.0.0-m5

[Sudharma Subasinghe]

Hi Rasika,

Those two issues are solved with the provided fix. Thank you  for the
response.

On Fri, May 27, 2016 at 11:14 AM, Rasika Perera  wrote:

> ​Hi Sudharma,
>
> ​UUF will turning into the debug mode from "-Xdebug" JVM parameter(when
> remote debugging is on).
>
> When UUF debug mode is on, It doesn't cache anything. Trying to reload the
> application per each request. This error occurs when trying to reload the
> app. This is a known bug and fixed with [1].
>
> Also it deactivates the debug pointers after starting the debug mode
>
> Can you verify this behaviour? This should not affect your IDE or break
> pointers.
>
> [1] 
> *https://github.com/wso2/carbon-uuf/commit/fe1255a702d08370843db2e06096412ba283708c
> *
>
>
> On Fri, May 27, 2016 at 10:32 AM, Sudharma Subasinghe 
> wrote:
>
>> Hi,
>>
>> I got following exception while loading the uuf app under remote
>> debugging mode. Also it deactivates the debug pointers after starting the
>> debug mode.
>>
>> [2016-05-27 10:12:48,206] ERROR
>> {org.wso2.carbon.uuf.internal.UUFRegistry} - A server occurred while
>> serving for request '/bpmn-explorer/'.
>> org.wso2.carbon.uuf.exception.UUFException: Cannot reload app
>> 'org.wso2.uuf.sample.bpmn-explorer'.
>> at
>> org.wso2.carbon.uuf.internal.UUFRegistry.lambda$reloadApp$15(UUFRegistry.java:158)
>> at
>> org.wso2.carbon.uuf.internal.UUFRegistry$$Lambda$113/1112994017.get(Unknown
>> Source)
>> at java.util.Optional.orElseThrow(Optional.java:290)
>> at
>> org.wso2.carbon.uuf.internal.UUFRegistry.reloadApp(UUFRegistry.java:158)
>> at org.wso2.carbon.uuf.internal.UUFRegistry.serve(UUFRegistry.java:99)
>> at
>> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.execute(UUFMicroservice.java:105)
>> at
>> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.get(UUFMicroservice.java:93)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at
>> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:95)
>> at
>> org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:53)
>> at
>> org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:31)
>> at
>> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>> at
>> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
>> at
>> io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:32)
>> at
>> io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:299)
>> at
>> io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:36)
>> at
>> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:110)
>> at
>> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
>>
>> Without remote debugging mode enabling, it loads apps successfully.
>>
>> Without "Debugger.isDebuggingEnabled()" as in [1], it starts the
>> debugging successfully. But still gives the same exception.
>>
>> I think, when debugging is enabled, reloading the requested app is not
>> properly working.
>>
>> [1]
>> https://github.com/wso2/carbon-uuf/blob/v1.0.0-m5/uuf-core/src/main/java/org/wso2/carbon/uuf/internal/UUFRegistry.java#L98
>>
>> Thanks
>> Sudharma
>>
>>
>>
>>
>> --
>> Sudharma Subasinghe,
>> Software Engineer,
>> WSO2 Inc.
>> Email: sudhar...@wso2.com 
>> Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
>>
>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
Sudharma Subasinghe,
Software Engineer,
WSO2 Inc.
Email: sudhar...@wso2.com 
Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Failing remote debugging the code of UUF v1.0.0-m5

[Rasika Perera]

​Hi Sudharma,

​UUF will turning into the debug mode from "-Xdebug" JVM parameter(when
remote debugging is on).

When UUF debug mode is on, It doesn't cache anything. Trying to reload the
application per each request. This error occurs when trying to reload the
app. This is a known bug and fixed with [1].

Also it deactivates the debug pointers after starting the debug mode

Can you verify this behaviour? This should not affect your IDE or break
pointers.

[1] 
*https://github.com/wso2/carbon-uuf/commit/fe1255a702d08370843db2e06096412ba283708c
*


On Fri, May 27, 2016 at 10:32 AM, Sudharma Subasinghe 
wrote:

> Hi,
>
> I got following exception while loading the uuf app under remote debugging
> mode. Also it deactivates the debug pointers after starting the debug mode.
>
> [2016-05-27 10:12:48,206] ERROR {org.wso2.carbon.uuf.internal.UUFRegistry}
> - A server occurred while serving for request '/bpmn-explorer/'.
> org.wso2.carbon.uuf.exception.UUFException: Cannot reload app
> 'org.wso2.uuf.sample.bpmn-explorer'.
> at
> org.wso2.carbon.uuf.internal.UUFRegistry.lambda$reloadApp$15(UUFRegistry.java:158)
> at
> org.wso2.carbon.uuf.internal.UUFRegistry$$Lambda$113/1112994017.get(Unknown
> Source)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at
> org.wso2.carbon.uuf.internal.UUFRegistry.reloadApp(UUFRegistry.java:158)
> at org.wso2.carbon.uuf.internal.UUFRegistry.serve(UUFRegistry.java:99)
> at
> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.execute(UUFMicroservice.java:105)
> at
> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.get(UUFMicroservice.java:93)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:95)
> at
> org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:53)
> at
> org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:31)
> at
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
> at
> io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:32)
> at
> io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:299)
> at
> io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:36)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:110)
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
>
> Without remote debugging mode enabling, it loads apps successfully.
>
> Without "Debugger.isDebuggingEnabled()" as in [1], it starts the
> debugging successfully. But still gives the same exception.
>
> I think, when debugging is enabled, reloading the requested app is not
> properly working.
>
> [1]
> https://github.com/wso2/carbon-uuf/blob/v1.0.0-m5/uuf-core/src/main/java/org/wso2/carbon/uuf/internal/UUFRegistry.java#L98
>
> Thanks
> Sudharma
>
>
>
>
> --
> Sudharma Subasinghe,
> Software Engineer,
> WSO2 Inc.
> Email: sudhar...@wso2.com 
> Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
>



-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

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

Re: [Dev] What is the Jira project for "carbon-gateway-framework"

[Isuru Udana]

Hi Lahiru,

Jira project is,

https://wso2.org/jira/browse/CGF

Readme updated.

Thanks.


On Wed, May 25, 2016 at 9:41 PM, Lahiru Sandaruwan  wrote:

> Hi,
>
> $subject? Shall we update in Readme?
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> phone: +94773325954
> email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>


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

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Bhathiya Jayasekara]

Thanks.

On Fri, May 27, 2016 at 10:37 AM, Megala Uthayakumar 
wrote:

> We will do a release tonight.
>
> Thanks
>
> On Fri, May 27, 2016 at 10:33 AM, Bhathiya Jayasekara 
> wrote:
>
>> We still have carbon dashboard 1.0.15 in APIM. Will upgrade. When are you
>> planning to release this?
>>
>> Thanks,
>> Bhathiya
>>
>> On Fri, May 27, 2016 at 10:31 AM, Bhathiya Jayasekara 
>> wrote:
>>
>>> +Ruwan
>>>
>>> On Fri, May 27, 2016 at 10:20 AM, Megala Uthayakumar 
>>> wrote:
>>>
 Hi,
 This fix is available in carbon-dashboards 1.0.17-SNAPSHOT. Is APIM
 2.0.0 SNAPSHOT uses the same version?

 Thanks.

 On Fri, May 27, 2016 at 10:02 AM, Deependra Ariyadewa 
 wrote:

> This error still exists in the APIM 2.0.0 SNAPSHOT pack built on 26th
> May 2016.
>
> On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar 
> wrote:
>
>> Hi,
>>
>> We have moved the fix for the google connectivity problem with the
>> commit [1].
>>
>> [1]
>> https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb
>>
>> Thanks.
>>
>> Regards,
>> Megala
>>
>> On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran <
>> sinth...@wso2.com> wrote:
>>
>>> Hi Megala,
>>>
>>> Please check the shindig-server feature and try to remove the
>>> unwanted files from there it self, hence we can omit this behaviour.
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon 
>>> wrote:
>>>
 >>Can't we fix this during the shinding-server feature generation?
 +1
 So that every product using shindig does not have to unzip and zip
 the war file to fix it.

 Cheers,
 Ruwan

 On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran <
 sinth...@wso2.com> wrote:

> Hi Tanya,
>
> Can't we fix this during the shinding-server feature generation?
>
> Thanks,
> Sinthuja.
>
> On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara 
> wrote:
>
>> Adding Bhathiya.
>>
>> We got same exception yesterday in APIM as well. We will need to
>> same thing for DS as well.
>>
>> Thanks,
>> Harsha
>>
>> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon > > wrote:
>>
>>> Thanks Tanya for the information. We will follow the same as in
>>> DS.
>>>
>>> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma <
>>> ta...@wso2.com> wrote:
>>>
 Hi Ruwan,

 Usually this error is thrown as shindig is trying to load some
 google analytics apis. So when there is no internet connection 
 this error
 can be observed.
 To get rid of this error we have to remove google related stuff
 from shindig features.txt file

 *features-extras/analytics/feature.xml*
 *features-extras/com.google.gadgets.analytics/feature.xml*

 But since we don't maintain a shindig fork, we can't do this
 from carbon-dashboards level. So in the Dashboard Server level we 
 are
 replacing the features.txt file with a file which doesn't have 
 above 2
 entries [1]. We'll have to do the same for apim analytics as well.

 [1]
 https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e

 Thanks,
 Tanya

 On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon <
 ruw...@wso2.com> wrote:

> Hi DS team,
> I am getting the following error in APIM 2.0.0-SNAPSHOT which
> integrate DS features. Any Idea why? can we not print those 
> errors due to
> outside dependencies?
>
> ---
>
> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
> One of the two will be used. Which one is undefined.
>
> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources
> from res:features/features.txt are loading.
>
> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor
> being used does not support secure parsing.
>
> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders
> are being reused.
>
> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources
> from 

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Megala Uthayakumar]

We will do a release tonight.

Thanks

On Fri, May 27, 2016 at 10:33 AM, Bhathiya Jayasekara 
wrote:

> We still have carbon dashboard 1.0.15 in APIM. Will upgrade. When are you
> planning to release this?
>
> Thanks,
> Bhathiya
>
> On Fri, May 27, 2016 at 10:31 AM, Bhathiya Jayasekara 
> wrote:
>
>> +Ruwan
>>
>> On Fri, May 27, 2016 at 10:20 AM, Megala Uthayakumar 
>> wrote:
>>
>>> Hi,
>>> This fix is available in carbon-dashboards 1.0.17-SNAPSHOT. Is APIM
>>> 2.0.0 SNAPSHOT uses the same version?
>>>
>>> Thanks.
>>>
>>> On Fri, May 27, 2016 at 10:02 AM, Deependra Ariyadewa 
>>> wrote:
>>>
 This error still exists in the APIM 2.0.0 SNAPSHOT pack built on 26th
 May 2016.

 On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar 
 wrote:

> Hi,
>
> We have moved the fix for the google connectivity problem with the
> commit [1].
>
> [1]
> https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb
>
> Thanks.
>
> Regards,
> Megala
>
> On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran <
> sinth...@wso2.com> wrote:
>
>> Hi Megala,
>>
>> Please check the shindig-server feature and try to remove the
>> unwanted files from there it self, hence we can omit this behaviour.
>>
>> Thanks,
>> Sinthuja.
>>
>> On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon 
>> wrote:
>>
>>> >>Can't we fix this during the shinding-server feature generation?
>>> +1
>>> So that every product using shindig does not have to unzip and zip
>>> the war file to fix it.
>>>
>>> Cheers,
>>> Ruwan
>>>
>>> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran <
>>> sinth...@wso2.com> wrote:
>>>
 Hi Tanya,

 Can't we fix this during the shinding-server feature generation?

 Thanks,
 Sinthuja.

 On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara 
 wrote:

> Adding Bhathiya.
>
> We got same exception yesterday in APIM as well. We will need to
> same thing for DS as well.
>
> Thanks,
> Harsha
>
> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon 
> wrote:
>
>> Thanks Tanya for the information. We will follow the same as in
>> DS.
>>
>> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma <
>> ta...@wso2.com> wrote:
>>
>>> Hi Ruwan,
>>>
>>> Usually this error is thrown as shindig is trying to load some
>>> google analytics apis. So when there is no internet connection this 
>>> error
>>> can be observed.
>>> To get rid of this error we have to remove google related stuff
>>> from shindig features.txt file
>>>
>>> *features-extras/analytics/feature.xml*
>>> *features-extras/com.google.gadgets.analytics/feature.xml*
>>>
>>> But since we don't maintain a shindig fork, we can't do this
>>> from carbon-dashboards level. So in the Dashboard Server level we 
>>> are
>>> replacing the features.txt file with a file which doesn't have 
>>> above 2
>>> entries [1]. We'll have to do the same for apim analytics as well.
>>>
>>> [1]
>>> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon <
>>> ruw...@wso2.com> wrote:
>>>
 Hi DS team,
 I am getting the following error in APIM 2.0.0-SNAPSHOT which
 integrate DS features. Any Idea why? can we not print those errors 
 due to
 outside dependencies?

 ---

 achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
 One of the two will be used. Which one is undefined.

 [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources
 from res:features/features.txt are loading.

 [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor
 being used does not support secure parsing.

 [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are
 being reused.

 [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources
 from res:features-extras/features.txt are loading.

 [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService
 Starting polling event receivers

 [2016-05-17 17:36:19,510]  INFO - 

[Dev] Deprecating APIM Analytics REST Client Implementation

[Rukshan Premathunga]

Hi all,

We hope to deprecate current Statistics implementation of DAS REST API from
the APIM 2.0.x version. The reason was, when compared with RDBMS
implementation REST client having a comparable performance issue. We did a
performance test for both REST and RDBMS implementation and we observed the
following result.


records RDBMS (ms) REST (ms)
10 42 89
20 10 110
30 10 120
40 9 150
50 15 160
100 9 350
200 12 1100
350 10 1466
1000 33 2306
2000 8 7351
3000 11 11381
4000 14 20504
5000 9 29633


​

Thus comparing numbers, we can see that in REST client implementation there
is a huge performance issue compared to RDBMS. Thus APIM default analytic
client will be RDBMS instead of REST client from APIM next release onward
and REST implementation[1] will be deprecated.

[1]
https://github.com/wso2/carbon-apimgt/blob/release-6.0.x/components/apimgt/org.wso2.carbon.apimgt.usage/org.wso2.carbon.apimgt.usage.client/src/main/java/org/wso2/carbon/apimgt/usage/client/impl/APIUsageStatisticsRestClientImpl.java

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

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Bhathiya Jayasekara]

We still have carbon dashboard 1.0.15 in APIM. Will upgrade. When are you
planning to release this?

Thanks,
Bhathiya

On Fri, May 27, 2016 at 10:31 AM, Bhathiya Jayasekara 
wrote:

> +Ruwan
>
> On Fri, May 27, 2016 at 10:20 AM, Megala Uthayakumar 
> wrote:
>
>> Hi,
>> This fix is available in carbon-dashboards 1.0.17-SNAPSHOT. Is APIM
>> 2.0.0 SNAPSHOT uses the same version?
>>
>> Thanks.
>>
>> On Fri, May 27, 2016 at 10:02 AM, Deependra Ariyadewa 
>> wrote:
>>
>>> This error still exists in the APIM 2.0.0 SNAPSHOT pack built on 26th
>>> May 2016.
>>>
>>> On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar 
>>> wrote:
>>>
 Hi,

 We have moved the fix for the google connectivity problem with the
 commit [1].

 [1]
 https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb

 Thanks.

 Regards,
 Megala

 On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran  wrote:

> Hi Megala,
>
> Please check the shindig-server feature and try to remove the unwanted
> files from there it self, hence we can omit this behaviour.
>
> Thanks,
> Sinthuja.
>
> On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon 
> wrote:
>
>> >>Can't we fix this during the shinding-server feature generation?
>> +1
>> So that every product using shindig does not have to unzip and zip
>> the war file to fix it.
>>
>> Cheers,
>> Ruwan
>>
>> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran <
>> sinth...@wso2.com> wrote:
>>
>>> Hi Tanya,
>>>
>>> Can't we fix this during the shinding-server feature generation?
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara 
>>> wrote:
>>>
 Adding Bhathiya.

 We got same exception yesterday in APIM as well. We will need to
 same thing for DS as well.

 Thanks,
 Harsha

 On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon 
 wrote:

> Thanks Tanya for the information. We will follow the same as in DS.
>
> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma <
> ta...@wso2.com> wrote:
>
>> Hi Ruwan,
>>
>> Usually this error is thrown as shindig is trying to load some
>> google analytics apis. So when there is no internet connection this 
>> error
>> can be observed.
>> To get rid of this error we have to remove google related stuff
>> from shindig features.txt file
>>
>> *features-extras/analytics/feature.xml*
>> *features-extras/com.google.gadgets.analytics/feature.xml*
>>
>> But since we don't maintain a shindig fork, we can't do this from
>> carbon-dashboards level. So in the Dashboard Server level we are 
>> replacing
>> the features.txt file with a file which doesn't have above 2 entries 
>> [1].
>> We'll have to do the same for apim analytics as well.
>>
>> [1]
>> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>>
>> Thanks,
>> Tanya
>>
>> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon > > wrote:
>>
>>> Hi DS team,
>>> I am getting the following error in APIM 2.0.0-SNAPSHOT which
>>> integrate DS features. Any Idea why? can we not print those errors 
>>> due to
>>> outside dependencies?
>>>
>>> ---
>>>
>>> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
>>> One of the two will be used. Which one is undefined.
>>>
>>> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
>>> res:features/features.txt are loading.
>>>
>>> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor
>>> being used does not support secure parsing.
>>>
>>> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are
>>> being reused.
>>>
>>> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
>>> res:features-extras/features.txt are loading.
>>>
>>> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService
>>> Starting polling event receivers
>>>
>>> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
>>> exception occurred when fetching
>>> http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.
>>>
>>> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>>>
>>> org.apache.http.conn.ConnectTimeoutException: 

[Dev] [UUF] Failing remote debugging the code of UUF v1.0.0-m5

[Sudharma Subasinghe]

Hi,

I got following exception while loading the uuf app under remote debugging
mode. Also it deactivates the debug pointers after starting the debug mode.

[2016-05-27 10:12:48,206] ERROR {org.wso2.carbon.uuf.internal.UUFRegistry}
- A server occurred while serving for request '/bpmn-explorer/'.
org.wso2.carbon.uuf.exception.UUFException: Cannot reload app
'org.wso2.uuf.sample.bpmn-explorer'.
at
org.wso2.carbon.uuf.internal.UUFRegistry.lambda$reloadApp$15(UUFRegistry.java:158)
at
org.wso2.carbon.uuf.internal.UUFRegistry$$Lambda$113/1112994017.get(Unknown
Source)
at java.util.Optional.orElseThrow(Optional.java:290)
at
org.wso2.carbon.uuf.internal.UUFRegistry.reloadApp(UUFRegistry.java:158)
at org.wso2.carbon.uuf.internal.UUFRegistry.serve(UUFRegistry.java:99)
at
org.wso2.carbon.uuf.connector.ms.UUFMicroservice.execute(UUFMicroservice.java:105)
at
org.wso2.carbon.uuf.connector.ms.UUFMicroservice.get(UUFMicroservice.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:95)
at
org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:53)
at
org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:31)
at
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
at
io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:32)
at
io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:299)
at
io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:36)
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:110)
at
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)

Without remote debugging mode enabling, it loads apps successfully.

Without "Debugger.isDebuggingEnabled()" as in [1], it starts the debugging
successfully. But still gives the same exception.

I think, when debugging is enabled, reloading the requested app is not
properly working.

[1]
https://github.com/wso2/carbon-uuf/blob/v1.0.0-m5/uuf-core/src/main/java/org/wso2/carbon/uuf/internal/UUFRegistry.java#L98

Thanks
Sudharma




-- 
Sudharma Subasinghe,
Software Engineer,
WSO2 Inc.
Email: sudhar...@wso2.com 
Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Bhathiya Jayasekara]

+Ruwan

On Fri, May 27, 2016 at 10:20 AM, Megala Uthayakumar 
wrote:

> Hi,
> This fix is available in carbon-dashboards 1.0.17-SNAPSHOT. Is APIM 2.0.0
> SNAPSHOT uses the same version?
>
> Thanks.
>
> On Fri, May 27, 2016 at 10:02 AM, Deependra Ariyadewa 
> wrote:
>
>> This error still exists in the APIM 2.0.0 SNAPSHOT pack built on 26th May
>> 2016.
>>
>> On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar 
>> wrote:
>>
>>> Hi,
>>>
>>> We have moved the fix for the google connectivity problem with the
>>> commit [1].
>>>
>>> [1]
>>> https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Megala
>>>
>>> On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran 
>>> wrote:
>>>
 Hi Megala,

 Please check the shindig-server feature and try to remove the unwanted
 files from there it self, hence we can omit this behaviour.

 Thanks,
 Sinthuja.

 On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon 
 wrote:

> >>Can't we fix this during the shinding-server feature generation?
> +1
> So that every product using shindig does not have to unzip and zip the
> war file to fix it.
>
> Cheers,
> Ruwan
>
> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran <
> sinth...@wso2.com> wrote:
>
>> Hi Tanya,
>>
>> Can't we fix this during the shinding-server feature generation?
>>
>> Thanks,
>> Sinthuja.
>>
>> On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara 
>> wrote:
>>
>>> Adding Bhathiya.
>>>
>>> We got same exception yesterday in APIM as well. We will need to
>>> same thing for DS as well.
>>>
>>> Thanks,
>>> Harsha
>>>
>>> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon 
>>> wrote:
>>>
 Thanks Tanya for the information. We will follow the same as in DS.

 On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma <
 ta...@wso2.com> wrote:

> Hi Ruwan,
>
> Usually this error is thrown as shindig is trying to load some
> google analytics apis. So when there is no internet connection this 
> error
> can be observed.
> To get rid of this error we have to remove google related stuff
> from shindig features.txt file
>
> *features-extras/analytics/feature.xml*
> *features-extras/com.google.gadgets.analytics/feature.xml*
>
> But since we don't maintain a shindig fork, we can't do this from
> carbon-dashboards level. So in the Dashboard Server level we are 
> replacing
> the features.txt file with a file which doesn't have above 2 entries 
> [1].
> We'll have to do the same for apim analytics as well.
>
> [1]
> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>
> Thanks,
> Tanya
>
> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon 
> wrote:
>
>> Hi DS team,
>> I am getting the following error in APIM 2.0.0-SNAPSHOT which
>> integrate DS features. Any Idea why? can we not print those errors 
>> due to
>> outside dependencies?
>>
>> ---
>>
>> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
>> One of the two will be used. Which one is undefined.
>>
>> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
>> res:features/features.txt are loading.
>>
>> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being
>> used does not support secure parsing.
>>
>> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are
>> being reused.
>>
>> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
>> res:features-extras/features.txt are loading.
>>
>> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService
>> Starting polling event receivers
>>
>> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
>> exception occurred when fetching
>> http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.
>>
>> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>>
>> org.apache.http.conn.ConnectTimeoutException: Connect to
>> www.google-analytics.com:80 timed out
>>
>> at
>> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
>>
>> at
>> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>>

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Megala Uthayakumar]

Hi,
This fix is available in carbon-dashboards 1.0.17-SNAPSHOT. Is APIM 2.0.0
SNAPSHOT uses the same version?

Thanks.

On Fri, May 27, 2016 at 10:02 AM, Deependra Ariyadewa  wrote:

> This error still exists in the APIM 2.0.0 SNAPSHOT pack built on 26th May
> 2016.
>
> On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar 
> wrote:
>
>> Hi,
>>
>> We have moved the fix for the google connectivity problem with the commit
>> [1].
>>
>> [1]
>> https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb
>>
>> Thanks.
>>
>> Regards,
>> Megala
>>
>> On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran 
>> wrote:
>>
>>> Hi Megala,
>>>
>>> Please check the shindig-server feature and try to remove the unwanted
>>> files from there it self, hence we can omit this behaviour.
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon 
>>> wrote:
>>>
 >>Can't we fix this during the shinding-server feature generation?
 +1
 So that every product using shindig does not have to unzip and zip the
 war file to fix it.

 Cheers,
 Ruwan

 On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran  wrote:

> Hi Tanya,
>
> Can't we fix this during the shinding-server feature generation?
>
> Thanks,
> Sinthuja.
>
> On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara 
> wrote:
>
>> Adding Bhathiya.
>>
>> We got same exception yesterday in APIM as well. We will need to same
>> thing for DS as well.
>>
>> Thanks,
>> Harsha
>>
>> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon 
>> wrote:
>>
>>> Thanks Tanya for the information. We will follow the same as in DS.
>>>
>>> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma <
>>> ta...@wso2.com> wrote:
>>>
 Hi Ruwan,

 Usually this error is thrown as shindig is trying to load some
 google analytics apis. So when there is no internet connection this 
 error
 can be observed.
 To get rid of this error we have to remove google related stuff
 from shindig features.txt file

 *features-extras/analytics/feature.xml*
 *features-extras/com.google.gadgets.analytics/feature.xml*

 But since we don't maintain a shindig fork, we can't do this from
 carbon-dashboards level. So in the Dashboard Server level we are 
 replacing
 the features.txt file with a file which doesn't have above 2 entries 
 [1].
 We'll have to do the same for apim analytics as well.

 [1]
 https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e

 Thanks,
 Tanya

 On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon 
 wrote:

> Hi DS team,
> I am getting the following error in APIM 2.0.0-SNAPSHOT which
> integrate DS features. Any Idea why? can we not print those errors 
> due to
> outside dependencies?
>
> ---
>
> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
> One of the two will be used. Which one is undefined.
>
> [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
> res:features/features.txt are loading.
>
> [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being
> used does not support secure parsing.
>
> [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are
> being reused.
>
> [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
> res:features-extras/features.txt are loading.
>
> [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService
> Starting polling event receivers
>
> [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
> exception occurred when fetching
> http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.
>
> [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher
>
> org.apache.http.conn.ConnectTimeoutException: Connect to
> www.google-analytics.com:80 timed out
>
> at
> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
>
> at
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>
> at
> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>
> at
> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>
> 

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

[Susankha Nirmala]

On Thu, May 26, 2016 at 9:02 PM, Awanthika Senarath 
wrote:

> Hello Susankha,
>
> We cannot have those VM arguments in serverdefinition.xml as ESB 5.0.0
> which is based on carbon 4.4.1 has a different wso2carbon.sh which will not
> be able to start if we pass those VM arguments. So the option is to
> integrate a new server for carbon 4.4.1.
>

ESB 5.0.0 is using the Carbon Kernel version 4.4.5 and in the
"wso2server.sh" carbon file, it will check the Java version like below and
assign the values of the VM parameters to the "JVM_MEM_OPTS" variable,
according to the java version. Then use the "$JVM_MEM_OPTS" parameter in
the
system property section (refer [1])


if [ -z "$JVM_MEM_OPTS" ]; then
   java_version=$("$JAVACMD" -version 2>&1 | awk -F '"' '/version/ {print
$2}')
   JVM_MEM_OPTS="-Xms256m -Xmx1024m"
   if [ "$java_version" \< "1.8" ]; then
  JVM_MEM_OPTS="$JVM_MEM_OPTS -XX:MaxPermSize=256m"
   fi
fi

.

while [ "$status" = "$START_EXIT_STATUS" ]
do
$JAVACMD \
-Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
$JVM_MEM_OPTS \

Without creating a new server for ESB 5.0.0 (Carbon Kernel 4.4.5), we can
use the same CarbonServer44 component.
We can check the JAVA version and according to that, we can set the
relavent VM parameters.
I think that is the best way to handle this issue, without introduce a new
CarbonSever vertion inside the DevStudio.


[1]-
https://github.com/wso2/carbon-kernel/blob/v4.4.5/distribution/kernel/carbon-home/bin/wso2server.sh




>
>
>
> Regards
> Awanthika
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Fri, May 27, 2016 at 9:15 AM, Susankha Nirmala 
> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala 
>> wrote:
>>
>>>
>>>
>>> On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake 
>>> wrote:
>>>


 On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath  wrote:

> Hello Nuwan,
>
> Please find my comments inline,
>
> I have noticed following issues while testing.
>
>
> https://wso2.org/jira/browse/TOOLS-3412
>
> As I have mentioned before this is a OS specific issue which comes in
> Linux and not a blocker. We will attempt to fix this as we move on.
>
> https://wso2.org/jira/browse/TOOLS-3416
>

 Actually this issue happens only when the server is started in JDK 1.7
 if server runs on JDK 1.8 this issue won't be there , reason for this issue
 is ,  memory settings are defined in two different ways for JDK 7 and 8  in
 carbons server , So we have to find  a way to distinguish  these two
 settings inside the eclipse

>>>
>>>
>>> This error happens due to missing "-Xms256m -Xmx1024m -XX:
>>> MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
>>> is support for Java 1.7.0 and 1.8.0 (refer [3]).
>>> ESB 4.9.0 also supported for both Java versions and in the
>>> carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
>>> -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].
>>>
>>> With the Java 1.8, PermSize VM parameter not using, because in Java 8
>>> PermGen is replace with Metaspace. But we need to support Both Java
>>> versions (1.7 and 1.8).
>>> We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
>>> parameters and when we are starting server in Java 1.8.0 it will give the
>>> following warning, but continue the starting process.
>>>
>>> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>>> MaxPermSize=256m; support was removed in 8.0
>>>
>>> If you directly run ESB with Java 1.8.0, you can see above warning log.
>>> The best thing we can do is use the same VM parameters define in the
>>> wso2carbon.sh file in the carbon.definition.xml (that's what we have done
>>> with carbonserver 4.2 and that's why we can't see
>>> This issue, when starting ESB 4.9.0 with Java 1.7.0)
>>>
>>> [1]-
>>> https://github.com/wso2/devstudio-tooling-platform/blob/developer-studio-tooling-platform-4.1.0-beta2/plugins/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>>> [2]-
>>> https://github.com/wso2/devstudio-tooling-platform/blob/master/plugins/org.wso2.developerstudio.eclipse.carbonserver42/serverdefinition/carbon.definition.xml
>>> [3]- https://docs.wso2.com/display/ESB500/Installation+Prerequisites
>>>
>>> Thanks.
>>> /Susankha.
>>>
>>
>>
>> With the DevStudio 3.8.0 also we can run carbon44 servers and but there
>> we can see "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters ([1])
>>
>> [1]-
>> https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>>
>>
>>
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>

 Thanks and Regards
 /Jasintha

>
> We will look into this. It appears that 

[Dev] Missing required capability in osgi component

[Fathima Dilhasha]

Hi,

I'm trying to build an osgi component which uses "
*org.wso2.carbon.analytics.api.AnalyticsDataAPI*". When I add the bundle to
carbon server, the bundle is working as expected. But in the osgi console
when I diagnose the bundle I get the following.




*Direct constraints which are unresolved:Missing required capability
Require-Capability: osgi.service;
filter="(objectClass=org.wso2.carbon.analytics.api.AnalyticsDataAPI)"*
Following are the imported packages in the written osgi component.



org.apache.commons.logging.*; version="${commons.logging.version}",
org.osgi.service.component;
version="${imp.pkg.version.osgi.service.component}",
org.osgi.framework; version="${imp.pkg.version.osgi.framework}",
org.wso2.carbon.core; version="${wso2das.version}",
org.wso2.carbon.analytics.api.*; version=${wso2analytics.api.version},
org.wso2.carbon.analytics.datasource.commons.exception.*;
resolution:=optional



Following are the scr tags specified in the component.







*/** * @scr.component name="org.wso2.carbon.cloud.das.datapurge.tool"
* @scr.reference name="analytics.component"
interface="org.wso2.carbon.analytics.api.AnalyticsDataAPI" *
cardinality="1..1" policy="dynamic" bind="setAnalyticsDataAPI"
unbind="unsetAnalyticsDataAPI" */*

I highly appreciate any help on understandng this issue.

Thanks
Regards,
Dilhasha


-- 
Fathima Dilhasha
*Software Engineer*
Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
<%2B94%20%280%29%20773%20451194>
dilha...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Deependra Ariyadewa]

This error still exists in the APIM 2.0.0 SNAPSHOT pack built on 26th May
2016.

On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar 
wrote:

> Hi,
>
> We have moved the fix for the google connectivity problem with the commit
> [1].
>
> [1]
> https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb
>
> Thanks.
>
> Regards,
> Megala
>
> On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran 
> wrote:
>
>> Hi Megala,
>>
>> Please check the shindig-server feature and try to remove the unwanted
>> files from there it self, hence we can omit this behaviour.
>>
>> Thanks,
>> Sinthuja.
>>
>> On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon  wrote:
>>
>>> >>Can't we fix this during the shinding-server feature generation?
>>> +1
>>> So that every product using shindig does not have to unzip and zip the
>>> war file to fix it.
>>>
>>> Cheers,
>>> Ruwan
>>>
>>> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran 
>>> wrote:
>>>
 Hi Tanya,

 Can't we fix this during the shinding-server feature generation?

 Thanks,
 Sinthuja.

 On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara 
 wrote:

> Adding Bhathiya.
>
> We got same exception yesterday in APIM as well. We will need to same
> thing for DS as well.
>
> Thanks,
> Harsha
>
> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon 
> wrote:
>
>> Thanks Tanya for the information. We will follow the same as in DS.
>>
>> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma > > wrote:
>>
>>> Hi Ruwan,
>>>
>>> Usually this error is thrown as shindig is trying to load some
>>> google analytics apis. So when there is no internet connection this 
>>> error
>>> can be observed.
>>> To get rid of this error we have to remove google related stuff from
>>> shindig features.txt file
>>>
>>> *features-extras/analytics/feature.xml*
>>> *features-extras/com.google.gadgets.analytics/feature.xml*
>>>
>>> But since we don't maintain a shindig fork, we can't do this from
>>> carbon-dashboards level. So in the Dashboard Server level we are 
>>> replacing
>>> the features.txt file with a file which doesn't have above 2 entries 
>>> [1].
>>> We'll have to do the same for apim analytics as well.
>>>
>>> [1]
>>> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon 
>>> wrote:
>>>
 Hi DS team,
 I am getting the following error in APIM 2.0.0-SNAPSHOT which
 integrate DS features. Any Idea why? can we not print those errors due 
 to
 outside dependencies?

 ---

 achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
 One of the two will be used. Which one is undefined.

 [2016-05-17 17:35:49,176]  INFO - FeatureRegistry Resources from
 res:features/features.txt are loading.

 [2016-05-17 17:35:49,186]  INFO - XmlUtil The XML processor being
 used does not support secure parsing.

 [2016-05-17 17:35:49,187]  INFO - XmlUtil Document builders are
 being reused.

 [2016-05-17 17:35:49,396]  INFO - FeatureRegistry Resources from
 res:features-extras/features.txt are loading.

 [2016-05-17 17:36:11,707]  INFO - CarbonEventManagementService
 Starting polling event receivers

 [2016-05-17 17:36:19,510]  INFO - BasicHttpFetcher The following
 exception occurred when fetching
 http://www.google-analytics.com/urchin.js: 30,103 ms elapsed.

 [2016-05-17 17:36:19,511]  INFO - BasicHttpFetcher

 org.apache.http.conn.ConnectTimeoutException: Connect to
 www.google-analytics.com:80 timed out

 at
 org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)

 at
 org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)

 at
 org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)

 at
 org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)

 at
 org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)

 at
 org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)

 at
 org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)

Re: [Dev] Puppet modules are not compatible with puppet 4

[Akila Ravihansa Perera]

Hi Manuranga,

This is not exactly a Puppet issue, rather Vagrant provisioning we have
used is not compatible with Puppet 4. So the $subject is kind of misleading
:)
We will look into this issue and fix in the next release, if it needs
fixing. Please create a JIRA for this.

Regarding Puppet 4 compatibility, we haven't tested yet. But looking at the
deprecation list [1], I don't see any blockers. Please do raise if you
notice any issues with Puppet 4.

[1]
https://docs.puppet.com/puppet/3.8/reference/deprecated_language.html#in-puppet-40-1

Thanks.

On Thu, May 26, 2016 at 9:39 PM, Manuranga Perera  wrote:

> We are using non-environment puppet mode this is not compatible with
> puppet 4 [1]
>
> If manifests_path and manifest_file are specified without environments,
>> the old non-environment mode will be used (which will fail on Puppet 4+).
>> [2]
>
>
> Are we planing to update to be compatible with puppet 4?
>
> [1] https://github.com/mitchellh/vagrant/issues/5615
> [2] https://www.vagrantup.com/docs/provisioning/puppet_apply.html
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] Puppet modules are not compatible with puppet 4

[Imesh Gunaratne]

On Thu, May 26, 2016 at 9:39 PM, Manuranga Perera  wrote:

> We are using non-environment puppet mode this is not compatible with
> puppet 4 [1]
>
> If manifests_path and manifest_file are specified without environments,
>> the old non-environment mode will be used (which will fail on Puppet 4+).
>> [2]
>
>
> Are we planing to update to be compatible with puppet 4?
>

As I see this is not a compatibility issue in Puppet modules, rather this
is about the Vagrant Puppet plugin which is used for testing Puppet
modules. We may need to test this and update the Vagrant script in the next
release.

Did you see any issues in Puppet modules related to Puppet 4?

Thanks

>
> [1] https://github.com/mitchellh/vagrant/issues/5615
> [2] https://www.vagrantup.com/docs/provisioning/puppet_apply.html
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



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

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

[Awanthika Senarath]

Hello Susankha,

We cannot have those VM arguments in serverdefinition.xml as ESB 5.0.0
which is based on carbon 4.4.1 has a different wso2carbon.sh which will not
be able to start if we pass those VM arguments. So the option is to
integrate a new server for carbon 4.4.1.



Regards
Awanthika

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



On Fri, May 27, 2016 at 9:15 AM, Susankha Nirmala  wrote:

>
>
> On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala 
> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake 
>> wrote:
>>
>>>
>>>
>>> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath 
>>> wrote:
>>>
 Hello Nuwan,

 Please find my comments inline,

 I have noticed following issues while testing.


 https://wso2.org/jira/browse/TOOLS-3412

 As I have mentioned before this is a OS specific issue which comes in
 Linux and not a blocker. We will attempt to fix this as we move on.

 https://wso2.org/jira/browse/TOOLS-3416

>>>
>>> Actually this issue happens only when the server is started in JDK 1.7
>>> if server runs on JDK 1.8 this issue won't be there , reason for this issue
>>> is ,  memory settings are defined in two different ways for JDK 7 and 8  in
>>> carbons server , So we have to find  a way to distinguish  these two
>>> settings inside the eclipse
>>>
>>
>>
>> This error happens due to missing "-Xms256m -Xmx1024m -XX:
>> MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
>> is support for Java 1.7.0 and 1.8.0 (refer [3]).
>> ESB 4.9.0 also supported for both Java versions and in the
>> carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
>> -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].
>>
>> With the Java 1.8, PermSize VM parameter not using, because in Java 8
>> PermGen is replace with Metaspace. But we need to support Both Java
>> versions (1.7 and 1.8).
>> We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
>> parameters and when we are starting server in Java 1.8.0 it will give the
>> following warning, but continue the starting process.
>>
>> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>> MaxPermSize=256m; support was removed in 8.0
>>
>> If you directly run ESB with Java 1.8.0, you can see above warning log.
>> The best thing we can do is use the same VM parameters define in the
>> wso2carbon.sh file in the carbon.definition.xml (that's what we have done
>> with carbonserver 4.2 and that's why we can't see
>> This issue, when starting ESB 4.9.0 with Java 1.7.0)
>>
>> [1]-
>> https://github.com/wso2/devstudio-tooling-platform/blob/developer-studio-tooling-platform-4.1.0-beta2/plugins/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>> [2]-
>> https://github.com/wso2/devstudio-tooling-platform/blob/master/plugins/org.wso2.developerstudio.eclipse.carbonserver42/serverdefinition/carbon.definition.xml
>> [3]- https://docs.wso2.com/display/ESB500/Installation+Prerequisites
>>
>> Thanks.
>> /Susankha.
>>
>
>
> With the DevStudio 3.8.0 also we can run carbon44 servers and but there we
> can see "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters ([1])
>
> [1]-
> https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>
>
>
>
>>
>>
>>
>>
>>
>>
>>
>>>
>>> Thanks and Regards
>>> /Jasintha
>>>

 We will look into this. It appears that this is caused by a memory leak
 due to non heap-size setting[1] by the configurations.


 [1] https://github.com/spring-projects/spring-boot/issues/4376




 Regards
 Awanthika



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



 On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe 
 wrote:

> Hi All,
>
> I have tested the updater tool functionality including installing
> features and no major issues found
>
> @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.
>
> [1] https://wso2.org/jira/browse/TOOLS-3416
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela 
> wrote:
>
>> Hi All,
>>
>> I have noticed following issues while testing.
>> https://wso2.org/jira/browse/TOOLS-3412
>> https://wso2.org/jira/browse/TOOLS-3416
>>
>> Thanks,
>> Nuwan
>>
>> On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa <
>> heshit...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I have tested 

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

[Susankha Nirmala]

On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala  wrote:

>
>
> On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake 
> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath 
>> wrote:
>>
>>> Hello Nuwan,
>>>
>>> Please find my comments inline,
>>>
>>> I have noticed following issues while testing.
>>>
>>>
>>> https://wso2.org/jira/browse/TOOLS-3412
>>>
>>> As I have mentioned before this is a OS specific issue which comes in
>>> Linux and not a blocker. We will attempt to fix this as we move on.
>>>
>>> https://wso2.org/jira/browse/TOOLS-3416
>>>
>>
>> Actually this issue happens only when the server is started in JDK 1.7 if
>> server runs on JDK 1.8 this issue won't be there , reason for this issue is
>> ,  memory settings are defined in two different ways for JDK 7 and 8  in
>> carbons server , So we have to find  a way to distinguish  these two
>> settings inside the eclipse
>>
>
>
> This error happens due to missing "-Xms256m -Xmx1024m -XX:
> MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
> is support for Java 1.7.0 and 1.8.0 (refer [3]).
> ESB 4.9.0 also supported for both Java versions and in the
> carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
> -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].
>
> With the Java 1.8, PermSize VM parameter not using, because in Java 8
> PermGen is replace with Metaspace. But we need to support Both Java
> versions (1.7 and 1.8).
> We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
> parameters and when we are starting server in Java 1.8.0 it will give the
> following warning, but continue the starting process.
>
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> MaxPermSize=256m; support was removed in 8.0
>
> If you directly run ESB with Java 1.8.0, you can see above warning log.
> The best thing we can do is use the same VM parameters define in the
> wso2carbon.sh file in the carbon.definition.xml (that's what we have done
> with carbonserver 4.2 and that's why we can't see
> This issue, when starting ESB 4.9.0 with Java 1.7.0)
>
> [1]-
> https://github.com/wso2/devstudio-tooling-platform/blob/developer-studio-tooling-platform-4.1.0-beta2/plugins/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
> [2]-
> https://github.com/wso2/devstudio-tooling-platform/blob/master/plugins/org.wso2.developerstudio.eclipse.carbonserver42/serverdefinition/carbon.definition.xml
> [3]- https://docs.wso2.com/display/ESB500/Installation+Prerequisites
>
> Thanks.
> /Susankha.
>


With the DevStudio 3.8.0 also we can run carbon44 servers and but there we
can see "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters ([1])

[1]-
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml




>
>
>
>
>
>
>
>>
>> Thanks and Regards
>> /Jasintha
>>
>>>
>>> We will look into this. It appears that this is caused by a memory leak
>>> due to non heap-size setting[1] by the configurations.
>>>
>>>
>>> [1] https://github.com/spring-projects/spring-boot/issues/4376
>>>
>>>
>>>
>>>
>>> Regards
>>> Awanthika
>>>
>>>
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Hi All,

 I have tested the updater tool functionality including installing
 features and no major issues found

 @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.

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

 Sohani Weerasinghe
 Software Engineer
 WSO2, Inc: http://wso2.com

 Mobile  : +94 716439774
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine

 On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela 
 wrote:

> Hi All,
>
> I have noticed following issues while testing.
> https://wso2.org/jira/browse/TOOLS-3412
> https://wso2.org/jira/browse/TOOLS-3416
>
> Thanks,
> Nuwan
>
> On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa <
> heshit...@wso2.com> wrote:
>
>> Hi all,
>>
>> I have tested BPS Tooling with the new platform and no major issues
>> found.
>>
>> +1
>>
>> Thanks.
>>
>> On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya > > wrote:
>>
>>> Hi all,
>>>
>>> I have tested the project nature extension point and found no issues.
>>>
>>> +1
>>>
>>> Thanks,
>>> Maheeka
>>>
>>> Maheeka Jayasuriya
>>> Software Engineer
>>> Mobile : +9450661
>>>
>>> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath <
>>> awanth...@wso2.com> wrote:
>>>
 Hello Devs,

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

[Susankha Nirmala]

On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake 
wrote:

>
>
> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath 
> wrote:
>
>> Hello Nuwan,
>>
>> Please find my comments inline,
>>
>> I have noticed following issues while testing.
>>
>>
>> https://wso2.org/jira/browse/TOOLS-3412
>>
>> As I have mentioned before this is a OS specific issue which comes in
>> Linux and not a blocker. We will attempt to fix this as we move on.
>>
>> https://wso2.org/jira/browse/TOOLS-3416
>>
>
> Actually this issue happens only when the server is started in JDK 1.7 if
> server runs on JDK 1.8 this issue won't be there , reason for this issue is
> ,  memory settings are defined in two different ways for JDK 7 and 8  in
> carbons server , So we have to find  a way to distinguish  these two
> settings inside the eclipse
>


This error happens due to missing "-Xms256m -Xmx1024m -XX:
MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
is support for Java 1.7.0 and 1.8.0 (refer [3]).
ESB 4.9.0 also supported for both Java versions and in the
carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
-Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].

With the Java 1.8, PermSize VM parameter not using, because in Java 8
PermGen is replace with Metaspace. But we need to support Both Java
versions (1.7 and 1.8).
We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
parameters and when we are starting server in Java 1.8.0 it will give the
following warning, but continue the starting process.

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0

If you directly run ESB with Java 1.8.0, you can see above warning log.
The best thing we can do is use the same VM parameters define in the
wso2carbon.sh file in the carbon.definition.xml (that's what we have done
with carbonserver 4.2 and that's why we can't see
This issue, when starting ESB 4.9.0 with Java 1.7.0)

[1]-
https://github.com/wso2/devstudio-tooling-platform/blob/developer-studio-tooling-platform-4.1.0-beta2/plugins/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
[2]-
https://github.com/wso2/devstudio-tooling-platform/blob/master/plugins/org.wso2.developerstudio.eclipse.carbonserver42/serverdefinition/carbon.definition.xml
[3]- https://docs.wso2.com/display/ESB500/Installation+Prerequisites

Thanks.
/Susankha.







>
> Thanks and Regards
> /Jasintha
>
>>
>> We will look into this. It appears that this is caused by a memory leak
>> due to non heap-size setting[1] by the configurations.
>>
>>
>> [1] https://github.com/spring-projects/spring-boot/issues/4376
>>
>>
>>
>>
>> Regards
>> Awanthika
>>
>>
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the updater tool functionality including installing
>>> features and no major issues found
>>>
>>> @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.
>>>
>>> [1] https://wso2.org/jira/browse/TOOLS-3416
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela 
>>> wrote:
>>>
 Hi All,

 I have noticed following issues while testing.
 https://wso2.org/jira/browse/TOOLS-3412
 https://wso2.org/jira/browse/TOOLS-3416

 Thanks,
 Nuwan

 On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa  wrote:

> Hi all,
>
> I have tested BPS Tooling with the new platform and no major issues
> found.
>
> +1
>
> Thanks.
>
> On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
> wrote:
>
>> Hi all,
>>
>> I have tested the project nature extension point and found no issues.
>>
>> +1
>>
>> Thanks,
>> Maheeka
>>
>> Maheeka Jayasuriya
>> Software Engineer
>> Mobile : +9450661
>>
>> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath <
>> awanth...@wso2.com> wrote:
>>
>>> Hello Devs,
>>>
>>>
>>> We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio 
>>> Tooling
>>> for Platform 4.1.0.*
>>>
>>> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0
>>> is available here
>>> .
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> 
>>> .
>>>

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

[Jasintha Dasanayake]

On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath 
wrote:

> Hello Nuwan,
>
> Please find my comments inline,
>
> I have noticed following issues while testing.
>
>
> https://wso2.org/jira/browse/TOOLS-3412
>
> As I have mentioned before this is a OS specific issue which comes in
> Linux and not a blocker. We will attempt to fix this as we move on.
>
> https://wso2.org/jira/browse/TOOLS-3416
>

Actually this issue happens only when the server is started in JDK 1.7 if
server runs on JDK 1.8 this issue won't be there , reason for this issue is
,  memory settings are defined in two different ways for JDK 7 and 8  in
carbons server , So we have to find  a way to distinguish  these two
settings inside the eclipse

Thanks and Regards
/Jasintha

>
> We will look into this. It appears that this is caused by a memory leak
> due to non heap-size setting[1] by the configurations.
>
>
> [1] https://github.com/spring-projects/spring-boot/issues/4376
>
>
>
>
> Regards
> Awanthika
>
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> I have tested the updater tool functionality including installing
>> features and no major issues found
>>
>> @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.
>>
>> [1] https://wso2.org/jira/browse/TOOLS-3416
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela  wrote:
>>
>>> Hi All,
>>>
>>> I have noticed following issues while testing.
>>> https://wso2.org/jira/browse/TOOLS-3412
>>> https://wso2.org/jira/browse/TOOLS-3416
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa 
>>> wrote:
>>>
 Hi all,

 I have tested BPS Tooling with the new platform and no major issues
 found.

 +1

 Thanks.

 On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
 wrote:

> Hi all,
>
> I have tested the project nature extension point and found no issues.
>
> +1
>
> Thanks,
> Maheeka
>
> Maheeka Jayasuriya
> Software Engineer
> Mobile : +9450661
>
> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath <
> awanth...@wso2.com> wrote:
>
>> Hello Devs,
>>
>>
>> We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio 
>> Tooling
>> for Platform 4.1.0.*
>>
>> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
>> available here
>> .
>>  Source
>> and Tag Location to be voted upon is available here
>> 
>> .
>>
>> Developer Studio 4.1.0  Tooling for Platform is released on Developer
>> Studio kernel 4.1.0
>> Developer Studio Kernel contains a single feature which has the
>> bundles that are required to implement WSO2 specific product tooling on
>> Eclipse.
>>
>>- This release contains Developer Studio migration to Eclipse mars
>>- Improvements in the Developer Studio Updater tool for automatic
>>updates
>>
>>
>>
>>1. [+] Stable - go ahead and release
>>2. [-]  Broken - do not release (please explain why)
>>
>>
>> The platform could to be tested on top of Developer Studio Kernel
>> with compatible tooling SNAPSHOT versions available at [1].
>>
>>
>> [1]
>> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>>
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> ___
>> 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
>
>


 --
 Heshitha Hettihewa
 *Software Engineer*
 Mobile : +94716866386
 <%2B94%20%280%29%20773%20451194>
 heshit...@wso2.com

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


>>>
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Tharindu Edirisinghe]

Hi Asantha,

Glad to hear the progress... Sure I'll review over the weekend and provide
feedback. By next week we'll have a hangout to discuss on how to move
forward and the difficulties you have faced.  Keep the momentum going !

Regards,
TharinduE

On Fri, May 27, 2016 at 12:17 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> i been able to fix the mongodb user store intitalizing error now it
> working successfully it will be registered as a secondary user store in IS
> and when going to add a new users and roles it will show the domain of
> mongodb userstore still i having small issues in my json query formats for
> mongodb i fixing those issues at the moment all the progress so far i made
> updated to my github repository[1] and i recently updated my blog[2] as
> well,can you review my code and give me a feedback?
>
> [1]https://github.com/asanthamax/mongodbuserstore
> [2]http://asanthamax.blogspot.com/
>
> Thanks,
> Asantha
>
> On Sun, May 22, 2016 at 3:38 PM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> I have override all the methods in AbstractUserStoreManager in my
>> MongoDBUserStoreManager class after that when i try to add new secondary
>> user store in management console i got following error i attached the
>> screen shot of the error with this mail
>> i have pushed all the progress upto now to my github repository[1]
>> can you give me some tips to solve this issue?
>> any suggestion would be grateful
>> [1] https://github.com/asanthamax/mongodbuserstore
>> Thanks,
>> Asantha
>>
>> On Thu, May 19, 2016 at 11:47 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> sorry for the late reply ,as you advised i remove the scr reference and
>>> its corresponding methods from user store now it's works fine but i having
>>> another small issue if i wanted to run my mongodb user store as as my
>>> primary user store how would i do that?
>>> i added my user store configurations to user-mgt.xml file and comented
>>> the ldap userstore properties and i added MongoDBUserStore to
>>> tenant-mgt.xml as well but then i get error as datasource cannot be casted
>>> to MongoDB db source while deploying thats mean its still referring to
>>> Default Activator inside carbon core module how would i set it to my
>>> activator to reffer?
>>> any suggestion or help would be grateful
>>> Thanks,
>>> Asantha
>>>
>>> On Wed, May 18, 2016 at 10:29 PM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asantha,

 Great progress so far !

 Since the reference is given to realm service in the bundle activator,
 you should be facing the issue. Can you remove the service reference from
 the bundle activator class. (You can delete the following from the class).

 * @scr.reference name="user.realmservice.default"
  * interface="org.wso2.carbon.user.core.service.RealmService"
 cardinality="1..1"
  * policy="dynamic" bind="setRealmService"
  * unbind="unsetRealmService"

 Also delete the following methods where realm service is used.

 getRealmService()
 setRealmService(RealmService rlmService)
 unsetRealmService(RealmService rlmService)

 After that can you try if the userstore manager is working as expected.
 If you face any issues, please get back.

 Thank you,
 TharinduE






 On Sun, May 15, 2016 at 7:48 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> I found the issue after debugging into my code ,my service bundle is
> not get activated because i referring into mongodb-driver which is not 
> osgi
> comaptible and i just found another library in here[1] and it is worked 
> for
> me ,fixed project i pushed into my github repository [2].
> i found out that *DefaultRealmService* which is used in Bundle
> Activator of JDBCUserstoreManager cannot be used for MongoDB since it used
> *java.sql.DataSource*.
> Is their having any DataSource class like that for MongoDB? or would i
> have to create a different logic to implement that scenario in MongoDB?
> waiting for your suggestion
>
> [1].
> http://central.maven.org/maven2/org/mongodb/mongo-java-driver/3.2.2/
> [2]. https://github.com/asanthamax/mongodbuserstore
> Thanks,
> Asantha
>
> On Sat, May 14, 2016 at 10:53 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> i faced following issue while i developing ,
>> after adding my new json query support i didn't able to see My
>> MongoDBUserStore in dropdown in create user store option.
>> for json related activites i used an external json dependency from
>> here[1] and i added it jar to lib folder in IS as well,i have enabled
>> remote debugging and inspect my code and there i found in my 
>> 

Re: [Dev] ESB Enrich Mediator Issue with JSON array

[Godwin Shrimal]

Hi Shafreen,

Solve the issue by copying the payload using following. But I think there
is a issue in the JSON Builder as i discussed you.




Thanks Vijitha and Jagath for helping me to sort out this issue.


Thanks
Godwin



On Tue, May 24, 2016 at 6:56 AM, Shafreen Anfar  wrote:

> Hi Godwin,
>
> In that case, we have a problem. So usually what we do is adding the below
> xml instruction just before the element that has to be represented as an
> array. For instance let's say you have an element name foo and want to
> represent that as an array. You can do the following. For more info see [1].
>
> 
> 
> 
> 
>
> [1] https://docs.wso2.com/display/ESB480/JSON+Support
> 
>
>
> On Tue, May 24, 2016 at 5:17 PM, Godwin Shrimal  wrote:
>
>> Hi Shafreen,
>>
>> Yes. This is JSON array.
>>
>>
>> Thanks
>> Godwin
>>
>>
>> On Tue, May 24, 2016 at 6:22 AM, Shafreen Anfar 
>> wrote:
>>
>>> Hi Godwin,
>>>
>>> On Mon, May 23, 2016 at 9:05 PM, Godwin Shrimal  wrote:
>>>
 Hi All,

 I used Enrich Mediator to copy the original payload as follows.

 

 

 

 

 Incoming JSON payload has multi-value attribute, But when multi-value
 attribute has only one value, Enrich mediator convert the JSON payload it
 as a single value attribute. Is this a known issue or do we have any work
 around for this ?

>>>
>>> When you say multi-value attribute do you mean json arrays ?
>>>
>>>


 Thanks
 Godwin



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

 mobile: *+94772264165*
 linkedin: *http://lnkd.in/KUum6D *
 twitter: https://twitter.com/godwinamila

>>>
>>>
>>>
>>> --
>>> Regards,
>>> *Shafreen*
>>> Software Engineer
>>> WSO2 Inc
>>> Mobile : 077-556-395-1
>>>
>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>>
>
>
>
> --
> Regards,
> *Shafreen*
> Software Engineer
> WSO2 Inc
> Mobile : 077-556-395-1
>



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

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

Re: [Dev] [DEV] [CEP] MySQL table storage engine and character set used with Output Mysql Event Adaptor

[Lasantha Fernando]

Hi Thanuja,

Were you able to resolve the issue after changing the charset and engine?
Also can you specify the MySQL connector version that you were using?

@Mohan, we did a debug session and what we could observe was that the
encoding was set to windows-1252 as I remember. The main issue here was
that there is a logic in MySQL adapter to retrieve the data type of each
column and we map these types to our databridge data types. However, all
non-string data types were returning the value -1, instead of assigned data
type number for BIGINT, INT etc. We were thinking since it was returning
different or incorrect values, this was due to charset mismatch or engine
mismatch.

Relevant code is under initializeTableInfo() in [1]

[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/event-stream/event-output-adaptor/org.wso2.carbon.event.output.adaptor.mysql/1.0.1/src/main/java/org/wso2/carbon/event/output/adaptor/mysql/MysqlEventAdaptorType.java

Thanks,
Lasantha

On 27 May 2016 at 00:38, Mohanadarshan Vivekanandalingam 
wrote:

>
>
> On Fri, May 27, 2016 at 12:17 AM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi ,
>>
>> Do we need to set the MySQL *storage engine* as '*MyISAM*' and *character
>> set *to* utf8* for the tables created by the CEP Output MySQL Event
>> Adaptors?
>>
>> I'm using CEP 3.0.0/3.1.0 with MySQL server version *5.6.30*. If I don't
>> set those, by default storage engine is set to *InnoDB* and character
>> set is set to *latin1 *and events are not persisted in the table. Once I
>> change those as said above, events are persisted in the table.
>>
>>
> No, it is not a requirement..
>
> I am using MySQL server version 5.6.28.. Tried with InnoDB engine and
> latin1 charset and it is working fine.. Have you checked data format that
> you tried to insert ?
>
> Thanks,
> Mohan
>
>
>
>> Thanks.
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Lasantha Fernando*
Senior Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: lasan...@wso2.com
mobile: (+94) 71 5247551
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [CEP] MySQL table storage engine and character set used with Output Mysql Event Adaptor

[Mohanadarshan Vivekanandalingam]

On Fri, May 27, 2016 at 12:17 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi ,
>
> Do we need to set the MySQL *storage engine* as '*MyISAM*' and *character
> set *to* utf8* for the tables created by the CEP Output MySQL Event
> Adaptors?
>
> I'm using CEP 3.0.0/3.1.0 with MySQL server version *5.6.30*. If I don't
> set those, by default storage engine is set to *InnoDB* and character set
> is set to *latin1 *and events are not persisted in the table. Once I
> change those as said above, events are persisted in the table.
>
>
No, it is not a requirement..

I am using MySQL server version 5.6.28.. Tried with InnoDB engine and
latin1 charset and it is working fine.. Have you checked data format that
you tried to insert ?

Thanks,
Mohan



> Thanks.
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Asantha Thilina]

Hi Tharindu,

i been able to fix the mongodb user store intitalizing error now it working
successfully it will be registered as a secondary user store in IS and when
going to add a new users and roles it will show the domain of mongodb
userstore still i having small issues in my json query formats for mongodb
i fixing those issues at the moment all the progress so far i made updated
to my github repository[1] and i recently updated my blog[2] as well,can
you review my code and give me a feedback?

[1]https://github.com/asanthamax/mongodbuserstore
[2]http://asanthamax.blogspot.com/

Thanks,
Asantha

On Sun, May 22, 2016 at 3:38 PM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> I have override all the methods in AbstractUserStoreManager in my
> MongoDBUserStoreManager class after that when i try to add new secondary
> user store in management console i got following error i attached the
> screen shot of the error with this mail
> i have pushed all the progress upto now to my github repository[1]
> can you give me some tips to solve this issue?
> any suggestion would be grateful
> [1] https://github.com/asanthamax/mongodbuserstore
> Thanks,
> Asantha
>
> On Thu, May 19, 2016 at 11:47 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> sorry for the late reply ,as you advised i remove the scr reference and
>> its corresponding methods from user store now it's works fine but i having
>> another small issue if i wanted to run my mongodb user store as as my
>> primary user store how would i do that?
>> i added my user store configurations to user-mgt.xml file and comented
>> the ldap userstore properties and i added MongoDBUserStore to
>> tenant-mgt.xml as well but then i get error as datasource cannot be casted
>> to MongoDB db source while deploying thats mean its still referring to
>> Default Activator inside carbon core module how would i set it to my
>> activator to reffer?
>> any suggestion or help would be grateful
>> Thanks,
>> Asantha
>>
>> On Wed, May 18, 2016 at 10:29 PM, Tharindu Edirisinghe <
>> tharin...@wso2.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> Great progress so far !
>>>
>>> Since the reference is given to realm service in the bundle activator,
>>> you should be facing the issue. Can you remove the service reference from
>>> the bundle activator class. (You can delete the following from the class).
>>>
>>> * @scr.reference name="user.realmservice.default"
>>>  * interface="org.wso2.carbon.user.core.service.RealmService"
>>> cardinality="1..1"
>>>  * policy="dynamic" bind="setRealmService"
>>>  * unbind="unsetRealmService"
>>>
>>> Also delete the following methods where realm service is used.
>>>
>>> getRealmService()
>>> setRealmService(RealmService rlmService)
>>> unsetRealmService(RealmService rlmService)
>>>
>>> After that can you try if the userstore manager is working as expected.
>>> If you face any issues, please get back.
>>>
>>> Thank you,
>>> TharinduE
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sun, May 15, 2016 at 7:48 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 I found the issue after debugging into my code ,my service bundle is
 not get activated because i referring into mongodb-driver which is not osgi
 comaptible and i just found another library in here[1] and it is worked for
 me ,fixed project i pushed into my github repository [2].
 i found out that *DefaultRealmService* which is used in Bundle
 Activator of JDBCUserstoreManager cannot be used for MongoDB since it used
 *java.sql.DataSource*.
 Is their having any DataSource class like that for MongoDB? or would i
 have to create a different logic to implement that scenario in MongoDB?
 waiting for your suggestion

 [1].
 http://central.maven.org/maven2/org/mongodb/mongo-java-driver/3.2.2/
 [2]. https://github.com/asanthamax/mongodbuserstore
 Thanks,
 Asantha

 On Sat, May 14, 2016 at 10:53 AM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> i faced following issue while i developing ,
> after adding my new json query support i didn't able to see My
> MongoDBUserStore in dropdown in create user store option.
> for json related activites i used an external json dependency from
> here[1] and i added it jar to lib folder in IS as well,i have enabled
> remote debugging and inspect my code and there i found in my 
> *MongoDBUserStoreDSComponent
> *class *activate *method triggered but execute 1st line of code only.
> it will not registered the service but in my osgi console window when
> i run *ss mongo* command i get monodb.userstore bundle and mongodb
> java driver bundle are activated successfully i attached my console output
> and identity server output for your consideration as well
> any suggestion would be grateful
>
> [1]. 

[Dev] [DEV] [CEP] MySQL table storage engine and character set used with Output Mysql Event Adaptor

[Thanuja Uruththirakodeeswaran]

Hi ,

Do we need to set the MySQL *storage engine* as '*MyISAM*' and *character
set *to* utf8* for the tables created by the CEP Output MySQL Event
Adaptors?

I'm using CEP 3.0.0/3.1.0 with MySQL server version *5.6.30*. If I don't
set those, by default storage engine is set to *InnoDB* and character set
is set to *latin1 *and events are not persisted in the table. Once I change
those as said above, events are persisted in the table.

Thanks.

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

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

[Dev] Puppet modules are not compatible with puppet 4

[Manuranga Perera]

We are using non-environment puppet mode this is not compatible with puppet
4 [1]

If manifests_path and manifest_file are specified without environments, the
> old non-environment mode will be used (which will fail on Puppet 4+). [2]


Are we planing to update to be compatible with puppet 4?

[1] https://github.com/mitchellh/vagrant/issues/5615
[2] https://www.vagrantup.com/docs/provisioning/puppet_apply.html
-- 
With regards,
*Manu*ranga Perera.

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

Re: [Dev] [UUF] Pet store sample not working without last forwards slash

[SajithAR Ariyarathna]

>
> But cannot be accessed with "http://127.0.0.1:8080/pets-store; (with the
> missing forward slash at the end). I get a "Cannot find an app for
> context 'null'." message on the browser.
>
This is a bug. When URL is "http://127.0.0.1:8080/pets-store;, then URI
becomes "/pets-store". UUF assumes an URI has at least 02 slashes [1].
Will fix this.

[1]
https://github.com/wso2/carbon-uuf/blob/v1.0.0-m5/uuf-core/src/main/java/org/wso2/carbon/uuf/internal/util/RequestUtil.java#L51

On Thu, May 26, 2016 at 7:26 PM, Manuranga Perera  wrote:

> it was working on old release
> https://github.com/wso2/carbon-uuf/blob/v1.0.0-m2/uuf-core/src/main/java/org/wso2/carbon/uuf/UUFRegistry.java#L82
> but some how it has been removed in new, we should add it back
>
> On Thu, May 26, 2016 at 9:17 AM, Sudharma Subasinghe 
> wrote:
>
>> Hi Hemika,
>>
>> I faced the same problem. I think, it is because the implementation says
>> "An URI must end with a slash."
>>
>> [1]
>> https://github.com/wso2/carbon-uuf/blob/v1.0.0-m5/uuf-core/src/main/java/org/wso2/carbon/uuf/internal/util/RequestUtil.java#L29
>>
>> On Thu, May 26, 2016 at 6:39 PM, Manuranga Perera  wrote:
>>
>>> Actually without slash one should redirect to the other , that's what
>>> tomcat does
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sudharma Subasinghe,
>> Software Engineer,
>> WSO2 Inc.
>> Email: sudhar...@wso2.com 
>> Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Vagrent from puppet modules startup error

[Manuranga Perera]

Hi,
Solved by adding a git attribute file.

# sh scripts must have unix line endings to work
*.erb text eol=lf

I'll send a PR later.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Carbon Caching] Caching won't work for objects from different bundles without dynamic imports

[Jayanga Kaushalya]

Hi,

As per $subject if we want to cache a object from a different bundle other
than carbon-caching, it will fail while giving a ClassNotFoundException in
the deserialize() [1]. This can be overcome by enabling dynamic imports.

[1]
https://github.com/wso2/carbon-caching/blob/master/component/src/main/java/org/wso2/carbon/caching/internal/SerializingInternalConverter.java#L141

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

Re: [Dev] [UUF] Pet store sample not working without last forwards slash

[Manuranga Perera]

it was working on old release
https://github.com/wso2/carbon-uuf/blob/v1.0.0-m2/uuf-core/src/main/java/org/wso2/carbon/uuf/UUFRegistry.java#L82
but some how it has been removed in new, we should add it back

On Thu, May 26, 2016 at 9:17 AM, Sudharma Subasinghe 
wrote:

> Hi Hemika,
>
> I faced the same problem. I think, it is because the implementation says
> "An URI must end with a slash."
>
> [1]
> https://github.com/wso2/carbon-uuf/blob/v1.0.0-m5/uuf-core/src/main/java/org/wso2/carbon/uuf/internal/util/RequestUtil.java#L29
>
> On Thu, May 26, 2016 at 6:39 PM, Manuranga Perera  wrote:
>
>> Actually without slash one should redirect to the other , that's what
>> tomcat does
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sudharma Subasinghe,
> Software Engineer,
> WSO2 Inc.
> Email: sudhar...@wso2.com 
> Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
With regards,
*Manu*ranga Perera.

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

Re: [Dev] [UUF] Pet store sample not working without last forwards slash

[Sudharma Subasinghe]

Hi Hemika,

I faced the same problem. I think, it is because the implementation says
"An URI must end with a slash."

[1]
https://github.com/wso2/carbon-uuf/blob/v1.0.0-m5/uuf-core/src/main/java/org/wso2/carbon/uuf/internal/util/RequestUtil.java#L29

On Thu, May 26, 2016 at 6:39 PM, Manuranga Perera  wrote:

> Actually without slash one should redirect to the other , that's what
> tomcat does
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sudharma Subasinghe,
Software Engineer,
WSO2 Inc.
Email: sudhar...@wso2.com 
Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Pet store sample not working without last forwards slash

[Manuranga Perera]

Actually without slash one should redirect to the other , that's what
tomcat does
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Pet store sample not working without last forwards slash

[Hemika Kodikara]

IMO, ideally yes.

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

Mobile : +9477762

On Thu, May 26, 2016 at 5:40 PM, Ramith Jayasinghe  wrote:

> I think in both cases the app should load in the browser?
>
> On Thu, May 26, 2016 at 5:31 PM, Hemika Kodikara  wrote:
> > Hi All,
> >
> > The pets-store can be accessed with "http://127.0.0.1:8080/pets-store/;
> >
> > But cannot be accessed with "http://127.0.0.1:8080/pets-store; (with the
> > missing forward slash at the end). I get a "Cannot find an app for
> context
> > 'null'." message on the browser.
> >
> > Also a small suggestion - Can we show the URLs of the apps deployed on
> the
> > console when the server startsup. IMO, it will help out the users in user
> > experience wise.
> >
> > Regards,
> > Hemika
> >
> > Hemika Kodikara
> > Software Engineer
> > WSO2 Inc.
> > lean . enterprise . middleware
> > http://wso2.com
> >
> > Mobile : +9477762
> >
> > ___
> > Dev mailing list
> > Dev@wso2.org
> > http://wso2.org/cgi-bin/mailman/listinfo/dev
> >
>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 772534930
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Pet store sample not working without last forwards slash

[Ramith Jayasinghe]

I think in both cases the app should load in the browser?

On Thu, May 26, 2016 at 5:31 PM, Hemika Kodikara  wrote:
> Hi All,
>
> The pets-store can be accessed with "http://127.0.0.1:8080/pets-store/;
>
> But cannot be accessed with "http://127.0.0.1:8080/pets-store; (with the
> missing forward slash at the end). I get a "Cannot find an app for context
> 'null'." message on the browser.
>
> Also a small suggestion - Can we show the URLs of the apps deployed on the
> console when the server startsup. IMO, it will help out the users in user
> experience wise.
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



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

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

[Dev] [UUF] Pet store sample not working without last forwards slash

[Hemika Kodikara]

Hi All,

The pets-store can be accessed with "http://127.0.0.1:8080/pets-store/;

But cannot be accessed with "http://127.0.0.1:8080/pets-store; (with the
missing forward slash at the end). I get a "Cannot find an app for context
'null'." message on the browser.

Also a small suggestion - Can we show the URLs of the apps deployed on the
console when the server startsup. IMO, it will help out the users in user
experience wise.

Regards,
Hemika

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

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

Re: [Dev] Reading headers/form fields of a multipart/form-data request in msf4j

[Thusitha Thilina Dayaratne]

Hi All,

I started looking into implementing FormParam support for MSF4J. AFAIU we
need to support below content types

   1. application/x-www-form-urlencoded
   2. multpart/form-data

For the *application/x-www-form-urlencoded *
This is pretty much similar to the QueryParam. We can read the Request body
and get the encoded string and process that as a key-value pair.

For the *multpart/form-data*
We can implement the multpart/form-data support to cater requests like file
upload.
Rather than decoding multipart content by ourselves we can use a
multipart/form-data parsing library to parse the raw HTTP body. Following
apache libraries can be used for this purpose

   1. Apache Clerezza [1]
   2. Apache Commons-Fileupload [2]

As discussed in early in the thread we can't use Commons-Fileupload out of
the box to cater our requirements. But we can get the code and modify the
to tally with our implementation and work on the FormParam implementation.

[1] - https://clerezza.apache.org/
[2] - https://commons.apache.org/proper/commons-fileupload/

Thanks

On Wed, May 11, 2016 at 11:31 AM, Samiyuru Senarathne 
wrote:

> When I was looking into form processing in MSF4J, I was looking at
> modifying apache commons [1][2] to meet our needs since it has multipart
> support and it is widely used with servlets. But IMO we wont be able to use
> it directly out of the box as a library to parse the byte buffer we have
> because it starts processing from a servlet request object.
>
> [1] - https://commons.apache.org/proper/commons-fileupload/using.html
> [2] - https://commons.apache.org/proper/commons-fileupload/streaming.html
>
> On Wed, May 11, 2016 at 11:18 AM, Himasha Guruge 
> wrote:
>
>> In C4 we have used [1] for this purpose.
>>
>> [1] http://cxf.apache.org/docs/jax-rs-multiparts.html
>>
>> On Wed, May 11, 2016 at 11:12 AM, Afkham Azeez  wrote:
>>
>>> Any libraries you are familiar with? Since BPS folks are using the code
>>> from the MSF4J master branch, we may be able to quickly implement it.
>>>
>>> On Wed, May 11, 2016 at 11:09 AM, Samiyuru Senarathne >> > wrote:
>>>
 Hi Azeez,

 Yes I looked at this sometime back. But it was not progressed to the
 implementation level.

 For the moment we will have to use a multipart/form-data parsing
 library to parse the raw HTTP body. We can get the raw HTTP body by
 injecting an org.wso2.msf4j.Request object to the resource method using
 @Context annotation.

 Best Regards,
 Samiyuru

 On Wed, May 11, 2016 at 11:02 AM, Afkham Azeez  wrote:

> Samiyuru,
> You looked at this some time back right? What work is involved in
> implementing this?
>
> Azeez
>
> On Wed, May 11, 2016 at 11:00 AM, Himasha Guruge 
> wrote:
>
>> From the offline discussion with Azeez, it seems that this is not
>> supported in current msf4j implementation. How are we to proceed with the
>> use case of acquiring form field values from the request?
>>
>>
>>
>> On Wed, Apr 6, 2016 at 11:22 AM, Himasha Guruge 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have gone through the available sample [1]  on how to process a
>>> stream and read and save files in msf4j. However given a request with 
>>> form
>>> fields like [2] , how can we retrieve those form fields in msf4j? If it 
>>> is
>>> to read from the stream itself, any suggested way to do this?
>>>
>>> [1]
>>> https://github.com/wso2/msf4j/blob/652435ee7f8fdf31307667adb888e9a13513f6d8/samples/petstore/microservices/fileserver/src/main/java/org/wso2/msf4j/examples/petstore/fileserver/FileServerService.java
>>>
>>> [2] curl --form
>>> "fileupload=@Desktop/bigdot.png;filename=desired-filename.txt" --form
>>> param1=value1 --form param2=value2
>>> http://localhost:8080/bps/repo/stream
>>>
>>> Thanks,
>>>
>>> Himasha Guruge
>>> *Software Engineer*
>>> WS*O2* *Inc.*
>>> Mobile: +94 777459299
>>> himas...@wso2.com
>>>
>>
>>
>>
>> --
>> Himasha Guruge
>> *Software Engineer*
>> WS*O2* *Inc.*
>> Mobile: +94 777459299
>> himas...@wso2.com
>>
>> ___
>> 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...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: 

Re: [Dev] Contributing to WSO2 Open Source Projects.

[Malaka Silva]

Hi Pawan,

Glad to hear you are interested. You can contact us using dev@wso2.org or
architect...@wso2.org mails. You will find some information on steps to
follow with [1] and [2]

You can also visit our office or discuss via hangout if anything is needed.

[1]
https://docs.wso2.com/display/ESBCONNECTORS/Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Connector+Store
[2]
https://docs.wso2.com/display/ISCONNECTORS/Creating+a+Third+Party+Authenticator+or+Connector+and+Publishing+in+WSO2+Store

On Thu, May 26, 2016 at 3:19 PM, Keerthika Mahendralingam <
keerth...@wso2.com> wrote:

> Hi Pawan,
>
> As we discussed we can have the discussion today evening at Jaffna office.
> Malaka and Kesavan will join.
>
>
> Thanks,
> Keerthika.
>
> On Thu, May 26, 2016 at 3:07 PM, Pawan Nayanajith 
> wrote:
>
>> Hi all,
>>
>> We are a group of 3rd year undergraduate students following Computer
>> Science at  University of Jaffna. And we are supposed to built an Open
>> Source project for our course unit CSC305GC2- Rapid Application Development
>> within a year. And for this we have decided to contribute to a WSO2
>> product.Therefore for we wish you will guide us to begin the  project and
>> you will help us to make it a success.So we are expecting a good reply form
>> you and we wish to know the procedure how we should start our project.
>>
>> Our group members are as follows
>>
>> 1. J.A. Pawan Nayanajith Madushanka
>>  -djnayanaj...@gmail.com
>>
>> 2. Logeshwaran Praveenath
>>  -
>> logeshwaranpraveen...@gmail.com
>>
>> 3. D.M.Salitha Prasad Disanayaka -salith...@gmail.com
>>
>> Thank you.
>>
>
>
>
> --
> 
> Keerthika Mahendralingam
> Associate Software Engineer
> Mobile :+94 (0) 776 121144
> keerth...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>



-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/

https://store.wso2.com/store/

Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why do we have gmail and gmailRest connector?

[Malaka Silva]

+1 Latest connector only support all the integration use cases and seamless
refresh token logic. No point keeping the the previous one since this is
done at early stage.

On Thu, May 26, 2016 at 2:38 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi,
>
> Currently we have two connector for gmail operations with ESB [1]
>
> gmail connector was implemented by using sdk and the gmailRest connector
> has implemented using REST api and gmailRest connector has more methods
> than gmail connector and has released with input and output schema as well.
>
> Use cases covered by gmail is already covered with gmailRest in addition
> to new methods.
>
> Can we deprecate the gmail connector?
>
> [1] - https://store.wso2.com/store/assets/esbconnector/?query=gmail
>
> --
>
>
> *Thank you and Regards**Hariprasath Thanarajah*
> Associate Software Engineer | WSO2
> E: haripras...@wso2.com
> M: +94752806528, 0777216903
>
>


-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/

https://store.wso2.com/store/

Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Contributing to WSO2 Open Source Projects.

[Keerthika Mahendralingam]

Hi Pawan,

As we discussed we can have the discussion today evening at Jaffna office.
Malaka and Kesavan will join.


Thanks,
Keerthika.

On Thu, May 26, 2016 at 3:07 PM, Pawan Nayanajith 
wrote:

> Hi all,
>
> We are a group of 3rd year undergraduate students following Computer
> Science at  University of Jaffna. And we are supposed to built an Open
> Source project for our course unit CSC305GC2- Rapid Application Development
> within a year. And for this we have decided to contribute to a WSO2
> product.Therefore for we wish you will guide us to begin the  project and
> you will help us to make it a success.So we are expecting a good reply form
> you and we wish to know the procedure how we should start our project.
>
> Our group members are as follows
>
> 1. J.A. Pawan Nayanajith Madushanka
>  -djnayanaj...@gmail.com
>
> 2. Logeshwaran Praveenath
>  -
> logeshwaranpraveen...@gmail.com
>
> 3. D.M.Salitha Prasad Disanayaka -salith...@gmail.com
>
> Thank you.
>



-- 

Keerthika Mahendralingam
Associate Software Engineer
Mobile :+94 (0) 776 121144
keerth...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: GSOC2016: [ML][CEP] Predictive analytic with online data for WSO2 Machine Learner

[Mahesh Dananjaya]

Hi Maheshakya,
today i got the siddhi and debug the math extention. then did some changes
and check. Now i am trying to write same kind of extension in my code base.
so i add dependencies and it was built fine. Now i am trying to debug my
extension and i did the same thing as i did in previous case. Cep is
sending data, bu my extension is not firing in relevant break point.
1. So how can i debug the siddhi extension in my new extension.(you can see
it in my example repoo)

I think if i do it correctly we can built the extension for our purpose.
And i will send the relevant timing report of SGD algorithms very soon as
supun was asking me. thank you.
regards,
Mahesh.

On Tue, May 24, 2016 at 11:07 AM, Maheshakya Wijewardena <
mahesha...@wso2.com> wrote:

> Also note that there is a calculation interval in the siddhi time series
> regression function[1]. You maybe able get some insight for this from that
> as well.
>
> [1] https://docs.wso2.com/display/CEP400/Regression
>
> On Tue, May 24, 2016 at 11:03 AM, Maheshakya Wijewardena <
> mahesha...@wso2.com> wrote:
>
>> Hi Mahesh,
>>
>> As we discussed offline, we can use similar mechanism to train linear
>> regression models, logistic regression models and k-means clustering models.
>>
>> It is very interesting that i have found that somethings that can make
>>> use of our work. In the cep 4.0 documentation there is a Custom Stream
>>> Processor Extention program [1]. There is a example of
>>> LinearRegressionStreamProcessor [1].
>>>
>>
>> As we have to train predictive models with Spark, you can write wrappers
>> around regression/clustering models of Spark. Refer to Siddhi time series
>> regression source codes[1][2]. You can write a streaming linear regression
>> class for ML in a similar fashion by wrapping Spark mllib implementations.
>> You can use the methods "addEvent", "removeEvent", etc. (may have to be
>> changed according to requirements) for the similar purpose. You can
>> introduce trainLinearRegression/LogisticRegression/Kmeans which does a
>> similar thing as in createLinearRegression in those time series functions.
>> In the processData method you can use Spark mllib classes to actually train
>> models and return the model weights, evaluation metrics. So, converting
>> streams into RDDs and retrieving information from the trained models shall
>> happen in this method.
>>
>> In the stream processor extension example, you can retrieve those values
>> then use them to train new models with new batches. Weights/cluster centers
>> maybe passed as initialization parameters for the wrappers.
>>
>> Please note that we have to figure out the best siddhi extension type for
>> this process. In the siddhi query, we define batch size, type of algorithm
>> and number of features (there can be more). After batch size number of
>> events received, train a model and save parameters, return evaluation
>> metric. With the next batch, retrain the model initialized with previously
>> learned parameters.
>>
>> We also may need to test the same scenario with a moving window, but I
>> suspect that that approach may become so slow as a model is trained each
>> time an event is received. So, we may have to change the number of slots
>> the moving window moves at a time (eg: not one by one, but ten by ten).
>>
>> Once this is resolved, majority of the research part will be finished and
>> all we will be left to do is implementing wrappers around the 3 learning
>> algorithms we consider.
>>
>> Best regards.
>>
>> [1]
>> https://github.com/wso2/siddhi/blob/master/modules/siddhi-extensions/timeseries/src/main/java/org/wso2/siddhi/extension/timeseries/linreg/RegressionCalculator.java
>> [2]
>> https://github.com/wso2/siddhi/blob/master/modules/siddhi-extensions/timeseries/src/main/java/org/wso2/siddhi/extension/timeseries/linreg/SimpleLinearRegressionCalculator.java
>>
>>
>> On Sat, May 21, 2016 at 2:55 PM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>> Hi Maheshkya,
>>> shall we use [1] for our work? i am checking the possibility.
>>> BR,
>>> Mahesh.
>>> [1]
>>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension
>>> [2]
>>> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
>>> [3]
>>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
>>>
>>> On Sat, May 21, 2016 at 2:44 PM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi Maheshakya,
 It is very interesting that i have found that somethings that can make
 use of our work. In the cep 4.0 documentation there is a Custom Stream
 Processor Extention program [1]. There is a example of
 LinearRegressionStreamProcessor [1] and also i saw
  private int batchSize = 10; i am going through this one.
 Please check whether we can use. WIll there be any compatibility or
 support issue?
 regards,
 Mahesh.


 [1]
 

Re: [Dev] [UUF] Referring correspond client side .Js script with Handlebars template

[Sudharma Subasinghe]

Thank you for the response.

On Thu, May 26, 2016 at 2:21 PM, Hemika Kodikara  wrote:

> Hi Rasika/SajithAR,
>
> Thanks for the explanation.
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Thu, May 26, 2016 at 2:19 PM, Rasika Perera  wrote:
>
>> Hi Hemika,
>>
>> {{#headOther}} is a block helper. This allows you to add anything between
>>  tags. For instance;
>>
>> {{#headOther}}
>> 
>> {{/headOther}}
>>
>> You can use this helper whenever other helpers "title, css, headJs" is
>> not sufficient.
>>
>> On Thu, May 26, 2016 at 2:07 PM, Hemika Kodikara  wrote:
>>
>>> Hi SajithAR,
>>>
>>> What kind of implementations/uses can be done through the {{#headOther}} 
>>> placeholder
>>> ?
>>>
>>> Regards,
>>> Hemika
>>>
>>> Hemika Kodikara
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middleware
>>> http://wso2.com
>>>
>>> Mobile : +9477762
>>>
>>> On Thu, May 26, 2016 at 2:04 PM, SajithAR Ariyarathna >> > wrote:
>>>
 We changed names of some Handlebars helpers to make them short whilst
 being self-descriptive. I have updated the description of 1.0.0-M5 release
 [1], please refer it.

 [1] https://github.com/wso2/carbon-uuf/releases/tag/v1.0.0-m5

 Thanks.

 On Thu, May 26, 2016 at 1:42 PM, Hemika Kodikara 
 wrote:

> Hi Sudharma,
>
> It seems they have been changed [1]. Can you try with "headJs" instead
> of "headerJs".
>
> [1] -
> https://github.com/wso2/carbon-uuf/commit/2f95a6cd27604f033268bbd4dd807c75d993b18a
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Thu, May 26, 2016 at 1:12 PM, Sudharma Subasinghe <
> sudhar...@wso2.com> wrote:
>
>> Hi,
>>
>> I successfully loaded client side .Js script with Handlebars template
>> with 1.0.0-M4 release. I used the approach as following in the
>> "process-details.hbs" template.
>>
>> {{headerJs "/js/process-details.js"}}
>>
>> Now I am getting following exception for the same approach with 1.0.0-M5 
>> release.
>>
>> [2016-05-26 12:49:27,353] ERROR 
>> {org.wso2.carbon.uuf.internal.UUFRegistry} - An unexpected error 
>> occurred while serving for request '/bpmn-explorer/bpmn/process'. 
>> com.github.jknack.handlebars.HandlebarsException: 
>> components/root/fragments/process-details/process-details.hbs:1:2: 
>> java.lang.IllegalArgumentException: Cannot evaluate the variable/helper 
>> 'headerJs'.
>> components/root/fragments/process-details/process-details.hbs:1:2
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.MissingHelper.apply(MissingHelper.java:36)
>>  at 
>> com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
>>  at 
>> com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:100)
>>  at 
>> org.wso2.carbon.uuf.handlebars.renderable.HbsFragmentRenderable.render(HbsFragmentRenderable.java:79)
>>  at org.wso2.carbon.uuf.core.Fragment.render(Fragment.java:50)
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:59)
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:38)
>>  at 
>> com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
>>  at com.github.jknack.handlebars.Options.apply(Options.java:538)
>>  at com.github.jknack.handlebars.Options.fn(Options.java:433)
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:37)
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:27)
>>  at com.github.jknack.handlebars.internal.Block.merge(Block.java:210)
>>  at 
>> 

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Dilshani Subasinghe]

Hi Nuwan,

Thank you for your response. I tried with both


*java.naming.provider.url=failover:tcp://localhost:61616, and *


*java.naming.provider.url=failover:(tcp://localhost:61616).*
But still missing messages.

Regards,
Dilshani


On Thu, May 26, 2016 at 2:15 PM, Nuwan Wimalasekara  wrote:

> Hi Dilshani,
>
>
> On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe 
> wrote:
>
>> Hi Nuwan,
>>
>> Yes I configured jms url with failover. Actually I used failover syntax
>> as u asked me to change
>> (java.naming.provider.url=failover:(tcp://localhost:61616) or
>>  java.naming.provider.url=failover:tcp://localhost:61616)
>>
>> Proxy config:
>>
>> > uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> *java.naming.provider.url=failover:tcp://localhost:61616*
>> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>>
>
>
>>
>> I'm really sorry I didn't get your suggestion. Can you point out the
>> error within my config?
>>
> The problem in your config is , that there is no '*,*'  at the end of the
> url.
> It should be as bellow.
>
> *java.naming.provider.url=failover:tcp://localhost:61616,*
>
> New Config:
>  uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> *java.naming.provider.url=failover:tcp://localhost:61616,*
> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>
> Thanks,
> Nuwanw
>
>
>
>> Regards,
>> Dilshani
>>
>>
>> On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara 
>> wrote:
>>
>>> Hi Dilshani,
>>>
>>>  In your proxy config, you have defined a jms url with failover. Can you
>>> please try the failover url syntax as one of bellow. I think it is due to
>>> invalid url definition of failover for ActiveMQ.
>>>
>>> Please refer[1] for failover url syntax in ActiveMQ
>>>
>>> java.naming.provider.url=failover:(tcp://localhost:61616) or
>>>  java.naming.provider.url=failover:tcp://localhost:61616,
>>>
>>> [1] http://activemq.apache.org/failover-transport-reference.html
>>>
>>> Thanks,
>>> Nuwanw
>>>
>>> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe >> > wrote:
>>>
 Hi ESB Team,

 I am testing JMS parameters and identified scenario of missing messages
 when using "transport.Transactionality" parameter.

 Configured axis2.xml as follows;

   >>> class="org.apache.axis2.transport.jms.JMSListener">
 
 >>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
 >>> locked="false">failover:tcp://localhost:61616
 >>> name="transport.jms.ConnectionFactoryJNDIName"
 locked="false">TopicConnectionFactory
 >>> locked="false">topic
 >>> locked="false">topic

 * >>> locked="false">local>>> name="transport.jms.SessionTransacted" locked="false">true*
 

 
 >>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
 >>> locked="false">failover:tcp://localhost:61616
 >>> name="transport.jms.ConnectionFactoryJNDIName"
 locked="false">QueueConnectionFactory
 >>> locked="false">queue

 * >>> locked="false">local>>> name="transport.jms.SessionTransacted" locked="false">true*
 

 
 >>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
 >>> locked="false">failover:tcp://localhost:61616
 >>> name="transport.jms.ConnectionFactoryJNDIName"
 locked="false">TopicConnectionFactory
 >>> locked="false">topic
 >>> locked="false">topic

 *  >>> locked="false">local>>> name="transport.jms.SessionTransacted" locked="false">true*
 
 

 And aslo added same parameters to JMS sender too.

   >>> class="org.apache.axis2.transport.jms.JMSSender">

 >>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
 >>> locked="false">failover:tcp://localhost:61616
 >>> name="transport.jms.ConnectionFactoryJNDIName"
 locked="false">TopicConnectionFactory
 >>> locked="false">topic
 >>> locked="false">topic

 *>>> locked="false">local>>> name="transport.jms.SessionTransacted" locked="false">true*
 

 
 >>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
 >>> 

[Dev] Why do we have gmail and gmailRest connector?

[Hariprasath Thanarajah]

Hi,

Currently we have two connector for gmail operations with ESB [1]

gmail connector was implemented by using sdk and the gmailRest connector
has implemented using REST api and gmailRest connector has more methods
than gmail connector and has released with input and output schema as well.

Use cases covered by gmail is already covered with gmailRest in addition to
new methods.

Can we deprecate the gmail connector?

[1] - https://store.wso2.com/store/assets/esbconnector/?query=gmail

-- 


*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528, 0777216903
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Referring correspond client side .Js script with Handlebars template

[Rasika Perera]

Hi Hemika,

{{#headOther}} is a block helper. This allows you to add anything between
 tags. For instance;

{{#headOther}}

{{/headOther}}

You can use this helper whenever other helpers "title, css, headJs" is not
sufficient.

On Thu, May 26, 2016 at 2:07 PM, Hemika Kodikara  wrote:

> Hi SajithAR,
>
> What kind of implementations/uses can be done through the {{#headOther}} 
> placeholder
> ?
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Thu, May 26, 2016 at 2:04 PM, SajithAR Ariyarathna 
> wrote:
>
>> We changed names of some Handlebars helpers to make them short whilst
>> being self-descriptive. I have updated the description of 1.0.0-M5 release
>> [1], please refer it.
>>
>> [1] https://github.com/wso2/carbon-uuf/releases/tag/v1.0.0-m5
>>
>> Thanks.
>>
>> On Thu, May 26, 2016 at 1:42 PM, Hemika Kodikara  wrote:
>>
>>> Hi Sudharma,
>>>
>>> It seems they have been changed [1]. Can you try with "headJs" instead
>>> of "headerJs".
>>>
>>> [1] -
>>> https://github.com/wso2/carbon-uuf/commit/2f95a6cd27604f033268bbd4dd807c75d993b18a
>>>
>>> Regards,
>>> Hemika
>>>
>>> Hemika Kodikara
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middleware
>>> http://wso2.com
>>>
>>> Mobile : +9477762
>>>
>>> On Thu, May 26, 2016 at 1:12 PM, Sudharma Subasinghe >> > wrote:
>>>
 Hi,

 I successfully loaded client side .Js script with Handlebars template
 with 1.0.0-M4 release. I used the approach as following in the
 "process-details.hbs" template.

 {{headerJs "/js/process-details.js"}}

 Now I am getting following exception for the same approach with 1.0.0-M5 
 release.

 [2016-05-26 12:49:27,353] ERROR {org.wso2.carbon.uuf.internal.UUFRegistry} 
 - An unexpected error occurred while serving for request 
 '/bpmn-explorer/bpmn/process'. 
 com.github.jknack.handlebars.HandlebarsException: 
 components/root/fragments/process-details/process-details.hbs:1:2: 
 java.lang.IllegalArgumentException: Cannot evaluate the variable/helper 
 'headerJs'.
 components/root/fragments/process-details/process-details.hbs:1:2
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.MissingHelper.apply(MissingHelper.java:36)
at 
 com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
at 
 com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:100)
at 
 org.wso2.carbon.uuf.handlebars.renderable.HbsFragmentRenderable.render(HbsFragmentRenderable.java:79)
at org.wso2.carbon.uuf.core.Fragment.render(Fragment.java:50)
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:59)
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:38)
at 
 com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
at com.github.jknack.handlebars.Options.apply(Options.java:538)
at com.github.jknack.handlebars.Options.fn(Options.java:433)
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:37)
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:27)
at com.github.jknack.handlebars.internal.Block.merge(Block.java:210)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:86)
at 
 org.wso2.carbon.uuf.handlebars.renderable.HbsPageRenderable.render(HbsPageRenderable.java:82)
at org.wso2.carbon.uuf.core.Page.render(Page.java:48)
at org.wso2.carbon.uuf.core.Component.renderPage(Component.java:89)
at 

Re: [Dev] [UUF] Referring correspond client side .Js script with Handlebars template

[SajithAR Ariyarathna]

Hi Hemika,

Anything except title, CSS, JS, & favicon[1] that goes in the page's 
section can be added using the {{#headOther}} block helper.
e.g. Adding some  tags.

{{#headOther}}





{{/headOther}}

[1] favicon helper {{favicon "path/to/favicon/image.png"}} will be
available in the next milestone.

Thanks.

On Thu, May 26, 2016 at 2:07 PM, Hemika Kodikara  wrote:

> Hi SajithAR,
>
> What kind of implementations/uses can be done through the {{#headOther}} 
> placeholder
> ?
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Thu, May 26, 2016 at 2:04 PM, SajithAR Ariyarathna 
> wrote:
>
>> We changed names of some Handlebars helpers to make them short whilst
>> being self-descriptive. I have updated the description of 1.0.0-M5 release
>> [1], please refer it.
>>
>> [1] https://github.com/wso2/carbon-uuf/releases/tag/v1.0.0-m5
>>
>> Thanks.
>>
>> On Thu, May 26, 2016 at 1:42 PM, Hemika Kodikara  wrote:
>>
>>> Hi Sudharma,
>>>
>>> It seems they have been changed [1]. Can you try with "headJs" instead
>>> of "headerJs".
>>>
>>> [1] -
>>> https://github.com/wso2/carbon-uuf/commit/2f95a6cd27604f033268bbd4dd807c75d993b18a
>>>
>>> Regards,
>>> Hemika
>>>
>>> Hemika Kodikara
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middleware
>>> http://wso2.com
>>>
>>> Mobile : +9477762
>>>
>>> On Thu, May 26, 2016 at 1:12 PM, Sudharma Subasinghe >> > wrote:
>>>
 Hi,

 I successfully loaded client side .Js script with Handlebars template
 with 1.0.0-M4 release. I used the approach as following in the
 "process-details.hbs" template.

 {{headerJs "/js/process-details.js"}}

 Now I am getting following exception for the same approach with 1.0.0-M5 
 release.

 [2016-05-26 12:49:27,353] ERROR {org.wso2.carbon.uuf.internal.UUFRegistry} 
 - An unexpected error occurred while serving for request 
 '/bpmn-explorer/bpmn/process'. 
 com.github.jknack.handlebars.HandlebarsException: 
 components/root/fragments/process-details/process-details.hbs:1:2: 
 java.lang.IllegalArgumentException: Cannot evaluate the variable/helper 
 'headerJs'.
 components/root/fragments/process-details/process-details.hbs:1:2
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.MissingHelper.apply(MissingHelper.java:36)
at 
 com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
at 
 com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:100)
at 
 org.wso2.carbon.uuf.handlebars.renderable.HbsFragmentRenderable.render(HbsFragmentRenderable.java:79)
at org.wso2.carbon.uuf.core.Fragment.render(Fragment.java:50)
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:59)
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:38)
at 
 com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
at com.github.jknack.handlebars.Options.apply(Options.java:538)
at com.github.jknack.handlebars.Options.fn(Options.java:433)
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:37)
at 
 org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:27)
at com.github.jknack.handlebars.internal.Block.merge(Block.java:210)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
 com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
 com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:86)
at 
 org.wso2.carbon.uuf.handlebars.renderable.HbsPageRenderable.render(HbsPageRenderable.java:82)
at org.wso2.carbon.uuf.core.Page.render(Page.java:48)
at 

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Nuwan Wimalasekara]

Hi Dilshani,


On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe 
wrote:

> Hi Nuwan,
>
> Yes I configured jms url with failover. Actually I used failover syntax as
> u asked me to change
> (java.naming.provider.url=failover:(tcp://localhost:61616) or
>  java.naming.provider.url=failover:tcp://localhost:61616)
>
> Proxy config:
>
>  uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> *java.naming.provider.url=failover:tcp://localhost:61616*
> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>


>
> I'm really sorry I didn't get your suggestion. Can you point out the error
> within my config?
>
The problem in your config is , that there is no '*,*'  at the end of the
url.
It should be as bellow.

*java.naming.provider.url=failover:tcp://localhost:61616,*

New Config:


Thanks,
Nuwanw



> Regards,
> Dilshani
>
>
> On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Dilshani,
>>
>>  In your proxy config, you have defined a jms url with failover. Can you
>> please try the failover url syntax as one of bellow. I think it is due to
>> invalid url definition of failover for ActiveMQ.
>>
>> Please refer[1] for failover url syntax in ActiveMQ
>>
>> java.naming.provider.url=failover:(tcp://localhost:61616) or
>>  java.naming.provider.url=failover:tcp://localhost:61616,
>>
>> [1] http://activemq.apache.org/failover-transport-reference.html
>>
>> Thanks,
>> Nuwanw
>>
>> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi ESB Team,
>>>
>>> I am testing JMS parameters and identified scenario of missing messages
>>> when using "transport.Transactionality" parameter.
>>>
>>> Configured axis2.xml as follows;
>>>
>>>   >> class="org.apache.axis2.transport.jms.JMSListener">
>>> 
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">TopicConnectionFactory
>>> >> locked="false">topic
>>> >> locked="false">topic
>>>
>>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true*
>>> 
>>>
>>> 
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">QueueConnectionFactory
>>> >> locked="false">queue
>>>
>>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true*
>>> 
>>>
>>> 
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">TopicConnectionFactory
>>> >> locked="false">topic
>>> >> locked="false">topic
>>>
>>> *  >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true*
>>> 
>>> 
>>>
>>> And aslo added same parameters to JMS sender too.
>>>
>>>   >> class="org.apache.axis2.transport.jms.JMSSender">
>>>
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">TopicConnectionFactory
>>> >> locked="false">topic
>>> >> locked="false">topic
>>>
>>> *>> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true*
>>> 
>>>
>>> 
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">QueueConnectionFactory
>>> >> locked="false">queue
>>>
>>>
>>> *>> locked="false">local>> name="transport.jms.SessionTransacted"
>>> locked="false">true*
>>>  
>>>
>>>
>>>- Used activeMQ as JMS broker
>>>- I used the scenario of "ESB as Both a JMS Producer and Consumer"
>>>[1]
>>>- When testing that used external publisher to send messages to JMS
>>>queue
>>>
>>> *Results:*
>>>
>>>- *Messages will be missing when consuming through ESB.*(It may
>>>publish 1 messages to jms queue and only get around 100 or less 
>>> number
>>>of messages through ESB)
>>>
>>> *Further identifications:*
>>>
>>>  

Re: [Dev] [UUF] Referring correspond client side .Js script with Handlebars template

[Hemika Kodikara]

Hi SajithAR,

What kind of implementations/uses can be done through the
{{#headOther}} placeholder
?

Regards,
Hemika

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

Mobile : +9477762

On Thu, May 26, 2016 at 2:04 PM, SajithAR Ariyarathna 
wrote:

> We changed names of some Handlebars helpers to make them short whilst
> being self-descriptive. I have updated the description of 1.0.0-M5 release
> [1], please refer it.
>
> [1] https://github.com/wso2/carbon-uuf/releases/tag/v1.0.0-m5
>
> Thanks.
>
> On Thu, May 26, 2016 at 1:42 PM, Hemika Kodikara  wrote:
>
>> Hi Sudharma,
>>
>> It seems they have been changed [1]. Can you try with "headJs" instead of
>> "headerJs".
>>
>> [1] -
>> https://github.com/wso2/carbon-uuf/commit/2f95a6cd27604f033268bbd4dd807c75d993b18a
>>
>> Regards,
>> Hemika
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>> On Thu, May 26, 2016 at 1:12 PM, Sudharma Subasinghe 
>> wrote:
>>
>>> Hi,
>>>
>>> I successfully loaded client side .Js script with Handlebars template
>>> with 1.0.0-M4 release. I used the approach as following in the
>>> "process-details.hbs" template.
>>>
>>> {{headerJs "/js/process-details.js"}}
>>>
>>> Now I am getting following exception for the same approach with 1.0.0-M5 
>>> release.
>>>
>>> [2016-05-26 12:49:27,353] ERROR {org.wso2.carbon.uuf.internal.UUFRegistry} 
>>> - An unexpected error occurred while serving for request 
>>> '/bpmn-explorer/bpmn/process'. 
>>> com.github.jknack.handlebars.HandlebarsException: 
>>> components/root/fragments/process-details/process-details.hbs:1:2: 
>>> java.lang.IllegalArgumentException: Cannot evaluate the variable/helper 
>>> 'headerJs'.
>>> components/root/fragments/process-details/process-details.hbs:1:2
>>> at 
>>> org.wso2.carbon.uuf.handlebars.helpers.runtime.MissingHelper.apply(MissingHelper.java:36)
>>> at 
>>> com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
>>> at 
>>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>> at 
>>> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>>> at 
>>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>> at 
>>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
>>> at 
>>> com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:100)
>>> at 
>>> org.wso2.carbon.uuf.handlebars.renderable.HbsFragmentRenderable.render(HbsFragmentRenderable.java:79)
>>> at org.wso2.carbon.uuf.core.Fragment.render(Fragment.java:50)
>>> at 
>>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:59)
>>> at 
>>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:38)
>>> at 
>>> com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
>>> at 
>>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>> at 
>>> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>>> at 
>>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>> at 
>>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
>>> at com.github.jknack.handlebars.Options.apply(Options.java:538)
>>> at com.github.jknack.handlebars.Options.fn(Options.java:433)
>>> at 
>>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:37)
>>> at 
>>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:27)
>>> at com.github.jknack.handlebars.internal.Block.merge(Block.java:210)
>>> at 
>>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>> at 
>>> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>>> at 
>>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>> at 
>>> com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:86)
>>> at 
>>> org.wso2.carbon.uuf.handlebars.renderable.HbsPageRenderable.render(HbsPageRenderable.java:82)
>>> at org.wso2.carbon.uuf.core.Page.render(Page.java:48)
>>> at org.wso2.carbon.uuf.core.Component.renderPage(Component.java:89)
>>> at org.wso2.carbon.uuf.core.App.renderPage(App.java:85)
>>> at org.wso2.carbon.uuf.internal.UUFRegistry.serve(UUFRegistry.java:113)
>>> at 
>>> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.execute(UUFMicroservice.java:105)
>>> at 
>>> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.get(UUFMicroservice.java:93)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at 
>>> 

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Nuwan Wimalasekara]

Hi Dilshani,

Can you please try below endpoint config and  see whether all the messages
are delivering properly.



Thanks,
Nuwanw

On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe 
wrote:

> Hi Nuwan,
>
> Yes I configured jms url with failover. Actually I used failover syntax as
> u asked me to change
> (java.naming.provider.url=failover:(tcp://localhost:61616) or
>  java.naming.provider.url=failover:tcp://localhost:61616)
>
> Proxy config:
>
>  uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
> *java.naming.provider.url=failover:tcp://localhost:61616*
> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/>
>
> I'm really sorry I didn't get your suggestion. Can you point out the error
> within my config?
>
> Regards,
> Dilshani
>
>
> On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Dilshani,
>>
>>  In your proxy config, you have defined a jms url with failover. Can you
>> please try the failover url syntax as one of bellow. I think it is due to
>> invalid url definition of failover for ActiveMQ.
>>
>> Please refer[1] for failover url syntax in ActiveMQ
>>
>> java.naming.provider.url=failover:(tcp://localhost:61616) or
>>  java.naming.provider.url=failover:tcp://localhost:61616,
>>
>> [1] http://activemq.apache.org/failover-transport-reference.html
>>
>> Thanks,
>> Nuwanw
>>
>> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi ESB Team,
>>>
>>> I am testing JMS parameters and identified scenario of missing messages
>>> when using "transport.Transactionality" parameter.
>>>
>>> Configured axis2.xml as follows;
>>>
>>>   >> class="org.apache.axis2.transport.jms.JMSListener">
>>> 
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">TopicConnectionFactory
>>> >> locked="false">topic
>>> >> locked="false">topic
>>>
>>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true*
>>> 
>>>
>>> 
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">QueueConnectionFactory
>>> >> locked="false">queue
>>>
>>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true*
>>> 
>>>
>>> 
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">TopicConnectionFactory
>>> >> locked="false">topic
>>> >> locked="false">topic
>>>
>>> *  >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true*
>>> 
>>> 
>>>
>>> And aslo added same parameters to JMS sender too.
>>>
>>>   >> class="org.apache.axis2.transport.jms.JMSSender">
>>>
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">TopicConnectionFactory
>>> >> locked="false">topic
>>> >> locked="false">topic
>>>
>>> *>> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true*
>>> 
>>>
>>> 
>>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>> >> locked="false">failover:tcp://localhost:61616
>>> >> name="transport.jms.ConnectionFactoryJNDIName"
>>> locked="false">QueueConnectionFactory
>>> >> locked="false">queue
>>>
>>>
>>> *>> locked="false">local>> name="transport.jms.SessionTransacted"
>>> locked="false">true*
>>>  
>>>
>>>
>>>- Used activeMQ as JMS broker
>>>- I used the scenario of "ESB as Both a JMS Producer and Consumer"
>>>[1]
>>>- When testing that used external publisher to send messages to JMS
>>>queue
>>>
>>> *Results:*
>>>
>>>- *Messages will be missing when consuming through ESB.*(It may
>>>publish 1 messages to jms queue and only get around 100 or less 
>>> number
>>>of messages through ESB)
>>>
>>> *Further identifications:*
>>>
>>>- *Tried with inbound endpoints. It works properly.*
>>>
>>> *Attachments:*
>>>

Re: [Dev] [UUF] Referring correspond client side .Js script with Handlebars template

[SajithAR Ariyarathna]

We changed names of some Handlebars helpers to make them short whilst being
self-descriptive. I have updated the description of 1.0.0-M5 release [1],
please refer it.

[1] https://github.com/wso2/carbon-uuf/releases/tag/v1.0.0-m5

Thanks.

On Thu, May 26, 2016 at 1:42 PM, Hemika Kodikara  wrote:

> Hi Sudharma,
>
> It seems they have been changed [1]. Can you try with "headJs" instead of
> "headerJs".
>
> [1] -
> https://github.com/wso2/carbon-uuf/commit/2f95a6cd27604f033268bbd4dd807c75d993b18a
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Thu, May 26, 2016 at 1:12 PM, Sudharma Subasinghe 
> wrote:
>
>> Hi,
>>
>> I successfully loaded client side .Js script with Handlebars template
>> with 1.0.0-M4 release. I used the approach as following in the
>> "process-details.hbs" template.
>>
>> {{headerJs "/js/process-details.js"}}
>>
>> Now I am getting following exception for the same approach with 1.0.0-M5 
>> release.
>>
>> [2016-05-26 12:49:27,353] ERROR {org.wso2.carbon.uuf.internal.UUFRegistry} - 
>> An unexpected error occurred while serving for request 
>> '/bpmn-explorer/bpmn/process'. 
>> com.github.jknack.handlebars.HandlebarsException: 
>> components/root/fragments/process-details/process-details.hbs:1:2: 
>> java.lang.IllegalArgumentException: Cannot evaluate the variable/helper 
>> 'headerJs'.
>> components/root/fragments/process-details/process-details.hbs:1:2
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.MissingHelper.apply(MissingHelper.java:36)
>>  at 
>> com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
>>  at 
>> com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:100)
>>  at 
>> org.wso2.carbon.uuf.handlebars.renderable.HbsFragmentRenderable.render(HbsFragmentRenderable.java:79)
>>  at org.wso2.carbon.uuf.core.Fragment.render(Fragment.java:50)
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:59)
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:38)
>>  at 
>> com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
>>  at com.github.jknack.handlebars.Options.apply(Options.java:538)
>>  at com.github.jknack.handlebars.Options.fn(Options.java:433)
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:37)
>>  at 
>> org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:27)
>>  at com.github.jknack.handlebars.internal.Block.merge(Block.java:210)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>>  at 
>> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>>  at 
>> com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:86)
>>  at 
>> org.wso2.carbon.uuf.handlebars.renderable.HbsPageRenderable.render(HbsPageRenderable.java:82)
>>  at org.wso2.carbon.uuf.core.Page.render(Page.java:48)
>>  at org.wso2.carbon.uuf.core.Component.renderPage(Component.java:89)
>>  at org.wso2.carbon.uuf.core.App.renderPage(App.java:85)
>>  at org.wso2.carbon.uuf.internal.UUFRegistry.serve(UUFRegistry.java:113)
>>  at 
>> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.execute(UUFMicroservice.java:105)
>>  at 
>> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.get(UUFMicroservice.java:93)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>  at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>  at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  at java.lang.reflect.Method.invoke(Method.java:497)
>>  at 
>> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:95)
>>  at 
>> 

Re: [Dev] [UUF] Referring correspond client side .Js script with Handlebars template

[Hemika Kodikara]

Hi Sudharma,

It seems they have been changed [1]. Can you try with "headJs" instead of
"headerJs".

[1] -
https://github.com/wso2/carbon-uuf/commit/2f95a6cd27604f033268bbd4dd807c75d993b18a

Regards,
Hemika

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

Mobile : +9477762

On Thu, May 26, 2016 at 1:12 PM, Sudharma Subasinghe 
wrote:

> Hi,
>
> I successfully loaded client side .Js script with Handlebars template with
> 1.0.0-M4 release. I used the approach as following in the
> "process-details.hbs" template.
>
> {{headerJs "/js/process-details.js"}}
>
> Now I am getting following exception for the same approach with 1.0.0-M5 
> release.
>
> [2016-05-26 12:49:27,353] ERROR {org.wso2.carbon.uuf.internal.UUFRegistry} - 
> An unexpected error occurred while serving for request 
> '/bpmn-explorer/bpmn/process'. 
> com.github.jknack.handlebars.HandlebarsException: 
> components/root/fragments/process-details/process-details.hbs:1:2: 
> java.lang.IllegalArgumentException: Cannot evaluate the variable/helper 
> 'headerJs'.
> components/root/fragments/process-details/process-details.hbs:1:2
>   at 
> org.wso2.carbon.uuf.handlebars.helpers.runtime.MissingHelper.apply(MissingHelper.java:36)
>   at 
> com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
>   at 
> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>   at 
> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>   at 
> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>   at 
> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
>   at 
> com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:100)
>   at 
> org.wso2.carbon.uuf.handlebars.renderable.HbsFragmentRenderable.render(HbsFragmentRenderable.java:79)
>   at org.wso2.carbon.uuf.core.Fragment.render(Fragment.java:50)
>   at 
> org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:59)
>   at 
> org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:38)
>   at 
> com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
>   at 
> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>   at 
> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>   at 
> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>   at 
> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
>   at com.github.jknack.handlebars.Options.apply(Options.java:538)
>   at com.github.jknack.handlebars.Options.fn(Options.java:433)
>   at 
> org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:37)
>   at 
> org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:27)
>   at com.github.jknack.handlebars.internal.Block.merge(Block.java:210)
>   at 
> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>   at 
> com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
>   at 
> com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
>   at 
> com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:86)
>   at 
> org.wso2.carbon.uuf.handlebars.renderable.HbsPageRenderable.render(HbsPageRenderable.java:82)
>   at org.wso2.carbon.uuf.core.Page.render(Page.java:48)
>   at org.wso2.carbon.uuf.core.Component.renderPage(Component.java:89)
>   at org.wso2.carbon.uuf.core.App.renderPage(App.java:85)
>   at org.wso2.carbon.uuf.internal.UUFRegistry.serve(UUFRegistry.java:113)
>   at 
> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.execute(UUFMicroservice.java:105)
>   at 
> org.wso2.carbon.uuf.connector.ms.UUFMicroservice.get(UUFMicroservice.java:93)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:95)
>   at 
> org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:53)
>   at 
> org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:31)
>   at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>   at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
>   at 
> 

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Dilshani Subasinghe]

Hi Nuwan,

Yes I configured jms url with failover. Actually I used failover syntax as
u asked me to change
(java.naming.provider.url=failover:(tcp://localhost:61616) or
 java.naming.provider.url=failover:tcp://localhost:61616)

Proxy config:



I'm really sorry I didn't get your suggestion. Can you point out the error
within my config?

Regards,
Dilshani


On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara  wrote:

> Hi Dilshani,
>
>  In your proxy config, you have defined a jms url with failover. Can you
> please try the failover url syntax as one of bellow. I think it is due to
> invalid url definition of failover for ActiveMQ.
>
> Please refer[1] for failover url syntax in ActiveMQ
>
> java.naming.provider.url=failover:(tcp://localhost:61616) or
>  java.naming.provider.url=failover:tcp://localhost:61616,
>
> [1] http://activemq.apache.org/failover-transport-reference.html
>
> Thanks,
> Nuwanw
>
> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe 
> wrote:
>
>> Hi ESB Team,
>>
>> I am testing JMS parameters and identified scenario of missing messages
>> when using "transport.Transactionality" parameter.
>>
>> Configured axis2.xml as follows;
>>
>>   > class="org.apache.axis2.transport.jms.JMSListener">
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">TopicConnectionFactory
>> > locked="false">topic
>> > locked="false">topic
>>
>> * > locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>>
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">QueueConnectionFactory
>> > locked="false">queue
>>
>> * > locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>>
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">TopicConnectionFactory
>> > locked="false">topic
>> > locked="false">topic
>>
>> *  > locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>> 
>>
>> And aslo added same parameters to JMS sender too.
>>
>>   > class="org.apache.axis2.transport.jms.JMSSender">
>>
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">TopicConnectionFactory
>> > locked="false">topic
>> > locked="false">topic
>>
>> *> locked="false">local> name="transport.jms.SessionTransacted" locked="false">true*
>> 
>>
>> 
>> > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>> > locked="false">failover:tcp://localhost:61616
>> > locked="false">QueueConnectionFactory
>> > locked="false">queue
>>
>>
>> *> locked="false">local> name="transport.jms.SessionTransacted"
>> locked="false">true*
>>  
>>
>>
>>- Used activeMQ as JMS broker
>>- I used the scenario of "ESB as Both a JMS Producer and Consumer" [1]
>>- When testing that used external publisher to send messages to JMS
>>queue
>>
>> *Results:*
>>
>>- *Messages will be missing when consuming through ESB.*(It may
>>publish 1 messages to jms queue and only get around 100 or less number
>>of messages through ESB)
>>
>> *Further identifications:*
>>
>>- *Tried with inbound endpoints. It works properly.*
>>
>> *Attachments:*
>>
>>- inboundResult.png - This shows results with inbound endpoint.
>>- proxyResult.png - This shows results with proxy configuration.
>>- QueueProxy.xml -attached relevant proxy configuration.
>>
>> Any clarification on this situation ?
>>
>> [1]
>> https://docs.wso2.com/display/ESB500/ESB+as+Both+a+JMS+Producer+and+Consumer
>> Thank you.
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> 
>> lean.enterprise.middleware
>> Mobile: +94773375185
>> Blog: dilshanilive.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>


-- 
Best 

[Dev] GSoC Dockerfiles - Weekly status meeting minutes

[Abhishek Tiwari]

Hello Everyone,

Below are the meeting minutes from our weekly status meeting on Wed May 25, 
2016.

Tasks completed:
1. Deployed WSO2MB product using puppet provisioning. 
2. Completed code walk though of puppet-modules with understanding of Hiera and 
related dependencies.
3. Pull request to fail fast if docker daemon is not running has been merged.

Next steps:
1. Develop concrete milestone plan for test framework with focus on tasks to be 
completed within mid-term evaluation.
2. Utilize the current bash test script from Chamila as a basis for writing 
tests.

Thanks
Abhishek

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

Re: [Dev] [APIM] Changing Default Tier Limits and Names

[Harsha Kumara]

If we going to maintain both old tiers and new ones then number of
execution plans also will be increase.

Anyway with new handler users will need to change their quotas because we
have changed the previous quota calculation for application level and
subscription level.

I believe we should have meaningful set of tier values in our new releases.
If tier names becoming a issue, we may can use existing tiers with
meaningful descriptions. Yes it will be best to arrange a meeting and
discuss the impact of this change.

On Thu, May 26, 2016 at 11:54 AM, Uvindra Dias Jayasinha 
wrote:

> I think we need to setup a meeting to discuss the impact on existing
> users, there could be lots of things we need to consider.
>
> On 26 May 2016 at 11:31, Sam Sivayogam  wrote:
>
>> What if we ship the 2.0.0 with the new tier definitions(new tier names,
>> new limits) and during migration we can check if there is any subscriptions
>> for the old tiers in version 1.10 and if there is existing subscriptions,
>> we can add those old tiers to 2.0.0 database using in the migration tool.
>> In that way existing subscriptions will be able get the old tier
>> information WDYT ?
>>
>> Thanks,
>> Sam
>>
>> On Thu, May 26, 2016 at 10:47 AM, Lakmali Baminiwatta 
>> wrote:
>>
>>> I think when migrating, we can't change the names/limits of exiting
>>> tiers since it will be a problem to existing subscriptions. So IMO, instead
>>> of renaming tiers, we should add these new resource level and app level
>>> tiers while keeping the old ones as well.
>>>
>>> Thanks,
>>> Lakmali
>>>
>>> On 26 May 2016 at 10:23, Nuwan Dias  wrote:
>>>
 Changing the names of the Resource Tiers and User Quota will be a
 problem for migrating users :(.

 If these tier names are recorded in the DB only, we can simply write an
 sql script that replaces the old names with the new ones. But if they are
 recorded in the rxt/swagger, we'll have more problems.

 Thanks,
 NuwanD.

 On Wed, May 25, 2016 at 2:51 PM, Harsha Kumara 
 wrote:

> Hi All,
>
> Currently we are using very small number for our default tier values.
> We are going to change them to more meaningful counts. Here are the 
> current
> limits. Also with the change of quota calculation and undesirability we
> think of change the tier names as well.
>
> Subscription Level Tiers
>
>- Gold - 20 req/min
>- Silver - 5 req/min
>- Bronze - 1 req/min
>
>
>
> Resource Level Tiers
>
>- Ultimate - 20 req/min
>- Plus - 5  req/min
>- Basic -1 req/min
>
>
> Application Level Tiers
>
>- Large - 20 req/min
>- Medium - 5 req/min
>- Small -1 req/min
>
>
> Unauthenticated Tier - 60  req/min
>
> *Proposed Limits*
>
> Subscription Level Tiers
>
>- Gold - 5000  req/min
>- Silver - 2000 req/min
>- Bronze - 1000 req/min
>
> Resource Level Tiers
>
>- 50KPerMin - 5 req/min
>- 20KPerMin - 2 req/min
>- 10KPerMin - 1  req/min
>
> Application Level Tiers -> Per User Quota
>
>- 50PerMin - 50 req/min
>- 20PerMin  - 20 req/min
>- 10PerMin  - 10 req/min
>
> Unauthenticated Tier - 500  req/min
>
> Thanks,
> Harsha
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>



 --
 Nuwan Dias

 Technical Lead - WSO2, Inc. http://wso2.com
 email : nuw...@wso2.com
 Phone : +94 777 775 729

>>>
>>>
>>>
>>> --
>>> Lakmali Baminiwatta
>>> Senior Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>> mobile:  +94 71 2335936
>>> blog : lakmali.com
>>>
>>>
>>
>>
>> --
>> *Sam Sivayogam*
>>
>> Software Engineer
>> Mobile  : +94 772 906 439
>> Office   : +94 112 145 345
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>



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

[Dev] [UUF] Referring correspond client side .Js script with Handlebars template

[Sudharma Subasinghe]

Hi,

I successfully loaded client side .Js script with Handlebars template with
1.0.0-M4 release. I used the approach as following in the
"process-details.hbs" template.

{{headerJs "/js/process-details.js"}}

Now I am getting following exception for the same approach with
1.0.0-M5 release.

[2016-05-26 12:49:27,353] ERROR
{org.wso2.carbon.uuf.internal.UUFRegistry} - An unexpected error
occurred while serving for request '/bpmn-explorer/bpmn/process'.
com.github.jknack.handlebars.HandlebarsException:
components/root/fragments/process-details/process-details.hbs:1:2:
java.lang.IllegalArgumentException: Cannot evaluate the
variable/helper 'headerJs'.
components/root/fragments/process-details/process-details.hbs:1:2
at 
org.wso2.carbon.uuf.handlebars.helpers.runtime.MissingHelper.apply(MissingHelper.java:36)
at 
com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
at 
com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
at 
com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:100)
at 
org.wso2.carbon.uuf.handlebars.renderable.HbsFragmentRenderable.render(HbsFragmentRenderable.java:79)
at org.wso2.carbon.uuf.core.Fragment.render(Fragment.java:50)
at 
org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:59)
at 
org.wso2.carbon.uuf.handlebars.helpers.runtime.FragmentHelper.apply(FragmentHelper.java:38)
at 
com.github.jknack.handlebars.internal.Variable.merge(Variable.java:166)
at 
com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:116)
at com.github.jknack.handlebars.Options.apply(Options.java:538)
at com.github.jknack.handlebars.Options.fn(Options.java:433)
at 
org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:37)
at 
org.wso2.carbon.uuf.handlebars.helpers.runtime.FillZoneHelper.apply(FillZoneHelper.java:27)
at com.github.jknack.handlebars.internal.Block.merge(Block.java:210)
at 
com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
com.github.jknack.handlebars.internal.TemplateList.merge(TemplateList.java:94)
at 
com.github.jknack.handlebars.internal.BaseTemplate.apply(BaseTemplate.java:128)
at 
com.github.jknack.handlebars.internal.ForwardingTemplate.apply(ForwardingTemplate.java:86)
at 
org.wso2.carbon.uuf.handlebars.renderable.HbsPageRenderable.render(HbsPageRenderable.java:82)
at org.wso2.carbon.uuf.core.Page.render(Page.java:48)
at org.wso2.carbon.uuf.core.Component.renderPage(Component.java:89)
at org.wso2.carbon.uuf.core.App.renderPage(App.java:85)
at org.wso2.carbon.uuf.internal.UUFRegistry.serve(UUFRegistry.java:113)
at 
org.wso2.carbon.uuf.connector.ms.UUFMicroservice.execute(UUFMicroservice.java:105)
at 
org.wso2.carbon.uuf.connector.ms.UUFMicroservice.get(UUFMicroservice.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:95)
at 
org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:53)
at 
org.wso2.msf4j.internal.router.HttpDispatcher.channelRead0(HttpDispatcher.java:31)
at 
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308)
at 
io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:32)
at 
io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:299)
at 
io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:36)
at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:110)
at 
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
at 

Re: [Dev] [C5] Retrieving claim values with Claim Manager changes

[Himasha Guruge]

Thanks Jayanga.

On Thu, May 26, 2016 at 12:59 PM, Jayanga Kaushalya 
wrote:

> Hi Himasha,
>
> This is fixed with
> https://github.com/wso2-extensions/carbon-security-user-store-jdbc/pull/28
>
> Thanks!
>
> *Jayanga Kaushalya*
> Software Engineer
> Mobile: +94777860160
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
> On Thu, May 26, 2016 at 10:26 AM, Himasha Guruge 
> wrote:
>
>> Thanks for the quick response Thanuja.
>>
>> On Thu, May 26, 2016 at 10:24 AM, Thanuja Jayasinghe 
>> wrote:
>>
>>> Hi Himasha,
>>>
>>> This is a known issue and Jayanga will provide a fix soon.
>>>
>>> Thanks,
>>> Thanuja
>>>
>>> On Thu, May 26, 2016 at 10:19 AM, Himasha Guruge 
>>> wrote:
>>>
 [1]
 https://github.com/wso2-extensions/carbon-security-user-store-jdbc/blob/75d466dd4110ab55fb5dcb728b33611ec116bf63/feature/resources/database/WSO2CARBON_DB.sql

 [2]
 https://github.com/wso2-extensions/carbon-security-user-store-jdbc/blob/master/tests/osgi-tests/src/test/resources/h2_test_data.sql

 On Thu, May 26, 2016 at 10:19 AM, Himasha Guruge 
 wrote:

> Hi ,
>
> With the latest Claim Manager changes in carbon-security, following
> test was done to retrieve user claim values for user admin. However, an
> empty claim list is returned for the following line.
>
> user.getClaims(claims);
>
> While debugging, following stack trace was identified. I have used [1]
> and [2] to create the database tables and test data values. Any idea on
> what could be the issue? User object contains the claim mappings , however
> the values are not retrieved.
>
> Given *Caused by: org.h2.jdbc.JdbcSQLException: Invalid value "3" for
> parameter "parameterIndex" [90008-191]* could it be an issue with the
> test data?
>
> org.wso2.carbon.bpmn[org.wso2.carbon.bpmn.core.integration.BPSUserIdentityManager]
> : Error retrieving user info by id for: 41dadd2aea6e11e59ce95e5517507c66
> org.wso2.carbon.security.caas.user.core.exception.IdentityStoreException:
> Error occurred while retrieving user claims.
> at
> org.wso2.carbon.security.userstore.jdbc.connector.JDBCIdentityStoreConnector.getUserAttributeValues(JDBCIdentityStoreConnector.java:250)
> at
> org.wso2.carbon.security.caas.user.core.store.IdentityStore.getUserAttributeValues(IdentityStore.java:185)
> at
> org.wso2.carbon.security.caas.user.core.bean.User.getClaims(User.java:146)
> at
> org.wso2.carbon.bpmn.core.integration.BPSUserIdentityManager.findUserById(BPSUserIdentityManager.java:111)
> at
> org.wso2.carbon.bpmn.tests.osgi.BPMNClaimUserTaskTest.testInvokeClaimedUserTask(BPMNClaimUserTaskTest.java:144)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at
> org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.injectContextAndInvoke(ProbeInvokerImpl.java:125)
> at
> org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.findAndInvoke(ProbeInvokerImpl.java:85)
> at
> org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.call(ProbeInvokerImpl.java:73)
> at
> org.ops4j.pax.exam.nat.internal.NativeTestContainer.call(NativeTestContainer.java:112)
> at
> org.ops4j.pax.exam.spi.reactors.SingletonStagedReactor.invoke(SingletonStagedReactor.java:114)
> at
> org.ops4j.pax.exam.spi.reactors.PerSuiteStagedReactor.invoke(PerSuiteStagedReactor.java:47)
> at
> org.ops4j.pax.exam.testng.listener.PaxExam.runByDriver(PaxExam.java:458)
> at org.ops4j.pax.exam.testng.listener.PaxExam.run(PaxExam.java:308)
> at
> org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:212)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:652)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:845)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1153)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
> at org.testng.TestRunner.privateRun(TestRunner.java:771)
> at org.testng.TestRunner.run(TestRunner.java:621)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
> at org.testng.SuiteRunner.run(SuiteRunner.java:259)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at 

Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter

[Nuwan Wimalasekara]

Hi Dilshani,

 In your proxy config, you have defined a jms url with failover. Can you
please try the failover url syntax as one of bellow. I think it is due to
invalid url definition of failover for ActiveMQ.

Please refer[1] for failover url syntax in ActiveMQ

java.naming.provider.url=failover:(tcp://localhost:61616) or
 java.naming.provider.url=failover:tcp://localhost:61616,

[1] http://activemq.apache.org/failover-transport-reference.html

Thanks,
Nuwanw

On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe 
wrote:

> Hi ESB Team,
>
> I am testing JMS parameters and identified scenario of missing messages
> when using "transport.Transactionality" parameter.
>
> Configured axis2.xml as follows;
>
>class="org.apache.axis2.transport.jms.JMSListener">
> 
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  locked="false">TopicConnectionFactory
>  locked="false">topic
>  locked="false">topic
>
> *  locked="false">local name="transport.jms.SessionTransacted" locked="false">true*
> 
>
> 
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  locked="false">QueueConnectionFactory
>  locked="false">queue
>
> *  locked="false">local name="transport.jms.SessionTransacted" locked="false">true*
> 
>
> 
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  locked="false">TopicConnectionFactory
>  locked="false">topic
>  locked="false">topic
>
> *   locked="false">local name="transport.jms.SessionTransacted" locked="false">true*
> 
> 
>
> And aslo added same parameters to JMS sender too.
>
>class="org.apache.axis2.transport.jms.JMSSender">
>
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  locked="false">TopicConnectionFactory
>  locked="false">topic
>  locked="false">topic
>
> * locked="false">local name="transport.jms.SessionTransacted" locked="false">true*
> 
>
> 
>  locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  locked="false">failover:tcp://localhost:61616
>  locked="false">QueueConnectionFactory
>  locked="false">queue
>
>
> * locked="false">local name="transport.jms.SessionTransacted"
> locked="false">true*
>  
>
>
>- Used activeMQ as JMS broker
>- I used the scenario of "ESB as Both a JMS Producer and Consumer" [1]
>- When testing that used external publisher to send messages to JMS
>queue
>
> *Results:*
>
>- *Messages will be missing when consuming through ESB.*(It may
>publish 1 messages to jms queue and only get around 100 or less number
>of messages through ESB)
>
> *Further identifications:*
>
>- *Tried with inbound endpoints. It works properly.*
>
> *Attachments:*
>
>- inboundResult.png - This shows results with inbound endpoint.
>- proxyResult.png - This shows results with proxy configuration.
>- QueueProxy.xml -attached relevant proxy configuration.
>
> Any clarification on this situation ?
>
> [1]
> https://docs.wso2.com/display/ESB500/ESB+as+Both+a+JMS+Producer+and+Consumer
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
> Mobile: +94773375185
> Blog: dilshanilive.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

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

Re: [Dev] [C5] Retrieving claim values with Claim Manager changes

[Jayanga Kaushalya]

Hi Himasha,

This is fixed with
https://github.com/wso2-extensions/carbon-security-user-store-jdbc/pull/28

Thanks!

*Jayanga Kaushalya*
Software Engineer
Mobile: +94777860160
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware

On Thu, May 26, 2016 at 10:26 AM, Himasha Guruge  wrote:

> Thanks for the quick response Thanuja.
>
> On Thu, May 26, 2016 at 10:24 AM, Thanuja Jayasinghe 
> wrote:
>
>> Hi Himasha,
>>
>> This is a known issue and Jayanga will provide a fix soon.
>>
>> Thanks,
>> Thanuja
>>
>> On Thu, May 26, 2016 at 10:19 AM, Himasha Guruge 
>> wrote:
>>
>>> [1]
>>> https://github.com/wso2-extensions/carbon-security-user-store-jdbc/blob/75d466dd4110ab55fb5dcb728b33611ec116bf63/feature/resources/database/WSO2CARBON_DB.sql
>>>
>>> [2]
>>> https://github.com/wso2-extensions/carbon-security-user-store-jdbc/blob/master/tests/osgi-tests/src/test/resources/h2_test_data.sql
>>>
>>> On Thu, May 26, 2016 at 10:19 AM, Himasha Guruge 
>>> wrote:
>>>
 Hi ,

 With the latest Claim Manager changes in carbon-security, following
 test was done to retrieve user claim values for user admin. However, an
 empty claim list is returned for the following line.

 user.getClaims(claims);

 While debugging, following stack trace was identified. I have used [1]
 and [2] to create the database tables and test data values. Any idea on
 what could be the issue? User object contains the claim mappings , however
 the values are not retrieved.

 Given *Caused by: org.h2.jdbc.JdbcSQLException: Invalid value "3" for
 parameter "parameterIndex" [90008-191]* could it be an issue with the
 test data?

 org.wso2.carbon.bpmn[org.wso2.carbon.bpmn.core.integration.BPSUserIdentityManager]
 : Error retrieving user info by id for: 41dadd2aea6e11e59ce95e5517507c66
 org.wso2.carbon.security.caas.user.core.exception.IdentityStoreException:
 Error occurred while retrieving user claims.
 at
 org.wso2.carbon.security.userstore.jdbc.connector.JDBCIdentityStoreConnector.getUserAttributeValues(JDBCIdentityStoreConnector.java:250)
 at
 org.wso2.carbon.security.caas.user.core.store.IdentityStore.getUserAttributeValues(IdentityStore.java:185)
 at
 org.wso2.carbon.security.caas.user.core.bean.User.getClaims(User.java:146)
 at
 org.wso2.carbon.bpmn.core.integration.BPSUserIdentityManager.findUserById(BPSUserIdentityManager.java:111)
 at
 org.wso2.carbon.bpmn.tests.osgi.BPMNClaimUserTaskTest.testInvokeClaimedUserTask(BPMNClaimUserTaskTest.java:144)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:483)
 at
 org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.injectContextAndInvoke(ProbeInvokerImpl.java:125)
 at
 org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.findAndInvoke(ProbeInvokerImpl.java:85)
 at
 org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.call(ProbeInvokerImpl.java:73)
 at
 org.ops4j.pax.exam.nat.internal.NativeTestContainer.call(NativeTestContainer.java:112)
 at
 org.ops4j.pax.exam.spi.reactors.SingletonStagedReactor.invoke(SingletonStagedReactor.java:114)
 at
 org.ops4j.pax.exam.spi.reactors.PerSuiteStagedReactor.invoke(PerSuiteStagedReactor.java:47)
 at
 org.ops4j.pax.exam.testng.listener.PaxExam.runByDriver(PaxExam.java:458)
 at org.ops4j.pax.exam.testng.listener.PaxExam.run(PaxExam.java:308)
 at
 org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:212)
 at org.testng.internal.Invoker.invokeMethod(Invoker.java:652)
 at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:845)
 at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1153)
 at
 org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
 at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
 at org.testng.TestRunner.privateRun(TestRunner.java:771)
 at org.testng.TestRunner.run(TestRunner.java:621)
 at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
 at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
 at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
 at org.testng.SuiteRunner.run(SuiteRunner.java:259)
 at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
 at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
 at org.testng.TestNG.runSuitesSequentially(TestNG.java:1199)
 at org.testng.TestNG.runSuitesLocally(TestNG.java:1124)
 at org.testng.TestNG.run(TestNG.java:1032)
 at
 

Re: [Dev] [APIM] Changing Default Tier Limits and Names

[Uvindra Dias Jayasinha]

I think we need to setup a meeting to discuss the impact on existing users,
there could be lots of things we need to consider.

On 26 May 2016 at 11:31, Sam Sivayogam  wrote:

> What if we ship the 2.0.0 with the new tier definitions(new tier names,
> new limits) and during migration we can check if there is any subscriptions
> for the old tiers in version 1.10 and if there is existing subscriptions,
> we can add those old tiers to 2.0.0 database using in the migration tool.
> In that way existing subscriptions will be able get the old tier
> information WDYT ?
>
> Thanks,
> Sam
>
> On Thu, May 26, 2016 at 10:47 AM, Lakmali Baminiwatta 
> wrote:
>
>> I think when migrating, we can't change the names/limits of exiting tiers
>> since it will be a problem to existing subscriptions. So IMO, instead of
>> renaming tiers, we should add these new resource level and app level tiers
>> while keeping the old ones as well.
>>
>> Thanks,
>> Lakmali
>>
>> On 26 May 2016 at 10:23, Nuwan Dias  wrote:
>>
>>> Changing the names of the Resource Tiers and User Quota will be a
>>> problem for migrating users :(.
>>>
>>> If these tier names are recorded in the DB only, we can simply write an
>>> sql script that replaces the old names with the new ones. But if they are
>>> recorded in the rxt/swagger, we'll have more problems.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Wed, May 25, 2016 at 2:51 PM, Harsha Kumara  wrote:
>>>
 Hi All,

 Currently we are using very small number for our default tier values.
 We are going to change them to more meaningful counts. Here are the current
 limits. Also with the change of quota calculation and undesirability we
 think of change the tier names as well.

 Subscription Level Tiers

- Gold - 20 req/min
- Silver - 5 req/min
- Bronze - 1 req/min



 Resource Level Tiers

- Ultimate - 20 req/min
- Plus - 5  req/min
- Basic -1 req/min


 Application Level Tiers

- Large - 20 req/min
- Medium - 5 req/min
- Small -1 req/min


 Unauthenticated Tier - 60  req/min

 *Proposed Limits*

 Subscription Level Tiers

- Gold - 5000  req/min
- Silver - 2000 req/min
- Bronze - 1000 req/min

 Resource Level Tiers

- 50KPerMin - 5 req/min
- 20KPerMin - 2 req/min
- 10KPerMin - 1  req/min

 Application Level Tiers -> Per User Quota

- 50PerMin - 50 req/min
- 20PerMin  - 20 req/min
- 10PerMin  - 10 req/min

 Unauthenticated Tier - 500  req/min

 Thanks,
 Harsha

 --
 Harsha Kumara
 Software Engineer, WSO2 Inc.
 Mobile: +94775505618
 Blog:harshcreationz.blogspot.com

>>>
>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>>
>> --
>> Lakmali Baminiwatta
>> Senior Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>> mobile:  +94 71 2335936
>> blog : lakmali.com
>>
>>
>
>
> --
> *Sam Sivayogam*
>
> Software Engineer
> Mobile  : +94 772 906 439
> Office   : +94 112 145 345
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>



-- 
Regards,
Uvindra

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

Re: [Dev] [APIM] Changing Default Tier Limits and Names

[Sam Sivayogam]

What if we ship the 2.0.0 with the new tier definitions(new tier names, new
limits) and during migration we can check if there is any subscriptions for
the old tiers in version 1.10 and if there is existing subscriptions, we
can add those old tiers to 2.0.0 database using in the migration tool. In
that way existing subscriptions will be able get the old tier information
WDYT ?

Thanks,
Sam

On Thu, May 26, 2016 at 10:47 AM, Lakmali Baminiwatta 
wrote:

> I think when migrating, we can't change the names/limits of exiting tiers
> since it will be a problem to existing subscriptions. So IMO, instead of
> renaming tiers, we should add these new resource level and app level tiers
> while keeping the old ones as well.
>
> Thanks,
> Lakmali
>
> On 26 May 2016 at 10:23, Nuwan Dias  wrote:
>
>> Changing the names of the Resource Tiers and User Quota will be a problem
>> for migrating users :(.
>>
>> If these tier names are recorded in the DB only, we can simply write an
>> sql script that replaces the old names with the new ones. But if they are
>> recorded in the rxt/swagger, we'll have more problems.
>>
>> Thanks,
>> NuwanD.
>>
>> On Wed, May 25, 2016 at 2:51 PM, Harsha Kumara  wrote:
>>
>>> Hi All,
>>>
>>> Currently we are using very small number for our default tier values. We
>>> are going to change them to more meaningful counts. Here are the current
>>> limits. Also with the change of quota calculation and undesirability we
>>> think of change the tier names as well.
>>>
>>> Subscription Level Tiers
>>>
>>>- Gold - 20 req/min
>>>- Silver - 5 req/min
>>>- Bronze - 1 req/min
>>>
>>>
>>>
>>> Resource Level Tiers
>>>
>>>- Ultimate - 20 req/min
>>>- Plus - 5  req/min
>>>- Basic -1 req/min
>>>
>>>
>>> Application Level Tiers
>>>
>>>- Large - 20 req/min
>>>- Medium - 5 req/min
>>>- Small -1 req/min
>>>
>>>
>>> Unauthenticated Tier - 60  req/min
>>>
>>> *Proposed Limits*
>>>
>>> Subscription Level Tiers
>>>
>>>- Gold - 5000  req/min
>>>- Silver - 2000 req/min
>>>- Bronze - 1000 req/min
>>>
>>> Resource Level Tiers
>>>
>>>- 50KPerMin - 5 req/min
>>>- 20KPerMin - 2 req/min
>>>- 10KPerMin - 1  req/min
>>>
>>> Application Level Tiers -> Per User Quota
>>>
>>>- 50PerMin - 50 req/min
>>>- 20PerMin  - 20 req/min
>>>- 10PerMin  - 10 req/min
>>>
>>> Unauthenticated Tier - 500  req/min
>>>
>>> Thanks,
>>> Harsha
>>>
>>> --
>>> Harsha Kumara
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94775505618
>>> Blog:harshcreationz.blogspot.com
>>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> Lakmali Baminiwatta
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>


-- 
*Sam Sivayogam*

Software Engineer
Mobile  : +94 772 906 439
Office   : +94 112 145 345
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev