from:"Dileepa Jayakody"

Re: [Dev] Error in wso2 apim 2.1.0 kubernetes deployment in google container engine

2017-09-28 Thread Dileepa Jayakody

Hi Pubudu et al,

The root cause was that the volumes were not getting created in the given
hostPaths at /tmp/data/. at the deployment time.

As suggested by Pubudu, we could get the issue fixed by setting the
StorageClass annotation :
storageclass.beta.kubernetes.io/is-default-class: *false*

Thanks Pubudu and all for the help.

Regards,
Dileepa

On Thu, Sep 28, 2017 at 12:50 PM, Pubudu Gunatilaka 
wrote:

> Hi Ayesh,
>
> This error comes when you don't have synapse artifacts in the
> deployment/server location.  As you are using host path for mounting, make
> sure host mount paths are empty or use the server folder files. There is a
> chance that mounts get exchanged as it dynamically pics the mounts when you
> redeploy the deployment.
>
> One solution is to delete the content in the host mounts when you are
> redeploying the entire deployment. As we are using host path, we need to
> restrict the deployment (ex: wso2apim-manager-worker) to a known host.
> Otherwise, when the pod respins for some reason, it would lose the data
> already had when spins up in another host node. These limitations have been
> tackled in NFS based mounting [2].
>
> [2] - https://github.com/wso2/kubernetes-apim/releases/tag/v2.1.0-2
>
> Thank you!
>
> On Thu, Sep 28, 2017 at 12:19 PM, Ayeshmantha Perera <
> akayeshman...@gmail.com> wrote:
>
>> Hi all,
>>
>> As mentioned in the kubernetes artifacts deployment documentation [1] we
>> have built the base image and deployed k8 artifacts with the pattern 1.
>> Although artifacts got deployed without an error at deployment time, and
>> the analytics dashboard is accessible via :
>> https://wso2apim-analytics/carbon  the API manager is not working as
>> expected.
>> When going through the logs in wso2-apim-worker and
>> wso2-api-manager-worker pods, we can see below error:
>>
>> [2017-09-28 06:21:53,224] FATAL - ServiceBusInitializer Couldn't
>> initialize the ESB...
>> org.apache.synapse.SynapseException: The synapse.xml location
>> ././repository/deployment/server/synapse-configs/default doesn't exist
>> at org.apache.synapse.SynapseControllerFactory.handleFatal(Syna
>> pseControllerFactory.java:121)
>> at org.apache.synapse.SynapseControllerFactory.validatePath(Syn
>> apseControllerFactory.java:113)
>> at org.apache.synapse.SynapseControllerFactory.validate(Synapse
>> ControllerFactory.java:88)
>> at org.apache.synapse.SynapseControllerFactory.createSynapseCon
>> troller(SynapseControllerFactory.java:44)
>> at org.apache.synapse.ServerManager.init(ServerManager.java:103)
>> at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.
>> initESB(ServiceBusInitializer.java:451)
>> at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.
>> activate(ServiceBusInitializer.java:196)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>> ate(ServiceComponent.java:260)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>> ctivate(ServiceComponentProp.java:146)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>> uild(ServiceComponentProp.java:345)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nt(InstanceProcess.java:620)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nts(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
>> r.java:343)
>>
>> We also ran the apim-kubernetes:2.1.0 docker image in the deployed VM
>> instance, and it starts up without above error, so we think this is
>> something related to the kubernetes artifacts.
>>
>> Appreciate if someone can help us to resolve this deployment issue.
>>
>> Regards,
>> Ayeshmantha
>>
>> [1] https://github.com/wso2/kubernetes-apim/tree/v2.1.0-1
>>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> 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] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-07-03 Thread Dileepa Jayakody

Hi Anuruddha et al,

Thanks. Renaming the mysql file worked, and I was able to build the docker
image.
However I'm getting a JAVA_HOME error when I run the image locally.

docker run wso2am-kubernetes-pattern-1:2.1.0

Initializing wso2am-2.1.0 in default profile on kubernetes platform...
Successfully updated localMemberHost with 172.17.0.2
Creating directory /mnt/172.17.0.2
Creating symlink [Target] /mnt/wso2am-2.1.0, [Link] /mnt/
172.17.0.2/wso2am-2.1.0
/usr/local/bin/init.sh: line 94: /etc/profile.d/set_java_home.sh: No such
file or directory
Starting wso2am-2.1.0 with [Startup Args] , [CARBON_HOME] /mnt/
172.17.0.2/wso2am-2.1.0
Error: JAVA_HOME is not defined correctly.
 CARBON cannot execute /opt/java/bin/java


I have copied the jdk-8u131-linux-x64.tar.gz to
PUPPET_HOME/modules/wso2base/files and also to
PUPPET_HOME/modules/wso2am_runtime/files

The wso2am-2.1.0.zip is copied to PUPPET_HOME/modules/wso2am_runtime/files

The dependency jars, kubernetes membership scheme jar and mysql jar are
copied to :
PUPPET_HOME/modules/wso2am_runtime/files/configs/repository/components/lib

Can you please verify my dependency file-paths above are correct? The paths
are not defined in the github guide [1] step 7.

Please let me know if I have done any configuration mistake.

Thanks,
Dileepa



On Fri, Jun 30, 2017 at 4:38 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Dileepa,
>
> Your mysql connector jar is different than what puppet is trying to copy.
> Rename your mysql jar to mysql-connector-java-5.1.36-bin.jar.
>
> mysql-connector-java-5.1.36.jar != mysql-connector-java-5.1.36-bin.jar
>
>
> On Fri, Jun 30, 2017 at 12:57 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi Pubudu,
>>
>> Thanks. Checking out v1.0.0 from puppet-base resolved above error.
>> However, I'm getting a new error, related to the mysql jar file.
>>
>> Notice: /Stage[main]/Wso2base::Configure/Wso2base::Push_templates[
>> repository/conf/carbon.xml]/File[/mnt/wso2am-2.1.0/
>> repository/conf/carbon.xml]/content: content changed
>> '{md5}5c92af40d406b3368ceafd3b582017bd' to '{md5}326757437935bb13c3d71d8a
>> e692d04b'
>> Error: /Stage[main]/Wso2base::Configure/Wso2base::Push_files[
>> repository/components/lib/mysql-connector-java-5.1.36-
>> bin.jar]/File[/mnt/wso2am-2.1.0/repository/components/lib/
>> mysql-connector-java-5.1.36-bin.jar]: Could not evaluate: Could not
>> retrieve information from environment production source(s)
>> puppet:///modules/wso2am_runtime/configs/repository/componen
>> ts/lib/mysql-connector-java-5.1.36-bin.jar,
>> puppet:///modules/wso2base/configs/repository/components/lib
>> /mysql-connector-java-5.1.36-bin.jar, puppet:///files/configs/reposi
>> tory/components/lib/mysql-connector-java-5.1.36-bin.jar
>>
>> ERROR: Docker image wso2am-traffic-manager-kubernetes-pattern-3:2.1.0
>> creation failed
>>
>>
>> As in the guide step 7, I have copied the following jars to
>> *PUPPET_HOME/modules*
>> jackson-annotations-2.5.4.jar
>> jackson-databind-2.5.4.jar
>> jackson-core-2.5.4.jar
>> kubernetes-membership-scheme-1.0.0.jar
>> mysql-connector-java-5.1.36.jar
>>
>> jdk-8u131-linux-x64.tar.gz
>> wso2am-2.1.0.zip
>>
>> I also tried executing the build as per the older guide by copying the
>> jdk to PUPPET_HOME/modules/wso2base/files and the dependencies,
>> kubernetes-membership-schemes to PUPPET_HOME/modules/wso2am/wso
>> 2am_runtime/files/configs/repository/components/lib
>>
>> Still I'm getting the same error. :(
>>
>> Any idea what I might be doing wrong here?
>>
>> Thanks,
>> Dileepa
>>
>>
>> On Fri, Jun 30, 2017 at 3:10 PM, Pubudu Gunatilaka <pubu...@wso2.com>
>> wrote:
>>
>>> Hi Dileepa,
>>>
>>> Could you please check the tag of the wso2base module? By default, it
>>> refers the master branch and this has to point to v1.0.0 [1]. In your setup
>>> check the git branch in /modules/wso2base. You need to
>>> check out this to [1].
>>>
>>> We are having discussions to remove puppet scripts when creating Docker
>>> images. Hopefully, with K8 release we will remove puppet and allow users to
>>> provide configuration files. All you need is to have a docker image for the
>>> product with relevant configurations to run on K8s.
>>>
>>> [1] - https://github.com/wso2/puppet-base/tree/v1.0.0
>>>
>>> Thank you!
>>>
>>> On Fri, Jun 30, 2017 at 2:39 PM, Dileepa Jayakody <
>>> dileepajayak...@gmail.com> wrote:
>>>
>>>> Hi Pubudu, Isuru,
>>>>

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Dileepa Jayakody

Hi Pubudu,

Thanks. Checking out v1.0.0 from puppet-base resolved above error. However,
I'm getting a new error, related to the mysql jar file.

Notice:
/Stage[main]/Wso2base::Configure/Wso2base::Push_templates[repository/conf/carbon.xml]/File[/mnt/wso2am-2.1.0/repository/conf/carbon.xml]/content:
content changed '{md5}5c92af40d406b3368ceafd3b582017bd' to
'{md5}326757437935bb13c3d71d8ae692d04b'
Error:
/Stage[main]/Wso2base::Configure/Wso2base::Push_files[repository/components/lib/mysql-connector-java-5.1.36-bin.jar]/File[/mnt/wso2am-2.1.0/repository/components/lib/mysql-connector-java-5.1.36-bin.jar]:
Could not evaluate: Could not retrieve information from environment
production source(s)
puppet:///modules/wso2am_runtime/configs/repository/components/lib/mysql-connector-java-5.1.36-bin.jar,
puppet:///modules/wso2base/configs/repository/components/lib/mysql-connector-java-5.1.36-bin.jar,
puppet:///files/configs/repository/components/lib/mysql-connector-java-5.1.36-bin.jar

ERROR: Docker image wso2am-traffic-manager-kubernetes-pattern-3:2.1.0
creation failed


As in the guide step 7, I have copied the following jars to
*PUPPET_HOME/modules*
jackson-annotations-2.5.4.jar
jackson-databind-2.5.4.jar
jackson-core-2.5.4.jar
kubernetes-membership-scheme-1.0.0.jar
mysql-connector-java-5.1.36.jar

jdk-8u131-linux-x64.tar.gz
wso2am-2.1.0.zip

I also tried executing the build as per the older guide by copying the jdk
to PUPPET_HOME/modules/wso2base/files and the dependencies,
kubernetes-membership-schemes to
PUPPET_HOME/modules/wso2am/wso2am_runtime/files/configs/repository/components/lib

Still I'm getting the same error. :(

Any idea what I might be doing wrong here?

Thanks,
Dileepa


On Fri, Jun 30, 2017 at 3:10 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:

> Hi Dileepa,
>
> Could you please check the tag of the wso2base module? By default, it
> refers the master branch and this has to point to v1.0.0 [1]. In your setup
> check the git branch in /modules/wso2base. You need to check
> out this to [1].
>
> We are having discussions to remove puppet scripts when creating Docker
> images. Hopefully, with K8 release we will remove puppet and allow users to
> provide configuration files. All you need is to have a docker image for the
> product with relevant configurations to run on K8s.
>
> [1] - https://github.com/wso2/puppet-base/tree/v1.0.0
>
> Thank you!
>
> On Fri, Jun 30, 2017 at 2:39 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi Pubudu, Isuru,
>>
>> Thanks, yes manifests have been deleted by mistake. Now the
>> PUPPET_HOME/manifests directory has site.pp.
>> But now when I build again I'm getting another error by the puppet agent.
>>
>> log;
>>
>> 172.17.0.2 - - [30/Jun/2017 14:34:07] "GET /modules/wso2am_runtime/templa
>> tes/repository/deployment/server/synapse-configs/
>> default/api/_UserInfoAPI_.xml.erb HTTP/1.1" 200 -
>> Running Puppet agent...
>> Error: Must pass install_java to Class[Wso2base] at
>> /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
>> d01e4f05b24b.mitrai.local
>> Error: Must pass install_java to Class[Wso2base] at
>> /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
>> d01e4f05b24b.mitrai.local
>> The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
>> non-zero code: 1
>>
>> ERROR: Docker image wso2am-gateway-manager-kubernetes-pattern-3:2.1.0
>> creation failed
>> Cleaning...
>>
>> Any idea what might be the issue here?
>>
>> Regards,
>> Dileepa
>>
>> On Fri, Jun 30, 2017 at 2:11 PM, Pubudu Gunatilaka <pubu...@wso2.com>
>> wrote:
>>
>>> Hi Dileepa,
>>>
>>> Based on the log it looks like you are missing the manifest files in
>>> puppet-home. You need to have the following files in the puppet home
>>> location.
>>>
>>> 1. hieradata
>>> 2. hiera.yaml
>>> 3. manifests
>>> 4. modules
>>>
>>> Please make sure you have the above files in your setup.
>>>
>>> Thank you!
>>>
>>> On Fri, Jun 30, 2017 at 1:06 PM, Dileepa Jayakody <
>>> dileepajayak...@gmail.com> wrote:
>>>
>>>> Hi Pubudu,
>>>>
>>>> We followed the latest guide given above, but we are getting an error
>>>> at step 9, building the docker image.
>>>> The log :
>>>>
>>>> 2.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>>>> wso2am_runtime/pattern-7/default.yaml HTTP/1.1" 200 -
>>>> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
>>>> /hieradata/dev/wso2/hieradata/wso2

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Dileepa Jayakody

Hi Pubudu, Isuru,

Thanks, yes manifests have been deleted by mistake. Now the
PUPPET_HOME/manifests directory has site.pp.
But now when I build again I'm getting another error by the puppet agent.

log;

172.17.0.2 - - [30/Jun/2017 14:34:07] "GET
/modules/wso2am_runtime/templates/repository/deployment/server/synapse-configs/default/api/_UserInfoAPI_.xml.erb
HTTP/1.1" 200 -
Running Puppet agent...
Error: Must pass install_java to Class[Wso2base] at
/etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
d01e4f05b24b.mitrai.local
Error: Must pass install_java to Class[Wso2base] at
/etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
d01e4f05b24b.mitrai.local
The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
non-zero code: 1

ERROR: Docker image wso2am-gateway-manager-kubernetes-pattern-3:2.1.0
creation failed
Cleaning...

Any idea what might be the issue here?

Regards,
Dileepa

On Fri, Jun 30, 2017 at 2:11 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:

> Hi Dileepa,
>
> Based on the log it looks like you are missing the manifest files in
> puppet-home. You need to have the following files in the puppet home
> location.
>
> 1. hieradata
> 2. hiera.yaml
> 3. manifests
> 4. modules
>
> Please make sure you have the above files in your setup.
>
> Thank you!
>
> On Fri, Jun 30, 2017 at 1:06 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi Pubudu,
>>
>> We followed the latest guide given above, but we are getting an error at
>> step 9, building the docker image.
>> The log :
>>
>> 2.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>> wso2am_runtime/pattern-7/default.yaml HTTP/1.1" 200 -
>> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>> wso2am_runtime/pattern-7/README.md HTTP/1.1" 200 -
>> 172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /hieradata/dev/wso2/hieradata/
>> wso2is_prepacked/pattern-1/default.yaml HTTP/1.1" 200 -
>> 172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found
>>
>>
>>
>> *172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404
>> -The command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
>> non-zero code: 8Docker image
>> wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build process
>> completed in 0 minutes and 12 seconds
>> Cleaning...
>>
>>
>> Although it says the image is created, when we try to list the images we
>> don't see it.
>> docker images
>> REPOSITORY  TAG
>> IMAGE IDCREATED SIZE
>>   
>> bb1fbd050e8220 minutes ago  232MB
>>   
>> e115a82ab1c930 minutes ago  232MB
>>   
>> 63f7208ec0ca41 minutes ago  232MB
>>   
>> 8d7232ae31d942 minutes ago  232MB
>>   
>> 82d067d96a2443 minutes ago  232MB
>>   
>> 849952ec5cfc44 minutes ago  232MB
>>   
>> f0940512761d45 minutes ago  232MB
>>   
>> ce7f1779b17445 minutes ago  232MB
>>   
>> f9011faab51b    45 minutes ago  232MB
>>   
>> 6b2550bd75b445 minutes ago  232MB
>>   
>> 9331674976a6About an hour ago   232MB
>>
>> I think  it fails to execute the image-config.sh due to some reason.
>> Any idea how to resolve this?
>>
>> Thanks,
>> Dileepa
>>
>> On Wed, Jun 28, 2017 at 11:01 PM, Dileepa Jayakody <
>> dileepajayak...@gmail.com> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Thank you very much for the pointer. We will try out the new kubernetes
>>> artifacts and get back to you with our findings.
>>>
>>> Regards,
>>> Dileepa
>>>
>>> On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka <pubu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Dileepa,
>>>>
>>>> What you have followed is very old and we haven't tested those
>>>> Kubernetes artifacts with APIM 2.1.0. We are currently in the process of
>

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-30 Thread Dileepa Jayakody

Hi Pubudu,

We followed the latest guide given above, but we are getting an error at
step 9, building the docker image.
The log :

2.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2am_runtime/pattern-7/default.yaml
HTTP/1.1" 200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2am_runtime/pattern-7/README.md HTTP/1.1"
200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2is_prepacked/pattern-1/default.yaml
HTTP/1.1" 200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found



*172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404 -The
command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
non-zero code: 8Docker image
wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build process
completed in 0 minutes and 12 seconds
Cleaning...


Although it says the image is created, when we try to list the images we
don't see it.
docker images
REPOSITORY  TAG
IMAGE IDCREATED SIZE
  
bb1fbd050e8220 minutes ago  232MB
  
e115a82ab1c930 minutes ago  232MB
  
63f7208ec0ca41 minutes ago  232MB
  
8d7232ae31d942 minutes ago  232MB
  
82d067d96a2443 minutes ago  232MB
  
849952ec5cfc44 minutes ago  232MB
  
f0940512761d45 minutes ago  232MB
  
ce7f1779b17445 minutes ago  232MB
  
f9011faab51b45 minutes ago  232MB
  
6b2550bd75b445 minutes ago  232MB
  
9331674976a6About an hour ago   232MB

I think  it fails to execute the image-config.sh due to some reason.
Any idea how to resolve this?

Thanks,
Dileepa

On Wed, Jun 28, 2017 at 11:01 PM, Dileepa Jayakody <
dileepajayak...@gmail.com> wrote:

> Hi Pubudu,
>
> Thank you very much for the pointer. We will try out the new kubernetes
> artifacts and get back to you with our findings.
>
> Regards,
> Dileepa
>
> On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> Hi Dileepa,
>>
>> What you have followed is very old and we haven't tested those Kubernetes
>> artifacts with APIM 2.1.0. We are currently in the process of updating
>> Kubernetes artifacts for the APIM 2.1.0. You can find the latest artifacts
>> in [1]. Please follow this and let us know if you find any issues.
>>
>> The reason for the above behavior is that it keeps waiting for the
>> service to be active. Do you see any wso2am pods in the deployment?
>> Kubernetes data model has been changed and it is always better to try the
>> latest artifacts as we have tested some of the patterns with the new
>> deployment model [1].
>>
>> [1] - https://github.com/wso2/kubernetes-apim/tree/2.1.0
>>
>> Thank you!
>>
>> On Tue, Jun 27, 2017 at 7:00 PM, Dileepa Jayakody <
>> dileepajayak...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> We have been following the kubernetes deployment guide for WSO2 products
>>> [1] to deploy APIM 2.1.0 in kubernetes on Google cloud. We have also
>>> followed the blog post [2] as a reference.
>>> When I execute the final deploy command by running
>>> $KUBERNETES_HOME/wso2am/deploy.sh it keeps on idling at message : *Waiting
>>> wso2am to launch on http://104.198.75.29:32003 <http://104.198.75.29:32003>*
>>>
>>> When we try to access above given URL, we get a connection time-out.
>>> Further we have also created firewall rules in GC to open ports :
>>> 9443,9763,8280,8243.
>>> But cannot access any of these endpoints, and can't access the carbon
>>> mgt console.
>>>
>>> Also in the kubernetes service deployed in GC we can't see any external
>>> endpoint exposed.
>>>
>>> Appreciate if someone can please give us any tip to resolve this and get
>>> the deployment working.
>>>
>>> Regards,
>>> Dileepa
>>>
>>>
>>> [1] https://docs.wso2.com/display/KA100/Deploying+and+Undeployin
>>> g+a+WSO2+Product+on+Kubernetes
>>> [2] http://rushmin.blogspot.com/2016/11/deploying-wso2-products-
>>> in-google.html
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-28 Thread Dileepa Jayakody

Hi Pubudu,

Thank you very much for the pointer. We will try out the new kubernetes
artifacts and get back to you with our findings.

Regards,
Dileepa

On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:

> Hi Dileepa,
>
> What you have followed is very old and we haven't tested those Kubernetes
> artifacts with APIM 2.1.0. We are currently in the process of updating
> Kubernetes artifacts for the APIM 2.1.0. You can find the latest artifacts
> in [1]. Please follow this and let us know if you find any issues.
>
> The reason for the above behavior is that it keeps waiting for the service
> to be active. Do you see any wso2am pods in the deployment? Kubernetes data
> model has been changed and it is always better to try the latest artifacts
> as we have tested some of the patterns with the new deployment model [1].
>
> [1] - https://github.com/wso2/kubernetes-apim/tree/2.1.0
>
> Thank you!
>
> On Tue, Jun 27, 2017 at 7:00 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi All,
>>
>> We have been following the kubernetes deployment guide for WSO2 products
>> [1] to deploy APIM 2.1.0 in kubernetes on Google cloud. We have also
>> followed the blog post [2] as a reference.
>> When I execute the final deploy command by running
>> $KUBERNETES_HOME/wso2am/deploy.sh it keeps on idling at message : *Waiting
>> wso2am to launch on http://104.198.75.29:32003 <http://104.198.75.29:32003>*
>>
>> When we try to access above given URL, we get a connection time-out.
>> Further we have also created firewall rules in GC to open ports :
>> 9443,9763,8280,8243.
>> But cannot access any of these endpoints, and can't access the carbon mgt
>> console.
>>
>> Also in the kubernetes service deployed in GC we can't see any external
>> endpoint exposed.
>>
>> Appreciate if someone can please give us any tip to resolve this and get
>> the deployment working.
>>
>> Regards,
>> Dileepa
>>
>>
>> [1] https://docs.wso2.com/display/KA100/Deploying+and+Undeployin
>> g+a+WSO2+Product+on+Kubernetes
>> [2] http://rushmin.blogspot.com/2016/11/deploying-wso2-products-
>> in-google.html
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

2017-06-27 Thread Dileepa Jayakody

Hi All,

We have been following the kubernetes deployment guide for WSO2 products
[1] to deploy APIM 2.1.0 in kubernetes on Google cloud. We have also
followed the blog post [2] as a reference.
When I execute the final deploy command by running
$KUBERNETES_HOME/wso2am/deploy.sh it keeps on idling at message : *Waiting
wso2am to launch on http://104.198.75.29:32003 *

When we try to access above given URL, we get a connection time-out.
Further we have also created firewall rules in GC to open ports :
9443,9763,8280,8243.
But cannot access any of these endpoints, and can't access the carbon mgt
console.

Also in the kubernetes service deployed in GC we can't see any external
endpoint exposed.

Appreciate if someone can please give us any tip to resolve this and get
the deployment working.

Regards,
Dileepa


[1]
https://docs.wso2.com/display/KA100/Deploying+and+Undeploying+a+WSO2+Product+on+Kubernetes
[2]
http://rushmin.blogspot.com/2016/11/deploying-wso2-products-in-google.html
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 4.5.1] Load balance endpoint only sends HTTP response header to the client

2015-02-11 Thread Dileepa Jayakody

2015-02-11T10:31:24.979Z/j.0:created[\n]
[2015-02-11 16:01:25,195] DEBUG - wire  j.0:creator rdf:datatype=
http://www.w3.org/2001/XMLSchema#string
org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine/j.0:creator[\n]
[2015-02-11 16:01:25,196] DEBUG - wire  
 j.0:languagefr/j.0:language[\n]
[2015-02-11 16:01:25,196] DEBUG - wire  j.0:type rdf:resource=
http://purl.org/dc/terms/LinguisticSystem/[\n]
[2015-02-11 16:01:25,196] DEBUG - wire  rdf:type rdf:resource=
http://fise.iks-project.eu/ontology/Enhancement/[\n]
[2015-02-11 16:01:25,196] DEBUG - wire  rdf:type rdf:resource=
http://fise.iks-project.eu/ontology/TextAnnotation/[\n]
[2015-02-11 16:01:25,196] DEBUG - wire/rdf:Description[\n]
[2015-02-11 16:01:25,196] DEBUG - wire  /rdf:RDF[\n]
[2015-02-11 16:01:25,196] DEBUG - wire  [\r][\n]
[2015-02-11 16:01:25,196] DEBUG - wire  0[\r][\n]
[2015-02-11 16:01:25,196] DEBUG - wire  [\r][\n]
[2015-02-11 16:01:25,199]  INFO - LogMediator To:
http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: ,
MessageID: urn:uuid:c43cf639-8ef0-4a87-99df-c9eae1c8a0c5, Direction:
response, Envelope: ?xml version='1.0' encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodyrdf:RDF
xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#; xmlns:j.1=
http://fise.iks-project.eu/ontology/; xmlns:j.0=http://purl.org/dc/terms/

  rdf:Description
rdf:about=urn:enhancement-cdbc9f2a-89b7-0b61-9159-081ae687ccd9
j.1:confidence rdf:datatype=http://www.w3.org/2001/XMLSchema#double
0.14285864925027827/j.1:confidence
j.1:extracted-from
rdf:resource=urn:content-item-sha1-ebfbb96693dc00da6924f8bd0b738819b84829a8/
j.0:created rdf:datatype=http://www.w3.org/2001/XMLSchema#dateTime
2015-02-11T10:31:24.979Z/j.0:created
j.0:creator rdf:datatype=http://www.w3.org/2001/XMLSchema#string
org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine/j.0:creator
j.0:languageen/j.0:language
j.0:type rdf:resource=http://purl.org/dc/terms/LinguisticSystem/
rdf:type rdf:resource=http://fise.iks-project.eu/ontology/Enhancement
/
rdf:type rdf:resource=
http://fise.iks-project.eu/ontology/TextAnnotation/
  /rdf:Description
  rdf:Description
rdf:about=urn:enhancement-ccc10374-74b7-7a7a-0b93-6a94ca0f88b5
j.1:confidence rdf:datatype=http://www.w3.org/2001/XMLSchema#double
0.8571391372006272/j.1:confidence
j.1:extracted-from
rdf:resource=urn:content-item-sha1-ebfbb96693dc00da6924f8bd0b738819b84829a8/
j.0:created rdf:datatype=http://www.w3.org/2001/XMLSchema#dateTime
2015-02-11T10:31:24.979Z/j.0:created
j.0:creator rdf:datatype=http://www.w3.org/2001/XMLSchema#string
org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine/j.0:creator
j.0:languagefr/j.0:language
j.0:type rdf:resource=http://purl.org/dc/terms/LinguisticSystem/
rdf:type rdf:resource=http://fise.iks-project.eu/ontology/Enhancement
/
rdf:type rdf:resource=
http://fise.iks-project.eu/ontology/TextAnnotation/
  /rdf:Description
/rdf:RDF/soapenv:Body/soapenv:Envelope
[2015-02-11 16:01:25,201] DEBUG - wire  HTTP/1.1 200 OK[\r][\n]
[2015-02-11 16:01:25,201] DEBUG - wire  Content-Type: text/plain;
charset=UTF-8[\r][\n]
[2015-02-11 16:01:25,201] DEBUG - wire  Server:
Jetty(7.x.y-SNAPSHOT)[\r][\n]
[2015-02-11 16:01:25,201] DEBUG - wire  Date: Wed, 11 Feb 2015 10:31:25
GMT[\r][\n]
[2015-02-11 16:01:25,201] DEBUG - wire  Transfer-Encoding:
chunked[\r][\n]
[2015-02-11 16:01:25,201] DEBUG - wire  [\r][\n]
[2015-02-11 16:01:25,202] DEBUG - wire  0[\r][\n]
[2015-02-11 16:01:25,202] DEBUG - wire  [\r][\n]


On Wed, Feb 11, 2015 at 2:54 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Dileepa,

 You could observe that Content-Type of response coming from the backend to
 ESB is application/rdf+xml and the response sent from ESB to Client is
 text/plain. So Content-Type is getting changed at the ESB.
 Could you check whether you have selected correct message formatter for 
 application/rdf+xml
 Content-Type in axis2.xml ?



 On Wed, Feb 11, 2015 at 2:43 PM, Dileepa Jayakody 
 dileepajayak...@gmail.com wrote:

 Hi Ruwan,

 Thanks again.
 However I still get only the HTTP status code response header to the
 client as below;
 I noted that the response's Transfer-Encoding is chunked. Could this be
 the cause that my client only gets the header part of the response?


  HTTP/1.1 200 OK
  Content-Type: text/plain; charset=UTF-8
  Server: Jetty(7.x.y-SNAPSHOT)
  Date: Wed, 11 Feb 2015 08:55:32 GMT
  Transfer-Encoding: chunked

 Thanks,
 Dileepa


 On Wed, Feb 11, 2015 at 1:42 PM, Ruwan Abeykoon ruw...@wso2.com wrote:

 Hi Dileepa,
 I am sorry to point you on sample of newer version 4.8.1.

 Can you try something like this , taken and changed based on sample for
 4.5.1 [1]. I Have not tested it though.



 proxy name=MyProxy
transports=https http
startOnLoad=true
 target
 inSequence

Re: [Dev] [ESB 4.5.1] Load balance endpoint only sends HTTP response header to the client

2015-02-11 Thread Dileepa Jayakody

Hi Ruwan,

Thanks again.
However I still get only the HTTP status code response header to the client
as below;
I noted that the response's Transfer-Encoding is chunked. Could this be the
cause that my client only gets the header part of the response?


 HTTP/1.1 200 OK
 Content-Type: text/plain; charset=UTF-8
 Server: Jetty(7.x.y-SNAPSHOT)
 Date: Wed, 11 Feb 2015 08:55:32 GMT
 Transfer-Encoding: chunked

Thanks,
Dileepa


On Wed, Feb 11, 2015 at 1:42 PM, Ruwan Abeykoon ruw...@wso2.com wrote:

 Hi Dileepa,
 I am sorry to point you on sample of newer version 4.8.1.

 Can you try something like this , taken and changed based on sample for
 4.5.1 [1]. I Have not tested it though.



 proxy name=MyProxy
transports=https http
startOnLoad=true
 target
 inSequence
 send
 endpoint
 session type=simpleClientSession/
 loadbalance
 algorithm=org.apache.synapse.endpoints.algorithms.RoundRobin
 endpoint name=s1
 address uri=http://localhost:8080/enhancer
 /
 /endpoint
 endpoint name=s2
 address uri=http://localhost:8082/enhancer
 /
 /endpoint
 /loadbalance
 /endpoint
 /send
 drop/
 /inSequence
 outSequence
 send/
 /outSequence
 /target
 /proxy

 As I understand it, your configuration is missing inSequence and it might
 have caused an undesired behaviour. I would configure both in and out
 sequences when we have to change one.

 [1]
 https://docs.wso2.com/display/ESB451/Sample+752%3A+Load+Balancing+Between+3+Endpoints+With+Endpoint+Templates

 Cheers,
 Ruwan


 On Wed, Feb 11, 2015 at 12:15 PM, Dileepa Jayakody 
 dileepajayak...@gmail.com wrote:

 Hi Ruwan,

 Thanks for the link. I followed the sample but the issue still persists.

 Although the BE response comes to the out sequence only the HTTP 200
 status message is sent to the client.
 Response body is not sent.

 Regards,
 Dileepa

 On Wed, Feb 11, 2015 at 10:23 AM, Ruwan Abeykoon ruw...@wso2.com wrote:

 Hi Deleepa,
 Would you be able to adopt the configuration according to the following
 sample?


 https://docs.wso2.com/display/ESB481/Sample+154%3A+Load+Balancing+with+Proxy+Services

 Have a nice day!
 -Ruwan

 On Tue, Feb 10, 2015 at 11:14 PM, Dileepa Jayakody 
 dileepajayak...@gmail.com wrote:

 Hi All,

 Following is the log for a client request to my proxy service with
 wire-log enabled.
 BE response is logged by the LogMediator in the proxy service's
 out-sequence. But the response to the client doesn't contain the response
 body, only contains the HTTP 200 response header.
 Any tips to tackle the issue is much appreciated.

 Thanks,
 Dileepa

 [1]
 [2015-02-10 23:05:21,381] DEBUG - wire  POST /services/StanbolProxy
 HTTP/1.1[\r][\n]
 [2015-02-10 23:05:21,384] DEBUG - wire  Content-Type:
 text/plain[\r][\n]
 [2015-02-10 23:05:21,384] DEBUG - wire  Accept:
 application/rdf+xml[\r][\n]
 [2015-02-10 23:05:21,384] DEBUG - wire  User-Agent:
 Java/1.7.0_72[\r][\n]
 [2015-02-10 23:05:21,384] DEBUG - wire  Host: 192.168.1.8:8280
 [\r][\n]
 [2015-02-10 23:05:21,385] DEBUG - wire  Connection:
 keep-alive[\r][\n]
 [2015-02-10 23:05:21,385] DEBUG - wire  Content-Length: 35[\r][\n]
 [2015-02-10 23:05:21,385] DEBUG - wire  [\r][\n]
 [2015-02-10 23:05:21,385] DEBUG - wire  Barak Obama is the president
 of USA
 [2015-02-10 23:05:21,875] DEBUG - wire  POST /enhancer
 HTTP/1.1[\r][\n]
 [2015-02-10 23:05:21,876] DEBUG - wire  Content-Type: text/plain;
 charset=UTF-8[\r][\n]
 [2015-02-10 23:05:21,876] DEBUG - wire  Accept:
 application/rdf+xml[\r][\n]
 [2015-02-10 23:05:21,877] DEBUG - wire  Transfer-Encoding:
 chunked[\r][\n]
 [2015-02-10 23:05:21,877] DEBUG - wire  Host: localhost:8082[\r][\n]
 [2015-02-10 23:05:21,877] DEBUG - wire  Connection:
 Keep-Alive[\r][\n]
 [2015-02-10 23:05:21,878] DEBUG - wire  User-Agent:
 Synapse-HttpComponents-NIO[\r][\n]
 [2015-02-10 23:05:21,878] DEBUG - wire  [\r][\n]
 [2015-02-10 23:05:21,879] DEBUG - wire  23[\r][\n]
 [2015-02-10 23:05:21,880] DEBUG - wire  Barak Obama is the president
 of USA[\r][\n]
 [2015-02-10 23:05:21,880] DEBUG - wire  0[\r][\n]
 [2015-02-10 23:05:21,881] DEBUG - wire  [\r][\n]
 [2015-02-10 23:05:26,211] DEBUG - wire  HTTP/1.1 200 OK[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  Date: Tue, 10 Feb 2015
 17:35:21 GMT[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  Content-Type:
 application/rdf+xml[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  Transfer-Encoding:
 chunked[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  Server:
 Jetty(7.x.y-SNAPSHOT)[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  [\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  1093[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  rdf:RDF[\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  xmlns:rdf=
 http

Re: [Dev] [ESB 4.5.1] Load balance endpoint only sends HTTP response header to the client

2015-02-11 Thread Dileepa Jayakody

Hi Isuru,

Thanks a lot!
Adding the messageType property did the trick.
I will use 4.8.1 :)

Regards,
Dileepa

On Wed, Feb 11, 2015 at 4:15 PM, Isuru Udana isu...@wso2.com wrote:

 Can you try with setting the messageType property to application/rdf+xml
 in outSequence.

 property name=messageType value=application/rdf+xml scope=axis2/

 And also 4.5.1 is a very old version of ESB, If there is no strong reason
 for you to keep using it, try to use latest 4.8.1 version.

 Thanks.

 On Wed, Feb 11, 2015 at 4:09 PM, Dileepa Jayakody 
 dileepajayak...@gmail.com wrote:

 Hi Isuru,

 Thanks a lot for that pointer :)
 As you pointed out it seems the issue is related Accept content type of
 my request (application/rdf+xml).

 I tried adding messageFormatter contentType=application/rdf+xml
 class=org.wso2.carbon.relay.ExpandingMessageFormatter/ to the axis2.xml
 but still ESB serializes the BE response as a text/plain which results in
 just sending the HTTP 200 response header to the client.

 I also tried enabling  messageBuilder contentType=application/rdf+xml
 class=org.wso2.carbon.relay.BinaryRelayBuilder/ but still the in the
 out-sequence ESB tries to serialize the response as text/plain.


 Following is a full log of a sample request : curl -v -X POST -H Accept:
 application/rdf+xml -H Content-type: text/plain --data sample request
 to detect cities like Paris in content.
 http://localhost:8280/services/StanbolProxy

 [2015-02-11 16:01:24,844] DEBUG - wire  POST /services/StanbolProxy
 HTTP/1.1[\r][\n]
 [2015-02-11 16:01:24,846] DEBUG - wire  User-Agent: curl/7.22.0
 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4
 libidn/1.23 librtmp/2.3[\r][\n]
 [2015-02-11 16:01:24,846] DEBUG - wire  Host: localhost:8280[\r][\n]
 [2015-02-11 16:01:24,846] DEBUG - wire  Accept:
 application/rdf+xml[\r][\n]
 [2015-02-11 16:01:24,846] DEBUG - wire  Content-type:
 text/plain[\r][\n]
 [2015-02-11 16:01:24,846] DEBUG - wire  Content-Length: 54[\r][\n]
 [2015-02-11 16:01:24,846] DEBUG - wire  [\r][\n]
 [2015-02-11 16:01:24,846] DEBUG - wire  sample request to detect
 cities like Paris in content.
 [2015-02-11 16:01:24,854] DEBUG - wire  POST /enhancer
 HTTP/1.1[\r][\n]
 [2015-02-11 16:01:24,854] DEBUG - wire  Content-Type: text/plain;
 charset=UTF-8[\r][\n]
 [2015-02-11 16:01:24,855] DEBUG - wire  Accept:
 application/rdf+xml[\r][\n]
 [2015-02-11 16:01:24,855] DEBUG - wire  Transfer-Encoding:
 chunked[\r][\n]
 [2015-02-11 16:01:24,855] DEBUG - wire  Host: localhost:8081[\r][\n]
 [2015-02-11 16:01:24,855] DEBUG - wire  Connection: Keep-Alive[\r][\n]
 [2015-02-11 16:01:24,856] DEBUG - wire  User-Agent:
 Synapse-HttpComponents-NIO[\r][\n]
 [2015-02-11 16:01:24,856] DEBUG - wire  [\r][\n]
 [2015-02-11 16:01:24,857] DEBUG - wire  36[\r][\n]
 [2015-02-11 16:01:24,857] DEBUG - wire  sample request to detect
 cities like Paris in content.[\r][\n]
 [2015-02-11 16:01:24,858] DEBUG - wire  0[\r][\n]
 [2015-02-11 16:01:24,858] DEBUG - wire  [\r][\n]
 [2015-02-11 16:01:25,192] DEBUG - wire  HTTP/1.1 200 OK[\r][\n]
 [2015-02-11 16:01:25,193] DEBUG - wire  Date: Wed, 11 Feb 2015
 10:31:24 GMT[\r][\n]
 [2015-02-11 16:01:25,193] DEBUG - wire  Content-Type:
 application/rdf+xml[\r][\n]
 [2015-02-11 16:01:25,193] DEBUG - wire  Transfer-Encoding:
 chunked[\r][\n]
 [2015-02-11 16:01:25,193] DEBUG - wire  Server:
 Jetty(7.x.y-SNAPSHOT)[\r][\n]
 [2015-02-11 16:01:25,193] DEBUG - wire  [\r][\n]
 [2015-02-11 16:01:25,193] DEBUG - wire  783[\r][\n]
 [2015-02-11 16:01:25,193] DEBUG - wire  rdf:RDF[\n]
 [2015-02-11 16:01:25,194] DEBUG - wire  xmlns:rdf=
 http://www.w3.org/1999/02/22-rdf-syntax-ns#[\n];
 [2015-02-11 16:01:25,194] DEBUG - wire  xmlns:j.0=
 http://purl.org/dc/terms/[\n];
 [2015-02-11 16:01:25,194] DEBUG - wire  xmlns:j.1=
 http://fise.iks-project.eu/ontology/;  [\n]
 [2015-02-11 16:01:25,194] DEBUG - wirerdf:Description
 rdf:about=urn:enhancement-cdbc9f2a-89b7-0b61-9159-081ae687ccd9[\n]
 [2015-02-11 16:01:25,194] DEBUG - wire  j.1:confidence
 rdf:datatype=http://www.w3.org/2001/XMLSchema#double
 0.14285864925027827/j.1:confidence[\n]
 [2015-02-11 16:01:25,194] DEBUG - wire  j.1:extracted-from
 rdf:resource=urn:content-item-sha1-ebfbb96693dc00da6924f8bd0b738819b84829a8/[\n]
 [2015-02-11 16:01:25,194] DEBUG - wire  j.0:created rdf:datatype=
 http://www.w3.org/2001/XMLSchema#dateTime
 2015-02-11T10:31:24.979Z/j.0:created[\n]
 [2015-02-11 16:01:25,194] DEBUG - wire  j.0:creator rdf:datatype=
 http://www.w3.org/2001/XMLSchema#string
 org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine/j.0:creator[\n]
 [2015-02-11 16:01:25,194] DEBUG - wire  
  j.0:languageen/j.0:language[\n]
 [2015-02-11 16:01:25,195] DEBUG - wire  j.0:type rdf:resource=
 http://purl.org/dc/terms/LinguisticSystem/[\n]
 [2015-02-11 16:01:25,195] DEBUG - wire  rdf:type rdf:resource=
 http://fise.iks-project.eu/ontology/Enhancement/[\n]
 [2015-02-11 16:01:25,195] DEBUG - wire  rdf:type

[Dev] [ESB 4.5.1] Load balance endpoint only sends HTTP response header to the client

2015-02-10 Thread Dileepa Jayakody

Hi All,

I'm using WSO2 4.5.1 ESB in my project to balance load to my BE server
nodes.
I created a pass through proxy service calling a Load Balance Endpoint to
handle the request load by 2 BE nodes in a round-robin manner.

When I call the proxy service, although the expected BE response comes to
the out-sequence of my proxy service, only the HTTP response header is sent
back to the client.
LogMediator logs the full response from the BE, so the expected response
comes to the ESB, but the client only receives the HTTP response header
from the proxy-service.
When I enable wire log I can see that only the response header is sent to
the client as below;

[2015-02-10 18:29:36,101] DEBUG - wire  HTTP/1.1 200 OK[\r][\n]
[2015-02-10 18:29:36,101] DEBUG - wire  Content-Type: text/plain;
charset=UTF-8[\r][\n]
[2015-02-10 18:29:36,102] DEBUG - wire  Server:
Jetty(7.x.y-SNAPSHOT)[\r][\n]
[2015-02-10 18:29:36,102] DEBUG - wire  Date: Tue, 10 Feb 2015 12:59:36
GMT[\r][\n]
[2015-02-10 18:29:36,102] DEBUG - wire  Transfer-Encoding:
chunked[\r][\n]
[2015-02-10 18:29:36,102] DEBUG - wire  [\r][\n]
[2015-02-10 18:29:36,103] DEBUG - wire  0[\r][\n]
[2015-02-10 18:29:36,103] DEBUG - wire  [\r][\n]


Following is my proxy service configuration;

 proxy name=MyProxy
  transports=local https http
  startOnLoad=true
  trace=disable
  target endpoint=lbendpoint
 outSequence
log level=full/
send/
 /outSequence
  /target
   /proxy

   endpoint name=lbendpoint
  loadbalance
algorithm=org.apache.synapse.endpoints.algorithms.RoundRobin
 endpoint name=s1
address uri=http://localhost:8080/enhancer/
 /endpoint
 endpoint name=s2
address uri=http://localhost:8082/enhancer/
 /endpoint
  /loadbalance
   /endpoint

Can anyone help me figure out what might be going wrong here?

Thanks,
Dileepa

[1] https://docs.wso2.com/display/ESB490/Load-balance+Endpoint
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 4.5.1] Load balance endpoint only sends HTTP response header to the client

2015-02-10 Thread Dileepa Jayakody

#string
org.apache.stanbol.enhancer.engines.opennlp.impl.NamedEntityExtractionEnhancementEngine/j.0:creator
j.0:type rdf:resource=http://dbpedia.org/ontology/Place/
rdf:type rdf:resource=http://fise.iks-project.eu/ontology/Enhancement
/
rdf:type rdf:resource=
http://fise.iks-project.eu/ontology/TextAnnotation/
  /rdf:Description
  rdf:Description
rdf:about=urn:enhancement-58277280-ed99-10b3-8c5b-81a62ca44824
j.1:confidence rdf:datatype=http://www.w3.org/2001/XMLSchema#double
0.857140049021033/j.1:confidence
j.1:extracted-from
rdf:resource=urn:content-item-sha1-6f8a2fe9f9b83c97853ef463df229f4664f52798/
j.0:created rdf:datatype=http://www.w3.org/2001/XMLSchema#dateTime
2015-02-10T17:35:22.360Z/j.0:created
j.0:creator rdf:datatype=http://www.w3.org/2001/XMLSchema#string
org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine/j.0:creator
j.0:languageen/j.0:language
j.0:type rdf:resource=http://purl.org/dc/terms/LinguisticSystem/
rdf:type rdf:resource=http://fise.iks-project.eu/ontology/Enhancement
/
rdf:type rdf:resource=
http://fise.iks-project.eu/ontology/TextAnnotation/
  /rdf:Description
  rdf:Description
rdf:about=urn:enhancement-1696e861-d643-539f-a3a4-75865c2711e0
j.1:confidence rdf:datatype=http://www.w3.org/2001/XMLSchema#double
0.40536309634989937/j.1:confidence
j.1:end rdf:datatype=http://www.w3.org/2001/XMLSchema#int
11/j.1:end
j.1:extracted-from
rdf:resource=urn:content-item-sha1-6f8a2fe9f9b83c97853ef463df229f4664f52798/
j.1:selected-text xml:lang=enBarak Obama/j.1:selected-text
j.1:selection-context xml:lang=enBarak Obama is the president of
USA/j.1:selection-context
j.1:start rdf:datatype=http://www.w3.org/2001/XMLSchema#int
0/j.1:start
j.0:created rdf:datatype=http://www.w3.org/2001/XMLSchema#dateTime
2015-02-10T17:35:24.444Z/j.0:created
j.0:creator rdf:datatype=http://www.w3.org/2001/XMLSchema#string
org.apache.stanbol.enhancer.engines.opennlp.impl.NamedEntityExtractionEnhancementEngine/j.0:creator
j.0:type rdf:resource=http://dbpedia.org/ontology/Person/
rdf:type rdf:resource=http://fise.iks-project.eu/ontology/Enhancement
/
rdf:type rdf:resource=
http://fise.iks-project.eu/ontology/TextAnnotation/
  /rdf:Description
  rdf:Description
rdf:about=urn:enhancement-454a72b2-f8d0-0eb5-ff5b-5eae0b442d92
j.1:confidence rdf:datatype=http://www.w3.org/2001/XMLSchema#double
0.14285759171764037/j.1:confidence
j.1:extracted-from
rdf:resource=urn:content-item-sha1-6f8a2fe9f9b83c97853ef463df229f4664f52798/
j.0:created rdf:datatype=http://www.w3.org/2001/XMLSchema#dateTime
2015-02-10T17:35:22.360Z/j.0:created
j.0:creator rdf:datatype=http://www.w3.org/2001/XMLSchema#string
org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine/j.0:creator
j.0:languageid/j.0:language
j.0:type rdf:resource=http://purl.org/dc/terms/LinguisticSystem/
rdf:type rdf:resource=http://fise.iks-project.eu/ontology/Enhancement
/
rdf:type rdf:resource=
http://fise.iks-project.eu/ontology/TextAnnotation/
  /rdf:Description
/rdf:RDF/soapenv:Body/soapenv:Envelope
[2015-02-10 23:05:26,276] DEBUG - wire  HTTP/1.1 200 OK[\r][\n]
[2015-02-10 23:05:26,276] DEBUG - wire  Content-Type: text/plain;
charset=UTF-8[\r][\n]
[2015-02-10 23:05:26,276] DEBUG - wire  Server:
Jetty(7.x.y-SNAPSHOT)[\r][\n]
[2015-02-10 23:05:26,277] DEBUG - wire  Date: Tue, 10 Feb 2015 17:35:26
GMT[\r][\n]
[2015-02-10 23:05:26,277] DEBUG - wire  Transfer-Encoding:
chunked[\r][\n]
[2015-02-10 23:05:26,277] DEBUG - wire  Connection: keep-alive[\r][\n]
[2015-02-10 23:05:26,277] DEBUG - wire  [\r][\n]
[2015-02-10 23:05:26,277] DEBUG - wire  0[\r][\n]
[2015-02-10 23:05:26,277] DEBUG - wire  [\r][\n]


On Tue, Feb 10, 2015 at 8:33 PM, Dileepa Jayakody dileepajayak...@gmail.com
 wrote:

 Hi All,

 I'm using WSO2 4.5.1 ESB in my project to balance load to my BE server
 nodes.
 I created a pass through proxy service calling a Load Balance Endpoint to
 handle the request load by 2 BE nodes in a round-robin manner.

 When I call the proxy service, although the expected BE response comes to
 the out-sequence of my proxy service, only the HTTP response header is sent
 back to the client.
 LogMediator logs the full response from the BE, so the expected response
 comes to the ESB, but the client only receives the HTTP response header
 from the proxy-service.
 When I enable wire log I can see that only the response header is sent to
 the client as below;

 [2015-02-10 18:29:36,101] DEBUG - wire  HTTP/1.1 200 OK[\r][\n]
 [2015-02-10 18:29:36,101] DEBUG - wire  Content-Type: text/plain;
 charset=UTF-8[\r][\n]
 [2015-02-10 18:29:36,102] DEBUG - wire  Server:
 Jetty(7.x.y-SNAPSHOT)[\r][\n]
 [2015-02-10 18:29:36,102] DEBUG - wire  Date: Tue, 10 Feb 2015 12:59:36
 GMT[\r][\n]
 [2015-02-10 18:29:36,102] DEBUG - wire  Transfer-Encoding:
 chunked[\r][\n]
 [2015-02-10 18:29:36,102] DEBUG - wire  [\r][\n]
 [2015-02-10 18:29:36,103] DEBUG

Re: [Dev] [ESB 4.5.1] Load balance endpoint only sends HTTP response header to the client

2015-02-10 Thread Dileepa Jayakody

Hi Ruwan,

Thanks for the link. I followed the sample but the issue still persists.

Although the BE response comes to the out sequence only the HTTP 200 status
message is sent to the client.
Response body is not sent.

Regards,
Dileepa

On Wed, Feb 11, 2015 at 10:23 AM, Ruwan Abeykoon ruw...@wso2.com wrote:

 Hi Deleepa,
 Would you be able to adopt the configuration according to the following
 sample?


 https://docs.wso2.com/display/ESB481/Sample+154%3A+Load+Balancing+with+Proxy+Services

 Have a nice day!
 -Ruwan

 On Tue, Feb 10, 2015 at 11:14 PM, Dileepa Jayakody 
 dileepajayak...@gmail.com wrote:

 Hi All,

 Following is the log for a client request to my proxy service with
 wire-log enabled.
 BE response is logged by the LogMediator in the proxy service's
 out-sequence. But the response to the client doesn't contain the response
 body, only contains the HTTP 200 response header.
 Any tips to tackle the issue is much appreciated.

 Thanks,
 Dileepa

 [1]
 [2015-02-10 23:05:21,381] DEBUG - wire  POST /services/StanbolProxy
 HTTP/1.1[\r][\n]
 [2015-02-10 23:05:21,384] DEBUG - wire  Content-Type:
 text/plain[\r][\n]
 [2015-02-10 23:05:21,384] DEBUG - wire  Accept:
 application/rdf+xml[\r][\n]
 [2015-02-10 23:05:21,384] DEBUG - wire  User-Agent:
 Java/1.7.0_72[\r][\n]
 [2015-02-10 23:05:21,384] DEBUG - wire  Host: 192.168.1.8:8280
 [\r][\n]
 [2015-02-10 23:05:21,385] DEBUG - wire  Connection: keep-alive[\r][\n]
 [2015-02-10 23:05:21,385] DEBUG - wire  Content-Length: 35[\r][\n]
 [2015-02-10 23:05:21,385] DEBUG - wire  [\r][\n]
 [2015-02-10 23:05:21,385] DEBUG - wire  Barak Obama is the president
 of USA
 [2015-02-10 23:05:21,875] DEBUG - wire  POST /enhancer
 HTTP/1.1[\r][\n]
 [2015-02-10 23:05:21,876] DEBUG - wire  Content-Type: text/plain;
 charset=UTF-8[\r][\n]
 [2015-02-10 23:05:21,876] DEBUG - wire  Accept:
 application/rdf+xml[\r][\n]
 [2015-02-10 23:05:21,877] DEBUG - wire  Transfer-Encoding:
 chunked[\r][\n]
 [2015-02-10 23:05:21,877] DEBUG - wire  Host: localhost:8082[\r][\n]
 [2015-02-10 23:05:21,877] DEBUG - wire  Connection: Keep-Alive[\r][\n]
 [2015-02-10 23:05:21,878] DEBUG - wire  User-Agent:
 Synapse-HttpComponents-NIO[\r][\n]
 [2015-02-10 23:05:21,878] DEBUG - wire  [\r][\n]
 [2015-02-10 23:05:21,879] DEBUG - wire  23[\r][\n]
 [2015-02-10 23:05:21,880] DEBUG - wire  Barak Obama is the president
 of USA[\r][\n]
 [2015-02-10 23:05:21,880] DEBUG - wire  0[\r][\n]
 [2015-02-10 23:05:21,881] DEBUG - wire  [\r][\n]
 [2015-02-10 23:05:26,211] DEBUG - wire  HTTP/1.1 200 OK[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  Date: Tue, 10 Feb 2015
 17:35:21 GMT[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  Content-Type:
 application/rdf+xml[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  Transfer-Encoding:
 chunked[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  Server:
 Jetty(7.x.y-SNAPSHOT)[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  [\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  1093[\r][\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  rdf:RDF[\n]
 [2015-02-10 23:05:26,212] DEBUG - wire  xmlns:rdf=
 http://www.w3.org/1999/02/22-rdf-syntax-ns#[\n];
 [2015-02-10 23:05:26,212] DEBUG - wire  xmlns:j.0=
 http://purl.org/dc/terms/[\n];
 [2015-02-10 23:05:26,212] DEBUG - wire  xmlns:j.1=
 http://fise.iks-project.eu/ontology/;  [\n]
 [2015-02-10 23:05:26,212] DEBUG - wirerdf:Description
 rdf:about=urn:enhancement-f50e270f-6c52-78a1-96e0-a9a150f42dce[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.1:confidence
 rdf:datatype=http://www.w3.org/2001/XMLSchema#double
 0.7127498890292797/j.1:confidence[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.1:end rdf:datatype=
 http://www.w3.org/2001/XMLSchema#int;35/j.1:end[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.1:extracted-from
 rdf:resource=urn:content-item-sha1-6f8a2fe9f9b83c97853ef463df229f4664f52798/[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.1:selected-text
 xml:lang=enUSA/j.1:selected-text[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.1:selection-context
 xml:lang=enBarak Obama is the president of
 USA/j.1:selection-context[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.1:start rdf:datatype=
 http://www.w3.org/2001/XMLSchema#int;32/j.1:start[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.0:created rdf:datatype=
 http://www.w3.org/2001/XMLSchema#dateTime
 2015-02-10T17:35:25.820Z/j.0:created[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.0:creator rdf:datatype=
 http://www.w3.org/2001/XMLSchema#string
 org.apache.stanbol.enhancer.engines.opennlp.impl.NamedEntityExtractionEnhancementEngine/j.0:creator[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  j.0:type rdf:resource=
 http://dbpedia.org/ontology/Place/[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  rdf:type rdf:resource=
 http://fise.iks-project.eu/ontology/Enhancement/[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire  rdf:type rdf:resource=
 http://fise.iks-project.eu/ontology/TextAnnotation/[\n]
 [2015-02-10 23:05:26,213] DEBUG - wire

Re: [Dev] Do we really need a separate carbon orbit?

2013-05-22 Thread Dileepa Jayakody

Hi All,

The logic we used to have separate orbits is like below.

carbon project
|--orbit (top level orbit) : bundled 3rd party libraries with no
modifications to the source (eg: rabbitmq)
|
|--kernel/dependencies : forked non-osgi libraries used in kernel with
source code modifications (eg: axis2, axiom)
||--orbit : bundled versions of above forked libraries used
in kernel
|
|--platform/dependencies : forked non-osgi libraries used in platform with
source code modifications (eg: hadoop)
 |--orbit : bundled versions of above forked libraries used
in platform

Thanks,
Dileepa


On Wed, May 22, 2013 at 11:02 AM, Nuwan Bandara nu...@wso2.com wrote:




 On Wed, May 22, 2013 at 10:32 AM, Senaka Fernando sen...@wso2.com wrote:

 Hi Nuwan,

 That's what's desired, but it is not what you find in practice, :). Take
 a look @ platform/dependencies and then platform/dependencies/orbit. So,
 you find things that are not inside platform/dependencies to be referenced
 inside platform/dependencies/orbit. Such things are directly taken from
 outside too.


 Thats absolutely wrong. we should either fix that or remove top level
 orbit. I am +1 for top level orbit and -0 for removing the concept all
 to gather.

 Regards,
 /Nuwan



 Thanks,
 Senaka.


 On Wed, May 22, 2013 at 10:14 AM, Nuwan Bandara nu...@wso2.com wrote:

 Hi,

 Well, platform/orbit and kernal/orbit has its meaning right. if we put
 some non osgi components to kernal/dependencies we wrap it at kernal/orbit.
 but top level orbit is the stuff we directly take from outside. So IMO
 there is a meaning in having top level /orbit. its not confusing, its
 rather clean. but ofcause you can have kernal/orbit with everything needed
 for kernel.

 Regards,
 /Nuwan


 On Wed, May 22, 2013 at 9:45 AM, Senaka Fernando sen...@wso2.comwrote:

 Hi Miyuru,

 IMHO, I see no point in having a separate orbit, so I too am +1 for
 this. A separate orbit has always been a confusion, since you also find
 orbit inside kernel/dependencies and platform/dependencies, making it
 highly confusing for anyone who tries to understand (or explain) our SVN
 structure.

 Thanks,
 Senaka.


 On Wed, May 22, 2013 at 9:24 AM, Miyuru Wanninayaka miy...@wso2.comwrote:

 Hi all,

 What is the point of having a separate orbit? [1]

 We either release kernel or platform and we don't release orbit. So
 any orbit bundle which required for kernel can live inside
 kernel/dependencies/orbit and platform required orbits can live inside
 /platform/dependencies/orbit

 [1] https://svn.wso2.org/repos/wso2/carbon/orbit/

 --
 Miyuru Wanninayaka
 Technical Lead
 Member, Management Committee - Integration Technologies
 WSO2 Inc. : http://wso2.com

 Mobile : +94 77 209 9788
 Blog : http://miyurudw.blogspot.com
 Flickr : http://www.flickr.com/photos/miyuru_daminda
 ___
 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




 --
 *Thanks  Regards,

 Nuwan Bandara
 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/




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




 --
 *Thanks  Regards,

 Nuwan Bandara
 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/

 ___
 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] Kernel trunk - p2 profile build error

2013-04-15 Thread Dileepa Jayakody

Hi Kishanthan,

Can you start the server with the osgi console and check the relevant
carbon bundles are in ACTIVE state?
Maybe some of the bundles are not added to the distribution during the
build OR not in active state at run time.
AFAIK The distribution structure changes with the plugins/bundles
in relevant profile directories in the new multi-profile distribution
during the build phase.

Thanks,
Dileepa

On Tue, Apr 16, 2013 at 10:38 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

Hi Reka,

I cannot start carbon server in current trunk (4.2.0-SNAPSHOT) with a
clean repo build. It hangs for a long time. Are you missing any more
commits related to multi-profile support to kernel?

Kishanthan.

On Tue, Apr 2, 2013 at 6:55 PM, Reka Thirunavukkarasu r...@wso2.comwrote:

I have fixed it in r169864.

Thanks,
Reka

On Tue, Apr 2, 2013 at 6:45 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

Hi Reka,

Build failed at kernel/trunk/distribution/product/modules/p2-profile-gen.

Looks like it may be due to the changes on multiple profile in kernel
distribution. Can you please have a look?

Installing org.wso2.carbon.styles.feature.group 4.1.0.SNAPSHOT.
Installation failed.
An error occurred while installing the items
session context was:(profile=WSO2CarbonProfile,
phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null
-- [R]org.wso2.carbon.styles 4.1.0.SNAPSHOT,
action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
Error while loading manipulator.
Caused by: Application failed, log file location:
/home/kicha/mvnRepo/m3repo/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1364903487880.log

*Error trace form the log file*

!ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2013-04-02
17:21:30.952
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: The framework persistent data location
(/home/kicha/checkouts/wso2/carbon/kernel/trunk/distribution/kernel/target/WSO2Carbon/WSO2CarbonProfile/configuration)
is not the same as the framework configuration location
(/home/kicha/checkouts/wso2/carbon/kernel/trunk/distribution/product/modules/p2-profile-gen/target/wso2carbon-core-4.1.0-SNAPSHOT/repository/components/WSO2CarbonProfile/configuration).
at
org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65)
at
org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:348)

Thanks,
Kishanthan.
--
*Kishanthan Thangarajah*
Software Engineer,
Development Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*

--
Reka Thirunavukkarasu
Software Engineer,
WSO2, Inc.:http://wso2.com,

--
*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] Multiple profile support in Carbon

2013-03-04 Thread Dileepa Jayakody

Hi All,

Please see this blog-post :
http://dileepajayakody.blogspot.com/2013/03/multiple-p2-profile-support-in-carbon.html
to
get details on the POC done to support multiple-profiles.

The things to do;
1.Fix the problem of feature installations with copying resources to the
target. (the problem is with relative paths of the copying resources in the
new multi-profile target)
2. Maintain the running Profile when restarting the server.
3. (Improvement) Adding a new goal to merge materialize-product and
p2-profile-gen goals so that it can be done in 1 execution cycle.

Thanks,
Dileepa

On Wed, Feb 20, 2013 at 1:26 AM, Dileepa Jayakody dile...@wso2.com wrote:

On Tue, Feb 19, 2013 at 8:20 AM, Dileepa Jayakody dile...@wso2.comwrote:

Hi All,

I continued with the 1st option of updating the relative paths for
source,destination in p2.inf of platform features in the new multi-profile
target directory structure.
Based on that I have done below changes to kernel in the scratch area;

1. carbon-p2-plugin [1]
Updated the p2-director launcher arguments to support multiple-profile
installations with a shared p2 area, in MaterialzeProductMojo and
ProfileGenMojo
-destination : targetPath/${profile}
-shared : targetPath/p2

targetPath is: $CARBON_HOME/repository/components

2. carbon.server [2]
CarbonLauncher changes: At startup osgi-runtime arguments are passed
according on the running profile
osgi.install.area : repository/components/${profile}
osgi.configuration.area : repository/components/${profile}/configuration
eclipse.p2.data.area : repository/components/p2 (not changed as we are
using a shared p2 area for all profiles)

Main class change : if no profile is given as a startup parameter, carbon
will start with the default profile : WSO2CarbonProfile

3. Product p2-profile-gen [3]
Please see how a new Profile can be installed into the distribution in a
product's p2-profile-gen.
I have changed the carbon product p2-profile-gen [3] module, to install a
new Profile : WSO2SampleProfile that has tryit, soaptracer features
installed in addition to the carbon.runtime and carbon.core features.

Below steps should be performed to install a new Profile in
p2-profile-gen;
1. Publish the product configuration file (eg:carbon.product) with the
initial runtime configurations.
(A product configuration is required to materialize the minimal runtime
before installing features)
2. Materialize the new Profile using above .product configuration file
3. Install features to the new profile

Please find the carbon distribution at [4] which has WSO2CarbonProfile,
WSO2SampleProfile pre-installed.
You can start Carbon to load a profile by giving profile argument at
startup (eg: ./wso2server.sh -Dprofile=WSO2SampleProfile)

Feature installation in the multi-profile environment is not yet working
as it only updates the relevant Profile but not the relevant
bundles.infofile.
The reason for this is that org.eclipse.equinox.p2.installFolder value
gets hard-coded in the Profile during build time and p2 cannot locate the
bundles.info file in the modified directory structure. Need to fix this.

Above issue was fixed by passing -roaming argument to the p2-director in
the carbon-p2-plugin.
With -roaming enabled, org.eclipse.equinox.p2.installFolder value is
modified by the profile registry when the profile is loaded from disk.
Now when we install new features to a Profile they are maintained
separately under the repository/components/${Profile} directory.

Now the problem is with relative paths defined in features p2.inf files
(eg: org.eclipse.equinox.p2.touchpoint.natives.copy(source:*
${installFolder}*
/features/org.wso2.carbon.cassandra.dataaccess_${feature.version}/conf/cassandra-component.xml,target:
*${installFolder*}/../conf/etc/cassandra-component.xml,overwrite:true);).

In the new multi-profile target, the installFolder will point the
components/{Profile} directory and source and destination directory paths
given above will be invalid. Need to find a solution on how we can install
features both during build-time and runtime by correctly giving the
source,destination directory path to P2.

Thanks,
Dileepa

The related jira : https://wso2.org/jira/browse/CARBON-14064

Thanks,
Dileepa

[1] https://svn.wso2.org/repos/wso2/scratch/dileepa/carbon-p2-plugin
[2]
https://svn.wso2.org/repos/wso2/scratch/dileepa/kernel/trunk/core/org.wso2.carbon.server
[3]
https://svn.wso2.org/repos/wso2/scratch/dileepa/kernel/trunk/distribution/product/modules/p2-profile-gen/pom.xml
[4]
https://svn.wso2.org/repos/wso2/scratch/dileepa/wso2carbon-4.1.0-SNAPSHOT.zip

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

Re: [Dev] Build failed in trunk with clean repo

2013-03-03 Thread Dileepa Jayakody

On Sun, Mar 3, 2013 at 11:00 AM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi Dileepa,


 Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0
 branch, and we haven't released it yet. So for the moment we'll have to
 build (only) orbit 4.1.0 branch before building trunk.


 Normally we branch from trunk. What I have felt here is on the other way
 around. When creating the 4.1.0 branch the code what you mentioned missing
 should be there in the orbit trunk. Isn't it what should be?


Yes, I think the reason is orbit 4.1.0 branch has being created separately
without merging from orbit trunk, hence the new tomcat orbit version is not
there in trunk. Perhaps we should
merge the 4.1.0 orbits to trunk.

@Kishanthan,
was there any specific reason to add the new tomcat bundles to 4.1.0 branch
and not trunk?maybe we can commit them to trunk to avoid build failures?

Thanks,
Dileepa


 thanks
 Eranda

 *
 *




-- 
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] Build failed in trunk with clean repo

2013-03-02 Thread Dileepa Jayakody

Hi Lahiru,

Please build the orbit 4.1.0 branch first :
https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.1.0
tomcat bundle is there.

Thanks,
Dileepa

On Sat, Mar 2, 2013 at 10:06 PM, Lahiru Sandaruwan lahi...@wso2.com wrote:

 Hi,

 $subject,

 Error,

 [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.1.0-SNAPSHOT: Could not
 find artifact org.apache.tomcat.wso2:tomcat:jar:7.0.34.wso2v1 in
 carbon-plugin-repo (
 http://maven.wso2.org/nexus/content/repositories/wso2archtype) - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

 Any idea please?

 Thanks.

 --
 --
 Lahiru Sandaruwan
 Software Engineer,
 Platform Technologies,
 WSO2 Inc., http://wso2.com
 lean.enterprise.middleware

 email: lahi...@wso2.com cell: (+94) 773 325 954
 blog: http://lahiruwrites.blogspot.com/
 twitter: http://twitter.com/lahirus
 linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146


 ___
 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] Build failed in trunk with clean repo

2013-03-02 Thread Dileepa Jayakody

Hi Amila,

On Sun, Mar 3, 2013 at 10:35 AM, Amila Maharachchi ami...@wso2.com wrote:

 Is this because we haven't done the 4.1.0 release yet? Lahiru is building
 the trunk and we cannot expect him to build the branch too.

Yes, the tomcat 7.0.34.wso2v1 bundle is not added to trunk. it's in 4.1.0
branch, and we haven't released it yet. So for the moment we'll have to
build (only) orbit 4.1.0 branch before building trunk.

Thanks,
Dileepa



Sent from my iPad

 On Mar 2, 2013, at 11:13 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Hi Lahiru,

 Please build the orbit 4.1.0 branch first :
 https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.1.0
 tomcat bundle is there.

 Thanks,
 Dileepa

 On Sat, Mar 2, 2013 at 10:06 PM, Lahiru Sandaruwan lahi...@wso2.comwrote:

 Hi,

 $subject,

 Error,

 [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.1.0-SNAPSHOT: Could not
 find artifact org.apache.tomcat.wso2:tomcat:jar:7.0.34.wso2v1 in
 carbon-plugin-repo (
 http://maven.wso2.org/nexus/content/repositories/wso2archtype) - [Help
 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

 Any idea please?

 Thanks.

 --
 --
 Lahiru Sandaruwan
 Software Engineer,
 Platform Technologies,
 WSO2 Inc., http://wso2.com
 lean.enterprise.middleware

 email: lahi...@wso2.com cell: (+94) 773 325 954
 blog: http://lahiruwrites.blogspot.com/
 twitter: http://twitter.com/lahirus
 linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146


 ___
 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




-- 
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] Configuring a Default Feature Repository in Carbon

2013-02-22 Thread Dileepa Jayakody

Hi Isabelle, Pradeep,


On Fri, Feb 22, 2013 at 3:15 PM, Isabelle Mauny isabe...@wso2.com wrote:

 Dileepa,

 Does that mean that the entry will only be there if we've been able to
 validate the connection to it ?

Yes, it will be added only if the repository is valid and available.


 When are we validating this , each time we start the server ?


Default repository is not loaded at server-startup, but in feature-manager
index.jsp [1] when we load feature-manager UI. (This is where we load all
repositories currently added).

Here I do a service-call to load the default-repository, and at the BE, it
calls RepositoryUtils[1] addRepository() which will add the repository if
it's not added already.
When adding a repository P2 validates the given repository URL and if it
can't connect to the repository, it throws a ProvisioningException, if
that's the case the repo will not be added to the list of available
repositories.

Thanks,
Dileepa

[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/feature-manager/org.wso2.carbon.feature.mgt.ui/src/main/resources/web/feature-mgt/index.jsp
[2]
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/feature-manager/org.wso2.carbon.feature.mgt.core/src/main/java/org/wso2/carbon/feature/mgt/core/util/RepositoryUtils.java



 Isabelle.
 __

 *Isabelle Mauny
 *Director, Product Management; WSO2, Inc.;  http://wso2.com/
 email: isabe...@wso2.com - mobile (Spain) : +34 616050684 - mobile (Sri
 Lanka) +94 (0)774777663

 *
 *

 On Feb 21, 2013, at 8:52 PM, Dileepa Jayakody wrote:



 On Wed, Feb 20, 2013 at 5:13 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Wed, Feb 20, 2013 at 4:31 PM, Pradeep Fernando prad...@wso2.comwrote:

 I dont think we should load the repository during startup. Provisioning
 is not a requirement for server startup. The default URL appearing in the
 feature repository textbox is good enought IMHO.

 Yes, I see the point. I'll just update the sample URL text in feature
 manager UI accordingly.


 On second thought; as per the initial requirement of having a default
 per-configured feature repository with carbon, just having the repo-url
 defined in the carbon.xml appear as the sample URL text wouldn't be enough
 I think.
 So I loaded the per-configured repo in feature-manager UI when listing
 available repositories.
 Since adding a pre-defined repository is not mandatory for feature-manager
 functionality, if any error occurs while trying to load the predefined repo
 (say it's not available or hosted) error will be ignored and the repo-url
 will not be added to the list.

 Thanks,
 Dileepa


 Thanks,
 Dileepa

  --Pradeep


 On Wed, Feb 20, 2013 at 4:26 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Wed, Feb 20, 2013 at 11:18 AM, Pradeep Fernando prad...@wso2.comwrote:

 Since we are giving carbon.version during the product build time, how
 about having,

 http://dist.wso2.org/p2/carbon/releases/${carbon.version}
 http://dist.wso2.org/p2/carbon/releases/4.0.5

 as the default. Maven filters will replace the value.

 +1.
 Also if the repository isn't hosted/available, I think we should not
 give an error at startup trying to load the given repository, and continue
 startup without a default repository.

 Having said that, i don't see anything wrong with your approach as
 well, just want to avoid configs if possible.


 --Pradeep


 On Wed, Feb 20, 2013 at 1:43 AM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 Configuring a default feature repository in Carbon has been a
 requirement for sometime now.

 We can do this by having an entry in carbon.xml like below and load
 the given repo by default in feature manager;

 FeatureRepository
 RepositoryNamedefault repository/RepositoryName
 RepositoryURLhttp://dist.wso2.org/p2/carbon/releases/4.0.5
 /RepositoryURL
 /FeatureRepository

 I have done the necessary changes locally, is it good to commit this
 to trunk now and make it available in future releases?

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

 Mobile : +94777-857616




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




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

 Mobile : +94777-857616




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




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

 Mobile : +94777-857616




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

 Mobile : +94777-857616





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

Mobile : +94777-857616

Re: [Dev] Configuring a Default Feature Repository in Carbon

2013-02-21 Thread Dileepa Jayakody

On Wed, Feb 20, 2013 at 5:13 PM, Dileepa Jayakody dile...@wso2.com wrote:



 On Wed, Feb 20, 2013 at 4:31 PM, Pradeep Fernando prad...@wso2.comwrote:

 I dont think we should load the repository during startup. Provisioning
 is not a requirement for server startup. The default URL appearing in the
 feature repository textbox is good enought IMHO.

 Yes, I see the point. I'll just update the sample URL text in feature
 manager UI accordingly.


On second thought; as per the initial requirement of having a default
per-configured feature repository with carbon, just having the repo-url
defined in the carbon.xml appear as the sample URL text wouldn't be enough
I think.
So I loaded the per-configured repo in feature-manager UI when listing
available repositories.
Since adding a pre-defined repository is not mandatory for feature-manager
functionality, if any error occurs while trying to load the predefined repo
(say it's not available or hosted) error will be ignored and the repo-url
will not be added to the list.

Thanks,
Dileepa


 Thanks,
 Dileepa

  --Pradeep


 On Wed, Feb 20, 2013 at 4:26 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Wed, Feb 20, 2013 at 11:18 AM, Pradeep Fernando prad...@wso2.comwrote:

 Since we are giving carbon.version during the product build time, how
 about having,

 http://dist.wso2.org/p2/carbon/releases/${carbon.version}
 http://dist.wso2.org/p2/carbon/releases/4.0.5

 as the default. Maven filters will replace the value.

 +1.
 Also if the repository isn't hosted/available, I think we should not
 give an error at startup trying to load the given repository, and continue
 startup without a default repository.

 Having said that, i don't see anything wrong with your approach as well,
 just want to avoid configs if possible.


 --Pradeep


 On Wed, Feb 20, 2013 at 1:43 AM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 Configuring a default feature repository in Carbon has been a
 requirement for sometime now.

 We can do this by having an entry in carbon.xml like below and load
 the given repo by default in feature manager;

 FeatureRepository
 RepositoryNamedefault repository/RepositoryName
 RepositoryURLhttp://dist.wso2.org/p2/carbon/releases/4.0.5
 /RepositoryURL
 /FeatureRepository

 I have done the necessary changes locally, is it good to commit this
 to trunk now and make it available in future releases?

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

 Mobile : +94777-857616




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




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

 Mobile : +94777-857616




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




 --
 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] Configuring a Default Feature Repository in Carbon

2013-02-20 Thread Dileepa Jayakody

On Wed, Feb 20, 2013 at 11:18 AM, Pradeep Fernando prad...@wso2.com wrote:

 Since we are giving carbon.version during the product build time, how
 about having,

 http://dist.wso2.org/p2/carbon/releases/${carbon.version}
 http://dist.wso2.org/p2/carbon/releases/4.0.5

 as the default. Maven filters will replace the value.

+1.
Also if the repository isn't hosted/available, I think we should not give
an error at startup trying to load the given repository, and continue
startup without a default repository.

Having said that, i don't see anything wrong with your approach as well,
 just want to avoid configs if possible.


 --Pradeep


 On Wed, Feb 20, 2013 at 1:43 AM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 Configuring a default feature repository in Carbon has been a requirement
 for sometime now.

 We can do this by having an entry in carbon.xml like below and load the
 given repo by default in feature manager;

 FeatureRepository
 RepositoryNamedefault repository/RepositoryName
 RepositoryURLhttp://dist.wso2.org/p2/carbon/releases/4.0.5
 /RepositoryURL
 /FeatureRepository

 I have done the necessary changes locally, is it good to commit this to
 trunk now and make it available in future releases?

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

 Mobile : +94777-857616




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




-- 
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] Configuring a Default Feature Repository in Carbon

2013-02-20 Thread Dileepa Jayakody

On Wed, Feb 20, 2013 at 4:31 PM, Pradeep Fernando prad...@wso2.com wrote:

 I dont think we should load the repository during startup. Provisioning is
 not a requirement for server startup. The default URL appearing in the
 feature repository textbox is good enought IMHO.

 Yes, I see the point. I'll just update the sample URL text in feature
manager UI accordingly.

Thanks,
Dileepa

 --Pradeep


 On Wed, Feb 20, 2013 at 4:26 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Wed, Feb 20, 2013 at 11:18 AM, Pradeep Fernando prad...@wso2.comwrote:

 Since we are giving carbon.version during the product build time, how
 about having,

 http://dist.wso2.org/p2/carbon/releases/${carbon.version}
 http://dist.wso2.org/p2/carbon/releases/4.0.5

 as the default. Maven filters will replace the value.

 +1.
 Also if the repository isn't hosted/available, I think we should not give
 an error at startup trying to load the given repository, and continue
 startup without a default repository.

 Having said that, i don't see anything wrong with your approach as well,
 just want to avoid configs if possible.


 --Pradeep


 On Wed, Feb 20, 2013 at 1:43 AM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 Configuring a default feature repository in Carbon has been a
 requirement for sometime now.

 We can do this by having an entry in carbon.xml like below and load the
 given repo by default in feature manager;

 FeatureRepository
 RepositoryNamedefault repository/RepositoryName
 RepositoryURLhttp://dist.wso2.org/p2/carbon/releases/4.0.5
 /RepositoryURL
 /FeatureRepository

 I have done the necessary changes locally, is it good to commit this to
 trunk now and make it available in future releases?

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

 Mobile : +94777-857616




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




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

 Mobile : +94777-857616




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




-- 
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] Multiple profile support in Carbon

2013-02-19 Thread Dileepa Jayakody

On Tue, Feb 19, 2013 at 8:20 AM, Dileepa Jayakody dile...@wso2.com wrote:

Hi All,

targetPath is: $CARBON_HOME/repository/components

Main class change : if no profile is given as a startup parameter, carbon
will start with the default profile : WSO2CarbonProfile

Below steps should be performed to install a new Profile in p2-profile-gen;
1. Publish the product configuration file (eg:carbon.product) with the
initial runtime configurations.
(A product configuration is required to materialize the minimal runtime
before installing features)
2. Materialize the new Profile using above .product configuration file
3. Install features to the new profile

Feature installation in the multi-profile environment is not yet working
as it only updates the relevant Profile but not the relevant bundles.infofile.
The reason for this is that org.eclipse.equinox.p2.installFolder value
gets hard-coded in the Profile during build time and p2 cannot locate the
bundles.info file in the modified directory structure. Need to fix this.

Now the problem is with relative paths defined in features p2.inf files
(eg: org.eclipse.equinox.p2.touchpoint.natives.copy(source:*${installFolder}
*
/features/org.wso2.carbon.cassandra.dataaccess_${feature.version}/conf/cassandra-component.xml,target:
*${installFolder*}/../conf/etc/cassandra-component.xml,overwrite:true);).

Thanks,
Dileepa

The related jira : https://wso2.org/jira/browse/CARBON-14064

Thanks,
Dileepa

--
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] Configuring a Default Feature Repository in Carbon

2013-02-19 Thread Dileepa Jayakody

Hi All,

Configuring a default feature repository in Carbon has been a requirement
for sometime now.

We can do this by having an entry in carbon.xml like below and load the
given repo by default in feature manager;

FeatureRepository
RepositoryNamedefault repository/RepositoryName
RepositoryURLhttp://dist.wso2.org/p2/carbon/releases/4.0.5
/RepositoryURL
/FeatureRepository

I have done the necessary changes locally, is it good to commit this to
trunk now and make it available in future releases?

Thanks,
Dileepa
-- 
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] Multiple profile support in Carbon

2013-02-18 Thread Dileepa Jayakody

Hi All,

I continued with the 1st option of updating the relative paths for
source,destination in p2.inf of platform features in the new multi-profile
target directory structure.
Based on that I have done below changes to kernel in the scratch area;

1. carbon-p2-plugin [1]
Updated the p2-director launcher arguments to support multiple-profile
installations with a shared p2 area, in MaterialzeProductMojo and
ProfileGenMojo
 -destination : targetPath/${profile}
 -shared : targetPath/p2

targetPath is: $CARBON_HOME/repository/components

2. carbon.server [2]
CarbonLauncher changes: At startup osgi-runtime arguments are passed
according on the running profile
osgi.install.area : repository/components/${profile}
osgi.configuration.area : repository/components/${profile}/configuration
eclipse.p2.data.area : repository/components/p2 (not changed as we are
using a shared p2 area for all profiles)

Main class change : if no profile is given as a startup parameter, carbon
will start with the default profile : WSO2CarbonProfile

3. Product p2-profile-gen [3]
Please see how a new Profile can be installed into the distribution in a
product's p2-profile-gen.
I have changed the carbon product p2-profile-gen [3] module, to install a
new Profile : WSO2SampleProfile that has tryit, soaptracer features
installed in addition to the carbon.runtime and carbon.core features.

Below steps should be performed to install a new Profile in p2-profile-gen;
1. Publish the product configuration file (eg:carbon.product) with the
initial runtime configurations.
(A product configuration is required to materialize the minimal runtime
before installing features)
2. Materialize the new Profile using above .product configuration file
3. Install features to the new profile

Please find the carbon distribution at [4] which has WSO2CarbonProfile,
WSO2SampleProfile pre-installed.
You can start Carbon to load a profile by giving profile argument at
startup (eg: ./wso2server.sh -Dprofile=WSO2SampleProfile)

Feature installation in the multi-profile environment is not yet working as
it only updates the relevant Profile but not the relevant bundles.infofile.
The reason for this is that org.eclipse.equinox.p2.installFolder value gets
hard-coded in the Profile during build time and p2 cannot locate the
bundles.info file in the modified directory structure. Need to fix this.
The related jira  : https://wso2.org/jira/browse/CARBON-14064

Thanks,
Dileepa


[1] https://svn.wso2.org/repos/wso2/scratch/dileepa/carbon-p2-plugin
[2]
https://svn.wso2.org/repos/wso2/scratch/dileepa/kernel/trunk/core/org.wso2.carbon.server
[3]
https://svn.wso2.org/repos/wso2/scratch/dileepa/kernel/trunk/distribution/product/modules/p2-profile-gen/pom.xml
[4]
https://svn.wso2.org/repos/wso2/scratch/dileepa/wso2carbon-4.1.0-SNAPSHOT.zip
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Multiple profile support in Carbon

2013-02-16 Thread Dileepa Jayakody

Hi All,
On Fri, Feb 15, 2013 at 4:08 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Hi All,

 After some discussions with p2-dev guys on how to support multiple product
 installations in a single distribution, the previous directory structure
 had to be slightly modified to provide separate configuration directory per
 installed Product.
 (Here a P2-Profile represents a separate Product; eg: WSO2CarbonProfile
 represents the carbon product, WSO2ASProfile represents the AppServer
 product )

 So the modified distribution structure now looks like below;
 *repository/components/*
 |--WSO2CarbonProfile
 |/configuration
 |   |--config.ini
 |   |--org.eclipse.equinox.simpleconfigurator/bundles.info (bundle
 set to load Carbon product)
 |
 |--WSO2ASProfile
 |/configuration
 |   |--config.ini
 |   |--org.eclipse.equinox.simpleconfigurator/bundles.info (bundle
 set to load AS product) *

 repository/components/p2 *{shared p2 data directory for above created
 profiles}
 |--org.eclipse.equinox.p2.engine
 |  |--profileRegistry
 ||---WSO2CarbonProfile.profile {profile state of Carbon}
 ||---WSO2ASProfile.profile {profile state of AS}

 To generate the above target distribution structure using carbon-p2-plugin
 we should parse the correct arguments to the p2-director [1]. P2-director
 is the tool we invoke underneath carbon-p2-plugin to perform provisioning
 actions and build our product distributions.

 We can parse below arguments to p2-director to create a shared
 installation in our product build;
 *-shared* ${carbon.components.dir}/p2
 *-destination* ${carbon.components.dir}/{ProfileID}

 When giving -destination separately for each Profile (eg: -destination
/media/Carbon_Volume/carbon/platform/branches/4.0.0/products/bam2/2.1.0/modules/p2-profile-gen/target/wso2carbon-core-4.0.6/repository/components/WSO2BAMReceiverProfile)
and installing features, an error occurs[1] for features having p2
instructions to copy files to target directories.

The issue is with the variable ${installFolder} used by the instructions.
It defaults to the destination of the current profile :
${carbon.home}/repository/components/${profile} and the relative path to
find the source and target becomes invalid for instructions like below in
the multi-profile target environment:
org.eclipse.equinox.p2.touchpoint.natives.copy(source:${installFolder}/features/org.wso2.carbon.cassandra.dataaccess_${feature.version}/conf/cassandra-component.xml,target:${installFolder}/../conf/etc/cassandra-component.xml,overwrite:true);

So the 2 options to rectify this installation issue are;

1. Change our features' p2.inf files to define the relative paths of source
and destination in the new multi-profile target environment.
2. Invoke p2-director with -destination :
${carbon.home}/repository/components/ in p2-profile-gen phase (as we
normally do), without specifying it per each Profile and do a manual file
operation to move generated directories under the
${carbon.home}/repository/${Profile} after the the profile-gen operation is
executed.

What could be the better option here?

Thanks,
Dileepa

[1] Error :
An error occurred while configuring the installed items
 session context was:(profile=WSO2BAMReceiverProfile,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
-- [R]org.wso2.carbon.cassandra.dataaccess.feature.group 4.0.5,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 I/O Error while copying
/media/Carbon_Volume/carbon/platform/branches/4.0.0/products/bam2/2.1.0/modules/p2-profile-gen/target/wso2carbon-core-4.0.6/repository/components/WSO2BAMReceiverProfile/features/org.wso2.carbon.cassandra.dataaccess_4.0.5/conf/cassandra-component.xml
- see details.
Caused by:  java.io.IOException: Source:
/media/Carbon_Volume/carbon/platform/branches/4.0.0/products/bam2/2.1.0/modules/p2-profile-gen/target/wso2carbon-core-4.0.6/repository/components/WSO2BAMReceiverProfile/features/org.wso2.carbon.cassandra.dataaccess_4.0.5/conf/cassandra-component.xmldoes
not exists




 -shared parameter indicates that the installed products share the same
 p2-data area to store/retrieve the P2-Profile related information
 -destination is the installation path given for each product. (For each
 Product profile we can change this -destination argument like
 {carbon.home}/repository/components/WSO2CarbonProfile,
 {carbon.home}/repository/components/WSO2ASProfile)

 example invocation of p2-director to install carbon.core.feature to
 WSO2CarbonProfile in a shared installation:

 -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
 file:/media/Carbon_Volume/Ubuntu_Resources/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.6/target/p2-repo
 -artifactRepository
 file:/media/Carbon_Volume/Ubuntu_Resources/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.6/target/p2-repo
 -profileProperties org.eclipse.update.install.features=true -installIU

Re: [Dev] Multiple profile support in Carbon

2013-02-15 Thread Dileepa Jayakody

, if we are going to create a BAM product with
different profiles such as Receiver, Analyzer, Dashboard etc, per each
profile we need to materialize bam-receiver.product, bam-analyzer.product,
bam-dashboard.product and construct the Profiles separately.

Can someone suggest a better approach in achieving this?

Thanks,
Dileepa


[1]
http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html
[2]
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/kernel/pom.xml
[3]
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/kernel/carbon.product
[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=287619

On Thu, Jan 31, 2013 at 11:09 AM, Pradeep Fernando prad...@wso2.com wrote:

 Excellent progress!!

 --Pradeep


 On Thu, Jan 31, 2013 at 11:08 AM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi Pradeep and All,

 To give a brief introduction on this; the purpose of this implementation
 is to be able to pre-provision several products in to one distribution and
 select the product to load at startup.
 Each product can be considered a separate Product profile and at startup
 by passing an argument like -Dprofile={Product.Profile} we should be able
 to load the required product.

 After doing some background research on Equinox configurations I did a
 POC by manually constructing the product distribution structure to support
 this (as shown below), and point the equinox.configuration directory to
 relevant {Profile}configuration directory at startup. This will load the
 set of bundles relevant to the given Product.Profile.

 *Things to do;*
 Need to look at on how to support feature installations separately to the
 loaded Profile. Currently after loading a particular profile and installing
 features the newly added bundle entries are not persisted.
 I'm currently working on changing the carbon-p2-plugin goals to construct
 the modified product distribution structure.
 Will update the thread on the progress.
 *

 Modified Product structure to support multiple-profiles*
 *repository/components/configuration *{equinox configuration directory}
 |
 |--WSO2CarbonProfile
 ||--config.ini
 ||--org.eclipse.equinox.simpleconfigurator/bundles.info {bundle set
 to load Carbon product}
  |--WSO2ASProfile
 ||--config.ini
 ||--org.eclipse.equinox.simpleconfigurator/bundles.info {bundle set
 to load AS product}

 *repository/components/p2 *{p2 data directory}
 |--org.eclipse.equinox.p2.engine
 |  |--profileRegistry
 ||---WSO2CarbonProfile.profile {p2 state of Carbon}
 ||---WSO2ASProfile.profile {p2 state of AS}

 Thanks,
 Dileepa



 On Thu, Jan 31, 2013 at 8:38 AM, Pradeep Fernando prad...@wso2.comwrote:

 Hi,

 Dileepa working on the $subject.

 @Dileepa : can you please provide a brief update :)


 thanks,
 --Pradeep





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

 Mobile : +94777-857616




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




-- 
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] Add Latest Version Of Features To Carbon

2013-02-13 Thread Dileepa Jayakody

Hi Bram,

On Wed, Feb 13, 2013 at 9:43 PM, Bram Cymet bcy...@cbnco.com wrote:

 Hi,

 Correct me if I am wrong but the best way to install multiple wso2
 products on the same server is to first install carbon and then add
 features correct?

Yep you can install the required features on top of carbon and compose a
product as per your requirement.


 I am attempting to do this and I added
 http://dist.wso2.org/p2/carbon/releases/4.0.4/ as a repository.

 This repository does not seem to have the latest versions of the
 application server 5.0.1 and esb 4.6?


 Is there a more current repository? I am hoping to have a unified
 interface for all my wso2 products and user that latest versions.

 You can find App server 5.0.2 and ESB 4.6.0 features hosted in the p2-repo
at :  http://dist.wso2.org/p2/carbon/releases/4.0.5/

 Thanks,

 Thanks,
Dileepa

 --
 Bram Cymet
 Software Developer
 Canadian Bank Note Co. Ltd.
 613-608-9752
 ___
 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] Adding Data Agents as a different composite feature

2013-02-10 Thread Dileepa Jayakody

On Mon, Feb 11, 2013 at 12:55 AM, Kasun Weranga kas...@wso2.com wrote:



 On Mon, Feb 11, 2013 at 12:47 AM, Sinthuja Ragendran sinth...@wso2.comwrote:

 Hi Maninda,

 I think the data agents should be removed from BAM composite feature, and
 only JMX data agent  should be added under BAM feature category, which is
 shipped as default in BAM distribution. AFAIU having the feature
 category is basically a logical group of required features for a particular
 product and it enables a user to install, say BAM features in any WSO2
 server and get the BAM functionality. Therefore as far as the data agents
 are not there in standard BAM distribution, it's not logical to have it
 under BAM composite feature. And some data agents such as mediation stats
 agent and BAM mediator are not relevant to be within the BAM product.

 IMHO we should remove the Data Agents from BAM composite feature and
 include it as separate feature category.


 +1, We need to separate out data-agent from BAM category.


+1.
I think BAM data agents are considered a separate category already right? I
see in 4.0.5 p2-repo [1] the data-agents are grouped under a separate
category.

On a side note: Please note that creating product-level composite features
is important to support sub-categorization of features under your product.
Lets make sure the sub-categories reflect functional level grouping of
features under the product categories so that it provides a more
fine-grained selection of features for the users at feature installation.
Also please test installation of your features onto Carbon and other base
products (eg: AS) and see the installation is successful with required
configurations.

Thanks,
Dileepa

[1] http://dist.wso2.org/p2/carbon/releases/4.0.5/



 Thanks,
 Sinthuja.


 On Sun, Feb 10, 2013 at 10:29 PM, Maninda Edirisooriya 
 mani...@wso2.comwrote:

 BAM Data Agents are currently added as a feature in BAM composite
 feature. So it is visible inside the tree under BAM when Find Features
 button is clicked in 4.0.7 p2-repo installation UI. There is another
 argument that BAM Data Agents should be shipped outside the BAM product
 separately as they are not a part of BAM. In the upcoming release 4.0.7
 there only BAM and IS are there. If Data Agents are shipped outside BAM
 then there will be three of them. WDYT?



 *Maninda Edirisooriya*
 Software Engineer
 *WSO2, Inc.
 *lean.enterprise.middleware.

 *Blog* : http://maninda.blogspot.com/
 *Phone* : +94 777603226

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




 --
 *Sinthuja Rajendran*
 Software Engineer http://wso2.com/
 WSO2, Inc.:http://wso2.com

 Blog: http://sinthu-rajan.blogspot.com/
 Mobile: +94774273955



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




 --
 *Kasun Weranga*
 **
 Member, Management Committee - Data Technologies
 Software Engineer
 *WSO2, Inc.
 *lean.enterprise.middleware.
 mobile : +94 772314602
 http://sanjeewamalalgoda.blogspot.com/blog :
 http://kasunweranga.blogspot.com/
 ___
 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] [Bamboo-Build] WSO2 Carbon 4.0.x Kernel 4.0.6 #50 has FAILED. Change made by dileepa.

2013-02-05 Thread Dileepa Jayakody

Fixed by adding the missing feature.mgt.ui 4.0.6 component

Thanks,
Dileepa

On Tue, Feb 5, 2013 at 12:02 PM, Bamboo cbuil...@wso2.org wrote:

  [image: Failed]  WSO2 Carbon 
 4.0.xhttp://wso2.org/bamboo/browse/WCB001/› Kernel
 4.0.6 http://wso2.org/bamboo/browse/WCB001-KER006/ › 
 #50http://wso2.org/bamboo/browse/WCB001-KER006-50/
 failed

 Changes by dileepa http://wso2.org/bamboo/browse/author/dileepa

 No failed tests found, a possible compilation error.
   Responsible No one is responsible for this build.
   Failing Jobs http://wso2.org/bamboo/browse/WCB001-KER006-50/Job
 Duration Tests[image: Failed]  Default 
 Jobhttp://wso2.org/bamboo/browse/WCB001-KER006-JOB1-50/ (Default
 Stage)  9 seconds  No tests found  
 Logshttp://wso2.org/bamboo/browse/WCB001-KER006-JOB1-50/log|
 Artifacts http://wso2.org/bamboo/browse/WCB001-KER006-JOB1-50/artifact 
 Code
 Changes http://wso2.org/bamboo/browse/WCB001-KER006-50/commit/  View
 full change detailshttp://wso2.org/bamboo/browse/WCB001-KER006-50/commit/
 dileepa http://wso2.org/bamboo/browse/author/dileepa
 reverting commit to 4.0.5 component  160965
 dileepahttp://wso2.org/bamboo/browse/author/dileepa
 fixing feature manager UI bug in the tableTree.js to list down feature
 lists which more than 10 rows  160959 View 
 Onlinehttp://wso2.org/bamboo/browse/WCB001-KER006-50
 | Add 
 Commentshttp://wso2.org/bamboo/browse/WCB001-KER006-50?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




-- 
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] Integration tests to cover p2 feature installation across platform

2013-01-31 Thread Dileepa Jayakody

On Thu, Jan 31, 2013 at 11:49 PM, Pradeep Fernando prad...@wso2.com wrote:




 On Thu, Jan 31, 2013 at 11:44 PM, Amila Maha Arachchi ami...@wso2.comwrote:

 Hi Pradeep,

 Seems like a good thing to consider. Do you mean to run these tests
 during the build time (integration tests) or against a built pack (by using
 the test automation binary pack)?


 the latter seems to be way to proceed. But I'm not sure. Open for ideas. :)


+1 for running against built packs and the platform p2-repo.
This way we can iteratively test the p2-repo against all product
combinations for resolution conflicts and startup issues after feature
installations.
--Pradeep




 AmilaM.

 On Thu, Jan 31, 2013 at 10:24 PM, Pradeep Fernando prad...@wso2.comwrote:

  Hi,

 Right now we are updating the P2-repo as and when an issue occurs. Can't
 blame product teams/QA either since we are only doing smoke testing against
 the p2-repo.


 The idea is to incorporate feature installation in to integration tests
 and sort out feature level issues early in the release cycle. There we
 should test for most common user scenarios.

 eg: install IS feature set to ESB product and run both IS and ESB
 integration tests.

 Can we use clarity to do the above ?

 Ideally this should be declarative. Means we should be able to give the,

 target platform : ESB
 feature-list-to-install : list of features
 integration test suite to run against the end product.

 may be im bit too ambitious. I'm ok to start the effort with whatever
 implementation we have.

 Krishantha et al, WDYT ?


 thanks,
 --Pradeep

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




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

 Blog: http://maharachchi.blogspot.com
 Mobile: +94719371446




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




-- 
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] Multiple profile support in Carbon

2013-01-30 Thread Dileepa Jayakody

Hi Pradeep and All,

To give a brief introduction on this; the purpose of this implementation is
to be able to pre-provision several products in to one distribution and
select the product to load at startup.
Each product can be considered a separate Product profile and at startup by
passing an argument like -Dprofile={Product.Profile} we should be able to
load the required product.

After doing some background research on Equinox configurations I did a POC
by manually constructing the product distribution structure to support this
(as shown below), and point the equinox.configuration directory to relevant
{Profile}configuration directory at startup. This will load the set of
bundles relevant to the given Product.Profile.

*Things to do;*
Need to look at on how to support feature installations separately to the
loaded Profile. Currently after loading a particular profile and installing
features the newly added bundle entries are not persisted.
I'm currently working on changing the carbon-p2-plugin goals to construct
the modified product distribution structure.
Will update the thread on the progress.
*

Modified Product structure to support multiple-profiles*
*repository/components/configuration *{equinox configuration directory}
|
|--WSO2CarbonProfile
||--config.ini
||--org.eclipse.equinox.simpleconfigurator/bundles.info {bundle set to
load Carbon product}
|--WSO2ASProfile
||--config.ini
||--org.eclipse.equinox.simpleconfigurator/bundles.info {bundle set to
load AS product}

*repository/components/p2 *{p2 data directory}
|--org.eclipse.equinox.p2.engine
|  |--profileRegistry
||---WSO2CarbonProfile.profile {p2 state of Carbon}
||---WSO2ASProfile.profile {p2 state of AS}

Thanks,
Dileepa


On Thu, Jan 31, 2013 at 8:38 AM, Pradeep Fernando prad...@wso2.com wrote:

 Hi,

 Dileepa working on the $subject.

 @Dileepa : can you please provide a brief update :)


 thanks,
 --Pradeep





-- 
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] org.wso2.esb.mandatory.feature

2013-01-23 Thread Dileepa Jayakody

Hi Gihan,

It's at
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/features/composite-features/esb/esb-mandatory/4.0.6

Thanks,
Dileepa

On Wed, Jan 23, 2013 at 2:53 PM, Gihan Anuruddha gi...@wso2.com wrote:

 Hi,

 Where I can find the $subject ?

 Regards,
 ---
 W.G. Gihan Anuruddha
 Software Engineer | WSO2, Inc.
 Phone: +9477272595 callto:+9477272595

 ___
 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] org.wso2.esb.mandatory.feature

2013-01-23 Thread Dileepa Jayakody

Hi Amila,

On Wed, Jan 23, 2013 at 3:26 PM, Amila Maha Arachchi ami...@wso2.comwrote:

 Never heard of it. But the grep command is there.

It has been added recently, as a product specific composite-feature to
support feature sub-categorization in P2-repo.

thanks,
Dileepa


 On Wed, Jan 23, 2013 at 2:53 PM, Gihan Anuruddha gi...@wso2.com wrote:

 Hi,

 Where I can find the $subject ?

 Regards,
 ---
 W.G. Gihan Anuruddha
 Software Engineer | WSO2, Inc.
 Phone: +9477272595 callto:+9477272595

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




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




-- 
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] User mgt bundle in both carbon core server and carbon core commons feature?

2013-01-18 Thread Dileepa Jayakody

Hi Tharindu,

IMO there's no valid reason for having the same bundle in both core.server
and core.common features. According to our feature convention I think it
should be included in core.server feature.
We can remove it from core.common feature.

Thanks,
Dileepa

On Fri, Jan 18, 2013 at 3:08 PM, Tharindu Mathew thari...@wso2.com wrote:

 Hi,

 $subject. May I know the reason?

 --
 Regards,

 Tharindu Mathew

 Associate Technical Lead, WSO2 BAM
 Member - Data Mgmt. Committee

 blog: http://tharindumathew.com/
 M: +9459908




-- 
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] User mgt bundle in both carbon core server and carbon core commons feature?

2013-01-18 Thread Dileepa Jayakody

Please note I removed user.mgt and user.core from carbon.core.common
feature and added them in carbon.core.server feature

On Fri, Jan 18, 2013 at 3:58 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Hi Tharindu,

 IMO there's no valid reason for having the same bundle in both core.server
 and core.common features. According to our feature convention I think it
 should be included in core.server feature.
 We can remove it from core.common feature.

 Thanks,
 Dileepa


 On Fri, Jan 18, 2013 at 3:08 PM, Tharindu Mathew thari...@wso2.comwrote:

 Hi,

 $subject. May I know the reason?

 --
 Regards,

 Tharindu Mathew

 Associate Technical Lead, WSO2 BAM
 Member - Data Mgmt. Committee

 blog: http://tharindumathew.com/
 M: +9459908




 --
 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] [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 cbuil...@wso2.org wrote:

  [image: Failed]  WSO2 Carbon 
 4.0.xhttp://wso2.org/bamboo/browse/WCB001/› Kernel
 4.0.6 http://wso2.org/bamboo/browse/WCB001-KER006/ › 
 #20http://wso2.org/bamboo/browse/WCB001-KER006-20/
 failed

 Changes by dileepa http://wso2.org/bamboo/browse/author/dileepa

 No failed tests found, a possible compilation error.
   Responsible No one is responsible for this build.
   Failing Jobs http://wso2.org/bamboo/browse/WCB001-KER006-20/Job
 Duration Tests[image: Failed]  Default 
 Jobhttp://wso2.org/bamboo/browse/WCB001-KER006-JOB1-20/ (Default
 Stage)  12 minutes  No tests found  
 Logshttp://wso2.org/bamboo/browse/WCB001-KER006-JOB1-20/log|
 Artifacts http://wso2.org/bamboo/browse/WCB001-KER006-JOB1-20/artifact 
 Code
 Changes http://wso2.org/bamboo/browse/WCB001-KER006-20/commit/  View
 full change detailshttp://wso2.org/bamboo/browse/WCB001-KER006-20/commit/
 dileepa http://wso2.org/bamboo/browse/author/dileepa
 incorperating serverStartupDuration param addition to ServerData  153256
 dileepa http://wso2.org/bamboo/browse/author/dileepa
 updating features to incorperate ServerStartupDuration addition to
 ServerData  153255dileepahttp://wso2.org/bamboo/browse/author/dileepa
 adding serverStartupDuration to ServerData so that it can be accessed via
 ServerAdmin  153254 View 
 Onlinehttp://wso2.org/bamboo/browse/WCB001-KER006-20
 | Add 
 Commentshttp://wso2.org/bamboo/browse/WCB001-KER006-20?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




-- 
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] [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 dile...@wso2.com wrote:

 I'm looking into this.

 On Thu, Jan 17, 2013 at 3:27 AM, Bamboo cbuil...@wso2.org wrote:

  [image: Failed]  WSO2 Carbon 
 4.0.xhttp://wso2.org/bamboo/browse/WCB001/› Kernel
 4.0.6 http://wso2.org/bamboo/browse/WCB001-KER006/ › 
 #20http://wso2.org/bamboo/browse/WCB001-KER006-20/
 failed

 Changes by dileepa http://wso2.org/bamboo/browse/author/dileepa

 No failed tests found, a possible compilation error.
Responsible No one is responsible for this build.
Failing Jobs http://wso2.org/bamboo/browse/WCB001-KER006-20/ Job
 Duration Tests[image: Failed]  Default 
 Jobhttp://wso2.org/bamboo/browse/WCB001-KER006-JOB1-20/ (Default
 Stage)  12 minutes  No tests found  
 Logshttp://wso2.org/bamboo/browse/WCB001-KER006-JOB1-20/log|
 Artifacts http://wso2.org/bamboo/browse/WCB001-KER006-JOB1-20/artifact 
 Code
 Changes http://wso2.org/bamboo/browse/WCB001-KER006-20/commit/  View
 full change detailshttp://wso2.org/bamboo/browse/WCB001-KER006-20/commit/
 dileepa http://wso2.org/bamboo/browse/author/dileepa
 incorperating serverStartupDuration param addition to ServerData  153256
 dileepa http://wso2.org/bamboo/browse/author/dileepa
 updating features to incorperate ServerStartupDuration addition to
 ServerData  153255dileepahttp://wso2.org/bamboo/browse/author/dileepa
 adding serverStartupDuration to ServerData so that it can be accessed via
 ServerAdmin  153254 View 
 Onlinehttp://wso2.org/bamboo/browse/WCB001-KER006-20
 | Add 
 Commentshttp://wso2.org/bamboo/browse/WCB001-KER006-20?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




 --
 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] Is Product == Carbon Core + Set of Features true?

2013-01-14 Thread Dileepa Jayakody

: 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




 --
 Kasun Indrasiri
 Associate Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 71 536 4128
 Blog : http://kasunpanorama.blogspot.com/




 --
 * http://wso2con.com/
 *
 *

 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

 Thanks,
Dileepa

[1] http://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instructions_35


-- 
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] Unwanted UI permissions.

2013-01-10 Thread Dileepa Jayakody

Hi Ajith,

Since the permissions are configured in the BE component.xml which is
packaged inside the server feature, these permissions will get included by
default during feature installation.

At the moment when we build products using carbon-p2-plugin, we don't do
any product specific customization logic to configure/edit  the installing
features. To support such product-wise customization of features, I think
we need to improve the p2-plugin. Same kind of improvement needs to be
incorporated in feature-manager to to perform a filtering logic during
feature installations from a p2-repo.
Another possible way of achieving such customized installation would be to
maintain  some-kind of product-wise profiles inside the features so during
installation, it will be configured according to the target product.

WDYT?

Thanks,
Dileepa

On Fri, Jan 11, 2013 at 6:09 AM, Ajith Vitharana aji...@wso2.com wrote:


 Hi all,

 We are using  some features that are not directly related with product.
 Therefore, unwanted UI permissions are adding to permission tree.

 Eg: G-Reg using human task server feature for work list notification,
 therefore some unwanted UI permissions are showing in permission tree(see
 the attached image).

 Add HumanTasks
 Manage HumanTask Packages
 Manage HumanTasks

 How do we remove those permissions while adding those features ?

 Thanks
 Ajith


 --
 Ajith Vitharana.
 Senior Software Engineer,
 Member,Management Committee,
 Integration Technologies.

 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94772217350




-- 
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] [Bamboo-Build] WSO2 Carbon 4.0.x Products 4.0.6 #10 has FAILED (1 tests failed, no failures were new). Change made by prabatha, dimuthul and dushan.

2013-01-05 Thread Dileepa Jayakody

fixed stratos.common features in 152797.
importFeatureDef for identity.authenticator.saml.sso features had a minor
error (.feature part in the definition is not required).

On Sat, Jan 5, 2013 at 12:01 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:



 On Sat, Jan 5, 2013 at 10:54 AM, Amila Maha Arachchi ami...@wso2.comwrote:

 Please have a look. Integration tests looking for is-4.0.2.zip and cannot
 be found.


 IS p2-profile-generation fails.

 04-Jan-2013 08:28:32 Cannot complete the install because one or more
 required items could not be found.  04-Jan-2013 08:28:32  Software being
 installed: WSO2 Stratos - Common Composite Feature 2.0.6
 (org.wso2.carbon.stratos.common.feature.group 2.0.6)  04-Jan-2013
 08:28:32  Missing requirement: WSO2 Stratos - Common Core Feature 2.0.6
 (org.wso2.carbon.stratos.common.server.feature.group 2.0.6) requires
 'org.wso2.carbon.identity.authenticator.saml2.sso.server.*feature.feature*.group
 [4.0.3,4.1.0)' but it could not be found  04-Jan-2013 08:28:32  Cannot
 satisfy dependency:  04-Jan-2013 08:28:32   From: WSO2 Stratos - Common
 Composite Feature 2.0.6 (org.wso2.carbon.stratos.common.feature.group 2.0.6)  
 04-Jan-2013
 08:28:32   To: org.wso2.carbon.stratos.common.server.feature.group [2.0.6]  
 04-Jan-2013
 08:28:32 Application failed, log file location:
 /home/bamboo/Bamboo-3.4/Bamboo/.m2/AGENT-23035905/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1357316908400.log
   04-Jan-2013
 08:28:32


 thanks,
 dimuthu


 On Fri, Jan 4, 2013 at 10:01 PM, Bamboo cbuil...@wso2.org wrote:

  [image: Failed]  WSO2 Carbon 
 4.0.xhttp://wso2.org/bamboo/browse/WCB001/› Products
 4.0.6 http://wso2.org/bamboo/browse/WCB001-PRO006/ › 
 #10http://wso2.org/bamboo/browse/WCB001-PRO006-10/
 failed

 Changes by 3 
 peoplehttp://wso2.org/bamboo/browse/WCB001-PRO006-10#changesSummary

 *1/1* tests failed.
Responsible No one is responsible for this build.
Failing Jobs http://wso2.org/bamboo/browse/WCB001-PRO006-10/Job
 Duration Tests[image: Failed]  Default 
 Jobhttp://wso2.org/bamboo/browse/WCB001-PRO006-JOB1-10/ (Default
 Stage)  3 minutes  1 of 1 failed  
 Logshttp://wso2.org/bamboo/browse/WCB001-PRO006-JOB1-10/log|
 Artifacts http://wso2.org/bamboo/browse/WCB001-PRO006-JOB1-10/artifact
  Code
 Changes http://wso2.org/bamboo/browse/WCB001-PRO006-10/commit/  View
 all 4 code changeshttp://wso2.org/bamboo/browse/WCB001-PRO006-10/commit/
 dushan http://wso2.org/bamboo/browse/author/dushan
 when POX failed the soap fault  handler didn't work properly and the
 committed revision will resolve the pending POX soap failures  152790
 prabatha http://wso2.org/bamboo/browse/author/prabatha
 committing modified stub of RSSAdmin  152789
 prabathahttp://wso2.org/bamboo/browse/author/prabatha
 modifying RSSAdmin service to include two operations to check the
 existence of a database/database user  152788   1 more 
 changes…http://wso2.org/bamboo/browse/WCB001-PRO006-10/commit
 Tests http://wso2.org/bamboo/browse/WCB001-PRO006-10/test  View full
 test details http://wso2.org/bamboo/browse/WCB001-PRO006-10/test   1
 Existing Test Failures   Test Job ISTestServerManager 
 startServerhttp://wso2.org/bamboo/browse/WCB001-PRO006-JOB1-10/test/case/41485705
   Default
 Job http://wso2.org/bamboo/browse/WCB001-PRO006-JOB1-10/test View
 Online http://wso2.org/bamboo/browse/WCB001-PRO006-10 | Add 
 Commentshttp://wso2.org/bamboo/browse/WCB001-PRO006-10?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




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



 ___
 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] Identity server profile gen failing

2013-01-05 Thread Dileepa Jayakody

Hi Tharindu,

Fixed the error in stratos.common feature (r152797) which is used to build
IS profile. It builds successfully now.

Thanks,
Dileepa

On Sat, Jan 5, 2013 at 12:53 PM, Tharindu Mathew thari...@wso2.com wrote:

 Hi,

 $subject... with the mysterious error code 13...


 INFO] WSO2 Cloud Identity - Tenant Configuration User Interface  SUCCESS
 [3.916s]
 [INFO] WSO2 Carbon - Identity UI Feature . SUCCESS [0.172s]
 [INFO] WSO2 IS - IS Profile Generation ... FAILURE
 [38.092s]
 [INFO] Identity Server ... SKIPPED
 [INFO] WSO2 Identity Server Styles Parent  SKIPPED
 [INFO] Identity Server: UI styles  SKIPPED
 [INFO] Identity Server Integration Tests . SKIPPED
 [INFO] Identity Server : Samples . SKIPPED
 [INFO] Samples/Remote User Management  SKIPPED
 [INFO] WSO2 Carbon - Patch releases - products - Aggregator Module  SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 14:07.446s
 [INFO] Finished at: Sat Jan 05 12:46:05 IST 2013
 [INFO] Final Memory: 228M/475M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5:p2-profile-gen
 (3-p2-profile-generation) on project identity-profile-gen: P2 publisher
 return code was 13 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :identity-profile-gen

 --
 Regards,

 Tharindu

 blog: http://mackiemathew.com/
 M: +9459908

 ___
 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] Properly use importFeatureDef to import external feature dependencies when developing Carbon Features

2013-01-03 Thread Dileepa Jayakody

On Wed, Jan 2, 2013 at 6:59 PM, Prabath Abeysekera praba...@wso2.comwrote:

 Hi,

 On Wed, Jan 2, 2013 at 6:24 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Hi All,

 I came across some more features in our platform which have included
 external features instead of importing them as dependencies.
 As explained above, these included features can cause P2 installation
 version conflicts. We must fix these features to import their external
 dependency features rather than including them, to avoid such conflicts in
 future.

 Following is the list of features which have included external features;

- 
 ./mediation-initializer/org.wso2.carbon.mediation.initializer.server.feature/4.0.2/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.event.server.feature:4.0.2/includedFeatureDef


- ./service-mgt/org.wso2.carbon.service.mgt.ui.feature/4.0.0/pom.xml:



 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.throttle.ui.feature/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.module.mgt.ui.feature:${project.version}/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.throttle.ui.feature:${project.parent.version}/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.caching.ui.feature:${project.parent.version}/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.rm.ui.feature:${project.parent.version}/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.security.mgt.ui.feature:${project.version}/includedFeatureDef


- 
 ./stratos/common/org.wso2.carbon.stratos.common.server.feature/2.0.5/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.server.feature:4.0.3/includedFeatureDef


- 
 ./stratos/common/org.wso2.carbon.stratos.common.ui.feature/2.0.6/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature:4.0.6/includedFeatureDef


- 
 ./data-services/data-services-tasks/org.wso2.carbon.dataservices.task.server.feature/4.0.5/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.ntask.core.feature:4.0.5/includedFeatureDef


- 
 ./identity/oauth/org.wso2.carbon.identity.oauth.ui.feature/4.0.5/pom.xml:


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:4.0.5/includedFeatureDef


- 
 ./identity/scim/org.wso2.carbon.identity.scim.provider.feature/4.0.5/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:4.0.5/includedFeatureDef


- ./rss-manager/org.wso2.carbon.rssmanager.server.feature/4.0.1/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.service.mgt.server.feature:4.0.1

 The above feature was already fixed in 4.0.5 branch.


Yes, org.wso2.carbon.rssmanager.server.feature and
org.wso2.carbon.mediation.initializer.server.feature are fixed in 4.0.5.
sorry for adding them in this list.




- ./cg/org.wso2.carbon.cloud.gateway.feature/4.0.2/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.mediation.initializer.server.feature:4.0.2/includedFeatureDef

 If there are no objections, and feature owners are agreeable to above
 change, can we please fix these features in 4.0.6?

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 7:38 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Thu, Dec 13, 2012 at 7:31 PM, Pradeep Fernando prad...@wso2.comwrote:

 May be you should make this a blog post, so that others can easily
 refer this. Good post!!

 Actually I have written one post on general guidelines for Feature
 developers :
 http://dileepajayakody.blogspot.com/2012/11/guidelines-for-carbon-feature-developers.html
 :)

 Thanks,
 Dileepa

 --Pradeep


 On Thu, Dec 13, 2012 at 6:08 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 *importFeatureDef* instruction in carbon-p2-plugin is used to define
 dependencies to external features when developing a feature.
 We come across conflicts in feature installations when features have
 tight-dependencies to external features as* includedFeatures*.
 includedFeatureDef should be used to include sub-features (eg:to
 include server and ui features in the aggregate feature) and not to 
 include
 other external features.
 Included features are considered parts of the nesting feature and they
 are not allowed to be updated by P2.

 One example is :* org.wso2.carbon.service.mgt.server.feature*. It has
 included several external features as part of it, including
 org.wso2.carbon.security.mgt.server feature.
 So if the user needs to install a newer version of one of the nested
 features (eg: org.wso2.carbon.security.mgt.server feature), P2 doesn't
 allow it to update parts of a nested feature.

 So as a best practice when developing features; when a feature has a
 dependency to an external feature, it should be defined as an
 importFeatureDef.
 Then the feature installation is enforced by P2 and updates are
 supported

Re: [Dev] Properly use importFeatureDef to import external feature dependencies when developing Carbon Features

2013-01-02 Thread Dileepa Jayakody

Hi All,

I came across some more features in our platform which have included
external features instead of importing them as dependencies.
As explained above, these included features can cause P2 installation
version conflicts. We must fix these features to import their external
dependency features rather than including them, to avoid such conflicts in
future.

Following is the list of features which have included external features;

   - 
./mediation-initializer/org.wso2.carbon.mediation.initializer.server.feature/4.0.2/pom.xml:
   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.event.server.feature:4.0.2/includedFeatureDef


   - ./service-mgt/org.wso2.carbon.service.mgt.ui.feature/4.0.0/pom.xml:


   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.throttle.ui.feature/includedFeatureDef

   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.module.mgt.ui.feature:${project.version}/includedFeatureDef

   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.throttle.ui.feature:${project.parent.version}/includedFeatureDef

   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.caching.ui.feature:${project.parent.version}/includedFeatureDef

   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.rm.ui.feature:${project.parent.version}/includedFeatureDef

   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.security.mgt.ui.feature:${project.version}/includedFeatureDef


   - 
./stratos/common/org.wso2.carbon.stratos.common.server.feature/2.0.5/pom.xml:
   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.server.feature:4.0.3/includedFeatureDef


   - ./stratos/common/org.wso2.carbon.stratos.common.ui.feature/2.0.6/pom.xml:
   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature:4.0.6/includedFeatureDef


   - 
./data-services/data-services-tasks/org.wso2.carbon.dataservices.task.server.feature/4.0.5/pom.xml:
   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.ntask.core.feature:4.0.5/includedFeatureDef


   - ./identity/oauth/org.wso2.carbon.identity.oauth.ui.feature/4.0.5/pom.xml:

   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:4.0.5/includedFeatureDef


   - 
./identity/scim/org.wso2.carbon.identity.scim.provider.feature/4.0.5/pom.xml:
   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:4.0.5/includedFeatureDef


   - ./rss-manager/org.wso2.carbon.rssmanager.server.feature/4.0.1/pom.xml:
   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.service.mgt.server.feature:4.0.1


   - ./cg/org.wso2.carbon.cloud.gateway.feature/4.0.2/pom.xml:
   
includedFeatureDeforg.wso2.carbon:org.wso2.carbon.mediation.initializer.server.feature:4.0.2/includedFeatureDef

If there are no objections, and feature owners are agreeable to above
change, can we please fix these features in 4.0.6?

Thanks,
Dileepa

On Thu, Dec 13, 2012 at 7:38 PM, Dileepa Jayakody dile...@wso2.com wrote:



 On Thu, Dec 13, 2012 at 7:31 PM, Pradeep Fernando prad...@wso2.comwrote:

 May be you should make this a blog post, so that others can easily refer
 this. Good post!!

 Actually I have written one post on general guidelines for Feature
 developers :
 http://dileepajayakody.blogspot.com/2012/11/guidelines-for-carbon-feature-developers.html
 :)

 Thanks,
 Dileepa

 --Pradeep


 On Thu, Dec 13, 2012 at 6:08 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 *importFeatureDef* instruction in carbon-p2-plugin is used to define
 dependencies to external features when developing a feature.
 We come across conflicts in feature installations when features have
 tight-dependencies to external features as* includedFeatures*.
 includedFeatureDef should be used to include sub-features (eg:to include
 server and ui features in the aggregate feature) and not to include other
 external features.
 Included features are considered parts of the nesting feature and they
 are not allowed to be updated by P2.

 One example is :* org.wso2.carbon.service.mgt.server.feature*. It has
 included several external features as part of it, including
 org.wso2.carbon.security.mgt.server feature.
 So if the user needs to install a newer version of one of the nested
 features (eg: org.wso2.carbon.security.mgt.server feature), P2 doesn't
 allow it to update parts of a nested feature.

 So as a best practice when developing features; when a feature has a
 dependency to an external feature, it should be defined as an
 importFeatureDef.
 Then the feature installation is enforced by P2 and updates are
 supported at the time of installation.

 I have fixed the org.wso2.carbon.service.mgt.server feature: 4.0.5 for
 above reason, by importing external features. When importing external
 features we should also make sure the importedFeatures are published to the
 repository.

 Thanks,
 Dileepa


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

 Mobile : +94777-857616

Re: [Dev] Properly use importFeatureDef to import external feature dependencies when developing Carbon Features

2013-01-02 Thread Dileepa Jayakody

Hi AmilaM,

If they are not packed in 4.0.6 products, the fixes will not immediately
have their effect. But if they are published in the 4.0.6 p2-repo, then
they should be fixed.
I think if we fix the whole set of features, and use them in future
releases it will be easier :)
WDYT?

Thanks,
Dileepa


On Wed, Jan 2, 2013 at 6:30 PM, Amila Maha Arachchi ami...@wso2.com wrote:

 Hi Dileepa,

 If the products which packs these features are not released with 4.0.6, is
 it necessary to fix them also?


 Regards,
 AmilaM.


 On Wed, Jan 2, 2013 at 6:24 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Hi All,

 I came across some more features in our platform which have included
 external features instead of importing them as dependencies.
 As explained above, these included features can cause P2 installation
 version conflicts. We must fix these features to import their external
 dependency features rather than including them, to avoid such conflicts in
 future.

 Following is the list of features which have included external features;

- 
 ./mediation-initializer/org.wso2.carbon.mediation.initializer.server.feature/4.0.2/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.event.server.feature:4.0.2/includedFeatureDef


- ./service-mgt/org.wso2.carbon.service.mgt.ui.feature/4.0.0/pom.xml:



 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.throttle.ui.feature/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.module.mgt.ui.feature:${project.version}/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.throttle.ui.feature:${project.parent.version}/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.caching.ui.feature:${project.parent.version}/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.rm.ui.feature:${project.parent.version}/includedFeatureDef


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.security.mgt.ui.feature:${project.version}/includedFeatureDef


- 
 ./stratos/common/org.wso2.carbon.stratos.common.server.feature/2.0.5/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.server.feature:4.0.3/includedFeatureDef


- 
 ./stratos/common/org.wso2.carbon.stratos.common.ui.feature/2.0.6/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature:4.0.6/includedFeatureDef


- 
 ./data-services/data-services-tasks/org.wso2.carbon.dataservices.task.server.feature/4.0.5/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.ntask.core.feature:4.0.5/includedFeatureDef


- 
 ./identity/oauth/org.wso2.carbon.identity.oauth.ui.feature/4.0.5/pom.xml:


 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:4.0.5/includedFeatureDef


- 
 ./identity/scim/org.wso2.carbon.identity.scim.provider.feature/4.0.5/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:4.0.5/includedFeatureDef


- ./rss-manager/org.wso2.carbon.rssmanager.server.feature/4.0.1/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.service.mgt.server.feature:4.0.1


- ./cg/org.wso2.carbon.cloud.gateway.feature/4.0.2/pom.xml:

 includedFeatureDeforg.wso2.carbon:org.wso2.carbon.mediation.initializer.server.feature:4.0.2/includedFeatureDef

 If there are no objections, and feature owners are agreeable to above
 change, can we please fix these features in 4.0.6?

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 7:38 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Thu, Dec 13, 2012 at 7:31 PM, Pradeep Fernando prad...@wso2.comwrote:

 May be you should make this a blog post, so that others can easily
 refer this. Good post!!

 Actually I have written one post on general guidelines for Feature
 developers :
 http://dileepajayakody.blogspot.com/2012/11/guidelines-for-carbon-feature-developers.html
 :)

 Thanks,
 Dileepa

 --Pradeep


 On Thu, Dec 13, 2012 at 6:08 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 *importFeatureDef* instruction in carbon-p2-plugin is used to define
 dependencies to external features when developing a feature.
 We come across conflicts in feature installations when features have
 tight-dependencies to external features as* includedFeatures*.
 includedFeatureDef should be used to include sub-features (eg:to
 include server and ui features in the aggregate feature) and not to 
 include
 other external features.
 Included features are considered parts of the nesting feature and they
 are not allowed to be updated by P2.

 One example is :* org.wso2.carbon.service.mgt.server.feature*. It has
 included several external features as part of it, including
 org.wso2.carbon.security.mgt.server feature.
 So if the user needs to install a newer version of one of the nested
 features (eg: org.wso2.carbon.security.mgt.server feature), P2 doesn't
 allow it to update parts of a nested feature.

 So

[Dev] Can't install BAM Data Agents on top of AS 5.0.2

2012-12-15 Thread Dileepa Jayakody

Hi All,

Getting below error when trying to install BAM Data Agents category from
latest 4.0.5 p2-repo;

Your original install request has been modified.
org.wso2.carbon.databridge.datapublisher.feature.group-4.0.2 is already
installed, so an update will be performed instead.

Cannot complete the install because of a conflicting dependency. Software
being installed: WSO2 Carbon - *BAM Mediator Aggregate Feature 4.0.5
(org.wso2.carbon.mediator.bam.feature.group 4.0.5)* Software currently
installed: WSO2 Carbon - Event Server Feature 4.0.5
(org.wso2.carbon.event.server.feature.group 4.0.5) Only one of the
following can be installed at once: WSO2 Carbon - Event Server Feature
4.0.2 (org.wso2.carbon.event.server.feature.jar 4.0.2) WSO2 Carbon - Event
Server Feature 4.0.5 (org.wso2.carbon.event.server.feature.jar 4.0.5)
Cannot satisfy dependency: From: WSO2 Carbon - Event Server Feature 4.0.2
(org.wso2.carbon.event.server.feature.group 4.0.2) To:
org.wso2.carbon.event.server.feature.jar [4.0.2] Cannot satisfy dependency:
From: WSO2 Carbon - Event Server Feature 4.0.5
(org.wso2.carbon.event.server.feature.group 4.0.5) To:
org.wso2.carbon.event.server.feature.jar [4.0.5] Cannot satisfy dependency:
From: WSO2 Carbon - Mediation Initializer Server Feature 4.0.2
(org.wso2.carbon.mediation.initializer.server.feature.group 4.0.2) To:
org.wso2.carbon.event.server.feature.group [4.0.2] Cannot satisfy
dependency: From: WSO2 Carbon - BAM Mediator Aggregate Feature 4.0.5
(org.wso2.carbon.mediator.bam.feature.group 4.0.5) To:
org.wso2.carbon.mediator.bam.server.feature.group [4.0.5] Cannot satisfy
dependency: From: WSO2 Carbon - BAM Mediator Feature 4.0.5
(org.wso2.carbon.mediator.bam.server.feature.group 4.0.5) To:
org.wso2.carbon.mediation.initializer.server.feature.group [4.0.0,4.1.0)

In summary;

The root cause here again is features including external features as a
nested part of it instead of properly* importing external features*.
In org.wso2.carbon.mediator.bam.server.feature 4.0.5 it has a dependency to
org.wso2.carbon.mediation.initializer.server.feature:4.0.2.

In org.wso2.carbon.mediation.initializer.server.feature:4.0.2, the
event.server.feature:4.0.2 is included instead of being imported. Hence the
above conflict in installation as AS 5.0.2 has event.server.feature:4.0.5
already installed and doesn't allow it's lower versioned (4.0.2) get
installed as part of
org.wso2.carbon.mediation.initializer.server.feature:4.0.2

If we are to fix this need to update mediation.initializer.server.feature
to properly import the server.feature. How to proceed with this?

Thanks,
Dileepa

-- 
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] Can't install BAM Data Agents on top of AS 5.0.2

2012-12-15 Thread Dileepa Jayakody

On Sat, Dec 15, 2012 at 3:57 PM, Buddhika Chamith buddhi...@wso2.comwrote:

 There is no much point in installing BAM mediator feature on top of AS
 since this is specific for ESB. Having said that the issue is some thing
 that needs to be fixed if possible.

 This is not only specific to BAM mediator installation.
mediation.initializer.server feature is going with many other features. So
same conflicts can occur when trying to install those features which have
dependency to mediation.initializer feature.

The same problem is there with *identity.oauth.ui.*feature where it has
external dependency features like webapp.mgt.server,
jaxws.webapp.mgt.server included as part of it and not properly imported.
These cause conflicts when installing features where P2 doesn't allow to
update parts of features to newer versions. If every product is updated to
use the same versions of features, this problem may not occur. However,
some of our products are using older/newer versions of such conflicting
features which are published in the p2-repo, hence this problem. Also some
of the product categories in the p2-repo are still not updated to latest
feature versions.

If we are to fix this, need to change every conflicting features like
identity.oauth.ui, mediation.initializer.server features to properly define
feature imports to external dependencies.
Changing these features can cause some product p2-profiles to break if they
are not updated accordingly. We also have to make sure features and
feature-categories in the p2-repo are updated to latest versions.
How can we proceed with this?

Thanks,
Dileepa

Regards
 Buddhika

 On Sat, Dec 15, 2012 at 1:56 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 Getting below error when trying to install BAM Data Agents category from
 latest 4.0.5 p2-repo;

 Your original install request has been modified.
 org.wso2.carbon.databridge.datapublisher.feature.group-4.0.2 is already
 installed, so an update will be performed instead.

 Cannot complete the install because of a conflicting dependency. Software
 being installed: WSO2 Carbon - *BAM Mediator Aggregate Feature 4.0.5
 (org.wso2.carbon.mediator.bam.feature.group 4.0.5)* Software currently
 installed: WSO2 Carbon - Event Server Feature 4.0.5
 (org.wso2.carbon.event.server.feature.group 4.0.5) Only one of the
 following can be installed at once: WSO2 Carbon - Event Server Feature
 4.0.2 (org.wso2.carbon.event.server.feature.jar 4.0.2) WSO2 Carbon - Event
 Server Feature 4.0.5 (org.wso2.carbon.event.server.feature.jar 4.0.5)
 Cannot satisfy dependency: From: WSO2 Carbon - Event Server Feature 4.0.2
 (org.wso2.carbon.event.server.feature.group 4.0.2) To:
 org.wso2.carbon.event.server.feature.jar [4.0.2] Cannot satisfy dependency:
 From: WSO2 Carbon - Event Server Feature 4.0.5
 (org.wso2.carbon.event.server.feature.group 4.0.5) To:
 org.wso2.carbon.event.server.feature.jar [4.0.5] Cannot satisfy dependency:
 From: WSO2 Carbon - Mediation Initializer Server Feature 4.0.2
 (org.wso2.carbon.mediation.initializer.server.feature.group 4.0.2) To:
 org.wso2.carbon.event.server.feature.group [4.0.2] Cannot satisfy
 dependency: From: WSO2 Carbon - BAM Mediator Aggregate Feature 4.0.5
 (org.wso2.carbon.mediator.bam.feature.group 4.0.5) To:
 org.wso2.carbon.mediator.bam.server.feature.group [4.0.5] Cannot satisfy
 dependency: From: WSO2 Carbon - BAM Mediator Feature 4.0.5
 (org.wso2.carbon.mediator.bam.server.feature.group 4.0.5) To:
 org.wso2.carbon.mediation.initializer.server.feature.group [4.0.0,4.1.0)

 In summary;

 The root cause here again is features including external features as a
 nested part of it instead of properly* importing external features*.
 In org.wso2.carbon.mediator.bam.server.feature 4.0.5 it has a dependency
 to org.wso2.carbon.mediation.initializer.server.feature:4.0.2.

 In org.wso2.carbon.mediation.initializer.server.feature:4.0.2, the
 event.server.feature:4.0.2 is included instead of being imported. Hence the
 above conflict in installation as AS 5.0.2 has event.server.feature:4.0.5
 already installed and doesn't allow it's lower versioned (4.0.2) get
 installed as part of
 org.wso2.carbon.mediation.initializer.server.feature:4.0.2

 If we are to fix this need to update mediation.initializer.server.feature
 to properly import the server.feature. How to proceed with this?

 Thanks,
 Dileepa

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





-- 
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] Kernel test failures in PersistenceManagerTest

2012-12-14 Thread Dileepa Jayakody

Created a jira to fix the test: https://wso2.org/jira/browse/CARBON-14031
I'll exclude the 2 failing unit tests in carbon.core for the timebeing.

On Fri, Dec 14, 2012 at 2:55 PM, Dileepa Jayakody dile...@wso2.com wrote:



 On Fri, Dec 14, 2012 at 2:39 PM, Muhammed Shariq sha...@wso2.com wrote:



 On Fri, Dec 14, 2012 at 9:18 AM, Dileepa Jayakody dile...@wso2.comwrote:



 On Fri, Dec 14, 2012 at 7:32 AM, Muhammed Shariq sha...@wso2.comwrote:

 On Fri, Dec 14, 2012 at 7:26 AM, Pradeep Fernando prad...@wso2.comwrote:

 what if we write the test only using CarbonContext and
 PrivilegedCarbonContext. ?

 - getting CarbonContextDataHolder is not possible

 I think we should be able to start a tenant flow use CC ?!


 - getting registry service is wrong within a unit test

 Yup .. we cannot do this .. wonder if there is a way to get a dummy
 registry instance .. ?!



 *carbonContextDataHolder.getConfigSystemRegistry();* - we should be
 able to do the same thing using the new apis.

 I think it is somewhat similar to,
 cc.getRegistry(registryType);
 you have to populate CC before doing this, as the method call takes
 tenant info from the CC. Just a thought, didnt go through the code or
 tested it.

 Actually the issue is although we populate CC by setting registry
 instances in the test setups, the test methods use a *
 ServiceGroupPersistenceManage*r instance like:
 pf.getServiceGroupPM().handleNewServiceGroupAddition(asvGroup);

 And when initializing ServiceGroupPersistenceManager instance, in the
 constructor it's configRegistry instance is again initialized  using CC's
 getRegistry() method which is now re-factored to return using
 RegistryService.

 protected AbstractPersistenceManager(AxisConfiguration axisConfig)
 throws AxisFault {
 this.axisConfig = axisConfig;
 try {
 configRegistry =
 (Registry)
 PrivilegedCarbonContext.getCurrentContext(axisConfig).  //needed for
 TransportPM

 getRegistry(RegistryType.SYSTEM_CONFIGURATION);
 } catch (Exception e) {
 log.error(Error while retrieving config registry from Axis
 configuration, e);
 }
 if (configRegistry == null) {
 throw new AxisFault(Configuration Registry is not
 available);
 }
 }

 Since the returned RegistryService is null, PersistenceManager object
 fails to initialize and returns null in the test logic. At the moment there
 is no method to setRegistry explicitly to PersistenceManager instance.

 Thoughts on a possible work-around for this?


 Initially before my fix CC was blindly returning the ST registry, so I
 dont think we can revert that fix.. So basically it seems like this unit
 test is invalid .. A better place for this test case would be integration
 test phase, cz the server starts up .. Lets remove it from the unit tests
 .. ?!


 +1.

 Thanks,
 Dileepa


  --Pradeep






 On Fri, Dec 14, 2012 at 1:08 AM, Dileepa Jayakody dile...@wso2.comwrote:

 In CC the registry is now retrieved using registryService from
 OSGIDataHolder like below;
  eg:
 if (tenantId != MultitenantConstants.INVALID_TENANT_ID) {
  registry = *
 dataHolder.getRegistryService().getConfigSystemRegistry(tenantId);*
  setRegistry(RegistryType.SYSTEM_CONFIGURATION,
 registry);
  return registry;
}
 In carbon.4.0.4 and before, it merely returned the registry from
 carbonContextDataHolder as below;
 *return carbonContextDataHolder.getConfigSystemRegistry();*

 So in the unitsTests when trying to acces registryService in current
 CC implementation, it fails as there is no OSGi registry service 
 available
 during the unit test life-cycle.
 Any idea on how to fix the unitTests here?

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 7:43 PM, Dileepa Jayakody 
 dile...@wso2.comwrote:



 On Thu, Dec 13, 2012 at 7:28 PM, Pradeep Fernando 
 prad...@wso2.comwrote:

 Hi Dileepa,

 im still getting the error in my c5-scratch. shariqs
 configSystemRegistry null fix is present in the code.

 Yes, I get it in C5 scratch locally. working on it.

  T E S T S
 ---
 Running
 org.wso2.carbon.core.test.security.AuthenticatorsConfigurationTest
 log4j:WARN No appenders could be found for logger
 (org.apache.axiom.om.util.StAXUtils).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
 0.209 sec
 Running org.wso2.carbon.core.test.persistence.PersistenceUtilsTest
 log4j:WARN No appenders could be found for logger
 (org.wso2.carbon.context.internal.CarbonContextDataHolder).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed:
 2.423 sec  FAILURE!
 Running org.wso2.carbon.core.test.persistence.PersistenceManagerTest
 log4j:WARN No appenders could be found for logger
 (org.wso2.carbon.context.internal.CarbonContextDataHolder).
 log4j:WARN

Re: [Dev] [G-Reg 4.5.3]Can't remove selected UI features through feature manager.

2012-12-14 Thread Dileepa Jayakody

Created a jira for this : https://wso2.org/jira/browse/CARBON-14032

On Fri, Dec 14, 2012 at 7:14 PM, Pradeep Fernando prad...@wso2.com wrote:

 we never had that functionality ajith. We are working on a  solution
 though.

 --Pradeep


 On Fri, Dec 14, 2012 at 11:56 AM, Ajith Vitharana aji...@wso2.com wrote:


 Hi Dileepa,

 I'm trying to do the $subject, but it doesn't allow to select UI bundles.
 Please see the attached image.

 Thanks
 Ajith

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



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




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




-- 
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] Properly use importFeatureDef to import external feature dependencies when developing Carbon Features

2012-12-13 Thread Dileepa Jayakody

Hi All,

*importFeatureDef* instruction in carbon-p2-plugin is used to define
dependencies to external features when developing a feature.
We come across conflicts in feature installations when features have
tight-dependencies to external features as* includedFeatures*.
includedFeatureDef should be used to include sub-features (eg:to include
server and ui features in the aggregate feature) and not to include other
external features.
Included features are considered parts of the nesting feature and they are
not allowed to be updated by P2.

One example is :* org.wso2.carbon.service.mgt.server.feature*. It has
included several external features as part of it, including
org.wso2.carbon.security.mgt.server feature.
So if the user needs to install a newer version of one of the nested
features (eg: org.wso2.carbon.security.mgt.server feature), P2 doesn't
allow it to update parts of a nested feature.

So as a best practice when developing features; when a feature has a
dependency to an external feature, it should be defined as an
importFeatureDef.
Then the feature installation is enforced by P2 and updates are supported
at the time of installation.

I have fixed the org.wso2.carbon.service.mgt.server feature: 4.0.5 for
above reason, by importing external features. When importing external
features we should also make sure the importedFeatures are published to the
repository.

Thanks,
Dileepa


-- 
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] Kernel test failures in PersistenceManagerTest

2012-12-13 Thread Dileepa Jayakody

On Thu, Dec 13, 2012 at 6:15 PM, Muhammed Shariq sha...@wso2.com wrote:

 Hi Dileepa,

 This test is still failing in builder3
 Looking into it.

 On Thu, Dec 13, 2012 at 12:09 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Yes Krishantha I committed the changes to carbon.core 4.0.5 in r151291.
 Could it be because bamboo source not updated to latest for the last
 build?

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 11:39 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Dileepa,

 Last bamboo kernel build[1] also failed due to following failures. Did
 you commit the fixes to branch?

 build 12-Dec-2012 21:00:49 Tests in error:

 build   12-Dec-2012 21:00:49  
 testNewServiceGroupAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testSetServiceGroupProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testNewServiceAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testServiceProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testUpdateServiceGroupParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testUpdateServiceParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testNewModuleAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testNewModuleNullVersionAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testModuleParameterUpdate(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testDeleteService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testRemoveServiceParam(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testDeleteServiceGroup(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testRemoveModule(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testengageModuleForService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build   12-Dec-2012 21:00:49  
 testGetResourcePath1(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)
 build   12-Dec-2012 21:00:49  
 testGetResourcePath3(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)
 build   12-Dec-2012 21:00:49
 build   12-Dec-2012 21:00:49Tests run: 23, Failures: 0, Errors: 16, 
 Skipped: 0
 build   12-Dec-2012 21:00:49

 Thanks,
 Krishantha

 [1]
 http://wso2.org/bamboo/download/WCB001-KER005-JOB1/build_logs/WCB001-KER005-JOB1-54.log

  On Wed, Dec 12, 2012 at 1:40 PM, Dileepa Jayakody dile...@wso2.comwrote:

 fixed in 151291, by initializing super-tenant flow for
 PersistenceUtilsTest and PersistenceManagerTest.

 The reason the tests were failing was, tenantId is not initialized (-1)
 when Registry instance is created from CarbonContext.getRegistry(). Now the
 tenantId is set to superTenantID in the test's setup flow.

 Thanks,
 Dileepa


 On Tue, Dec 11, 2012 at 10:27 AM, Dileepa Jayakody dile...@wso2.comwrote:

 I will look into this


 On Tue, Dec 11, 2012 at 10:17 AM, Muhammed Shariq sha...@wso2.comwrote:

 Hi,

 We need to get this test passing ASAP .. can someone have a look
 please ?!

 On Mon, Dec 10, 2012 at 11:19 AM, Dinusha Senanayaka 
 dinu...@wso2.com wrote:

 Build ran with the r150786. Surefire reports are attached herewith..

 Regards,
 Dinusha.

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




 --
 Thanks,
 Shariq.
 Phone: +94 777 202 225




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





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

 Mobile : +94777-857616




 --
 Thanks,
 Shariq.
 Phone: +94 777 202 225




-- 
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] Kernel test failures in PersistenceManagerTest

2012-12-13 Thread Dileepa Jayakody

There was a problem in CC registry returning logic where it's always
returning null regardless of the tenantID.
Since that issue is now fixed, the tests should be passing.

Thanks,
Dileepa

On Thu, Dec 13, 2012 at 6:22 PM, Dileepa Jayakody dile...@wso2.com wrote:



 On Thu, Dec 13, 2012 at 6:15 PM, Muhammed Shariq sha...@wso2.com wrote:

 Hi Dileepa,

 This test is still failing in builder3
 Looking into it.

 On Thu, Dec 13, 2012 at 12:09 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Yes Krishantha I committed the changes to carbon.core 4.0.5 in r151291.
 Could it be because bamboo source not updated to latest for the last
 build?

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 11:39 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Dileepa,

 Last bamboo kernel build[1] also failed due to following failures. Did
 you commit the fixes to branch?

 build 12-Dec-2012 21:00:49 Tests in error:

 build  12-Dec-2012 21:00:49  
 testNewServiceGroupAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testSetServiceGroupProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testNewServiceAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testServiceProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testUpdateServiceGroupParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testUpdateServiceParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testNewModuleAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testNewModuleNullVersionAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testModuleParameterUpdate(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testDeleteService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testRemoveServiceParam(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testDeleteServiceGroup(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testRemoveModule(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testengageModuleForService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build  12-Dec-2012 21:00:49  
 testGetResourcePath1(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)
 build  12-Dec-2012 21:00:49  
 testGetResourcePath3(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)
 build  12-Dec-2012 21:00:49
 build  12-Dec-2012 21:00:49Tests run: 23, Failures: 0, Errors: 16, 
 Skipped: 0
 build  12-Dec-2012 21:00:49

 Thanks,
 Krishantha

 [1]
 http://wso2.org/bamboo/download/WCB001-KER005-JOB1/build_logs/WCB001-KER005-JOB1-54.log

  On Wed, Dec 12, 2012 at 1:40 PM, Dileepa Jayakody dile...@wso2.comwrote:

 fixed in 151291, by initializing super-tenant flow for
 PersistenceUtilsTest and PersistenceManagerTest.

 The reason the tests were failing was, tenantId is not initialized
 (-1) when Registry instance is created from CarbonContext.getRegistry().
 Now the tenantId is set to superTenantID in the test's setup flow.

 Thanks,
 Dileepa


 On Tue, Dec 11, 2012 at 10:27 AM, Dileepa Jayakody 
 dile...@wso2.comwrote:

 I will look into this


 On Tue, Dec 11, 2012 at 10:17 AM, Muhammed Shariq sha...@wso2.comwrote:

 Hi,

 We need to get this test passing ASAP .. can someone have a look
 please ?!

 On Mon, Dec 10, 2012 at 11:19 AM, Dinusha Senanayaka 
 dinu...@wso2.com wrote:

 Build ran with the r150786. Surefire reports are attached herewith..

 Regards,
 Dinusha.

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




 --
 Thanks,
 Shariq.
 Phone: +94 777 202 225




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





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

 Mobile : +94777-857616




 --
 Thanks,
 Shariq.
 Phone: +94 777 202 225




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

 Mobile : +94777-857616




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

Mobile : +94777-857616

Re: [Dev] Properly use importFeatureDef to import external feature dependencies when developing Carbon Features

2012-12-13 Thread Dileepa Jayakody

On Thu, Dec 13, 2012 at 7:31 PM, Pradeep Fernando prad...@wso2.com wrote:

 May be you should make this a blog post, so that others can easily refer
 this. Good post!!

 Actually I have written one post on general guidelines for Feature
developers :
http://dileepajayakody.blogspot.com/2012/11/guidelines-for-carbon-feature-developers.html
:)

Thanks,
Dileepa

 --Pradeep


 On Thu, Dec 13, 2012 at 6:08 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 *importFeatureDef* instruction in carbon-p2-plugin is used to define
 dependencies to external features when developing a feature.
 We come across conflicts in feature installations when features have
 tight-dependencies to external features as* includedFeatures*.
 includedFeatureDef should be used to include sub-features (eg:to include
 server and ui features in the aggregate feature) and not to include other
 external features.
 Included features are considered parts of the nesting feature and they
 are not allowed to be updated by P2.

 One example is :* org.wso2.carbon.service.mgt.server.feature*. It has
 included several external features as part of it, including
 org.wso2.carbon.security.mgt.server feature.
 So if the user needs to install a newer version of one of the nested
 features (eg: org.wso2.carbon.security.mgt.server feature), P2 doesn't
 allow it to update parts of a nested feature.

 So as a best practice when developing features; when a feature has a
 dependency to an external feature, it should be defined as an
 importFeatureDef.
 Then the feature installation is enforced by P2 and updates are supported
 at the time of installation.

 I have fixed the org.wso2.carbon.service.mgt.server feature: 4.0.5 for
 above reason, by importing external features. When importing external
 features we should also make sure the importedFeatures are published to the
 repository.

 Thanks,
 Dileepa


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




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




-- 
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] Kernel test failures in PersistenceManagerTest

2012-12-13 Thread Dileepa Jayakody

On Thu, Dec 13, 2012 at 7:28 PM, Pradeep Fernando prad...@wso2.com wrote:

 Hi Dileepa,

 im still getting the error in my c5-scratch. shariqs configSystemRegistry
 null fix is present in the code.

 Yes, I get it in C5 scratch locally. working on it.

  T E S T S
 ---
 Running org.wso2.carbon.core.test.security.AuthenticatorsConfigurationTest
 log4j:WARN No appenders could be found for logger
 (org.apache.axiom.om.util.StAXUtils).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.209 sec
 Running org.wso2.carbon.core.test.persistence.PersistenceUtilsTest
 log4j:WARN No appenders could be found for logger
 (org.wso2.carbon.context.internal.CarbonContextDataHolder).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.423 sec
  FAILURE!
 Running org.wso2.carbon.core.test.persistence.PersistenceManagerTest
 log4j:WARN No appenders could be found for logger
 (org.wso2.carbon.context.internal.CarbonContextDataHolder).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 14, Failures: 0, Errors: 14, Skipped: 0, Time elapsed: 2.758
 sec  FAILURE!
 Running org.wso2.carbon.core.test.persistence.ParameterUtilTest
 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.12 sec
 Running org.wso2.carbon.core.test.config.CarbonAxisConfiguratorTest
 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec

 Results :

 Tests in error:

 testGetResourcePath1(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)

 testGetResourcePath3(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)

 testNewServiceGroupAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testSetServiceGroupProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testNewServiceAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testServiceProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testUpdateServiceGroupParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testUpdateServiceParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testNewModuleAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testNewModuleNullVersionAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testModuleParameterUpdate(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testDeleteService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testRemoveServiceParam(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testDeleteServiceGroup(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testRemoveModule(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testengageModuleForService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)


 Tests run: 23, Failures: 0, Errors: 16, Skipped: 0


 On Thu, Dec 13, 2012 at 6:54 PM, Dileepa Jayakody dile...@wso2.comwrote:

 There was a problem in CC registry returning logic where it's always
 returning null regardless of the tenantID.
 Since that issue is now fixed, the tests should be passing.

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 6:22 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Thu, Dec 13, 2012 at 6:15 PM, Muhammed Shariq sha...@wso2.comwrote:

  Hi Dileepa,

 This test is still failing in builder3
 Looking into it.

 On Thu, Dec 13, 2012 at 12:09 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Yes Krishantha I committed the changes to carbon.core 4.0.5 in
 r151291.
 Could it be because bamboo source not updated to latest for the last
 build?

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 11:39 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Dileepa,

 Last bamboo kernel build[1] also failed due to following failures.
 Did you commit the fixes to branch?

 build 12-Dec-2012 21:00:49 Tests in error:

 build12-Dec-2012 21:00:49  
 testNewServiceGroupAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build12-Dec-2012 21:00:49  
 testSetServiceGroupProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build12-Dec-2012 21:00:49  
 testNewServiceAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build12-Dec-2012 21:00:49  
 testServiceProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build12-Dec-2012 21:00:49  
 testUpdateServiceGroupParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build12-Dec-2012 21:00:49  
 testUpdateServiceParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build12-Dec-2012 21:00:49  
 testNewModuleAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build12-Dec-2012 21:00:49  
 testNewModuleNullVersionAddition

Re: [Dev] GReg P2 profile gen build failure due to org.wso2.carbon.service.mgt.server.feature

2012-12-13 Thread Dileepa Jayakody

Sorry missed the .feature parts of the given featureArtifactDefs.
@Product teams who use service.mgt.server.feature in their p2-profiles,
please ensure below set of features are added in your product's p2-profile
pom, under p2-repo-gen phase.

featureArtifactDeforg.wso2.carbon:org.wso2.carbon.security.mgt.server.feature:4.0.5/featureArtifactDef
featureArtifactDeforg.wso2.carbon:org.wso2.carbon.module.mgt.server.feature:4.0.2/featureArtifactDef
featureArtifactDeforg.wso2.carbon:org.wso2.carbon.throttle.server.feature:4.0.2/featureArtifactDef
featureArtifactDeforg.wso2.carbon:org.wso2.carbon.caching.server.feature:4.0.2/featureArtifactDef
featureArtifactDeforg.wso2.carbon:org.wso2.carbon.rm.server.feature:4.0.0/featureArtifactDef

On Thu, Dec 13, 2012 at 9:59 PM, Dileepa Jayakody dile...@wso2.com wrote:

Yes, we had to incorporate this change to make sure it doesn't break the
p2-installations when need arises to update certain features included in
nested features.
To fix the product-build failures in p2-profile-gens

please ensure that below list of featureArtifactDefs are added under
p2-repo-gen phase in the product's profile-gen pom.xml. These are the
features which were included inside service.mgt.server feature earlier. Now
since it is importing, these features should be published in *p2-repo-gen*for
the product.

featureArtifactDeforg.wso2.carbon:org.wso2.carbon.security.mgt.server:4.0.5/featureArtifactDef

featureArtifactDeforg.wso2.carbon:org.wso2.carbon.module.mgt.server:4.0.2/featureArtifactDef

featureArtifactDeforg.wso2.carbon:org.wso2.carbon.throttle.server:4.0.2/featureArtifactDef

featureArtifactDeforg.wso2.carbon:org.wso2.carbon.caching.server:4.0.2/featureArtifactDef

featureArtifactDeforg.wso2.carbon:org.wso2.carbon.rm.server:4.0.0/featureArtifactDef

Sorry for the inconvenience caused.

On Thu, Dec 13, 2012 at 9:35 PM, Pradeep Fernando prad...@wso2.comwrote:

Hi,

Its true that this is not the time to make changes to the build. However,
this particular bug needs to be fixed. Service-mgt and security features
are heavily used across many products. Because of the wrong feature
definitions it causes errors during feature installation and we are kind
stuck once that happens.

So, bettter to incoperate this change rather than ignoring it. Dileepa
please provide the instruction to be followed by the product teams.

adding security-mgt feature in to the repo-gen goal should do,

thanks,
--Pradeep

--
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] Kernel test failures in PersistenceManagerTest

2012-12-13 Thread Dileepa Jayakody

In CC the registry is now retrieved using registryService from
OSGIDataHolder like below;
 eg:
if (tenantId != MultitenantConstants.INVALID_TENANT_ID) {
 registry = *
dataHolder.getRegistryService().getConfigSystemRegistry(tenantId);*
 setRegistry(RegistryType.SYSTEM_CONFIGURATION, registry);
 return registry;
   }
In carbon.4.0.4 and before, it merely returned the registry from
carbonContextDataHolder as below;
*return carbonContextDataHolder.getConfigSystemRegistry();*

So in the unitsTests when trying to acces registryService in current CC
implementation, it fails as there is no OSGi registry service available
during the unit test life-cycle.
Any idea on how to fix the unitTests here?

Thanks,
Dileepa

On Thu, Dec 13, 2012 at 7:43 PM, Dileepa Jayakody dile...@wso2.com wrote:



 On Thu, Dec 13, 2012 at 7:28 PM, Pradeep Fernando prad...@wso2.comwrote:

 Hi Dileepa,

 im still getting the error in my c5-scratch. shariqs configSystemRegistry
 null fix is present in the code.

 Yes, I get it in C5 scratch locally. working on it.

  T E S T S
 ---
 Running org.wso2.carbon.core.test.security.AuthenticatorsConfigurationTest
 log4j:WARN No appenders could be found for logger
 (org.apache.axiom.om.util.StAXUtils).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.209 sec
 Running org.wso2.carbon.core.test.persistence.PersistenceUtilsTest
 log4j:WARN No appenders could be found for logger
 (org.wso2.carbon.context.internal.CarbonContextDataHolder).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.423 sec
  FAILURE!
 Running org.wso2.carbon.core.test.persistence.PersistenceManagerTest
 log4j:WARN No appenders could be found for logger
 (org.wso2.carbon.context.internal.CarbonContextDataHolder).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 14, Failures: 0, Errors: 14, Skipped: 0, Time elapsed: 2.758
 sec  FAILURE!
 Running org.wso2.carbon.core.test.persistence.ParameterUtilTest
 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.12 sec
 Running org.wso2.carbon.core.test.config.CarbonAxisConfiguratorTest
 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec

 Results :

 Tests in error:

 testGetResourcePath1(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)

 testGetResourcePath3(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)

 testNewServiceGroupAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testSetServiceGroupProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testNewServiceAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testServiceProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testUpdateServiceGroupParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testUpdateServiceParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testNewModuleAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testNewModuleNullVersionAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testModuleParameterUpdate(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testDeleteService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testRemoveServiceParam(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testDeleteServiceGroup(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testRemoveModule(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)

 testengageModuleForService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)


 Tests run: 23, Failures: 0, Errors: 16, Skipped: 0


 On Thu, Dec 13, 2012 at 6:54 PM, Dileepa Jayakody dile...@wso2.comwrote:

 There was a problem in CC registry returning logic where it's always
 returning null regardless of the tenantID.
 Since that issue is now fixed, the tests should be passing.

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 6:22 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Thu, Dec 13, 2012 at 6:15 PM, Muhammed Shariq sha...@wso2.comwrote:

  Hi Dileepa,

 This test is still failing in builder3
 Looking into it.

 On Thu, Dec 13, 2012 at 12:09 PM, Dileepa Jayakody 
 dile...@wso2.comwrote:

 Yes Krishantha I committed the changes to carbon.core 4.0.5 in
 r151291.
 Could it be because bamboo source not updated to latest for the last
 build?

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 11:39 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Dileepa,

 Last bamboo kernel build[1] also failed due to following failures.
 Did you commit the fixes to branch?

 build 12-Dec-2012 21:00:49 Tests in error:

 build   12-Dec-2012 21:00:49  
 testNewServiceGroupAddition(org.wso2

Re: [Dev] Kernel test failures in PersistenceManagerTest

2012-12-13 Thread Dileepa Jayakody

On Fri, Dec 14, 2012 at 7:32 AM, Muhammed Shariq sha...@wso2.com wrote:

 On Fri, Dec 14, 2012 at 7:26 AM, Pradeep Fernando prad...@wso2.comwrote:

 what if we write the test only using CarbonContext and
 PrivilegedCarbonContext. ?

 - getting CarbonContextDataHolder is not possible

 I think we should be able to start a tenant flow use CC ?!


 - getting registry service is wrong within a unit test

 Yup .. we cannot do this .. wonder if there is a way to get a dummy
 registry instance .. ?!



 *carbonContextDataHolder.getConfigSystemRegistry();* - we should be
 able to do the same thing using the new apis.

 I think it is somewhat similar to,
 cc.getRegistry(registryType);
 you have to populate CC before doing this, as the method call takes
 tenant info from the CC. Just a thought, didnt go through the code or
 tested it.

 Actually the issue is although we populate CC by setting registry
instances in the test setups, the test methods use a *
ServiceGroupPersistenceManage*r instance like:
pf.getServiceGroupPM().handleNewServiceGroupAddition(asvGroup);

And when initializing ServiceGroupPersistenceManager instance, in the
constructor it's configRegistry instance is again initialized  using CC's
getRegistry() method which is now re-factored to return using
RegistryService.

protected AbstractPersistenceManager(AxisConfiguration axisConfig) throws
AxisFault {
this.axisConfig = axisConfig;
try {
configRegistry =
(Registry)
PrivilegedCarbonContext.getCurrentContext(axisConfig).  //needed for
TransportPM
getRegistry(RegistryType.SYSTEM_CONFIGURATION);
} catch (Exception e) {
log.error(Error while retrieving config registry from Axis
configuration, e);
}
if (configRegistry == null) {
throw new AxisFault(Configuration Registry is not available);
}
}

Since the returned RegistryService is null, PersistenceManager object fails
to initialize and returns null in the test logic. At the moment there is no
method to setRegistry explicitly to PersistenceManager instance.

Thoughts on a possible work-around for this?

Thanks,
Dileepa


 --Pradeep






 On Fri, Dec 14, 2012 at 1:08 AM, Dileepa Jayakody dile...@wso2.comwrote:

 In CC the registry is now retrieved using registryService from
 OSGIDataHolder like below;
  eg:
 if (tenantId != MultitenantConstants.INVALID_TENANT_ID) {
  registry = *
 dataHolder.getRegistryService().getConfigSystemRegistry(tenantId);*
  setRegistry(RegistryType.SYSTEM_CONFIGURATION,
 registry);
  return registry;
}
 In carbon.4.0.4 and before, it merely returned the registry from
 carbonContextDataHolder as below;
 *return carbonContextDataHolder.getConfigSystemRegistry();*

 So in the unitsTests when trying to acces registryService in current CC
 implementation, it fails as there is no OSGi registry service available
 during the unit test life-cycle.
 Any idea on how to fix the unitTests here?

 Thanks,
 Dileepa


 On Thu, Dec 13, 2012 at 7:43 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Thu, Dec 13, 2012 at 7:28 PM, Pradeep Fernando prad...@wso2.comwrote:

 Hi Dileepa,

 im still getting the error in my c5-scratch. shariqs
 configSystemRegistry null fix is present in the code.

 Yes, I get it in C5 scratch locally. working on it.

  T E S T S
 ---
 Running
 org.wso2.carbon.core.test.security.AuthenticatorsConfigurationTest
 log4j:WARN No appenders could be found for logger
 (org.apache.axiom.om.util.StAXUtils).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.209
 sec
 Running org.wso2.carbon.core.test.persistence.PersistenceUtilsTest
 log4j:WARN No appenders could be found for logger
 (org.wso2.carbon.context.internal.CarbonContextDataHolder).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.423
 sec  FAILURE!
 Running org.wso2.carbon.core.test.persistence.PersistenceManagerTest
 log4j:WARN No appenders could be found for logger
 (org.wso2.carbon.context.internal.CarbonContextDataHolder).
 log4j:WARN Please initialize the log4j system properly.
 Tests run: 14, Failures: 0, Errors: 14, Skipped: 0, Time elapsed:
 2.758 sec  FAILURE!
 Running org.wso2.carbon.core.test.persistence.ParameterUtilTest
 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.12
 sec
 Running org.wso2.carbon.core.test.config.CarbonAxisConfiguratorTest
 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012
 sec

 Results :

 Tests in error:

 testGetResourcePath1(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)

 testGetResourcePath3(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)

 testNewServiceGroupAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest

Re: [Dev] Kernel test failures in PersistenceManagerTest

2012-12-12 Thread Dileepa Jayakody

fixed in 151291, by initializing super-tenant flow for PersistenceUtilsTest
and PersistenceManagerTest.

The reason the tests were failing was, tenantId is not initialized (-1)
when Registry instance is created from CarbonContext.getRegistry(). Now the
tenantId is set to superTenantID in the test's setup flow.

Thanks,
Dileepa

On Tue, Dec 11, 2012 at 10:27 AM, Dileepa Jayakody dile...@wso2.com wrote:

 I will look into this


 On Tue, Dec 11, 2012 at 10:17 AM, Muhammed Shariq sha...@wso2.com wrote:

 Hi,

 We need to get this test passing ASAP .. can someone have a look please ?!

 On Mon, Dec 10, 2012 at 11:19 AM, Dinusha Senanayaka dinu...@wso2.comwrote:

 Build ran with the r150786. Surefire reports are attached herewith..

 Regards,
 Dinusha.

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




 --
 Thanks,
 Shariq.
 Phone: +94 777 202 225




 --
 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] [Commits] [Carbon-kernel] svn commit r151291 - carbon/kernel/branches/4.0.0/core/org.wso2.carbon.core/4.0.5/src/test/java/org/wso2/carbon/core/test/persistence

2012-12-12 Thread Dileepa Jayakody

/mailman/listinfo/commits




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

 blog: http://pradeepfernando.blogspot.com
 m: +94776603662




-- 
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] Kernel test failures in PersistenceManagerTest

2012-12-12 Thread Dileepa Jayakody

Yes Krishantha I committed the changes to carbon.core 4.0.5 in r151291.
Could it be because bamboo source not updated to latest for the last build?

Thanks,
Dileepa

On Thu, Dec 13, 2012 at 11:39 AM, Krishantha Samaraweera 
krishan...@wso2.com wrote:

 Hi Dileepa,

 Last bamboo kernel build[1] also failed due to following failures. Did you
 commit the fixes to branch?

 build 12-Dec-2012 21:00:49 Tests in error:

 build 12-Dec-2012 21:00:49  
 testNewServiceGroupAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testSetServiceGroupProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testNewServiceAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testServiceProperty(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testUpdateServiceGroupParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testUpdateServiceParameter(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testNewModuleAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testNewModuleNullVersionAddition(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testModuleParameterUpdate(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testDeleteService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testRemoveServiceParam(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testDeleteServiceGroup(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testRemoveModule(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testengageModuleForService(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
 build 12-Dec-2012 21:00:49  
 testGetResourcePath1(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)
 build 12-Dec-2012 21:00:49  
 testGetResourcePath3(org.wso2.carbon.core.test.persistence.PersistenceUtilsTest)
 build 12-Dec-2012 21:00:49
 build 12-Dec-2012 21:00:49Tests run: 23, Failures: 0, Errors: 16, 
 Skipped: 0
 build 12-Dec-2012 21:00:49

 Thanks,
 Krishantha

 [1]
 http://wso2.org/bamboo/download/WCB001-KER005-JOB1/build_logs/WCB001-KER005-JOB1-54.log

  On Wed, Dec 12, 2012 at 1:40 PM, Dileepa Jayakody dile...@wso2.comwrote:

 fixed in 151291, by initializing super-tenant flow for
 PersistenceUtilsTest and PersistenceManagerTest.

 The reason the tests were failing was, tenantId is not initialized (-1)
 when Registry instance is created from CarbonContext.getRegistry(). Now the
 tenantId is set to superTenantID in the test's setup flow.

 Thanks,
 Dileepa


 On Tue, Dec 11, 2012 at 10:27 AM, Dileepa Jayakody dile...@wso2.comwrote:

 I will look into this


 On Tue, Dec 11, 2012 at 10:17 AM, Muhammed Shariq sha...@wso2.comwrote:

 Hi,

 We need to get this test passing ASAP .. can someone have a look please
 ?!

 On Mon, Dec 10, 2012 at 11:19 AM, Dinusha Senanayaka 
 dinu...@wso2.comwrote:

 Build ran with the r150786. Surefire reports are attached herewith..

 Regards,
 Dinusha.

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




 --
 Thanks,
 Shariq.
 Phone: +94 777 202 225




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





-- 
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] Kernel test failures in PersistenceManagerTest

2012-12-10 Thread Dileepa Jayakody

I will look into this

On Tue, Dec 11, 2012 at 10:17 AM, Muhammed Shariq sha...@wso2.com wrote:

 Hi,

 We need to get this test passing ASAP .. can someone have a look please ?!

 On Mon, Dec 10, 2012 at 11:19 AM, Dinusha Senanayaka dinu...@wso2.comwrote:

 Build ran with the r150786. Surefire reports are attached herewith..

 Regards,
 Dinusha.

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




 --
 Thanks,
 Shariq.
 Phone: +94 777 202 225




-- 
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] wso2server.bat is updated to support UTF8 encoding on Windows by default

2012-12-06 Thread Dileepa Jayakody

Hi All,

As a fix to [1], UTF8 characters not supported on Windows by default, I
added the *-Dfile.encoding=UTF8 * parameter to wso2server.bat file in
Kernel [2].
If anyone uses different/updated startup script please update the .bat
script accordingly.

Thanks,
Dileepa

[1] https://wso2.org/jira/browse/CARBON-14012
[2]
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.5/carbon-home/bin

-- 
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] wso2server.bat is updated to support UTF8 encoding on Windows by default

2012-12-06 Thread Dileepa Jayakody

Only changed the .bat file [1] because this is specific to Windows

[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.5/carbon-home/bin/wso2server.bat

On Thu, Dec 6, 2012 at 2:59 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Hi All,

 As a fix to [1], UTF8 characters not supported on Windows by default, I
 added the *-Dfile.encoding=UTF8 * parameter to wso2server.bat file in
 Kernel [2].
 If anyone uses different/updated startup script please update the .bat
 script accordingly.

 Thanks,
 Dileepa

 [1] https://wso2.org/jira/browse/CARBON-14012
 [2]
 https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.5/carbon-home/bin

 --
 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] wso2server.bat is updated to support UTF8 encoding on Windows by default

2012-12-06 Thread Dileepa Jayakody

On Thu, Dec 6, 2012 at 7:44 PM, Chethiya Abeysinghe cheth...@wso2.comwrote:

 There are different Unix/Linux distros not having UTF8 by default. So we
 might have to consider doing this for .sh file too?

+1.

 - chethiya
 software engineer, WSO2
 On Dec 6, 2012 3:09 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Only changed the .bat file [1] because this is specific to Windows

 [1]
 https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.5/carbon-home/bin/wso2server.bat

 On Thu, Dec 6, 2012 at 2:59 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi All,

 As a fix to [1], UTF8 characters not supported on Windows by default, I
 added the *-Dfile.encoding=UTF8 * parameter to wso2server.bat file in
 Kernel [2].
 If anyone uses different/updated startup script please update the .bat
 script accordingly.

 Thanks,
 Dileepa

 [1] https://wso2.org/jira/browse/CARBON-14012
 [2]
 https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.5/carbon-home/bin

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




-- 
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] Clarification on features present in the IS p2-profile {was:Lot of unnecessary Jars in Carbon Core}

2012-12-05 Thread Dileepa Jayakody

On Thu, Dec 6, 2012 at 12:12 PM, Hasini Gunasinghe has...@wso2.com wrote:

 Hi,

 I was checking the IS p2-profile to clean up if any unnecessary features
 are present.
 Out of the existing features, I am not very much clear whether following
 features are must to have in IS.
 Appreciate the feedback to get this confirmed..

 org.wso2.carbon.databridge.datapublisher.feature
 org.wso2.carbon.xfer.feature
 org.wso2.carbon.mex.feature
 org.wso2.carbon.registry.profiles.feature

 Got clarified from Sanjeewa
 that org.wso2.carbon.stratos.usage.agent.feature, 
 org.wso2.carbon.stratos.throttling.agent.feature
 and org.wso2.carbon.load.balance.agent.server.feature are needed.

 I thought we don't use org.wso2.carbon.load.balance.agent feature now?
@Nirmal can you please confirm?


On a side note, I think it would be useful if we can maintain a wiki
 page/doc containing the information about the features - such as the
 purpose/functionality, owner etc, so that we can look at it when needed and
 can update it when ever we add a new feature.

 +1. It will be really useful to have such a doc. It will be useful for
p2-repo and feature-categories as well, to identify and define categories
with minimal set of features to gain required functionality.


 Thanks,
 Hasini.


 -- Forwarded message --
 From: Srinath Perera srin...@wso2.com
 Date: Wed, Nov 28, 2012 at 9:45 AM
 Subject: [Dev] Lot of unneccasry Jars in Carbon Core
 To: architecture architect...@wso2.org, dev dev@wso2.org


 We were building a minimal pack and observed this. I created a L1 for this
 https://wso2.org/jira/browse/CARBON-14010

 For example we have solr jar, jgorups, both ehcache and inifnispan etc in
 carbon core ..
 Pradeep please  send the list we created

 Also there are similar problems in IS, and I am sure in others. Please
 check the product profiles.

 --Srinath



 --
 
 Srinath Perera, Ph.D.
   Senior Software Architect, WSO2 Inc.
   Visiting Faculty, University of Moratuwa
   Member, Apache Software Foundation
   Research Scientist, Lanka Software Foundation
   Blog: http://srinathsview.blogspot.com/
   Photos: http://www.flickr.com/photos/hemapani/
  Phone: 0772360902

 ___
 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




-- 
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] Merge kernel branch into trunk ASAP

2012-11-11 Thread Dileepa Jayakody

On Sun, Nov 11, 2012 at 10:30 AM, Pradeep Fernando prad...@wso2.com wrote:

 hi,

 will own this. I'm not so sure about the tuesday deadline but lets see if
 we can meet this.
 @Dileepa : were you able to manage the complete the branching scritpt ? if
 so we can use the same for this.

 Rajika worked on the script and used it to merge the 4.0.3 changes to
support-trunk, Please find the attached latest script.
But if we are to use this for OT trunk, some changes might be needed for
the script.

Thanks,
Dileepa

 thanks,
 --Pradeep




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

Mobile : +94777-857616


support-branching.sh
Description: Bourne shell script
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stop releasing Carbon distribution with each and every product release.

2012-11-11 Thread Dileepa Jayakody

On Sun, Nov 11, 2012 at 7:50 PM, Pradeep Fernando prad...@wso2.com wrote:

 Hi All,

 right now we are doing a carbon distribution release with each and every
 product release. IMHO, this creates unnecessary set of work for carbon team.

 1. After we released C4.0.0 we only wanted to do a C4.0.1 release since
 CarbonContext refactoring happened.
 2 Carbon distribution contains Styling feature, Version change +
 Documentation (more or less the same) in addition to Carbon-Core.
 3. The only use case of Carbon Distribution is to install features on top
 of vanilla carbon-kernel. The same can be achieved by installing features
 on top of corresponding carbon-core version.


 With the the new mode of individual product releases, maintaining a carbon
 distribution is not practicable. We need our team to focus on C4.1.0 now.

 The plan is to decouple carbon team from every week release process,
 we will document all the steps like , creating OT branch, support branch,
 deploying, etc so that a member/members from the releasing product teams
 can complete them of their own.

 +1

 wdyt ?

 thanks,
 --Pradeep









-- 
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] Problem in installing MB features to wso2 products

2012-11-08 Thread Dileepa Jayakody

On Thu, Nov 8, 2012 at 3:22 PM, Shammi Jayasinghe sha...@wso2.com wrote:



 On Thu, Nov 8, 2012 at 1:24 PM, Selvaratnam Uthaiyashankar 
 shan...@wso2.com wrote:



 On Thu, Nov 8, 2012 at 10:43 AM, Shammi Jayasinghe sha...@wso2.comwrote:

 Hi,

 In Wso2 Message Broker , currently we are using a custom wso2server.sh
 file. We inject this in to the pack when
 building the distribution. The reason for this customization is we need
 to have some system properties in the start
 script of MB.

 Reason for system properties :

 We are using cassandra server feature in MB which is designed to start
 the Cassandra server , when starting the
 wso2 product. But in MB we have controlled this using an OSGI service to
 not start the cassandra server automatically.
 Then we specify to start the embedded cassandra or external cassandra in
 the configuration file on MB. So , to have
 the above control , we need to have the system property.


 Can we have some sensible default value for these properties? So, if
 the properties are not defined, we can assume the default and start
 servers.


 Yes, I checked with adding a default value and it works. How every if the
 user is going to have an external cassandra server ( which
 is recommended ) , he will have to add those system properties to start
 script.

 So we are going to solve this problem by having default values for the
 specified system properties and Updating the product Wiki on
 adding required properties when using an external cassandra server after
 feature installation.


+1.
I think every product team needs to verify whether their features need
manual configurations like this for a successful feature installation. If
any manual configuration is needed after a feature installation we should
document them in our product wikis.


 Thanks
 Shammi


 (Also, this mail should go to dev@)




 So when we try to install the MB product features via the p2 repository
 to Carbon or any wso2 product, we will have to
 have these system properties in the start up script.  AFAIU there are
 two possible ways to do that.

 1. Replace the existing start up scripts with the custom start up
 scripts we have for MB , when installing andes feature.
 - With this approach , there can be problems. If a user has
 added some tune up parameters or any customization
   to his start up scripts , those are getting lost when
 replaced the script.

 2. Documenting to add the required system properties in the MB wiki with
 out doing any script replacements.
 - First impression of the user on feature installation
 getting bad, when it prompting errors after feature
   installation and then he need to look for the fix in the
 web.

 What would be the best possible way to handle this.

 Thanks
 Shammi
 --
 Best Regards,*

 Shammi Jayasinghe*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com,
 mobile: +94 71 4493085





 --
 S.Uthaiyashankar
 Director, Cloud Solutions
 WSO2 Inc.
 http://wso2.com/ - lean . enterprise . middleware

 Phone: +94 714897591




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




-- 
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] Integration Tests Failure 4.0.4

2012-11-06 Thread Dileepa Jayakody

 - Aggregate Pom ... SUCCESS
 [0.267s]
 [INFO] WSO2 Carbon - Patch releases - dependencies - Aggregator Module
  SUCCESS [0.045s]
 [INFO] WSO2 Carbon - Patch releases - service-stubs - Aggregator Module
  SUCCESS [0.009s]
 [INFO] WSO2 Carbon - User Manager Kernel . SUCCESS
 [19.928s]
 [INFO] WSO2 Carbon - Patch releases - core - Aggregator Module  SUCCESS
 [0.007s]
 [INFO] WSO2 Carbon - Carbon Common Feature ... SUCCESS
 [6.305s]
 [INFO] WSO2 Carbon - Carbon Feature .. SUCCESS
 [7.644s]
 [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module
  SUCCESS [0.006s]
 [INFO] WSO2 Carbon Core - Distribution ... SUCCESS
 [56.039s]
 [INFO] WSO2 Carbon - Integration . SUCCESS
 [0.019s]
 [INFO] WSO2 Carbon - Security Verification Service ... SUCCESS
 [1.662s]
 [INFO] WSO2 Carbon - Integration Core  SUCCESS
 [3.111s]
 [INFO] WSO2 Carbon - Integration Testing Framework ... SUCCESS
 [2.230s]
 [INFO] WSO2 Carbon - Integration Tests ... FAILURE
 [3.205s]
 [INFO] WSO2 Carbon - Patch releases - distribution - Aggregator Module
  SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 1:41.719s
 [INFO] Finished at: Tue Nov 06 03:15:31 PST 2012
 [INFO] Final Memory: 99M/969M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on
 project org.wso2.carbon.integration.tests: There are test failures.
 [ERROR]
 [ERROR] Please refer to
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/tests/target/surefire-reports
 for the individual test results.
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.integration.tests


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

  http://sanjeewamalalgoda.blogspot.com/blog
 :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/


 ___
 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




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


 ___
 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] Integration Tests Failure 4.0.4

2012-11-06 Thread Dileepa Jayakody

Committed the change. Please take a svn up at
4.0.0/distribution/integration/4.0.4/tests

Thanks,
Dileepa

On Tue, Nov 6, 2012 at 8:10 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Yes The path should not be hard coded instead defined like;

 carbon.zip${basedir}/../../../kernel/${project.version}/target/wso2carbon-core-${project.version}.zip/carbon.zip

 where project.version is 4.0.4


 On Tue, Nov 6, 2012 at 8:02 PM, Sumedha Rubasinghe sume...@wso2.comwrote:

 But this path looks wrong.. It looks for 4.0.4 distro inside 4.0.3 folder
 path.


 On Tue, Nov 6, 2012 at 7:38 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Sanjeewa,

 Can you check whether  the path
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/tests/../../../kernel/4.0.3/target/wso2carbon-core-4.0.4.zip
 is exists?

 I think this is related to carbon-core distro version.

 Thanks,
 Krishantha.


  On Tue, Nov 6, 2012 at 7:24 PM, Sanjeewa Malalgoda 
 sanje...@wso2.comwrote:

  Hi,
 Please fix following test failure (due to wrong version).

 Thanks.



 /.m2/repository/org/wso2/carbon/org.wso2.carbon.integration.core/4.0.4/org.wso2.carbon.integration.core-4.0.4-tests.jar
 [INFO]

 [INFO]
 
 [INFO] Building WSO2 Carbon - Integration Testing Framework 4.0.4
 [INFO]
 
 [INFO]
 [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
 org.wso2.carbon.integration.framework ---
 [INFO] Deleting
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/target
 [INFO]
 [INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
 org.wso2.carbon.integration.framework ---
 [INFO] Verifying module descriptor ...
 [INFO] Pom descriptor modification detected.
 [INFO] Deleting
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/target
 [INFO]
 [INFO] --- maven-clean-plugin:2.4.1:clean (auto-clean) @
 org.wso2.carbon.integration.framework ---
 [INFO] Deleting
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/target
 [INFO]
 [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
 org.wso2.carbon.integration.framework ---
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] Copying 2 resources
 [INFO]
 [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
 org.wso2.carbon.integration.framework ---
 [INFO] Compiling 13 source files to
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/target/classes
 [INFO]
 [INFO] --- maven-resources-plugin:2.4.3:testResources
 (default-testResources) @ org.wso2.carbon.integration.framework ---
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/src/test/resources
 [INFO]
 [INFO] --- maven-compiler-plugin:2.3.1:testCompile
 (default-testCompile) @ org.wso2.carbon.integration.framework ---
 [INFO] No sources to compile
 [INFO]
 [INFO] --- maven-surefire-plugin:2.7.2:test (default-test) @
 org.wso2.carbon.integration.framework ---
 [INFO] No tests to run.
 [INFO] Surefire report directory:
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/target/surefire-reports
 There are no tests to run.
 [INFO]
 [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @
 org.wso2.carbon.integration.framework ---
 [INFO] Building jar:
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/target/org.wso2.carbon.integration.framework-4.0.4.jar
 [INFO]
 [INFO] --- maven-install-plugin:2.3.1:install (default-install) @
 org.wso2.carbon.integration.framework ---
 [INFO] Installing
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/target/org.wso2.carbon.integration.framework-4.0.4.jar
 to
 /var/home/lakmali/.m2/repository/org/wso2/carbon/org.wso2.carbon.integration.framework/4.0.4/org.wso2.carbon.integration.framework-4.0.4.jar
 [INFO] Installing
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/framework/pom.xml
 to
 /var/home/lakmali/.m2/repository/org/wso2/carbon/org.wso2.carbon.integration.framework/4.0.4/org.wso2.carbon.integration.framework-4.0.4.pom
 [INFO]

 [INFO]
 
 [INFO] Building WSO2 Carbon - Integration Tests 4.0.4
 [INFO]
 
 [INFO]
 [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
 org.wso2.carbon.integration.tests ---
 [INFO] Deleting
 /var/home/lakmali/branch/kernel/4.0.0/distribution/integration/4.0.4/tests/target
 [INFO]
 [INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
 org.wso2.carbon.integration.tests ---
 [INFO] Verifying module descriptor ...
 [INFO] Pom descriptor modification

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

2012-11-06 Thread Dileepa Jayakody

Fixed by adding carbon product 4.0.4 profile-gen and distribution modules.

Thanks,
Dileepa

On Wed, Nov 7, 2012 at 5:52 AM, Bamboo cbuil...@wso2.org wrote:

  [image: Failed]  WSO2 Carbon 
 4.0.xhttp://wso2.org/bamboo/browse/WCB001/› Kernel
 4.0.4 http://wso2.org/bamboo/browse/WCB001-KER004/ › 
 #3http://wso2.org/bamboo/browse/WCB001-KER004-3/
 failed

 Code has been updated by dileepahttp://wso2.org/bamboo/browse/author/dileepa
 .

 No failed tests found, a possible compilation error.
   Responsible No one is responsible for this build.
   Failing Jobs http://wso2.org/bamboo/browse/WCB001-KER004-3/Job
 Duration Tests[image: Failed]  Default 
 Jobhttp://wso2.org/bamboo/browse/WCB001-KER004-JOB1-3/ (Default
 Stage)  5 seconds  No tests found  
 Logshttp://wso2.org/bamboo/browse/WCB001-KER004-JOB1-3/log|
 Artifacts http://wso2.org/bamboo/browse/WCB001-KER004-JOB1-3/artifact 
 Code
 Changes http://wso2.org/bamboo/browse/WCB001-KER004-3/commit/  View all
 9 code changes http://wso2.org/bamboo/browse/WCB001-KER004-3/commit/
 dileepa http://wso2.org/bamboo/browse/author/dileepa
 adding carbon p2-profile-gen and product distribution to patch release pom
 147463dileepa http://wso2.org/bamboo/browse/author/dileepa
 updating user.core dependency version to 4.0.4  147462
 dileepahttp://wso2.org/bamboo/browse/author/dileepa
 updating carbon.core.server.feature included in the carbon.core aggregate
 147461   6 more 
 changes…http://wso2.org/bamboo/browse/WCB001-KER004-3/commit View
 Online http://wso2.org/bamboo/browse/WCB001-KER004-3 | Add 
 Commentshttp://wso2.org/bamboo/browse/WCB001-KER004-3?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




-- 
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] Error while building Kernel - 4.0.4

2012-11-06 Thread Dileepa Jayakody

Added the carbon 4.0.4 product p2-profilegen and distribution. Sorry for
the inconvenience caused.

Thanks,
Dileepa

On Wed, Nov 7, 2012 at 5:43 AM, Sumedha Rubasinghe sume...@wso2.com wrote:

 More digging... there is no 4.0.4 @

  ls
  
 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/../../../distribution/product/modules/distribution/
 4.0.0 4.0.1 4.0.2 4.0.3

 Neither @
 https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/product/modules/distributionas
  of Revision 147463.



 On Wed, Nov 7, 2012 at 5:38 AM, Sumedha Rubasinghe sume...@wso2.comwrote:

 On Wed, Nov 7, 2012 at 5:35 AM, Sumedha Rubasinghe sume...@wso2.comwrote:


 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4
  b
 [INFO] Scanning for projects...
 [ERROR] The build could not read 1 project - [Help 1]
 [ERROR]
 [ERROR]   The project
 org.wso2.carbon:carbon-patch-releases-distribution:4.0.4
 (/Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/pom.xml)
 has 2 errors
 [ERROR] Child module
 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/../../../distribution/product/modules/p2-profile-gen/4.0.4
 of
 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/pom.xml
 does not exist
 [ERROR] Child module
 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/../../../distribution/product/modules/distribution/4.0.4
 of
 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/pom.xml
 does not exist
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException



 However,
  ls
 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/pom.xml

 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/pom.xml


 Sorry. Wrong path. I should have done following check.

  ls
 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/../../../distribution/product/modules/distribution/4.0.4
 ls:
 /Volumes/data/projects/wso2/branches/carbon-4.0.0/kernel/patch-releases/4.0.4/distribution/../../../distribution/product/modules/distribution/4.0.4:
 No such file or directory

 which is non existent. Is 4.0.4 kernel building successful?



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




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




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




-- 
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] [BUILD FAILED] WSO2 Carbon 4.0.x Kernel_4.0.4 build #4

2012-11-06 Thread Dileepa Jayakody

Yes it is fixed now. Please take a svn up from
carbon/kernel/branches/4.0.0/distribution/product/modules.

Thanks,
Dileepa

On Wed, Nov 7, 2012 at 10:36 AM, Nuwan Dias nuw...@wso2.com wrote:

 I think Dileepa fixed this issue a few minutes back.

 Thanks,
 NuwanD.


 On Wed, Nov 7, 2012 at 10:28 AM, Maheshika Goonetilleke 
 mahesh...@wso2.com wrote:


 Hi All

 The Carbon Kernel_4.0.4 has failed due to the below errors;

 build06-Nov-2012 19:49:59[ERROR] The build could not read 1 
 project - [Help 1]
 build06-Nov-2012 19:49:59[ERROR]
 build06-Nov-2012 19:49:59[ERROR]   The project 
 org.wso2.carbon:carbon-patch-releases-distribution:4.0.4 
 (/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER004-JOB1/patch-releases/4.0.4/distribution/pom.xml)
  has 2 errors
 build06-Nov-2012 19:49:59[ERROR] Child module 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER004-JOB1/patch-releases/4.0.4/distribution/../../../distribution/product/modules/p2-profile-gen/4.0.4
  of 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER004-JOB1/patch-releases/4.0.4/distribution/pom.xml
  does not exist
 build06-Nov-2012 19:49:59[ERROR] Child module 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER004-JOB1/patch-releases/4.0.4/distribution/../../../distribution/product/modules/distribution/4.0.4
  of 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER004-JOB1/patch-releases/4.0.4/distribution/pom.xml
  does not exist



 --

 Thanks  Best Regards,

 Maheshika Goonetilleke
 Engineering Process Coordinator
 WSO2 Inc

 www.wso2.com/

 M : 0773 596707




 --
 Nuwan Dias

 Software Engineer - WSO2, Inc.
 Integration Technologies Team
 email : nuw...@wso2.com
 Phone : +94 777 775 729




-- 
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] Please add Identity Server Feature Category to 4.0.3 feature repository

2012-10-30 Thread Dileepa Jayakody

Hi IS team,

Can we please add IS category to 4.0.3 p2 repo pom? This is vital to test
IS feature group on top other carbon products. If you need further
clarifications on defining the feature category please let me know.

Thanks,
Dileepa

-- 
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] Please add Identity Server Feature Category to 4.0.3 feature repository

2012-10-30 Thread Dileepa Jayakody

On Wed, Oct 31, 2012 at 10:44 AM, Rajika Kumarasiri raj...@wso2.com wrote:

 I noticed that the current 4.0.3 feature is a copy from the 4.0.2, so it
 has all the released 4.0.2 features defined. Is this intentional or should
 it be fixed ? If this is indented behavior will that not build up the p2
 repo size each time we do  a release ?

 Yes this is intended, we followed the same flow since 4.0.0 release.
With 4.0.0 only AM got released so it only had 1 product category in the
repo.
With 4.0.1 the new set of product categories were added with updated
feature versions and the AM category already released was also included.

Since not all the products are getting released in chunk releases, the
features  products already got released in prev. chunk releases should be
in the p2-repo so users can install them as well. If any of their features
got updated we need to update feature versions.

So as a summary what needs to be done is;
1. Add new features or update features that are going to be released in
4.0.3
2. Add new product categories that are going to be released. eg: IS category


*Note: With regard to Product categories*

As per the discussion we had on current feature categorization we came to a
conclusion that a product category should be defined in a clear and usable
manner so a user can clearly identify the list of required features to
install a product/product combination. Not all features in the
p2-profile-gen need to be added to the category. Composite features
aggregating required set of sub-features should be used as a best practice.
This will become a form of sub-categories for the users in installing
features.
eg: when adding event features, don't add event.ui, event.common,
event.server separately instead add the composite feature.

Like wise every product category in the current p2-repo should be revised
to remove unwanted features and include composite features in a logical
manner. We need to go forward with a process for this where each product
team need to restructure their categories in a meaningful way for the
carbon users installing features. Will need help from each product team for
this.

Thanks,
Dileepa




Rajika

 On Wed, Oct 31, 2012 at 1:32 AM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi IS team,

 Can we please add IS category to 4.0.3 p2 repo pom? This is vital to test
 IS feature group on top other carbon products. If you need further
 clarifications on defining the feature category please let me know.

 Thanks,
 Dileepa

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





-- 
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] Please create Carbon 4.0.3 product

2012-10-29 Thread Dileepa Jayakody

On Mon, Oct 29, 2012 at 12:49 PM, Samisa Abeysinghe sam...@wso2.com wrote:



 On Sun, Oct 28, 2012 at 11:41 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi Prabath,

 Sorry for the delay in reply.
 We can do this as soon as commit rights are granted. Can we please have
 commit rights for this please?


 Did you try commiting???

No I didn't try committing as I was aware we shouldn't commit to branch at
this time, so I thought of asking for permission first to commit.
Since I am given permission now, I committed the carbon 4.0.3 distribution
and added it to kernel 4.0.3 patch release.

Thanks,
Dileepa




 Thanks,
 Dileepa


 On Sat, Oct 27, 2012 at 12:26 PM, Prabath Siriwardena 
 prab...@wso2.comwrote:



 On Wed, Oct 24, 2012 at 2:02 AM, Prabath Siriwardena 
 prab...@wso2.comwrote:

 Hi Dileepa/Pradeep,


 Wonder whether any of you had time to work on this?



 Thanks  regards,
 -Prabath



 Can you please do the $subject...

 --
 Thanks  Regards,
 Prabath

 Mobile : +94 71 809 6732

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




 --
 Thanks  Regards,
 Prabath

 Mobile : +94 71 809 6732

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




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

 Thanks,
 Samisa...

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





-- 
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] Feature manager categorization seems to be badly broken

2012-10-29 Thread Dileepa Jayakody

Hi Samisa,


On Mon, Oct 29, 2012 at 12:59 PM, Samisa Abeysinghe sam...@wso2.com wrote:

 And there is more into this: https://wso2.org/jira/browse/CARBON-13968

 Regarding the above jira about having category metadata in the installed
features list;

As per current implementation of Carbon P2 categorization using Eclipse P2
Category Publisher, we cannot maintain the categories in the installed
features.
Category is a logical grouping mechanism used to organize features in an
existing p2-repo, by adding extra metadata about categories to the repo.
What's installable in a category is the list of child features under the
category. The category doesn't get installed, so after installing the list
of child features under a category, the category metadata is lost and what
we have in the installation is a flat set of features. Therefore with the
current implementation of p2-categorization in the repository, we cannot
persist category metadata in our installation.

However as a work-around, if we consider a category as another feature and
have it also installed with it's child features we can persist
categorization in the installed feature list. I have asked p2-dev guys
about such mechanisms to maintain category metadata after a feature
installation. Will work on it.

Thanks,
Dileepa




 On Sat, Oct 27, 2012 at 11:57 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Fri, Oct 26, 2012 at 11:15 AM, Samisa Abeysinghe sam...@wso2.comwrote:



 On Fri, Oct 26, 2012 at 11:12 AM, Samisa Abeysinghe sam...@wso2.comwrote:

 More issues: https://wso2.org/jira/browse/CARBON-13968


 In general, it seems we have to review and re-design the categorization.

 When it comes to using the current categorization, there seems to be a
 bunch of usability issues.

 Please schedule a review for this ASAP.

 Sure, will schedule a review for this.





 On Wed, Oct 24, 2012 at 3:15 PM, Samisa Abeysinghe sam...@wso2.comwrote:

 Here is what I did:

 1. Downloaded, unzipped and ran AS
 2. Went to feature manager, added the online P2 repo and then
 installed Governance feature category, by clicking at the top level
  3. Re-started the server

 and it crashed down :(

 See the Jiras:
 https://wso2.org/jira/browse/REGISTRY-1471
 https://wso2.org/jira/browse/REGISTRY-1472
 https://wso2.org/jira/browse/CARBON-13958
  https://wso2.org/jira/browse/CARBON-13960

 Thanks,
 Samisa...

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

  Thanks,
 Samisa...

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


  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




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

 Mobile : +94777-857616

  Thanks,
 Samisa...

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





-- 
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] Feature manager categorization seems to be badly broken

2012-10-29 Thread Dileepa Jayakody

On Mon, Oct 29, 2012 at 5:20 PM, Rajika Kumarasiri raj...@wso2.com wrote:

 This is the off the topic. It seems if the license is not given in the
 feature, the feature manger is throwing errors
 https://wso2.org/jira/browse/IDENTITY-348.

 Looking into this.

 Rajika


 On Mon, Oct 29, 2012 at 12:59 PM, Samisa Abeysinghe sam...@wso2.comwrote:

 And there is more into this: https://wso2.org/jira/browse/CARBON-13968


 On Sat, Oct 27, 2012 at 11:57 PM, Dileepa Jayakody dile...@wso2.comwrote:



 On Fri, Oct 26, 2012 at 11:15 AM, Samisa Abeysinghe sam...@wso2.comwrote:



 On Fri, Oct 26, 2012 at 11:12 AM, Samisa Abeysinghe sam...@wso2.comwrote:

 More issues: https://wso2.org/jira/browse/CARBON-13968


 In general, it seems we have to review and re-design the
 categorization.

 When it comes to using the current categorization, there seems to be a
 bunch of usability issues.

 Please schedule a review for this ASAP.

 Sure, will schedule a review for this.





 On Wed, Oct 24, 2012 at 3:15 PM, Samisa Abeysinghe sam...@wso2.comwrote:

 Here is what I did:

 1. Downloaded, unzipped and ran AS
 2. Went to feature manager, added the online P2 repo and then
 installed Governance feature category, by clicking at the top level
  3. Re-started the server

 and it crashed down :(

 See the Jiras:
 https://wso2.org/jira/browse/REGISTRY-1471
 https://wso2.org/jira/browse/REGISTRY-1472
 https://wso2.org/jira/browse/CARBON-13958
  https://wso2.org/jira/browse/CARBON-13960

 Thanks,
 Samisa...

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

  Thanks,
 Samisa...

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


  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




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

 Mobile : +94777-857616

  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





-- 
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] Feature manager categorization seems to be badly broken

2012-10-27 Thread Dileepa Jayakody

On Fri, Oct 26, 2012 at 11:15 AM, Samisa Abeysinghe sam...@wso2.com wrote:



 On Fri, Oct 26, 2012 at 11:12 AM, Samisa Abeysinghe sam...@wso2.comwrote:

 More issues: https://wso2.org/jira/browse/CARBON-13968


 In general, it seems we have to review and re-design the categorization.

 When it comes to using the current categorization, there seems to be a
 bunch of usability issues.

 Please schedule a review for this ASAP.

 Sure, will schedule a review for this.





 On Wed, Oct 24, 2012 at 3:15 PM, Samisa Abeysinghe sam...@wso2.comwrote:

 Here is what I did:

 1. Downloaded, unzipped and ran AS
 2. Went to feature manager, added the online P2 repo and then installed
 Governance feature category, by clicking at the top level
  3. Re-started the server

 and it crashed down :(

 See the Jiras:
 https://wso2.org/jira/browse/REGISTRY-1471
 https://wso2.org/jira/browse/REGISTRY-1472
 https://wso2.org/jira/browse/CARBON-13958
  https://wso2.org/jira/browse/CARBON-13960

 Thanks,
 Samisa...

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

  Thanks,
 Samisa...

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


  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




-- 
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] Integration test failure in Carbon 4.0.2

2012-10-13 Thread Dileepa Jayakody

Yes, I cannot reproduce this test failure as well.

On Sat, Oct 13, 2012 at 9:37 PM, Krishantha Samaraweera krishan...@wso2.com
 wrote:

 We haven't touched these tests for months, still kernel build uses older
 integration tests core which was written in last November. May be PA
 machine configuration causing this failures, we might need to debug the
 tests on PA machine and see.

 Thanks,
 Krishantha.


 On Sat, Oct 13, 2012 at 9:21 PM, Amila Maha Arachchi ami...@wso2.comwrote:

 I have reported another weird failure in kernel. I think these are
 happening only in the PA builder.

 On Sat, Oct 13, 2012 at 9:11 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 I did a build again with latest changes and  haven't got such a failure.

 Thanks,
 Krishantha.

 On Fri, Oct 12, 2012 at 8:37 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi all,

 I see the below failure in 4.0.2 kernel integration

 Test class: org.wso2.carbon.integration.tests.MaintenanceModeTestCase
 Test Method: startMaintenance

 java.lang.AssertionError: Port 9443 should be closed in maintenance
 mode, but is open expected:false but was:true
 at
 org.wso2.carbon.integration.tests.MaintenanceModeTestCase.startMaintenance(MaintenanceModeTestCase.java:66)
 at
 org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:76)
 at
 org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
 at
 org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
 at
 org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
 at
 org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
 at
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
 at
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
 at
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
 at
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
 ... Removed 29 stack frames

 Sure fire reports attached
 --
 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 mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




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

 Blog: http://maharachchi.blogspot.com
 Mobile: +94719371446






-- 
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] Clarification regarding OAth UI and Data Bridge - Data Receiver Aggregate features

2012-10-12 Thread Dileepa Jayakody

Hi All,

I like to get a clarification regarding OAth ui feature and
databridge.datareceiver features in our platform.

1. In OAth UI feature

   includedFeatures

includedFeatureDeforg.wso2.carbon:org.wso2.carbon.jaxws.webapp.mgt.server.feature:4.0.2/includedFeatureDef

includedFeatureDeforg.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:4.0.2/includedFeatureDef
/includedFeatures

Why does the ui feature need server features like above?
And why have these external features included instead of being imported?
Generally we use includedFeatureDef in an aggregate feature to include it's
sub features and we use ImportFeatureDef to import external features.

2. In databridge.datareceiver feautre

Same question with  including external features instead of defining them as
import-features.

includedFeatureDeforg.wso2.carbon:org.wso2.carbon.jaxws.webapp.mgt.server.feature:${carbon.platform.patch.version.402}/includedFeatureDef

includedFeatureDeforg.wso2.carbon:org.wso2.carbon.webapp.mgt.server.feature:${carbon.platform.patch.version.402}/includedFeatureDef

Is there a particular reason we have included above features instead of
importing them?

Thanks,
Dileepa
-- 
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] Feature manager is slow

2012-10-11 Thread Dileepa Jayakody

On Thu, Oct 11, 2012 at 7:08 AM, Pradeep Fernando prad...@wso2.com wrote:

 May be this is a regression due to product/service merge. I see a
 related class [1].

 [1]
 carbon/platform/trunk/components/stratos/org.wso2.carbon.stratos.deployment/src/main/java/org/wso2/carbon/stratos/deployment/SuperTenantRolePlayer.java

 This occurs in products which have org.wso2.carbon.stratos.deployment
component, where the SOAP rolePlayer gets set to supertenant role.
When processing addressing headers, in the
org.apache.axiom.soap.impl.llom.SOAPHeaderImpl.checkHeader()
method it returns a boolean as below;

return (rolePlayer == null || rolePlayer.isUltimateDestination());

In org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer,
isUltimateDestination() is implemented as below,

 public boolean isUltimateDestination() {
return (CarbonContext.getCurrentContext().getTenantId() ==
MultitenantConstants.SUPER_TENANT_ID);
}

So in this case, if the current TenantId is equal to superTenantId (-1234),
the isUltimateDestination() method returns true and addressing headers are
processed.

But the problem comes when addRepository async. request is sent over
LocalTransport. The backend doesn't get the current TenantId. It's value
becomes -1.
As per offline discussion with Amila and Azeez, this could be because, when
async calls are sent with client options.setUseSeparateListener(true); the
AxisEngine invokes a separate
thread:TransportNonBlockingInvocationWorker(msgContext, sender) to send the
message.

The current solution for this is, when LocalTransport is enabled, not using
async requests.
In org.wso2.carbon.feature.mgt.ui I have fixed this by sending normal
blocking requests for addRepository, performProvisioningAction etc when
running on LocalTransport.

eg:

if (CarbonUtils.isRunningOnLocalTransportMode()) {
repositoryAdminServiceStub.addRepository(repoURL,
nickName);
} else {
ServiceClient client =
repositoryAdminServiceStub._getServiceClient();
client.engageModule(addressing);
Options options = client.getOptions();
options.setUseSeparateListener(true);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
repositoryAdminServiceStub.startaddRepository(repoURL,
nickName, callback);
handleCallback();
}

Appreciate any more insight into this fix.

Thanks,
Dileepa


 --Pradeep




-- 
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] Feature manager is slow

2012-10-10 Thread Dileepa Jayakody

Hi all,

I spent some time on debugging this issue at several levels including
repositoryAdminService client  stub, localTransport and addressing.
AFAIU the root cause is at addressing level where axis2 is unable to
process the addressing headers for the addRepository request when
localTransport is enabled in AS.

In org.apache.axis2.handlers.addressing.AddressingInHandler.doInvoke() the
header blocks are extracted as below;

iterator = header.getHeadersToProcess(rolePlayer, namespace);

Initially I thought the problem is with the namespace of the headers but it
was not the case. The problem is with the soap rolePlayer. I observed in
AppServer that rolePlayer is initialized with role: *supertenant*. When
supertant is set as the SOAP role header.getHeadersToProcess(rolePlayer,
namespace) doesn't process the header blocks so the server just treats the
message as a normal message without headers and sends the response without
any addressing information. That is why the callback is not triggered when
the response comes.


In carbon 4.0.1, 4.0.2 the role is not set as supertenant, The roleplayer
is always null. I observed the same behaviour in greg-4.5.0.
So In carbon, greg this works properly regardless of localTransport is
enabled or disabled.

The roleplayer is initialized in AddressingInHandler.doInvoke() as below
using AxisConfiguration;

 if(configuration == null){
System.out.println(axis config is null creating new one..);
AxisConfiguration conf =
msgContext.getConfigurationContext().getAxisConfiguration();
rolePlayer =
(RolePlayer)conf.getParameterValue(Constants.SOAP_ROLE_PLAYER_PARAMETER);
configuration = conf;
}


Any suggestions on how to resolve this issue with soap role : supertenant ?

Thanks,
Dileepa

On Wed, Oct 3, 2012 at 1:15 AM, Dileepa Jayakody dile...@wso2.com wrote:

 Hi All,

 I could reproduce this issue in esb 4.5.0 as well, so it's not limited to
 AS.

 When debugging the featureManager code what I observed is
 RepositoryAdminServiceCallbackHandler object registered for the
 addRepository asynchronous service request in RepositoryAdminServiceClient
 doesn't receive the response from the backend service.
 The handleCallback() waits forever till the callback handler receives the
 response from the BE service, hence the feature manager UI thread appears
 to be stuck.

 However if I disable the local transport by setting ServerURL as 
 https://${carbon.local.ip}:${carbon.management.port}${carbon.context}/services/
 in carbon.xml, the callbackhandler receives the service response for the
 above asynch call and the addRepository action completes without taking
 much time.

 Could this be an issue with local transport and WS-addressing where it is
 causing trouble for asynchronous clients to receive service response?


 Thanks,
 Dileepa




 On Mon, Oct 1, 2012 at 5:09 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 On Mon, Oct 1, 2012 at 3:57 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi Rajika and all,

 This issue with adding a p2-repo getting stuck is reproduced in AS 5.0.
 The issue is not there in kernel, esb-4.5.0 etc. Another thing to note is
 although the ui thread gets stuck, if we restart AS after a sufficient time
 for a repo-add or feature installation request, we can see the request has
 been fulfilled from the feature manager BE after the restart.


 I too observed this in AS. The installation task/ repo adding task
 completion notifications doesn't appear.

 thanks,


 This could be an issue with CallBackHandlers for feature manager
 requests. But what I cannot understand is why is it only happening in AS,
 because feature-manager component is common to all products.
 Any ideas?

 Thanks,
 Dileepa

 On Mon, Sep 10, 2012 at 9:06 PM, Chethiya Abeysinghe 
 cheth...@wso2.comwrote:

 OK. Got it. We can reason out loading meta data of all the features to
 the memory for computing the dependency tree. But I don't think that needs
 feature artifacts to be loaded into memory too.
 I guess how it works is, first it hash all features in memory and then
 create dependency tree for the user selected features efficiently f

 Yes Chethiya p2 computes the dependencies before installing features.
 It is called a provisioning plan.

 But Rajika's concern is that it's taking a long time at repository
 adding stage, which should not be performing any dependency computations.
 But I suspect p2 might be loading all the features in the repo to memory 
 at
 this stage. Have to clarify with p2-dev.

 Thanks,
 Dileepa

 On Mon, Sep 10, 2012 at 5:47 PM, Chethiya Abeysinghe 
 cheth...@wso2.com wrote:

 AFAIK, installing a p2 feature means not just copying set of files.
 It computes required dependency trees too. Looking at the content.xml I
 think it can take sometime for computation. But always better to check 
 with
 p2-dev as there can be cases which can be configured to
 avoid unnecessary dependency checks.

  - Chethiya

 On Mon, Sep 10

Re: [Dev] DSS build failure

2012-10-08 Thread Dileepa Jayakody

Hi Rajika,

This might be similar to https://wso2.org/jira/browse/CARBON-13592.
When there is an erroneous featureArtifact defined in p2-repo-gen goal, the
plugin just throws a NPE without indicating the erroneous artifact.
I fixed this by indicating what featureArtifact is giving the error (this
is fixed in carbon p2-plugin 1.5.1).

@Lakmali,
Can you please verify by using carbon-p2-plugin 1.5.1 in DSS p2-profile

Thanks,
Dileepa

On Mon, Oct 8, 2012 at 12:58 PM, Rajika Kumarasiri raj...@wso2.com wrote:

 The p2 profile plugin just throw a NPE instead of giving useful error
 message.

 Rajika


 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 DataServices Parent .. SUCCESS [0.409s]
 [INFO] WSO2 DataServices Styles Parent ... SUCCESS [0.068s]
 [INFO] DataServices UI styles  SUCCESS [4.740s]
 [INFO] WSO2 Stratos DSS - UI styles .. SUCCESS [1.032s]
 [INFO] WSO2 DataServices Samples Parent .. SUCCESS [0.315s]
 [INFO] DataServices Clients .. SUCCESS
 [25.465s]
 [INFO] WSO2 DataServices Features Parent . SUCCESS [0.050s]
 [INFO] WSO2 DataServices - Style Features  SUCCESS [0.967s]
 [INFO] WSO2 Stratos DSS - Features Aggregator Module . SUCCESS [0.059s]
 [INFO] WSO2 Stratos DSS - Style Features . SUCCESS [0.177s]
 [INFO] WSO2 Stratos DSS - Login User Interface ... SUCCESS [1.759s]
 [INFO] WSO2 Stratos DSS - Deployment Features  SUCCESS [0.245s]
 [INFO] WSO2 Stratos Data Services Server - Dashboard UI .. SUCCESS [1.613s]
 [INFO] WSO2 Stratos DSS - Dashboard UI Features .. SUCCESS [0.264s]
 [INFO] WSO2 DataServices - DataServices Profile Generation  FAILURE
 [21.950s]
 [INFO] WSO2 Data Services Server Distribution  SKIPPED
 [INFO] WSO2 DSS - Integration Tests .. SKIPPED
 [INFO] DataService Integration test module ... SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 1:00.475s
 [INFO] Finished at: Mon Oct 08 12:53:50 IST 2012
 [INFO] Final Memory: 46M/232M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5:p2-profile-gen
 (3-p2-profile-generation) on project wso2dataservices-profile-gen: null:
 MojoExecutionException: NullPointerException - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :wso2dataservices-profile-gen


 ___
 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] Governance UI compilation faliure

2012-10-03 Thread Dileepa Jayakody

Hi Eranda,

It's already there in maven repo

http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.governance.generic.stub/4.0.1/

Regards,
Dileepa

On Wed, Oct 3, 2012 at 5:52 PM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi Dileepa,
 Can we have org.wso2.carbon.governance.generic.stub 4.0.1 jar in the nexus.

 thanks
 Eranda


 On Wed, Oct 3, 2012 at 5:49 PM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi Miyuru,
 The reason for this because you don't have the correct stub jar file.
 Please build service-stubs/org.wso2.carbon.governance.generic.stub/4.0.1/
 first and then you will be able to build org.wso2.carbon.governance.
 generic.ui.

 thanks
 Eranda

 *
 *




 --
 *Eranda Sooriyabandara
 *Software Engineer;
 Integration Technologies Team;
 WSO2 Inc.; http://wso2.com

 *
 *




-- 
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] Build failure Andes - core

2012-10-03 Thread Dileepa Jayakody

Actually this jar is there in dist :
http://dist.wso2.org/maven2/org/apache/cassandra/apache-cassandra/1.1.3-wso2v1/
(however the jar has been updated very recently somehow)

Need to run a sync for our maven repos.
@Dhanushka can you please run a repo sync?

Thanks,
Dileepa

On Thu, Oct 4, 2012 at 10:42 AM, Ajith Vitharana aji...@wso2.com wrote:

 Hi Dileepa,

 Please upload org.apache.cassandra:apache-cassandra:jar:1.1.3-wso2v1 to
 nexus repo.

 Thanks
 Ajith

 On Thu, Oct 4, 2012 at 10:36 AM, Ajith Vitharana aji...@wso2.com wrote:

 Hi all,

 I'm getting following build failure in clean repo.

 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 15:15.223s
 [INFO] Finished at: Thu Oct 04 10:16:57 IST 2012
 [INFO] Final Memory: 1257M/1949M
 [INFO]
 
 [ERROR] Failed to execute goal on project org.wso2.carbon.andes.core:
 Could not resolve dependencies for project
 org.wso2.carbon:org.wso2.carbon.andes.core:bundle:4.0.2: The following
 artifacts could not be resolved:
 org.apache.cassandra:apache-cassandra:jar:1.1.3-wso2v1,
 org.apache.cassandra:apache-cassandra-thrift:jar:1.1.3-wso2v1: Could not
 find artifact org.apache.cassandra:apache-cassandra:jar:1.1.3-wso2v1 in
 wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) -
 [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

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





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





-- 
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] Feature manager is slow

2012-10-02 Thread Dileepa Jayakody

Hi All,

I could reproduce this issue in esb 4.5.0 as well, so it's not limited to
AS.

When debugging the featureManager code what I observed is
RepositoryAdminServiceCallbackHandler object registered for the
addRepository asynchronous service request in RepositoryAdminServiceClient
doesn't receive the response from the backend service.
The handleCallback() waits forever till the callback handler receives the
response from the BE service, hence the feature manager UI thread appears
to be stuck.

However if I disable the local transport by setting ServerURL as
https://${carbon.local.ip}:${carbon.management.port}${carbon.context}/services/
in carbon.xml, the callbackhandler receives the service response for the
above asynch call and the addRepository action completes without taking
much time.

Could this be an issue with local transport and WS-addressing where it is
causing trouble for asynchronous clients to receive service response?


Thanks,
Dileepa



On Mon, Oct 1, 2012 at 5:09 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 On Mon, Oct 1, 2012 at 3:57 PM, Dileepa Jayakody dile...@wso2.com wrote:

 Hi Rajika and all,

 This issue with adding a p2-repo getting stuck is reproduced in AS 5.0.
 The issue is not there in kernel, esb-4.5.0 etc. Another thing to note is
 although the ui thread gets stuck, if we restart AS after a sufficient time
 for a repo-add or feature installation request, we can see the request has
 been fulfilled from the feature manager BE after the restart.


 I too observed this in AS. The installation task/ repo adding task
 completion notifications doesn't appear.

 thanks,


 This could be an issue with CallBackHandlers for feature manager
 requests. But what I cannot understand is why is it only happening in AS,
 because feature-manager component is common to all products.
 Any ideas?

 Thanks,
 Dileepa

 On Mon, Sep 10, 2012 at 9:06 PM, Chethiya Abeysinghe 
 cheth...@wso2.comwrote:

 OK. Got it. We can reason out loading meta data of all the features to
 the memory for computing the dependency tree. But I don't think that needs
 feature artifacts to be loaded into memory too.
 I guess how it works is, first it hash all features in memory and then
 create dependency tree for the user selected features efficiently f

 Yes Chethiya p2 computes the dependencies before installing features.
 It is called a provisioning plan.

 But Rajika's concern is that it's taking a long time at repository
 adding stage, which should not be performing any dependency computations.
 But I suspect p2 might be loading all the features in the repo to memory at
 this stage. Have to clarify with p2-dev.

 Thanks,
 Dileepa

 On Mon, Sep 10, 2012 at 5:47 PM, Chethiya Abeysinghe cheth...@wso2.com
  wrote:

 AFAIK, installing a p2 feature means not just copying set of files. It
 computes required dependency trees too. Looking at the content.xml I think
 it can take sometime for computation. But always better to check with
 p2-dev as there can be cases which can be configured to
 avoid unnecessary dependency checks.

  - Chethiya

 On Mon, Sep 10, 2012 at 4:37 PM, Dileepa Jayakody dile...@wso2.comwrote:

 Hi Rajika,

 Thanks for the pointers.
 In the feature-manager we are using p2 sdk, calling the p2-api under
 the hood.

 For eg: to add and load a repository following code is used by us.

 IMetadataRepositoryManager metadataRepositoryManager =
 ServiceHolder.getMetadataRepositoryManager();
 IArtifactRepositoryManager artifactRepositoryManager =
 ServiceHolder.getArtifactRepositoryManager();

 //adding metadata and artifact repositories
 metadataRepositoryManager.addRepository(location);
 artifactRepositoryManager.addRepository(location);
 //Loading the metadata repository
 metadataRepositoryManager.loadRepository(location, new
 NullProgressMonitor());
 metadataRepositoryManager.setRepositoryProperty(location,
 IRepository.PROP_NICKNAME, nickName);

 //Loading the artifact repository
 artifactRepositoryManager.loadRepository(location, new
 NullProgressMonitor());
 artifactRepositoryManager.setRepositoryProperty(location,
 IRepository.PROP_NICKNAME, nickName);

 First we need to clarify how p2-works under the hood when loading a
 repository from a given location.
 Ideally it should just index the feature list by reading the the
 repository's content.xml and artifacts.xml at this point without loading
 all the features to the memory ( I believe this is what you are also
 suggesting).
 I will discuss this with p2-dev also and see how we can improve our
 feature manager based on that.

 Thanks,
 Dileepa


 On Mon, Sep 10, 2012 at 4:12 PM, Rajika Kumarasiri 
 raj...@wso2.comwrote:

 I meant the consumer task should do the feature installation
 asynchronously.

 Rajika


 On Mon, Sep 10, 2012 at 3:54 PM, Rajika Kumarasiri 
 raj...@wso2.comwrote:

 If you have not done already, here how it should be done

Re: [Dev] Feature manager is slow

2012-10-01 Thread Dileepa Jayakody

Hi Rajika and all,

This issue with adding a p2-repo getting stuck is reproduced in AS 5.0. The
issue is not there in kernel, esb-4.5.0 etc. Another thing to note is
although the ui thread gets stuck, if we restart AS after a sufficient time
for a repo-add or feature installation request, we can see the request has
been fulfilled from the feature manager BE after the restart.

This could be an issue with CallBackHandlers for feature manager requests.
But what I cannot understand is why is it only happening in AS, because
feature-manager component is common to all products.
Any ideas?

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 9:06 PM, Chethiya Abeysinghe cheth...@wso2.comwrote:

OK. Got it. We can reason out loading meta data of all the features to the
memory for computing the dependency tree. But I don't think that needs
feature artifacts to be loaded into memory too.
I guess how it works is, first it hash all features in memory and then
create dependency tree for the user selected features efficiently f

Yes Chethiya p2 computes the dependencies before installing features. It
is called a provisioning plan.

But Rajika's concern is that it's taking a long time at repository adding
stage, which should not be performing any dependency computations. But I
suspect p2 might be loading all the features in the repo to memory at this
stage. Have to clarify with p2-dev.

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 5:47 PM, Chethiya Abeysinghe
cheth...@wso2.comwrote:

AFAIK, installing a p2 feature means not just copying set of files. It
computes required dependency trees too. Looking at the content.xml I think
it can take sometime for computation. But always better to check with
p2-dev as there can be cases which can be configured to
avoid unnecessary dependency checks.

- Chethiya

On Mon, Sep 10, 2012 at 4:37 PM, Dileepa Jayakody dile...@wso2.comwrote:

Hi Rajika,

Thanks for the pointers.
In the feature-manager we are using p2 sdk, calling the p2-api under
the hood.

For eg: to add and load a repository following code is used by us.

IMetadataRepositoryManager metadataRepositoryManager =
ServiceHolder.getMetadataRepositoryManager();
IArtifactRepositoryManager artifactRepositoryManager =
ServiceHolder.getArtifactRepositoryManager();

//adding metadata and artifact repositories
metadataRepositoryManager.addRepository(location);
artifactRepositoryManager.addRepository(location);
//Loading the metadata repository
metadataRepositoryManager.loadRepository(location, new
NullProgressMonitor());
metadataRepositoryManager.setRepositoryProperty(location,
IRepository.PROP_NICKNAME, nickName);

//Loading the artifact repository
artifactRepositoryManager.loadRepository(location, new
NullProgressMonitor());
artifactRepositoryManager.setRepositoryProperty(location,
IRepository.PROP_NICKNAME, nickName);

First we need to clarify how p2-works under the hood when loading a
repository from a given location.
Ideally it should just index the feature list by reading the the
repository's content.xml and artifacts.xml at this point without loading
all the features to the memory ( I believe this is what you are also
suggesting).
I will discuss this with p2-dev also and see how we can improve our
feature manager based on that.

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 4:12 PM, Rajika Kumarasiri raj...@wso2.comwrote:

I meant the consumer task should do the feature installation
asynchronously.

Rajika

On Mon, Sep 10, 2012 at 3:54 PM, Rajika Kumarasiri raj...@wso2.comwrote:

If you have not done already, here how it should be done.

There should be an instance of blocking queue instance which keeps
track of requested features to install. There should be a producer task
which drop next requested feature list to install into the blocking
queue.
There should be a consumer task will remove items from the blocking
queue.
For producing and consuming use
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#puthttp://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#put%28E%29
and
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#take()
so
that your consumer and producer task will not kill the CPU.

Since Feature manager will not use frequently this model may not make
sense much, but I think it will be useful when our p2 feature repository
starts to grow.

Hope this helps.

Rajika

On Mon, Sep 10, 2012 at 2:47 PM, Dileepa Jayakody
dile...@wso2.comwrote:

Hi Rajika,

Is the repository you are adding a local-repository or a remote
repository?

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 2:44 PM, Rajika Kumarasiri
raj...@wso2.comwrote:

I just tried to add the feature repository of 4.0.1 into a AS
(built from 4.0.1 branch) and it seems it just take too much time.

Re: [Dev] org.wso2.carbon.identity.entitlement.proxy build failure

2012-10-01 Thread Dileepa Jayakody

Hi Andun,

The balana jars have been deployed and Dhanushka synched the nexus repos.
You can try building it now.

Thanks,
Dileepa

On Tue, Oct 2, 2012 at 10:56 AM, Andun Sameera an...@wso2.com wrote:

 Hi,

 This happens because the org.wso2.balana-1.0.0-wso2v2.jar is not deployed
 in the wso2 nexus repo due to a build failure in the balana it self.
 Dileepa has fixed that and deployed the jar in to nexus. You can fix this
 problem in a while.

 Thank
 AndunSLG

 On Tue, Oct 2, 2012 at 9:42 AM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 *
 *
 Hi,

 Following error is thrown when building
 org.wso2.carbon.identity.entitlement.proxy in a clean repo.

 [ERROR] Failed to execute goal on project
 org.wso2.carbon.identity.entitlement.proxy: Could not resolve dependencies
 for project
 org.wso2.carbon:org.wso2.carbon.identity.entitlement.proxy:bundle:4.0.2:
 Failure to find org.wso2.balana:org.wso2.balana:jar:1.0.0-wso2v2 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
 the local repository, resolution will not be reattempted until the update
 interval of wso2-nexus has elapsed or updates are forced

 Please have a look.

 Thanks,
 Lakmali

 ___
 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] [Bamboo-Build] WSO2 Carbon BRANCH Platform_4.0.0 #410 has FAILED. Change made by 12 authors.

2012-10-01 Thread Dileepa Jayakody

Hi Nirmal,

Redeployed the jar, Please check.

Thanks,
Dileepa

On Mon, Oct 1, 2012 at 8:22 PM, Nirmal Fernando nir...@wso2.com wrote:

 Hi Dileepa,

 Can you redeploy
 https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/service-stubs/org.wso2.carbon.load.balance.autoscaler.service.stub/4.0.0jar
  into Nexus please?

 Somehow Nexus seems to have an old jar.

 On Mon, Oct 1, 2012 at 5:53 PM, Bamboo cbuil...@wso2.org wrote:

  [image: Failed]  WSO2 Carbon 
 BRANCHhttp://wso2.org/bamboo/browse/WCB001/›
 Platform_4.0.0 http://wso2.org/bamboo/browse/WCB001-PLA000/ › 
 #410http://wso2.org/bamboo/browse/WCB001-PLA000-410/
 failed

 This build occurred because it is a dependant of 
 WCB001-KER000-247http://wso2.org/bamboo/browse/WCB001-KER000-247
 .

 *0/1518* tests failed.
Responsible No one is responsible for this build.
Failing Jobs http://wso2.org/bamboo/browse/WCB001-PLA000-410/Job
 Duration Tests[image: Failed]  Default 
 Jobhttp://wso2.org/bamboo/browse/WCB001-PLA000-JOB1-410/ (Default
 Stage)  159 minutes  1518 passed  
 Logshttp://wso2.org/bamboo/browse/WCB001-PLA000-JOB1-410/log|
 Artifacts http://wso2.org/bamboo/browse/WCB001-PLA000-JOB1-410/artifact
  Code
 Changes http://wso2.org/bamboo/browse/WCB001-PLA000-410/commit/  View
 all 33 code changeshttp://wso2.org/bamboo/browse/WCB001-PLA000-410/commit/
 sinthuja http://wso2.org/bamboo/browse/author/sinthuja
 adding thrift-agent-config.xml to the bin.xml  144342
 sinthujahttp://wso2.org/bamboo/browse/author/sinthuja
 adding agent asyn data publisher and load balancing config to
 thrift-agent-config.xml  144341
 sinthujahttp://wso2.org/bamboo/browse/author/sinthuja
 removing data-publisher.xml from publisher feature  144340   30 more
 changes… http://wso2.org/bamboo/browse/WCB001-PLA000-410/commit View
 Online http://wso2.org/bamboo/browse/WCB001-PLA000-410 | Add 
 Commentshttp://wso2.org/bamboo/browse/WCB001-PLA000-410?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




 --

 Thanks  regards,
 Nirmal

 Software Engineer- Platform Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/




-- 
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] AS p2 failure with Reporting Feature 4.0.2

2012-09-30 Thread Dileepa Jayakody

On Fri, Sep 28, 2012 at 1:48 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Reporting Feature 4.0.2
 (org.wso2.carbon.reporting.feature.group 4.0.2)
  Missing requirement: org.wso2.carbon.reporting.core 4.0.2
 (org.wso2.carbon.reporting.core 4.0.2) requires 'package
 org.wso2.carbon.reporting.api* [4.0.0,5.0.0)*' but it could not be found


The above required package version range is probably injected by the maven
bundle plugin based on the dependency tree.
This is intermittent, and you can avoid this behavior of maven bundle
plugin (bnd) injecting dependency version ranges automatically by properly
defining export/import versions in the bundles.
In this case if you give Import-Package for org.wso2.carbon.reporting.api
as version=0.0.0 you can rectify this issue.

 Cannot satisfy dependency:
   From: WSO2 Carbon - Reporting Feature 4.0.2
 (org.wso2.carbon.reporting.feature.group 4.0.2)
   To: org.wso2.carbon.reporting.template.server.feature.group [4.0.2]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Reporting Template Core Feature 4.0.2
 (org.wso2.carbon.reporting.template.server.feature.group 4.0.2)
   To: org.wso2.carbon.reporting.core [4.0.2]

 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




-- 
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] BUILD FAILURE : Mediation Library Feature

2012-09-21 Thread Dileepa Jayakody

Hi all,

Actually the org.wso2.carbon:mediation-library-feature:pom:4.0.1 and the
feature are deployed to the main nexus repo:
http://sr5.us1.wso2.com/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.mediation.library.feature/4.0.1/

Need to see further why this gets a failure in the build.

Thanks,
Dileepa


On Thu, Sep 20, 2012 at 11:54 PM, Charitha Madurangi charit...@wso2.comwrote:

 Hi,

 I included mediation-library to the features/pom.xml file which was not
 there before. That may be the reason why the mediation-library-feature is
 not listed in wso2-nexus. I committed the change with r143267. Please take
 a svn up in features/pom.xml, build features(this is to build
 mediation-library feature, so you can build only
 features/mediation-library/pom.xml instead) and try to build the
 patch-release 4.0.2 features again. I hope this would fix the issue.

 Thanks,
 Charitha.

 On Thu, Sep 20, 2012 at 6:16 PM, Sanjaya Vithanagama sanja...@wso2.comwrote:

 This issue is still there (r143276)

 On Thu, Sep 20, 2012 at 3:16 PM, Supun Malinga sup...@wso2.com wrote:

 [INFO]
 
 [ERROR] Failed to execute goal on project
 org.wso2.carbon.mediation.library.feature: Could not resolve dependencies
 for project
 org.wso2.carbon:org.wso2.carbon.mediation.library.feature:pom:4.0.2: Failed
 to collect dependencies for
 [org.wso2.carbon:org.wso2.carbon.mediation.library.ui.feature:zip:4.0.1
 (compile),
 org.wso2.carbon:org.wso2.carbon.mediation.library.server.feature:zip:4.0.2
 (compile)]: Failed to read artifact descriptor for
 org.wso2.carbon:org.wso2.carbon.mediation.library.ui.feature:zip:4.0.1:
 Could not find artifact org.wso2.carbon:mediation-library-feature:pom:4.0.1
 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
 - [Help 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




 --
 Sanjaya Vithanagama
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 71 342 2881


 ___
 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




-- 
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] Non-resolvable parent POM: Failure

2012-09-20 Thread Dileepa Jayakody

Hi Amila, Shameera,

Actually 4.0.1 artifacts are deployed to repo. The above referenced pom can
be found at:
http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/integration/4.0.1/

Thanks,
Dileepa

On Thu, Sep 20, 2012 at 3:51 PM, Shameera Rathnayaka shame...@wso2.comwrote:

 Hi ,

 On Thu, Sep 20, 2012 at 3:30 PM, Amila Maha Arachchi ami...@wso2.comwrote:

 There is a parent folder in kernel/branch/4.0.0. You can build it (by
 commenting out all the modules. Otherwise it will start building
 everything). 4.0.1 artifacts are not there in the repos yet AFAIK. But
 4.0.0. stuff should be there.


 I think better thing is try with 4.0.0 :)

 yes Amila , There is no error with the repos. has an error in
 carbon/kernel/branches/4.0.0/distribution/integration/4.0.0/security-verifier/pom.xml.
 please see the previous reply of mine to this thread.


 Thanks,
 Shameera.


 On Thu, Sep 20, 2012 at 3:13 PM, Shameera Rathnayaka 
 shame...@wso2.comwrote:

 Hi devs,

 When i try to build the kernel/tags/4.0.1 or kernel/branch/4.0.0 it
 failed due to non resolvable parent pom. Here is the error message

 [ERROR] Non-resolvable parent POM: Failure to find
 org.wso2.carbon:integration:pom:4.0.0 in http://repo1.maven.org/maven2was 
 cached in the local repository, resolution will not be reattempted
 until the update interval of central has elapsed or updates are forced and
 'parent.relativePath' points at wrong local POM @ line 22, column 13 -
 [Help 2]

 It seems particula pom is missing in repo isn't it?

 BTW at the moment, what i need is working source code to continue task
 which is writing a new adapter for ESB. If i am in wrong direction could
 you please mention a way to continue this building process.


 Thanks,
 Shameera.

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




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

 Blog: http://maharachchi.blogspot.com
 Mobile: +94719371446






-- 
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] P2 Repository for Carbon 4.0.1 releases

2012-09-14 Thread Dileepa Jayakody

Hi Jorge,

The p2-repo.zip for Carbon 4.0.1 is now available at WSO2 Carbon Product
Home page.

[1] http://dist.wso2.org/products/carbon/

Thanks,
Dileepa

On Fri, Sep 14, 2012 at 2:40 AM, Jorge Infante Osorio jorg...@uci.cuwrote:

 Can you provide us with a .zip repo?

 ** **

 Saludos,

 Ing. Jorge Infante Osorio.

 J´Dpto Soluciones SOA.

 CDAE.

 Fac. 5.

 UCI.

 “En un mundo perfecto las pizzas serían una comida saludable, las laptops
 se cargarían desde una fuente de corriente inalámbrica y todos los JAR
 serían bundles de OSGI ”

 ** **

 *De:* dev-boun...@wso2.org [mailto:dev-boun...@wso2.org] *En nombre de 
 *Dileepa
 Jayakody
 *Enviado el:* lunes, 10 de septiembre de 2012 2:45
 *Para:* Dasunpriya Anuradha
 *CC:* WSO2 Developers' List
 *Asunto:* Re: [Dev] P2 Repository for Carbon 4.0.1 releases

 ** **

 Yes please, can we have it expanded and hosted as an online repo like in
 previous releases?

 Thanks,
 Dileepa

 On Sun, Sep 9, 2012 at 12:53 AM, Kasun Gajasinghe kas...@wso2.com wrote:
 

 ** **

 On Sun, Sep 9, 2012 at 12:40 AM, Senaka Fernando sen...@wso2.com wrote:*
 ***

 Hi all,

 ** **

 I found that we have a zipped version of the P2 repo at [1]. But, do we
 also have an expanded version of it as in [2]?

 ** **

 ** **

 +1

  

 [1] http://dist.wso2.org/p2/carbon/releases/4.0.1/

 [2] http://dist.wso2.org/p2/carbon/releases/4.0.0/

 ** **

 Thanks,
 Senaka.
 

 ** **

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



 

 ** **

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




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

 Mobile : +94777-857616

   http://www.uci.cu/




-- 
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] P2 Repository for Carbon 4.0.1 releases

2012-09-10 Thread Dileepa Jayakody

Yes please, can we have it expanded and hosted as an online repo like in
previous releases?

Thanks,
Dileepa

On Sun, Sep 9, 2012 at 12:53 AM, Kasun Gajasinghe kas...@wso2.com wrote:



 On Sun, Sep 9, 2012 at 12:40 AM, Senaka Fernando sen...@wso2.com wrote:

 Hi all,

 I found that we have a zipped version of the P2 repo at [1]. But, do we
 also have an expanded version of it as in [2]?


 +1


 [1] http://dist.wso2.org/p2/carbon/releases/4.0.1/
 [2] http://dist.wso2.org/p2/carbon/releases/4.0.0/

 Thanks,
 Senaka.

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




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




-- 
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] Feature manager is slow

2012-09-10 Thread Dileepa Jayakody

Hi Rajika,

Is the repository you are adding a local-repository or a remote repository?

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 2:44 PM, Rajika Kumarasiri raj...@wso2.com wrote:

 I just tried to add the feature repository of 4.0.1 into a AS (built from
 4.0.1 branch) and it seems it just take too much time.

 I still can see the message Adding repository.. and it just there.

 This need to improve. We just need to load the list features (just names)
 and install any selected features asynchronously.

 It seems this loads the whole features into memory.

 Rajika

 ___
 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] Feature manager is slow

2012-09-10 Thread Dileepa Jayakody

Hi Rajika,

Thanks for the pointers.
In the feature-manager we are using p2 sdk, calling the p2-api under the
hood.

For eg: to add and load a repository following code is used by us.

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 4:12 PM, Rajika Kumarasiri raj...@wso2.com wrote:

I meant the consumer task should do the feature installation
asynchronously.

Rajika

On Mon, Sep 10, 2012 at 3:54 PM, Rajika Kumarasiri raj...@wso2.comwrote:

If you have not done already, here how it should be done.

There should be an instance of blocking queue instance which keeps track
of requested features to install. There should be a producer task which
drop next requested feature list to install into the blocking queue. There
should be a consumer task will remove items from the blocking queue. For
producing and consuming use
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#puthttp://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#put%28E%29
and
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#take()
so
that your consumer and producer task will not kill the CPU.

Since Feature manager will not use frequently this model may not make
sense much, but I think it will be useful when our p2 feature repository
starts to grow.

Hope this helps.

Rajika

On Mon, Sep 10, 2012 at 2:47 PM, Dileepa Jayakody dile...@wso2.comwrote:

Hi Rajika,

Is the repository you are adding a local-repository or a remote
repository?

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 2:44 PM, Rajika Kumarasiri raj...@wso2.comwrote:

I just tried to add the feature repository of 4.0.1 into a AS (built
from 4.0.1 branch) and it seems it just take too much time.

I still can see the message Adding repository.. and it just there.

This need to improve. We just need to load the list features (just
names) and install any selected features asynchronously.

It seems this loads the whole features into memory.

Rajika

___
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] Feature manager is slow

2012-09-10 Thread Dileepa Jayakody

Yes Chethiya p2 computes the dependencies before installing features. It is
called a provisioning plan.

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 5:47 PM, Chethiya Abeysinghe cheth...@wso2.comwrote:

- Chethiya

On Mon, Sep 10, 2012 at 4:37 PM, Dileepa Jayakody dile...@wso2.comwrote:

Hi Rajika,

Thanks for the pointers.
In the feature-manager we are using p2 sdk, calling the p2-api under the
hood.

For eg: to add and load a repository following code is used by us.

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 4:12 PM, Rajika Kumarasiri raj...@wso2.comwrote:

I meant the consumer task should do the feature installation
asynchronously.

Rajika

On Mon, Sep 10, 2012 at 3:54 PM, Rajika Kumarasiri raj...@wso2.comwrote:

If you have not done already, here how it should be done.

There should be an instance of blocking queue instance which keeps
track of requested features to install. There should be a producer task
which drop next requested feature list to install into the blocking queue.
There should be a consumer task will remove items from the blocking queue.
For producing and consuming use
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#puthttp://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#put%28E%29
and
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#take()
so
that your consumer and producer task will not kill the CPU.

Since Feature manager will not use frequently this model may not make
sense much, but I think it will be useful when our p2 feature repository
starts to grow.

Hope this helps.

Rajika

On Mon, Sep 10, 2012 at 2:47 PM, Dileepa Jayakody dile...@wso2.comwrote:

Hi Rajika,

Is the repository you are adding a local-repository or a remote
repository?

Thanks,
Dileepa

On Mon, Sep 10, 2012 at 2:44 PM, Rajika Kumarasiri raj...@wso2.comwrote:

I just tried to add the feature repository of 4.0.1 into a AS (built
from 4.0.1 branch) and it seems it just take too much time.

I still can see the message Adding repository.. and it just there.

This need to improve. We just need to load the list features (just
names) and install any selected features asynchronously.

It seems this loads the whole features into memory.

Rajika

___
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

--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com

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

Mobile : +94777-857616

Re: [Dev] Doesn't BAM run on Windows?

2012-09-10 Thread Dileepa Jayakody

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




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




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

1 2 3 >

1 - 100 of 211 matches

Mail list logo