On Thu, Apr 18, 2013 at 9:28 AM, Sumedha Rubasinghe sume...@wso2.comwrote:
On a general note, does this mean when there are kernel patches involved,
we should change the server start up command to include -DapplyPatches ?
Kind of complicated for users. Isn't it?
Can't we do this first ship a
On Tue, Apr 23, 2013 at 12:01 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
On Thu, Apr 18, 2013 at 9:28 AM, Sumedha Rubasinghe sume...@wso2.comwrote:
On a general note, does this mean when there are kernel patches involved,
we should change the server start up command to include
Hi All,
Any specific reason for this? Since patch0001 is not yet released, we can
still add those components in patch0002 [1] to 0001.
Thanks,
Kishanthan.
[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.1.0/patches/patch0002/
--
*Kishanthan Thangarajah*
Software Engineer,
---
Developer Studio Eclipse-Tools #916 failed.
---
Code has been updated by Viraj Rajaguru.
No failed tests found, a possible compilation error.
---
Developer Studio Eclipse-Tools #917 was successful.
---
Code has been updated by Harshana Martin.
http://wso2.org/bamboo/browse/DS0001-DSET01-917/
Hi Amila,
The relationship between dynamic queue support of the Message Broker and
the requirement to declare
queue name in the jndi.properties file of ESB is some thing different.
Though we had dynamic queue support in MB 1.x versions, still we had to
declare the queue name in the
On Mon, Apr 22, 2013 at 9:38 PM, Eranda Sooriyabandara era...@wso2.comwrote:
Hi Sanjeewa,
On Mon, Apr 22, 2013 at 6:59 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi All,
I'm executing following code block to create wsdl and add it to registry.
But if i entered wsdl url which does not
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
On Tue, Apr 23, 2013 at 12:30 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
Hi All,
Any specific reason
Yes, thats why i suggested adding -DapplyPatches to server script by
default.
On Tue, Apr 23, 2013 at 12:08 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
On Tue, Apr 23, 2013 at 12:01 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
On Thu, Apr 18, 2013 at 9:28 AM, Sumedha
On Tue, Apr 23, 2013 at 4:26 PM, Pradeep Fernando prad...@wso2.com wrote:
Yes, thats why i suggested adding -DapplyPatches to server script by
default.
+1
We need to add this from carbon level so all servers get that.
thanks,
On Tue, Apr 23, 2013 at 12:08 PM, Sanjeewa Malalgoda
Any suggestions?
Thanks,
Muhammad
On 15 April 2013 13:06, Mohammad Benslimne mohammad.benslim...@gmail.comwrote:
Hi all,
Setting the parameter max.delivery.attempts will desactive forever the
message processor?
Is there any way to re-activate it (non manually)?
Thanks in advance
Any suggestions guys?
Thanks,
Muhammad
On 19 April 2013 16:18, Mohammad Benslimne mohammad.benslim...@gmail.comwrote:
Any suggestions, geeks?
Thanks,
Mohammad
On 17 April 2013 16:46, Mohammad Benslimne
mohammad.benslim...@gmail.comwrote:
H all,
I am developping a class mediator and
Getting the same error in the latest trunk as well.
Thanks,
Hasini.
On Mon, Apr 22, 2013 at 1:11 PM, Johann Nallathamby joh...@wso2.com wrote:
Hi,
This is due to the new user.core API changes. This code needs to be
updated to work with the new user.core.
Thanks,
Johann.
On Mon, Apr
13 matches
Mail list logo