Hi,
Completed implementing the user population logic which is one of the
initial task of the test execution cycle. User polulation is supported for
both multi- tenant mode and single-tenant mode.
Implemented a logic to allow users to add custom propertied to the specific
contexts in the
Hi ,
We are automating some aspects of product distributions. I came across a
situation where I need to refer previous releases of a given product.Once
referred to maven repository (eg :
Hi All,
Please note that we'll be doing $subject as there's nobody who's releasing
in chunk-2 using Cassandra related direct dependencies. Do shout if there's
any objection.
Cheers,
Prabath
--
Prabath Abeysekara
Associate Technical Lead, Data TG.
WSO2 Inc.
Email: praba...@wso2.com
Mobile:
Hi Prabath,
Currently BAM and CEP are in chunk-02 and we depend on the cassandra
dependencies. Once Chunk02 is released, the migration of unreleased
components is supposed to be carried out, so till then it will be better if
the Cassandra dependencies are kept.
On Wed, Oct 16, 2013 at 12:19
Hi,
This is fixed. Please take an up of cassandra feature.
Cheers,
Prabath
On Wed, Oct 16, 2013 at 9:05 AM, Prabath Abeysekera praba...@wso2.comwrote:
Hi Lasantha,
Let me have a look.
Cheers,
Prabath
On Wed, Oct 16, 2013 at 1:18 AM, Lasantha Fernando lasan...@wso2.comwrote:
Hi
On 16 October 2013 14:42, Prabath Abeysekera praba...@wso2.com wrote:
Hi,
This is fixed. Please take an up of cassandra feature.
Cheers,
Prabath
Thanks for looking into this..
Thanks,
Lasantha
On Wed, Oct 16, 2013 at 9:05 AM, Prabath Abeysekera praba...@wso2.comwrote:
Hi Lasantha,
Hi,
I created and CBR proxy (with a switch mediator) in our QA setup and When I
invoke it directly from the worker nodes response comes properly back to
the client. But when it is invoked through ELB the response body gets
dropped, only gets a 200OK response.
[1]
Hi,
INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 27:17.805s
[INFO] Finished at: Wed Oct 16 15:26:14 IST 2013
[INFO] Final Memory: 1359M/1835M
Hi,
On Wed, Oct 16, 2013 at 2:05 PM, Prabath Abeysekera praba...@wso2.comwrote:
Hi,
Please ignore my previous mail. Just got to know that there shouldn't
ideally be a chunk-3 SVN locaiton created till its preceding version is
released.
This means we cannot work on releases in parallel,
I am getting this error while trying to deploy a Capp in esb 4.8.0
distribution. I have created Message store and a Message processor and a
faulty Endpoint. AFAIU according to the synchronized Capp deployment
concept ApplicationManager Successfully Deployed Carbon Application :
CApp_1.0.0 should
Still I'm getting this with clean repo. Please have a look.
Regards,
Gihan
On Tue, Oct 8, 2013 at 11:44 AM, Kasun Gajasinghe kas...@wso2.com wrote:
I have fixed this.
Thanks.
On Tue, Oct 8, 2013 at 9:02 AM, Subash Chaturanga sub...@wso2.com wrote:
Hi
Apparently this is due to some
Hi all products teams whose features releasing with chunk 02. $subject
please with the latest versions of your features.
--
Thanks
/subash
*Subash Chaturanga*
Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
email: sub...@wso2.com
blog: http://subashsdm.blogspot.com/
Hi folks,
Please fix,
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4:11.309s
[INFO] Finished at: Wed Oct 16 15:34:30 IST 2013
[INFO] Final
IIRC, Miyuru fixed this at synapse level recently.
On Wed, Oct 16, 2013 at 4:18 PM, Dimuthu De Lanerolle dimut...@wso2.comwrote:
I am getting this error while trying to deploy a Capp in esb 4.8.0
distribution. I have created Message store and a Message processor and a
faulty Endpoint. AFAIU
Hi all, I have already implemented all the code needed to kafka broker. I
made the connection between WSO2 and kafka queue.
I send the events to WSO2 as follows:
**
public class ConsumerTest
Hi Andres,
I couldn't make much decision based on the given information.. But I can
give some comments based on your info. See the comments in line..
On Wed, Oct 16, 2013 at 8:54 PM, andresgomez92 andresgome...@gmail.comwrote:
Hi all, I have already implemented all the code needed to kafka
Hi all,
When I tried to call DSS boxcaring and faced a issue when processing reply
message flow.
for begin boxcar, DSS returns 202 message with content type header.
HTTP/1.1 202 Accepted
Set-Cookie: JSESSIONID=E6D09FBA4BEF0AE451844DE3726E28A5; Path=/; HttpOnly
*Content-Type:
*WSO2 Business Process Server 3.1.0 Alpha Released!*
Date: 16th October 2013
WSO2 Business Process Server team is pleased to announce the release of
3.1.0 Alpha version of WSO2 Business Process Server.
It could be downloaded from h
Hi,
Fixed in 188496. This is due to wrong dependency version and artifact id
inline with new cassandra v10 dependency.
On Wed, Oct 16, 2013 at 3:45 PM, Subash Chaturanga sub...@wso2.com wrote:
Hi,
INFO]
[INFO] BUILD
Hi Mohan,
First, Thank you for your help!!
To verify that my custom broker kafka get events properly! I have thrown an
exception on the line marked / / HERE!! and I could see that the map is
created successfully! I map I can print objects without problems! :) That
map is the same That I send to
$Subject can be found at [1]
[1] http://builder1.us1.wso2.org/~gs2/store/10-17-13/wso2store-1.0.0.zip
--
*Thanks Regards,
Nuwan Bandara
Technical Lead; **WSO2 Inc. *
*lean . enterprise . middleware | http://wso2.com *
*blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 214
Hi Andres,
First, Thank you for your help!!
To verify that my custom broker kafka get events properly! I have thrown an
exception on the line marked / / HERE!! and I could see that the map is
created successfully! I map I can print objects without problems! :) That
map is the same That I
It works perfectly!! THANK YOU :) When I test it a little more if you're
interested in the broker I will give it to you!!
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-Custom-broker-kafka-all-implemented-Error-when-testing-tp87435p87442.html
Sent from the
It works perfectly!! THANK YOU :) When I test it a little more if you're
interested in the broker I will give it to you!!
Oh that's great... : )
If you really like to contribute for this open source project.. Then you
can add your broker in the CEP public jira
Hi Miyuru,
If it is not illegal to do so, then we cannot fix something like that. This
behavior anyway, we are getting from Axis2, not from data services specific
code. Also, I saw in a ESB sample [1], the ESB itself is behaving this way
in responding with HTTP 202.
[1]
Hi IsuruH,
$Subject? If not can you please test it before the release. We (Cloud team)
are going to need it for our deployment and we will also try it from our
end. Wanted to bring it to your attention so that you can fix if there are
any issues before the release.
Regards,
AmilaM.
--
*Amila
Hi AmilaM,
On Thu, Oct 17, 2013 at 9:25 AM, Amila Maha Arachchi ami...@wso2.comwrote:
Hi IsuruH,
$Subject? If not can you please test it before the release. We (Cloud
team) are going to need it for our deployment and we will also try it from
our end. Wanted to bring it to your attention so
Hi Isuru,
On Wed, Oct 16, 2013 at 3:52 PM, Isuru Perera isu...@wso2.com wrote:
Hi,
On Wed, Oct 16, 2013 at 2:05 PM, Prabath Abeysekera praba...@wso2.comwrote:
Hi,
Please ignore my previous mail. Just got to know that there shouldn't
ideally be a chunk-3 SVN locaiton created till its
AFAIR there're not much (if not none) changes in this area. But we should
always test this aspect of ELB.
On Thu, Oct 17, 2013 at 9:32 AM, Isuru Haththotuwa isu...@wso2.com wrote:
Hi AmilaM,
On Thu, Oct 17, 2013 at 9:25 AM, Amila Maha Arachchi ami...@wso2.comwrote:
Hi IsuruH,
$Subject?
Hi,
I am still getting the same error while building Kernal-4.2.0.
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]
[ERROR] The project org.wso2.carbon:SecVerifier:4.2.0
(/home/malintha/projects/carbon-branch-4.2.0/kernel/4.2.0/distribution/integration/security-verifier/pom.xml)
Please grant commit rights to :
Dushan, Miyuru, Kasun
On Mon, Oct 7, 2013 at 1:13 PM, Prabath Abeysekera praba...@wso2.comwrote:
Hi Sumedha,
On Mon, Oct 7, 2013 at 12:18 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
On Mon, Oct 7, 2013 at 11:21 AM, Prabath Abeysekera
Hi,
Thanks Prabath for the explanation. I agree with your points.
I just felt that this is very complicated. i.e. work in one chunk and move
to next when one chunk release is over.
But I cannot really tell, since I'm not working on release work for now and
I do not understand the real
Hi All,
In API-M 1.5.0 there is a api[1] in [2] which takes application name as the
input parameter and returns api information[3]. Moreover it usees the
logged in users' username to get the results along with the application
name.
[1] getSubscriptionByApplication
[2]
Hi,
On Thu, Oct 17, 2013 at 10:01 AM, Isuru Perera isu...@wso2.com wrote:
Hi,
Thanks Prabath for the explanation. I agree with your points.
No prob.
I just felt that this is very complicated. i.e. work in one chunk and move
to next when one chunk release is over.
I guess, it would be
This means that anyone having a valid user account can login and retrieve
subscription information of another user right? If so, isn't it a security
violation?
Thanks,
NuwanD.
On Thu, Oct 17, 2013 at 10:45 AM, Punnadi Gunarathna punn...@wso2.comwrote:
Hi All,
In API-M 1.5.0 there is a
Hi,
$subject is in chunk-01 feature list(/features/ws-discovery)[1], but it's
not available in the nexus repo[2]. This cause build breaks when building
on a clean repo. AFAIK whatever the features listed in the chunk-01 should
be available in the nexus repo. Please check this.
1.
BTW sending a content type header when there is no content is wrong. Yes
it's comes from axis2.
To get things working, only solution is consider 202 as no body messages as
there is no way to check that 202 has a content when content-type header is
present.
On Thu, Oct 17, 2013 at 7:44 AM,
Yes it is a security violation but with the details (apiName, apiVersion,
apiProvider, description, subscribedTier, status) that he can get the
security threat is minimal.
Also we have added a logic to check if the request is from same tenant
domain.
On Thu, Oct 17, 2013 at 10:53 AM, Nuwan Dias
38 matches
Mail list logo
