Hi All,
Thanks for the responses.
build was succeeded after updating the repo with new xml schema version.
On Wed, Nov 26, 2014 at 10:22 PM, Kalpa Welivitigoda kal...@wso2.com
wrote:
Hi Vijitha,
Once you update the xml schema version in pom.xml and still have the same
issue, you can try mvn
Hi,
We are setting up a simple WSO2 Application Server cluster with one master
node and one worker node. This is done via spawning instances in OpenStack
cloud via python NovaClient API.
After spawning instances we need to get their ip addresses and use them to
fill puppet template values. (say
Jaggery build fails in https://wso2.org/jenkins/job/jaggery/100/console
seem like it's caused by some update in integration framework. Can you
please take a look and let us know if this is something we should fix in
our side.
--
With regards,
*Manu*ranga Perera.
phone : 071 7 70 20 50
mail :
Hi ,
Staxon library is used in ESB as underlying JSON library. We need to
improve and add more functionalities to this library .So what will be the
process of creating above git repo.
thanks
isurur
--
Best Regards
Isuru Ranawaka
M: +94714629880
Blog : http://isurur.blogspot.com/
Hi Suhan,
nodes.pp file can contain the generic information that are used by almost
all of the modules. However, as far as I understand, you can go for a
better pattern using Puppet's Hiera key value store[1]. Its main purpose is
to separate data from the manifests, so in your case you can store
Hi Jaggery Team,
Can we get the build fixed [1]? This is blocking AS nightly build packs
generation.
Thanks,
Kishanthan.
[1] https://wso2.org/jenkins/job/jaggery/
--
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware
Mobile -
Hi Krishantha,
Can you please shed some light here? AS team is blocked due to this.
On Fri, Nov 28, 2014 at 2:35 PM, Manuranga Perera m...@wso2.com wrote:
Jaggery build fails in https://wso2.org/jenkins/job/jaggery/100/console
seem like it's caused by some update in integration framework.
Hi Kishanthan,
There is a separate thread Jaggery Build Fail started by Manu. Please
follow that. We will fix it asap after talking to automation team.
/Ruchira
On Fri, Nov 28, 2014 at 2:57 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
Hi Jaggery Team,
Can we get the build fixed
Thusara, I'm still seeing some formatting issues with this patch.
On Thu, Nov 27, 2014 at 3:02 PM, Thushara Ranawaka thusha...@wso2.com
wrote:
Hi Kishanthan,
Corrected the formatting issues. Kindly apply the patch attached in
Jira[1].
[1] https://wso2.org/jira/browse/CARBON-15092
Thanks,
Notes on the API Manager TODOs for first iteration
1. Make the Subscriptions Clickable and redirect to API overview Page.
2. Highlight the Stats menu when it is clicked.
3. On every page limit number of records to show.
4. Drill down on Overall API Usage - drill down by date range. Change
Hi Kishanthan,
Corrected the formatting issues. Kindly apply the patch attached in Jira[1].
Note: removed the newline
[1] https://wso2.org/jira/browse/CARBON-15092
Thanks,
On Fri, Nov 28, 2014 at 3:16 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
Thusara, I'm still seeing some
Hi Kasun/Isuru
Please apply the patch attached in jira[1]
[1] https://wso2.org/jira/browse/ESBJAVA-3438
--
*Pubudu Dissanayake*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Mob: + 94 775 503 304
Blog: http://geekdetected.wordpress.com/
Linkedin:
Notes on App Manager :
- Separates graphs into separate pages
- Allow to sort tables
Graph1 : Overall Subscriptions
Subscription pie chart: show max no of elements that can show in pie chat.
then take remaining subscriptions as other.
Legend width
Hi Chamila,
Thanks you for the prompt reply.
Will check with Hiera and revert.
Thanks,
Suhan
On Fri, Nov 28, 2014 at 2:39 PM, Chamila De Alwis chami...@wso2.com wrote:
Hi Suhan,
nodes.pp file can contain the generic information that are used by almost
all of the modules. However, as far as
Hi Ruchira/ Manuranga,
The automation framework 4.3.1-SNAPSHOT id no longer available. Please
change the version into 4.3.1 and check this.
As the log it seems like you are using older version of Automation.xml.
Please refer the automation.xml on [1].
[1].
Hi Ruchira
This is due to class loading issue when loading from xalan jar when
evaluating XPath. Please add below dependency to tests pom to load the
correct class.
dependency
groupIdxalan/groupId
artifactIdxalan/artifactId
version2.6.0/version
scopetest/scope
/dependency
Thanks,
Hi QA Team,
Please find the BAM 2.5.0 latest build for QA testing at [1].
This was built with a clean repo from the revision 209990.
[1]
https://svn.wso2.org/repos/wso2/people/malith/BAM-2.5.0/28-11-2014/wso2bam-2.5.0.zip
Thanks,
Malith
--
Malith Dhanushka
Software Engineer - Data
Hi Inshaf,
You are using BAM 2.4.1. But you are referring BAM 2.4.0 documentation
which is an old one. please try the right documentation[1].
[1].https://docs.wso2.com/display/BAM241/Analysing+HTTPD+Logs
On Fri, Nov 28, 2014 at 5:30 PM, Inshaf Mahath ins...@wso2.com wrote:
Hi,
I am trying
Applied the patch. On a side note, don't resolve the jira until the fix is
applied and verified.
On Fri, Nov 28, 2014 at 3:40 PM, Thushara Ranawaka thusha...@wso2.com
wrote:
Hi Kishanthan,
Corrected the formatting issues. Kindly apply the patch attached in
Jira[1].
Note: removed the newline
The new pack can be found from
https://svn.wso2.org/repos/wso2/scratch/chunk13-release/28-11-2014/
On Fri, Nov 28, 2014 at 5:28 AM, Chanika Geeganage chan...@wso2.com wrote:
p2-repo is available at
https://svn.wso2.org/repos/wso2/scratch/chunk13-release/27-11-2014/p2-repo/
On Thu, Nov 27,
Hi Dharshana and Nuwan,
thanks, this fixed in it in my local setup
On Fri, Nov 28, 2014 at 4:20 PM, Nuwan Wimalasekara nuw...@wso2.com wrote:
Hi Ruchira
This is due to class loading issue when loading from xalan jar when
evaluating XPath. Please add below dependency to tests pom to load the
Hi Lakshman,
I tried using both BAM 2.4.0 and 2.4.1. I got the same error on both
occasion.
On Fri, Nov 28, 2014 at 5:39 PM, Lakshman Udayakantha lakshm...@wso2.com
wrote:
Hi Inshaf,
You are using BAM 2.4.1. But you are referring BAM 2.4.0 documentation
which is an old one. please try the
Hi Inshaf,
Did you set the JAVA_HOME in your machine by adding following lines to
.bashrc or .bash_profile?
JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
export JAVA_HOME
Thanks
On Fri, Nov 28, 2014 at 6:05 PM, Inshaf Mahath ins...@wso2.com wrote:
Hi Lakshman,
Hi Kernel Team,
Please commit patch for [1]. The modification is done in the carbon.core.
[1] - https://wso2.org/jira/browse/IDENTITY-2730
Thank you.
--
Shiva Balachandran
Software Engineer
WSO2 Inc.
Mobile - +94 774445788
___
Dev mailing list
I am generally -1 for forking external dependencies. There should be
workarounds for these. Please explain with details why this fork is
necessary.
On Fri, Nov 28, 2014 at 2:39 PM, Isuru Ranawaka isu...@wso2.com wrote:
Hi ,
Staxon library is used in ESB as underlying JSON library. We need to
On Fri, Nov 28, 2014 at 7:28 PM, Afkham Azeez az...@wso2.com wrote:
I am generally -1 for forking external dependencies. There should be
workarounds for these. Please explain with details why this fork is
necessary.
Additionally I would like to know whether you have contact original authors
Hi Harsha,
Make sure any of those are not required for cqlsh.
Thanks,
Bhathiya
On Fri, Nov 28, 2014 at 12:44 AM, Harsha Kumara hars...@wso2.com wrote:
Hi All,
Storage Server is shipping
cql-internal-only-1.4.1.zip, thrift-python-internal-only-0.7.0.zip in the
distribution. Do we needs to
Hi All,
I'm implementing WSO2 ESB connector project for SlideShare API. Their
API end point working properly in Rest client .When running through WSO2
ESB i got this error. Can you please figure out this error.
Response in XML
?xml version=1.0 encoding=UTF-8?
SlideShareServiceError
Hi Bhathiya,
We are copying necessary library to the repository for the cql, hence these
are not needed. I will remove these files from the distribution as they no
need.
Thanks,
Harsha
On Fri, Nov 28, 2014 at 8:04 PM, Bhathiya Jayasekara bhath...@wso2.com
wrote:
Hi Harsha,
Make sure any of
Hi,
I want to use per service logging in ESB.
I created a proxy with a simple log mediator. And I configured my log4j
properties as below.
log4j.category.SERVICE_LOGGER.MyProxy=INFO, PROXY_APPENDER
log4j.additivity.PROXY_APPENDER=false
log4j.additivity.PROXY_APPENDER.threshold=TRACE
Hi Dulanja,
Were you able to solve this issue?
I am trying to use per service logging in ESB. I enabled trace log for my
proxy service. I am not getting any trace logs in my log file. It is
discussed in [1].
Appreciate if you could share how you solved this issue.
1. [Dev][ESB] Per service
This is already forked for some set of fixes/features. Lets review them and
then then decide how we can proceed.
On Fri, Nov 28, 2014 at 7:41 PM, Sagara Gunathunga sag...@wso2.com wrote:
On Fri, Nov 28, 2014 at 7:28 PM, Afkham Azeez az...@wso2.com wrote:
I am generally -1 for forking
Hi,
I'm trying to merge the PR and have a concern.
This change would potentially affect other service types as well. Were you
able to do a regression test with other products which use axis2 services
?. For eg: DSS use axis2, and please try with other proxy service types
other than jms proxy if
33 matches
Mail list logo