date:20130423

[Dev] Fwd: [Commits] [Carbon-platform] svn commit r153055 - in carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template: . parser

2013-04-23 Thread Miyuru Wanninayaka

Hi Sanjeewa,

This cause a test fail in synapse URITemplateBasedDispatcherTest

 resource.setDispatcherHelper(new
URITemplateHelper("/dictionary/{char}/{word}"));
does not accept

synCtx = getMessageContext(synapseConfig, false, "/dictionary/d/dog/",
"GET");

Note and training /

-- Forwarded message --
From: 
Date: Fri, Jan 11, 2013 at 2:06 PM
Subject: [Commits] [Carbon-platform] svn commit r153055 - in
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template:
. parser
To: comm...@wso2.org


Author: sanjeewa
Date: Fri Jan 11 14:06:54 2013
New Revision: 153055
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=153055

Log:
adding improvements for uri template

Modified:

 
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/URITemplate.java

 
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/parser/Node.java

Modified:
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/URITemplate.java
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/URITemplate.java?rev=153055&r1=153054&r2=153055&view=diff
==
---
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/URITemplate.java
   (original)
+++
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/URITemplate.java
   Fri Jan 11 14:06:54 2013
@@ -40,9 +40,9 @@
 }

 public boolean matches(String uri, Map variables) {
-if (uri.endsWith("/") && uri.length() > 1) {
+/* if (uri.endsWith("/") && uri.length() > 1) {
 uri = uri.substring(0, uri.length() - 1);
-}
+}*/
 return syntaxTree.matchAll(uri, variables) == uri.length();
 }
 }

Modified:
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/parser/Node.java
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/parser/Node.java?rev=153055&r1=153054&r2=153055&view=diff
==
---
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/parser/Node.java
   (original)
+++
carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template/parser/Node.java
   Fri Jan 11 14:06:54 2013
@@ -54,7 +54,8 @@
 } else {
 // We have more content in the URI to match
 // But there aren't any nodes left to match against
-return -1;
+// return -1;
+return matchLength;
 }
 } else if (matchLength == uriFragment.length() && next != null) {
 // We have matched all the characters in the URI
___
Commits mailing list
comm...@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/commits



-- 
Miyuru Wanninayaka
Senior Software Engineer - WSO2 Inc
+94-772099788
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Trunk] Build failed in appfactory components

2013-04-23 Thread Johann Nallathamby

Hi,

Fixed in r170968.

Thanks,
Johann.


On Wed, Apr 24, 2013 at 11:14 AM, Hasini Gunasinghe  wrote:

> Getting the same error in the latest trunk as well.
>
> Thanks,
> Hasini.
>
>
> On Mon, Apr 22, 2013 at 1:11 PM, Johann Nallathamby 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 22, 2013 at 12:52 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Getting the following error in platform trunk. Please fix this.
>>>
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 21.980s
>>> [INFO] Finished at: Mon Apr 22 12:39:11 IST 2013
>>> [INFO] Final Memory: 237M/1119M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>> (default-compile) on project org.wso2.carbon.appfactory.userstore:
>>> Compilation failure: Compilation failure:
>>> [ERROR]
>>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[32,19]
>>> authenticate(java.lang.String,java.lang.Object) in
>>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>>> authenticate(java.lang.String,java.lang.Object) in
>>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>>> method is final
>>> [ERROR]
>>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[45,20]
>>> listUsers(java.lang.String,int) in
>>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>>> listUsers(java.lang.String,int) in
>>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>>> method is final
>>> [ERROR]
>>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[66,16]
>>> addUser(java.lang.String,java.lang.Object,java.lang.String[],java.util.Map,java.lang.String,boolean)
>>> in org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>>> addUser(java.lang.String,java.lang.Object,java.lang.String[],java.util.Map,java.lang.String,boolean)
>>> in org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>>> method is final
>>> [ERROR]
>>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[77,16]
>>> updateCredentialByAdmin(java.lang.String,java.lang.Object) in
>>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>>> updateCredentialByAdmin(java.lang.String,java.lang.Object) in
>>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>>> method is final
>>> [ERROR] -> [Help 1]
>>> [ERROR]
>>>
>>> Thanks,
>>> Kishanthan.
>>> --
>>> *Kishanthan Thangarajah*
>>> Software Engineer,
>>> Development Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com*
>>> Twitter - *http://twitter.com/kishanthan*
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Trunk] Build failed in appfactory components

2013-04-23 Thread Hasini Gunasinghe

Getting the same error in the latest trunk as well.

Thanks,
Hasini.


On Mon, Apr 22, 2013 at 1:11 PM, Johann Nallathamby  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 22, 2013 at 12:52 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi,
>>
>> Getting the following error in platform trunk. Please fix this.
>>
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 21.980s
>> [INFO] Finished at: Mon Apr 22 12:39:11 IST 2013
>> [INFO] Final Memory: 237M/1119M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.appfactory.userstore:
>> Compilation failure: Compilation failure:
>> [ERROR]
>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[32,19]
>> authenticate(java.lang.String,java.lang.Object) in
>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>> authenticate(java.lang.String,java.lang.Object) in
>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>> method is final
>> [ERROR]
>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[45,20]
>> listUsers(java.lang.String,int) in
>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>> listUsers(java.lang.String,int) in
>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>> method is final
>> [ERROR]
>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[66,16]
>> addUser(java.lang.String,java.lang.Object,java.lang.String[],java.util.Map,java.lang.String,boolean)
>> in org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>> addUser(java.lang.String,java.lang.Object,java.lang.String[],java.util.Map,java.lang.String,boolean)
>> in org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>> method is final
>> [ERROR]
>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[77,16]
>> updateCredentialByAdmin(java.lang.String,java.lang.Object) in
>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>> updateCredentialByAdmin(java.lang.String,java.lang.Object) in
>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>> method is final
>> [ERROR] -> [Help 1]
>> [ERROR]
>>
>> Thanks,
>> Kishanthan.
>> --
>> *Kishanthan Thangarajah*
>> Software Engineer,
>> Development Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com*
>> Twitter - *http://twitter.com/kishanthan*
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Detect client timeout in a class mediator

2013-04-23 Thread Mohammad Benslimne

Any suggestions guys?

Thanks,
Muhammad

On 19 April 2013 16:18, Mohammad Benslimne wrote:

> Any suggestions, geeks?
>
> Thanks,
> Mohammad
>
>
> On 17 April 2013 16:46, Mohammad Benslimne 
> wrote:
>
>> H all,
>>
>> I am developping a class mediator and I need to test if the client have
>> reached its timeout to stop mediator processing, else the later keeps
>> running in background!
>> Please can you help me out?
>>
>> Thanks in advance
>>
>> --
>>
>>
>> Mohammad
>>
>
>
>
> --
>
>
> Mohammad
>



-- 


Mohammad
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Message processor's max.delivery.attempts not considered

2013-04-23 Thread Mohammad Benslimne

Any suggestions?

Thanks,
Muhammad

On 15 April 2013 13:06, Mohammad Benslimne wrote:

> 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
> Regards,
> Muhammad
>
>
>
> On 11 April 2013 09:01, Mohammad Benslimne 
> wrote:
>
>> Thank you Prabath for your intervention
>> In fact we are using 4.5.0, it's a bug of 4.5.x versions ?
>>
>> Regards,
>> Muhammad
>>
>>
>> On 10 April 2013 22:39, Prabath Abeysekera  wrote:
>>
>>> Hi,
>>>
>>> Please ignore my previous reply.
>>>
>>> I've gone through the attached configurations and thought there was
>>> nothing wrong in them except for setting the property FORCE_SC_ACCEPTED
>>> within the fault sequence, as it wouldn't make any sense to define it in
>>> the fault sequence.
>>>
>>> However, I've tried a sample scenario with the provided configurations
>>> (ESB v4.6.0) and observed that the message processor honors the
>>> max.delivery.attempts parameter value without any issue. Therefore, I'm
>>> guessing this might have to do something with the ESB version you're using
>>> as we'd come across a similar problem with one of the earlier ESB versions
>>> [1].
>>>
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-1688
>>>
>>>
>>> Cheers,
>>> Prabath
>>>
>>>
>>> On Wed, Apr 10, 2013 at 7:36 AM, Prabath Abeysekera 
>>> wrote:
>>>
 Try setting,  within your proxy
 configuration before you dump the message into the store.

 IMO, it would be fundamentally inappropriate to let the ESB wait for a
 response of a message dispatched out of the combination of message
 store/processor as those two entities have been designed primarily to
 support asynchronous messaging.

 Hope this helps!


 Cheers,
 Prabath

 On Tue, Apr 9, 2013 at 4:40 PM, Shelan Perera  wrote:

> Hi,
>
> Could you please remove  value="true" scope="axis2" type="STRING"/> from your proxy and try again?.
> ESB should be waiting for a response  and hence can be
> retrying.
>
> Thanks
>
>
> On Tue, Apr 9, 2013 at 11:42 AM, Mohammad Benslimne <
> mohammad.benslim...@gmail.com> wrote:
>
>> Please, any help ?
>>
>>
>> On 3 April 2013 11:41, Mohammad Benslimne <
>> mohammad.benslim...@gmail.com> wrote:
>>
>>> Hi folks,
>>>
>>> I am implementing a dead letter channel using message store and
>>> processor as described in attached files, and I would like to stop retry
>>> after max.delivery.attempts and send a timeout fault
>>> But the value specified in max.delivery.attempts is not considered
>>> and message processor keeps retrying indefinitely.
>>> Is it a wrong configuration of my receipt or a bug in your side?
>>>
>>> Thanks in advance for your help!
>>>
>>> Regards,
>>>
>>> --
>>>
>>>
>>> Mohammad
>>>
>>
>>
>>
>> --
>>
>>
>> Mohammad
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Shelan Perera*
>
> Software Engineer
> **
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Home Page*  :   shelan.org
> *Blog* :   blog.shelan.org
> *Linked-i*n  :
> http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Prabath Abeysekara
 Email: praba...@wso2.com 
 Mobile: +94774171471

 

>>>
>>>
>>>
>>> --
>>> Prabath Abeysekara
>>> Email: praba...@wso2.com 
>>> Mobile: +94774171471
>>>
>>> 
>>>
>>
>>
>>
>> --
>>
>>
>> Mohammad
>>
>
>
>
> --
>
>
> Mohammad
>



-- 


Mohammad
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Manager 1.4.0 - RC1

2013-04-23 Thread Supun Malinga

On Tue, Apr 23, 2013 at 4:26 PM, Pradeep Fernando  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 wrote:
>
>>
>>
>> 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 wrote:
>>>
 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 patch applied pack for release?

>>>
>>> I think we can't do this. Because, If we do this, then the distribution
>>> size will become double.
>>>
>> +1 same set of jars available in plugins and patches due to the change in
>> single jar file. In that case we can remove all jars in plugins folder.
>>
>> Thanks.
>> Sanjeewa.
>>
>>>
>>>


 On Wed, Apr 17, 2013 at 2:18 PM, Nuwan Dias  wrote:

> It is shipped and the server by default starts with -DapplyPatches.
>
> Thanks,
> NuwanD.
>
>
> On Wed, Apr 17, 2013 at 2:07 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi NuwanD,
>>
>> Please make sure that kernel patch0001 gets shipped with AM
>> distribution.
>>
>> Thanks,
>> Kishanthan.
>>
>>
>> On Wed, Apr 17, 2013 at 1:17 PM, Nuwan Dias  wrote:
>>
>>>  Hi,
>>>
>>> Please find the API Manager 1.4.0 RC1 pack from [1].
>>>
>>> Note that if running in multi-tenant mode, the API Gateway needs to
>>> be run with NHTTP transport (default transport is pass-through).
>>>
>>> Switching to nhttp can be done by overriding the axis2.xml
>>> (AM_HOME/repository/conf/axis2/axis2.xml) file with the axis2.xml_NHTTP
>>> file. Similarly, switching back to pass-through can be done by 
>>> overriding
>>> the axis2.xml with the axis2.xml_PT file.
>>>
>>> [1] - http://builder3.us1.wso2.org/builds/17-Apr-2013/
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Software Engineer - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Software Engineer,
>> Development Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com*
>> Twitter - *http://twitter.com/kishanthan*
>>
>
>
>
> --
> Nuwan Dias
>
> Member, Management Committee - Solutions Technology Group
>
> Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 /sumedha
 m: +94 773017743
 b :  bit.ly/sumedha

>>>
>>>
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Software Engineer,
>>> Development Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com*
>>> Twitter - *http://twitter.com/kishanthan*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +14084122175 | +94713068779
>>
>>  blog
>> :http://sanjeewamalalgoda.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pradeep Fernando*
> Member, Management Committee - Platform & Cloud Technologies
> Senior Software Engineer;WSO2 Inc.; http://wso2.com
>
> blog: http://pradeepfernando.blogspot.com
> m: +94776603662
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Manager 1.4.0 - RC1

2013-04-23 Thread Pradeep Fernando

Yes, thats why i suggested adding -DapplyPatches to server script by
default.


On Tue, Apr 23, 2013 at 12:08 PM, Sanjeewa Malalgoda wrote:

>
>
> 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 wrote:
>>
>>> 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 patch applied pack for release?
>>>
>>
>> I think we can't do this. Because, If we do this, then the distribution
>> size will become double.
>>
> +1 same set of jars available in plugins and patches due to the change in
> single jar file. In that case we can remove all jars in plugins folder.
>
> Thanks.
> Sanjeewa.
>
>>
>>
>>>
>>>
>>> On Wed, Apr 17, 2013 at 2:18 PM, Nuwan Dias  wrote:
>>>
 It is shipped and the server by default starts with -DapplyPatches.

 Thanks,
 NuwanD.


 On Wed, Apr 17, 2013 at 2:07 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> Hi NuwanD,
>
> Please make sure that kernel patch0001 gets shipped with AM
> distribution.
>
> Thanks,
> Kishanthan.
>
>
> On Wed, Apr 17, 2013 at 1:17 PM, Nuwan Dias  wrote:
>
>>  Hi,
>>
>> Please find the API Manager 1.4.0 RC1 pack from [1].
>>
>> Note that if running in multi-tenant mode, the API Gateway needs to
>> be run with NHTTP transport (default transport is pass-through).
>>
>> Switching to nhttp can be done by overriding the axis2.xml
>> (AM_HOME/repository/conf/axis2/axis2.xml) file with the axis2.xml_NHTTP
>> file. Similarly, switching back to pass-through can be done by overriding
>> the axis2.xml with the axis2.xml_PT file.
>>
>> [1] - http://builder3.us1.wso2.org/builds/17-Apr-2013/
>>
>> Thanks,
>> NuwanD.
>>
>> --
>> Nuwan Dias
>>
>> Software Engineer - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Software Engineer,
> Development Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>



 --
 Nuwan Dias

 Member, Management Committee - Solutions Technology Group

 Software Engineer - WSO2, Inc. http://wso2.com
 email : nuw...@wso2.com
 Phone : +94 777 775 729

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> /sumedha
>>> m: +94 773017743
>>> b :  bit.ly/sumedha
>>>
>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Software Engineer,
>> Development Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com*
>> Twitter - *http://twitter.com/kishanthan*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +14084122175 | +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pradeep Fernando*
Member, Management Committee - Platform & Cloud Technologies
Senior Software Engineer;WSO2 Inc.; http://wso2.com

blog: http://pradeepfernando.blogspot.com
m: +94776603662
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why kernel patch0002 is added already?

2013-04-23 Thread Miyuru Wanninayaka

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 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,
> Development Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>



-- 
Miyuru Wanninayaka
Senior Software Engineer - WSO2 Inc
+94-772099788
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Registry become unusable after adding wrong wsdl

2013-04-23 Thread Sanjeewa Malalgoda

On Mon, Apr 22, 2013 at 9:38 PM, Eranda Sooriyabandara wrote:

> Hi Sanjeewa,
>
>
> On Mon, Apr 22, 2013 at 6:59 PM, Sanjeewa Malalgoda wrote:
>
>> 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 exists it gives following error.
>> In addition to that registry become totally unusable until we restart
>> server. I have tested scenario in standalone pack and distributed
>> setup(mysql and shared registry). Please let us know what is the issue here.
>>
>> Thanks.
>> Sanjeewa.
>>
>> Code block
>> 
>> WsdlManager wsdlManager = new WsdlManager(registry);
>> Wsdl wsdl = wsdlManager.newWsdl(wsdlUrl);
>> wsdlManager.addWsdl(wsdl);
>>
>
>
> Use Governance Registry instead normal registry should solve the problem.
> Governance Registry can be obtain using the following code.
>
> Registry governanceRegistry =
> GovernanceUtils.getGovernanceUserRegistry(registry, username);
>
Hi Eranda,
I'm getting registry as  follows which is the same way you mentioned.

this.registry = ServiceReferenceHolder.getInstance().

getRegistryService().getGovernanceUserRegistry(tenantUserName, tenantId);

Any idea?

Thanks,
Sanjeewa

>
> thanks
> Eranda
>
>
>>
>>
>> Server Log
>> ---
>> [2013-04-22 18:52:32,026] ERROR - GovernanceUtils Error in getting the
>> result for media type: application/vnd.wso2.registry-ext-type+xml.
>> org.wso2.carbon.registry.core.exceptions.RegistryException: Timeout
>> trying to lock table "REG_RESOURCE"; SQL statement:
>> SELECT DISTINCT REG_PATH_ID, REG_NAME FROM REG_RESOURCE WHERE
>> (REG_RESOURCE.REG_TENANT_ID=?) AND  REG_MEDIA_TYPE=? [50200-140]
>>  at
>> org.wso2.carbon.registry.core.jdbc.dataaccess.SQLQueryProcessor.executeQuery(SQLQueryProcessor.java:242)
>> at
>> org.wso2.carbon.registry.core.jdbc.queries.QueryProcessorManager.executeQuery(QueryProcessorManager.java:137)
>>  at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.executeQuery(EmbeddedRegistry.java:2276)
>> at
>> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.executeQuery(CacheBackedRegistry.java:354)
>>  at
>> org.wso2.carbon.registry.core.session.UserRegistry.executeQuery(UserRegistry.java:1252)
>> at
>> org.wso2.carbon.governance.api.util.GovernanceUtils.getResultPaths(GovernanceUtils.java:176)
>>  at
>> org.wso2.carbon.governance.api.util.GovernanceUtils.findGovernanceArtifacts(GovernanceUtils.java:119)
>> at
>> org.wso2.carbon.governance.api.util.GovernanceUtils.findGovernanceArtifactConfigurations(GovernanceUtils.java:398)
>>  at
>> org.wso2.carbon.governance.api.util.GovernanceUtils.loadGovernanceArtifacts(GovernanceUtils.java:226)
>> at
>> org.wso2.carbon.apimgt.impl.utils.APIUtil.getArtifactManager(APIUtil.java:622)
>>  at
>> org.wso2.carbon.apimgt.impl.AbstractAPIManager.getAllAPIs(AbstractAPIManager.java:239)
>> at
>> org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsFunction_getAllAPIs(APIProviderHostObject.java:997)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>>  at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
>> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:411)
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:119)
>> at
>> org.jaggeryjs.rhino.publisher.modules.api.c2._c3(/publisher/modules/api/list.jag:97)
>>  at
>> org.jaggeryjs.rhino.publisher.modules.api.c2.call(/publisher/modules/api/list.jag)
>> at
>> org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2347)
>>  at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:272)
>> at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:127)
>>  at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:76)
>> at
>> org.jaggeryjs.rhino.publisher.modules.api.c0._c8(/publisher/modules/api/module.jag:31)
>>  at
>> org.jaggeryjs.rhino.publisher.modules.api.c0.call(/publisher/modules/api/module.jag)
>> at
>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:119)
>>  at
>> org.jaggeryjs.rhino.publisher.site.blocks.listing.c0._c3(/publisher/site/blocks/listing/block.jag:37)
>> at
>> org.jaggeryjs.rhino.publisher.site.blocks.listing.c0.call(/publisher/site/blocks/listing/block.jag)
>>  at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:66)
>> at
>> org.jaggeryjs.rhino.publisher.jagg.c0._c30(/publisher/jagg/jagg.jag:211)
>>  at org.jaggeryjs.rhino.publisher.jagg.c0.call(/publisher/jagg/jagg.jag)
>> at
>> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:97)
>>  at
>> org.jaggeryjs.rhino.publisher.jagg.c0._c31(/publisher/jagg/jagg.jag:274)
>> at org.jaggeryjs.rhino.publisher.ja

Re: [Dev] MB 2.0.x not supporting dynamic queues

2013-04-23 Thread Shammi Jayasinghe

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 jndi.properties file of ESB. That was
according to the implementation of the axis2 jms transport.

In JMS transport implementation, first it do a lookup in the initial
context for a queue name and if it does not found it will throw a name not
found exception. In that catch block, it try to do a look up by adding
"dynamicQueue/" prefix to the destination as bellow;

* public static Destination lookupDestination(Context context, String
destinationName,*
*String destinationType)
throws NamingException {*
*
*
*if (destinationName == null) {*
*return null;*
*}*
*
*
*try {*
*return JMSUtils.lookup(context, Destination.class,
destinationName);*
*} catch (NameNotFoundException e) {*
*try {*
*return JMSUtils.lookup(context, Destination.class,*
*
(JMSConstants.DESTINATION_TYPE_TOPIC.equalsIgnoreCase(destinationType) ?*
*"dynamicTopics/" : "dynamicQueues/") +
destinationName);*
*} catch (NamingException x) {*
*log.warn("Cannot locate destination : " + destinationName);
*
*throw x;*
*}*
*} catch (NamingException e) {*
*log.warn("Cannot locate destination : " + destinationName, e);*
*throw e;*
*}*
*}*
*
*
 So As we know, we have this kind of a dynamic queue declaration support in
ActiveMQ [1]. Because of that using this JMS transport implementation , it
is possible to create queues in ActiveMQ though they are not defined in the
jndi.properties file. But if we are using other JMS brokers, there dynamic
queue declaration scenario is some thing different from the way for
ActiveMQ. *
*

As Danushka mentioned we had dynamic queue support in MB 1.x versions. In
that we created those queues as follows.
*
*
* Queue queue = queueSession.createQueue(queueName + ";{create:always,
node:{durable: True}}");*

Currently we do not have that support in MB 2.x version due to a AMQP
protocol version (0.91) limitation and we will work on to provide that.

Any how though we provide dynamic queue creation support in the above way,
we ll have to change the JMS transport to achieve above mentioned
requirement and it should do the queue declaration according to the broker.
I ll send a separate mail on that to architecture list on changing the jms
transport implementation to provide dynamic queue support with MB 2.x ,
once we able to provide that support for MB 2.x versions.

Thanks
Shammi

[1]http://activemq.apache.org/jndi-support.html

On Mon, Apr 22, 2013 at 9:46 AM, Amila Maha Arachchi wrote:

> Hi Shammi,
>
> When we try to integrate ESB with MB 2.0.x, if we want to send messages to
> a queue in MB, we need to have an entry in the jndi.properties file. But in
> MB 1.x, AFAIR it supported dynamicQueue property. Editing the
> jndi.properties file means we need to restart the ESB which is not good in
> a production env (If we want to add a new proxy with a JMS endpoint we need
> to restart the ESB).
>
> I thought of bringing this up because you guys are working on MB 2.1.x
> release these days. Is this something which can be fixed?
>
> Regards,
> AmilaM.
>
> --
> *Amila Maharachchi*
> Technical Lead
> Member, Management Committee - Cloud & Platform TG
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>

-- 
Best Regards,*

Shammi Jayasinghe*
Senior Software Engineer; WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] Developer Studio > Eclipse-Tools > #917 was SUCCESSFUL. Change made by Harshana Martin.

2013-04-23 Thread Bamboo


---
Developer Studio > Eclipse-Tools > #917 was successful.
---
Code has been updated by Harshana Martin.

http://wso2.org/bamboo/browse/DS0001-DSET01-917/




--
Code Changes
--
Harshana Martin (170871):

>Exported org.wso2.carbon.mediator.bam.config.stream



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] Developer Studio > Eclipse-Tools > #916 has FAILED. Change made by Viraj Rajaguru.

2013-04-23 Thread Bamboo


---
Developer Studio > Eclipse-Tools > #916 failed.
---
Code has been updated by Viraj Rajaguru.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/DS0001-DSET01-916/

-
Currently Responsible
-

Harshana Martin (Automatically assigned)



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
Viraj Rajaguru (170865):

>Update bam mediator serializer and deserializer after upgrading jars



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Why kernel patch0002 is added already?

2013-04-23 Thread Kishanthan Thangarajah

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,
Development Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fwd: [Commits] [Carbon-platform] svn commit r153055 - in carbon/platform/branches/4.0.0/dependencies/commons/uri-templates/1.6.3/src/main/java/org/wso2/uri/template: . parser

Re: [Dev] [Trunk] Build failed in appfactory components

Re: [Dev] [Trunk] Build failed in appfactory components

Re: [Dev] Detect client timeout in a class mediator

Re: [Dev] Message processor's max.delivery.attempts not considered

Re: [Dev] API Manager 1.4.0 - RC1

Re: [Dev] API Manager 1.4.0 - RC1

Re: [Dev] Why kernel patch0002 is added already?

Re: [Dev] Registry become unusable after adding wrong wsdl

Re: [Dev] MB 2.0.x not supporting dynamic queues

[Dev] [Bamboo-Build] Developer Studio > Eclipse-Tools > #917 was SUCCESSFUL. Change made by Harshana Martin.

[Dev] [Bamboo-Build] Developer Studio > Eclipse-Tools > #916 has FAILED. Change made by Viraj Rajaguru.

[Dev] Why kernel patch0002 is added already?

13 matches

Site Navigation

Mail list logo

Footer information