If I use org.apache.axis2.client.OperationClient and use the method
_operationClient.getOptions().setAction("<--actionName-->"); What would be
the <--actionName-->
Or else is there any other (easy) way?
--
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075
WSO2 Inc. http://wso2.com/
Hi susinda,
What is the exact requirement for this?
Thanks and Regards,
Harshana
On Thu, Oct 10, 2013 at 11:59 PM, Susinda Perera wrote:
> If I use org.apache.axis2.client.OperationClient and use the method
> _operationClient.getOptions().setAction("<--actionName-->"); What would
> be the <
Hi,
While working on removing the part on loading/persisting transport config
from registry I came across several places that that
TransportPersitenceManger class is used. From my understanding the above
class is used to persist/load transport configurations to/from registry.
What I'm thinking is
IIUC, the persistant manager comes in to picture only when we do changes
using UI. However we only do transport cofnigs through config files now...
Hence +1 to removal.
Thanks,
--Pradeep
On Fri, Oct 11, 2013 at 1:29 PM, Kishanthan Thangarajah wrote:
> Hi,
>
> While working on removing the part
Hi Nirmal,
This happens when the window porcessor modifies incoming events instead of
creating new ones and emitting them. In CEP, same event is dispatched to
multiple execution plans without cloning.
So modifying the custom window processor to create a new event with
modified data will solve the
You must not edit the events. Events are read only.
On Fri, Oct 11, 2013 at 2:12 PM, Rajeev Sampath wrote:
>
> Hi Nirmal,
>
> This happens when the window porcessor modifies incoming events instead of
> creating new ones and emitting them. In CEP, same event is dispatched to
> multiple executio
Hi,
On Fri, Oct 11, 2013 at 2:22 PM, Srinath Perera wrote:
> You must not edit the events. Events are read only.
>
>
Yes, But the issue is siddhi extension gives more freedom to do anything to
the event, (actually can even affect the siddhi engine).
Since it is a powerful tool, we have to use i
Rajeev,
On Fri, Oct 11, 2013 at 2:12 PM, Rajeev Sampath wrote:
>
> Hi Nirmal,
>
> This happens when the window porcessor modifies incoming events instead of
> creating new ones and emitting them. In CEP, same event is dispatched to
> multiple execution plans without cloning.
>
In fact I'm crea
I'm not editing events. Please see my above email.
On Fri, Oct 11, 2013 at 2:22 PM, Srinath Perera wrote:
> You must not edit the events. Events are read only.
>
>
> On Fri, Oct 11, 2013 at 2:12 PM, Rajeev Sampath wrote:
>
>>
>> Hi Nirmal,
>>
>> This happens when the window porcessor modifies
On Fri, Oct 11, 2013 at 2:33 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:
> Hi,
>
>
> On Fri, Oct 11, 2013 at 2:22 PM, Srinath Perera wrote:
>
>> You must not edit the events. Events are read only.
>>
>>
> Yes, But the issue is siddhi extension gives more freedom to do anything
>
On 11 October 2013 15:10, Nirmal Fernando wrote:
> Rajeev,
>
>
> On Fri, Oct 11, 2013 at 2:12 PM, Rajeev Sampath wrote:
>
>>
>> Hi Nirmal,
>>
>> This happens when the window porcessor modifies incoming events instead
>> of creating new ones and emitting them. In CEP, same event is dispatched to
On Fri, Oct 11, 2013 at 3:18 PM, Lasantha Fernando wrote:
>
>
>
> On 11 October 2013 15:10, Nirmal Fernando wrote:
>
>> Rajeev,
>>
>>
>> On Fri, Oct 11, 2013 at 2:12 PM, Rajeev Sampath wrote:
>>
>>>
>>> Hi Nirmal,
>>>
>>> This happens when the window porcessor modifies incoming events instead
>>
Lasantha,
Yes, that was the issue. Thanks.
Just for my information, why don't you guys clone events and give them to
the different execution plans? Is it a performance hit? Wouldn't keeping a
reference harms the mutual exclusiveness?
On Fri, Oct 11, 2013 at 3:25 PM, Nirmal Fernando wrote:
>
>
Still we are getting this on clustered setup.
TID: [0] [ELB] [2013-10-11 15:21:47,364] WARN {org.apache.synapse.transport
.passthru.TargetHandler} - http-outgoing-344: Connection time out while in
state: REQUEST_DONE {org.apache.synapse.transport.passthru.TargetHandler}
TID: [0] [ELB] [2013-10-1
Hi,
Chunk-02 build failing with bellow error.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 13:39.990s
[INFO] Finished at: Fri Oct 11 15:55:31
Hi,
Please ignore this.. This was due to a missing update.
Thank You.
Ranga.
On Fri, Oct 11, 2013 at 4:30 PM, Ranga Siriwardena wrote:
> Hi,
>
> Chunk-02 build failing with bellow error.
>
> [INFO]
>
> [INFO] BUILD FAILU
Hi Nirmal,
On 11 October 2013 15:35, Nirmal Fernando wrote:
> Lasantha,
>
> Yes, that was the issue. Thanks.
>
Great to hear that!..
>
> Just for my information, why don't you guys clone events and give them to
> the different execution plans? Is it a performance hit? Wouldn't keeping a
> ref
On Fri, Oct 11, 2013 at 4:44 PM, Lasantha Fernando wrote:
> Hi Nirmal,
>
>
> On 11 October 2013 15:35, Nirmal Fernando wrote:
>
>> Lasantha,
>>
>> Yes, that was the issue. Thanks.
>>
>
> Great to hear that!..
>
>>
>> Just for my information, why don't you guys clone events and give them to
>> the
BTW thanks everyone, I'm glad that I was wrong!
On Fri, Oct 11, 2013 at 4:50 PM, Nirmal Fernando wrote:
>
>
>
> On Fri, Oct 11, 2013 at 4:44 PM, Lasantha Fernando wrote:
>
>> Hi Nirmal,
>>
>>
>> On 11 October 2013 15:35, Nirmal Fernando wrote:
>>
>>> Lasantha,
>>>
>>> Yes, that was the issue.
On Fri, Oct 11, 2013 at 4:50 PM, Nirmal Fernando wrote:
>
>
>
> On Fri, Oct 11, 2013 at 4:44 PM, Lasantha Fernando wrote:
>
>> Hi Nirmal,
>>
>>
>> On 11 October 2013 15:35, Nirmal Fernando wrote:
>>
>>> Lasantha,
>>>
>>> Yes, that was the issue. Thanks.
>>>
>>
>> Great to hear that!..
>>
>>>
>>>
Hi Nirmal,
It is a performance hit. Also note cases where we edit the events are rare
(and happen when you write extensions only).
--Srinath
On Fri, Oct 11, 2013 at 4:50 PM, Nirmal Fernando wrote:
>
>
>
> On Fri, Oct 11, 2013 at 4:44 PM, Lasantha Fernando wrote:
>
>> Hi Nirmal,
>>
>>
>> On 11
On Fri, Oct 11, 2013 at 4:56 PM, Srinath Perera wrote:
> Hi Nirmal,
>
> It is a performance hit. Also note cases where we edit the events are rare
> (and happen when you write extensions only).
>
Agree, thanks.
>
> --Srinath
>
>
> On Fri, Oct 11, 2013 at 4:50 PM, Nirmal Fernando wrote:
>
>>
>>
Hi,
I came across a some weird behavior . The scenario is mentioned below.
There is a service , and it has been exposed as OSGI service and a Axis2
service.
in the service xml,
Authorization action parameter is set to /permission/admin.
This is called as an osgi service in the jaggery , using
s
Hi,
https://wso2.org/jira/browse/APIMANAGER-1725 Issue got resolved when
disabling caching. But https://wso2.org/jira/browse/APIMANAGER-1754 could
be reproduced even the caching was disabled.
Thanks!
On Wed, Oct 9, 2013 at 11:00 PM, Sumedha Rubasinghe wrote:
> Chamara,
> Both of these issues
The second issue pointed here was an issue in the configuration. Fixing the
configuration fixed the problem.
Thanks,
NuwanD.
On Fri, Oct 11, 2013 at 5:17 PM, Ushani Balasooriya wrote:
> Hi,
>
> https://wso2.org/jira/browse/APIMANAGER-1725 Issue got resolved when
> disabling caching. But https:
Hi All,
Is there a way to do $subject. Because the user story as below.
Tenant admin imports users to the tenant with a default password.
Users are asked to change their passwords on the first login.
How can we identify the first login of the user?
We are using a LDAP as the user store.
--
*As
I think we can do this using password policy extensions that we have
introduced for 4.2.0 release. We may need to write new extension for
this... This would be a good use case... I guess, Chamath can help you on
this
Thanks,
Asela.
On Fri, Oct 11, 2013 at 6:52 PM, Asanka Dissanayake wrote:
HI AsankaD,
On Fri, Oct 11, 2013 at 5:15 PM, Asanka Dissanayake wrote:
> Hi,
> I came across a some weird behavior . The scenario is mentioned below.
>
> There is a service , and it has been exposed as OSGI service and a Axis2
> service.
> in the service xml,
>
Why this is exposed both ways?
Hi KasunG,
There seems to be some tight dependency between ServicePersistenceManager
(SPM) and TransportPersistenceManger (TPM).
For example SPM uses some methods from TPM to retrieve transport related
resources from registry and then add those values to service meta file for
persisting. I know t
Hi Kishanthan,
After going through the ServicePersistenceManager, it seems we use it to
see whether a given transport is enabled in the running instance. Since all
the available transports persist the transport config by design (via
org.wso2.carbon.transport. bundles), this mechanism has
been chos
It seems API does not support for tracing unlike proxy services is this
intentional ? IMHO tracing is important for API as well. If there is no
specific reason I can incorporate tracing also with my per API logging
configuration improvements WDYT ?
Thanks !
--
Sagara Gunathunga
Senior Technic
Please fix these issues.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project org.wso2.carbon.apimgt.impl: Compilation
failure
[ERROR]
/home/janaka/work/wso2/carbon/platform/branches/4.2.0/components/apimgt/org.wso2.carbon.apimgt.
*WSO2 Enterprise Store 1.0.0 Beta-1 Released !*
This is the Beta-1 release of WSO2 Enterprise Store, which will create a
marketplace for your enterprise assets. You can download the Beta-1 at [1].
This release specifically contains following tasks, improvements and bug
fixes towards 1.0.0 GA.
*Bu
Hi ,
Please commit [1] to carbon kernal 4.2.0
[1] https://wso2.org/jira/browse/CARBON-14515
cheers,
Asanka D
--
*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware | wso2.com*
*
email: asan...@wso2.com , blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpre
Hi Kishanthan,
Thanks for the quick resposne.Please find answers inline.
cheers,
Asanka D
On Fri, Oct 11, 2013 at 7:25 PM, Kishanthan Thangarajah wrote:
> HI AsankaD,
>
>
> On Fri, Oct 11, 2013 at 5:15 PM, Asanka Dissanayake wrote:
>
>> Hi,
>> I came across a some weird behavior . The scenario
35 matches
Mail list logo
