Ok.. that explains. But, I'm confused. How you guys assign this appOwner
role to the user who creates an app??
Role name=appOwner
DisplayNameApplication Owner/DisplayName
Permission
/permission/admin/login,
Hi Nuwan,
You are right. Since the JIRA pertains to an upcoming release, it would be
best to avoid upgrades at this point and go with the hostobject approach.
For this JIRA I need to get the current webcontextroot in Jaggery, and I'll
work with Manu to get this done.
Thanks,
Gokul.
On 7 May
Hi Nirmal,
This is done through a BPEL process, in that BPEL process 'AppOwner' is
used.
thank you.
On Tue, May 7, 2013 at 11:38 AM, Nirmal Fernando nir...@wso2.com wrote:
Ok.. that explains. But, I'm confused. How you guys assign this appOwner
role to the user who creates an app??
Role
Hi
On Mon, May 6, 2013 at 4:36 AM, Krishantha Samaraweera
krishan...@wso2.comwrote:
Hi Reka,
What is the reason behind this commit ? Any particular reason to comment
out auto framework and platform automated test suite from root pom.
Since we introduced a new product called Stratos
So as of now, if you change the appOwner, it will break that process.
As discussed offline, IMO no user would have any interest over changing the
role name appOwner, but the display name. So I don't think we should
allow that (i.e. appfactory xml should be validated for a role appOwner,
for a
Hi Nirmal,
I understood your point, what you suggest is to document that 'AppOwner' is
a special case and let the user to change display name of role.
+1, that is cleaner and not adding more attributes to the configuration.
Regarding BPEL, we can get configuration values through BPEL custom
Hi Nirmal,
+1 for the idea. Then no worries about this issue.
On Tue, May 7, 2013 at 12:50 PM, Manjula Rathnayake manju...@wso2.comwrote:
Hi Nirmal,
I understood your point, what you suggest is to document that 'AppOwner'
is a special case and let the user to change display name of role.
Hi all,
Following intermittent error is noticed. Any idea/clue please.
ERROR {org.jaggeryjs.jaggery.core.manager.WebAppManager} -
org.mozilla.javascript.JavaScriptException: Error: No action specified
(/appmgt/site/blocks/application/add/ajax/add.jag#140)
whats in (/appmgt/site/blocks/application/add/ajax/add.jag#140
Regards,
/Nuwan
On Tue, May 7, 2013 at 1:55 PM, Manjula Rathnayake manju...@wso2.comwrote:
Hi all,
Following intermittent error is noticed. Any idea/clue please.
ERROR {org.jaggeryjs.jaggery.core.manager.WebAppManager} -
Hi Nuwan,
Please note that this is intermittent. Here the error is action is missing
in incoming httpRequest. But Why this become intermittent?
var mod, obj, result,
action = request.getParameter(action),
site = require(/site/conf/site.json);
// line 140
else {
throw
Hi all,
EntitlementFilter sample is working fine and you may missed the part Enable
and Promote To PDP when importing the xacml policy.
I have updated the Readme.txt informing this.
Johann can you please the apply the attached patch to update the Readme.txt
Thanks,
Darshana.
On Tue, May 7,
Hi Darshana,
Thank you very much for looking into this. Will apply the patch.
Regards,
Johann.
On Tue, May 7, 2013 at 2:17 PM, Darshana Gunawardana darsh...@wso2.comwrote:
Hi all,
EntitlementFilter sample is working fine and you may missed the part
Enable and Promote To PDP when importing
Am sure during those intermittent cases the action is not sent, this is
pretty trivial code block, if the item is not in the request then its
throwing the error.
Regards,
/Nuwan
On Tue, May 7, 2013 at 2:06 PM, Manjula Rathnayake manju...@wso2.comwrote:
Hi Nuwan,
Please note that this is
Hi Nuwan,
Please find the corresponding code block in template.jag which do the post
to above page. Here we are setting the action. Any possible scenario that
above block get executed without these post parameters?
function createApplicationSubmit(){
Hi Ravi,
On Tue, Apr 16, 2013 at 2:46 PM, Sagara Gunathunga sag...@wso2.com wrote:
On Tue, Apr 16, 2013 at 1:08 PM, Ravi Undupitiya r...@wso2.com wrote:
Hello,
I'm trying to move the multipart/from-data builder to work without the
use of Servlets so that this format can be used in the
Hi Charitha,
Not yet. I have to create a patch and pass it over to Sagara who is going
to commit it. I wanted to write a test case for it as well.
Thanks,
Ravi
On Tue, May 7, 2013 at 3:36 PM, Charitha Kankanamge chari...@wso2.comwrote:
Hi Ravi,
On Tue, Apr 16, 2013 at 2:46 PM, Sagara
Hi,
If the script is working fine, please use it. Currently we haven't hosted
puppet configurations in a public place.
On Tue, Apr 30, 2013 at 9:37 AM, Ajanthan Balachandran ajant...@wso2.comwrote:
Hi,
Previously we used a script [0] to setup AF dev setup locally.Are we going
to deprecate
On Tue, Apr 23, 2013 at 3:08 PM, Miyuru Wanninayaka miy...@wso2.com wrote:
This patch has changes need for ESB 4.7 release.
Patch0001 will release with 3rd of March release and ESB 4.7 will go
later. So we are keeping ESB 4.7 related patches in patch0002
Please remove patch0002 and merge
It seems you havent configure data source properly. Please see this
log*Error occurred while getting carbon data-source
*
*
*
Thanks
Sanjeewa.
On Tue, May 7, 2013 at 5:20 PM, Shavantha Weerasinghe shavan...@wso2.comwrote:
Hi All
I just now faced the same exception while testing with ESB
Please check whether you have created and using the datasource correctly.
Sanjeewa's issue was due to that, I checked with him.
On Tue, May 7, 2013 at 5:20 PM, Shavantha Weerasinghe shavan...@wso2.comwrote:
Hi All
I just now faced the same exception while testing with ESB Stat2. and
done
On Tue, May 7, 2013 at 4:57 PM, Amila Suriarachchi am...@wso2.com wrote:
On Tue, Apr 23, 2013 at 3:08 PM, Miyuru Wanninayaka miy...@wso2.comwrote:
This patch has changes need for ESB 4.7 release.
Patch0001 will release with 3rd of March release and ESB 4.7 will go
later. So we are
Hi QA Team,
Please find the BAM 2.3.0 pack for QA testing at [1].
[1] http://173.164.178.33/builds/BAM-2.3.0/07-05-2013/wso2bam-2.3.0.zip
Thanks,
Gihan
--
---
W.G. Gihan Anuruddha
Senior Software Engineer | WSO2, Inc.
M: +94772272595
___
Dev mailing
Malith,
You don't have to add the version (1.1.0-wso2v8) directory here. It is
redundant. Refer how other dependencies (axis2) components have been added.
Can you change it accordingly?
Thanks,
Kishanthan.
On Mon, May 6, 2013 at 8:48 PM, mal...@wso2.com wrote:
Author: mal...@wso2.com
Date:
Yeah, that was the issue. I have checked with him and fixed it.
Thanks,
Sinthuja
On Tue, May 7, 2013 at 5:28 PM, Kasun Weranga kas...@wso2.com wrote:
Please check whether you have created and using the datasource correctly.
Sanjeewa's issue was due to that, I checked with him.
On Tue, May
Hi Kishanthan,
Sure will do the change.
Thanks,
Malith
On Tue, May 7, 2013 at 5:57 PM, Kishanthan Thangarajah
kishant...@wso2.comwrote:
Malith,
You don't have to add the version (1.1.0-wso2v8) directory here. It is
redundant. Refer how other dependencies (axis2) components have been
Hi,
Applied the patch.
Thanks,
Johann.
On Tue, May 7, 2013 at 2:20 PM, Johann Nallathamby joh...@wso2.com wrote:
Hi Darshana,
Thank you very much for looking into this. Will apply the patch.
Regards,
Johann.
On Tue, May 7, 2013 at 2:17 PM, Darshana Gunawardana darsh...@wso2.comwrote:
Hi,
I am getting following build failure in branch when building ESB product.
[INFO] WSO2 Stratos ESB - Styles Features SUCCESS [0.049s]
[INFO] WSO2 Stratos ESB - Samples Features ... SUCCESS [0.124s]
[INFO] WSO2 ESB - P2 Profile Generation ..
patch0002 was already removed from ESB build. Pls take a svn up of ESB
product and build
On Tue, May 7, 2013 at 7:47 PM, Kasun Weranga kas...@wso2.com wrote:
Hi,
I am getting following build failure in branch when building ESB product.
[INFO] WSO2 Stratos ESB - Styles Features
Hi Reka,
I didn't get you properly. However I don't see any relation with fixing
test cases and test framework exclusion from root pom.
Test framework was building successfully in 4.1.1 branch and other products
like API-Manger depends on it. So removing this caused API manger build
failure.
Changes that needs to be done:
1. If using HTTPClient, make the httpclient version *4.1 *(above 4.0)
dependency
groupIdorg.apache.httpcomponents/groupId
artifactIdhttpclient/artifactId
version4.1/version
/dependency
2. To get build logs, you need to
Hi Manjula,
jagg.post is a wrapper function for jQuery.ajax. There are possible ways
this could get failed. It seems the data parameter required for jquery post
is not properly created in this scenario. If so it will go as null and will
result this kind of error. Possible reproducible scenarios
Hi,
Forwarding this to dev-group as this should be sent there. Sorry for the
mistake.
-Ishara
-- Forwarded message --
From: Ishara Premadasa ish...@wso2.com
Date: Wed, May 8, 2013 at 9:49 AM
Subject: [Dev] SAML2 Web Browser based SSO with WSO2 IS demo webapp doesn't
work with IS
dd50ea1146863ec4fdd0137673564089 wso2bam-2.3.0.zip
chamara@chamara-TECRA-M11:~/Downloads/newpack7thMAY/wso2bam-2.3.0/samples/service-stats$
ant
Buildfile:
/home/chamara/Downloads/newpack7thMAY/wso2bam-2.3.0/samples/service-stats/build.xml
clean:
compile:
[mkdir] Created dir:
Service Statistics, Mediation Statistics, Activity monitoring samples are
broken like this.
Rest API Sample works.
On Wed, May 8, 2013 at 11:03 AM, Chamara Ariyarathne chama...@wso2.comwrote:
dd50ea1146863ec4fdd0137673564089 wso2bam-2.3.0.zip
34 matches
Mail list logo
