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
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
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
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
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
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
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
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
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,
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/'.
+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:
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
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
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
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]
>
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
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
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
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
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.
>>
>>
>>
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
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
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
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
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
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
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
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]
>
> 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
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
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]
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
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
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
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
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
>
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
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
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]
+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
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
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
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 :
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
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
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
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
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
>
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
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
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
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
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
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
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
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.
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
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
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
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
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
61 matches
Mail list logo