date:20120716

Hi DimuthuL,

I uncommented the replicated cache conf and removed the local cache conf in
cache.xml and starts with -Dbind.address=IP and also changed the host
name in carbon xml accordingly.
And getting this at server startup.

[2012-07-16 12:18:14,304] ERROR
{org.wso2.carbon.utils.multitenancy.CarbonContextHolder} -  Error while
instantiating the cache.
java.lang.NullPointerException
at
org.wso2.carbon.caching.infinispan.InfinispanCacheManager.initialize(InfinispanCacheManager.java:137)
at
org.wso2.carbon.utils.multitenancy.CarbonContextHolder.clinit(CarbonContextHolder.java:174)
at
org.wso2.carbon.utils.logging.TenantAwarePatternLayout$TenantAwarePatternParser$TenantPatternConverter.getFullyQualifiedName(TenantAwarePatternLayout.java:327)
at
org.wso2.carbon.utils.logging.TenantAwarePatternLayout$TenantAwarePatternParser$TenantAwareNamedPatternConverter.convert(TenantAwarePatternLayout.java:166)
at
org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64)
at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)
at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
at
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
at org.apache.log4j.Category.callAppenders(Category.java:203)
at org.apache.log4j.Category.forcedLog(Category.java:388)
at org.apache.log4j.Category.log(Category.java:853)
at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
at
org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService.init(ZKCoordinationService.java:96)
at
org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService.init(ZKCoordinationService.java:101)
at
org.wso2.carbon.coordination.core.internal.CoordinationClientDSComponent.activate(CoordinationClientDSComponent.java:50)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at
org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
at
org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
at
org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
at
org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
at java.lang.Thread.run(Thread.java:662)


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GReg] Throws NPE when starts GReg with replicated cache enabled in latest pack

2012-07-16 Thread Dimuthu Leelarathne

Hi,

This is already fixed in revision 133036.

thanks,
dimuthu

On Mon, Jul 16, 2012 at 12:27 PM, Subash Chaturanga sub...@wso2.com wrote:

 Hi DimuthuL,

 I uncommented the replicated cache conf and removed the local cache conf
 in cache.xml and starts with -Dbind.address=IP and also changed the host
 name in carbon xml accordingly.
 And getting this at server startup.

 [2012-07-16 12:18:14,304] ERROR
 {org.wso2.carbon.utils.multitenancy.CarbonContextHolder} -  Error while
 instantiating the cache.
 java.lang.NullPointerException
  at
 org.wso2.carbon.caching.infinispan.InfinispanCacheManager.initialize(InfinispanCacheManager.java:137)
 at
 org.wso2.carbon.utils.multitenancy.CarbonContextHolder.clinit(CarbonContextHolder.java:174)
  at
 org.wso2.carbon.utils.logging.TenantAwarePatternLayout$TenantAwarePatternParser$TenantPatternConverter.getFullyQualifiedName(TenantAwarePatternLayout.java:327)
  at
 org.wso2.carbon.utils.logging.TenantAwarePatternLayout$TenantAwarePatternParser$TenantAwareNamedPatternConverter.convert(TenantAwarePatternLayout.java:166)
  at
 org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64)
 at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
  at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)
 at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
  at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
 at
 org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
  at org.apache.log4j.Category.callAppenders(Category.java:203)
 at org.apache.log4j.Category.forcedLog(Category.java:388)
  at org.apache.log4j.Category.log(Category.java:853)
 at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
  at
 org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService.init(ZKCoordinationService.java:96)
 at
 org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService.init(ZKCoordinationService.java:101)
  at
 org.wso2.carbon.coordination.core.internal.CoordinationClientDSComponent.activate(CoordinationClientDSComponent.java:50)
 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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
  at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
  at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
  at
 org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
 at
 org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
  at
 org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
 at
 org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
  at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
 at java.lang.Thread.run(Thread.java:662)


 --

 Subash Chaturanga
 Software Engineer
 WSO2 Inc. http://wso2.com

 email - sub...@wso2.com
 phone - 077 2225922


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

Re: [Dev] [GReg] Throws NPE when starts GReg with replicated cache enabled in latest pack

On Mon, Jul 16, 2012 at 12:31 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:

 Hi,

 This is already fixed in revision 133036.


Thanks . will update and try.


 thanks,
 dimuthu


 On Mon, Jul 16, 2012 at 12:27 PM, Subash Chaturanga sub...@wso2.comwrote:

 Hi DimuthuL,

 I uncommented the replicated cache conf and removed the local cache conf
 in cache.xml and starts with -Dbind.address=IP and also changed the host
 name in carbon xml accordingly.
 And getting this at server startup.

 [2012-07-16 12:18:14,304] ERROR
 {org.wso2.carbon.utils.multitenancy.CarbonContextHolder} -  Error while
 instantiating the cache.
 java.lang.NullPointerException
  at
 org.wso2.carbon.caching.infinispan.InfinispanCacheManager.initialize(InfinispanCacheManager.java:137)
 at
 org.wso2.carbon.utils.multitenancy.CarbonContextHolder.clinit(CarbonContextHolder.java:174)
  at
 org.wso2.carbon.utils.logging.TenantAwarePatternLayout$TenantAwarePatternParser$TenantPatternConverter.getFullyQualifiedName(TenantAwarePatternLayout.java:327)
  at
 org.wso2.carbon.utils.logging.TenantAwarePatternLayout$TenantAwarePatternParser$TenantAwareNamedPatternConverter.convert(TenantAwarePatternLayout.java:166)
  at
 org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64)
 at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
  at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)
 at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
  at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
 at
 org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
  at org.apache.log4j.Category.callAppenders(Category.java:203)
 at org.apache.log4j.Category.forcedLog(Category.java:388)
  at org.apache.log4j.Category.log(Category.java:853)
 at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199)
  at
 org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService.init(ZKCoordinationService.java:96)
 at
 org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService.init(ZKCoordinationService.java:101)
  at
 org.wso2.carbon.coordination.core.internal.CoordinationClientDSComponent.activate(CoordinationClientDSComponent.java:50)
 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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
  at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
  at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
  at
 org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
 at
 org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
  at
 org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
 at
 org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
  at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
 at java.lang.Thread.run(Thread.java:662)


 --

 Subash Chaturanga
 Software Engineer
 WSO2 Inc. http://wso2.com

 email - sub...@wso2.com
 phone - 077 2225922





-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build Fails platform/components/business-processes/humantask

2012-07-16 Thread Isuru Wimalasundera

Hi Dhanushka

I am receiving this error as well, can we check on this asap.

Thanks
Isuruw

On Mon, Jul 16, 2012 at 11:16 AM, Andun Gunawardena an...@wso2.com wrote:

 Hi All,

 Getting this error int the updated trunk,

 [ERROR] Failed to execute goal on project org.wso2.carbon.humantask: Could
  not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.
 humantask:bundle:4.0.0-SNAPSHOT:Could not find artifact net.sf.saxon.wso2
 :saxon.he:jar:9.4.wso2v1-SNAPSHOT in wso2-nexus (http://maven.wso2.org
 /nexus/content/groups/wso2-public/) - [Help 1]


 Thanks
 AndunSLG

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




-- 
*Isuru Wimalasundera*
Software Engineer;  WSO2, Inc.; http://wso2.com,
 mobile: +94 77 920 5641
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build Fails platform/components/business-processes/humantask

I have get rid of it by building the orbit/trunk/saxon-he. But I don't know
is it the correct way.

On Mon, Jul 16, 2012 at 12:37 PM, Isuru Wimalasundera isu...@wso2.comwrote:

 Hi Dhanushka

 I am receiving this error as well, can we check on this asap.

 Thanks
 Isuruw

 On Mon, Jul 16, 2012 at 11:16 AM, Andun Gunawardena an...@wso2.comwrote:

 Hi All,

 Getting this error int the updated trunk,

 [ERROR] Failed to execute goal on project org.wso2.carbon.humantask:
 Could not resolve dependencies for project org.wso2.carbon:org.wso2.
 carbon.humantask:bundle:4.0.0-SNAPSHOT:Could not find artifact
 net.sf.saxon.wso2:saxon.he:jar:9.4.wso2v1-SNAPSHOT in wso2-nexus (
 http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1]


 Thanks
 AndunSLG

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




 --
 *Isuru Wimalasundera*
 Software Engineer;  WSO2, Inc.; http://wso2.com,
  mobile: +94 77 920 5641


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

[Dev] IS Build Fails in Profile Generation

Hi all,

Getting this at the build of updated trunk.

Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
(org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
 Missing requirement: jaxb 2.1.7.wso2v1 (jaxb 2.1.7.wso2v1) requires
'package javax.activation 1.1.0' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
(org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
  To: jaxb [2.1.7.wso2v1]

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

Re: [Dev] ESB Callout mediator fails when accessing an endpoint through local transport

2012-07-16 Thread Amila Suriarachchi

On Fri, Jul 13, 2012 at 4:47 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi all,


 On Wed, Jul 11, 2012 at 6:23 PM, Supun Kamburugamuva supu...@gmail.comwrote:

 The server config context has the nhttp transport as the http transport.
 So callout mediator will pick this transport if we use the server
 configuration context. We should have a proper naming for the transports in
 axis2 before we can do this. i.e. At the moment axis2 thinks that the name
 of the transport is equal to the protocol name of the transport.


 We were able to use Callout mediator with local transport by doing some
 modifications to the synapse Callout mediator. We are proposing to add an
 attribute 'useServerConfig' to the callout mediator which will use server
 configuration context if set as true. By default it will be false and
 Client configuration context will be used.

 So to use the Server Configuration in Callout mediator, the configuration
 will be,

 callout serviceURL=local://localhost/services/DTPSampleService
 action=urn:addToAccountBalanceInBank2 useServerConfig=true
 source xpath=$body/child::*[fn:position()=1]/
 target xpath=$body/child::*[fn:position()=1]/
  /callout

 The modification done to the Callout Mediator was changing the init method
 of CalloutMediator.java

 public void init(SynapseEnvironment synEnv) {
 try {
 if (useServerConfig) {
 configCtx = ((Axis2SynapseEnvironment)
 synEnv).getAxis2ConfigurationContext();
 } else {
 configCtx =
 ConfigurationContextFactory.createConfigurationContextFromFileSystem(
  clientRepository != null ? clientRepository :
 DEFAULT_CLIENT_REPO,
  axis2xml != null ? axis2xml : DEFAULT_AXIS2_XML);
 }
 } catch (AxisFault e) {
 String msg = Error initializing callout mediator :  +
 e.getMessage();
 log.error(msg, e);
 throw new SynapseException(msg, e);
 }
 }

 When *useServerConfig* is set true, the *configCtx* will be initialized
 with Server Configuration Context as in Send mediator.

 Shall we proceed with this solution?


+1. This allows to use the call out mediator with local transport as well.

thanks,
Amila.


 Thanks,
 Lakmali


 Thanks,
 Supun..


 On Wed, Jul 11, 2012 at 4:46 AM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi,

 How can we proceed if we are going to change the Callout mediator to use
 the server config context as well?

 Thanks,
 Lakmali



 On Tue, Jul 10, 2012 at 11:39 PM, Kasun Indrasiri ka...@wso2.comwrote:

 However, following scenario seems to work fine. Seems this is not the
 expected behavior.

proxy name=EchoProxy transports=https http startOnLoad=true
 trace=disable
 description/
 target
 inSequence

 callout serviceURL=local://services/echo
 action=urn:echoString
 source xmlns:s12=
 http://www.w3.org/2003/05/soap-envelope; xmlns:s11=
 http://schemas.xmlsoap.org/soap/envelope/;
 xpath=s11:Body/child::*[fn:position()=1] |
 s12:Body/child::*[fn:position()=1]/
 target xmlns:s12=
 http://www.w3.org/2003/05/soap-envelope; xmlns:s11=
 http://schemas.xmlsoap.org/soap/envelope/;
 xpath=s11:Body/child::*[fn:position()=1] |
 s12:Body/child::*[fn:position()=1]/
 /callout
 property name=RESPONSE value=true/
 header name=To action=remove/
 send/
 /inSequence
 outSequence
 send/
 /outSequence
 /target
 /proxy

 On Tue, Jul 10, 2012 at 10:23 PM, Supun Kamburugamuva 
 supu...@gmail.com wrote:

 For the local transport to work both the invoker and the invoking
 service should be in the same configuration context. So this scenario will
 never work with the local transport + callout mediator.

 Thanks,
 Supun..

 On Tue, Jul 10, 2012 at 12:48 PM, Hiranya Jayathilaka 
 hira...@wso2.com wrote:



 On Tue, Jul 10, 2012 at 5:50 PM, Lakmali Baminiwatta 
 lakm...@wso2.com wrote:

 Hi,

 On Tue, Jul 10, 2012 at 5:26 PM, Hiranya Jayathilaka 
 hira...@wso2.com wrote:

 Send mediator and callout mediator use different
 ConfigurationContext instances. Former uses the server cfgctx and the
 latter uses the client cfgctx. That should be the problem.


 I have enabled local transport on
 samples/axis2Client/client_repo/conf/axis2.xml. Does it require more
 configurations to the client cfgctx ?


 I think the local transport looks up the cfgctx to find the target
 AxisService. So unless you somehow use the server cfgctx in the callout
 mediator, this scenario will never work. Better to debug and confirm - 
 I'm
 not 100% certain.



 If you're using the local transport, it doesn't matter which
 mediator you use performance wise. So why not just use the send 
 mediator?


 The requirement is to get the response from the endpoint in the same
 sequence. For

Re: [Dev] IS Build Fails in Profile Generation

2012-07-16 Thread Isuru Udana

This is reported in the recent bamboo product build also [1].

[1]
http://wso2.org/bamboo/download/WSO2CARBON-PRODUCTS-JOB1/build_logs/WSO2CARBON-PRODUCTS-JOB1-303.log

On Mon, Jul 16, 2012 at 2:19 PM, Andun Gunawardena an...@wso2.com wrote:

 Hi all,

 Getting this at the build of updated trunk.

 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
 (org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
  Missing requirement: jaxb 2.1.7.wso2v1 (jaxb 2.1.7.wso2v1) requires
 'package javax.activation 1.1.0' but it could not be found
  Cannot satisfy dependency:
   From: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
 (org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
   To: jaxb [2.1.7.wso2v1]


 Thanks
 AndunSLG

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




-- 
*Isuru Udana*
*
 *
*
Software Engineer
*
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB Callout mediator fails when accessing an endpoint through local transport

2012-07-16 Thread Hiranya Jayathilaka

The server configuration of Synapse usually has the non-blocking
transports. That may have an effect on the thread model of the callout
mediator.

Thanks,
Hiranya

On Mon, Jul 16, 2012 at 2:33 PM, Amila Suriarachchi am...@wso2.com wrote:



 On Fri, Jul 13, 2012 at 4:47 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi all,


 On Wed, Jul 11, 2012 at 6:23 PM, Supun Kamburugamuva 
 supu...@gmail.comwrote:

 The server config context has the nhttp transport as the http transport.
 So callout mediator will pick this transport if we use the server
 configuration context. We should have a proper naming for the transports in
 axis2 before we can do this. i.e. At the moment axis2 thinks that the name
 of the transport is equal to the protocol name of the transport.


 We were able to use Callout mediator with local transport by doing some
 modifications to the synapse Callout mediator. We are proposing to add an
 attribute 'useServerConfig' to the callout mediator which will use server
 configuration context if set as true. By default it will be false and
 Client configuration context will be used.

 So to use the Server Configuration in Callout mediator, the configuration
 will be,

 callout serviceURL=local://localhost/services/DTPSampleService
 action=urn:addToAccountBalanceInBank2 useServerConfig=true
 source xpath=$body/child::*[fn:position()=1]/
 target xpath=$body/child::*[fn:position()=1]/
  /callout

 The modification done to the Callout Mediator was changing the init
 method of CalloutMediator.java

 public void init(SynapseEnvironment synEnv) {
 try {
 if (useServerConfig) {
 configCtx = ((Axis2SynapseEnvironment)
 synEnv).getAxis2ConfigurationContext();
 } else {
 configCtx =
 ConfigurationContextFactory.createConfigurationContextFromFileSystem(
  clientRepository != null ? clientRepository :
 DEFAULT_CLIENT_REPO,
  axis2xml != null ? axis2xml : DEFAULT_AXIS2_XML);
 }
 } catch (AxisFault e) {
 String msg = Error initializing callout mediator :  +
 e.getMessage();
 log.error(msg, e);
 throw new SynapseException(msg, e);
 }
 }

 When *useServerConfig* is set true, the *configCtx* will be initialized
 with Server Configuration Context as in Send mediator.

 Shall we proceed with this solution?


 +1. This allows to use the call out mediator with local transport as well.

 thanks,
 Amila.


 Thanks,
 Lakmali


 Thanks,
 Supun..


 On Wed, Jul 11, 2012 at 4:46 AM, Lakmali Baminiwatta 
 lakm...@wso2.comwrote:

 Hi,

 How can we proceed if we are going to change the Callout mediator to
 use the server config context as well?

 Thanks,
 Lakmali



 On Tue, Jul 10, 2012 at 11:39 PM, Kasun Indrasiri ka...@wso2.comwrote:

 However, following scenario seems to work fine. Seems this is not the
 expected behavior.

proxy name=EchoProxy transports=https http startOnLoad=true
 trace=disable
 description/
 target
 inSequence

 callout serviceURL=local://services/echo
 action=urn:echoString
 source xmlns:s12=
 http://www.w3.org/2003/05/soap-envelope; xmlns:s11=
 http://schemas.xmlsoap.org/soap/envelope/;
 xpath=s11:Body/child::*[fn:position()=1] |
 s12:Body/child::*[fn:position()=1]/
 target xmlns:s12=
 http://www.w3.org/2003/05/soap-envelope; xmlns:s11=
 http://schemas.xmlsoap.org/soap/envelope/;
 xpath=s11:Body/child::*[fn:position()=1] |
 s12:Body/child::*[fn:position()=1]/
 /callout
 property name=RESPONSE value=true/
 header name=To action=remove/
 send/
 /inSequence
 outSequence
 send/
 /outSequence
 /target
 /proxy

 On Tue, Jul 10, 2012 at 10:23 PM, Supun Kamburugamuva 
 supu...@gmail.com wrote:

 For the local transport to work both the invoker and the invoking
 service should be in the same configuration context. So this scenario 
 will
 never work with the local transport + callout mediator.

 Thanks,
 Supun..

 On Tue, Jul 10, 2012 at 12:48 PM, Hiranya Jayathilaka 
 hira...@wso2.com wrote:



 On Tue, Jul 10, 2012 at 5:50 PM, Lakmali Baminiwatta 
 lakm...@wso2.com wrote:

 Hi,

 On Tue, Jul 10, 2012 at 5:26 PM, Hiranya Jayathilaka 
 hira...@wso2.com wrote:

 Send mediator and callout mediator use different
 ConfigurationContext instances. Former uses the server cfgctx and the
 latter uses the client cfgctx. That should be the problem.


 I have enabled local transport on
 samples/axis2Client/client_repo/conf/axis2.xml. Does it require more
 configurations to the client cfgctx ?


 I think the local transport looks up the cfgctx to find the target
 AxisService. So unless you somehow use the server cfgctx in the callout
 mediator, this scenario will never work. Better to debug and confirm -

Re: [Dev] ESB Callout mediator fails when accessing an endpoint through local transport

2012-07-16 Thread Amila Suriarachchi

On Mon, Jul 16, 2012 at 3:09 PM, Hiranya Jayathilaka hira...@wso2.comwrote:

 The server configuration of Synapse usually has the non-blocking
 transports. That may have an effect on the thread model of the callout
 mediator.


this property is only to use with local transport. If some one needs http
transport they should not enable this property.

thanks,
Amila.



 Thanks,
 Hiranya


 On Mon, Jul 16, 2012 at 2:33 PM, Amila Suriarachchi am...@wso2.comwrote:



 On Fri, Jul 13, 2012 at 4:47 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi all,


 On Wed, Jul 11, 2012 at 6:23 PM, Supun Kamburugamuva 
 supu...@gmail.comwrote:

 The server config context has the nhttp transport as the http
 transport. So callout mediator will pick this transport if we use the
 server configuration context. We should have a proper naming for the
 transports in axis2 before we can do this. i.e. At the moment axis2 thinks
 that the name of the transport is equal to the protocol name of the
 transport.


 We were able to use Callout mediator with local transport by doing some
 modifications to the synapse Callout mediator. We are proposing to add an
 attribute 'useServerConfig' to the callout mediator which will use server
 configuration context if set as true. By default it will be false and
 Client configuration context will be used.

 So to use the Server Configuration in Callout mediator, the
 configuration will be,

 callout serviceURL=local://localhost/services/DTPSampleService
 action=urn:addToAccountBalanceInBank2 useServerConfig=true
 source xpath=$body/child::*[fn:position()=1]/
 target xpath=$body/child::*[fn:position()=1]/
  /callout

 The modification done to the Callout Mediator was changing the init
 method of CalloutMediator.java

 public void init(SynapseEnvironment synEnv) {
 try {
 if (useServerConfig) {
 configCtx = ((Axis2SynapseEnvironment)
 synEnv).getAxis2ConfigurationContext();
 } else {
 configCtx =
 ConfigurationContextFactory.createConfigurationContextFromFileSystem(
  clientRepository != null ? clientRepository :
 DEFAULT_CLIENT_REPO,
  axis2xml != null ? axis2xml : DEFAULT_AXIS2_XML);
 }
 } catch (AxisFault e) {
 String msg = Error initializing callout mediator :  +
 e.getMessage();
 log.error(msg, e);
 throw new SynapseException(msg, e);
 }
 }

 When *useServerConfig* is set true, the *configCtx* will be initialized
 with Server Configuration Context as in Send mediator.

 Shall we proceed with this solution?


 +1. This allows to use the call out mediator with local transport as well.

 thanks,
 Amila.


 Thanks,
 Lakmali


 Thanks,
 Supun..


 On Wed, Jul 11, 2012 at 4:46 AM, Lakmali Baminiwatta 
 lakm...@wso2.comwrote:

 Hi,

 How can we proceed if we are going to change the Callout mediator to
 use the server config context as well?

 Thanks,
 Lakmali



 On Tue, Jul 10, 2012 at 11:39 PM, Kasun Indrasiri ka...@wso2.comwrote:

 However, following scenario seems to work fine. Seems this is not the
 expected behavior.

proxy name=EchoProxy transports=https http startOnLoad=true
 trace=disable
 description/
 target
 inSequence

 callout serviceURL=local://services/echo
 action=urn:echoString
 source xmlns:s12=
 http://www.w3.org/2003/05/soap-envelope; xmlns:s11=
 http://schemas.xmlsoap.org/soap/envelope/;
 xpath=s11:Body/child::*[fn:position()=1] |
 s12:Body/child::*[fn:position()=1]/
 target xmlns:s12=
 http://www.w3.org/2003/05/soap-envelope; xmlns:s11=
 http://schemas.xmlsoap.org/soap/envelope/;
 xpath=s11:Body/child::*[fn:position()=1] |
 s12:Body/child::*[fn:position()=1]/
 /callout
 property name=RESPONSE value=true/
 header name=To action=remove/
 send/
 /inSequence
 outSequence
 send/
 /outSequence
 /target
 /proxy

 On Tue, Jul 10, 2012 at 10:23 PM, Supun Kamburugamuva 
 supu...@gmail.com wrote:

 For the local transport to work both the invoker and the invoking
 service should be in the same configuration context. So this scenario 
 will
 never work with the local transport + callout mediator.

 Thanks,
 Supun..

 On Tue, Jul 10, 2012 at 12:48 PM, Hiranya Jayathilaka 
 hira...@wso2.com wrote:



 On Tue, Jul 10, 2012 at 5:50 PM, Lakmali Baminiwatta 
 lakm...@wso2.com wrote:

 Hi,

 On Tue, Jul 10, 2012 at 5:26 PM, Hiranya Jayathilaka 
 hira...@wso2.com wrote:

 Send mediator and callout mediator use different
 ConfigurationContext instances. Former uses the server cfgctx and the
 latter uses the client cfgctx. That should be the problem.


 I have enabled local transport on
 samples/axis2Client/client_repo/conf/axis2.xml. Does it require more
 configurations to the client

Re: [Dev] IS Build Fails in Profile Generation

2012-07-16 Thread Hasini Gunasinghe

Fixed the platform/trunk/products/pom.xml to have the correct jaxb version,
from where IS inherits the version.

The above issue should be fixed now.

Thanks,
Hasini.

On Mon, Jul 16, 2012 at 3:04 PM, Hasini Gunasinghe has...@wso2.com wrote:

 Hi,

 We inherit those versions from platform/trunk/products/pom.xml.

 Will fix that.

 Thanks,
 Hasini.

 On Mon, Jul 16, 2012 at 2:57 PM, Ajith Vitharana aji...@wso2.com wrote:



 On Mon, Jul 16, 2012 at 2:19 PM, Andun Gunawardena an...@wso2.comwrote:

 Hi all,

 Getting this at the build of updated trunk.

 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
 (org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
  Missing requirement: jaxb 2.1.7.wso2v1 (jaxb 2.1.7.wso2v1) requires
 'package javax.activation 1.1.0' but it could not be found
  Cannot satisfy dependency:
   From: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
 (org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
   To: jaxb [2.1.7.wso2v1]



 Hi All,

 We also noticed same error while building the AS profile.
 Pradeep has already fixed that issue for AS (r132852).
 Please use same fix for IS.

 Thanks
 Ajith


 Thanks
 AndunSLG

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




 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94714631794



 ___
 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

[Dev] AS Integration Test Fails

Hi All,

Getting this in the latest trunk,

[2012-07-17 15:27:47,250]  INFO
{org.wso2.appserver.integration.tests.ASTestServerManager} -  compute
Jaggery Source Path samplesDir :
/media/Studies/My_Works/WSO2_Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/resourcesdelet.jag
Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed: 302.673
sec  FAILURE!

Results :

Failed tests:
startServer(org.wso2.appserver.integration.tests.ASTestServerManager):
Method org.testng.internal.ConfigurationMethod.startServer() didn't finish
within the time-out 30

Tests run: 87, Failures: 1, Errors: 0, Skipped: 86

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

Re: [Dev] AS Integration Test Fails

2012-07-16 Thread Kasun Gajasinghe

Can you provide the surefire report for intergration module as well? That
should tell us about the issue more.

On Mon, Jul 16, 2012 at 3:39 PM, Andun Gunawardena an...@wso2.com wrote:

 Hi All,

 Getting this in the latest trunk,

 [2012-07-17 15:27:47,250]  INFO
 {org.wso2.appserver.integration.tests.ASTestServerManager} -  compute
 Jaggery Source Path samplesDir :
 /media/Studies/My_Works/WSO2_Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/resourcesdelet.jag
 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed: 302.673
 sec  FAILURE!

 Results :

 Failed tests:
 startServer(org.wso2.appserver.integration.tests.ASTestServerManager):
 Method org.testng.internal.ConfigurationMethod.startServer() didn't finish
 within the time-out 30

 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86

 Thanks
 AndunSLG

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




-- 
*Kasun Gajasinghe*
Software Engineer;
Development Technologies Team, WSO2 Inc.; http://wso2.com ,
*email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe*
*
*blog: **http://blog.kasunbg.org* http://blog.kasunbg.org*
twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fwd: [Bamboo-Build] Sonar Reporting Kernel #111 has FAILED

2012-07-16 Thread Maheshika Goonetilleke

-- Forwarded message --
From: Bamboo cbuil...@wso2.org
Date: Mon, Jul 16, 2012 at 3:33 PM
Subject: [Bamboo-Build] Sonar Reporting  Kernel  #111 has FAILED
To: mahesh...@wso2.com

 [image: Failed]  Sonar Reporting http://wso2.org/bamboo/browse/CR001/›
Kernel http://wso2.org/bamboo/browse/CR001-CRCK01/ ›
#111http://wso2.org/bamboo/browse/CR001-CRCK01-111/
failed

This build occurred because it is a dependant of
CR001-CRCO01-108http://wso2.org/bamboo/browse/CR001-CRCO01-108
.

No failed tests found, a possible compilation error.
  Failing Jobs http://wso2.org/bamboo/browse/CR001-CRCK01-111/Job
Duration Tests[image: Failed]  Default
Jobhttp://wso2.org/bamboo/browse/CR001-CRCK01-JOB1-111/ (Default
Stage)  5 minutes  No tests found
Logshttp://wso2.org/bamboo/browse/CR001-CRCK01-JOB1-111/log|
Artifacts http://wso2.org/bamboo/browse/CR001-CRCK01-JOB1-111/artifact
View
Online http://wso2.org/bamboo/browse/CR001-CRCK01-111 | Add
Commentshttp://wso2.org/bamboo/browse/CR001-CRCK01-111?commentMode=true

This message was sent by Atlassian Bamboo http://wso2.org/bamboo.

If you wish to stop receiving these emails edit your user
profilehttp://wso2.org/bamboo/profile/userNotifications.actionor
notify
your administrator http://wso2.org/bamboo/viewAdministrators.action.

Hi All

The Sonar Reporting for Kernel is failing due to the following error;

16-Jul-2012 03:18:20[INFO]
16-Jul-2012
03:18:20[INFO] BUILD FAILURE16-Jul-2012 03:18:20[INFO]
16-Jul-2012
03:18:20[INFO] Total time: 5:17.619s16-Jul-2012 03:18:20[INFO] Finished at:
Mon Jul 16 03:18:20 PDT 201216-Jul-2012 03:18:23[INFO] Final Memory:
434M/1563M16-Jul-2012 03:18:23[INFO]
16-Jul-2012
03:18:23[ERROR] Failed to execute goal on project org.wso2.carbon.tomcat:
Could not resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.tomcat:bundle:4.0.0-SNAPSHOT: Failed to
collect dependencies for
[org.eclipse.osgi:org.eclipse.osgi:jar:3.7.0.v20110613 (compile),
org.eclipse.equinox:org.eclipse.equinox.http.servlet:jar:1.0.200.v20090520-1800
(compile),
org.eclipse.equinox:org.eclipse.equinox.common:jar:3.6.0.v20110523
(compile), org.wso2.carbon:javax.servlet:jar:3.0.0.wso2v1 (compile),
org.apache.tomcat.wso2:tomcat:jar:7.0.28.wso2v1 (compile),
org.wso2.carbon:org.wso2.carbon.logging:jar:4.0.0-SNAPSHOT (compile),
junit:junit:jar:3.8.2 (test)]: Failed to read artifact descriptor for
org.apache.tomcat:tomcat-dbcp:jar:${version.tomcat}: Could not transfer
artifact org.apache.tomcat:tomcat-dbcp:pom:${version.tomcat} from/to
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/):
IllegalArgumentException: Illegal character in path at index 86:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/tomcat/tomcat-dbcp/${version.tomcat}/tomcat-dbcp-${version.tomcat}.pom-
[Help 1]16-Jul-2012
03:18:23[ERROR] 16-Jul-2012 03:18:23[ERROR] To see the full stack trace of
the errors, re-run Maven with the -e switch.

Please make necessary amendments to rectify.
-- 

Thanks  Best Regards,

Maheshika Goonetilleke
Engineering Process Coordinator
WSO2 Inc

www.wso2.com/

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

Re: [Dev] AS Integration Test Fails

2012-07-16 Thread Madhuka Udantha

hi,

Getting this in the latest trunk,

[2012-07-17 15:27:47,250]  INFO
{org.wso2.appserver.integration.tests.ASTestServerManager} -  compute
Jaggery Source Path samplesDir :
/media/Studies/My_Works/WSO2_Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/resourcesdelet.jag
Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed: 302.673
sec  FAILURE!

It must to be
[2012-07-17 15:27:47,250]  INFO
{org.wso2.appserver.integration.tests.ASTestServerManager}
-  compute Jaggery Source Path samplesDir : /media/Studies/My_Works/WSO2_
Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/
resources/delet.jag
Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed: 302.673
sec  FAILURE!

seems to be 'File.separator' is not working in that level.
Need to check it.


Thank you.






On Mon, Jul 16, 2012 at 3:46 PM, Kasun Gajasinghe kas...@wso2.com wrote:


 Can you provide the surefire report for intergration module as well? That
 should tell us about the issue more.

 On Mon, Jul 16, 2012 at 3:39 PM, Andun Gunawardena an...@wso2.com wrote:

 Hi All,

 Getting this in the latest trunk,

 [2012-07-17 15:27:47,250]  INFO
 {org.wso2.appserver.integration.tests.ASTestServerManager} -  compute
 Jaggery Source Path samplesDir :
 /media/Studies/My_Works/WSO2_Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/resourcesdelet.jag
 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed: 302.673
 sec  FAILURE!

 Results :

 Failed tests:
 startServer(org.wso2.appserver.integration.tests.ASTestServerManager):
 Method org.testng.internal.ConfigurationMethod.startServer() didn't finish
 within the time-out 30

 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86

 Thanks
 AndunSLG

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




 --
 *Kasun Gajasinghe*
 Software Engineer;
 Development Technologies Team, WSO2 Inc.; http://wso2.com ,
 *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe*
 *
  *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org*
 twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg*
 *


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




-- 
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] Carbon Snapshot P2-Repo #149 has FAILED

2012-07-16 Thread Shammi Jayasinghe

This was happened due to a configuration problem and Fixed it.

Thanks
Shammi

On Mon, Jul 16, 2012 at 1:49 PM, Bamboo cbuil...@wso2.org wrote:

  [image: Failed]  Carbon 
 Snapshothttp://wso2.org/bamboo/browse/WSO2CARBON/›
 P2-Repo http://wso2.org/bamboo/browse/WSO2CARBON-P2REPO/ › 
 #149http://wso2.org/bamboo/browse/WSO2CARBON-P2REPO-149/
 failed

 This build occurred because it is a dependant of 
 WSO2CARBON-PLATFORM-464http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-464
 .

 No failed tests found, a possible compilation error.
   Failing Jobs http://wso2.org/bamboo/browse/WSO2CARBON-P2REPO-149/
 Job Duration Tests[image: Failed]  Default 
 Jobhttp://wso2.org/bamboo/browse/WSO2CARBON-P2REPO-JOB1-149/ (Default
 Stage)   1 second  No tests found  
 Logshttp://wso2.org/bamboo/browse/WSO2CARBON-P2REPO-JOB1-149/log|
 Artifactshttp://wso2.org/bamboo/browse/WSO2CARBON-P2REPO-JOB1-149/artifact  
View
 Online http://wso2.org/bamboo/browse/WSO2CARBON-P2REPO-149 | Add
 Commentshttp://wso2.org/bamboo/browse/WSO2CARBON-P2REPO-149?commentMode=true

 This message was sent by Atlassian Bamboo http://wso2.org/bamboo.

 If you wish to stop receiving these emails edit your user 
 profilehttp://wso2.org/bamboo/profile/userNotifications.actionor notify
 your administrator http://wso2.org/bamboo/viewAdministrators.action.

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




-- 
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

Re: [Dev] AS Integration Test Fails

2012-07-16 Thread Madhuka Udantha

just check the code for 'File.separator'. It works fine. No issue in there.
Test are OK with jaggery in AS.

check the distribution was successful?


On Mon, Jul 16, 2012 at 4:10 PM, Madhuka Udantha madh...@wso2.com wrote:

 hi,

  Getting this in the latest trunk,

 [2012-07-17 15:27:47,250]  INFO
 {org.wso2.appserver.integration.tests.ASTestServerManager} -  compute
 Jaggery Source Path samplesDir :
 /media/Studies/My_Works/WSO2_Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/resourcesdelet.jag
 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed: 302.673
 sec  FAILURE!

 It must to be
 [2012-07-17 15:27:47,250]  INFO 
 {org.wso2.appserver.integration.tests.ASTestServerManager}
 -  compute Jaggery Source Path samplesDir : /media/Studies/My_Works/WSO2_
 Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/
 resources/delet.jag
  Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed:
 302.673 sec  FAILURE!

 seems to be 'File.separator' is not working in that level.
 Need to check it.


 Thank you.






 On Mon, Jul 16, 2012 at 3:46 PM, Kasun Gajasinghe kas...@wso2.com wrote:


 Can you provide the surefire report for intergration module as well? That
 should tell us about the issue more.

 On Mon, Jul 16, 2012 at 3:39 PM, Andun Gunawardena an...@wso2.comwrote:

 Hi All,

 Getting this in the latest trunk,

 [2012-07-17 15:27:47,250]  INFO
 {org.wso2.appserver.integration.tests.ASTestServerManager} -  compute
 Jaggery Source Path samplesDir :
 /media/Studies/My_Works/WSO2_Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/resourcesdelet.jag
 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed:
 302.673 sec  FAILURE!

 Results :

 Failed tests:
 startServer(org.wso2.appserver.integration.tests.ASTestServerManager):
 Method org.testng.internal.ConfigurationMethod.startServer() didn't finish
 within the time-out 30

 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86

 Thanks
 AndunSLG

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




 --
 *Kasun Gajasinghe*
 Software Engineer;
 Development Technologies Team, WSO2 Inc.; http://wso2.com ,
 *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe*
 *
  *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org*
 twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg*
 *


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




 --
 *Madhuka* Udantha
 http://madhukaudantha.blogspot.com/




-- 
*Madhuka* Udantha
http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS Integration Test Fails

Hi,

We are building the Carbon Platform as a team Today for ESB
Test Automatons. I have checked with other one, she has the same
integration test failure a mine. But she didn't get that warning.

Thanks
AndunSLG

On Mon, Jul 16, 2012 at 4:51 PM, Andun Gunawardena an...@wso2.com wrote:

 I checked, the distribution has been built successfully. Log is given
 bellow. But something odd shows as a warning. Is that the cause for this?
 When we generate feature archive this warning was shown for each feature
 build.The surefire-reports are attached.

 Thanks
 AndunSLG

 The Warning


 [WARNING]
 org.apache.maven.plugin.MojoExecutionException: Unable complete mop up
 operation
  at
 org.wso2.maven.p2.generate.feature.FeatureGenMojo.performMopUp(FeatureGenMojo.java:937)
 at
 org.wso2.maven.p2.generate.feature.FeatureGenMojo.execute(FeatureGenMojo.java:244)
  at
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
 at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
  at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
  at
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
  at
 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
 at
 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
  at
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
 at
 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
  at
 org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
 Caused by: java.io.IOException: Directory
 /media/Studies/My_Works/WSO2_Carbon_Trunk/platform/trunk/products/as/modules/features/service/org.wso2.stratos.appserver.login.ui.feature/target/raw/features/org.wso2.stratos.appserver.login.ui_2.0.0.SNAPSHOT
 unable to be deleted.
  at
 org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1539)
 at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1326)
  at org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1590)
 at org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1535)
  at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1326)
 at org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1590)
  at
 org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1535)
 at
 org.wso2.maven.p2.generate.feature.FeatureGenMojo.performMopUp(FeatureGenMojo.java:935)
  ... 22 more

 The Build log

 [2012-07-17 16:40:49,713]  INFO
 {org.wso2.appserver.integration.tests.ASTestServerManager} -  compute
 Jaggery Source Path samplesDir :
 /media/Studies/My_Works/WSO2_Carbon_Trunk/platform/trunk/products/as/modules/integration/src/test/resourcesdelet.jag
 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86, Time elapsed: 303.549
 sec  FAILURE!

 Results :

 Failed tests:
 startServer(org.wso2.appserver.integration.tests.ASTestServerManager):
 Method org.testng.internal.ConfigurationMethod.startServer() didn't finish
 within the time-out 30

 Tests run: 87, Failures: 1, Errors: 0, Skipped: 86

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 AppServer - Parent ... SUCCESS [0.526s]
 [INFO] WSO2 AppServer - Styles Parent  SUCCESS [0.016s]
 [INFO] WSO2 AppServer - UI styles  SUCCESS [7.142s]
 [INFO] WSO2 Stratos  AppServer - UI styles ... SUCCESS [4.161s]
 [INFO] WSO2 AppServer - Samples Parent ... SUCCESS [0.024s]
 [INFO] Samples ... SUCCESS [0.016s]
 [INFO] Sample/Chad ... SUCCESS [4.810s]
 [INFO] Sample/CommodityQuote . SUCCESS
 [11.787s]
 [INFO] Sample/TinyURL

Re: [Dev] Webapss with javascrips, css stylings does not work on IBM JDK 7 (latest)

2012-07-16 Thread Kishanthan Thangarajah

No webapps work in trunk AS when using IBM jdk. The same is there in 4.1.2
release also. Root cause is the same security exception. Did we test
webapps on previous releases of AS with IBM jdk before? or is this the
first time?

On Mon, Jul 16, 2012 at 12:08 PM, Chamara Ariyarathne chama...@wso2.comwrote:

 Here it is!


 On Sat, Jul 14, 2012 at 11:37 AM, Nuwan Bandara nu...@wso2.com wrote:

 We had similar issue, during tomcat osgification. the issue was the
 content type wasnt correctly set. this is done in the global web.xml in
 tomcat once we add that it went away. any chance the global settings not
 getting applied here ?

 Regards,
 /Nuwan


 On Fri, Jul 13, 2012 at 10:47 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Chamara,

 On Fri, Jul 13, 2012 at 12:07 PM, Chamara Ariyarathne chama...@wso2.com
  wrote:

 Same webapp works on tomcat with the ibm jdk 7.


 Can you share the same webapp used to test here? or perhaps attach it to
 the jira issue itself.

 Thanks,
 Kishanthan.


 On Fri, Jul 13, 2012 at 11:53 AM, Chamara Ariyarathne 
 chama...@wso2.com wrote:

 Does not work when the browser cache is cleared.
 I will try out on top of tomcat


 On Fri, Jul 13, 2012 at 11:45 AM, Afkham Azeez az...@wso2.com wrote:

 Can you clear the browser cache  retry.

 On Fri, Jul 13, 2012 at 11:29 AM, Chamara Ariyarathne 
 chama...@wso2.com wrote:

 JIRA created.

 https://wso2.org/jira/browse/CARBON-13637

 --
 *Chamara Ariyarathne*
 Senior Software Engineer - QA;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; *+94772786766*


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




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Chamara Ariyarathne*
 Senior Software Engineer - QA;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; *+94772786766*




 --
 *Chamara Ariyarathne*
 Senior Software Engineer - QA;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; *+94772786766*


 ___
 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*


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




 --
 *Thanks  Regards,

 Nuwan Bandara
 Associate Technical Lead  Member, MC, Development Technologies
 WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
 blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
 9629
 *
 http://www.nuwanbando.com/




 --
 *Chamara Ariyarathne*
 Senior Software Engineer - QA;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; *+94772786766*




-- 
*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] AS startup warn: Error loading properties from a file at from the System defined location: datasources.properties

$subject.
Full log,
[2012-07-16 19:32:56,104]  WARN
{org.apache.synapse.commons.util.MiscellaneousUtil} -  Error loading
properties from a file at from the System defined location:
datasources.properties

thanks,
-- 
Supun Malinga,

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

[Dev] AS startup warn: Error occurred while activating the UrlMapperServiceComponent

$subject,
Full log,

[2012-07-16 19:32:56,488]  WARN
{org.wso2.carbon.url.mapper.internal.UrlMapperServiceComponent} -  Error
occurred while activating the UrlMapperServiceComponent
java.lang.NullPointerException
at
org.wso2.carbon.url.mapper.internal.UrlMapperServiceComponent.addMappingToApplicationContext(UrlMapperServiceComponent.java:183)
 at
org.wso2.carbon.url.mapper.internal.UrlMapperServiceComponent.activate(UrlMapperServiceComponent.java:100)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
 at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
 at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
 at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
 at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
 at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
 at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
 at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
 at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
 at
org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.registerServices(DataSourceServiceComponent.java:102)
at
org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.initAllTenantUserDataSources(DataSourceServiceComponent.java:199)
 at
org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.checkInitTenantUserDataSources(DataSourceServiceComponent.java:183)
at
org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.setRegistryService(DataSourceServiceComponent.java:133)
 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.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:367)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:430)
 at
org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:415)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:319)
 at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
 at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
 at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
 at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
 at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
 at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent.activate(RegistryCoreServiceComponent.java:119)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at

Re: [Dev] Shall we ship a jax-rs application by default for super tenant?

2012-07-16 Thread Afkham Azeez

On Mon, Jul 16, 2012 at 7:54 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 How about $subject. Currently at initial startup jax-rs applications page
 is empty. This would help usability as well.


+1



 thanks,
 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321


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




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] AM startup failed in latest trunk.

2012-07-16 Thread Ajith Vitharana

Hi All,

I'm getting following error while start the AM server.

[2012-07-16 23:22:17,022] FATAL - CarbonServerManager WSO2 Carbon
initialization Failed
java.lang.NoClassDefFoundError: javax/ws/rs/Produces
at org.apache.axis2.jaxrs.JAXRSUtils.getClassModel(JAXRSUtils.java:53)
at
org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.generateSchema(DefaultSchemaGenerator.java:272)
at org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:468)
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:471)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:288)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: java.lang.ClassNotFoundException: javax.ws.rs.Produces
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 14 more


-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94714631794
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Registry API method for dissociate an aspect from a resource, is missing.

Hi All,

While going through the Registry API, I have noticed that the API method
for dissociate an aspect from a resource is missing. The abstract aspect
class has 5 methods and all of these 5 methods are required to be exposed
via the Registry API. Currently 4 of these methods are exposed from the
Registry API but the method to remove an aspect from a resource(dissociate)
method is not exposed through the Registry API. It seems like it is not
there from the initial API design. Were there any particular reason for
this?

IMO, this needs to be fixed since there is an inconsistency in the API
because of this.

This is a critical design error and issues such as [1] can not be fixed
because of this.

Thanks,
Janaka

[1] https://wso2.org/jira/browse/REGISTRY-964

-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : jan...@wso2.com
Blog : janakaranabahu.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS startup warn: Error loading properties from a file at from the System defined location: datasources.properties

2012-07-16 Thread Prabath Abeysekera

Hi Supun,

On Mon, Jul 16, 2012 at 7:35 PM, Supun Malinga sup...@wso2.com wrote:

 $subject.
 Full log,
 [2012-07-16 19:32:56,104]  WARN
 {org.apache.synapse.commons.util.MiscellaneousUtil} -  Error loading
 properties from a file at from the System defined location:
 datasources.properties


This is indicated when there's some issue while reading the datasource
configurations from the datasource.properties by the synapse dependencies
at the server startup. (Usually when the aforesaid configuration file is
not present).
Just to clarify, why do you guys need to have a dependency to synapse
features?



 thanks,
 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321


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



Regards,
Prabath
-- 
Prabath Abeysekara
Software Engineer
WSO2 Inc.
Email: praba...@wso2.com harsha...@wso2.com
Mobile: +94774171471

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

Re: [Dev] AS startup warn: Error loading properties from a file at from the System defined location: datasources.properties

2012-07-16 Thread Prabath Abeysekera

On Tue, Jul 17, 2012 at 12:50 AM, Prabath Abeysekera praba...@wso2.comwrote:

 Hi Supun,

 On Mon, Jul 16, 2012 at 7:35 PM, Supun Malinga sup...@wso2.com wrote:

 $subject.
 Full log,
 [2012-07-16 19:32:56,104]  WARN
 {org.apache.synapse.commons.util.MiscellaneousUtil} -  Error loading
 properties from a file at from the System defined location:
 datasources.properties


 This is indicated when there's some issue while reading the datasource
 configurations from the datasource.properties by the synapse dependencies


Here in this particular instance, it is the data-source feature that is
trying to load datasource properties from the aforesaid configuration file.
Therefore, removing the data-source features (I believe AS datasource
implementation has already been migrated to ndatasources) should fix this.


 at the server startup. (Usually when the aforesaid configuration file is
 not present).
 Just to clarify, why do you guys need to have a dependency to synapse
 features?



 thanks,
 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321


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



 Regards,
 Prabath
 --
 Prabath Abeysekara
 Software Engineer
 WSO2 Inc.
 Email: praba...@wso2.com harsha...@wso2.com
 Mobile: +94774171471

 http://harshana05.blogspot.com/




-- 
Prabath Abeysekara
Software Engineer
WSO2 Inc.
Email: praba...@wso2.com harsha...@wso2.com
Mobile: +94774171471

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

[Dev] Missing methods in ResourceDAO interface of registry core

Hi All,

I have noticed that the property handling in registry core is not done
properly. The ResourceDAO interface(which is the data access object for
resources) has only 2 methods which is related to properties and that is to
add properties and remove properties[1]. I have noticed that we call the
add properties method for both resource add and update operations. In other
words, for each add or update operation of a resource, we insert all its
properties again to the database. This behavior is there even if we turn
off resource versioning.

IMO, this is an critical issue and it can lead to unnecessary database
growth. Also note that this causes unnecessary calls to the database too.
To insert a single property, we use 3 queries and because of that 3
database calls happens. This number multiplies by the number of properties
for that resource. If we had 10 properties for a resource, the registry
core will do additional 30 database calls when the resource get
updated. Because of this reason, the REG_PROPERTY and
REG_RESOURCE_PROPERTY tables keep growing.

Please note that this is one of the reasons why we see a performance
degradation when we connect to a remote database and do certain operations
like lifecycle management(since it uses properties to hold certain
information). AFAIK, most of our products use registry properties to store
various information and because of that this is a critical issue that needs
to be fixed.

Thanks,
Janaka

https://wso2.org/jira/browse/REGISTRY-870

[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/src/main/java/org/wso2/carbon/registry/core/dao/ResourceDAO.java

--
Janaka Ranabahu
Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : jan...@wso2.com
Blog : janakaranabahu.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] C4 product release - platform branching

2012-07-16 Thread Pradeep Fernando

Hi folks,

we are nearly done with carbon-kernel branching. (not done done at the
moment - there are few test failures and chethiya is looking in to that.)
I think we should start on platform branching as well.

For that we have to,
* code freeze the platform
* apply branching strategy
* add branched kernel as the dependency

this is bit of a time consuming task. So we better start now.
WDYT ?

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

Re: [Dev] [Architecture] Missing methods in ResourceDAO interface of registry core

2012-07-16 Thread Senaka Fernando

Hi Janaka,

Are you suggesting that this needs to be done for C4? Or is this e-mail FTR?

Thanks,
Senaka.

On Mon, Jul 16, 2012 at 3:40 PM, Janaka Ranabahu jan...@wso2.com wrote:

Hi All,

Thanks,
Janaka

https://wso2.org/jira/browse/REGISTRY-870

[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/src/main/java/org/wso2/carbon/registry/core/dao/ResourceDAO.java

--
Janaka Ranabahu
Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : jan...@wso2.com
Blog : janakaranabahu.blogspot.com

___
Architecture mailing list
architect...@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

--
*Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

Re: [Dev] C4 product release - platform branching

2012-07-16 Thread Senaka Fernando

Hi all,

Have we done a dry run of branching the platform (like what Milinda did in
the past) to see whether it works as yet?

Thanks,
Senaka.

On Mon, Jul 16, 2012 at 5:52 PM, Pradeep Fernando prad...@wso2.com wrote:

 Hi folks,

 we are nearly done with carbon-kernel branching. (not done done at the
 moment - there are few test failures and chethiya is looking in to that.)
 I think we should start on platform branching as well.

 For that we have to,
 * code freeze the platform
 * apply branching strategy
 * add branched kernel as the dependency

 this is bit of a time consuming task. So we better start now.
 WDYT ?

 --Pradeep

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




-- 
*Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

Re: [Dev] G-Reg 4.5.0-Alpha-2 Released.

2012-07-16 Thread Prabath Siriwardena

Hi Subash,

Can you please make sure that we pass all the G-Reg integration tests
before we release next packs...

Thanks  regards,
-Prabath

On Fri, Jul 13, 2012 at 11:22 PM, Subash Chaturanga sub...@wso2.com wrote:

 Hi All,

 Please find the G-Reg 4.5.0-Alpha-2 pack at [1] and resolved JIRAs at [2].

 [1] -
 https://svn.wso2.com/wso2/svn/wso2/scratch/subash/latest-packs/alpha-2/
 [2] -
 https://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+REGISTRY+AND+fixVersion+%3D+%224.5.0+Beta%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide

 --

 Subash Chaturanga
 Software Engineer
 WSO2 Inc. http://wso2.com

 email - sub...@wso2.com
 phone - 077 2225922




-- 
Thanks  Regards,
Prabath

Mobile : +94 71 809 6732

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

[Dev] Working from home - 17/07/2012

2012-07-16 Thread Ruchira Wageesha

$subject.

-- 
*Ruchira Wageesha
Senior Software Engineer  Member, Management Committee, Development
Technologies*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: ruch...@wso2.com,   blog: ruchirawageesha.blogspot.com,   mobile:
+94 77 5493444*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] G-Reg 4.5.0-Alpha-2 Released.

2012-07-16 Thread Ajith Vitharana

On Tue, Jul 17, 2012 at 7:32 AM, Prabath Siriwardena prab...@wso2.comwrote:

 Hi Subash,

 Can you please make sure that we pass all the G-Reg integration tests
 before we release next packs...


Hi Prabath,

We have already released all the  milestone packs and alpha release after
verify all the integration tests. However, after merged the system test
framework with G-Reg some amounts of tests are failing. Following is the
current stats of integration tests, and we will fix the failing tests
before the beta release.

*Tests run: 852, Failures: 100, Errors: 0, Skipped: 20*
*
*
Thanks
Ajith



 Thanks  regards,
 -Prabath

 On Fri, Jul 13, 2012 at 11:22 PM, Subash Chaturanga sub...@wso2.comwrote:

 Hi All,

 Please find the G-Reg 4.5.0-Alpha-2 pack at [1] and resolved JIRAs at
 [2].

 [1] -
 https://svn.wso2.com/wso2/svn/wso2/scratch/subash/latest-packs/alpha-2/
 [2] -
 https://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+REGISTRY+AND+fixVersion+%3D+%224.5.0+Beta%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide

 --

 Subash Chaturanga
 Software Engineer
 WSO2 Inc. http://wso2.com

 email - sub...@wso2.com
 phone - 077 2225922




 --
 Thanks  Regards,
 Prabath

 Mobile : +94 71 809 6732

 http://blog.facilelogin.com
 http://RampartFAQ.com


 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94714631794
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] G-Reg 4.5.0-Alpha-2 Released.

2012-07-16 Thread Prabath Siriwardena

Thanks Ajith for looking in to this...

Regards,
-Prabath

On Tue, Jul 17, 2012 at 8:44 AM, Ajith Vitharana aji...@wso2.com wrote:



 On Tue, Jul 17, 2012 at 7:32 AM, Prabath Siriwardena prab...@wso2.comwrote:

 Hi Subash,

 Can you please make sure that we pass all the G-Reg integration tests
 before we release next packs...


 Hi Prabath,

 We have already released all the  milestone packs and alpha release after
 verify all the integration tests. However, after merged the system test
 framework with G-Reg some amounts of tests are failing. Following is the
 current stats of integration tests, and we will fix the failing tests
 before the beta release.

 *Tests run: 852, Failures: 100, Errors: 0, Skipped: 20*
 *
 *
 Thanks
 Ajith



 Thanks  regards,
 -Prabath

 On Fri, Jul 13, 2012 at 11:22 PM, Subash Chaturanga sub...@wso2.comwrote:

 Hi All,

 Please find the G-Reg 4.5.0-Alpha-2 pack at [1] and resolved JIRAs at
 [2].

 [1] -
 https://svn.wso2.com/wso2/svn/wso2/scratch/subash/latest-packs/alpha-2/
 [2] -
 https://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+REGISTRY+AND+fixVersion+%3D+%224.5.0+Beta%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide

 --

 Subash Chaturanga
 Software Engineer
 WSO2 Inc. http://wso2.com

 email - sub...@wso2.com
 phone - 077 2225922




 --
 Thanks  Regards,
 Prabath

 Mobile : +94 71 809 6732

 http://blog.facilelogin.com
 http://RampartFAQ.com


 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94714631794



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




-- 
Thanks  Regards,
Prabath

Mobile : +94 71 809 6732

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

Re: [Dev] Shall we ship a jax-rs application by default for super tenant?

2012-07-16 Thread Isuru Suriarachchi

+1. Please go ahead..

Thanks,
~Isuru

On Mon, Jul 16, 2012 at 7:54 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 How about $subject. Currently at initial startup jax-rs applications page
 is empty. This would help usability as well.

 thanks,
 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

Re: [Dev] [Architecture] Missing methods in ResourceDAO interface of registry core

Hi Senaka,

On Tue, Jul 17, 2012 at 4:52 AM, Senaka Fernando sen...@wso2.com wrote:

Hi Janaka,

Are you suggesting that this needs to be done for C4? Or is this e-mail
FTR?

We are not in a position to do this for C4. But if we are doing a patch
release in the kernel before C5, then my strong belief is that we should
fix this in that patch release.

Thanks,
Janaka

Thanks,
Senaka.

On Mon, Jul 16, 2012 at 3:40 PM, Janaka Ranabahu jan...@wso2.com wrote:

Hi All,

Thanks,
Janaka

https://wso2.org/jira/browse/REGISTRY-870

[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/src/main/java/org/wso2/carbon/registry/core/dao/ResourceDAO.java

--
Janaka Ranabahu
Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : jan...@wso2.com
Blog : janakaranabahu.blogspot.com

___
Architecture mailing list
architect...@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

--
*Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware

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

--
Janaka Ranabahu
Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : jan...@wso2.com
Blog : janakaranabahu.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB 4.5.0 - M2 Released

2012-07-16 Thread Isuru Udana

Hi All,

Please find the ESB 4.5.0 M2 Build at [1].

[1] http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-305/artifact/JOB1/ESB


Release Notes - WSO2 ESB - Version 4.5.0 M2

Bug

   - [ESBJAVA-932 https://wso2.org/jira/browse/ESBJAVA-932] - Application
   server logo missing on ESB About page
   - [ESBJAVA-942 https://wso2.org/jira/browse/ESBJAVA-942] - Unable to
   execute query
   - [ESBJAVA-970 https://wso2.org/jira/browse/ESBJAVA-970] - [Message
   Processors] - All sequences defined within ESB should be listed in a drop
   down for Message Sampling Processor  Scheduled Message Forwarding
   Processor UIs
   - [ESBJAVA-981 https://wso2.org/jira/browse/ESBJAVA-981] - [url
   rewrite mediator] Certain options are not available when editing rules in
   url rewrite mediator
   - [ESBJAVA-995 https://wso2.org/jira/browse/ESBJAVA-995] - [url
   rewrite mediator] If a wrong condition is added to a rewrite url, all the
   other previous configurations (previously added actions) are lost
   - [ESBJAVA-1001 https://wso2.org/jira/browse/ESBJAVA-1001] - [url
   rewrite mediator] Additional text box appear after updating the rewrite
   rule when action = Remove
   - [ESBJAVA-1002 https://wso2.org/jira/browse/ESBJAVA-1002] - [url
   rewrite mediator] Port is also removed when removing Host
   - [ESBJAVA-1004 https://wso2.org/jira/browse/ESBJAVA-1004] - [url
   rewrite mediator] NPE thrown if xpath expresson does not match the name of
   property (It's better if that error is handled properly)
   - [ESBJAVA-1011 https://wso2.org/jira/browse/ESBJAVA-1011] - Inlined
   Endpoint should have a delete button and the 'Add' button should be removed
   after adding a uri.
   - [ESBJAVA-1012 https://wso2.org/jira/browse/ESBJAVA-1012] - After
   creating an in-lined endpoint the ep details are not appearing in UI
   - [ESBJAVA-1013 https://wso2.org/jira/browse/ESBJAVA-1013] - [url
   rewrite mediator] The url is replaced without appending when action=append
   and fragment=full (the expected behavior is not clear)
   - [ESBJAVA-1016 https://wso2.org/jira/browse/ESBJAVA-1016] - [Fault
   mediator] How can a user create a fault mediator through UI which can
   handle POX faults
   - [ESBJAVA-1050 https://wso2.org/jira/browse/ESBJAVA-1050] - Pattern
   attribute of the property mediator does not seem to work
   - [ESBJAVA-1052 https://wso2.org/jira/browse/ESBJAVA-1052] -
   Properties can be created with names containing special characters. But
   Such properties cannot be used in some Xpath expressions.
   - [ESBJAVA-1056 https://wso2.org/jira/browse/ESBJAVA-1056] - [switch
   mediator] There should be an error/waring if source xpath is wrong
   - [ESBJAVA-1057 https://wso2.org/jira/browse/ESBJAVA-1057] - ESB UI:
   When specifying an invalid data type for a property value of property
   mediator, it cannot be changed to correct type
   - [ESBJAVA-1067 https://wso2.org/jira/browse/ESBJAVA-1067] - [Enrich
   mediator] Message is not enriched when trying to replace a property value
   with inline content of source configuration
   - [ESBJAVA-1080 https://wso2.org/jira/browse/ESBJAVA-1080] - [Cache
   mediator] - Unable to set scope=Per-Mediator
   - [ESBJAVA-1083 https://wso2.org/jira/browse/ESBJAVA-1083] -
   SynapseException: A fault node does not apply to a SOAP 1.1 fault error
   occurs when changing soap1.2 fault into 1.1 fault
   - [ESBJAVA-1087 https://wso2.org/jira/browse/ESBJAVA-1087] - [Cache
   mediator] - Cannot add dynamic sequences to onCacheHit sequence
   - [ESBJAVA-1090 https://wso2.org/jira/browse/ESBJAVA-1090] -
   ERROR_DETAIL gives the error message and ERROR_EXCEPTION returns null in
   case of an error
   - [ESBJAVA-1097 https://wso2.org/jira/browse/ESBJAVA-1097] - [Cache
   mediator] - Block using non collector cache type to out sequence in UI and
   vise versa
   - [ESBJAVA-1121 https://wso2.org/jira/browse/ESBJAVA-1121] - [Fault
   mediator] Additional detail tag added every time fault mediator
   configuration is updated
   - [ESBJAVA-1123 https://wso2.org/jira/browse/ESBJAVA-1123] - [Payload
   Factory mediator] In Arguments section, 'Namespace Editor' Column is
   visible even when 'Value' type is selected.
   - [ESBJAVA-1129 https://wso2.org/jira/browse/ESBJAVA-1129] - [Payload
   Factory mediator] When an invalid Namespace URI is given for an argument,
   ESB sends a invalid payload to the backend.
   - [ESBJAVA-1134 https://wso2.org/jira/browse/ESBJAVA-1134] - [Script
   mediator] - Include key doesn't get updated when you change it from source
   view
   - [ESBJAVA-1136 https://wso2.org/jira/browse/ESBJAVA-1136] - [Script
   mediator] - Dynamic key becomes un-editable from design-view after the
   mediator configuration is saved
   - [ESBJAVA-1138 https://wso2.org/jira/browse/ESBJAVA-1138] - [Enrich
   mediator] Source configuration does not get added as child of the specified
   property
   - [ESBJAVA-1172 https://wso2.org/jira/browse/ESBJAVA-1172] - ESB:
   Prompt a message before updating the

Re: [Dev] C4 product release - platform branching

2012-07-16 Thread Dimuthu Leelarathne

Hi RMs,

Please respond to this thread and raise your concerns.

On Tue, Jul 17, 2012 at 3:22 AM, Pradeep Fernando prad...@wso2.com wrote:

 Hi folks,

 we are nearly done with carbon-kernel branching. (not done done at the
 moment - there are few test failures and chethiya is looking in to that.)
 I think we should start on platform branching as well.

 For that we have to,
 * code freeze the platform


We don't need to code freeze. But we can freeze during the branching
duration.


 * apply branching strategy
 * add branched kernel as the dependency


thanks,
dimuthu


 this is bit of a time consuming task. So we better start now.
 WDYT ?

 --Pradeep

 ___
 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] AS startup warn: Error occurred while activating the UrlMapperServiceComponent

2012-07-16 Thread Reka Thirunavukkarasu

Hi

It is fixed in r133175.

Thanks,
Reka

On Mon, Jul 16, 2012 at 7:37 PM, Supun Malinga sup...@wso2.com wrote:
 $subject,
 Full log,

 [2012-07-16 19:32:56,488]  WARN
 {org.wso2.carbon.url.mapper.internal.UrlMapperServiceComponent} -  Error
 occurred while activating the UrlMapperServiceComponent
 java.lang.NullPointerException
 at
 org.wso2.carbon.url.mapper.internal.UrlMapperServiceComponent.addMappingToApplicationContext(UrlMapperServiceComponent.java:183)
 at
 org.wso2.carbon.url.mapper.internal.UrlMapperServiceComponent.activate(UrlMapperServiceComponent.java:100)
 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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
 at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
 at
 org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
 at
 org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
 at
 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
 at
 org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
 at
 org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.registerServices(DataSourceServiceComponent.java:102)
 at
 org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.initAllTenantUserDataSources(DataSourceServiceComponent.java:199)
 at
 org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.checkInitTenantUserDataSources(DataSourceServiceComponent.java:183)
 at
 org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.setRegistryService(DataSourceServiceComponent.java:133)
 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.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:367)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:430)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:415)
 at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:319)
 at
 org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
 at
 org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
 at
 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
 at
 org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
 at

Re: [Dev] Shall we ship a jax-rs application by default for super tenant?

Hi,

Will use the jaxrs_basic sample for this.

thanks,

On Tue, Jul 17, 2012 at 9:17 AM, Isuru Suriarachchi is...@wso2.com wrote:

 +1. Please go ahead..

 Thanks,
 ~Isuru

 On Mon, Jul 16, 2012 at 7:54 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 How about $subject. Currently at initial startup jax-rs applications page
 is empty. This would help usability as well.

 thanks,
 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Supun Malinga,

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

Re: [Dev] [Architecture] G-Reg 4.5.0-Alpha-2 Released.

Hi Samisa

On Tue, Jul 17, 2012 at 9:46 AM, Samisa Abeysinghe sam...@wso2.com wrote:



 On Tue, Jul 17, 2012 at 8:44 AM, Ajith Vitharana aji...@wso2.com wrote:



 On Tue, Jul 17, 2012 at 7:32 AM, Prabath Siriwardena prab...@wso2.comwrote:

 Hi Subash,

 Can you please make sure that we pass all the G-Reg integration tests
 before we release next packs...


 Hi Prabath,

 We have already released all the  milestone packs and alpha release after
 verify all the integration tests. However, after merged the system test
 framework with G-Reg some amounts of tests are failing. Following is the
 current stats of integration tests, and we will fix the failing tests
 before the beta release.


 I hope the fixes will include the skipped ones as well?


Yes, there are about nine tests on governance api which has skipped and
those needs to be fixed.





 *Tests run: 852, Failures: 100, Errors: 0, Skipped: 20*
 *
 *
 Thanks
 Ajith



 Thanks  regards,
 -Prabath

 On Fri, Jul 13, 2012 at 11:22 PM, Subash Chaturanga sub...@wso2.comwrote:

 Hi All,

 Please find the G-Reg 4.5.0-Alpha-2 pack at [1] and resolved JIRAs at
 [2].

 [1] -
 https://svn.wso2.com/wso2/svn/wso2/scratch/subash/latest-packs/alpha-2/
 [2] -
 https://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+REGISTRY+AND+fixVersion+%3D+%224.5.0+Beta%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide

 --

 Subash Chaturanga
 Software Engineer
 WSO2 Inc. http://wso2.com

 email - sub...@wso2.com
 phone - 077 2225922




 --
 Thanks  Regards,
 Prabath

 Mobile : +94 71 809 6732

 http://blog.facilelogin.com
 http://RampartFAQ.com


 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94714631794



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

 Thanks,
 Samisa...

 Samisa Abeysinghe
 VP Engineering
 WSO2 Inc.
 http://wso2.com
 http://wso2.org



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




-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C4 product release - platform branching

2012-07-16 Thread Ajith Vitharana

On Tue, Jul 17, 2012 at 10:13 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:

 Hi RMs,

 Please respond to this thread and raise your concerns.


The G-Reg plan is to fix remains  L1 issues in this week. Therefore, if you
are planing to branch in this week , we have to extend the  fixed date of
L1 issues that is depended on the trunk frozen time.


 On Tue, Jul 17, 2012 at 3:22 AM, Pradeep Fernando prad...@wso2.comwrote:

 Hi folks,

 we are nearly done with carbon-kernel branching. (not done done at the
 moment - there are few test failures and chethiya is looking in to that.)
 I think we should start on platform branching as well.

 For that we have to,
 * code freeze the platform


 We don't need to code freeze. But we can freeze during the branching
 duration.


 * apply branching strategy
 * add branched kernel as the dependency



Thanks
Ajith

thanks,
 dimuthu


 this is bit of a time consuming task. So we better start now.
 WDYT ?

 --Pradeep

 ___
 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




-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94714631794
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Commits] [Carbon-platform] svn commit r132727 - carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadm

2012-07-16 Thread Hiranya Jayathilaka

I don't think this fix is correct. It's introducing an unnecessary compile
time dependency between synapse-config-admin and sequence editor. Why don't
you use the SequenceMediatorFactory class from Synapse directly?

Thanks,
Hiranya

On Thu, Jul 12, 2012 at 3:52 PM, dus...@wso2.com wrote:

 Author: dushan
 Date: Thu Jul 12 06:22:20 2012
 New Revision: 132727
 URL: http://wso2.org/svn/browse/wso2?view=revrevision=132727

 Log:
 Properties can be created with names containing special characters. But
 Such properties cannot be used in some Xpath expressions.
 https://wso2.org/jira/browse/ESBJAVA-1052


 Modified:

  
 carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java

 Modified:
 carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
 URL:
 http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java?rev=132727r1=132726r2=132727view=diff

 ==
 ---
 carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
 (original)
 +++
 carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
 Thu Jul 12 06:22:20 2012
 @@ -27,6 +27,9 @@
  import org.apache.synapse.core.axis2.ProxyService;
  import org.apache.synapse.endpoints.Endpoint;
  import org.apache.synapse.endpoints.WSDLEndpoint;
 +import org.wso2.carbon.mediator.service.MediatorService;
 +import org.wso2.carbon.mediator.service.MediatorStore;
 +import org.wso2.carbon.mediator.service.builtin.SequenceMediator;

  import javax.xml.namespace.QName;
  import java.io.IOException;
 @@ -62,6 +65,8 @@
  validateProxyService(child, errors);
  } else if
 (XMLConfigConstants.ENDPOINT_ELT.equals(child.getQName())) {
  validateEndpoint(child, errors);
 +}else
 if(XMLConfigConstants.SEQUENCE_ELT.equals(child.getQName())){
 +   validateSequence(child,errors);
  }
  }
  }
 @@ -72,6 +77,16 @@
  return null;
  }

 +   private void validateSequence(OMElement
 sequenceElement,ListValidationError errors) {
 +   try{
 +MediatorService service =
 MediatorStore.getInstance().getMediatorService(sequenceElement);
 +SequenceMediator sequence = (SequenceMediator)
 service.getMediator();
 +sequence.build(sequenceElement);
 +   }catch (Exception e) {
 +  errors.add(newValidationError(sequenceElement,
 e.getMessage()));
 +   }
 +}
 +
  private void validateProxyService(OMElement proxyElement,
 ListValidationError errors) {
  try {
  ProxyService proxy =
 ProxyServiceFactory.createProxy(proxyElement, new Properties());
 ___
 Commits mailing list
 comm...@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/commits




-- 
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Do we allow to add/view subscriptions on remote mounts ?

Hi Senaka

$subject?  Because current EventService does not support
#getAllSubscriptions(userName, url) and throws unsupported exception,
What was the decision behind this ? Because I didn't either see a TODO for
this.

Thanks
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C4 product release - platform branching

Hi All,

Shall we have some mechanism in place to automatically update branch/trunk
while devs only commit to trunk/branch?. That would reduce inconsistencies
between branch and trunk.
We had a discussion thread about this after last release AFAIR.

thanks,

On Tue, Jul 17, 2012 at 10:13 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:

 Hi RMs,

 Please respond to this thread and raise your concerns.

 On Tue, Jul 17, 2012 at 3:22 AM, Pradeep Fernando prad...@wso2.comwrote:

 Hi folks,

 we are nearly done with carbon-kernel branching. (not done done at the
 moment - there are few test failures and chethiya is looking in to that.)
 I think we should start on platform branching as well.

 For that we have to,
 * code freeze the platform


 We don't need to code freeze. But we can freeze during the branching
 duration.


 * apply branching strategy
 * add branched kernel as the dependency


 thanks,
 dimuthu


  this is bit of a time consuming task. So we better start now.
 WDYT ?

 --Pradeep

 ___
 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




-- 
Supun Malinga,

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

Re: [Dev] Do we allow to add/view subscriptions on remote mounts ?

Hi Subash,

On Tue, Jul 17, 2012 at 11:00 AM, Subash Chaturanga sub...@wso2.com wrote:

 Hi Senaka

 $subject?  Because current EventService does not support
 #getAllSubscriptions(userName, url) and throws unsupported exception,
 What was the decision behind this ? Because I didn't either see a TODO for
 this.


I believe we don't have a concept of remote subscriptions. Are you trying
to fix a JIRA here. If so, please send the JIRA id.

Thanks,
Janaka


 Thanks
 --

 Subash Chaturanga
 Software Engineer
 WSO2 Inc. http://wso2.com

 email - sub...@wso2.com
 phone - 077 2225922


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




-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : jan...@wso2.com
Blog : janakaranabahu.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Commits] [Carbon-platform] svn commit r132727 - carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadm

2012-07-16 Thread Dushan Abeyruwan

Hi
  Yes, your suggestion is correct, I will do required changers and  will
introduce SequenceMediatorFactory instead of invoking
MediatorService   service = MediatorStore.getInstance().
getMediatorService(sequenceElement);

cheers
Dushan


On Tue, Jul 17, 2012 at 10:58 AM, Hiranya Jayathilaka hira...@wso2.comwrote:

 I don't think this fix is correct. It's introducing an unnecessary compile
 time dependency between synapse-config-admin and sequence editor. Why don't
 you use the SequenceMediatorFactory class from Synapse directly?

 Thanks,
 Hiranya


 On Thu, Jul 12, 2012 at 3:52 PM, dus...@wso2.com wrote:

 Author: dushan
 Date: Thu Jul 12 06:22:20 2012
 New Revision: 132727
 URL: http://wso2.org/svn/browse/wso2?view=revrevision=132727

 Log:
 Properties can be created with names containing special characters. But
 Such properties cannot be used in some Xpath expressions.
 https://wso2.org/jira/browse/ESBJAVA-1052


 Modified:

  
 carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java

 Modified:
 carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
 URL:
 http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java?rev=132727r1=132726r2=132727view=diff

 ==
 ---
 carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
 (original)
 +++
 carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
 Thu Jul 12 06:22:20 2012
 @@ -27,6 +27,9 @@
  import org.apache.synapse.core.axis2.ProxyService;
  import org.apache.synapse.endpoints.Endpoint;
  import org.apache.synapse.endpoints.WSDLEndpoint;
 +import org.wso2.carbon.mediator.service.MediatorService;
 +import org.wso2.carbon.mediator.service.MediatorStore;
 +import org.wso2.carbon.mediator.service.builtin.SequenceMediator;

  import javax.xml.namespace.QName;
  import java.io.IOException;
 @@ -62,6 +65,8 @@
  validateProxyService(child, errors);
  } else if
 (XMLConfigConstants.ENDPOINT_ELT.equals(child.getQName())) {
  validateEndpoint(child, errors);
 +}else
 if(XMLConfigConstants.SEQUENCE_ELT.equals(child.getQName())){
 +   validateSequence(child,errors);
  }
  }
  }
 @@ -72,6 +77,16 @@
  return null;
  }

 +   private void validateSequence(OMElement
 sequenceElement,ListValidationError errors) {
 +   try{
 +MediatorService service =
 MediatorStore.getInstance().getMediatorService(sequenceElement);
 +SequenceMediator sequence = (SequenceMediator)
 service.getMediator();
 +sequence.build(sequenceElement);
 +   }catch (Exception e) {
 +  errors.add(newValidationError(sequenceElement,
 e.getMessage()));
 +   }
 +}
 +
  private void validateProxyService(OMElement proxyElement,
 ListValidationError errors) {
  try {
  ProxyService proxy =
 ProxyServiceFactory.createProxy(proxyElement, new Properties());
 ___
 Commits mailing list
 comm...@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/commits




 --
 Hiranya Jayathilaka
 Senior Technical Lead;
 WSO2 Inc.;  http://wso2.org
 E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
 Blog: http://techfeast-hiranya.blogspot.com




-- 
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Do we allow to add/view subscriptions on remote mounts ?