date:20130116

Re: [Dev] [Error] Worker/Mgr ESB 4.6.0 in Windows

2013-01-16 Thread Kasun Gajasinghe

On Wed, Jan 16, 2013 at 10:58 PM, Miyuru Wanninayaka wrote:

> AFIR you have to put SVNKit libs to repository/components/lib
>

Yes, but the folder location is repository/components/dropins though, isn't
it? Please share this file location [1]. And also I think it's important
that we provide/inform them the svnkit license explicitly.

[1] http://dist.wso2.org/tools/svnClientBundle-1.0.0.jar

Thanks,
KasunG

This is works OOTB on our linux machines because we already have command
> line svn client installed. Anyway using command line svn client is not
> production recommended and should use SVNKit.
>
>
> On Wed, Jan 16, 2013 at 10:45 PM, Dushan Abeyruwan wrote:
>
>> Hi
>>Getting error while running 1 worker node at windows XP with Dep Synch
>> enable.. I think this was well known issue any workaround ?
>>
>>
>> 2013-01-16 09:08:33,007 [-] [Framework Event Dispatcher]  WARN
>> MediationStatisticsComponent Can't register an observer for
>> mediationStatisticsStore. If you have disabled StatisticsReporter, please
>> enable it in the Carbon.xml
>> 2013-01-16 09:10:14,499 [-] [Start Level Event Dispatcher]  WARN
>> ValidationResultPrinter RAM size (MB): 2047 of the system is below the
>> recommended minimum size :2048
>> 2013-01-16 09:11:48,945 [-] [Framework Event Dispatcher] ERROR
>> DeploymentSynchronizerComponent Error while initializing a deployment
>> synchronizer for the super tenant Carbon repository
>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException:
>> No Repository found for type svn
>> at
>> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getDeploymentSyncConfiguration(CarbonRepositoryUtils.java:165)
>>  at
>> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getActiveSynchronizerConfiguration(CarbonRepositoryUtils.java:97)
>>  at
>> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.isSynchronizerEnabled(CarbonRepositoryUtils.java:235)
>> at
>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.initDeploymentSynchronizerForSuperTenant(DeploymentSynchronizerComponent.java:100)
>>  at
>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.activate(DeploymentSynchronizerComponent.java:77)
>> 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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:513)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
>>  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.eventmg

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #21 was SUCCESSFUL. Change made by hasini and dileepa.

2013-01-16 Thread Bamboo


---
WSO2 Carbon 4.0.x > Kernel 4.0.6 > #21 was successful.
---
Code has been updated by hasini, dileepa.

http://wso2.org/bamboo/browse/WCB001-KER006-21/




--
Code Changes
--
hasini (153272):

>committing improvements done to multiple user store feature as raised in a 
>support issue

dileepa (153274):

>fixing build failure by reordering component order in the build due to 
>dependencies



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

Re: [Dev] Make Sample projects open in the dev studio

2013-01-16 Thread Susankha Nirmala

Hi all,
i'm also working with geeth for achieve this. when some one import app
server samples, now it give some class paths missing errors. my task is
develop the dev studio end to set class path dependency.

Thanks
/Susankha


On Thu, Jan 17, 2013 at 12:52 PM, Geeth Munasinghe  wrote:

> Hi
>
> I will be working on the sample projects of app server in order to allow
> the users to open projects in  wso2 dev studio without errors.
>
> Objective is to import all projects in samples to dev studio
>
>1. Making all project open in dev studio in the workspace once
>workspace changed to sample folder
>2. Resolving classpath errors and unresolved dependencies.
>3. Creating new servlet 3 project with annotations
>4. Setting Icons to identify the project type
>5. Allowing to export as deployable.
>
> Thanks
>
> Geeth
>
> ___
> 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] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #20 has FAILED. Change made by dileepa.

2013-01-16 Thread Dileepa Jayakody

fixed in r153274 by rearranging the build-order of components in
patch-releases/4.0.6/core

Thanks,
Dileepa

On Thu, Jan 17, 2013 at 10:20 AM, Dileepa Jayakody  wrote:

> I'm looking into this.
>
> On Thu, Jan 17, 2013 at 3:27 AM, Bamboo  wrote:
>
>>  [image: Failed]  WSO2 Carbon 
>> 4.0.x› Kernel
>> 4.0.6  › 
>> #20
>> failed
>>
>> Changes by dileepa 
>>
>> No failed tests found, a possible compilation error.
>>Responsible No one is responsible for this build.
>>Failing Jobs  Job
>> Duration Tests[image: Failed]  Default 
>> Job (Default
>> Stage)  12 minutes  No tests found  
>> Logs|
>> Artifacts  
>> Code
>> Changes   View
>> full change details
>> dileepa 
>> incorperating serverStartupDuration param addition to ServerData  153256
>> dileepa 
>> updating features to incorperate ServerStartupDuration addition to
>> ServerData  153255dileepa
>> adding serverStartupDuration to ServerData so that it can be accessed via
>> ServerAdmin  153254 View 
>> Online
>> | Add 
>> Comments
>>
>> This message was sent by Atlassian Bamboo .
>>
>> If you wish to stop receiving these emails edit your user 
>> profileor notify
>> your administrator .
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>



-- 
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware

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

[Dev] Make Sample projects open in the dev studio

2013-01-16 Thread Geeth Munasinghe

Hi

I will be working on the sample projects of app server in order to allow
the users to open projects in  wso2 dev studio without errors.

Objective is to import all projects in samples to dev studio

   1. Making all project open in dev studio in the workspace once workspace
   changed to sample folder
   2. Resolving classpath errors and unresolved dependencies.
   3. Creating new servlet 3 project with annotations
   4. Setting Icons to identify the project type
   5. Allowing to export as deployable.

Thanks

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

Re: [Dev] Java Client for BPEL

2013-01-16 Thread Kishanthan Thangarajah

You have build rampart config [1] before invoking, which will solve this
issue.

Thanks,
Kishanthan.
[1] http://blog.thilinamb.com/2009/12/how-to-build-rampart-config.html

On Thu, Jan 17, 2013 at 9:57 AM, Harsha Thirimanna  wrote:

> Hi ,
> I am going to call BPEL Service from Java  that using Rampart policy.
>
> This is how I did that.
>
> *final String  EPR =
> configuration.getFirstProperty(AppFactoryConstants.BPS_SERVER_URL) +
> "ApplicationCreation";
>
> try {
>
> ServiceClient client = new ServiceClient(
> ServiceReferenceHolder.getInstance().getConfigContextService().getClientConfigContext(),
> null);
>
> // Set the endpoint address
> client.getOptions().setTo(new
> EndpointReference(EPR));
> client.engageModule("rampart");
> client.engageModule("addressing");
> String userName =
> configuration.getFirstProperty(AppFactoryConstants.SERVER_ADMIN_NAME);
> String password =
> configuration.getFirstProperty(AppFactoryConstants.SERVER_ADMIN_PASSWORD);
> client.getOptions().setUserName(userName);
> client.getOptions().setPassword(password);
>
>
> String configs =
> CarbonUtils.getCarbonConfigDirPath();
>
> client.getOptions().setProperty(RampartMessageData.KEY_RAMPART_POLICY,
> loadPolicy(configs + "/appfactory/bpel-policy.xml"));
>
> client.sendRobust(getPayload(applicationInfoBean));
>
>
>
> } catch (Exception e) {
> log.error(e);
> }*
>
>
> but thing is that , it says
>
> *org.apache.axis2.AxisFault: Missing wsse:Security header in request*
>
>
> thanks
> Harsha Thirimanna
>
>
>
>
>
> ___
> 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

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #20 has FAILED. Change made by dileepa.

2013-01-16 Thread Dileepa Jayakody

I'm looking into this.

On Thu, Jan 17, 2013 at 3:27 AM, Bamboo  wrote:

>  [image: Failed]  WSO2 Carbon 
> 4.0.x› Kernel
> 4.0.6  › 
> #20
> failed
>
> Changes by dileepa 
>
> No failed tests found, a possible compilation error.
>   Responsible No one is responsible for this build.
>   Failing Jobs Job
> Duration Tests[image: Failed]  Default 
> Job (Default
> Stage)  12 minutes  No tests found  
> Logs|
> Artifacts  
> Code
> Changes   View
> full change details
> dileepa 
> incorperating serverStartupDuration param addition to ServerData  153256
> dileepa 
> updating features to incorperate ServerStartupDuration addition to
> ServerData  153255dileepa
> adding serverStartupDuration to ServerData so that it can be accessed via
> ServerAdmin  153254 View 
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian Bamboo .
>
> If you wish to stop receiving these emails edit your user 
> profileor notify
> your administrator .
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware

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

[Dev] Java Client for BPEL

2013-01-16 Thread Harsha Thirimanna

Hi ,
I am going to call BPEL Service from Java  that using Rampart policy.

This is how I did that.

*final String  EPR =
configuration.getFirstProperty(AppFactoryConstants.BPS_SERVER_URL) +
"ApplicationCreation";

try {

ServiceClient client = new ServiceClient(
ServiceReferenceHolder.getInstance().getConfigContextService().getClientConfigContext(),
null);

// Set the endpoint address
client.getOptions().setTo(new
EndpointReference(EPR));
client.engageModule("rampart");
client.engageModule("addressing");
String userName =
configuration.getFirstProperty(AppFactoryConstants.SERVER_ADMIN_NAME);
String password =
configuration.getFirstProperty(AppFactoryConstants.SERVER_ADMIN_PASSWORD);
client.getOptions().setUserName(userName);
client.getOptions().setPassword(password);


String configs =
CarbonUtils.getCarbonConfigDirPath();

client.getOptions().setProperty(RampartMessageData.KEY_RAMPART_POLICY,
loadPolicy(configs + "/appfactory/bpel-policy.xml"));

client.sendRobust(getPayload(applicationInfoBean));



} catch (Exception e) {
log.error(e);
}*


but thing is that , it says

*org.apache.axis2.AxisFault: Missing wsse:Security header in request*


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

Re: [Dev] [Error] Deployment synchronizer throws null stream ESB 4.6.0 Wrk/Mgr

2013-01-16 Thread Sandapa Handakumbura

Hi Dushan,

I have reported same issue [1] last week.

[1] https://wso2.org/jira/browse/ESBJAVA-1742

Regards,
Sandapa


On Thu, Jan 17, 2013 at 7:46 AM, Dushan Abeyruwan  wrote:

> Hi
> Enable caching (via Mgr node) and when wkr node try to deploy the
> Proxy, it tries to load policy key (at the worker node ) I don't think
> there is anything to do with PT
> *
> *
> *   file trying to load,*
> *
>   
> conf:/repository/axis2/service-groups/TestProxy/services/TestProxy/policies/WSO2CachingPolicy
> *
>
>
> Carbon Core section
>
> private Policy getPolicyFromKey(String key, SynapseConfiguration
> synCfg) {
>
> synCfg.getEntryDefinition(key);
>   *  return PolicyEngine.getPolicy(*
> *
> SynapseConfigUtils.getStreamSource(synCfg.getEntry(key)).getInputStream());
> *
> }
>
> /**
>
> and throws following error
>
> y/deployment/server/synapse-configs/default/proxy-services/TestProxy.xml
> failed - Continue in fail-safe mode
> org.apache.synapse.SynapseException: Cannot convert null to a StreamSource
> at
> org.apache.synapse.config.SynapseConfigUtils.handleException(SynapseConfigUtils.java:576)
>  at
> org.apache.synapse.config.SynapseConfigUtils.getStreamSource(SynapseConfigUtils.java:77)
> at
> org.apache.synapse.core.axis2.ProxyService.getPolicyFromKey(ProxyService.java:686)
>  at
> org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:495)
> at
> org.apache.synapse.deployers.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:75)
>  at
> org.wso2.carbon.proxyadmin.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:73)
> at
> org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:172)
>  at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>  at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>  at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>  at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>  at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:67)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:112)
>  at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>  at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThre
>
>
> cheers,
> 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] [Error] Deployment synchronizer throws null stream ESB 4.6.0 Wrk/Mgr

2013-01-16 Thread Miyuru Wanninayaka

This has nothing to do with PTT. Seems policy resource was not replicated
to worker nodes with cause proxy deployment fail.

--
Sent from my mobile
On Jan 17, 2013 7:47 AM, "Dushan Abeyruwan"  wrote:

> Hi
> Enable caching (via Mgr node) and when wkr node try to deploy the
> Proxy, it tries to load policy key (at the worker node ) I don't think
> there is anything to do with PT
> *
> *
> *   file trying to load,*
> *
>   
> conf:/repository/axis2/service-groups/TestProxy/services/TestProxy/policies/WSO2CachingPolicy
> *
>
>
> Carbon Core section
>
> private Policy getPolicyFromKey(String key, SynapseConfiguration
> synCfg) {
>
> synCfg.getEntryDefinition(key);
>   *  return PolicyEngine.getPolicy(*
> *
> SynapseConfigUtils.getStreamSource(synCfg.getEntry(key)).getInputStream());
> *
> }
>
> /**
>
> and throws following error
>
> y/deployment/server/synapse-configs/default/proxy-services/TestProxy.xml
> failed - Continue in fail-safe mode
> org.apache.synapse.SynapseException: Cannot convert null to a StreamSource
> at
> org.apache.synapse.config.SynapseConfigUtils.handleException(SynapseConfigUtils.java:576)
>  at
> org.apache.synapse.config.SynapseConfigUtils.getStreamSource(SynapseConfigUtils.java:77)
> at
> org.apache.synapse.core.axis2.ProxyService.getPolicyFromKey(ProxyService.java:686)
>  at
> org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:495)
> at
> org.apache.synapse.deployers.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:75)
>  at
> org.wso2.carbon.proxyadmin.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:73)
> at
> org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:172)
>  at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>  at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>  at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>  at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>  at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:67)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:112)
>  at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>  at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThre
>
>
> cheers,
> 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

[Dev] [Error] Deployment synchronizer throws null stream ESB 4.6.0 Wrk/Mgr

2013-01-16 Thread Dushan Abeyruwan

Hi
Enable caching (via Mgr node) and when wkr node try to deploy the
Proxy, it tries to load policy key (at the worker node ) I don't think
there is anything to do with PT
*
*
*   file trying to load,*
*
  
conf:/repository/axis2/service-groups/TestProxy/services/TestProxy/policies/WSO2CachingPolicy
*


Carbon Core section

private Policy getPolicyFromKey(String key, SynapseConfiguration
synCfg) {

synCfg.getEntryDefinition(key);
  *  return PolicyEngine.getPolicy(*
*
SynapseConfigUtils.getStreamSource(synCfg.getEntry(key)).getInputStream());*
}

/**

and throws following error

y/deployment/server/synapse-configs/default/proxy-services/TestProxy.xml
failed - Continue in fail-safe mode
org.apache.synapse.SynapseException: Cannot convert null to a StreamSource
at
org.apache.synapse.config.SynapseConfigUtils.handleException(SynapseConfigUtils.java:576)
 at
org.apache.synapse.config.SynapseConfigUtils.getStreamSource(SynapseConfigUtils.java:77)
at
org.apache.synapse.core.axis2.ProxyService.getPolicyFromKey(ProxyService.java:686)
 at
org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:495)
at
org.apache.synapse.deployers.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:75)
 at
org.wso2.carbon.proxyadmin.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:73)
at
org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:172)
 at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
 at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
 at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
 at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
 at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:67)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:112)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
 at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThre


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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #20 has FAILED. Change made by dileepa.

2013-01-16 Thread Bamboo


---
WSO2 Carbon 4.0.x > Kernel 4.0.6 > #20 failed.
---
Code has been updated by dileepa.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER006-20/

-
Currently Responsible
-

No one is responsible for fixing this build.



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



--
Code Changes
--
dileepa (153254):

>adding serverStartupDuration to ServerData so that it can be accessed via 
>ServerAdmin

dileepa (153255):

>updating features to incorperate ServerStartupDuration addition to ServerData

dileepa (153256):

>incorperating serverStartupDuration param addition to ServerData



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #57 has FAILED (12 tests failed, 2 failures were new). Change made by 5 authors.

2013-01-16 Thread Bamboo


---
WSO2 Carbon 4.0.x > Products 4.0.6 > #57 failed.
---
Code has been updated by hasini, maninda, prabatha, dushan, thilini.
12/969 tests failed, 2 failures were new.

http://wso2.org/bamboo/browse/WCB001-PRO006-57/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): 12 of 969 tests failed.



--
Code Changes
--
thilini (153229):

>setting default to true

dushan (153248):

>added missing out tranformation

thilini (153232):

>wsdl update for email disable functionality



--
Tests
--
New Test Failures (2)
   - RetrieveBackendWsdlTestCase: Retrieve backend service wsdl
   - GETRequestHandlerTestCase: Proxy service w s d l
Existing Test Failures (10)
   - JAXWSSampleTestCase: J a x w s request
   - FailoverEndpointTestCase: Sending fail over endpoint with specific errors
   - AggregateWithHighMaxAndLowMinTestCase: Equalto maximum
   - SpringMediationTestCase: Upload sequence having invalid spring x m l test
   - SpringMediationTestCase: Upload sequence having non existing spring x m l 
resource test
   - XsltTransformationFromUrlTestCase: Upload synapse config
   - ConfiguringNhttpAccessLogLocationTestCase: Nhttp access log location
   - MessageWithoutContentTypeTestCase: Message without content type
   - MalformedHTTPRequestTest: Malformed u r l
   - UrlEncordedFormPostViaProxyTestCase: Https request via http proxy
Fixed Tests (3)
   - PropertyWithinSequenceTestCase: More number than maximum
   - JSONToSOAPConversionUsingSample440TestCase: J s o n to s o a p conversion
   - Sample440Test: J s o n mediation

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

[Dev] Purging and Archiving Cassandra data in BAM

2013-01-16 Thread Kasun Weranga

Hi,

I am going to do the $subject. Plan is to use map-reduce jobs to do the
purging and archival process, so it can handle the purging/archiving large
amount of data. This feature has ability to purge/archive data manually
by specifying a duration and also automatically purge/archive older data
(only keeping data of last N number of days). User can select the stream
name, version and the duration of the data that he needs to archive.

Here I have described the model that we came up to achieve the above
functionality.

1. Select the data specified in the time duration and insert those data
into a column family. (use a Hive query)
2. Insert rowkeys of selected data into a temporary CF (use a Hive query) -
 If we have large amount of data to archive, we can't keep all the rowkeys
in memory, so we insert them into a temp CF.
3. Write a class analyzer to read the rowkeys from temporary CF and then
delete data in the original CF (use custom map-reduce jobs), finally we
will delete the temporary CF.


Class analyzer can be included in a hive script, because of that
purging/archiving can be done using single Hive script that can be
generated programmatically. As a advantage of that we can reuse the
scheduling functionality implemented for Hive scripts as well.

This is the model we came up for archiving/purging Cassandra data in BAM,
if you have any concerns Please raise them.

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

Re: [Dev] [Error] Worker/Mgr ESB 4.6.0 in Windows

2013-01-16 Thread Miyuru Wanninayaka

AFIR you have to put SVNKit libs to repository/components/lib
This is works OOTB on our linux machines because we already have command
line svn client installed. Anyway using command line svn client is not
production recommended and should use SVNKit.

On Wed, Jan 16, 2013 at 10:45 PM, Dushan Abeyruwan  wrote:

> Hi
>Getting error while running 1 worker node at windows XP with Dep Synch
> enable.. I think this was well known issue any workaround ?
>
>
> 2013-01-16 09:08:33,007 [-] [Framework Event Dispatcher]  WARN
> MediationStatisticsComponent Can't register an observer for
> mediationStatisticsStore. If you have disabled StatisticsReporter, please
> enable it in the Carbon.xml
> 2013-01-16 09:10:14,499 [-] [Start Level Event Dispatcher]  WARN
> ValidationResultPrinter RAM size (MB): 2047 of the system is below the
> recommended minimum size :2048
> 2013-01-16 09:11:48,945 [-] [Framework Event Dispatcher] ERROR
> DeploymentSynchronizerComponent Error while initializing a deployment
> synchronizer for the super tenant Carbon repository
> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException:
> No Repository found for type svn
> at
> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getDeploymentSyncConfiguration(CarbonRepositoryUtils.java:165)
>  at
> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getActiveSynchronizerConfiguration(CarbonRepositoryUtils.java:97)
>  at
> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.isSynchronizerEnabled(CarbonRepositoryUtils.java:235)
> at
> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.initDeploymentSynchronizerForSuperTenant(DeploymentSynchronizerComponent.java:100)
>  at
> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.activate(DeploymentSynchronizerComponent.java:77)
> 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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:513)
> at
> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
>  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)
> 2013-01-16 09:11:49,646 [-] [Framework Event Dispatcher]  WARN
> MediationStatisticsComponent Can't register an observer for
> mediationStatisticsStore. If you have disabled StatisticsReporter, please
> enable it in the Carbon.xml
> 2013-01-16 09:11:58,820 [-] [pool-8-thread-1] ERROR
> CarbonDeploymentSchedulerTask Deployment synchronization update for tenant
> -1234 failed
> ja

[Dev] [Error] Worker/Mgr ESB 4.6.0 in Windows

2013-01-16 Thread Dushan Abeyruwan

Hi
   Getting error while running 1 worker node at windows XP with Dep Synch
enable.. I think this was well known issue any workaround ?


2013-01-16 09:08:33,007 [-] [Framework Event Dispatcher]  WARN
MediationStatisticsComponent Can't register an observer for
mediationStatisticsStore. If you have disabled StatisticsReporter, please
enable it in the Carbon.xml
2013-01-16 09:10:14,499 [-] [Start Level Event Dispatcher]  WARN
ValidationResultPrinter RAM size (MB): 2047 of the system is below the
recommended minimum size :2048
2013-01-16 09:11:48,945 [-] [Framework Event Dispatcher] ERROR
DeploymentSynchronizerComponent Error while initializing a deployment
synchronizer for the super tenant Carbon repository
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No
Repository found for type svn
at
org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getDeploymentSyncConfiguration(CarbonRepositoryUtils.java:165)
 at
org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getActiveSynchronizerConfiguration(CarbonRepositoryUtils.java:97)
 at
org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.isSynchronizerEnabled(CarbonRepositoryUtils.java:235)
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.initDeploymentSynchronizerForSuperTenant(DeploymentSynchronizerComponent.java:100)
 at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.activate(DeploymentSynchronizerComponent.java:77)
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.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:513)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
 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)
2013-01-16 09:11:49,646 [-] [Framework Event Dispatcher]  WARN
MediationStatisticsComponent Can't register an observer for
mediationStatisticsStore. If you have disabled StatisticsReporter, please
enable it in the Carbon.xml
2013-01-16 09:11:58,820 [-] [pool-8-thread-1] ERROR
CarbonDeploymentSchedulerTask Deployment synchronization update for tenant
-1234 failed
java.lang.RuntimeException:
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No
Repository found for type svn
 at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:89)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncUpdate(CarbonDeploymentSchedulerTask.java:146)
 at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSche

Re: [Dev] Platform patch release 4.0.7 added to the branch

2013-01-16 Thread Pradeep Fernando

On Wed, Jan 16, 2013 at 9:49 PM, Hasini Gunasinghe  wrote:

> Hi Pradeep,
>
> On Wed, Jan 16, 2013 at 7:38 PM, Pradeep Fernando wrote:
>
>> hi all,
>>
>> - we should not create 4.0.7 components till we release 4.0.6 ones. When
>> you create 4.0.6 components, add them to the patch release poms, it has
>> nothing to do with product releases.
>> - do not include your  *product* build in patch release pom if it is not
>> get released with current patch release cycle. do the product builds
>> separately  (for alpha/beta releases based on 4.0.6 components)
>>
>
> When set of products get released, it is not quite feasible to build the
> products without adding them to patch release pom - specially when we are
> taking builds from builder machine. Also, 4.0.7 products needs 4.0.6 kernel
> to be built while 4.0.6 products do not.
>

AS guys are planning for a 4.0.8 release at the moment. If we follow the
same pattern they will create 4.0.8 components, 4.0.7 kernel.

Getting packs from builder machine is not that hard. Is it ? Do a local
edit in the product patch release pom and get the  pack.


>
> - You guys havent done anything wrong, but above is the convention that we
>> sticked to..
>>
>
> If there is not anything wrong, can't we change the convention when
> requirement arises and for valid requirement?  :)
>

Problem being, down the line , some people will find it hard to figure out
what happened, why ? Lets not change it all of a sudden - in a middle of a
release cycle.



>
> Thanks,
> Hasini.
>
>>
>> I know, this is a tedious thing to do. Lets refine the process in the
>> next release. :)
>>
>> thanks,
>> --Pradeep
>>
>
>


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

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

Re: [Dev] Platform patch release 4.0.7 added to the branch

2013-01-16 Thread Hasini Gunasinghe

Hi Pradeep,

On Wed, Jan 16, 2013 at 7:38 PM, Pradeep Fernando  wrote:

> hi all,
>
> - we should not create 4.0.7 components till we release 4.0.6 ones. When
> you create 4.0.6 components, add them to the patch release poms, it has
> nothing to do with product releases.
> - do not include your  *product* build in patch release pom if it is not
> get released with current patch release cycle. do the product builds
> separately  (for alpha/beta releases based on 4.0.6 components)
>

When set of products get released, it is not quite feasible to build the
products without adding them to patch release pom - specially when we are
taking builds from builder machine. Also, 4.0.7 products needs 4.0.6 kernel
to be built while 4.0.6 products do not.

- You guys havent done anything wrong, but above is the convention that we
> sticked to..
>

If there is not anything wrong, can't we change the convention when
requirement arises and for valid requirement?  :)

Thanks,
Hasini.

>
> I know, this is a tedious thing to do. Lets refine the process in the next
> release. :)
>
> thanks,
> --Pradeep
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Platform patch release 4.0.7 added to the branch

2013-01-16 Thread Pradeep Fernando

hi all,

- we should not create 4.0.7 components till we release 4.0.6 ones. When
you create 4.0.6 components, add them to the patch release poms, it has
nothing to do with product releases.
- do not include your  *product* build in patch release pom if it is not
get released with current patch release cycle. do the product builds
separately  (for alpha/beta releases based on 4.0.6 components)
- You guys havent done anything wrong, but above is the convention that we
sticked to..

I know, this is a tedious thing to do. Lets refine the process in the next
release. :)

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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #56 has FAILED (13 tests failed, 1 failures were new). Change made by hasini, vijitha and sanjeewa.

2013-01-16 Thread Bamboo


---
WSO2 Carbon 4.0.x > Products 4.0.6 > #56 failed.
---
Code has been updated by hasini, vijitha, sanjeewa.
13/969 tests failed, 1 failure was new.

http://wso2.org/bamboo/browse/WCB001-PRO006-56/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): 13 of 969 tests failed.



--
Code Changes
--
sanjeewa (153217):

>adding api manager features for 4.0.7

hasini (153221):

>creating 4.0.7 patch release.

sanjeewa (153216):

>



--
Tests
--
New Test Failures (1)
   - PropertyWithinSequenceTestCase: More number than maximum
Existing Test Failures (12)
   - JAXWSSampleTestCase: J a x w s request
   - FailoverEndpointTestCase: Sending fail over endpoint with specific errors
   - AggregateWithHighMaxAndLowMinTestCase: Equalto maximum
   - SpringMediationTestCase: Upload sequence having invalid spring x m l test
   - SpringMediationTestCase: Upload sequence having non existing spring x m l 
resource test
   - XsltTransformationFromUrlTestCase: Upload synapse config
   - ConfiguringNhttpAccessLogLocationTestCase: Nhttp access log location
   - MessageWithoutContentTypeTestCase: Message without content type
   - MalformedHTTPRequestTest: Malformed u r l
   - UrlEncordedFormPostViaProxyTestCase: Https request via http proxy
   - JSONToSOAPConversionUsingSample440TestCase: J s o n to s o a p conversion
   - Sample440Test: J s o n mediation
Fixed Tests (1)
   - ConcurrencyAndRequestThrottlingTestConcurrency: Concurrency and request 
based policy throttling concurrency

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

Re: [Dev] Platform patch release 4.0.7 added to the branch

2013-01-16 Thread Dileepa Jayakody

Hi Hasini, Janaka and all,

On Wed, Jan 16, 2013 at 5:19 PM, Hasini Gunasinghe  wrote:

>
>
> On Wed, Jan 16, 2013 at 5:02 PM, Dileepa Jayakody wrote:
>
>>
>>
>> On Wed, Jan 16, 2013 at 4:19 PM, Hasini Gunasinghe wrote:
>>
>>> Hi all,
>>>
>>> FYI...
>>> - $subject was done for the products to be released with platform 4.0.7
>>> - IS 4.1.0 uses kernel 4.0.6 which will also be released with platform
>>> 4.0.7
>>> - I hope there wont be issues in having two non-released platform patch
>>> release versions (i.e 4.0.6 and 4.0.7) at the moment - please let us know
>>> if there is any..
>>>
>>
>> I think this can result in the 4.0.6 tag having 4.0.7 components, then it
>> will be not compliant to our previous releases isn't it?
>> How about we commit the changes to 4.0.6 until it gets released and soon
>> after copy the changes and create 4.0.7?
>>
>
> Yes, we have been doing that, but since products which are not released
> with 4.0.6 were removed from 4.0.6 patch release, went for the option of
> creating 4.0.7. We can add them back to 4.0.6 till it is released.
>
> However, kernel 4.0.6 will not be released with platform 4.0.6 since 4.0.6
> products are using kernel 4.0.5. Therefore, even if we move 4.0.7 products
> and components to platform 4.0.6, we need to build kernel 4.0.6 with
> platform 4.0.6 if we go for the above option. Won't that add an additional
> overhead for 4.0.6 product release?
>

If some of already created 4.0.7 platform components depend on kernel 4.0.6
then I think we can't add the 4.0.7 changes back to 4.0.6 components and
not release kernel 4.0.6 (otherwise the platform 4.0.6 build could break).
Then I guess we have to go with the previous option of creating 4.0.7
components and have it built with kernel 4.0.6.

@Pradeep, do you have any opinion on a better solution for this?

Thanks,
Dileepa


>
> Thanks,
> Hasini.
>
>
>> - When building the packs for QA from builder machine, we can build
>>> platform patch release 4.0.6, kernel 4.0.6 and platform patch release 4.0.7
>>> - so that packs from both 4.0.6 and 4.0.7 will be available.
>>>
>>> Thanks,
>>> Hasini.
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dileepa Jayakody,
>> Software Engineer, WSO2 Inc.
>> Lean . Enterprise . Middleware
>>
>> Mobile : +94777-857616
>>
>
>


-- 
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware

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

Re: [Dev] Platform patch release 4.0.7 added to the branch

2013-01-16 Thread Hasini Gunasinghe

On Wed, Jan 16, 2013 at 5:02 PM, Dileepa Jayakody  wrote:

>
>
> On Wed, Jan 16, 2013 at 4:19 PM, Hasini Gunasinghe wrote:
>
>> Hi all,
>>
>> FYI...
>> - $subject was done for the products to be released with platform 4.0.7
>> - IS 4.1.0 uses kernel 4.0.6 which will also be released with platform
>> 4.0.7
>> - I hope there wont be issues in having two non-released platform patch
>> release versions (i.e 4.0.6 and 4.0.7) at the moment - please let us know
>> if there is any..
>>
>
> I think this can result in the 4.0.6 tag having 4.0.7 components, then it
> will be not compliant to our previous releases isn't it?
> How about we commit the changes to 4.0.6 until it gets released and soon
> after copy the changes and create 4.0.7?
>

Yes, we have been doing that, but since products which are not released
with 4.0.6 were removed from 4.0.6 patch release, went for the option of
creating 4.0.7. We can add them back to 4.0.6 till it is released.

However, kernel 4.0.6 will not be released with platform 4.0.6 since 4.0.6
products are using kernel 4.0.5. Therefore, even if we move 4.0.7 products
and components to platform 4.0.6, we need to build kernel 4.0.6 with
platform 4.0.6 if we go for the above option. Won't that add an additional
overhead for 4.0.6 product release?

Thanks,
Hasini.

> - When building the packs for QA from builder machine, we can build
>> platform patch release 4.0.6, kernel 4.0.6 and platform patch release 4.0.7
>> - so that packs from both 4.0.6 and 4.0.7 will be available.
>>
>> Thanks,
>> Hasini.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Platform patch release 4.0.7 added to the branch

2013-01-16 Thread Janaka Ranabahu

Hi Dileepa,


On Wed, Jan 16, 2013 at 5:02 PM, Dileepa Jayakody  wrote:

>
>
> On Wed, Jan 16, 2013 at 4:19 PM, Hasini Gunasinghe wrote:
>
>> Hi all,
>>
>> FYI...
>> - $subject was done for the products to be released with platform 4.0.7
>> - IS 4.1.0 uses kernel 4.0.6 which will also be released with platform
>> 4.0.7
>> - I hope there wont be issues in having two non-released platform patch
>> release versions (i.e 4.0.6 and 4.0.7) at the moment - please let us know
>> if there is any..
>>
>
> I think this can result in the 4.0.6 tag having 4.0.7 components, then it
> will be not compliant to our previous releases isn't it?
>
Is there any issue in this? IMO, this is ok as long as they are not
released.

Thanks,
Janaka

> How about we commit the changes to 4.0.6 until it gets released and soon
> after copy the changes and create 4.0.7?
>
> - When building the packs for QA from builder machine, we can build
>> platform patch release 4.0.6, kernel 4.0.6 and platform patch release 4.0.7
>> - so that packs from both 4.0.6 and 4.0.7 will be available.
>>
>> Thanks,
>> Hasini.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Senior 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] Platform patch release 4.0.7 added to the branch

2013-01-16 Thread Dileepa Jayakody

On Wed, Jan 16, 2013 at 4:19 PM, Hasini Gunasinghe  wrote:

> Hi all,
>
> FYI...
> - $subject was done for the products to be released with platform 4.0.7
> - IS 4.1.0 uses kernel 4.0.6 which will also be released with platform
> 4.0.7
> - I hope there wont be issues in having two non-released platform patch
> release versions (i.e 4.0.6 and 4.0.7) at the moment - please let us know
> if there is any..
>

I think this can result in the 4.0.6 tag having 4.0.7 components, then it
will be not compliant to our previous releases isn't it?
How about we commit the changes to 4.0.6 until it gets released and soon
after copy the changes and create 4.0.7?

- When building the packs for QA from builder machine, we can build
> platform patch release 4.0.6, kernel 4.0.6 and platform patch release 4.0.7
> - so that packs from both 4.0.6 and 4.0.7 will be available.
>
> Thanks,
> Hasini.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware

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

[Dev] Platform patch release 4.0.7 added to the branch

2013-01-16 Thread Hasini Gunasinghe

Hi all,

FYI...
- $subject was done for the products to be released with platform 4.0.7
- IS 4.1.0 uses kernel 4.0.6 which will also be released with platform 4.0.7
- I hope there wont be issues in having two non-released platform patch
release versions (i.e 4.0.6 and 4.0.7) at the moment - please let us know
if there is any..
- When building the packs for QA from builder machine, we can build
platform patch release 4.0.6, kernel 4.0.6 and platform patch release 4.0.7
- so that packs from both 4.0.6 and 4.0.7 will be available.

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

[Dev] App Factory - UI Review Notes

2013-01-16 Thread Dimuthu Leelarathne

Hi all,

Here are the UI review notes.

General - Change the font to Halwitica, Droide

Home page changes
=

   - Remove the top icons
   - Sign In - Sign Up - Make same languag - more focus on Sign Up
   - Unify the banner - bottom and top
   - Break the "About AppFactory" from Login
   - External link icon to top
   - Embed the Video to Banner


User Home
=

   - Add external liks after login as well
   - Use standard breadcrumbs
   - Add Applications cage
  - If no apps highlight the learn about and resources
  - If more than one app then list the apps and move the resources to
  rightmost corner
  - Remove application name
  - Put "Add Apps" button on left
   - Put the "You have new tasks" on top right hand corner

App Home


   - Remove version chart
   - Put AppName on top of icons
   - Put a name to each page on left hand corner
   - Remove the vertical bar on menus
   - Remove the "Unactivated look" from icons

Please add if I miss something.

thanks,

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

Re: [Dev] APIM documentation does not mention about the key manager

2013-01-16 Thread Nirdesha Munasinghe

Hi Sanjeewa,

Thanks. Will take the content from your OT article.

Regards,
-Nirdesha

On Wed, Jan 16, 2013 at 3:13 PM, Sanjeewa Malalgoda wrote:

> HI Nirdesha,
> I have done article describing all these components and their usages(on
> publishing process). So we can take content directly from that and update
> document.
>
> Thanks.
>
> On Wed, Jan 16, 2013 at 3:09 PM, Nirdesha Munasinghe wrote:
>
>> Hi Amila,
>>
>> I will write up a description which the team can add in to. Key manager
>> should appear as a component here. Thanks for pointing out.
>>
>> Regards,
>> -Nirdesha
>>
>>
>> On Wed, Jan 16, 2013 at 2:56 PM, Amila Maha Arachchi wrote:
>>
>>> Hi,
>>>
>>> [1] Does not mention about the key manager components of APIM. Any
>>> reason?
>>>
>>> [1] http://docs.wso2.org/wiki/display/AM130/API+Manager+Components
>>>
>>> Regards,
>>> AmilaM.
>>>
>>> --
>>> *Amila Maharachchi*
>>> Technical Lead
>>> Member, Management Committee - Cloud & Platform TG
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Blog: http://maharachchi.blogspot.com
>>> Mobile: +94719371446
>>>
>>>
>>
>>
>> --
>>
>> Thanks,
>>
>> Nirdesha Munasinghe,
>> WSO2 Inc.
>> Web:http://wso2.com
>>
>> Mobile: +94 776321920
>>
>
>
>
> --
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +14084122175 | +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>



-- 

Thanks,

Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com

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

Re: [Dev] APIM documentation does not mention about the key manager

2013-01-16 Thread Sanjeewa Malalgoda

HI Nirdesha,
I have done article describing all these components and their usages(on
publishing process). So we can take content directly from that and update
document.

Thanks.

On Wed, Jan 16, 2013 at 3:09 PM, Nirdesha Munasinghe wrote:

> Hi Amila,
>
> I will write up a description which the team can add in to. Key manager
> should appear as a component here. Thanks for pointing out.
>
> Regards,
> -Nirdesha
>
>
> On Wed, Jan 16, 2013 at 2:56 PM, Amila Maha Arachchi wrote:
>
>> Hi,
>>
>> [1] Does not mention about the key manager components of APIM. Any reason?
>>
>> [1] http://docs.wso2.org/wiki/display/AM130/API+Manager+Components
>>
>> Regards,
>> AmilaM.
>>
>> --
>> *Amila Maharachchi*
>> Technical Lead
>> Member, Management Committee - Cloud & Platform TG
>> WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446
>>
>>
>
>
> --
>
> Thanks,
>
> Nirdesha Munasinghe,
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 776321920
>



-- 
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +14084122175 | +94713068779

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

Re: [Dev] APIM documentation does not mention about the key manager

2013-01-16 Thread Nirdesha Munasinghe

Hi Amila,

I will write up a description which the team can add in to. Key manager
should appear as a component here. Thanks for pointing out.

Regards,
-Nirdesha

On Wed, Jan 16, 2013 at 2:56 PM, Amila Maha Arachchi wrote:

> Hi,
>
> [1] Does not mention about the key manager components of APIM. Any reason?
>
> [1] http://docs.wso2.org/wiki/display/AM130/API+Manager+Components
>
> Regards,
> AmilaM.
>
> --
> *Amila Maharachchi*
> Technical Lead
> Member, Management Committee - Cloud & Platform TG
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>

-- 

Thanks,

Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com

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

[Dev] APIM documentation does not mention about the key manager

2013-01-16 Thread Amila Maha Arachchi

Hi,

[1] Does not mention about the key manager components of APIM. Any reason?

[1] http://docs.wso2.org/wiki/display/AM130/API+Manager+Components

Regards,
AmilaM.

-- 
*Amila Maharachchi*
Technical Lead
Member, Management Committee - Cloud & Platform TG
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Error] Worker/Mgr ESB 4.6.0 in Windows

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #21 was SUCCESSFUL. Change made by hasini and dileepa.

Re: [Dev] Make Sample projects open in the dev studio

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #20 has FAILED. Change made by dileepa.

[Dev] Make Sample projects open in the dev studio

Re: [Dev] Java Client for BPEL

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #20 has FAILED. Change made by dileepa.

[Dev] Java Client for BPEL

Re: [Dev] [Error] Deployment synchronizer throws null stream ESB 4.6.0 Wrk/Mgr

Re: [Dev] [Error] Deployment synchronizer throws null stream ESB 4.6.0 Wrk/Mgr

[Dev] [Error] Deployment synchronizer throws null stream ESB 4.6.0 Wrk/Mgr

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #20 has FAILED. Change made by dileepa.

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #57 has FAILED (12 tests failed, 2 failures were new). Change made by 5 authors.

[Dev] Purging and Archiving Cassandra data in BAM

Re: [Dev] [Error] Worker/Mgr ESB 4.6.0 in Windows

[Dev] [Error] Worker/Mgr ESB 4.6.0 in Windows

Re: [Dev] Platform patch release 4.0.7 added to the branch

Re: [Dev] Platform patch release 4.0.7 added to the branch

Re: [Dev] Platform patch release 4.0.7 added to the branch

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #56 has FAILED (13 tests failed, 1 failures were new). Change made by hasini, vijitha and sanjeewa.

Re: [Dev] Platform patch release 4.0.7 added to the branch

Re: [Dev] Platform patch release 4.0.7 added to the branch

Re: [Dev] Platform patch release 4.0.7 added to the branch

Re: [Dev] Platform patch release 4.0.7 added to the branch

[Dev] Platform patch release 4.0.7 added to the branch

[Dev] App Factory - UI Review Notes

Re: [Dev] APIM documentation does not mention about the key manager

Re: [Dev] APIM documentation does not mention about the key manager

Re: [Dev] APIM documentation does not mention about the key manager

[Dev] APIM documentation does not mention about the key manager

30 matches

Site Navigation

Mail list logo

Footer information