[Dev] AppFactory 1.0.0 Build (11-June-2013)

Hi, Please find $Subject from [1]. [1] http://builder3.us1.wso2.org/builds/AF/11-June-2013/wso2appfactory-1.0.0.zip Thank You. Ranga. -- Ranga Siriwardena Software Engineer WSO2 Inc. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/l

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.1.x - Nightly > Platform_4.1.2 > #45 > Default Job has FAILED. Change made by 16 authors.

HI Amila I disabled the 4.1.2 plans in every project. On Tue, Jun 11, 2013 at 9:35 AM, Amila Maha Arachchi wrote: > Noticed that 4.1.3 plans are running. We still need to stop 4.1.2 plans. > > > On Tue, Jun 11, 2013 at 9:30 AM, Amila Maha Arachchi wrote: > >> I wonder why are we still building

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.1.x - Nightly > Platform_4.1.2 > #45 > Default Job has FAILED. Change made by 16 authors.

Noticed that 4.1.3 plans are running. We still need to stop 4.1.2 plans. On Tue, Jun 11, 2013 at 9:30 AM, Amila Maha Arachchi wrote: > I wonder why are we still building 4.1.2 after it is being released. And, > why the build fails time to time due to svn up or checkout failing. These > kind of f

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.1.x - Nightly > Platform_4.1.2 > #45 > Default Job has FAILED. Change made by 16 authors.

I wonder why are we still building 4.1.2 after it is being released. And, why the build fails time to time due to svn up or checkout failing. These kind of failures makes people pay less attention to build failure mails. Maheshika, I suggest we should remove 4.1.2 plans and run 4.1.3 plans now.

[Dev] {build-error} dataservicees/trunk

Hi all; im getting; FO] App Factory ... SKIPPED FO] FO] BUILD FAILURE FO] FO] Total time: 22:06.969s FO] Finished at:

Re: [Dev] build issue-trunk/registry uddi module

Thanks now builds fine.. On 10 June 2013 23:00, Vijitha Kumara wrote: > > > > On Mon, Jun 10, 2013 at 10:59 PM, Vijitha Kumara wrote: > >> >> >> >> On Mon, Jun 10, 2013 at 10:57 PM, Vijayaratha Vijayasingam < >> rat...@wso2.com> wrote: >> >>> Please tell me where to update..I did up last frida

[Dev] Failure to find org.wso2.carbon:WSO2-CARBON-PATCH-4.1.0:zip:0001

Getting following when building 4.1.0 branch on a clean repo. So we are not updating repos with patches? >>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack (2-unpack-kernel-patch) on project am-p2-profile: Unable

Re: [Dev] Error in adding artifact to Greg

I am not clear about your issue. What is the format of artifact JSON that you passed to carbon.registry.ArtifactManager instance. It should be something like below. Please trace your execution stack and verify whether it follows the below model before going to the AM instance's add method. {

Re: [Dev] build issue-trunk/registry uddi module

On Mon, Jun 10, 2013 at 10:59 PM, Vijitha Kumara wrote: > > > > On Mon, Jun 10, 2013 at 10:57 PM, Vijayaratha Vijayasingam < > rat...@wso2.com> wrote: > >> Please tell me where to update..I did up last friday!..You fixed during >> weekend? >> > > You need to update components/registry/orguddi

Re: [Dev] build issue-trunk/registry uddi module

On Mon, Jun 10, 2013 at 10:57 PM, Vijayaratha Vijayasingam wrote: > Please tell me where to update..I did up last friday!..You fixed during > weekend? > You need to update components/registry/orguddi > > > On 10 June 2013 20:54, Vijitha Kumara wrote: > >> When did you last update platform?

Re: [Dev] build issue-trunk/registry uddi module

Please tell me where to update..I did up last friday!..You fixed during weekend? On 10 June 2013 20:54, Vijitha Kumara wrote: > When did you last update platform? This should be fixed in trunk. > > > On Mon, Jun 10, 2013 at 12:19 PM, Vijayaratha Vijayasingam < > rat...@wso2.com> wrote: > >> >>

[Dev] Error in adding artifact to Greg

Hi all, I am faced with the below issue - My code is var publisher = require('/modules/publisher.js'); var t = "android"; publisher.addAsset(t, { name: ctx.name, lifecycle:["CREATED", "REVIEW", "PUBLISH", "REJECT", "REMOVED"], lifecycleState: "CREATED", options: {

Re: [Dev] [Architecture] [Platform enhancement] Clustering implementation has been switched to Hazelcast

Hi Azeez, Few questions, 1. What are the new configs comes into the picture? and the changes to existing configs?. 2. Also for the current tribes based clustering used implementations, will there be any changes that needs to be done?. thanks, On Mon, Jun 10, 2013 at 7:37 PM, Afkham Azeez wro

Re: [Dev] build issue-trunk/registry uddi module

When did you last update platform? This should be fixed in trunk. On Mon, Jun 10, 2013 at 12:19 PM, Vijayaratha Vijayasingam wrote: > > Hi all; > Im getting > [INFO] Building WSO2 Carbon - Registry - UDDI Service 4.2.0-SNAPSHOT > [INFO] > -

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

On Mon, Jun 10, 2013 at 7:15 AM, Amila Suriarachchi wrote: > > > > On Mon, Jun 10, 2013 at 7:09 AM, Afkham Azeez wrote: > >> On Mon, Jun 10, 2013 at 7:32 PM, Amila Suriarachchi >> wrote: >> > >> > >> > >> > On Mon, Jun 10, 2013 at 3:02 AM, Afkham Azeez wrote: >> >> >> >> Unfortunately, our cod

Re: [Dev] build issue-trunk/registry uddi module

This error was reported in 'Re: [Bamboo-Build] WSO2 Carbon 4.1.x > Platform 4.1.3 > #153 has FAILED' mail thread for Carbon 4.1.0 branch as well few days back. seems it it not fixed yet. - Ishara On Mon, Jun 10, 2013 at 6:53 PM, Vijayaratha Vijayasingam wrote: > anyone from registry team pls c

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

On Mon, Jun 10, 2013 at 7:09 AM, Afkham Azeez wrote: > On Mon, Jun 10, 2013 at 7:32 PM, Amila Suriarachchi > wrote: > > > > > > > > On Mon, Jun 10, 2013 at 3:02 AM, Afkham Azeez wrote: > >> > >> Unfortunately, our code repo structure & build structure is insanely > >> complex. This is the reaso

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

On Mon, Jun 10, 2013 at 3:02 AM, Afkham Azeez wrote: > Unfortunately, our code repo structure & build structure is insanely > complex. This is the reason why it is so hard to prevent build breaks. We > need to think of a much simplified structure. Too much complexity always > leads to human error

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

On Mon, Jun 10, 2013 at 7:12 PM, Afkham Azeez wrote: > The problem is, some components get used by more than one feature, and > in the future, we may decide to combine components in different ways > to create features. That is the reason why features are outside > components. > yeah, it's not re

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

I'm not sure I'm throwing an idea that already discussed in the past and found negative impacts. What about to remove top level component/feature directories and make related component/feature together. As an example we will have webapp-mgt module and inside that we have webapp-mgt components an

Re: [Dev] build issue-trunk/registry uddi module

anyone from registry team pls chk this? On 10 June 2013 12:19, Vijayaratha Vijayasingam wrote: > > Hi all; > Im getting > [INFO] Building WSO2 Carbon - Registry - UDDI Service 4.2.0-SNAPSHOT > [INFO] > > [INFO] > [INFO] --

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

On Mon, Jun 10, 2013 at 6:41 PM, Afkham Azeez wrote: > Reducing the number of components will automatically mean that we reduce > the number of features too. > yeah. we need to change the features's structure along with the modification to the components' structure. > > Azeez > > > On Mon, Jun

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

Reducing the number of components will automatically mean that we reduce the number of features too. Azeez On Mon, Jun 10, 2013 at 6:20 PM, Afkham Azeez wrote: > We should also look into our component list & see whether there are > components that can be deprecated. > > Azeez > > > On Mon, Jun

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

On Mon, Jun 10, 2013 at 6:06 PM, Afkham Azeez wrote: > I suggest that we remove all orbits which simply wrap 3rd party jars from > our main code repo, and have a separate repo for that. All such orbit > bundles will immediately be graduated, and deployed into the WSO2 Maven > repo. If there is an

Re: [Dev] [Architecture] Current Status of The Registry REST API and Issues I face when Integrate with APIM

Hai Sanjeewa..! We are having a strategic discussion that how to include the API publisher/ store jag apps to other products. Therefore, I will update this thread after the discussion...! As far as I understand, there will be single interceptor which decides the processing

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

We should also look into our component list & see whether there are components that can be deprecated. Azeez On Mon, Jun 10, 2013 at 6:06 PM, Afkham Azeez wrote: > I suggest that we remove all orbits which simply wrap 3rd party jars from > our main code repo, and have a separate repo for that.

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

I suggest that we remove all orbits which simply wrap 3rd party jars from our main code repo, and have a separate repo for that. All such orbit bundles will immediately be graduated, and deployed into the WSO2 Maven repo. If there is an issue with such an orbit bundle, which is a rare occurrence, y

Re: [Dev] [Architecture] Current Status of The Registry REST API and Issues I face when Integrate with APIM

Hai Lakmali..! Yes, the above link does not work...! I moved the user token generation menu under the "Resources" menu in order to appear for Greg. Therefore the existing doc won't work. Also these changes have not yet been committed. I will give you , the locally built lat

Re: [Dev] Encrypting the plain text passwords in config files

Look at a sample at https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/mediators/bam/org.wso2.carbon.mediator.bam.config/4.1.0/src/main/java/org/wso2/carbon/mediator/bam/config/CryptographyManager.java Thank you. * Maninda Edirisooriya* Software Engineer *WSO2, Inc. *lean.en

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

On Mon, Jun 10, 2013 at 3:32 PM, Afkham Azeez wrote: > Unfortunately, our code repo structure & build structure is insanely > complex. This is the reason why it is so hard to prevent build breaks. We > need to think of a much simplified structure. Too much complexity always > leads to human error

Re: [Dev] ESB: RDF Message Builder

On Mon, Jun 10, 2013 at 4:32 PM, Ravi Undupitiya wrote: > I managed to fix this by adding the following to axis2.xml: > > > class="org.apache.axis2.transport.http.ApplicationXMLFormatter"/> > > > class="org.apache.axis2.builder.ApplicationXMLBuilder"/> > > I think this is the right way around

[Dev] AxisConfiguration from TenantId

Hi, Is there any way to get the axisconfiguration from tenantId ?? Thanks, Mohan -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: mo...@wso2.com phone:(+94) 771117673 ___

Re: [Dev] Encrypting the plain text passwords in config files

Hi Shelan, Noted ! thanks. On Mon, Jun 10, 2013 at 5:09 PM, Shelan Perera wrote: > Hi, > > Have you looked into secure vault? You can use that to encrypt username > and password of config files. > > > thanks > > > On Mon, Jun 10, 2013 at 5:05 PM, Malinga Purnasiri wrote: > >> Hi, >> >> We have

[Dev] ESB 4.7.0 Docs on SSL Tunneling

In the doc for SSL Tunneling, http://docs.wso2.org/wiki/display/ESB470/Enabling+SSL+Tunneling+through+a+Proxy+Server Isn't it better to give the configuration example for the HttpCoreNIOSender and HttpCoreNIOSSLSender as well? Just a thought. -- *Chamara Ariyarathne* Senior Software Engineer -

Re: [Dev] Encrypting the plain text passwords in config files

Hi, Have you looked into secure vault? You can use that to encrypt username and password of config files. thanks On Mon, Jun 10, 2013 at 5:05 PM, Malinga Purnasiri wrote: > Hi, > > We have a ticket listed in the jira for MB as [1]. Please post some ideas > if anyone has achieved this before ?

[Dev] Encrypting the plain text passwords in config files

Hi, We have a ticket listed in the jira for MB as [1]. Please post some ideas if anyone has achieved this before ? or got suggestions on this ? [1] https://wso2.org/jira/browse/MB-171 -- Malinga Pathmal, Technical Lead, WSO2, Inc. : http://wso2.com/ Phone : (+94) 715335898 _

Re: [Dev] [Architecture] Current Status of The Registry REST API and Issues I face when Integrate with APIM

On Mon, Jun 10, 2013 at 4:08 PM, Dinusha Senanayaka wrote: > Hi All, > > This is what we are going to add from the APIM side. > > 1) We will be exposing current api manager handlers related > functionalities as some common packages. So this bundle can be included > into any of products to get API

[Dev] Latest ESB Pack (10-06-2013)

Please find $subject below. http://svn.wso2.org/repos/wso2/people/ravi/packs/20130610-wso2esb-4.7.0.zip -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com * * *E-mail: r...@wso2.com **M: **+94 772 930 712* * *Lean . Enterprise . Middleware

Re: [Dev] ESB: RDF Message Builder

I managed to fix this by adding the following to axis2.xml: I think this is the right way around this since RDF is XML. But this scenario works in HTTP-NIO transport without having to explicitly define the content type. Any advice on the proposed solution? Thanks, Ravi ___

[Dev] Build carbon orbit/trunk to avoid build failure

Folks, Please get an update & build carbon orbit/trunk. I have added Hazelcast, and the kernel core now depends on Hazelcast. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * ** email: **az

Re: [Dev] Current Status of The Registry REST API and Issues I face when Integrate with APIM

Hi Ragu, On 6 June 2013 12:01, Sriragu Arudsothy wrote: > Hai All, > >First of all, I will explain the architecture of the REST API > implementation. The Registry REST API has two mode of functionality. > > 1) Standalone mode - > > Straight access to Registry REST API. This has been

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

Unfortunately, our code repo structure & build structure is insanely complex. This is the reason why it is so hard to prevent build breaks. We need to think of a much simplified structure. Too much complexity always leads to human error. We need to simplify everything, starting from the repo struct

[Dev] ESB: RDF Message Builder

Is it correct functionality for the MessageProcessorSelector (the class responsible for selecting the message builder/formatter) to return the SOAP builder for the application/rdf+xml message type? How does this class return a builder based on the content type and message context? I think this is

Re: [Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

On Mon, Jun 10, 2013 at 1:48 PM, Afkham Azeez wrote: > Folks, > Can somebody let me know how to do this? I seem to have forgotten the > process, and everuthing looks very confusing. Some orbit bundles are in > trunk, some are in different branches... it is not easy to find where the > Hazelcast o

Re: [Dev] Get Axis 2 cluster worker member list at runtime

Hi, >> @Supun, >> worker nodes contain the 'wka' of the manager node. Manager >> node doesn't need to have the addresses of its workers. >> OC should know about all its managers and worker nodes >> > > @Manoj, No 'wka' can be a manager node or worker node. 'wka' is one of > membership Schema[1] w

[Dev] Need to add Hazelcast 2.5.wso2v1 to orbit

Folks, Can somebody let me know how to do this? I seem to have forgotten the process, and everuthing looks very confusing. Some orbit bundles are in trunk, some are in different branches... it is not easy to find where the Hazelcast orbit is :( This orbit bundle will be needed by all components &

Re: [Dev] Get Axis 2 cluster worker member list at runtime

Hi, On Mon, Jun 10, 2013 at 12:26 PM, Manoj Kumara wrote: > > @Supun, > worker nodes contain the 'wka' of the manager node. Manager > node doesn't need to have the addresses of its workers. > OC should know about all its managers and worker nodes > @Manoj, No 'wka' can be a manager node or work

Re: [Dev] Get Axis 2 cluster worker member list at runtime

Hi Manoj, On Mon, Jun 10, 2013 at 12:26 PM, Manoj Kumara wrote: > Hi All, > > I have debugged and inspected the ClusteringAgent element. Actually it > contain the details about worker nodes which registered using manager 'wka' > inside its transport elemet. The problem is there is no api calls