On Tue, Jan 22, 2013 at 12:56 PM, Lalaji Sureshika lal...@wso2.com wrote:
Hi,
On Tue, Jan 22, 2013 at 11:19 AM, Amila Suriarachchi am...@wso2.comwrote:
On Tue, Jan 22, 2013 at 12:14 PM, Buddhika Chamith buddhi...@wso2.comwrote:
This usually happens when an event not conforming to the
AFAIR from a previous experience, you are sending some wrong value with the
data being published. May be an integer instead of a string or something
like that. If you double check the event being published against the stream
definition carefully, I think you'll figure out the wrong parameter.
On
On Tue, Jan 22, 2013 at 1:48 PM, Amila Suriarachchi am...@wso2.com wrote:
On Tue, Jan 22, 2013 at 12:56 PM, Lalaji Sureshika lal...@wso2.comwrote:
Hi,
On Tue, Jan 22, 2013 at 11:19 AM, Amila Suriarachchi am...@wso2.comwrote:
On Tue, Jan 22, 2013 at 12:14 PM, Buddhika Chamith
Hai Prabath..!
We have a CXF Web applications with no UIs. The
application does have only the Resource related classes. I have installed
the OAuth feature to generate the client id, client secret, auth endpoint,
access endpoint for the registered application.
But if we want
---
WSO2 Carbon 4.0.x Platform 4.0.6 #86 failed.
---
Code has been updated by eranda, janaka, maninda, vijitha, ashansa, shammi,
nuwand, nirmal, kasun,
Hi Anjana,
I went through the ndatasource code. There we get
ConfigurationContextSerice/ServerConfiguration/etc. While searching for
their usages found out that we use those references to get clustering
agents/registering AxisContextObservers/etc.
How hard it is to decouple ndatasource
On Tue, Jan 22, 2013 at 5:16 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi Anjana,
I went through the ndatasource code. There we get
ConfigurationContextSerice/ServerConfiguration/etc. While searching for
their usages found out that we use those references to get clustering
Fixed issue in branch by setting anonymous user as user in auth context.
Thanks.
On Tue, Jan 22, 2013 at 2:59 PM, Amila Suriarachchi am...@wso2.com wrote:
On Tue, Jan 22, 2013 at 1:48 PM, Amila Suriarachchi am...@wso2.comwrote:
On Tue, Jan 22, 2013 at 12:56 PM, Lalaji Sureshika
Hi,
Checking this build log as well as some old once, the building is failing
while checking out .. do we need to check out all the time .. shouldn't
updating be sufficient .. ?! It says *Working directory is empty*, looks
like some issue in config or ways its setup .. full log is at [1]
imple
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20130128T09Z
DTEND:20130128T10Z
DTSTAMP:20130122T134536Z
ORGANIZER;CN=dharsha...@wso2.com:mailto:dharsha...@wso2.com
Hi All,
Is there a solution for the $Subject? As of now all these fail in the
development branch.
Sample error:
testAddNameWithSpacesWSDL(org.wso2.carbon.registry.metadata.test.wsdl.NameWithSpacesWsdlAdditionTestCase)
Time elapsed: 0.141 sec FAILURE!
org.apache.axis2.AxisFault: Failed to
On Tue, Jan 22, 2013 at 7:59 PM, Vijitha Kumara viji...@wso2.com wrote:
Hi All,
Is there a solution for the $Subject? As of now all these fail in the
development branch.
this is due to the recent update of wso2 svn public key certificate since
it was expired. certificate in
---
WSO2 Carbon 4.0.x Products 4.0.6 #78 failed.
---
Code has been updated by eranda, janaka, maninda, vijitha, ashansa, shammi,
nuwand, nirmal, kasun,
Hi guys,
Sure, this can be put as a separated component. As Pradeep said, internally
in the Kernel, we just use JNDI lookups to get the data sources (for
Registry/UM), so we are not directly dependent on it, i.e. someone could
use the Carbon Kernel and another mechanism to register the JNDI data
Hi Vijitha,
Most tests are failed because of below error.
javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Unable to
resolve imported document at '
---
WSO2 Carbon 4.0.x - Nightly Kernel_4.0.6 #17 failed.
---
This build occurred because it is a dependant of WCB002-NORB004-15.
No failed tests found, a
---
WSO2 Carbon 4.0.x Platform 4.0.6 #87 failed.
---
Code has been updated by hasini, sinthuja, ashansa, dimuthul, lalaji, eranda,
janaka, maninda, sanjeewa,
---
WSO2 Carbon 4.0.x Kernel 4.0.6 #32 failed.
---
Code has been updated by tharindu, nuwand.
No failed tests found, a possible compilation error.
Hi,
is the $subject possible?
Cli tool gave me an error while trying to use same alias from two
instances:
for sample (from CLI tool)
subscribe php sampleapp2
Error message thrown at CLI command:
Cartridge subscribe failure
Error while subscribing the cartridge php
--
Ramith Jayasinghe
Correction.
Cli tool gave me an error while trying to use same alias from two
instances:
needs to be corrected as:
Cli tool gave me an error while trying to use same alias from two *tenants
*:
On Tue, Jan 22, 2013 at 4:26 PM, Ramith Jayasinghe ram...@wso2.com wrote:
Hi,
is the $subject
Hi Ajith/Senaka
While going through the kernel code, found out that we are using
UserRegistry as a the reference type within api methods in kernel.
eg: in TenantAxisConfigurator
Why we depend on ConcreteClasses here ? What are the repercussions if i
move them to Registry interface type.? - One
Sorry, wrong mail list. Forwarded to the infra list.
Thanks
Dulanja
On Tue, Jan 22, 2013 at 10:05 AM, Dulanja Liyanage dula...@wso2.com wrote:
Hi,
From yesterday, I'm getting the $subject while running an svn update in
the platform. I tried reverting and cleanup as well.
In the latest
Hi Tharindu
Kernel 4.0.6 build #32 has failed due the following error in User
management;
22-Jan-2013 14:58:04[INFO] WSO2 Carbon - User Management
. FAILURE [1.718s]
22-Jan-2013 14:58:04[INFO]
22-Jan-2013
Hi Shariq
Yes, Updating is sufficient. That is how the plans were configured prior to
the build failures.
This could be due to *unavailability of disk space*, therefore I have
deleted the old artifacts working directory in the bamboo machine for
both the builds.
On Tue, Jan 22, 2013 at 6:10
On Wed, Jan 23, 2013 at 5:56 AM, Ramith Jayasinghe ram...@wso2.com wrote:
Hi,
is the $subject possible?
Cli tool gave me an error while trying to use same alias from two
instances:
for sample (from CLI tool)
subscribe php sampleapp2
Error message thrown at CLI command:
Cartridge
On Jan 23, 2013 8:28 AM, Lahiru Sandaruwan lahi...@wso2.com wrote:
On Wed, Jan 23, 2013 at 5:56 AM, Ramith Jayasinghe ram...@wso2.com
wrote:
Hi,
is the $subject possible?
Cli tool gave me an error while trying to use same alias from two
instances:
for sample (from CLI tool)
On Wed, Jan 23, 2013 at 8:44 AM, Nirmal Fernando nir...@wso2.com wrote:
On Jan 23, 2013 8:28 AM, Lahiru Sandaruwan lahi...@wso2.com wrote:
On Wed, Jan 23, 2013 at 5:56 AM, Ramith Jayasinghe ram...@wso2.com
wrote:
Hi,
is the $subject possible?
Cli tool gave me an error while
Hi all,
when importing wso2 app server examples to developer studio, it has
problem to identify the project nature. To solve i'm trying to set the
project nature as a wso2 project when importing the wso2 app server example
projects to developer studio. To achieve that i add below code
On Wed, Jan 23, 2013 at 9:05 AM, Lahiru Sandaruwan lahi...@wso2.com wrote:
On Wed, Jan 23, 2013 at 8:44 AM, Nirmal Fernando nir...@wso2.com wrote:
On Jan 23, 2013 8:28 AM, Lahiru Sandaruwan lahi...@wso2.com wrote:
On Wed, Jan 23, 2013 at 5:56 AM, Ramith Jayasinghe ram...@wso2.com
Hi,
Getting following compilation error in user.mgt module while building
kernel-4.0.6.
[ERROR] Failed to execute goal org.apache.maven.plugins:
maven-compiler-plugin:2.3.2:compile (default-compile) on project
org.wso2.carbon.user.mgt: Compilation failure
[ERROR]
There has been an API change in the MultipleCredentialUserStoreManager
interface on user core. This is what causes these compilation failures.
Thanks,
NuwanD.
On Wed, Jan 23, 2013 at 9:49 AM, Dinusha Senanayaka dinu...@wso2.comwrote:
Hi,
Getting following compilation error in user.mgt
On Wed, Jan 23, 2013 at 9:27 AM, Nirmal Fernando nir...@wso2.com wrote:
On Wed, Jan 23, 2013 at 9:05 AM, Lahiru Sandaruwan lahi...@wso2.comwrote:
On Wed, Jan 23, 2013 at 8:44 AM, Nirmal Fernando nir...@wso2.com wrote:
On Jan 23, 2013 8:28 AM, Lahiru Sandaruwan lahi...@wso2.com wrote:
On Wed, Jan 23, 2013 at 9:59 AM, Lahiru Sandaruwan lahi...@wso2.com wrote:
On Wed, Jan 23, 2013 at 9:27 AM, Nirmal Fernando nir...@wso2.com wrote:
On Wed, Jan 23, 2013 at 9:05 AM, Lahiru Sandaruwan lahi...@wso2.comwrote:
On Wed, Jan 23, 2013 at 8:44 AM, Nirmal Fernando
This is NOT a limitation. Its the design. Two users cant use same email
address!!!. Right. Think like that. So error message should guide user that
alias already taken by another tenant. Alias is the unique name given
for particular user. Don't forget design decisions.
On Wed, Jan 23, 2013 at
HI
On Wed, Jan 23, 2013 at 8:28 AM, Lahiru Sandaruwan lahi...@wso2.com wrote:
On Wed, Jan 23, 2013 at 5:56 AM, Ramith Jayasinghe ram...@wso2.comwrote:
Hi,
is the $subject possible?
Cli tool gave me an error while trying to use same alias from two
instances:
for sample (from CLI
I'm looking into it...
On Wed, Jan 23, 2013 at 9:56 AM, Nuwan Dias nuw...@wso2.com wrote:
There has been an API change in the MultipleCredentialUserStoreManager
interface on user core. This is what causes these compilation failures.
Thanks,
NuwanD.
On Wed, Jan 23, 2013 at 9:49 AM,
Check now please... sorry for the inconvenience...
On Wed, Jan 23, 2013 at 10:40 AM, Tharindu Mathew thari...@wso2.com wrote:
I'm looking into it...
On Wed, Jan 23, 2013 at 9:56 AM, Nuwan Dias nuw...@wso2.com wrote:
There has been an API change in the MultipleCredentialUserStoreManager
On Wed, Jan 23, 2013 at 8:05 AM, Maheshika Goonetilleke
mahesh...@wso2.comwrote:
Hi Shariq
Yes, Updating is sufficient. That is how the plans were configured prior
to the build failures.
Well I feel the correct model should be to update and build .. if there are
failures in that model we
On Wed, Jan 23, 2013 at 10:43 AM, Tharindu Mathew thari...@wso2.com wrote:
Check now please... sorry for the inconvenience...
Thanks Tharindu.. It works..
Regards,
Dinusha.
On Wed, Jan 23, 2013 at 10:40 AM, Tharindu Mathew thari...@wso2.comwrote:
I'm looking into it...
On Wed, Jan 23,
On Tue, Jan 22, 2013 at 10:58 PM, Anjana Fernando anj...@wso2.com wrote:
Hi guys,
Sure, this can be put as a separated component. As Pradeep said,
internally in the Kernel, we just use JNDI lookups to get the data sources
(for Registry/UM), so we are not directly dependent on it, i.e.
On Wed, Jan 23, 2013 at 10:26 AM, Lakmal Warusawithana lak...@wso2.comwrote:
This is NOT a limitation. Its the design. Two users cant use same email
address!!!. Right. Think like that. So error message should guide user that
alias already taken by another tenant. Alias is the unique name
Hi Amila,
On Tue, Jan 22, 2013 at 9:32 PM, Amila Suriarachchi am...@wso2.com wrote:
On Tue, Jan 22, 2013 at 10:58 PM, Anjana Fernando anj...@wso2.com wrote:
Hi guys,
Sure, this can be put as a separated component. As Pradeep said,
internally in the Kernel, we just use JNDI lookups to get
Hi Folks,
During the last Carbon Architecture meeting, we had a discussion along the
$Subject. The main goal of this process is to limit the number of
Committers in Carbon kernel to regulate the code changes. Once this process
is in place, it will help us to
- Reduce the changes introduced
---
WSO2 Carbon 4.0.x Platform 4.0.6 #89 failed.
---
This build was manually triggered by Maheshika Goonetilleke.
No failed tests found, a possible compilation
+1, thats a good idea, Once its moved to git, and if somebody needs and
does a change they can trigger a pull request where kernel team
can review and merge.
Regards,
/Nuwan
On Wed, Jan 23, 2013 at 11:12 AM, Sameera Jayasoma same...@wso2.com wrote:
Hi Folks,
During the last Carbon
Hi,
I have to agree with Nirmal ( by looking at the user's perspective). given
the fact that tenants isolated from each other and they might find it
irritating to figure out alias chosen by them is already taken (+ is it
possible to figure out alias already taken before hand?)
further, when
On Wed, Jan 23, 2013 at 11:06 AM, Muhammed Shariq sha...@wso2.com wrote:
On Wed, Jan 23, 2013 at 10:26 AM, Lakmal Warusawithana lak...@wso2.comwrote:
This is NOT a limitation. Its the design. Two users cant use same email
address!!!. Right. Think like that. So error message should guide user
On Wed, Jan 23, 2013 at 10:14 AM, Nirmal Fernando nir...@wso2.com wrote:
On Wed, Jan 23, 2013 at 9:59 AM, Lahiru Sandaruwan lahi...@wso2.comwrote:
On Wed, Jan 23, 2013 at 9:27 AM, Nirmal Fernando nir...@wso2.com wrote:
On Wed, Jan 23, 2013 at 9:05 AM, Lahiru Sandaruwan
The samples we have in AS in general are not really great. I was looking at
JAX-WS and JAX-RS services, and they are too primitive.
So adding only DevS project will add little value.
We need
1. Serious samples, those that help learn quickly, then help expand to next
level.
2. Let them all be
Registry in the core. But we are going to keep bare minmal things in the
kernel. For an example we going to remove all UM implementations but keep
the API and a simple file based implementation.
OTOH I think this registry based one can not be used without UI (unless
some one creates a data
I also Happy to have that feature :). But Like Lahiru
mention technically cant give with the current architect. If we going to
give that need some other compromising.
On Wed, Jan 23, 2013 at 11:24 AM, Ramith Jayasinghe ram...@wso2.com wrote:
Hi,
I have to agree with Nirmal ( by looking at
Hi,
please find the $subject at [1].
[1]. http://builder3.us1.wso2.org/builds/AM-1.4.0/RC2/
Regards,
Dinusha.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
On Wed, Jan 23, 2013 at 11:35 AM, Samisa Abeysinghe sam...@wso2.com wrote:
The samples we have in AS in general are not really great. I was looking
at JAX-WS and JAX-RS services, and they are too primitive.
So adding only DevS project will add little value.
We need
1. Serious samples,
On Wed, Jan 23, 2013 at 11:35 AM, Anjana Fernando anj...@wso2.com wrote:
Registry in the core. But we are going to keep bare minmal things in the
kernel. For an example we going to remove all UM implementations but keep
the API and a simple file based implementation.
OTOH I think this
On Wed, Jan 23, 2013 at 11:21 AM, Nuwan Bandara nu...@wso2.com wrote:
+1, thats a good idea, Once its moved to git, and if somebody needs and
does a change they can trigger a pull request where kernel team
can review and merge.
We are going to do this from 4.1.0 release onwards. 4.1.0 and
Hi Suresh,
Have we renamed SAMLSSOProviderConstants.ASSERTION_STR with
SAMLSSOProviderConstants.REQ_MSG_STR? Will replacing just work?
thanks,
dimuthu
On Wed, Jan 2, 2013 at 2:17 PM, sur...@wso2.com wrote:
Author: suresh
Date: Wed Jan 2 14:17:40 2013
New Revision: 152650
URL:
Hi,
On Wed, Jan 23, 2013 at 11:49 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi Suresh,
Have we renamed SAMLSSOProviderConstants.ASSERTION_STR with
SAMLSSOProviderConstants.REQ_MSG_STR? Will replacing just work?
Yes. Just replace it.
Thanks,
-Suresh
thanks,
dimuthu
On Wed,
So do we have trunk back now?
On Wed, Jan 23, 2013 at 11:48 AM, Amila Suriarachchi am...@wso2.com wrote:
On Wed, Jan 23, 2013 at 11:21 AM, Nuwan Bandara nu...@wso2.com wrote:
+1, thats a good idea, Once its moved to git, and if somebody needs and
does a change they can trigger a pull
Hi Susankha,
+1
This is the correct approach.
Thanks and Regards,
Harshana
On Wed, Jan 23, 2013 at 9:19 AM, Susankha Nirmala susan...@wso2.com wrote:
Hi all,
when importing wso2 app server examples to developer studio, it has
problem to identify the project nature. To solve i'm
physically its there, [1]
But i'm working on it and not encouraging anyone to commit. :)
[1] https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/
On Wed, Jan 23, 2013 at 11:51 AM, Samisa Abeysinghe sam...@wso2.com wrote:
So do we have trunk back now?
On Wed, Jan 23, 2013 at 11:48 AM,
Hi Samisa,
On Wed, Jan 23, 2013 at 11:35 AM, Samisa Abeysinghe sam...@wso2.com wrote:
The samples we have in AS in general are not really great. I was looking
at JAX-WS and JAX-RS services, and they are too primitive.
So adding only DevS project will add little value.
We need
1. Serious
Hi Supun,
On Wed, Jan 23, 2013 at 11:44 AM, Supun Malinga sup...@wso2.com wrote:
On Wed, Jan 23, 2013 at 11:35 AM, Samisa Abeysinghe sam...@wso2.comwrote:
The samples we have in AS in general are not really great. I was looking
at JAX-WS and JAX-RS services, and they are too primitive.
On Wed, Jan 23, 2013 at 11:35 AM, Samisa Abeysinghe sam...@wso2.com wrote:
The samples we have in AS in general are not really great. I was looking
at JAX-WS and JAX-RS services, and they are too primitive.
So adding only DevS project will add little value.
We need
1. Serious samples,
Hi Harshana,
On Wed, Jan 23, 2013 at 12:00 PM, Harshana Martin harsh...@wso2.com wrote:
Hi Supun,
On Wed, Jan 23, 2013 at 11:44 AM, Supun Malinga sup...@wso2.com wrote:
On Wed, Jan 23, 2013 at 11:35 AM, Samisa Abeysinghe sam...@wso2.comwrote:
The samples we have in AS in general are
But Amila with our current SVN model, we cannot simply restrict access only
to Carbon kernel project. Either restrict all or nothing. If we need to
implement the partial access model, we need to change the svn structure,
AFAIK.
Thanks,
Sameera.
On Wed, Jan 23, 2013 at 11:48 AM, Amila
---
WSO2 Carbon 4.0.x Products 4.0.6 #80 failed.
---
Code has been updated by ashansa.
No failed tests found, a possible compilation error.
---
WSO2 Carbon 4.0.x Platform 4.0.6 #91 failed.
---
Code has been updated by eranda.
No failed tests found, a possible compilation error.
67 matches
Mail list logo
