Re: [Dev] APIM 2.0 as a worker node in default profile doesn't not start

2016-08-22 Thread Janaka Ranabahu
Hi Supun,

API Manager has multiple components and there are different profiles to
start each component separately. When it comes to a distributed deployment,
only the gateway nodes will be configured in a worker-manager cluster and
we have profiles for those. For other nodes, there is no concept of a
worker profile.

Hence, the doc that IsuruH has shared has all the profiles that are needed
to do a fully distributed(HA) setup.

Thanks,
Janaka

On Mon, Aug 22, 2016 at 4:52 PM, Supun Malinga  wrote:

> Hi,
>
> $subject.
> $ ./bin/wso2server.sh
> JAVA_HOME environment variable is set to /opt/java
> CARBON_HOME environment variable is set to /home/supun/Builds/git-wso2-
> support/deployment-patterns/wso2am/temp/pattern6/wso2am-2.0.0
> Using Java memory options: -Xms256m -Xmx1024m
> [2016-08-22 16:44:31,725] FATAL {org.wso2.carbon.server.Main} -  OSGi
> runtime worker profile not found
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
> Caused by: java.lang.RuntimeException: worker profile not found
> at org.wso2.carbon.server.Main.main(Main.java:84)
> ... 6 more
>
> thanks,
> --
> Supun Malinga
>



-- 
*Janaka Ranabahu*
Associate Technical Lead, WSO2 Inc.
http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


[Dev] API Manager Beta2 - mysql_cluster.sql is not synced with mysql.sql

2016-07-11 Thread Janaka Ranabahu
Hi Nuwan,

The apimgt/mysql_cluster.sql has differences when compared to mysql.sql(or
mysql5.7+.sql). There are missing columns and seems like the recent changes
have not been added to the mysql_cluster.sql.

Please fix those accordingly. I've created [1] to track this.

Thanks,
Janaka

[1] https://wso2.org/jira/browse/APIMANAGER-5223

-- 
*Janaka Ranabahu*
Associate Technical Lead, WSO2 Inc.
http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [GREG] Invalid value error for REG_CREATED_TIME column in REG_RESOURCE with mysql 5.7

2016-05-09 Thread Janaka Ranabahu
Hi Thushara

On Tue, May 10, 2016 at 12:06 PM, Thushara Ranawaka 
wrote:

> Hi Thilini,
>
> AFAIU you workaround need to be updated with the current timestamp[1][2].
> Setting default value to zero is not nice. You might have to figure out the
> correct syntax for other DB types and test against them.
>
​What Thilini is pointing is an issue in the Registry database creation
script. Hence we will create a public JIRA and assign it to you guys.
Please fix them.

We can not modify the Registry database creation script since API Manager
would not capture the complete scenarios of G-Reg.

Thanks,
Janaka​


>
>
> [1] - DEFAULT CURRENT_TIMESTAMP
> [2] -
> http://stackoverflow.com/questions/168736/how-do-you-set-a-default-value-for-a-mysql-datetime-column
>
> Thanks,
> Thushara.
>
> On Tue, May 10, 2016 at 11:52 AM, Thilini Cooray 
> wrote:
>
>> Hi GReg team,
>>
>> We encounter following issue [1] while testing API Manager with MySQL 5.7
>> MySQL 5.7 has enabled NO_ZERO_IN_DATE, NO_ZERO_DATE policies by default.
>> Therefore it does not allow 0 as a valid default value for date/time.
>>
>> As a workaround we can set MySQL server to accept 0 changing the default
>> server settings if the database owner agrees on it.
>> [2] contains the related table creation script.
>>
>> Appreciate your feedback on a fix for this.
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-4645
>>
>> [2] CREATE TABLE IF NOT EXISTS REG_RESOURCE (
>> REG_PATH_ID INTEGER NOT NULL,
>> REG_NAMEVARCHAR(256),
>> REG_VERSION INTEGER NOT NULL AUTO_INCREMENT,
>> REG_MEDIA_TYPE  VARCHAR(500),
>> REG_CREATOR VARCHAR(31) NOT NULL,
>> REG_CREATED_TIMETIMESTAMP NOT NULL *DEFAULT 0*,
>> REG_LAST_UPDATORVARCHAR(31),
>> REG_LAST_UPDATED_TIMETIMESTAMP NOT NULL *DEFAULT 0*,
>> REG_DESCRIPTION VARCHAR(1000),
>> REG_CONTENT_ID  INTEGER,
>> REG_TENANT_ID INTEGER DEFAULT 0,
>> REG_UUID VARCHAR(100) NOT NULL,
>> CONSTRAINT PK_REG_RESOURCE PRIMARY KEY(REG_VERSION,
>> REG_TENANT_ID)
>> )ENGINE INNODB;
>>
>> Thanks.
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks,
> Thushara Kasun Ranawaka
> Software Engineer
> WSO2 Inc.; <http://www.wso2.com>
> lean.enterprise.middleware
> Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>*
> *thusha...@wso2.com *
>



-- 
*Janaka Ranabahu*
Associate Technical Lead, WSO2 Inc.
http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


[Dev] WSO2 Committers += Praminda Jayawardana

2016-03-28 Thread Janaka Ranabahu
Hi,

It is with great pleasure we welcome Praminda Jayawardana as a
WSO2 Committer. Congratulations Praminda and keep up the good work!

​Thanks,
Janaka​

-- 
*Janaka Ranabahu*
Associate Technical Lead, WSO2 Inc.
http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] APIM test stabilisation {was :Re: APIM git stabilization}

2015-02-11 Thread Janaka Ranabahu
Hi Krishantha,



On Wed, Feb 11, 2015 at 9:03 PM, Krishantha Samaraweera  wrote:

> Hi APIM Team,
>
> I'm getting following build failure when building GIT mater repo in clean
> repo.
>
> [ERROR] Failed to execute goal on project org.wso2.stratos.apimgt.styles:
> Could not resolve dependencies for project 
> org.wso2.am:org.wso2.stratos.apimgt.styles:bundle:2.2.0:
> Failure to find org.wso2.carbon:org.wso2.carbon.ui:jar:4.3.0-SNAPSHOT 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 -> [Help 1]
>
Is this the carbon-apimgt
​ repo? If so, please build the release-1.9.0 branch instead of the master.

Thanks,
Janaka​
​


> Can you please looking to it.
>
> Thanks,
> Krishantha.
>
>
>
> On Wed, Feb 11, 2015 at 12:47 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> [adding dev]
>>
>> On Wed, Feb 11, 2015 at 11:47 AM, Dimuthu De Lanerolle > > wrote:
>>
>>>
>>> Hi Krishantha,
>>>
>>> Following are the issues related to APIM git stabilization.
>>>
>>> 1. There are some changes needs to be done. Ex:
>>>
>>> These tests [1] are using old structure.
>>>
>>> [1]
>>> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-scenario/src/test/java/org/wso2/carbon/am/tests/header/ContentLengthHeaderTestCase.java
>>>
>>> (If going ahead with this structure needs to change -)
>>>
>>> integration-test-utils/src/main/java/org/wso2/am/integration/test/utils/APIManagerIntegrationTest.java
>>>
>>> import
>>> org.wso2.carbon.integration.common.admin.client.SecurityAdminServiceClient;
>>> import org.wso2.carbon.integration.common.utils.LoginLogoutClient;
>>>
>>> import
>>> org.wso2.am.integration.test.utils.publisher.utils.APIPublisherRestClient;
>>> import org.wso2.am.integration.test.utils.user.mgt.LoginLogoutClient;
>>>
>>> 2. At the root level project version is defined as ${apimserver.version}
>>> . However since after building wso2/carbon-apimgt still there were some
>>> build failures when building the  wso2/product-apim which  prohibits
>>> ${apimserver.version} to derive correctly for sub modules causing problems
>>> for building sub modules separately. ( we can overcome this issue by hard
>>> coding project version 1.9.0 as the version for integration and sub modules
>>> below integration.
>>>
>>> 3. Some of the tests needs to be migrated to public branch (svn) and
>>> git.
>>>
>>> 4. Introducing new structure to avoid code duplication and unnecessary
>>> codes.
>>>
>>>
>>> Dimuthu De Lanerolle
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middlewear.
>>> http://wso2.com/
>>> Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
>>>
>>>
>>
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middlewear.
>>
>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [APPFAC] Error regarding org.wso2.carbon.governance.lcm.jar

2015-02-05 Thread Janaka Ranabahu
Hi Kasun,

There is a schema validation that happens when adding a new lifecycle. In
order for that to happen, the ifecycle-config.xsd should be there in the
given location. IIRC, G-Reg includes this file when building the
distribution. Please check whether AF has such step and if not, please
refer to the G-Reg build to see how it is done.

Thanks,
Janaka


On Thu, Feb 5, 2015 at 1:55 PM, Kasun De Silva  wrote:

> Hi Janaka,
>
> In the given path (wso2appfactory-2.1.0-SNAPSHOT/repository/resources/)
> all I can find is,
>
> ├── lifecycles
> │   ├── configurations.xml
> │   └── UploadableApplicationLifeCycle.xml
> ├── rxts
> │   ├── application.rxt
> │   ├── appversions.rxt
> │   ├── database.rxt
> │   ├── databasetemplate.rxt
> │   ├── databaseuser.rxt
> │   ├── eta.rxt
> │   └── repouser.rxt
> ├── rxt.xsd
> ├── security
> │   ├── client-truststore.jks
> │   ├── tokenstore
> │   └── wso2carbon.jks
> ├── services-config.xsd
> └── service-ui-config.xsd
>
> Thanks,
> Kasun
>
> *Kasun de Silva*
> Software Engineer | *WSO2 Inc.*; http://wso2.com
> lean.enterprise.middleware
>
> email   : kas...@wso2.com
> mobile : +94 77 794 4260
>
>
> On Thu, Feb 5, 2015 at 11:55 AM, Janaka Ranabahu  wrote:
>
>> Hi Kasun,
>>
>> On Thu, Feb 5, 2015 at 11:49 AM, Kasun De Silva  wrote:
>>
>>> Hi All,
>>>
>>> Observed following in the AF log, This happens when login into tenant
>>> admin for the first time right after creating the tenant.
>>>
>>> we are using org.wso2.carbon.governance.lcm_4.2.1.jar in this pack.
>>>
>>>
>>> Any clue why is this happening ?
>>>
>> ​
>> ​This is when adding the LC for the 1st time. Could you check whether the
>> ​given file(
>> ​
>> /ifecycle-config.xsd) is there in the correct location?
>>
>> Thanks,
>> Janaka​
>>
>>
>>>
>>> TID: [0] [AF] [2015-02-05 10:22:21,890] ERROR {
>>> org.wso2.carbon.governance.lcm.util.CommonUtil} -  Unable to get a
>>> schema validator from the given file path : /mnt/
>>> 192.168.16.2/appfactory/wso2appfactory-2.1.0-SNAPSHOT/repository/resources/lifecycle-config.xsd
>>> {org.wso2.carbon.governance.lcm.util.CommonUtil}
>>> TID: [0] [AF] [2015-02-05 10:22:22,499] ERROR {
>>> org.wso2.carbon.governance.lcm.util.CommonUtil} -  Unable to get a
>>> schema validator from the given file path : /mnt/
>>> 192.168.16.2/appfactory/wso2appfactory-2.1.0-SNAPSHOT/repository/resources/lifecycle-config.xsd
>>> {org.wso2.carbon.governance.lcm.util.CommonUtil}
>>>
>>> Thanks,
>>>
>>> *Kasun de Silva*
>>> Software Engineer | *WSO2 Inc.*; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email   : kas...@wso2.com
>>> mobile : +94 77 794 4260
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Janaka Ranabahu*
>> Senior Software Engineer; WSO2 Inc.; http://wso2.com
>>
>>
>> *E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861
>> <%2B94%20718370861>*
>>
>> Lean . Enterprise . Middleware
>>
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [APPFAC] Error regarding org.wso2.carbon.governance.lcm.jar

2015-02-04 Thread Janaka Ranabahu
Hi Kasun,

On Thu, Feb 5, 2015 at 11:49 AM, Kasun De Silva  wrote:

> Hi All,
>
> Observed following in the AF log, This happens when login into tenant
> admin for the first time right after creating the tenant.
>
> we are using org.wso2.carbon.governance.lcm_4.2.1.jar in this pack.
>
>
> Any clue why is this happening ?
>
​
​This is when adding the LC for the 1st time. Could you check whether the
​given file(
​
/ifecycle-config.xsd) is there in the correct location?

Thanks,
Janaka​


>
> TID: [0] [AF] [2015-02-05 10:22:21,890] ERROR {
> org.wso2.carbon.governance.lcm.util.CommonUtil} -  Unable to get a schema
> validator from the given file path : /mnt/
> 192.168.16.2/appfactory/wso2appfactory-2.1.0-SNAPSHOT/repository/resources/lifecycle-config.xsd
> {org.wso2.carbon.governance.lcm.util.CommonUtil}
> TID: [0] [AF] [2015-02-05 10:22:22,499] ERROR {
> org.wso2.carbon.governance.lcm.util.CommonUtil} -  Unable to get a schema
> validator from the given file path : /mnt/
> 192.168.16.2/appfactory/wso2appfactory-2.1.0-SNAPSHOT/repository/resources/lifecycle-config.xsd
> {org.wso2.carbon.governance.lcm.util.CommonUtil}
>
> Thanks,
>
> *Kasun de Silva*
> Software Engineer | *WSO2 Inc.*; http://wso2.com
> lean.enterprise.middleware
>
> email   : kas...@wso2.com
> mobile : +94 77 794 4260
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] Demote action is visible for Uploadable apps - APPFAC-2702

2015-01-15 Thread Janaka Ranabahu
Hi Danushka,

On Wed, Jan 14, 2015 at 11:57 PM, Danushka Fernando 
wrote:

> Hi all
> [1] is fixed by having a check in ui to check whether its an uploadable
> application. But currently we have a different lifecycle for uploadable
> applications. So shouldn't we fix this by changing something in lifecycle.
> Since we are moving towards lifecycle per app type, I prefer fixing this by
> looking at the lifecycle. WDYT?
>
​True. The UI should be generated by reading all the "transition"
elements(where the "event" attribute is the action that is showed in the
UI) of each stage. That way, the per app type lifecycle model will work
without any issue.
Please note that a lifecycle stage can have 0 or more transitions.

Thanks,
Janaka


>
>
> [1] https://wso2.org/jira/browse/APPFAC-2702
>
>
> Thanks & Regards
> Danushka Fernando
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] Listen for an update to a registry resource

2014-12-18 Thread Janaka Ranabahu
Hi Gayeshan,

On Thu, Dec 18, 2014 at 6:23 PM, Gayashan Amarasinghe 
wrote:
>
> Hi all,
>
> I have a set of data services deployed in DSS which are exposed as
> RESTfull services. For each of these services there's a specific policy
> stored in the governance registry. (service knows this policy path from a
> parameter in the services xml file)
>
> I have requirement to register some sort of a listener/observer to this
> policy resource in the registry so that once the policy is updated in the
> registry it can redeploy the service. Is it possible to achieve this using
> the existing extension points of registry?
>
​Yes, You need to write a registry handler. Please refer [1] and [2] for
more information.

[1] https://docs.wso2.com/display/Governance460/Handlers
[2] https://docs.wso2.com/display/Governance460/Handler+Architecture

Thanks,
Janaka​


>
> Thanks.
> /Gayashan
>
> --
> *Gayashan Amarasinghe*
> Software Engineer | Platform TG
> WSO2, Inc. | http://wso2.com
> lean. enterprise. middleware
>
> Mobile : +94718314517
> Blog : gayashan-a.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [AF] If Auto Deploy fails for some reason Then we cannot promote that branch after that.

2014-12-18 Thread Janaka Ranabahu
Hi Danushka,

On Thu, Dec 18, 2014 at 12:10 PM, Danushka Fernando 
wrote:
>
> Hi all,
> According to current implementation, We pass a different deploy action to
> Auto Deploy which will label the artifact to promote. But for some reason
> if it fails and say user decided to disable auto deploy, user cannot
> promote that branch after that since label hasn't been created. And another
> down side is that if some one disable auto deploy and do manual deploy some
> of the changes are not going to be in the labeled artifact.
>
> IMO this should get fixed. WDYT?
>
​+1.

Please correct me if I'm wrong. But do we need to selectively label
artifacts when they are deployed? IMO, if an artifact is been deployed that
should be labeled as the deployed artifact.
On a side note, do we need label artifacts now?

Thanks,
Janaka
​


>
> Thanks & Regards
> Danushka Fernando
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [Note]Code freeze -05/12/2014 -3pm

2014-12-07 Thread Janaka Ranabahu
Hi Ratha,

On Mon, Dec 8, 2014 at 10:56 AM, Vijayaratha Vijayasingam 
wrote:

> You all want to commit only to 'appfac' component?
>
​Yes. also we need commit rights to
products/appfactory/2.1.0
​ as well.

Thanks,
Janaka​

>
> On 8 December 2014 at 10:09, Janaka Ranabahu  wrote:
>
>> Hi Ratha,
>>
>> On Mon, Dec 8, 2014 at 9:26 AM, Manjula Rathnayake 
>> wrote:
>>
>>> Hi Ratha,
>>>
>>> We are working towards AF-2.1.0 M7 release targeting on this Wednesday.
>>> Can AF team get commit rights? When we are planning to unfroze the Platform?
>>>
>> ​Adding to what Manjula has mentioned, we have moved our code base to
>> Turing branch and now the whole AppFactory team is working on Turing
>> branch. Hence this is a blocker for us to continue the work.
>>
>> Thanks,
>> Janaka​
>>
>>
>>>
>>> thank you.
>>>
>>> On Fri, Dec 5, 2014 at 5:08 PM, Vijayaratha Vijayasingam <
>>> rat...@wso2.com> wrote:
>>>
>>>> Platform is frozen ..
>>>> Thanks.
>>>>
>>>> On 4 December 2014 at 21:47, Vijayaratha Vijayasingam 
>>>> wrote:
>>>>
>>>>> Hi all;
>>>>> We will freeze the platform tomorrow by 3pm for chunk-14 RC build.
>>>>> Except AM/BAM team members, others won't be allowed to commit.
>>>>> Please note.
>>>>>
>>>>> Thanks.
>>>>> --
>>>>> -Ratha
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -Ratha
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "WSO2 Engineering Group" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to engineering-group+unsubscr...@wso2.com.
>>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Manjula Rathnayaka
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile:+94 77 743 1987
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "WSO2 Engineering Group" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to engineering-group+unsubscr...@wso2.com.
>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>
>>
>>
>>
>> --
>> *Janaka Ranabahu*
>> Senior Software Engineer; WSO2 Inc.; http://wso2.com
>>
>>
>> *E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861
>> <%2B94%20718370861>*
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> -Ratha
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [Note]Code freeze -05/12/2014 -3pm

2014-12-07 Thread Janaka Ranabahu
Hi Ratha,

On Mon, Dec 8, 2014 at 9:26 AM, Manjula Rathnayake 
wrote:

> Hi Ratha,
>
> We are working towards AF-2.1.0 M7 release targeting on this Wednesday.
> Can AF team get commit rights? When we are planning to unfroze the Platform?
>
​Adding to what Manjula has mentioned, we have moved our code base to
Turing branch and now the whole AppFactory team is working on Turing
branch. Hence this is a blocker for us to continue the work.

Thanks,
Janaka​


>
> thank you.
>
> On Fri, Dec 5, 2014 at 5:08 PM, Vijayaratha Vijayasingam 
> wrote:
>
>> Platform is frozen ..
>> Thanks.
>>
>> On 4 December 2014 at 21:47, Vijayaratha Vijayasingam 
>> wrote:
>>
>>> Hi all;
>>> We will freeze the platform tomorrow by 3pm for chunk-14 RC build.
>>> Except AM/BAM team members, others won't be allowed to commit.
>>> Please note.
>>>
>>> Thanks.
>>> --
>>> -Ratha
>>>
>>
>>
>>
>> --
>> -Ratha
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Engineering Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to engineering-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> Manjula Rathnayaka
> Software Engineer
> WSO2, Inc.
> Mobile:+94 77 743 1987
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Engineering Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to engineering-group+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [AF] Problem occurred while moving undeploy functionality to appfactory.deployers

2014-11-04 Thread Janaka Ranabahu
On Tue, Nov 4, 2014 at 11:06 PM, Mahesh Chinthaka  wrote:

> Hi Janaka,
> We initially decided to implement unDeployArtifact() in AbstractDeployer,
> now it seems better to implement it in AbstractStratosDeployer.
> +1 to implement it in AbstractStratosDeployer.
>
+1 for implementing it in the AbstractStratosDeployer since that is the
default place for all the stratos deployment related implementations.

Thanks,
Janaka

> @Harsha,
> WDYT ?
>
> On Tue, Nov 4, 2014 at 11:00 PM, Janaka Ranabahu  wrote:
>
>> Hi Mahesh,
>>
>> On Tue, Nov 4, 2014 at 10:51 PM, Mahesh Chinthaka 
>> wrote:
>>
>>> Hi Harsha,
>>> While following other codes i was able to figure out some usages and
>>> below is what im going to do. Let me know if anything wrong.
>>>
>>>
>>> *getRepositoryProviderAdminPassword()*
>>> *getRepositoryProviderAdminUser()*
>>>
>>> These two can be solved. We can
>>> use DeployerUtil.getRepositoryProviderProperty to get the repository
>>> provider admin username and password
>>>
>>> Please note that the current implementation of those methods are in the
>> NonBuildableArtifactDeployer. Please move them to AbstractStratosDeployer
>> so that in future, any deployment related operation for stratos can use
>> them.
>>
>>>
>>> *getGitRepoUrlForTenant()*
>>>
>>> RepositoryManager.getAppRepositoryURL can be used to do the job.
>>>
>>> Why can't you use the generateRepoUrl() method in
>> AbstractStratosDeployer for this. I didn't compare the implementations of
>> those 2 but they might be different since we are using 2 templates for Git
>> and S2Git. So please check that too.
>>
>>>
>>> *getServerDeploymentPaths()*
>>>
>>> This will be moved to AbstractDeployer.
>>>
>>> I would rather suggest to use AbstractStratosDeployer here since this is
>> related to stratos deployment and might not be the same for any other
>> deployment environment in the future
>>
>>>
>>> getFilesToDelete()
>>>
>>> I will move this in to AbstractDeployer, because unDeployAftifact is
>>> also in the AbstractDeployer and AbstractStratosDeployer is inherited from
>>> AbstractDeployer. So  I think we have to move it to AbstractDeployer
>>>
>>> Same as above.
>>
>> Thanks,
>> Janaka
>>
>>>
>>>
>>> On Tue, Nov 4, 2014 at 10:21 PM, Harsha Thirimanna 
>>> wrote:
>>>
>>>> Hi Mahesh,
>>>>
>>>> Don't write same code twice. Just move it. Because it is not suite to
>>>> use those kind of method that keeping this Service Class. When we are doing
>>>> some changes, we may have to re-factor according to the best practices.
>>>> WDYT ?
>>>>
>>>>
>>>> *Harsha Thirimanna*
>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>>> * <http://www.apache.org/>*
>>>> *email: **hars...@wso2.com* * cell: +94 71 5186770  ,
>>>> +94 *
>>>> *774617784twitter: **http://twitter.com/
>>>> <http://twitter.com/afkham_azeez>*
>>>> *harshathirimannlinked-in: **http:
>>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>>>
>>>> *Lean . Enterprise . Middleware*
>>>>
>>>>
>>>> On Tue, Nov 4, 2014 at 10:18 PM, Mahesh Chinthaka 
>>>> wrote:
>>>>
>>>>> Hi Harsha,
>>>>> Why cant we just make those methods public and use them ? Since
>>>>> appfactory.core is already a dependancy in appfactory.deployers
>>>>> So we can avoid writing the same code twice.
>>>>>
>>>>> On Tue, Nov 4, 2014 at 10:13 PM, Harsha Thirimanna 
>>>>> wrote:
>>>>>
>>>>>> Hi Janaka,
>>>>>>
>>>>>> There are no new utility method. Just keep it in right place as we
>>>>>> can reuse it.
>>>>>>
>>>>>>
>>>>>> *Harsha Thirimanna*
>>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>>>>> * <http://www.apache.org/>*
>>>>>> *email: **hars...@wso2.com* * cell: +94 71 5186770
>>>>>>  , +94 *
>>>>>> *774617784twitter: **http://twitter.com/
>&g

Re: [Dev] [AF] Problem occurred while moving undeploy functionality to appfactory.deployers

2014-11-04 Thread Janaka Ranabahu
>>>>> <http://twitter.com/afkham_azeez>*
>>>>> *harshathirimannlinked-in: **http:
>>>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>>>>
>>>>> *Lean . Enterprise . Middleware*
>>>>>
>>>>>
>>>>> On Tue, Nov 4, 2014 at 10:03 PM, Harsha Thirimanna 
>>>>> wrote:
>>>>>
>>>>>> Hi Janaka,
>>>>>>
>>>>>> As Mahesh mentioned some of here are Util methods as private.
>>>>>>
>>>>>> @Mahesh
>>>>>>
>>>>>> getGitRepoUrlForTenant - rename this method to getRepoUrlForTenant
>>>>>> and move it to RepositoryClient interface. Implement it
>>>>>> in GitRepositoryClient according to the Git.
>>>>>> getServerDeploymentPaths - in this method, there is only static
>>>>>> method call
>>>>>>
>>>>>>
>>>>>> *Harsha Thirimanna*
>>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>>>>> * <http://www.apache.org/>*
>>>>>> *email: **hars...@wso2.com* * cell: +94 71 5186770
>>>>>>  , +94 *
>>>>>> *774617784twitter: **http://twitter.com/
>>>>>> <http://twitter.com/afkham_azeez>*
>>>>>> *harshathirimannlinked-in: **http:
>>>>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>>>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>>>>>
>>>>>> *Lean . Enterprise . Middleware*
>>>>>>
>>>>>>
>>>>>> On Tue, Nov 4, 2014 at 9:52 PM, Janaka Ranabahu 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Mahesh,
>>>>>>>
>>>>>>> On Tue, Nov 4, 2014 at 9:42 PM, Mahesh Chinthaka 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all ,
>>>>>>>> I was trying to move the exact functionality in
>>>>>>>> *org.wso2.carbon.appfactory.core.deploy.ApplicationDeployer.undeployAllArtifactsOfAppFromDepSyncGitRepo()*
>>>>>>>> to
>>>>>>>> *org.wso2.carbon.appfactory.deployers.AbstractDeployer.unDeployArtifact()*
>>>>>>>>
>>>>>>>> while working on *unDeployArtifact()* i need to access some more
>>>>>>>> methods inside *ApplicationDeployer* class, which are private.
>>>>>>>> those are : getRepositoryProviderAdminUser()
>>>>>>>>   getRepositoryProviderAdminPassword()
>>>>>>>>   getGitRepoUrlForTenant()
>>>>>>>>   getServerDeploymentPaths()
>>>>>>>>   getFilesToDelete()
>>>>>>>>
>>>>>>> Did you check how these parameters are sent when the deployment call
>>>>>>> happens? IIRC, we pass a parameter map for that method which contains 
>>>>>>> all
>>>>>>> these parameters. Also those parameters are configured in the 
>>>>>>> appfactory.xml
>>>>>>> So please check how the deploy methods work. That should give you a
>>>>>>> clue.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Janaka
>>>>>>>
>>>>>>>>
>>>>>>>> What kind of approach should I follow ?
>>>>>>>>
>>>>>>>> 1. Make above methods public and use them.
>>>>>>>> 2. Implement same methods inside AbstactDeployer class and use them.
>>>>>>>>
>>>>>>>> FYI : *AbstractDeployer* class is implemented from *Deployer*
>>>>>>>> interface and currently it has following methods.
>>>>>>>> deployTaggedArtifact
>>>>>>>> deployLatestSuccessArtifact
>>>>>>>> deployPromotedArtifact
>>>>>>>> unDeployArtifact
>>>>>>>> handleException
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> --
>>>>>>>> *Mahesh Chinthaka Vidanagama* | Software Engineer
>>>>>>>> WSO2, Inc | lean. enterprise. middleware.
>>>>>>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>>>>>>> Mobile: +94 71 63 63 083 | Work: +94 112 145 345
>>>>>>>> Email: mahe...@wso2.com | Web: www.wso2.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Janaka Ranabahu*
>>>>>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com
>>>>>>>
>>>>>>>
>>>>>>> *E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861
>>>>>>> <%2B94%20718370861>*
>>>>>>>
>>>>>>> Lean . Enterprise . Middleware
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> *Mahesh Chinthaka Vidanagama* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 63 63 083 | Work: +94 112 145 345
>>> Email: mahe...@wso2.com | Web: www.wso2.com
>>>
>>
>>
>
>
> --
> *Mahesh Chinthaka Vidanagama* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 63 63 083 | Work: +94 112 145 345
> Email: mahe...@wso2.com | Web: www.wso2.com
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [AF] Problem occurred while moving undeploy functionality to appfactory.deployers

2014-11-04 Thread Janaka Ranabahu
Hi Harsha,

On Tue, Nov 4, 2014 at 10:03 PM, Harsha Thirimanna  wrote:

> Hi Janaka,
>
> As Mahesh mentioned some of here are Util methods as private.
>
Agreed. But to add the artifact to the git repo, we need the same
parameters right? Then there is a way that we pass those parameters to the
deploy method. What he should do it so use the same approach and same
methods since we are using the same repo to remove the artifact. IMO, for
that purpose, we do not need to introduce new utility methods.

Please correct me if I'm wrong.

Thanks,
Janaka

>
> @Mahesh
>
> getGitRepoUrlForTenant - rename this method to getRepoUrlForTenant and
> move it to RepositoryClient interface. Implement it in GitRepositoryClient
> according to the Git.
> getServerDeploymentPaths - in this method, there is only static method call
>
>
> *Harsha Thirimanna*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> * <http://www.apache.org/>*
> *email: **hars...@wso2.com* * cell: +94 71 5186770  ,
> +94 *
> *774617784twitter: **http://twitter.com/
> <http://twitter.com/afkham_azeez>*
> *harshathirimannlinked-in: **http:
> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>
> *Lean . Enterprise . Middleware*
>
>
> On Tue, Nov 4, 2014 at 9:52 PM, Janaka Ranabahu  wrote:
>
>> Hi Mahesh,
>>
>> On Tue, Nov 4, 2014 at 9:42 PM, Mahesh Chinthaka 
>> wrote:
>>
>>> Hi all ,
>>> I was trying to move the exact functionality in
>>> *org.wso2.carbon.appfactory.core.deploy.ApplicationDeployer.undeployAllArtifactsOfAppFromDepSyncGitRepo()*
>>> to
>>> *org.wso2.carbon.appfactory.deployers.AbstractDeployer.unDeployArtifact()*
>>>
>>> while working on *unDeployArtifact()* i need to access some more
>>> methods inside *ApplicationDeployer* class, which are private.
>>> those are : getRepositoryProviderAdminUser()
>>>   getRepositoryProviderAdminPassword()
>>>   getGitRepoUrlForTenant()
>>>   getServerDeploymentPaths()
>>>   getFilesToDelete()
>>>
>> Did you check how these parameters are sent when the deployment call
>> happens? IIRC, we pass a parameter map for that method which contains all
>> these parameters. Also those parameters are configured in the appfactory.xml
>> So please check how the deploy methods work. That should give you a clue.
>>
>> Thanks,
>> Janaka
>>
>>>
>>> What kind of approach should I follow ?
>>>
>>> 1. Make above methods public and use them.
>>> 2. Implement same methods inside AbstactDeployer class and use them.
>>>
>>> FYI : *AbstractDeployer* class is implemented from *Deployer* interface
>>> and currently it has following methods.
>>> deployTaggedArtifact
>>> deployLatestSuccessArtifact
>>> deployPromotedArtifact
>>> unDeployArtifact
>>> handleException
>>>
>>> Thanks
>>> --
>>> *Mahesh Chinthaka Vidanagama* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 63 63 083 | Work: +94 112 145 345
>>> Email: mahe...@wso2.com | Web: www.wso2.com
>>>
>>
>>
>>
>> --
>> *Janaka Ranabahu*
>> Senior Software Engineer; WSO2 Inc.; http://wso2.com
>>
>>
>> *E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861
>> <%2B94%20718370861>*
>>
>> Lean . Enterprise . Middleware
>>
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [AF] Problem occurred while moving undeploy functionality to appfactory.deployers

2014-11-04 Thread Janaka Ranabahu
Hi Mahesh,

On Tue, Nov 4, 2014 at 9:42 PM, Mahesh Chinthaka  wrote:

> Hi all ,
> I was trying to move the exact functionality in
> *org.wso2.carbon.appfactory.core.deploy.ApplicationDeployer.undeployAllArtifactsOfAppFromDepSyncGitRepo()*
> to
> *org.wso2.carbon.appfactory.deployers.AbstractDeployer.unDeployArtifact()*
>
> while working on *unDeployArtifact()* i need to access some more methods
> inside *ApplicationDeployer* class, which are private.
> those are : getRepositoryProviderAdminUser()
>   getRepositoryProviderAdminPassword()
>   getGitRepoUrlForTenant()
>   getServerDeploymentPaths()
>   getFilesToDelete()
>
Did you check how these parameters are sent when the deployment call
happens? IIRC, we pass a parameter map for that method which contains all
these parameters. Also those parameters are configured in the appfactory.xml
So please check how the deploy methods work. That should give you a clue.

Thanks,
Janaka

>
> What kind of approach should I follow ?
>
> 1. Make above methods public and use them.
> 2. Implement same methods inside AbstactDeployer class and use them.
>
> FYI : *AbstractDeployer* class is implemented from *Deployer* interface
> and currently it has following methods.
> deployTaggedArtifact
> deployLatestSuccessArtifact
> deployPromotedArtifact
> unDeployArtifact
> handleException
>
> Thanks
> --
> *Mahesh Chinthaka Vidanagama* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 63 63 083 | Work: +94 112 145 345
> Email: mahe...@wso2.com | Web: www.wso2.com
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] Problem with registry mounting with multiple mounts

2014-10-23 Thread Janaka Ranabahu
gt;>>>>>>>>>> /_system/governance of AS, but rather /_system/as/governance to
>>>>>>>>>>> /_system/governance of GREG.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Shazni Nazeer
>>>>>>>>>>>
>>>>>>>>>>> Senior Software Engineer
>>>>>>>>>>>
>>>>>>>>>>> Mob : +94 37331
>>>>>>>>>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>>>>>>>>>> Blog : http://shazninazeer.blogspot.com
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Oct 22, 2014 at 1:21 AM, Senaka Fernando <
>>>>>>>>>>> sen...@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Pulasthi,
>>>>>>>>>>>>
>>>>>>>>>>>> You have mounted AS on G-Reg but not G-Reg on AS right? This is
>>>>>>>>>>>> not the normal way of setting this up. Any reason for doing this?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Senaka.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tuesday, October 21, 2014, Pulasthi Supun 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Senaka/All,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Consider the following mounting scenario
>>>>>>>>>>>>>
>>>>>>>>>>>>> A greg has its governance space mounted
>>>>>>>>>>>>>
>>>>>>>>>>>>> 
>>>>>>>>>>>>> reggov
>>>>>>>>>>>>> /_system/governance
>>>>>>>>>>>>> 
>>>>>>>>>>>>>
>>>>>>>>>>>>> And the governance space of a separate AS server is mounted to
>>>>>>>>>>>>> a different path in the greg.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 
>>>>>>>>>>>>> asgov
>>>>>>>>>>>>> /_system/governance
>>>>>>>>>>>>> 
>>>>>>>>>>>>>
>>>>>>>>>>>>> When the mounts are done mount does not work properly
>>>>>>>>>>>>> everything under "/_system/as/governance" is replaced by 
>>>>>>>>>>>>> resources that are
>>>>>>>>>>>>> in "/_system/governance" . So the governance space of the greg is 
>>>>>>>>>>>>> populated
>>>>>>>>>>>>> into both paths. When we remove the mount of the greg and only 
>>>>>>>>>>>>> mount the
>>>>>>>>>>>>> governance of AS, it works properly. Is this a known bug?.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards
>>>>>>>>>>>>> Pulasthi
>>>>>>>>>>>>> --
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Pulasthi Supun
>>>>>>>>>>>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>>>>>>>>>>>> Email: pulas...@wso2.com
>>>>>>>>>>>>> Mobile: +94 (71) 9258281
>>>>>>>>>>>>> Blog : http://pulasthisupun.blogspot.com/
>>>>>>>>>>>>> Git hub profile: https://github.com/pulasthi
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *[image: http://wso2.com] <http://wso2.com>Senaka Fernando*
>>>>>>>>>>>> Solutions Architect; WSO2 Inc.; http://wso2.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *Member; Apache Software Foundation; http://apache.org
>>>>>>>>>>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P:
>>>>>>>>>>>> +1 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
>>>>>>>>>>>> http://linkedin.com/in/senakafernando
>>>>>>>>>>>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise .
>>>>>>>>>>>> Middleware
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ___
>>>>>>>>>>>> Dev mailing list
>>>>>>>>>>>> Dev@wso2.org
>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> --
>>>>>>>>>> Pulasthi Supun
>>>>>>>>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>>>>>>>>> Email: pulas...@wso2.com
>>>>>>>>>> Mobile: +94 (71) 9258281
>>>>>>>>>> Blog : http://pulasthisupun.blogspot.com/
>>>>>>>>>> Git hub profile: https://github.com/pulasthi
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>> *[image: http://wso2.com] <http://wso2.com>Senaka Fernando*
>>>>>>>> Solutions Architect; WSO2 Inc.; http://wso2.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *Member; Apache Software Foundation; http://apache.org
>>>>>>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P:
>>>>>>>> +1 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>>>>>>>>
>>>>>>>>
>>>>>>>> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
>>>>>>>> http://linkedin.com/in/senakafernando
>>>>>>>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise .
>>>>>>>> Middleware
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> *[image: http://wso2.com] <http://wso2.com>Senaka Fernando*
>>>>>> Solutions Architect; WSO2 Inc.; http://wso2.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Member; Apache Software Foundation; http://apache.org
>>>>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P:
>>>>>> +1 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>>>>>>
>>>>>>
>>>>>> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
>>>>>> http://linkedin.com/in/senakafernando
>>>>>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise .
>>>>>> Middleware
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> *[image: http://wso2.com] <http://wso2.com>Senaka Fernando*
>>>> Solutions Architect; WSO2 Inc.; http://wso2.com
>>>>
>>>>
>>>>
>>>> *Member; Apache Software Foundation; http://apache.org
>>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1
>>>> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>>>>
>>>>
>>>> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
>>>> http://linkedin.com/in/senakafernando
>>>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Architect & Product Lead of App Factory
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>> Mobile : 0773661935
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
>
>
> *[image: http://wso2.com] <http://wso2.com>Senaka Fernando*
> Solutions Architect; WSO2 Inc.; http://wso2.com
>
>
>
> *Member; Apache Software Foundation; http://apache.org
> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1
> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>
>
> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
> http://linkedin.com/in/senakafernando
> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [AppFactory] Moving the application name to the AppFactory database

2014-10-22 Thread Janaka Ranabahu
Hi Dimuthu,

On Wed, Oct 22, 2014 at 9:31 AM, Dimuthu Leelarathne 
wrote:

> Hi Janaka,
>
> +1 but we need caching at Carbon layer in front of the database. Please
> make sure the cache is updated properly as app names keeps adding.
>
All the other changes(including the migration scripts) are done. I'll start
introducing a caching layer for this.

Thanks,
Janaka

>
> thanks,
> dimuthu
>
>
> On Mon, Oct 20, 2014 at 5:45 PM, Danushka Fernando 
> wrote:
>
>> The only concern should be is about data migration we have to do in
>> cloud. But IMO its now or never. So +1 to do it now.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>> On Mon, Oct 20, 2014 at 5:05 PM, Janaka Ranabahu  wrote:
>>
>>> Hi,
>>>
>>> As a solution to [1], we have to move the Application Name to the
>>> AppFactory database. The current implementation keeps the application name
>>> in the registry and to check whether the name exists, we retrieve all the
>>> applications and then iterate through them to check whether the name
>>> exists. There is a considerable performance hit in this approach and
>>> therefore to improve the performance of this method,we will be adding the
>>> Application Name to the AppFactory database.
>>>
>>> Please raise any concerns you have on this.
>>>
>>> Also please note that we will be creating an migration script to migrate
>>> any old data as a part of this JIRA.
>>>
>>> Thanks,
>>> Janaka
>>>
>>> [1] https://wso2.org/jira/browse/APPFAC-2517
>>>
>>> --
>>> *Janaka Ranabahu*
>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com
>>>
>>>
>>> *E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861
>>> <%2B94%20718370861>*
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>
>
> --
> Dimuthu Leelarathne
> Architect & Product Lead of App Factory
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [Appfactory] Use GJit plugin for repository management

2014-10-21 Thread Janaka Ranabahu
Hi,

On Tue, Oct 21, 2014 at 6:19 PM, Mahesh Chinthaka  wrote:

> Hi ,
> No i meant a webservice, i understand it's not a good idea.
> Anyway there are some more findings so far,
>
> *Regarding appfactory.core.deploy.AppfactoryRepositoryClient*
>
> *appfactory.core.deploy.AppfactoryRepositoryClient* is used only twice
> for whole code. That is in *deleteFromDepSyncGitRepo* method and 
> *undeployAllArtifactsOfAppFromDepSyncGitRepo
> *method in *ApplicationDeployer* class within the same package. And above
> two methods are private.
>
> Though all other repository deployment functions happen in
> *appfactory.deployers *(which jar goes to jenkins) , undeployment happens
> in *appfactory.core* section (correct me if im wrong).
>
> Therefore if we move undeploy functionality to *appfactory.deployers *section
> , we can get rid of *appfactory.core.deploy.AppfactoryRepositoryClient. *
>
> +1. Please proceed with the re-factoring. We need to handle deployment and
undeployment related operations from the same place.

> *Regarding appfactory.deployers.clients.AppfactoryRepositoryClient*
>
> Unfortunately we will have to do the same implementation as in 
> *appfactory.repository.mgt
> *here , since this goes to jenkins and we need to keep minimum
> dependancies. Because of the minimum dependencies scenario we cannot use
> *JGitAgent* available in *appfacotry.repository.mgt . *Therefore we have
> to re-implement it here in *appfactory.deployers.clients* though it's a
> replication.
>
> Let's check whether we could move them to a common component, maybe
something like appfactory.common component.

Thanks,
Janaka

>
> Advise please
>
> On Tue, Oct 21, 2014 at 3:36 PM, Danushka Fernando 
> wrote:
>
>> What do you meant by a service ? An OSGI service? +1 Go ahead with the
>> solution #2.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>> On Tue, Oct 21, 2014 at 3:29 PM, Mahesh Chinthaka 
>> wrote:
>>
>>> Hi all,
>>> Im working on [1]
>>>
>>> In here we have to consider 3 classes
>>>
>>>1. org.wso2.carbon.appfactory.repository.mgt.client
>>>.AppfacotryRepositoryClient
>>>2. org.wso2.carbon.appfactory.core.deploy.AppfacotryRepositoryClient
>>>3. org.wso2.carbon.appfactory.deployers.clients
>>>.AppfacotryRepositoryClient
>>>
>>>
>>>
>>> *org.wso2.carbon.appfactory.repository.mgt.client.AppfacotryRepositoryClient*
>>> has already integrated with JGit plugin via *JGitAgent* class.
>>>
>>> Still
>>> *org.wso2.carbon.appfactory.core.deploy.AppfacotryRepositoryClient* and
>>> *org.wso2.carbon.appfactory.deployers.clients.AppfacotryRepositoryClient*
>>> use *GitSCMClient*. Now we need to remove SCM plugin and integrate JGit
>>> plugin to these two classes as well.
>>> I see following approaches,
>>>
>>> 1. Implement same functionality which is in
>>> *org.wso2.carbon.appfactory.repository.mgt.client.AppfacotryRepositoryClient*
>>> for above both places. But this will cause code redundancy, I guess.
>>> 2. Make
>>> *org.wso2.carbon.appfactory.repository.mgt.client.AppfacotryRepositoryClient*
>>> as a  service  and make it available to use in other two places.
>>>
>>> Please advise me in way forward. Suggest me a better approach please.
>>> Thanks
>>>
>>> [1] - https://wso2.org/jira/browse/APPFAC-2328
>>>
>>> --
>>> *Mahesh Chinthaka Vidanagama* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 63 63 083 | Work: +94 112 145 345
>>> Email: mahe...@wso2.com | Web: www.wso2.com
>>>
>>
>>
>
>
> --
> *Mahesh Chinthaka Vidanagama* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 63 63 083 | Work: +94 112 145 345
> Email: mahe...@wso2.com | Web: www.wso2.com
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


[Dev] [AppFactory] Moving the application name to the AppFactory database

2014-10-20 Thread Janaka Ranabahu
Hi,

As a solution to [1], we have to move the Application Name to the
AppFactory database. The current implementation keeps the application name
in the registry and to check whether the name exists, we retrieve all the
applications and then iterate through them to check whether the name
exists. There is a considerable performance hit in this approach and
therefore to improve the performance of this method,we will be adding the
Application Name to the AppFactory database.

Please raise any concerns you have on this.

Also please note that we will be creating an migration script to migrate
any old data as a part of this JIRA.

Thanks,
Janaka

[1] https://wso2.org/jira/browse/APPFAC-2517

-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] GReg LifeCycle - Enable transition related button after any checklist item selected

2014-10-02 Thread Janaka Ranabahu
Hi Manoj,

Like Subash mentioned earlier, there is no way to give optional check-list
items for a transition. We do not support that.

Thanks,
Janaka

On Thu, Oct 2, 2014 at 9:12 PM, Manoj Kumara  wrote:

> Hi Subash,
>
> Thanks for the prompt response, what I'm trying to achieve is enable the
> transition button after any checklist item selected. If we remove forEvnent
> attribute in each item 'Transition Button' will be enable by default.
>
> Is it possible to enable  'Transition Button' only after any one of Task
> 1, 2, 3 is selected.
>
> Thanks,
> Manoj
>
>
> *Manoj Kumara*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94713448188
>
> On Thu, Oct 2, 2014 at 11:22 AM, Subash Chaturanga 
> wrote:
>
>> Hi Manoj,
>> No you can't. Because the in the check item configuration,  the forEvent
>> value indicates that the particualr check item is required for it. In your
>> case Task1,2,3 all specified each checkitem is  required for the transition
>> "Promote". Hence unless all 3 checked, it will not appear. To achieve your
>> requirement, you can remove forEvent attribute in each item.
>>
>> On Thu, Oct 2, 2014 at 8:34 PM, Manoj Kumara  wrote:
>>
>>> Hi All,
>>>
>>> In registry lifecycles we can use forEvent="Promote" as, below to enable
>>> Promote once all the check boxes are checked.
>>>
>>> 
>>> 
>>>  
>>>  
>>>  
>>> 
>>> 
>>>
>>> I have a requirement that need to enable Promote when 'any of check
>>> boxes' is selected. Is there a option to do this.
>>>
>>> [1] https://docs.wso2.com/display/Governance460/Lifecycle+Sample
>>>
>>>
>>> Thanks,
>>> Manoj
>>>
>>
>>
>>
>> --
>> Thanks
>> /subash
>>
>> *Subash Chaturanga*
>> Senior Software Engineer
>> Platform TG; WSO2 Inc. http://wso2.com
>> Contact:
>> email: sub...@wso2.com
>> blog:  http://subashsdm.blogspot.com/
>> twitter: @subash89
>> phone: +9477 2225922
>> Lean . Enterprise . Middleware
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


*E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] ETA for on-premise App Factory

2014-07-29 Thread Janaka Ranabahu
Hi,

I was unable to attend to this past few days due to some personal matters.
I will get them done today. sorry for the inconvenience.

Thanks,
Janaka


On Wed, Jul 30, 2014 at 1:39 AM, Dmitry Sotnikov  wrote:

> This (scripts and docs for on-premise deployment) didn't get published,
> did it?
>
> Is there a new ETA?
>
> (Would like to have the answer if customers ask again.)
>
> Dmitry
>
>
> On Wed, Jul 23, 2014 at 8:23 PM, Dmitry Sotnikov  wrote:
>
>> *Dimuthu*, would these and the work that Janaka and Samith are doing be
>> sufficient for App Factory on-premise installation? User will still need to
>> download the actual bits and scripts - will we publish everything around
>> July 29?
>>
>> (Not sure whether you saw this today - another customer also said in
>> email he wanted to install AF on premises - the interest is growing, which
>> is a good thing.)
>>
>> Dmitry
>>
>>
>> On Wed, Jul 23, 2014 at 8:19 PM, Nirdesha Munasinghe 
>> wrote:
>>
>>> Done. 2.0.1 docs are public.
>>>
>>> Thanks,
>>> -Nirdesha
>>>
>>>
>>> On Wed, Jul 23, 2014 at 5:17 PM, Dimuthu Leelarathne 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> If we have the docs ready, then it is a matter of opening it up. If we
>>>> have continuous deployment I believe our doc strategy should change to
>>>> reflect that?
>>>>
>>>> @Nirdesha - Could we just make 2.0.1 docs public? So that as we deploy
>>>> things into cloud people can access the docs?
>>>>
>>>> thanks,
>>>> dimuthu
>>>>
>>>>
>>>>
>>>> On Wed, Jul 23, 2014 at 4:53 PM, Dmitry Sotnikov 
>>>> wrote:
>>>>
>>>>> Janaka,
>>>>>
>>>>> This comment by Nirdesha reads to me like a statement that although
>>>>> the scripts and docs will be created, it will not be until 2.0.1 release
>>>>> that they will be made public - so potentially much later than July 29. Is
>>>>> that so?
>>>>>
>>>>> As we are not going to give scripts with AF 2.0.0, I will remove that
>>>>>> section from the 2.0.0 docs. We will be adding the content to 2.0.1 docs.
>>>>>
>>>>>
>>>>> Dmitry
>>>>>
>>>>>
>>>>> On Wed, Jul 23, 2014 at 3:11 PM, Janaka Ranabahu 
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Our plan is to complete the docs by 29 July. Samith will be working
>>>>>> on these with me.
>>>>>>
>>>>>> Thanks,
>>>>>> Janaka
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 23, 2014 at 11:42 AM, Nirdesha Munasinghe <
>>>>>> nirde...@wso2.com> wrote:
>>>>>>
>>>>>>> Janaka will be adding the draft steps to wiki or in a Google doc.
>>>>>>> Please let me know once you are done so that I can complete this page.
>>>>>>>
>>>>>>> As we are not going to give scripts with AF 2.0.0, I will remove
>>>>>>> that section from the 2.0.0 docs. We will be adding the content to 2.0.1
>>>>>>> docs.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> -Nirdesha
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jul 23, 2014 at 11:08 AM, Dmitry Sotnikov 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Quick check on the status of this:
>>>>>>>>
>>>>>>>>- The scripts have been released, right?
>>>>>>>>- What is the ETA for documentation on using them to install AF?
>>>>>>>>
>>>>>>>> Dmitry
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Jul 5, 2014 at 4:10 PM, Dmitry Sotnikov 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks Harsha!
>>>>>>>>>
>>>>>>>>> I will let the customer know it is coming within a couple of weeks
>>>>>>>>> or so.
>>>>>>>>>
>>>>>>>>> Please let me know when everything is ready.
>>>>>>>>>
>>>>

Re: [Dev] ETA for on-premise App Factory

2014-07-23 Thread Janaka Ranabahu
Hi,

Our plan is to complete the docs by 29 July. Samith will be working on
these with me.

Thanks,
Janaka


On Wed, Jul 23, 2014 at 11:42 AM, Nirdesha Munasinghe 
wrote:

> Janaka will be adding the draft steps to wiki or in a Google doc. Please
> let me know once you are done so that I can complete this page.
>
> As we are not going to give scripts with AF 2.0.0, I will remove that
> section from the 2.0.0 docs. We will be adding the content to 2.0.1 docs.
>
> Thanks,
> -Nirdesha
>
>
> On Wed, Jul 23, 2014 at 11:08 AM, Dmitry Sotnikov  wrote:
>
>> Quick check on the status of this:
>>
>>- The scripts have been released, right?
>>- What is the ETA for documentation on using them to install AF?
>>
>> Dmitry
>>
>>
>> On Sat, Jul 5, 2014 at 4:10 PM, Dmitry Sotnikov  wrote:
>>
>>> Thanks Harsha!
>>>
>>> I will let the customer know it is coming within a couple of weeks or so.
>>>
>>> Please let me know when everything is ready.
>>>
>>> Dmitry
>>> On Jul 4, 2014 7:01 PM, "Harsha Thirimanna"  wrote:
>>>
>>>> Hi Dimitry,
>>>>
>>>> We are in final stage of this.
>>>>
>>>> After finish the appfactory puppet scripts we hope to run it with
>>>> privatepaas puppet and do the complete test.
>>>>
>>>> We can finish it on next friday (11th July).
>>>>
>>>> Thanks
>>>>  On Jul 4, 2014 5:20 PM, "Dmitry Sotnikov"  wrote:
>>>>
>>>>> An App Cloud user just asked me when the on-premise App Factory 2
>>>>> support coming.
>>>>>
>>>>> He wants to install it but docs are saying that this is not possible:
>>>>> https://docs.wso2.com/display/AF200/Installing+On-Premise
>>>>>
>>>>> Thanks!
>>>>> Dmitry
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>
>>
>> --
>> Dmitry Sotnikov
>> VP of Cloud; WSO2, Inc.;  http://wso2.com/
>> email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
>> Lean . Enterprise . Middleware
>>
>>  <http://wso2.com/events/>
>>
>
>
>
> --
>
> Thanks,
>
> Nirdesha Munasinghe,
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 776321920
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


* E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


[Dev] Build failure in Chunk-12 [cannot find symbol getCurrentUser() org.wso2.carbon.andes.stub.AndesAdminServiceStub]

2014-05-09 Thread Janaka Ranabahu
Hi Shammi,

Chunk-12 build fails due to the following exception. Did you guys remove
this method?

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 1:15.688s
[INFO] Finished at: Sat May 10 11:33:10 IST 2014
[INFO] Final Memory: 238M/1635M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.appfactory.eventing:
Compilation failure
[ERROR]
/home/janaka/work/wso2/carbon/carbon_4/platform/branches/turing/components/appfac/org.wso2.carbon.appfactory.eventing/2.0.0/src/main/java/org/wso2/carbon/appfactory/eventing/jms/AndesAdminServiceClient.java:[59,23]
cannot find symbol
*[ERROR] symbol  : method getCurrentUser()*
*[ERROR] location: class org.wso2.carbon.andes.stub.AndesAdminServiceStub*
*[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  -rf :org.wso2.carbon.appfactory.eventing

Thanks,
Janaka
-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


* E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


[Dev] Did we remove log analysing BAM from AppFactory setup?

2014-04-28 Thread Janaka Ranabahu
Hi,

Did we do $subject? If so could someone explain why we did that? I see that
we have commented that out in the setup script.

Thanks,
Janaka

https://svn.wso2.org/repos/wso2/scratch/appfactorycc/products/appfactory/1.1.0/vmware/appfactory_deployment_s4/set-up-mt-af.sh

-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


* E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861
<%2B94%20718370861>*

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


Re: [Dev] Do we need this handler in AF registry.xml

2014-04-10 Thread Janaka Ranabahu
Hi Amila,

We have removed these handlers from the configurations. Please refer the
following revision.







*Author: jan...@wso2.com  Date: Mon Nov 25 14:14:57
2013New Revision: 191671
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=191671
<http://wso2.org/svn/browse/wso2?view=rev&revision=191671> Log:Removing
unwanted handler and mount configuration*

Thanks,
Janaka


On Thu, Apr 10, 2014 at 1:51 PM, Amila Maha Arachchi wrote:

> AF team,
>
> $Subject?
>
>  "org.wso2.carbon.appfactory.registry.handler.ReferenceHandler">
>
>   stage
>
>  "org.wso2.carbon.registry.core.jdbc.handlers.filters.URLMatcher">
>
>   /_system/governance/.*
>
> 
>
>
>
>
> I hope we don't need those handlers now because we have separate
> registered for the dev,test,prod environments.
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> 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
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


* E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


Re: [Dev] [AppFactory] What is the reason for having 'default-SNAPSHOT' in pom.xml of web applications created in AppFactory?

2013-12-08 Thread Janaka Ranabahu
Hi Manjula,

Could not recall the exact reason but have seen this in the commit log.

@Manisha,
Would you be able to add some insight into this.



















*Log:changing the trunk's version from SNAPSHOT to default-SNAPSHOT to
avoid warnings Modified:
 
carbon/platform/branches/4.1.0/products/appfactory/1.0.0/vmware/appfactory_deployment/resources/appfactory.xml
Modified:
carbon/platform/branches/4.1.0/products/appfactory/1.0.0/vmware/appfactory_deployment/resources/appfactory.xml
URL: 
http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.1.0/products/appfactory/1.0.0/vmware/appfactory_deployment/resources/appfactory.xml?rev=178038&r1=178037&r2=178038&view=diff
<http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.1.0/products/appfactory/1.0.0/vmware/appfactory_deployment/resources/appfactory.xml?rev=178038&r1=178037&r2=178038&view=diff>
==
---
carbon/platform/branches/4.1.0/products/appfactory/1.0.0/vmware/appfactory_deployment/resources/appfactory.xml
 (original) +++
carbon/platform/branches/4.1.0/products/appfactory/1.0.0/vmware/appfactory_deployment/resources/appfactory.xml
 Thu Jul 11 20:52:34 2013 @@ -463,7 +463,7 @@ Web Application Archive file
 maven -DarchetypeGroupId=org.wso2.carbon.appfactory.maven.webapparchetype
-   -DarchetypeArtifactId=webapp-archetype
-DarchetypeVersion=1.0.0 -DgroupId=org.wso2.af
<http://org.wso2.af/> -Dversion=SNAPSHOT -DinteractiveMode=false +
  -DarchetypeArtifactId=webapp-archetype -DarchetypeVersion=1.0.0
-DgroupId=org.wso2.af
<http://org.wso2.af/> -Dversion=default-SNAPSHOT -DinteractiveMode=false
  -DarchetypeCatalog=local*

Thanks,
Janaka


On Mon, Dec 9, 2013 at 11:31 AM, Manjula Rathnayake wrote:

> Hi all,
>
> Noticed below version in pom.xml.
>
>  org.wso2.af
>   foo
>  * default-SNAPSHOT*
>   war
>   foo
>
> thank you.
>
> --
> Manjula Rathnayaka
> Software Engineer
> WSO2, Inc.
> Mobile:+94 77 743 1987
>



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com


* E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861*

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


[Dev] Build failure in chunk-02

2013-10-11 Thread Janaka Ranabahu
Please fix these issues.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project org.wso2.carbon.apimgt.impl: Compilation
failure
[ERROR]
/home/janaka/work/wso2/carbon/platform/branches/4.2.0/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.0/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[332,59]
cannot find symbol
[ERROR] symbol  : method getLength()
[ERROR] location: class
org.wso2.carbon.registry.core.pagination.PaginationContext
[ERROR] -> [Help 1]


Thanks,
Janaka

-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


Re: [Dev] Build failure in AF scratch code

2013-09-14 Thread Janaka Ranabahu
Hi Amila,

You need to build the service stubs in the scratch area. We have some dome
modifications to them as well.

Thanks,
Janaka


On Sat, Sep 14, 2013 at 4:12 PM, Amila Maha Arachchi wrote:

> Hi AF team,
>
> I was trying to build your code in scratch area and got the following
> build error. Code is up to date.
>
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 3:04.211s
> [INFO] Finished at: Sat Sep 14 16:05:55 IST 2013
> [INFO] Final Memory: 523M/1977M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.5:compile
> (default-compile) on project appfactory-plugin: Compilation failure:
> Compilation failure:
> [ERROR]
> /home/amila/temp/AF/af-scratch-code/appfactory/products/appfactory/1.1.0/modules/webapps/appfactory-plugin/src/main/java/org/wso2/carbon/appfactory/jenkins/build/notify/JenkinsCIBuildStatusReceiverClient.java:[5,52]
> cannot find symbol
> [ERROR] symbol  : class JenkinsCIBuildStatusRecieverServiceStub
> [ERROR] location: package org.wso2.carbon.appfactory.jenkins.build.stub
> [ERROR]
> /home/amila/temp/AF/af-scratch-code/appfactory/products/appfactory/1.1.0/modules/webapps/appfactory-plugin/src/main/java/org/wso2/carbon/appfactory/jenkins/build/notify/JenkinsCIBuildStatusReceiverClient.java:[18,12]
> cannot find symbol
> [ERROR] symbol  : class JenkinsCIBuildStatusRecieverServiceStub
> [ERROR] location: class
> org.wso2.carbon.appfactory.jenkins.build.notify.JenkinsCIBuildStatusReceiverClient
> [ERROR]
> /home/amila/temp/AF/af-scratch-code/appfactory/products/appfactory/1.1.0/modules/webapps/appfactory-plugin/src/main/java/org/wso2/carbon/appfactory/jenkins/build/notify/JenkinsCIBuildStatusReceiverClient.java:[5,52]
> cannot find symbol
> [ERROR] symbol  : class JenkinsCIBuildStatusRecieverServiceStub
> [ERROR] location: package org.wso2.carbon.appfactory.jenkins.build.stub
> [ERROR]
> /home/amila/temp/AF/af-scratch-code/appfactory/products/appfactory/1.1.0/modules/webapps/appfactory-plugin/src/main/java/org/wso2/carbon/appfactory/jenkins/build/notify/JenkinsCIBuildStatusReceiverClient.java:[18,12]
> cannot find symbol
> [ERROR] symbol  : class JenkinsCIBuildStatusRecieverServiceStub
> [ERROR] location: class
> org.wso2.carbon.appfactory.jenkins.build.notify.JenkinsCIBuildStatusReceiverClient
> [ERROR]
> /home/amila/temp/AF/af-scratch-code/appfactory/products/appfactory/1.1.0/modules/webapps/appfactory-plugin/src/main/java/org/wso2/carbon/appfactory/jenkins/build/notify/JenkinsCIBuildStatusReceiverClient.java:[22,25]
> cannot find symbol
> [ERROR] symbol  : class JenkinsCIBuildStatusRecieverServiceStub
> [ERROR] location: class
> org.wso2.carbon.appfactory.jenkins.build.notify.JenkinsCIBuildStatusReceiverClient
> [ERROR] -> [Help 1]
>
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Build error on 4.2.0 platform chunk 01(clean repo)

2013-09-11 Thread Janaka Ranabahu
Hi Shameera,

Please note that im getting the following error when trying to build chunk
01 from root level.

janaka@janaka-T530:~/work/wso2/carbon/platform/branches/4.2.0/product-releases/chunk-01$
mvn clean install
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project
org.wso2.carbon:product-releases-service-stubs:4.2.0-chunk01
(/home/janaka/work/wso2/carbon/platform/branches/4.2.0/product-releases/chunk-01/service-stubs/pom.xml)
has 2 errors
[ERROR] Child module
/home/janaka/work/wso2/carbon/platform/branches/4.2.0/product-releases/chunk-01/service-stubs/../../../service-stubs/org.wso2.carbon.input.transport.adaptor.manager.stub/1.0.0/pom.xml
of
/home/janaka/work/wso2/carbon/platform/branches/4.2.0/product-releases/chunk-01/service-stubs/pom.xml
does not exist
[ERROR] Child module
/home/janaka/work/wso2/carbon/platform/branches/4.2.0/product-releases/chunk-01/service-stubs/../../../service-stubs/org.wso2.carbon.output.transport.adaptor.manager.stub/1.0.0/pom.xml
of
/home/janaka/work/wso2/carbon/platform/branches/4.2.0/product-releases/chunk-01/service-stubs/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


Thanks,
Janaka

-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Build failure in 4.2.0 kernel branch {was : Build Failure Trunk}

2013-09-11 Thread Janaka Ranabahu
The previous subject was misleading. Hence sending with the correct
subject. Please note that Im getting the following error while building
4.2.0 kernel.

janaka@janaka-T530:~/work/wso2/carbon/kernel/branches/4.2.0$ mvn clean
install
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.wso2.carbon:SecVerifier:4.2.0
(/home/janaka/work/wso2/carbon/kernel/branches/4.2.0/distribution/integration/security-verifier/pom.xml)
has 1 error
[ERROR] Non-resolvable parent POM: Failure to find
org.wso2.carbon:carbon-products:pom:4.2.0 in
http://repo.maven.apache.org/maven2 was 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]
[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
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
janaka@janaka-T530:~/work/wso2/carbon/kernel/branches/4.2.0$


Thanks,
Janaka

-- Forwarded message ------
From: Janaka Ranabahu 
Date: Wed, Sep 11, 2013 at 1:41 PM
Subject: Re: [Dev] Build Failure Trunk
To: Danushka Fernando , Shameera Rathnayaka <
shame...@wso2.com>, Sameera Jayasoma , Prabath
Siriwardana 
Cc: WSO2 Developers' List 


Hi Shameera,

Please note that I'm getting the same build error on a clean repo. Please
fix this.

Thanks,
Janaka


On Tue, Sep 10, 2013 at 8:30 PM, Danushka Fernando wrote:

> Hi I am getting this build failure at kernal
>
> wdfdo1986@wdfdo1986-ThinkPad-T530:~/Source_Code/kernel/4.2.0$
> oncleannotest
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project org.wso2.carbon:SecVerifier:4.2.0
> (/home/wdfdo1986/Source_Code/kernel/4.2.0/distribution/integration/security-verifier/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM: Failure to find
> org.wso2.carbon:carbon-products:pom:4.2.0 in
> http://repo.maven.apache.org/maven2 was 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]
> [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
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>
> I edited the security-verifier pom's parent details as follows to make the
> build work
> 
> org.wso2.carbon
> integration
> 4.2.0
> ../pom.xml
> 
>
>
> Thanks & Regards
> Danushka Fernando
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

*Lean . Enterprise . Middleware



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


Re: [Dev] Build Failure Trunk

2013-09-11 Thread Janaka Ranabahu
Hi Shameera,

Please note that I'm getting the same build error on a clean repo. Please
fix this.

Thanks,
Janaka


On Tue, Sep 10, 2013 at 8:30 PM, Danushka Fernando wrote:

> Hi I am getting this build failure at kernal
>
> wdfdo1986@wdfdo1986-ThinkPad-T530:~/Source_Code/kernel/4.2.0$
> oncleannotest
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project org.wso2.carbon:SecVerifier:4.2.0
> (/home/wdfdo1986/Source_Code/kernel/4.2.0/distribution/integration/security-verifier/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM: Failure to find
> org.wso2.carbon:carbon-products:pom:4.2.0 in
> http://repo.maven.apache.org/maven2 was 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]
> [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
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>
> I edited the security-verifier pom's parent details as follows to make the
> build work
> 
> org.wso2.carbon
> integration
> 4.2.0
> ../pom.xml
> 
>
>
> Thanks & Regards
> Danushka Fernando
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Getting the NPE while deploying Deployers in 4.2.0 branch

2013-08-28 Thread Janaka Ranabahu
.carbon.bpel.deployer.BPELDeployer} -  Initializing BPEL Deployer
for tenant -1234.
[2013-08-29 10:14:26,647]  INFO
{org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}
-  User Store Configuration Deployer initiated.
[2013-08-29 10:14:26,647]  INFO
{org.wso2.carbon.humantask.deployer.HumanTaskDeployer} -  Initializing
HumanTask Deployer for tenant -1234.
[2013-08-29 10:14:26,723]  INFO
{org.apache.axis2.transport.mail.MailTransportSender} -  MAILTO Sender
started


Thanks,
Janaka

-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


Re: [Dev] Fwd: [Commits] [Carbon-kernel] svn commit r181262 - carbon/kernel/trunk/distribution/kernel

2013-08-19 Thread Janaka Ranabahu
But this change is causing a build failure in trunk. Please check and
confirm.

Thanks,
Janaka


On Mon, Aug 19, 2013 at 4:53 PM, Ajith Vitharana  wrote:

>
>
>
> On Mon, Aug 19, 2013 at 4:48 PM, Janaka Ranabahu  wrote:
>
>> Hi Ajith,
>>
>> Why have we done this change?
>>
>
> After branching(4.2.0) svn externals had point to trunk.
>
> Thanks
> Ajith.
>
>
>>
>> Thanks,
>> Janaka
>>
>>
>> -- Forwarded message --
>> From: 
>> Date: Thu, Aug 15, 2013 at 9:04 PM
>> Subject: [Commits] [Carbon-kernel] svn commit r181262 -
>> carbon/kernel/trunk/distribution/kernel
>> To: comm...@wso2.org
>>
>>
>> Author: aji...@wso2.com
>> Date: Thu Aug 15 21:04:23 2013
>> New Revision: 181262
>> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=181262
>>
>> Log:
>> Fix version issue
>>
>> Modified:
>>carbon/kernel/trunk/distribution/kernel/carbon.product
>>
>> Modified: carbon/kernel/trunk/distribution/kernel/carbon.product
>> URL:
>> http://wso2.org/svn/browse/wso2/carbon/kernel/trunk/distribution/kernel/carbon.product?rev=181262&r1=181261&r2=181262&view=diff
>>
>> ==
>> --- carbon/kernel/trunk/distribution/kernel/carbon.product  (original)
>> +++ carbon/kernel/trunk/distribution/kernel/carbon.product  Thu Aug
>> 15 21:04:23 2013
>> @@ -13,7 +13,7 @@
>> 
>>
>> 
>> -  > version="4.2.0.SNAPSHOT"/>
>> +  
>> 
>>
>>
>> ___
>> Commits mailing list
>> comm...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/commits
>>
>>
>>
>> --
>> *Janaka Ranabahu*
>> Senior Software Engineer; WSO2 Inc.; http://wso2.com*
>>
>> E-mail: jan...@wso2.com
>> **M: **+94 718370861**
>>
>> *Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Fwd: [Commits] [Carbon-kernel] svn commit r181262 - carbon/kernel/trunk/distribution/kernel

2013-08-19 Thread Janaka Ranabahu
Hi Ajith,

Why have we done this change?

Thanks,
Janaka

-- Forwarded message --
From: 
Date: Thu, Aug 15, 2013 at 9:04 PM
Subject: [Commits] [Carbon-kernel] svn commit r181262 -
carbon/kernel/trunk/distribution/kernel
To: comm...@wso2.org


Author: aji...@wso2.com
Date: Thu Aug 15 21:04:23 2013
New Revision: 181262
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=181262

Log:
Fix version issue

Modified:
   carbon/kernel/trunk/distribution/kernel/carbon.product

Modified: carbon/kernel/trunk/distribution/kernel/carbon.product
URL:
http://wso2.org/svn/browse/wso2/carbon/kernel/trunk/distribution/kernel/carbon.product?rev=181262&r1=181261&r2=181262&view=diff
==
--- carbon/kernel/trunk/distribution/kernel/carbon.product  (original)
+++ carbon/kernel/trunk/distribution/kernel/carbon.product  Thu Aug 15
21:04:23 2013
@@ -13,7 +13,7 @@



-  
+  


   
___
Commits mailing list
comm...@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/commits



-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Build failure in Kernel trunk

2013-08-13 Thread Janaka Ranabahu
on - Style Feature ... SKIPPED
[INFO] WSO2 Carbon - Profile Generation .. SKIPPED
[INFO] WSO2 Carbon - Distribution  SKIPPED
[INFO] Distribution-Aggregate  SKIPPED
[INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 1:40.606s
[INFO] Finished at: Wed Aug 14 11:59:38 IST 2013
[INFO] Final Memory: 346M/1727M
[INFO]

[ERROR] Failed to execute goal on project axis2-client: Could not resolve
dependencies for project
org.apache.axis2.wso2:axis2-client:bundle:1.6.1.wso2v10: Failure to find
org.apache.httpcomponents.wso2:httpcore:jar:4.3.0.wso2v1 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 -> [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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :axis2-client


-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


Re: [Dev] Build failure in trunk

2013-08-06 Thread Janaka Ranabahu
m:0.9.0-07262013 in
http://repo.maven.apache.org/maven2 was 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]*
*[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*
*[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException*
*janaka@janaka-T530:~/work/wso2/carbon/platform/trunk$ *


Thanks,
Janaka


On Tue, Aug 6, 2013 at 3:16 PM, Nuwan Bandara  wrote:

> Hi Janaka,
>
> can you take an update at components level, (and features) and build
> jaggery, we have added an external to components.
>
> Regards,
> /Nuwan
>
>
> On Tue, Aug 6, 2013 at 3:05 PM, Janaka Ranabahu  wrote:
>
>> Hi,
>>
>> I'm facing the following issue. Please fix the relative paths
>> accordingly.
>>
>> [INFO] Scanning for projects...
>>
>> [ERROR] The build could not read 8 projects -> [Help 1]
>> [ERROR]
>> [ERROR]   The project org.jaggeryjs:script-engine:0.9.0-07262013
>> (/home/janaka/work/wso2/carbon/platform/trunk/products/jaggery/components/script-engine/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.jaggeryjs:components:pom:0.9.0-07262013 in
>> http://repo.maven.apache.org/maven2 was 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]
>> [ERROR]
>> [ERROR]   The project org.jaggeryjs:hostobjects:0.9.0-07262013
>> (/home/janaka/work/wso2/carbon/platform/trunk/products/jaggery/components/hostobjects/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.jaggeryjs:components:pom:0.9.0-07262013 in
>> http://repo.maven.apache.org/maven2 was 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]
>> [ERROR]
>> [ERROR]   The project org.jaggeryjs:jaggery-core:0.9.0-07262013
>> (/home/janaka/work/wso2/carbon/platform/trunk/products/jaggery/components/jaggery-core/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.jaggeryjs:components:pom:0.9.0-07262013 in
>> http://repo.maven.apache.org/maven2 was 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]
>> [ERROR]
>> [ERROR]   The project org.jaggeryjs:jaggery-admin:0.9.0-07262013
>> (/home/janaka/work/wso2/carbon/platform/trunk/products/jaggery/components/jaggery-admin/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.jaggeryjs:components:pom:0.9.0-07262013 in
>> http://repo.maven.apache.org/maven2 was 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]
>> [ERROR]
>> [ERROR]   The project
>> org.jaggeryjs:org.jaggeryjs.admin.styles.feature:0.9.0-07262013
>> (/home/janaka/work/wso2/carbon/platform/trunk/products/jaggery/features/org.jaggeryjs.admin.styles.feature/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.jaggeryjs:features:pom:0.9.0-07262013 in
>> http://repo.maven.apache.org/maven2 was 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]
>> [ERROR]
>> [ERROR]   The project
>> org.jaggeryjs:org.jaggeryjs.server.feature:0.9.0-07262013
>> (/home/janaka/work/wso2/carbon/platform/trunk/products/jaggery/features/org.jaggeryjs.server.feature/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable pa

[Dev] Build failure in trunk

2013-08-06 Thread Janaka Ranabahu
solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
janaka@janaka-T530:~/work/wso2/carbon/platform/trunk$

Thanks,
Janaka

-- 
*Janaka Ranabahu*
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Naming convention of kernel patches pom

2013-07-16 Thread Janaka Ranabahu
I see that the name of the kernel patch pom is as follows

WSO2 Carbon Kernel Kernel Patch 0001
WSO2 Carbon Kernel Kernel Patch 0003

Is there any specific reason why we have added the version to the name and
why do we have 2 'Kernel' words? IMO the version should be excluded from
the name.

Thanks,
Janaka

-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] [Trunk] Test failures in Axis2

2013-07-16 Thread Janaka Ranabahu
SKIPPED
[INFO] WSO2 Carbon - Carbon Common Feature ... SKIPPED
[INFO] WSO2 Carbon - Carbon Server Feature ... SKIPPED
[INFO] WSO2 Carbon - Carbon UI Feature ... SKIPPED
[INFO] WSO2 Carbon - Carbon Runtime Feature .. SKIPPED
[INFO] WSO2 Carbon - Carbon Feature .. SKIPPED
[INFO] WSO2 Carbon - Student Manager Server Component  SKIPPED
[INFO] WSO2 Carbon - Student Manager UI .. SKIPPED
[INFO] WSO2 Carbon - Student Manager Components .. SKIPPED
[INFO] WSO2 Carbon - Student Manager Server Feature .. SKIPPED
[INFO] WSO2 Carbon - Student Manager UI Feature .. SKIPPED
[INFO] WSO2 Carbon - Student Manager Aggregate Feature ... SKIPPED
[INFO] WSO2 Carbon - Student Manager Features  SKIPPED
[INFO] WSO2 Carbon - Student Manager Feature Repository .. SKIPPED
[INFO] WSO2 Carbon - student Manager Sample .. SKIPPED
[INFO] WSO2 Carbon - Samples . SKIPPED
[INFO] WSO2 Carbon Core - Distribution ... SKIPPED
[INFO] WSO2 Carbon - Integration . SKIPPED
[INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
[INFO] WSO2 Carbon - Integration Core  SKIPPED
[INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
[INFO] WSO2 Carbon - Integration Tests ... SKIPPED
[INFO] WSO2 Carbon - Product Parent .. SKIPPED
[INFO] WSO2 Carbon - UI styles ... SKIPPED
[INFO] WSO2 Carbon - Style Feature ... SKIPPED
[INFO] WSO2 Carbon - Profile Generation .. SKIPPED
[INFO] WSO2 Carbon - Distribution  SKIPPED
[INFO] Distribution-Aggregate  SKIPPED
[INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 13.296s
[INFO] Finished at: Tue Jul 16 15:18:58 IST 2013
[INFO] Final Memory: 70M/874M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.13:test (default-test) on
project axis2-metadata: There are test failures.
[ERROR]
[ERROR] Please refer to
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/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
janaka@janaka-T530:~/work/wso2/carbon/kernel/trunk$


-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


Re: [Dev] WSO2 Developer Studio 3.2.0 Released!

2013-07-16 Thread Janaka Ranabahu
On Tue, Jul 16, 2013 at 1:58 PM, Asanka Sanjeewa  wrote:

> Hi,
>
> On Tue, Jul 16, 2013 at 1:30 PM, Keheliya Gallaba wrote:
>
>> Hi,
>>
>> It will be good to have TOOLS-1626[1] also as a high priority item. There
>> have been few questions on StackOverflow[2][3] about this. We've been
>> suggesting them to go back to Dev Studio 3.0.0 version only for BPEL
>> development due to this.
>>
>> Thanks & Best Regards,
>> Keheliya
>>
>> [1] https://wso2.org/jira/browse/TOOLS-1626
>> [2]
>> http://stackoverflow.com/questions/17547806/wso2-developer-studio-edit-properties-of-an-assign-activity
>> [3]
>> http://stackoverflow.com/questions/17616862/wso2-business-process-bpel-error-in-gui-with-if-component
>>
>>  <https://wso2.org/jira/browse/TOOLS-1413>
>>>>
>>>>
> Developer Studio still uses forked version of Eclipse BPEL editor 0.5.0
> version which does not support with Eclipse Juno release. There are few
> more releases of Eclipse BPEL editor after 0.5.0 (latest is 1.0.3,
> according to [1]). Eclipse BPEL editor 0.8.0 version onwards supports with
> Eclipse Juno. I think if we can fork or use the latest stable version of
> BPEL editor will solve the most of the issues that we are facing with
> Developer Studio BPEL editor.
>
+1 for the idea. Do we know why we have forked the earlier version? Was it
due to some missing features? Please make sure that we do not loose any of
the existing functionality when we move to the newer version.

Thanks,
Janaka

>
> [1] http://download.eclipse.org/bpel/site/
>
> Thanks and Regards,
> AsankaS.
>
>
> *Asanka Sanjeewa*
> Senior Software Engineer
> Mobile: +94772532924
> WSO2 Inc. http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Create gitblit repositories using curl

2013-03-29 Thread Janaka Ranabahu
Hi Punnadi,

Please use the following sample curl request to create repositories using
curl. Please note that you have to set the following parameters in
gitblit.properties file to "true".

web.enableRpcManagement = true
web.enableRpcAdministration = true


 curl --user admin -X POST -H 'content-type: application/json;' --data '{
 "name": "libraries/xmlapache-renamed.git",  "description": "apache xmlrpc
client and server",  "owner": "admin",  "lastChange":
"2010-01-28T22:12:06Z",  "hasCommits": true,  "showRemoteBranches": false,
 "useTickets": false,  "useDocs": false,  "accessRestriction": "VIEW",
 "isFrozen": false,  "showReadme": false,  "federationStrategy":
"FEDERATE_THIS",  "federationSets": ["libraries"  ],  "isFederated":
false,  "skipSizeCalculation": false,  "skipSummaryMetrics": false,
 "size": "102 KB"}' http://127.0.0.1:8080/rpc?req=CREATE_REPOSITORY

Thanks,
Janaka


-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


Re: [Dev] Build failure in 4.1.1 brach

2013-03-24 Thread Janaka Ranabahu
Fixed.

Thanks,
Janaka


On Mon, Mar 25, 2013 at 7:55 AM, Janaka Ranabahu  wrote:

> [INFO]
> 
> [INFO] Building WSO2 Carbon - Deployment Synchronizer Feature 4.1.1
> [INFO]
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> org.wso2.carbon.deployment.synchronizer.feature ---
> [INFO] Deleting
> /home/janaka/work/wso2/carbon/platform/branches/4.1.0/features/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.feature/4.1.1/target
> [INFO]
> [INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
> org.wso2.carbon.deployment.synchronizer.feature ---
> [INFO] Verifying module descriptor ...
> [INFO] Pom descriptor modification detected.
> [INFO] Deleting
> /home/janaka/work/wso2/carbon/platform/branches/4.1.0/features/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.feature/4.1.1/target
> [INFO]
> [INFO] --- carbon-p2-plugin:1.5.2:p2-feature-gen (4-p2-feature-generation)
> @ org.wso2.carbon.deployment.synchronizer.feature ---
> [INFO] Generating feature manifest
> [INFO] Generating feature properties
> [INFO] Generating MANIFEST.MF
> [INFO] Generating Advice file (p2.inf)
> [INFO] Extracting feature
> org.wso2.carbon:org.wso2.carbon.deployment.synchronizer.server.feature
> [INFO] Extracting feature
> org.wso2.carbon:org.wso2.carbon.deployment.synchronizer.subversion.feature
> [INFO] Extracting feature
> org.wso2.carbon:org.wso2.carbon.deployment.synchronizer.git.feature
> [INFO] Generating feature archive:
> /home/janaka/work/wso2/carbon/platform/branches/4.1.0/features/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.feature/4.1.1/target/org.wso2.carbon.deployment.synchronizer.feature-4.1.1.zip
> [INFO]
> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @
> org.wso2.carbon.deployment.synchronizer.feature ---
> [INFO] Installing
> /home/janaka/work/wso2/carbon/platform/branches/4.1.0/features/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.feature/4.1.1/pom.xml
> to
> /home/janaka/.m2/repository/org/wso2/carbon/org.wso2.carbon.deployment.synchronizer.feature/4.1.1/org.wso2.carbon.deployment.synchronizer.feature-4.1.1.pom
> [INFO] Installing
> /home/janaka/work/wso2/carbon/platform/branches/4.1.0/features/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.feature/4.1.1/target/org.wso2.carbon.deployment.synchronizer.feature-4.1.1.zip
> to
> /home/janaka/.m2/repository/org/wso2/carbon/org.wso2.carbon.deployment.synchronizer.feature/4.1.1/org.wso2.carbon.deployment.synchronizer.feature-4.1.1.zip
> [INFO]
>
> [INFO]
> 
> [INFO] Building WSO2 Carbon - Logging Management Core Feature 4.1.1
> [INFO]
> 
> [WARNING] The POM for
> org.wso2.carbon:org.wso2.carbon.logging.service:jar:4.1.1 is missing, no
> dependency information available
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Maven SCM Git Provider - Common library ... SUCCESS [5.472s]
> [INFO] maven-scm.wso2  SUCCESS [2.691s]
> [INFO] httpclient.wso2 ... SUCCESS [0.984s]
> [INFO] Apache Synapse - Secure vault . SUCCESS [3.227s]
> [INFO] Apache Synapse  SUCCESS [2.182s]
> [INFO] Apache Synapse - Commons classes .. SUCCESS [3.632s]
> [INFO] Apache Synapse - Transports ... SUCCESS [0.803s]
> [INFO] Apache Synapse - Non-blocking HTTP/s Transport  SUCCESS [4.147s]
> [INFO] Apache Synapse - PIPE Transport ... SUCCESS [0.869s]
> [INFO] Apache Synapse - VFS Transport  SUCCESS [1.320s]
> [INFO] Apache Synapse - Tasks classes  SUCCESS [1.063s]
> [INFO] Apache Synapse - Core . SUCCESS [9.274s]
> [INFO] Apache Synapse - FIX Transport  SUCCESS [1.863s]
> [INFO] Apache Synapse - Extensions ... SUCCESS [2.048s]
> [INFO] Apache Synapse - Samples .. SUCCESS [2.181s]
> [INFO] Apache Synapse - Patches .. SUCCESS [0.793s]
> [INFO] Apache Synapse - Experimental code  SUCCESS [1.017s]
> [INFO] Apache Synapse - Web Application .. SUCCESS [6.854s]
> [INFO] Apache Synapse - Handler Module ... SUCCESS [2.417s]
> [INFO] Apache Synapse - XAR Maven Plugin . SUCCESS [1.821s]
>

Re: [Dev] Build failure in 4.1.1 branch due to missing features in patch release 4.1.1 features pom

2013-03-24 Thread Janaka Ranabahu
Fixed.

Thanks,
Janaka


On Mon, Mar 25, 2013 at 7:59 AM, Janaka Ranabahu  wrote:

> Hi IsuruW,
>
> Please note $subject.
>
> [INFO] Building WSO2 Carbon - Datasource Management Feature 4.1.1
> [INFO]
> 
> Downloading:
> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.datasource.ui.feature/4.1.1/org.wso2.carbon.datasource.ui.feature-4.1.1.pom
> Downloading:
> http://repo.maven.apache.org/maven2/org/wso2/carbon/org.wso2.carbon.datasource.ui.feature/4.1.1/org.wso2.carbon.datasource.ui.feature-4.1.1.pom
> [WARNING] The POM for
> org.wso2.carbon:org.wso2.carbon.datasource.ui.feature:zip:4.1.1 is missing,
> no dependency information available
> Downloading:
> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.datasource.ui.feature/4.1.1/org.wso2.carbon.datasource.ui.feature-4.1.1.zip
> Downloading:
> http://repo.maven.apache.org/maven2/org/wso2/carbon/org.wso2.carbon.datasource.ui.feature/4.1.1/org.wso2.carbon.datasource.ui.feature-4.1.1.zip
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon - Logging Management Core Feature . SUCCESS [2.709s]
> [INFO] WSO2 Carbon - Logging Management UI Feature ... SUCCESS [0.512s]
> [INFO] WSO2 Carbon - Logging Management Feature .. SUCCESS [0.995s]
> [INFO] WSO2 Carbon - Loadbalancer Endpoint Management Feature  SUCCESS
> [1.663s]
> [INFO] WSO2 Carbon - Autoscaler Feature .. SUCCESS [1.183s]
> [INFO] WSO2 Carbon - NHttp GET Request Processor Feature . SUCCESS [0.143s]
> [INFO] WSO2 Carbon - Datasource Management Core Feature .. SUCCESS [0.184s]
> [INFO] WSO2 Carbon - Datasource Management Feature ... FAILURE
> [12.564s]
> [INFO] WSO2 Carbon - Endpoint Management Core Feature  SKIPPED
> [INFO] WSO2 Carbon - Sequences Management Core Feature ... SKIPPED
> [INFO] WSO2 Carbon - All Mediators Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Message Relay Core Feature .. SKIPPED
> [INFO] WSO2 Carbon - Mediation Initializer Feature ... SKIPPED
> [INFO] WSO2 Carbon - Scheduled Tasks Core Feature  SKIPPED
> [INFO] WSO2 Carbon - Scheduled Tasks Feature . SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Thrift Agent Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature
>  SKIPPED
> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
> [INFO] af-archetype .. SKIPPED
> [INFO] jaxrs-archetype ... SKIPPED
> [INFO] jaxws-archetype ... SKIPPED
> [INFO] jaggery-archetype . SKIPPED
> [INFO] bpel-archetype  SKIPPED
> [INFO] dbs-archetype . SKIPPED
> [INFO] esb-archetype . SKIPPED
> [INFO] php-archetype . SKIPPED
> [INFO] WSO2 AppFacotry - Parent .. SKIPPED
> [INFO] WSO2 AppFactory - Archetype For Applications .. SKIPPED
> [INFO] BPEL Parent ... SKIPPED
> [INFO] UserCreation .. SKIPPED
> [INFO] UserActivation  SKIPPED
> [INFO] ApplicationCreation ... SKIPPED
> [INFO] AddUserToApplication .. SKIPPED
> [INFO] CreateArtifact  SKIPPED
> [INFO] DeployArtifact  SKIPPED
> [INFO] DeployToStage . SKIPPED
> [INFO] UserCreationHT  SKIPPED
> [INFO] GovernanceBPEL  SKIPPED
> [INFO] UserApprovalTask .. SKIPPED
> [INFO] WSO2 AppFacotry - P2 Profile Generation Parent  SKIPPED
> [INFO] WSO2 AppFacotry - P2 Profile Generation ... SKIPPED
> [INFO] WSO2 AppFactory - Application Management Web Application  SKIPPED
> [INFO] appfactory-authentication-plugin .. SKIPPED
> [INFO] appfactory-plugin . SKIPPED
> [INFO] Web Apps parent ... SKIPPED
> [INFO] scm-carbon-auth-plugin  SKIPPED
> [INFO] SCM Web App ... SKIPPED
> [INFO] WSO2 AppFacotry - Distribution Parent . SKIPPED
> [INFO] WSO2 AppFacotry - Distribution  SKIPPED
> [INFO] WSO2 Carbon - Patch releases - products - Aggrega

[Dev] Build failure in 4.1.1 branch due to missing features in patch release 4.1.1 features pom

2013-03-24 Thread Janaka Ranabahu
.carbon.datasource.feature: Could not resolve dependencies for
project org.wso2.carbon:org.wso2.carbon.datasource.feature:pom:4.1.1: Could
not find artifact
org.wso2.carbon:org.wso2.carbon.datasource.ui.feature:zip:4.1.1 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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :org.wso2.carbon.datasource.feature


Thanks,
Janaka

-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Build failure in 4.1.1 brach

2013-03-24 Thread Janaka Ranabahu
 Data Bridge - Data Publisher Aggregate Feature  SKIPPED
[INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
[INFO] af-archetype .. SKIPPED
[INFO] jaxrs-archetype ... SKIPPED
[INFO] jaxws-archetype ... SKIPPED
[INFO] jaggery-archetype . SKIPPED
[INFO] bpel-archetype  SKIPPED
[INFO] dbs-archetype . SKIPPED
[INFO] esb-archetype . SKIPPED
[INFO] php-archetype . SKIPPED
[INFO] WSO2 AppFacotry - Parent .. SKIPPED
[INFO] WSO2 AppFactory - Archetype For Applications .. SKIPPED
[INFO] BPEL Parent ... SKIPPED
[INFO] UserCreation .. SKIPPED
[INFO] UserActivation  SKIPPED
[INFO] ApplicationCreation ... SKIPPED
[INFO] AddUserToApplication .. SKIPPED
[INFO] CreateArtifact  SKIPPED
[INFO] DeployArtifact  SKIPPED
[INFO] DeployToStage . SKIPPED
[INFO] UserCreationHT  SKIPPED
[INFO] GovernanceBPEL  SKIPPED
[INFO] UserApprovalTask .. SKIPPED
[INFO] WSO2 AppFacotry - P2 Profile Generation Parent  SKIPPED
[INFO] WSO2 AppFacotry - P2 Profile Generation ... SKIPPED
[INFO] WSO2 AppFactory - Application Management Web Application  SKIPPED
[INFO] appfactory-authentication-plugin .. SKIPPED
[INFO] appfactory-plugin . SKIPPED
[INFO] Web Apps parent ... SKIPPED
[INFO] scm-carbon-auth-plugin  SKIPPED
[INFO] SCM Web App ... SKIPPED
[INFO] WSO2 AppFacotry - Distribution Parent . SKIPPED
[INFO] WSO2 AppFacotry - Distribution  SKIPPED
[INFO] WSO2 Carbon - Patch releases - products - Aggregator Module  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 6:15.777s
[INFO] Finished at: Mon Mar 25 07:43:58 IST 2013
[INFO] Final Memory: 1093M/1972M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.logging.mgt.server.feature: Could not resolve dependencies
for project
org.wso2.carbon:org.wso2.carbon.logging.mgt.server.feature:pom:4.1.1: The
repository system is offline but the artifact
org.wso2.carbon:org.wso2.carbon.logging.service:jar:4.1.1 is not available
in the local repository. -> [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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :org.wso2.carbon.logging.mgt.server.feature
janaka@janaka-T530
:~/work/wso2/carbon/platform/branches/4.1.0/patch-releases/4.1.1$

Thanks,
Janaka

-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


Re: [Dev] Trying to set the domain from 86 to -1234, error noticed in AppServer 5.0.2 cartridge

2013-03-16 Thread Janaka Ranabahu
Thanks All,

@S2 team,

Could you please add this fix to the S2 AS 5.0.2 cartridge?

Thanks,
Janaka


On Sat, Mar 16, 2013 at 9:45 PM, Supun Malinga  wrote:

> Hi,
>
> We got similar error coming from
> DeploymentInterceptor.serviceGroupUpdate() method in AS 5.1.0 testing and
> fixed. I believe the same fix would work here.
> Please refer https://wso2.org/jira/browse/WSAS-1194.
> Fix revision is 167585.
>
> thanks,
>
>
>
> On Sat, Mar 16, 2013 at 6:28 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> AS 5.0.2 does not include support for GIT based dep synch. Is it patched
>> with it?
>>
>> If so we need to check the CarbonContext usage in it. That may
>> be causing this.
>>
>> On Sat, Mar 16, 2013 at 5:41 PM, Janaka Ranabahu  wrote:
>>
>>> Hi Sajith,
>>>
>>> Noticed the following error in the AppServer 5.0.2 cartridge. This
>>> happened couple of times.
>>>
>>> TID: [0] [AS] [2013-03-16 11:46:51,641]  INFO
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>>>  'ad...@admin.com@dimwar2 [86]' logged in at [2013-03-16
>>> 11:46:51,640+]
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
>>> TID: [0] [AS] [2013-03-16 11:46:52,576] ERROR
>>> {org.wso2.carbon.context.internal.CarbonContextDataHolder} -  Trying to set
>>> the domain from 86 to -1234
>>> {org.wso2.carbon.context.internal.CarbonContextDataHolder}
>>> java.lang.IllegalStateException: Trying to set the domain from 86 to
>>> -1234
>>> at
>>> org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1666)
>>>  at
>>> org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:209)
>>> at
>>> org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:198)
>>>  at
>>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceGroupUpdate(DeploymentInterceptor.java:112)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:677)
>>>  at
>>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:342)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:335)
>>>  at
>>> org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:178)
>>> at org.apache.axis2.client.ServiceClient.(ServiceClient.java:143)
>>>  at
>>> org.wso2.carbon.hosting.repository.information.RepositoryInformationServiceStub.(RepositoryInformationServiceStub.java:111)
>>> at
>>> org.wso2.carbon.hosting.repository.information.RepositoryInformationServiceStub.(RepositoryInformationServiceStub.java:97)
>>>  at
>>> org.wso2.carbon.hosting.repository.information.RepositoryInformationServiceStub.(RepositoryInformationServiceStub.java:146)
>>> at
>>> org.wso2.carbon.deployment.synchronizer.git.internal.RepositoryInformationServiceClient.(RepositoryInformationServiceClient.java:23)
>>>  at
>>> org.wso2.carbon.deployment.synchronizer.git.GitBasedArtifactRepository.initGitContext(GitBasedArtifactRepository.java:77)
>>> at
>>> org.wso2.carbon.deployment.synchronizer.git.GitBasedArtifactRepository.init(GitBasedArtifactRepository.java:52)
>>>  at
>>> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.newCarbonRepositorySynchronizer(CarbonRepositoryUtils.java:69)
>>> at
>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver.creatingConfigurationContext(DeploymentSyncAxis2ConfigurationContextObserver.java:50)
>>>  at
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.doPreConfigContextCreation(TenantAxisUtils.java:464)
>>> at
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:281)
>>>  at
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:118)
>>> at
>>> org.wso2.carbon.core.AbstractAdmin.getConfigContext(AbstractAdmin.java:79)
>>>  at
>>> org.wso2.carbon.webapp.mgt.WebappAdmin.getWebappsHolder(WebappAdmin.java:317)
>>> at
>>> org.wso2.carbon.webapp.mgt.WebappAdmin.getStartedWebapp(WebappAdmin.java:105)
>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:

[Dev] Trying to set the domain from 86 to -1234, error noticed in AppServer 5.0.2 cartridge

2013-03-16 Thread Janaka Ranabahu
va:57)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
 at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
 at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
 at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
 at
org.eclipse.equinox.http.helper.FilterServletAdaptor$FilterChainImpl.doFilter(FilterServletAdaptor.java:56)
at
org.wso2.carbon.mashup.jsservices.custom.ui.CustomUIServletFilter.doFilter(CustomUIServletFilter.java:233)
 at
org.eclipse.equinox.http.helper.FilterServletAdaptor.service(FilterServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
 at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:172)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
 at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
 at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AS] [2013-03-16 11:46:52,779]  INFO
{org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
 Doing initial sync up...
{org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
TID: [0] [AS] [2013-03-16 11:46:52,779]  INFO
{org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
 Checking out...
{org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
TID: [0] [AS] [2013-03-16 11:46:52,788]  INFO
{org.wso2.carbon.deployment.synchronizer.git.GitBasedArtifactRepository} -
 Existing git repository detected for tenant 86, no clone required
{org.wso2.carbon.deployment.synchronizer.git.GitBasedArtifactRepository}


-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] [Urgent]Have we done the 4.1.0 branching correctly?

2013-03-14 Thread Janaka Ranabahu
Hi,

I see that the version of the org.wso2.carbon.hostobjects.carbonutil/4.1.0
bundle is set to 1.0.1. Please refer [1]. But please note that this version
is already released and can be found in [2].

Have we done the versions correctly when we branched 4.1.0. Please check
and confirm.

Thanks,
Janaka


[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/hostobjects/org.wso2.carbon.hostobjects.carbonutil/4.1.0/pom.xml
[2]
http://dist.wso2.org/maven2/org/wso2/carbon/org.wso2.carbon.hostobjects.carbonutil/1.0.1/

-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Seeing exceptions when trying to deploy an application to S2

2013-03-13 Thread Janaka Ranabahu
che.catalina.tribes.group.GroupChannel.send(GroupChannel.java:224)
 at
org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:182)
at
org.apache.axis2.clustering.tribes.ChannelSender.sendToGroup(ChannelSender.java:65)
 at
org.apache.axis2.clustering.management.DefaultGroupManagementAgent.send(DefaultGroupManagementAgent.java:108)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.createAndSendClusterMessage(RepoNotificationService.java:135)
 at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.handleRepoSynch(RepoNotificationService.java:68)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.synchronize(RepoNotificationService.java:60)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
 at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
 at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
 at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
 at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
 at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
org.wso2.carbon.hosting.reponotification.stub.RepoNotificationServiceStub.synchronize(RepoNotificationServiceStub.java:199)
at
org.wso2.carbon.cartridge.mgt.ui.RepoNotificationClient.synchronize(RepoNotificationClient.java:39)
 at
org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet.doPost(RepoNotificationServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
 at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:172)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
 at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
 at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)


-- 
*Janaka Ranabahu*
Member - Solutions Management Committ

[Dev] WSO2 App Factory v1.0.0 Alpha1 Released!

2013-02-27 Thread Janaka Ranabahu
*WSO2 App Factory v1.0.0 Alpha1 Released!*
27th February, 2013


The WSO2 App Factory team is pleased to announce the release of 1.0.0 Alpha
1 version of WSO2 App Factory.
The pre-configured virtual machine could be downloaded from here
[1]<http://dist.wso2.org/solutions/app-factory/alpha1/wso2appfactory-vm-1.0.0_alpha1.zip>
or
through the product home page [2] <http://wso2.com/solutions/app-factory/>.


*How to Run*

Download the virtual machine. The servers start automatically when the VM
boot up.



*Key Features*

   - Lifecycle management of an application
   - Automated build and deployment
   - Support multiple application versions
   - APIs to integrate with SDLC Tool chain
   - SVN/GIT repository provisioning
   - Out of the box integration with Jenkins, Redmine
   - Integrated with WSO2 API Manager
   - Role based views
   - Dashboards to monitor application development
   - CIO/CEO dashboards
   - Dependency management - API sandboxing
   - Download logs
   - Approval UI and human tasks
   - Event Stream View
   - Resource Dependency Management UI

*
*
*New Features*

   - Publish the war end point URLs
   - Implement tagged promotions
   - External User store - LDAP
   - Ability to disable email verification
   - Application dashboard
   - Integration to WSO2 Storage Server
   - Improved permission model
   - Performance improvements

*
*
*Issues Fixed*

https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10924



*Known issues*
*
*

https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10925



*Report Problems*

Issues can be reported using the public JIRA available at
https://wso2.org/jira/browse/APPFAC



*Contact us*

WSO2 App Factory developers can be contacted via the mailing lists:
For Users: http://stackoverflow.com/questions/tagged/wso2
For Developers: dev@wso2.org
For details on subscriptions see http://wso2.org/mail

Product home page : http://wso2.com/solutions/app-factory/

-The WSO2 App Factory Team

[1]
http://dist.wso2.org/solutions/app-factory/alpha1/wso2appfactory-vm-1.0.0_alpha1.zip
[2] http://wso2.com/solutions/app-factory/

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] build error : gitbilt orbit bundle

2013-02-19 Thread Janaka Ranabahu
Hi Pradeep,

What was the build error?

Thanks,
Janaka


On Tue, Feb 19, 2013 at 12:58 PM, Pradeep Fernando  wrote:

> Hi Janaka,
>
> I came across the above build failure. Manoj will provide you with a patch.
>
> --Pradeep
>



-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


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

2013-02-17 Thread Janaka Ranabahu
Hi Senaka,

Have we fixed this issue? There were lots of debate going on at that time
whether we should fix this for C4 but we haven't done so. Are you guys
planning to fix this for C5?

Thanks,
Janaka


On Tue, Jul 17, 2012 at 5:24 PM, Senaka Fernando  wrote:

> Hi Janaka,
>
> Let's review the TODO list after this release and decide.
>
> Thanks,
> Senaka.
>
>
> On Tue, Jul 17, 2012 at 1:17 AM, Janaka Ranabahu  wrote:
>
>> Hi Senaka,
>>
>> On Tue, Jul 17, 2012 at 9:34 AM, Janaka Ranabahu  wrote:
>>
>>> Hi Senaka,
>>>
>>> On Tue, Jul 17, 2012 at 4:52 AM, Senaka Fernando wrote:
>>>
>>>> Hi Janaka,
>>>>
>>>> Are you suggesting that this needs to be done for C4? Or is this e-mail
>>>> FTR?
>>>>
>>> We are not in a position to do this for C4. But if we are doing a patch
>>> release in the kernel before C5, then my strong belief is that we should
>>> fix this in that patch release.
>>>
>>
>> Also please note that this behavior causes multiple database calls for a
>> single resource update operation. In a fairly concurrent scenario, this
>> leads to performance issues because of the number of database
>> calls happening. Fixing this can improve the performance of the registry in
>> some extent.
>>
>> WDYT?
>>
>> Thanks,
>> Janaka
>>
>>>
>>> Thanks,
>>> Janaka
>>>
>>>>
>>>> Thanks,
>>>> Senaka.
>>>>
>>>> On Mon, Jul 16, 2012 at 3:40 PM, Janaka Ranabahu wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I have noticed that the property handling in registry core is not done
>>>>> properly. The ResourceDAO interface(which is the data access object for
>>>>> resources) has only 2 methods which is related to properties and that is 
>>>>> to
>>>>> add properties and remove properties[1]. I have noticed that we call the
>>>>> add properties method for both resource add and update operations. In 
>>>>> other
>>>>> words, for each add or update operation of a resource, we insert all its
>>>>> properties again to the database. This behavior is there even if we turn
>>>>> off resource versioning.
>>>>>
>>>>> IMO, this is an critical issue and it can lead to unnecessary database
>>>>> growth. Also note that this causes unnecessary calls to the database too.
>>>>> To insert a single property, we use 3 queries and because of that 3
>>>>> database calls happens. This number multiplies by the number of properties
>>>>> for that resource. If we had 10 properties for a resource, the registry
>>>>> core will do additional 30 database calls when the resource get
>>>>> updated. Because of this reason, the REG_PROPERTY and
>>>>> REG_RESOURCE_PROPERTY tables keep growing.
>>>>>
>>>>> Please note that this is one of the reasons why we see a performance
>>>>> degradation when we connect to a remote database and do certain operations
>>>>> like lifecycle management(since it uses properties to hold certain
>>>>> information). AFAIK, most of our products use registry properties to store
>>>>> various information and because of that this is a critical issue that 
>>>>> needs
>>>>> to be fixed.
>>>>>
>>>>> Thanks,
>>>>> Janaka
>>>>>
>>>>> https://wso2.org/jira/browse/REGISTRY-870
>>>>>
>>>>> [1]
>>>>> https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/org.wso2.carbon.registry.core/src/main/java/org/wso2/carbon/registry/core/dao/ResourceDAO.java
>>>>>
>>>>> --
>>>>> Janaka Ranabahu
>>>>> Software Engineer
>>>>> WSO2 Inc.
>>>>>
>>>>> Mobile +94 718370861
>>>>> Email : jan...@wso2.com
>>>>> Blog : janakaranabahu.blogspot.com
>>>>>
>>>>>
>>>>> ___
>>>>> Architecture mailing list
>>>>> architect...@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Senaka Fernando*
>>>> Member - Integration Technologies Management Committee;
&g

Re: [Dev] Why does new jaggery apps added to release API manager products

2013-01-28 Thread Janaka Ranabahu
Hi Lalaji,

Even though this is fixed in later versions, for all the patch releases,
the apimgt 1.0.0 version will checkout the corresponding jaggery apps. Is
it possible to fix this?

Thanks,
Janaka


On Tue, Jan 29, 2013 at 12:03 AM, Lalaji Sureshika  wrote:

> Hi Janaka,
>
> In apimgt 1.0.0 product version,the svn extern for jaggery-apps has set as
> below.
>
> api-store-web
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/components/apimgt/api-store-web
> api-publisher-web
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/components/apimgt/api-publisher-web
>
> Because of that all the branched app versions inside the folders of  both
> apps are getting included when taking a svn up of apimgt 1.0.0. However
> this is fixed with later AM product released versions..
>
> Thanks;
>
>
> On Mon, Jan 28, 2013 at 10:39 PM, Janaka Ranabahu  wrote:
>
>> Hi Api Manager team,
>>
>> I see the following kind of logs when doing a svn update. Please correct
>> these kinds of svn externals.
>>
>> Aproducts/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5
>> /src/modules/user
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5/src/modules/user/module.jag
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5/src/modules/user/login.jag
>> A
>>  products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5/src/apis
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5/src/jaggery.conf
>> Aproducts/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7
>> A
>>  products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src
>> A
>>  products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/run.jag
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/users
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/users/login.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/users/users.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/subscriptions
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/subscriptions/subscriptions.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/docs
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/docs/add.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/docs/list.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/docs/remove.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis/add.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis/copy.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis/list.js
>>  A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis/update.js
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/tests.json
>> A
>>  
>> products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/utils.js
>> A
>>  products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/site
>>
>> Thanks,
>> Janaka
>>
>> --
>> Janaka Ranabahu
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Mobile +94 718370861
>> Email : jan...@wso2.com
>> Blog : janakaranabahu.blogspot.com
>>
>
>
>
> --
> Lalaji Sureshika
> Software Engineer; Development Technologies Team;WSO2, Inc.;
> http://wso2.com/
> email: lal...@wso2.com; cell: +94 71 608 6811
> blog: http://lalajisureshika.blogspot.com
>
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] Why does new jaggery apps added to release API manager products

2013-01-28 Thread Janaka Ranabahu
Hi Api Manager team,

I see the following kind of logs when doing a svn update. Please correct
these kinds of svn externals.

Aproducts/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5
/src/modules/user
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5/src/modules/user/module.jag
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5/src/modules/user/login.jag
A
 products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5/src/apis
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.5/src/jaggery.conf
Aproducts/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7
Aproducts/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src
A
 products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/run.jag
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/users
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/users/login.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/users/users.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/subscriptions
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/subscriptions/subscriptions.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/docs
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/docs/add.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/docs/list.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/docs/remove.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis/add.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis/copy.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis/list.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/core/apis/update.js
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/tests.json
A
 
products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/tests/utils.js
A
 products/apimgt/1.0.0/modules/jaggery-apps/api-publisher-web/1.0.7/src/site

Thanks,
Janaka

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Do we allow creating roles without users?

2013-01-27 Thread Janaka Ranabahu
Hi,

Thanks Hasini. I've set the correct parameter value and It worked without
any issue.

Thanks,
Janaka


On Mon, Jan 28, 2013 at 9:16 AM, Hasini Gunasinghe  wrote:

> Hi Janaka,
>
> Based on the underlying LDAP user store, you need to configure  name="EmptyRolesAllowed">true accordingly.
> For eg: in embedded LDAP, we have changed the schema to allow empty roles.
> However, if you are connecting to an external LDAP, most of the time, empty
> roles are not allowed. So based, on that, you need to configure above
> property.
>
> Thanks,
> Hasini.
>
>
> On Mon, Jan 28, 2013 at 8:44 AM, Janaka Ranabahu  wrote:
>
>> Hi,
>>
>> Do we allow creating roles without any users, through the API? I went
>> through the org.wso2.carbon.user.api.UserStoreManager interface but could
>> not find anything related in the comments.
>>
>> I have noticed that API Manager components have added roles without any
>> users(in APIManagerComponent class).
>>
>> *manager.addRole(role, null, null);*
>>
>>  But this code failed when I tried to connect API Manager to
>> AppFactory(same LDAP). The exception says that we can not create a role
>> without a user.
>>
>> *Caused by: org.wso2.carbon.user.core.UserStoreException: Can not create
>> empty role. There should be at least one user for the role.*
>> * at
>> org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager.doAddRole(ReadWriteLDAPUserStoreManager.java:968)
>> *
>>
>> Therefore, I wan't to clarify whether it is possible to create roles
>> without users.
>>
>> Thanks,
>> Janaka
>>
>> --
>> Janaka Ranabahu
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Mobile +94 718370861
>> Email : jan...@wso2.com
>> Blog : janakaranabahu.blogspot.com
>>
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] Do we allow creating roles without users?

2013-01-27 Thread Janaka Ranabahu
Hi,

Do we allow creating roles without any users, through the API? I went
through the org.wso2.carbon.user.api.UserStoreManager interface but could
not find anything related in the comments.

I have noticed that API Manager components have added roles without any
users(in APIManagerComponent class).

*manager.addRole(role, null, null);*

But this code failed when I tried to connect API Manager to AppFactory(same
LDAP). The exception says that we can not create a role without a user.

*Caused by: org.wso2.carbon.user.core.UserStoreException: Can not create
empty role. There should be at least one user for the role.*
* at
org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager.doAddRole(ReadWriteLDAPUserStoreManager.java:968)
*

Therefore, I wan't to clarify whether it is possible to create roles
without users.

Thanks,
Janaka

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


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

2013-01-16 Thread Janaka Ranabahu
Hi Dileepa,


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

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

Thanks,
Janaka

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


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Build Failed for https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0

2013-01-07 Thread Janaka Ranabahu
ndes - UI  SKIPPED
> [INFO] WSO2 Carbon - Feature - Andes . SKIPPED
> [INFO] WSO2 Carbon - Loadbalancer Endpoint Management Feature  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Commons Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Thrift Commons Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Core Server Feature ... SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Thrift Agent Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Thrift Reciever Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - REST API Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature
> SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Data Receiver Aggregate Feature  SKIPPED
> [INFO] WSO2 Carbon - AppFactory Server Feature ... SKIPPED
> [INFO] WSO2 Carbon - Proxy Services Core Feature . SKIPPED
> [INFO] WSO2 Carbon - Proxy Services Feature .. SKIPPED
> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
> [INFO] WSO2 Carbon - Patch releases - samples - Aggregator Module  SKIPPED
> [INFO] WSO2 Identity Server .. SKIPPED
> [INFO] WSO2 IS - Features Aggregator Module .. SKIPPED
> [INFO] WSO2 IS - Style Features .. SKIPPED
> [INFO] WSO2 IS - Utils Features .. SKIPPED
> [INFO] WSO2 Cloud Identity - Tenant Configuration User Interface  SKIPPED
> [INFO] WSO2 Carbon - Identity UI Feature . SKIPPED
> [INFO] WSO2 IS - IS Profile Generation ... SKIPPED
> [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: 4:58.036s
> [INFO] Finished at: Tue Jan 08 10:05:57 IST 2013
> [INFO] Final Memory: 634M/1296M
> [INFO]
> 
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.appfactory.repository.mgt.service: Could not resolve
> dependencies for project
> org.wso2.carbon:org.wso2.carbon.appfactory.repository.mgt.service:bundle:1.0.2:
> Failure to find com.gitblit:gitblit:jar:1.2.0.wso2v1 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 -> [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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf
> :org.wso2.carbon.appfactory.repository.mgt.service
>
>
>
> On Mon, Jan 7, 2013 at 4:24 PM, Vijitha Kumara  wrote:
>
>>
>>
>> On Mon, Jan 7, 2013 at 3:53 PM, Chanaka Fernando wrote:
>>
>>> [ERROR] Failed to execute goal on project
>>> org.wso2.carbon.appfactory.repository.mgt.service: Could not resolve
>>> dependencies for project
>>> org.wso2.carbon:org.wso2.carbon.appfactory.repository.mgt.service:bundle:1.0.2:
>>> Could not find artifact com.gitblit:gitblit:jar:1.2.0.wso2v1 in wso2-nexus (
>>> http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1]
>>>
>>
>> You need to update the Orbit and build.
>>
>>
>>
>>
>>
>>
>> --
>> Vijitha Kumara
>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>> email: viji...@wso2.com
>>
>> Lean . Enterprise . Middleware
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Build Failed for https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0

2013-01-07 Thread Janaka Ranabahu
. SKIPPED
>> [INFO] Identity SAML Single Sign-on Server Feature ... SKIPPED
>> [INFO] Identity SAML2 Single Sign-on UI Feature .. SKIPPED
>> [INFO] Identity SAML2.0 Single Sign-on Feature ... SKIPPED
>> [INFO] SAML2 based authenticator UI Feature .. SKIPPED
>> [INFO] SAML2 based Single Sign-On authenticator Feature .. SKIPPED
>> [INFO] WSO2 Stratos - Common UI Feature .. SKIPPED
>> [INFO] WSO2 Stratos - Common Core Feature  SKIPPED
>> [INFO] WSO2 Stratos - Common Composite Feature ... SKIPPED
>> [INFO] WSO2 Stratos - Stratos SSO Management UI Feature .. SKIPPED
>> [INFO] WSO2 Stratos - Stratos SSO Management Feature . SKIPPED
>> [INFO] Identity OAuth Common Feature . SKIPPED
>> [INFO] Identity OAuth Server Feature . SKIPPED
>> [INFO] Identity OAuth UI Feature . SKIPPED
>> [INFO] WSO2 Carbon - OAuth Mediation Feature . SKIPPED
>> [INFO] Identity OAuth Feature  SKIPPED
>> [INFO] WSO2 Carbon - Feature - Andes - Server  SKIPPED
>> [INFO] WSO2 Carbon - Feature - Andes - UI  SKIPPED
>> [INFO] WSO2 Carbon - Feature - Andes . SKIPPED
>> [INFO] WSO2 Carbon - Loadbalancer Endpoint Management Feature  SKIPPED
>> [INFO] WSO2 Carbon - Data Bridge - Commons Server Feature  SKIPPED
>> [INFO] WSO2 Carbon - Data Bridge - Thrift Commons Server Feature  SKIPPED
>> [INFO] WSO2 Carbon - Data Bridge - Core Server Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Data Bridge - Thrift Agent Server Feature  SKIPPED
>> [INFO] WSO2 Carbon - Data Bridge - Thrift Reciever Server Feature  SKIPPED
>> [INFO] WSO2 Carbon - Data Bridge - REST API Server Feature  SKIPPED
>> [INFO] WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature
>> SKIPPED
>> [INFO] WSO2 Carbon - Data Bridge - Data Receiver Aggregate Feature
>> SKIPPED
>> [INFO] WSO2 Carbon - AppFactory Server Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Proxy Services Core Feature . SKIPPED
>> [INFO] WSO2 Carbon - Proxy Services Feature .. SKIPPED
>> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module
>> SKIPPED
>> [INFO] WSO2 Carbon - Patch releases - samples - Aggregator Module  SKIPPED
>> [INFO] WSO2 Identity Server .. SKIPPED
>> [INFO] WSO2 IS - Features Aggregator Module .. SKIPPED
>> [INFO] WSO2 IS - Style Features .. SKIPPED
>> [INFO] WSO2 IS - Utils Features .. SKIPPED
>> [INFO] WSO2 Cloud Identity - Tenant Configuration User Interface  SKIPPED
>> [INFO] WSO2 Carbon - Identity UI Feature . SKIPPED
>> [INFO] WSO2 IS - IS Profile Generation ... SKIPPED
>> [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: 4:58.036s
>> [INFO] Finished at: Tue Jan 08 10:05:57 IST 2013
>> [INFO] Final Memory: 634M/1296M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.appfactory.repository.mgt.service: Could not resolve
>> dependencies for project
>> org.wso2.carbon:org.wso2.carbon.appfactory.repository.mgt.service:bundle:1.0.2:
>> Failure to find com.gitblit:gitblit:jar:1.2.0.wso2v1 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 -> [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,
>&

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #19 has FAILED (1 tests failed, no failures were new). Change made by janaka.

2013-01-06 Thread Janaka Ranabahu
Hi,

The reason for this is that orbit patch release 4.0.6 is not been built.
Please add it to the build if it is already not there.

Thanks,
Janaka


On Mon, Jan 7, 2013 at 12:18 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 Carbon 
> 4.0.x<http://wso2.org/bamboo/browse/WCB001/>› Platform
> 4.0.6 <http://wso2.org/bamboo/browse/WCB001-PLA006/> › 
> #19<http://wso2.org/bamboo/browse/WCB001-PLA006-19/>
> failed
>
> Changes by janaka <http://wso2.org/bamboo/browse/author/janaka>
>
> *1/888* tests failed.
>Responsible No one is responsible for this build.
>Failing Jobs <http://wso2.org/bamboo/browse/WCB001-PLA006-19/> Job
> Duration Tests[image: Failed]  Default 
> Job<http://wso2.org/bamboo/browse/WCB001-PLA006-JOB1-19/> (Default
> Stage)  9 minutes  1 of 888 failed  
> Logs<http://wso2.org/bamboo/browse/WCB001-PLA006-JOB1-19/log>|
> Artifacts <http://wso2.org/bamboo/browse/WCB001-PLA006-JOB1-19/artifact> 
> Code
> Changes <http://wso2.org/bamboo/browse/WCB001-PLA006-19/commit/>  View
> full change details<http://wso2.org/bamboo/browse/WCB001-PLA006-19/commit/>
> janaka <http://wso2.org/bamboo/browse/author/janaka>
> Adding the GITBlitBasedGITRepositoryProvider with the use of the gitblit
> orbit bundle
>  152831 Tests <http://wso2.org/bamboo/browse/WCB001-PLA006-19/test>  View
> full test details <http://wso2.org/bamboo/browse/WCB001-PLA006-19/test>   1
> Existing Test Failures   Test Job MultipleDefinitionConversionTest
> multipleDefnConversionFromJSON<http://wso2.org/bamboo/browse/WCB001-PLA006-JOB1-19/test/case/41485811>
>   Default
> Job <http://wso2.org/bamboo/browse/WCB001-PLA006-JOB1-19/test> View
> Online <http://wso2.org/bamboo/browse/WCB001-PLA006-19> | Add 
> Comments<http://wso2.org/bamboo/browse/WCB001-PLA006-19?commentMode=true>
>
> This message was sent by Atlassian Bamboo <http://wso2.org/bamboo>.
>
> If you wish to stop receiving these emails edit your user 
> profile<http://wso2.org/bamboo/profile/userNotifications.action>or notify
> your administrator <http://wso2.org/bamboo/viewAdministrators.action>.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] Compilation error when building Kernel

2013-01-06 Thread Janaka Ranabahu
Hi,

Im getting the following compilation error. Please note that my revision
is 152836.


[INFO] Compiling 75 source files to
/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/kernel/branches/4.0.0/core/org.wso2.carbon.user.core/4.0.6/target/classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/kernel/branches/4.0.0/core/org.wso2.carbon.user.core/4.0.6/src/main/java/org/wso2/carbon/user/core/common/DefaultRealmService.java:[189,18]
cannot find symbol
symbol  : method clearFromCache(int,java.lang.String)
location: class org.wso2.carbon.caching.core.realm.RealmCache
[INFO] 1 error
[INFO] -
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Carbon - Aggregate Pom ... SUCCESS [1.450s]
[INFO] WSO2 Carbon - Patch releases - dependencies - Aggregator Module
 SUCCESS [0.390s]
[INFO] WSO2 Carbon - Patch releases - service-stubs - Aggregator Module
 SUCCESS [0.150s]
[INFO] WSO2 Carbon - carbon tomcat bundle  SUCCESS [47.897s]
[INFO] WSO2 Carbon - Kernel .. SUCCESS
[10:18.177s]
[INFO] WSO2 Carbon - User Manager Kernel . FAILURE
[1:25.520s]

Thanks,
Janaka

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] org.wso2.carbon:org.wso2.carbon.identity.oauth.mediator:jar:4.0.6 is not included in the build

2013-01-02 Thread Janaka Ranabahu
Hi,

Getting the following error due to this. Is there any reason for this. If
not shall I include it in the build.

[INFO] WSO2 Stratos - Stratos SSO Management Feature . SUCCESS [3.699s]
[INFO] Identity OAuth Common Feature . SUCCESS [0.436s]
[INFO] Identity OAuth Server Feature . SUCCESS [9.977s]
[INFO] Identity OAuth UI Feature . SUCCESS
[15:23.845s]
[INFO] WSO2 Carbon - OAuth Mediation Feature . FAILURE [2.345s]
[INFO] Identity OAuth Feature  SKIPPED
[INFO] WSO2 Carbon - Feature - Andes - Server  SKIPPED
[INFO] WSO2 Carbon - Feature - Andes - UI  SKIPPED
[INFO] WSO2 Carbon - Feature - Andes . SKIPPED
[INFO] WSO2 Carbon - Loadbalancer Endpoint Management Feature  SKIPPED
[INFO] WSO2 Carbon - Data Bridge - Commons Server Feature  SKIPPED
[INFO] WSO2 Carbon - Data Bridge - Thrift Commons Server Feature  SKIPPED
[INFO] WSO2 Carbon - Data Bridge - Core Server Feature ... SKIPPED
[INFO] WSO2 Carbon - Data Bridge - Thrift Agent Server Feature  SKIPPED
[INFO] WSO2 Carbon - Data Bridge - Thrift Reciever Server Feature  SKIPPED
[INFO] WSO2 Carbon - Data Bridge - REST API Server Feature  SKIPPED
[INFO] WSO2 Carbon - Data Bridge - Data Publisher Aggregate Feature  SKIPPED
[INFO] WSO2 Carbon - Data Bridge - Data Receiver Aggregate Feature  SKIPPED
[INFO] WSO2 Carbon - AppFactory Server Feature ... SKIPPED
[INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
[INFO] WSO2 Carbon - Patch releases - samples - Aggregator Module  SKIPPED
[INFO] WSO2 Identity Server .. SKIPPED
[INFO] WSO2 IS - Features Aggregator Module .. SKIPPED
[INFO] WSO2 IS - Style Features .. SKIPPED
[INFO] WSO2 IS - Utils Features .. SKIPPED
[INFO] WSO2 Cloud Identity - Tenant Configuration User Interface  SKIPPED
[INFO] WSO2 Carbon - Identity UI Feature . SKIPPED
[INFO] WSO2 IS - IS Profile Generation ... SKIPPED
[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: 34:38.344s
[INFO] Finished at: Thu Jan 03 11:55:36 IST 2013
[INFO] Final Memory: 71M/719M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.identity.oauth.mediator.feature: Could not resolve
dependencies for project
org.wso2.carbon:org.wso2.carbon.identity.oauth.mediator.feature:pom:4.0.6:
Could not find artifact
org.wso2.carbon:org.wso2.carbon.identity.oauth.mediator:jar:4.0.6 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]

Thanks,
Janaka

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Could not find artifact org.wso2.carbon:org.wso2.carbon.identity.sts.store:jar:4.0.5 in wso2-nexus

2013-01-02 Thread Janaka Ranabahu
Hi Shariq,

Yes, and as it seem the above mentioned version is not there is 4.0.5 patch
release pom. Can someone please explain why we have a 4.0.5 component that
was not included in the release and why we have included that version in
the 4.0.6 feature? Also, if this was intended to be a 4.0.6 component,
please fix the version issue and the build.

Thanks,
Janaka


On Thu, Jan 3, 2013 at 10:54 AM, Muhammed Shariq  wrote:

> Hi,
>
> I checked in the patch release pom and org.wso2.carbon.identity.sts.store
> is not listed in the patch-release pom, so its not deployed in the repo ..
>
> [1] -
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/4.0.5/components/pom.xml
>
> On Thu, Jan 3, 2013 at 8:36 AM, Janaka Ranabahu  wrote:
>
>> org.wso2.carbon.identity.sts.store
>>
>
>
>
> --
> Thanks,
> Shariq.
> Phone: +94 777 202 225
>



-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] Could not find artifact org.wso2.carbon:org.wso2.carbon.identity.sts.store:jar:4.0.5 in wso2-nexus

2013-01-02 Thread Janaka Ranabahu
Hi,

Got the following error while building on a clean repo.

[INFO] Identity Core Server Feature .. SUCCESS [37.728s]
[INFO] Identity Core UI Feature .. SUCCESS
[1:16.795s]
[INFO] Identity Core Feature . SUCCESS [2.426s]
[INFO] Identity Provider Server Feature .. FAILURE
[1:00.914s]
[INFO] Identity Provider Feature . SKIPPED
[INFO] Identity Relying Party Server Feature . SKIPPED
[INFO] Identity Relying Party Feature  SKIPPED
[INFO] Identity SAML Single Sign-on Server Feature ... SKIPPED
[INFO] Identity SAML2 Single Sign-on UI Feature .. SKIPPED
[INFO] Identity SAML2.0 Single Sign-on Feature ... SKIPPED
[INFO] SAML2 based authenticator UI Feature .. SKIPPED
[INFO] SAML2 based Single Sign-On authenticator Feature .. SKIPPED
[INFO] WSO2 Stratos - Common UI Feature .. SKIPPED
[INFO] WSO2 Stratos - Common Composite Feature ... SKIPPED
[INFO] WSO2 Stratos - Stratos SSO Management UI Feature .. SKIPPED
[INFO] WSO2 Stratos - Stratos SSO Management Feature . SKIPPED
[INFO] Identity OAuth Common Feature . SKIPPED
[INFO] Identity OAuth Server Feature . SKIPPED
[INFO] Identity OAuth UI Feature . SKIPPED
[INFO] WSO2 Carbon - OAuth Mediation Feature . SKIPPED
[INFO] Identity OAuth Feature  SKIPPED
[INFO] WSO2 Carbon - Feature - Andes - Server  SKIPPED
[INFO] WSO2 Carbon - Feature - Andes - UI  SKIPPED
[INFO] WSO2 Carbon - Feature - Andes . SKIPPED
[INFO] WSO2 Carbon - Loadbalancer Endpoint Management Feature  SKIPPED
[INFO] WSO2 Carbon - AppFactory Server Feature ... SKIPPED
[INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
[INFO] WSO2 Carbon - Patch releases - samples - Aggregator Module  SKIPPED
[INFO] WSO2 Identity Server .. SKIPPED
[INFO] WSO2 IS - Features Aggregator Module .. SKIPPED
[INFO] WSO2 IS - Style Features .. SKIPPED
[INFO] WSO2 IS - Utils Features .. SKIPPED
[INFO] WSO2 Cloud Identity - Tenant Configuration User Interface  SKIPPED
[INFO] WSO2 Carbon - Identity UI Feature . SKIPPED
[INFO] WSO2 IS - IS Profile Generation ... SKIPPED
[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: 17:44.781s
[INFO] Finished at: Thu Jan 03 08:26:53 IST 2013
[INFO] Final Memory: 628M/1447M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.identity.provider.server.feature: Could not resolve
dependencies for project
org.wso2.carbon:org.wso2.carbon.identity.provider.server.feature:pom:4.0.6:
Could not find artifact
org.wso2.carbon:org.wso2.carbon.identity.sts.store:jar:4.0.5 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]

Thanks,
Janaka

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Error while building 4.0.6 platform on a clean repo

2013-01-02 Thread Janaka Ranabahu
Hi Dushan,

Yes that could be a reason. But the same jar is available in our maven
repo[1] but instead of fetching it from our repo, maven tries to download
it from the above mentioned server. Any idea why?

Thanks,
Janaka

[1] http://dist.wso2.org/maven2/net/sf/saxon/saxon/8.9/


On Wed, Jan 2, 2013 at 5:45 PM, Dushan Abeyruwan  wrote:

> Hi
>  "ct net.sf.saxon:saxon:pom:8.9 from/to snmp4j-repo (
> https://server.oosnmp.net/dist/release/): server.oosnmp.net: Unknown host
> server.oosnmp.net -> [Help 1]"  seems like this a network issue ?
>
> cheers
> Dushan
>
> On Wed, Jan 2, 2013 at 5:18 PM, Janaka Ranabahu  wrote:
>
>> ct net.sf.saxon:saxon:pom:8.9 from/to snmp4j-repo (
>> https://server.oosnmp.net/dist/release/): server.oosnmp.net: Unknown
>> host server.oosnmp.net -> [Help 1]
>>
>
>
>
> --
> Dushan Abeyruwan
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>



-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] Fwd: [Commits] [Carbon-platform] svn commit r152669 - carbon/platform/branches/4.0.0/patch-releases/4.0.6

2013-01-02 Thread Janaka Ranabahu
Hi Suresh,

I have corrected the property name of 4.0.6 patch release
version(previously it was *carbon.platform.patch.version.405*). Please
check whether you have used the correct property name in your components
and fix them.

Thanks,
Janaka

-- Forwarded message --
From: 
Date: Wed, Jan 2, 2013 at 5:29 PM
Subject: [Commits] [Carbon-platform] svn commit r152669 -
carbon/platform/branches/4.0.0/patch-releases/4.0.6
To: comm...@wso2.org


Author: janaka
Date: Wed Jan  2 17:29:34 2013
New Revision: 152669
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=152669

Log:
Correcting the property name of 4.0.6 patch release from
carbon.platform.patch.version.405 to carbon.platform.patch.version.406


Modified:
   carbon/platform/branches/4.0.0/patch-releases/4.0.6/pom.xml

Modified: carbon/platform/branches/4.0.0/patch-releases/4.0.6/pom.xml
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/patch-releases/4.0.6/pom.xml?rev=152669&r1=152668&r2=152669&view=diff
==
--- carbon/platform/branches/4.0.0/patch-releases/4.0.6/pom.xml (original)
+++ carbon/platform/branches/4.0.0/patch-releases/4.0.6/pom.xml Wed Jan  2
17:29:34 2013
@@ -87,6 +87,6 @@

 4.0.3

 4.0.4

 4.0.5
-
4.0.6
+
4.0.6
 
 
___
Commits mailing list
comm...@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/commits



-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] Error while building 4.0.6 platform on a clean repo

2013-01-02 Thread Janaka Ranabahu
qj:jar:8.9 (compile), commons-cli:commons-cli:jar:1.0
(compile), commons-lang:commons-lang:jar:2.4 (test),
org.wso2.uri.template:wso2-uri-templates:jar:1.6.2 (compile),
org.wso2.caching:wso2caching-core:jar:4.0.2 (compile),
org.wso2.eventing:wso2eventing-api:jar:2.1 (compile)]: Failed to read
artifact descriptor for net.sf.saxon:saxon:jar:8.9: Could not transfer
artifact net.sf.saxon:saxon:pom:8.9 from/to snmp4j-repo (
https://server.oosnmp.net/dist/release/): server.oosnmp.net: Unknown host
server.oosnmp.net -> [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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :Apache-Synapse


Thanks,
Janaka

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] org.wso2.carbon.identity.authenticator.saml2.sso.feature/4.0.6 is missing

2013-01-02 Thread Janaka Ranabahu
Hi,

I see the following entry in the 4.0.6 patch release features pom but
the corresponding feature is missing. Please do the needful.

 
../../../features/authenticators/saml2-sso/org.wso2.carbon.identity.authenticator.saml2.sso.feature/4.0.6

Thanks,
Janaka


-- 

Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] WSO2 App Factory v1.0.0 M8 Released!

2012-12-20 Thread Janaka Ranabahu
*WSO2 App Factory v1.0.0 M8 Released!*
20th December, 2012


The WSO2 App Factory team is pleased to announce the release of 1.0.0
Milestone 8 version of WSO2 App Factory.
The pre-configured virtual machine could be downloaded from here
[1]<http://dist.wso2.org/solutions/app-factory/m8/Wso2Appfactory-M8.zip>
.


*How to Run*

Download the virtual machine. The servers start automatically when the VM
boot up.



*Key Features*

   - Lifecycle management of an application
   - Automated build and deployment
   - Support multiple application versions
   - APIs to integrate with SDLC Tool chain
   - SVN/GIT repository provisioning
   - Out of the box integration with Jenkins, Redmine
   - Integrated with WSO2 API Manager
   - Role based views
   - Dashboards to monitor application development
   - CIO/CEO dashboards
   - Dependency Management - API sandboxing

*
*
*New Features*

   - Create applications with Git
   - Tagging builds with a name
   - Improved deployment model
   - Moving the servers to standard ports 80/443
   - Ability to work with a Jenkins farm
   - Log download feature
   - Approval UI and human tasks
   - Human task enabled user creation process
   - Search Application Gadget
   - Event Stream View
   - Resource dependency Management UI

*
*
*Issues Fixed*

https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10898



*Known issues*
*
*

https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10899



*Report Problems*

Issues can be reported using the public JIRA available at
https://wso2.org/jira/browse/APPFAC



*Contact us*

WSO2 App Factory developers can be contacted via the mailing lists:
For Users: http://stackoverflow.com/questions/tagged/wso2
For Developers: dev@wso2.org
For details on subscriptions see http://wso2.org/mail


-The WSO2 App Factory Team

[1] http://dist.wso2.org/solutions/app-factory/m8/Wso2Appfactory-M8.zip

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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



-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Have we moved the org.wso2.carbon.governance.services.ui.utils.LifecycleListPopulator in to some other bundle

2012-12-17 Thread Janaka Ranabahu
Hi Eranda,

Im not talking about those things. My only concern is the lifecycle list
populator that we used in previous releases got changed to a new package
name. And for that, you have to update existing rxts with the correct value.

Thanks,
Janaka


On Mon, Dec 17, 2012 at 4:33 PM, Eranda Sooriyabandara wrote:

> Hi Janaka,
> We did the conversion such that the back end not changed. So the
> handler/data layer did not changed and it does not need a migration.
>
> thanks
> Eranda
>
>
> On Mon, Dec 17, 2012 at 4:28 PM, Janaka Ranabahu  wrote:
>
>> Hi Eranda,
>>
>> It would have been better if you guys have put a mail after doing the
>> changes. Otherwise all the existing RXT's that uses this class would get
>> throw an error. This happened to the Appfactory RXT files.
>>
>> And I believe you have thought about migration of these resources.
>>
>> Thanks,
>> Janaka
>>
>>
>> On Mon, Dec 17, 2012 at 4:21 PM, Eranda Sooriyabandara 
>> wrote:
>>
>>> HI Janaka,
>>> Yes, we convert WSDLs/Schemas/Policies and Services into RXT. As a part
>>> we removed the bundles which are redundant.
>>> What is your requirement?
>>>
>>> thanks
>>> Eranda
>>>
>>>
>>> On Mon, Dec 17, 2012 at 4:15 PM, Janaka Ranabahu wrote:
>>>
>>>> Hi,
>>>>
>>>> Did we do $subject? If so, to where?
>>>>
>>>> I have installed the metadata feature 4.0.5 and it seems like number of
>>>> bundles have been removed from it.
>>>>
>>>> Eg:- org.wso2.carbon.governance.services.ui
>>>>
>>>> Therefore I'm getting the an CNF error mentioning the above mentioned
>>>> class.
>>>>
>>>> Thanks,
>>>> Janaka
>>>>
>>>>
>>>> --
>>>> Janaka Ranabahu
>>>> Senior Software Engineer
>>>> WSO2 Inc.
>>>>
>>>> Mobile +94 718370861
>>>> Email : jan...@wso2.com
>>>> Blog : janakaranabahu.blogspot.com
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Eranda Sooriyabandara
>>> *Software Engineer;
>>> Integration Technologies Team;
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *
>>> *
>>>
>>>
>>
>>
>> --
>> Janaka Ranabahu
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Mobile +94 718370861
>> Email : jan...@wso2.com
>> Blog : janakaranabahu.blogspot.com
>>
>>
>
>
> --
> *Eranda Sooriyabandara
> *Software Engineer;
> Integration Technologies Team;
> WSO2 Inc.; http://wso2.com
>
> *
> *
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Have we moved the org.wso2.carbon.governance.services.ui.utils.LifecycleListPopulator in to some other bundle

2012-12-17 Thread Janaka Ranabahu
Hi Eranda,

It would have been better if you guys have put a mail after doing the
changes. Otherwise all the existing RXT's that uses this class would get
throw an error. This happened to the Appfactory RXT files.

And I believe you have thought about migration of these resources.

Thanks,
Janaka


On Mon, Dec 17, 2012 at 4:21 PM, Eranda Sooriyabandara wrote:

> HI Janaka,
> Yes, we convert WSDLs/Schemas/Policies and Services into RXT. As a part we
> removed the bundles which are redundant.
> What is your requirement?
>
> thanks
> Eranda
>
>
> On Mon, Dec 17, 2012 at 4:15 PM, Janaka Ranabahu  wrote:
>
>> Hi,
>>
>> Did we do $subject? If so, to where?
>>
>> I have installed the metadata feature 4.0.5 and it seems like number of
>> bundles have been removed from it.
>>
>> Eg:- org.wso2.carbon.governance.services.ui
>>
>> Therefore I'm getting the an CNF error mentioning the above mentioned
>> class.
>>
>> Thanks,
>> Janaka
>>
>>
>> --
>> Janaka Ranabahu
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Mobile +94 718370861
>> Email : jan...@wso2.com
>> Blog : janakaranabahu.blogspot.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Eranda Sooriyabandara
> *Software Engineer;
> Integration Technologies Team;
> WSO2 Inc.; http://wso2.com
>
> *
> *
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] Have we moved the org.wso2.carbon.governance.services.ui.utils.LifecycleListPopulator in to some other bundle

2012-12-17 Thread Janaka Ranabahu
Hi,

Did we do $subject? If so, to where?

I have installed the metadata feature 4.0.5 and it seems like number of
bundles have been removed from it.

Eg:- org.wso2.carbon.governance.services.ui

Therefore I'm getting the an CNF error mentioning the above mentioned class.

Thanks,
Janaka


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] Is the order of features correct in 4.0.5 patch release features pom?

2012-12-14 Thread Janaka Ranabahu
.wso2.carbon.identity.authenticator.saml2.sso.ui.feature:zip:4.0.5
in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
[ERROR]
[ERROR] Try downloading the file manually from the project website.
[ERROR]
[ERROR] Then, install it using the command:
[ERROR] mvn install:install-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature
-Dversion=4.0.5 -Dpackaging=zip -Dfile=/path/to/file
[ERROR]
[ERROR] Alternatively, if you host your own repository you can deploy the
file there:
[ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature
-Dversion=4.0.5 -Dpackaging=zip -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
[ERROR]
[ERROR]
[ERROR]
org.wso2.carbon:org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature:zip:4.0.5
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/,
releases=true, snapshots=true),
[ERROR] central (http://repo.maven.apache.org/maven2, releases=true,
snapshots=false)
[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/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :org.wso2.carbon.stratos.common.ui.feature
janaka@janaka-TECRA-M11
:/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/branches/4.0.0/patch-releases/4.0.5$

Thanks,
Janaka

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Improving the Add/Edit RXT UI to load Preset Asset Models

2012-12-09 Thread Janaka Ranabahu
Hi Senaka,

+1.

How would the final outcome of this look like? Are you guys going to change
the RXT configuration UI to support adding the handlers and the report
templates or is there going to be a archive type which will install them
all(RXT configuration, handlers and report templates) when you upload it?

Thanks,
Janaka


On Sun, Dec 9, 2012 at 2:15 PM, Senaka Fernando  wrote:

> Hi all,
>
> Like we have preset security scenarios, toolboxes and ready to use
> mediators, I think we should create preset asset models which will load
> everything from RXT to Handler to Custom Reports that are related into the
> UI. This will connect the dots to complete what we claim to support OOTB
> with it making the least impact on those who do not wish to use them. I
> couldn't think of a better way to do this, but if it does, please do
> provide your feedback.
>
> For a start, we can plug this against the 5 sample asset models that we
> ship with G-Reg? Thoughts?
>
> Thanks,
> Senaka.
>
> --
> * <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
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] 4.0.2AF? What is that?

2012-11-15 Thread Janaka Ranabahu
Hi Tharindu,

This was a branch we created to do the Appfactory release work.

Thanks,
Janaka


On Thu, Nov 15, 2012 at 3:04 PM, Tharindu Mathew  wrote:

> Why do we have this in our source tree?
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
> M: +9459908
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Build failure in 4.0.5 platform

2012-11-15 Thread Janaka Ranabahu
Also you need to take an update of
/components/mediators/dblookup and features/mediators

Thanks,
Janaka


On Thu, Nov 15, 2012 at 2:51 PM, Janaka Ranabahu  wrote:

> Hi Rajika,
>
> Just fixed it. Please take an svn update of patch release 4.0.5 features
> pom
>
> Thanks,
> Janaka
>
>
> On Thu, Nov 15, 2012 at 2:49 PM, Rajika Kumarasiri wrote:
>
>> [rajika@localhost 4.0.5]$ mvn clean install -Dmaven.test.skip=true -o
>> [INFO] Scanning for projects...
>> [ERROR] The build could not read 4 projects -> [Help 1]
>> [ERROR]
>> [ERROR]   The project org.apache.httpcomponents:httpcore:4.1.3-wso2v3
>> (/home/rajika/projects/carbon/branch/4.0.0/platform/dependencies/httpcore/4.1.3-wso2v3/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: The repository system is offline
>> but the artifact org.apache.httpcomponents:httpcomponents-core:pom:4.1.3 is
>> not available in the local repository. and 'parent.relativePath' points at
>> wrong local POM @ line 30, column 11 -> [Help 2]
>> [ERROR]
>> [ERROR]   The project org.apache.httpcomponents:httpcore-nio:4.1.3-wso2v3
>> (/home/rajika/projects/carbon/branch/4.0.0/platform/dependencies/httpcore-nio/4.1.3-wso2v3/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: The repository system is offline
>> but the artifact org.apache.httpcomponents:httpcomponents-core:pom:4.1.3 is
>> not available in the local repository. and 'parent.relativePath' points at
>> wrong local POM @ line 30, column 11 -> [Help 2]
>> [ERROR]
>> [ERROR]   The project
>> org.wso2.carbon:org.wso2.carbon.mediator.dblookup.ui:4.0.0
>> (/home/rajika/projects/carbon/branch/4.0.0/platform/components/mediators/dblookup/org.wso2.carbon.mediator.dblookup.ui/4.0.5/pom.xml)
>> has 1 error
>> [ERROR] 'modelVersion' must be one of [4.0.0] but is '4.0.5'. @ line
>> 26, column 19
>> [ERROR]
>> [ERROR]   The project
>> org.wso2.carbon:platform-patch-releases-features:4.0.5
>> (/home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/pom.xml)
>> has 2 errors
>> [ERROR] Child module
>> /home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/../../../features/org.wso2.carbon.mediators.ui.feature/4.0.5
>> of
>> /home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/pom.xml
>> does not exist
>> [ERROR] Child module
>> /home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/../../../features/org.wso2.carbon.mediators.feature/4.0.5
>> of
>> /home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/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
>> [ERROR] [Help 2]
>> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Janaka Ranabahu
> Senior Software Engineer
> WSO2 Inc.
>
> Mobile +94 718370861
> Email : jan...@wso2.com
> Blog : janakaranabahu.blogspot.com
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Build failure in 4.0.5 platform

2012-11-15 Thread Janaka Ranabahu
Hi Rajika,

Just fixed it. Please take an svn update of patch release 4.0.5 features pom

Thanks,
Janaka


On Thu, Nov 15, 2012 at 2:49 PM, Rajika Kumarasiri  wrote:

> [rajika@localhost 4.0.5]$ mvn clean install -Dmaven.test.skip=true -o
> [INFO] Scanning for projects...
> [ERROR] The build could not read 4 projects -> [Help 1]
> [ERROR]
> [ERROR]   The project org.apache.httpcomponents:httpcore:4.1.3-wso2v3
> (/home/rajika/projects/carbon/branch/4.0.0/platform/dependencies/httpcore/4.1.3-wso2v3/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM: The repository system is offline
> but the artifact org.apache.httpcomponents:httpcomponents-core:pom:4.1.3 is
> not available in the local repository. and 'parent.relativePath' points at
> wrong local POM @ line 30, column 11 -> [Help 2]
> [ERROR]
> [ERROR]   The project org.apache.httpcomponents:httpcore-nio:4.1.3-wso2v3
> (/home/rajika/projects/carbon/branch/4.0.0/platform/dependencies/httpcore-nio/4.1.3-wso2v3/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM: The repository system is offline
> but the artifact org.apache.httpcomponents:httpcomponents-core:pom:4.1.3 is
> not available in the local repository. and 'parent.relativePath' points at
> wrong local POM @ line 30, column 11 -> [Help 2]
> [ERROR]
> [ERROR]   The project
> org.wso2.carbon:org.wso2.carbon.mediator.dblookup.ui:4.0.0
> (/home/rajika/projects/carbon/branch/4.0.0/platform/components/mediators/dblookup/org.wso2.carbon.mediator.dblookup.ui/4.0.5/pom.xml)
> has 1 error
> [ERROR] 'modelVersion' must be one of [4.0.0] but is '4.0.5'. @ line
> 26, column 19
> [ERROR]
> [ERROR]   The project
> org.wso2.carbon:platform-patch-releases-features:4.0.5
> (/home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/pom.xml)
> has 2 errors
> [ERROR] Child module
> /home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/../../../features/org.wso2.carbon.mediators.ui.feature/4.0.5
> of
> /home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/pom.xml
> does not exist
> [ERROR] Child module
> /home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/../../../features/org.wso2.carbon.mediators.feature/4.0.5
> of
> /home/rajika/projects/carbon/branch/4.0.0/platform/patch-releases/4.0.5/features/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
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] [Dev-Jaggery] IntelliJ Idea plugin for Jaggery

2012-11-13 Thread Janaka Ranabahu
Hi Ishara,

Nice work.

I have a little concern. I installed the plugin from idea repository and
noticed that there were some logs printed on the console. It seems like the
whole jaggery file has been printed in the console. Please note that there
were several logs such as the following.

JAGGERY_TAG_STARTED-OUTERBRACKETS<%=
JAGGERY_TAG_CLOSSING-JAVASCRIPT_TEXTapiData.name
YYINITIAL-OUTERBRACKETS%>
Content length :4
Last character :<
BRACE_STARTED-HTML_TEXT','
JAGGERY_TAG_STARTED-OUTERBRACKETS<%=
JAGGERY_TAG_CLOSSING-JAVASCRIPT_TEXTapiData.version
YYINITIAL-OUTERBRACKETS%>
Content length :4
Last character :<
BRACE_STARTED-HTML_TEXT','
JAGGERY_TAG_STARTED-OUTERBRACKETS<%=
JAGGERY_TAG_CLOSSING-JAVASCRIPT_TEXTapiData.provider
YYINITIAL-OUTERBRACKETS%>
Content length :696
Last character :<
BRACE_STARTED-HTML_TEXT')"


Thanks,
Janaka




On Sun, Nov 11, 2012 at 7:57 PM, Pradeep Fernando  wrote:

> nice work!
> just for my info : why cant we use it with community edition of Jidea. ?
>
>
> --Pradeep
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

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


[Dev] WSO2 App Factory 1.0.0 Milestone 7 Released!

2012-11-08 Thread Janaka Ranabahu
*WSO2 App Factory v1.0.0 M7 Released*
8th November, 2012


The WSO2 App Factory team is pleased to announce the release of 1.0.0
Milestone 7 version of WSO2 App Factory.
The pre-configured virtual machine could be downloaded from here
[0]<http://builder1.us1.wso2.org/~appfactory/releases/Wso2Appfactory_1.0.0_M7.zip>
.


*How to Run*

Download the virtual machine. The servers start automatically when the
VM boot up.


*Key Features*


   - Lifecycle management of an application
   - Automated build and deployment
   - Support multiple application versions
   - APIs to integrate with SDLC Tool chain
   - SVN/GIT repository provisioning
   - Out of the box integration with Jenkins, Redmine
   - Integrated with WSO2 APIManager
   - Role based views
   - Dashboards to monitor application development


*New Features and Improvements*

   - Integrating with Redmine
   - CIO/CEO dashbords
   - BPEL Security
   - Role based security
   - Change the username to email address
   - Dependency Management - API sandboxing
   - Build Status Recording and Gadget
   - Login to Controller to get Logs
   - G-Reg check list items
   - Other services tab
   - Publishing access URL


*Issues Fixed*


   - [APPFAC-1 <https://wso2.org/jira/browse/APPFAC-1>] - Secure the BPELs
   - [APPFAC-12 <https://wso2.org/jira/browse/APPFAC-12>] - User cannot log
   out - shows "http 405 " error and Url redirect into "
   https://vm.appfactory.wso2.com:9443/null";
   - [APPFAC-13 <https://wso2.org/jira/browse/APPFAC-13>] - frequently
   getting "HTTP 403 " error when accessing to repository location
   - [APPFAC-48 <https://wso2.org/jira/browse/APPFAC-48>] - Production
   appserver is not started in vm image
   - [APPFAC-62 <https://wso2.org/jira/browse/APPFAC-62>] - Add a favicon
   to WSO2 AppFactory
   - [APPFAC-64 <https://wso2.org/jira/browse/APPFAC-64>] - Automatically
   created app id has spaces
   - [APPFAC-69 <https://wso2.org/jira/browse/APPFAC-69>] - The pom.xml
   must be present in root directory for triggering the build
   - [APPFAC-71 <https://wso2.org/jira/browse/APPFAC-71>] - After
   registering a new user, directs to success/failure_register page
   - [APPFAC-78 <https://wso2.org/jira/browse/APPFAC-78>] - Sign up page
   allows users to submit the form with emplty data
   - [APPFAC-90 <https://wso2.org/jira/browse/APPFAC-90>] - Description of
   "Invite User to Application" should be changed
   - [APPFAC-91 <https://wso2.org/jira/browse/APPFAC-91>] - After the self
   registration, page stays in the same place.
   - [APPFAC-92 <https://wso2.org/jira/browse/APPFAC-92>] - Only AppOwner
   should be able to invite user and do other administrative actions on an
   application.
   - [APPFAC-110 <https://wso2.org/jira/browse/APPFAC-110>] - The
   application creation UI doesn't feel Asynchronous
   - [APPFAC-118 <https://wso2.org/jira/browse/APPFAC-118>] - Versioning of
   War files are not working properly
   - [APPFAC-119 <https://wso2.org/jira/browse/APPFAC-119>] - Remove
   hard-coded admin username from the bpel
   - [APPFAC-128 <https://wso2.org/jira/browse/APPFAC-128>] - Deployment to
   Production Fails
   - [APPFAC-146 <https://wso2.org/jira/browse/APPFAC-146>] - AccessUrl for
   web applications


*Known issues*
*
*
https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10867

*Report Problems*

Issues can be reported using the public JIRA available at
https://wso2.org/jira/browse/APPFAC


*Contact us*

WSO2 App Factory developers can be contacted via the mailing lists:
For Users: http://stackoverflow.com/questions/tagged/wso2
For Developers: dev@wso2.org
For details on subscriptions see http://wso2.org/mail


-The WSO2 App Factory Team

[0]
http://builder1.us1.wso2.org/~appfactory/releases/Wso2Appfactory_1.0.0_M7.zip


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Best approach to fix https://wso2.org/jira/browse/REGISTRY-1378

2012-11-05 Thread Janaka Ranabahu
Hi Shelan,

IMO, #1 is the best approach to fix this. There are couple of reasons for
me to say that.

   1. This has been already implemented and it is working without any
   issue. Therefore the only reason we need to change that is to comeup with a
   better solution.
   2. IMO, using full stop (".") to separate the words is more user
   friendly than using camel case phrases.
   3. If we change this, there is an aspect of data migration since this
   will change the properties of some resources(which have been associated
   with a lifecycle) and will change the content of all the lifecycle
   configurations.

Thanks,
Janaka


On Mon, Nov 5, 2012 at 5:24 PM, Shelan Perera  wrote:

> Hi,
>
> Could you please give the feedback on the suggested approach?
>
> 1) Let the user to add the fullstops and prevent adding spaces.
>
> 2) If user adds spaces remove it and do the parsing (Since it is not
> compliant with SCXML and then add the use the one with spaces.)
>
> I prefer 1st approach since 2nd seems like a hack.
>
> Thanks
>
>
> On Thu, Nov 1, 2012 at 3:35 PM, Shelan Perera  wrote:
>
>> Hi,
>>
>> So shall we adhere to that method? i.e using fullstops instead of spaces.
>> ? (I tested with fullstops and it worked)
>>
>> Thanks
>>
>>
>> On Thu, Nov 1, 2012 at 9:37 AM, Evanthika Amarasiri 
>> wrote:
>>
>>> Yes. We came across this issue while testing G-Reg 4.0.0 release and
>>> then the solution given was to use fullstops instead of spaces. In fact, in
>>> latest G-Reg packs, the default ServiceLifeCycle has a state in this
>>> format.
>>>
>>> :
>>> 
>>> 
>>> 
>>> >> class="org.wso2.carbon.governance.registry.extensions.executors.DemoteActionExecutor">
>>> 
>>> >> class="org.wso2.carbon.governance.registry.extensions.executors.apistore.ApiStoreExecutor">
>>>     
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> :
>>>
>>> Regards,
>>> Evanthika
>>>
>>>
>>> On Wed, Oct 31, 2012 at 11:36 PM, Janaka Ranabahu wrote:
>>>
>>>> Hi Shelan,
>>>>
>>>> Did you try defining the state ID by replacing all the  whitespaces
>>>> with '.' character.
>>>>
>>>> *Eg:- Ready For QA ==> Ready.For.QA*
>>>>
>>>> IIRC, it should show that correctly in the UI. Also IIRC, similar
>>>> scenarios have been tested against lifecycles in past releases. Maybe QA
>>>> folks can share more information on that.
>>>>
>>>> Thanks,
>>>> Janaka
>>>>
>>>>
>>>> On Wed, Oct 31, 2012 at 2:18 PM, Shelan Perera  wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> For the issue [1] we cannot specify whitespaces in state ID. It is a
>>>>> constraint added by SCXML and it gives an exception when it tries to 
>>>>> parse.
>>>>> According to this [2] release note they have mentioned
>>>>> not to add white spaces in state IDs. A fix would be to add a
>>>>> temporary element which will complaint with parsing and then again replace
>>>>> it with white space. Is that approach clean enough to introduce?
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>> [1] https://wso2.org/jira/browse/REGISTRY-1378
>>>>>
>>>>> [2]
>>>>> http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7/RELEASE-NOTES.txt
>>>>> --
>>>>> *Shelan Perera*
>>>>>
>>>>> Software Engineer
>>>>> **
>>>>> *WSO2, Inc. : wso2.com*
>>>>> lean.enterprise.middleware.
>>>>>
>>>>> *Home Page*  :shelan.org
>>>>> *Blog* : blog.shelan.org
>>>>> *Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
>>>>> *Twitter* :https://twitter.com/#!/shelan
>>>>>
>>>>> *Mobile*  : +94 772 604 402
>>>>>
>>>>>
>>>>>
>>>>> ___

Re: [Dev] Best approach to fix https://wso2.org/jira/browse/REGISTRY-1378

2012-10-31 Thread Janaka Ranabahu
Hi Shelan,

Did you try defining the state ID by replacing all the  whitespaces with
'.' character.

*Eg:- Ready For QA ==> Ready.For.QA*

IIRC, it should show that correctly in the UI. Also IIRC, similar scenarios
have been tested against lifecycles in past releases. Maybe QA folks can
share more information on that.

Thanks,
Janaka


On Wed, Oct 31, 2012 at 2:18 PM, Shelan Perera  wrote:

> Hi,
>
> For the issue [1] we cannot specify whitespaces in state ID. It is a
> constraint added by SCXML and it gives an exception when it tries to parse.
> According to this [2] release note they have mentioned
> not to add white spaces in state IDs. A fix would be to add a temporary
> element which will complaint with parsing and then again replace it with
> white space. Is that approach clean enough to introduce?
>
> Thanks
>
>
> [1] https://wso2.org/jira/browse/REGISTRY-1378
>
> [2]
> http://svn.apache.org/repos/asf/commons/proper/scxml/tags/SCXML_0_7/RELEASE-NOTES.txt
> --
> *Shelan Perera*
>
> Software Engineer
> **
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Home Page*  :shelan.org
> *Blog* : blog.shelan.org
> *Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Why have we customized maven-core & maven-model?

2012-10-14 Thread Janaka Ranabahu
Hi Sumedha,

On Mon, Oct 15, 2012 at 9:51 AM, Sumedha Rubasinghe wrote:

> See bellow..Why was this done?
>
 Have we provided patches to Maven? What about forward compatibility?

AFAIK, we haven't done any patching of Maven. This is just the orbit
version of maven bundles which can be found in 4.0.0 orbit branch.

Thanks,
Janaka

>
>
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.appfactory.utilities: Could not resolve dependencies for
> project org.wso2.carbon:org.wso2.carbon.appfactory.utilities:bundle:1.0.2:
> The following artifacts could not be resolved: *
> org.apache.maven.wso2:maven-core:jar:3.0.3.wso2v1,*org.apache.maven.wso2:maven-model:jar:3.0.3.wso2v1:
>  Could not find artifact
> org.apache.maven.wso2:maven-core:jar:3.0.3.wso2v1 in wso2-nexus (
> http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1]
>
>
> Failed to execute goal on project org.wso2.carbon.appfactory.utilities:
> Could not resolve dependencies for project
> org.wso2.carbon:org.wso2.carbon.appfactory.utilities:bundle:1.0.2: The
> repository system is offline but the artifact *
> org.apache.maven.wso2:maven-model:jar:3.0.3.wso2v1* is not available in
> the local repository. -> [Help 1]
>
>
> --
> /sumedha
> b :  bit.ly/sumedha
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Attaching an external call to a check list item in LC

2012-10-11 Thread Janaka Ranabahu
Hi Samisa,

On Thu, Oct 11, 2012 at 3:16 PM, Samisa Abeysinghe  wrote:

> This is kind of what I was looking for. However I need something more on
> top of this.
>
> I need to be able to pop us a dialog (JS), get a value and use that as a
> parameter to this service call.
>
We do not have this capability for check-item clicks. Only static
parameters(that are configured from the lifecycle configuration) can be
passed to validations classes.

>
> 1. Can I use transitionScripts to do the dialog po-up part?
>
Yes. But this UI will be showed when you try to do a transition and not a
check-item click.

2. How do I pass the captured param to service call?
>

>From the JS, you can send a request to the invoke_aspect_ajaxprocessor.jsp
with the following parameters. Example code can be found in [1](function
invokeAspect).

new Ajax.Request('../lifecycles/invoke_aspect_ajaxprocessor.jsp',
{
method : 'post',
parameters : {
path : path,
aspect : aspect,
action : action,
items : itemsGlobal,
parameterString : parameterString

})

The parameter string is constructed in the following manner .

obj.name + "^^" + obj.value + "^|^" + obj.name + "^^" + obj.value + "^|^";


In the BE class(executor implementation) these parameters are sent in the
requestContext, as properties. You can read these properties and get the
required parameters. We have such method in [2].

public static boolean populateParameterMap(RequestContext
requestContext, Map currentParameterMap) {
Set parameterMapKeySet = (Set)
requestContext.getProperty("parameterNames");
if (parameterMapKeySet == null) {
log.warn("No parameters where found");
return true;
}
for (Object entry : parameterMapKeySet) {
String key = (String) entry;
if (!key.equals("preserveOriginal")) {
currentParameterMap.put(key, (String)
requestContext.getProperty(key));
}
}
return true;

}

> 3. Do we have a sample?
>

[3] refer to the default transition UI that we ship with G-Reg.
[4] refer to one of the executors(CopyExecutor) we ship with G-Reg.


Eranda,

Did we add any samples related to these use cases?

Thanks,
Janaka

[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/components/governance/org.wso2.carbon.governance.custom.lifecycles.checklist.ui/4.0.1/src/main/resources/web/lifecycles/js/lifecycles.js

[2]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/components/governance/org.wso2.carbon.governance.registry.extensions/4.0.2/src/org/wso2/carbon/governance/registry/extensions/executors/utils/Utils.java

[3]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/components/governance/org.wso2.carbon.governance.custom.lifecycles.checklist.ui/4.0.1/src/main/resources/web/lifecycles/pre_invoke_aspect_ajaxprocessor.jsp

[4]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/components/governance/org.wso2.carbon.governance.registry.extensions/4.0.2/src/org/wso2/carbon/governance/registry/extensions/executors/CopyExecutor.java


> On Thu, Oct 11, 2012 at 10:15 AM, Janaka Ranabahu  wrote:
>
>> Hi Samisa,
>>
>> On Thu, Oct 11, 2012 at 9:49 AM, Samisa Abeysinghe wrote:
>>
>>> I want to do, say, some service calls, when someone ticks a ckecklist
>>> item on an LC state.
>>
>> Does this call should happen as a post check-item click action or a pre
>> check-item click action.
>>
>>>
>>> Is that possible? If so how?
>>>
>> This is possible as a pre check-item click action. We can define a
>> validation class for check-item clicks and these classes are pluggable.
>> Validation classes can be configured from the lifecycle configuration.
>>
>> **
>> 
>> 
>> **
>> 
>> **
>> 
>> 
>> 
>>
>> And as a validation, we can do a service call or some other
>> functionality. Validations are similar to transition executors and there is
>> an interface that you need to implement. More information about validations
>> can be found in our docs[1]. Also there are a set of standard validators
>> that we ship with the distribution[2].
>>
>> If it is not possible, can we add that functionality?
>>>
>>> The use case is, it is required to make the tick real, for e.g. if the
>>> tick is about - did you report time, if reporting time itself is attached
>>> to the tick, it is more practical. If not, people will pre-tic with the
>>> post action intent, and in reality the actio

Re: [Dev] Attaching an external call to a check list item in LC

2012-10-10 Thread Janaka Ranabahu
Hi Samisa,

On Thu, Oct 11, 2012 at 9:49 AM, Samisa Abeysinghe  wrote:

> I want to do, say, some service calls, when someone ticks a ckecklist item
> on an LC state.

Does this call should happen as a post check-item click action or a pre
check-item click action.

>
> Is that possible? If so how?
>
This is possible as a pre check-item click action. We can define a
validation class for check-item clicks and these classes are pluggable.
Validation classes can be configured from the lifecycle configuration.

**


*
*

**




And as a validation, we can do a service call or some other functionality.
Validations are similar to transition executors and there is an interface
that you need to implement. More information about validations can be found
in our docs[1]. Also there are a set of standard validators that we ship
with the distribution[2].

If it is not possible, can we add that functionality?
>
> The use case is, it is required to make the tick real, for e.g. if the
> tick is about - did you report time, if reporting time itself is attached
> to the tick, it is more practical. If not, people will pre-tic with the
> post action intent, and in reality the action associated with the tick
> would not really happen.
>

I believe validations are the solution for this problem. If the validation
fails, the check-item click will not happen.

Thanks,
Janaka

[1] http://docs.wso2.org/wiki/display/Governance450/Configuring+Lifecycles
[2]
http://docs.wso2.org/wiki/display/Governance450/Supported+Standard+Validators

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


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Why not promote verify the checklist in LC?

2012-10-07 Thread Janaka Ranabahu
Hi Samisa,

On Mon, Oct 8, 2012 at 8:37 AM, Samisa Abeysinghe  wrote:

> it just promoted to the next state, without caring about the check-list
> items. (may be I raised the same issue sometime back and there was a
> reasoning)
>
> A fresh look at this, seems to think that this is badly broken. The whole
> idea is that, if not checked, you cannot promote to LC to next stage.
>
> This behavior is there because the default lifecycle configuration is
written in way where it does not check for check-items when promoting. We
can fix this by changing the default lifecycle configuration so that all 3
check-items are mandatory for lifecycle promotion.

Thanks,
Janaka

https://wso2.org/jira/browse/REGISTRY-1371
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] API Manager REST API error when trying to get subscriptions

2012-09-23 Thread Janaka Ranabahu
Hi Sumedha,

Committed the fix in revision 143538.

Thanks,
Janaka

On Mon, Sep 24, 2012 at 9:32 AM, Sumedha Rubasinghe wrote:

> fixes are always welcome.. ;)
>
>
> On Mon, Sep 24, 2012 at 8:52 AM, Janaka Ranabahu  wrote:
>
>> Hi All,
>>
>> Im getting the following error when trying to use the REST API of API
>> Manager and fetch the subscriptions for a user.
>>
>>
>> [2012-09-24 07:58:59,116]  INFO - CarbonAuthenticationUtil
>> 'admin@carbon.super [-1234]' logged in at [2012-09-24 07:58:59,115+0530]
>> from IP address 10.200.2.99
>> [2012-09-24 07:59:23,500]  INFO - CarbonAuthenticationUtil
>> 'admin@carbon.super [-1234]' logged in at [2012-09-24 07:59:23,499+0530]
>> from IP address 10.200.2.99
>> [2012-09-24 07:59:23,589] ERROR - RhinoEngine
>> org.mozilla.javascript.EcmaError: ReferenceError: "user" is not defined.
>> (/store/site/blocks/subscription/subscription-list/ajax/subscription-list.jag#8)
>> [2012-09-24 07:59:23,593] ERROR - WebAppManager
>> org.mozilla.javascript.EcmaError: ReferenceError: "user" is not defined.
>> (/store/site/blocks/subscription/subscription-list/ajax/subscription-list.jag#8)
>> org.jaggeryjs.scriptengine.exceptions.ScriptException:
>> org.mozilla.javascript.EcmaError: ReferenceError: "user" is not defined.
>> (/store/site/blocks/subscription/subscription-list/ajax/subscription-list.jag#8)
>>  at
>> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:451)
>> at
>> org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:202)
>>  at
>> org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:224)
>> at
>> org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:51)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>  at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>  at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>  at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
>>  at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:133)
>>  at
>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
>>  at
>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:49)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>  at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>> at
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
>>  at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>  at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>  at java.lang.Thread.run(Thread.java:662)
>> Caused by: org.mozilla.javascript.EcmaError: ReferenceError: "user" is
>> not defined.
>> (/store/site/blocks/subscription/subscription-list/ajax/subscription-list.jag#8)
>>  at
>> org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3557)
>> at
>> org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3535)
>>  at
>> org.mozilla.javascript.ScriptRuntime.notFoundError(ScriptRuntime.java:3620)
>> at org.mozilla.javascript.ScriptRuntime.name(ScriptRuntime.java:1652)
>>  at
>> org.wso2.carbon.rhino.store.site.blocks.subscription.subscription_list.ajax.c0._c1(/store/site/blocks/subscription/subscription-list/ajax/subscription-list.jag:8)
>>  at
>> org.wso2.carbon.rhino.store.site.blocks.subscription.subscription_list.ajax.c0.call(/store/site/blocks/s

[Dev] API Manager REST API error when trying to get subscriptions

2012-09-23 Thread Janaka Ranabahu
tRuntime.java:97)
 at org.wso2.carbon.rhino.store.jagg.c0._c40(/store/jagg/jagg.jag:459)
at org.wso2.carbon.rhino.store.jagg.c0.call(/store/jagg/jagg.jag)
 at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:66)
at
org.wso2.carbon.rhino.store.site.themes.fancy.templates.page.base.c0._c1(/store/site/themes/fancy/templates/page/base/template.jag:52)
 at
org.wso2.carbon.rhino.store.site.themes.fancy.templates.page.base.c0.call(/store/site/themes/fancy/templates/page/base/template.jag)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:86)
 at org.wso2.carbon.rhino.store.jagg.c0._c38(/store/jagg/jagg.jag:442)
at org.wso2.carbon.rhino.store.jagg.c0.call(/store/jagg/jagg.jag)
 at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:66)
at
org.wso2.carbon.rhino.store.site.pages.error_pages.c0._c1(/store/site/pages/error-pages/500.jag:7)
 at
org.wso2.carbon.rhino.store.site.pages.error_pages.c0.call(/store/site/pages/error-pages/500.jag)
at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:57)
 at
org.wso2.carbon.rhino.store.site.pages.error_pages.c0._c0(/store/site/pages/error-pages/500.jag:5)
at
org.wso2.carbon.rhino.store.site.pages.error_pages.c0.call(/store/site/pages/error-pages/500.jag)
 at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:401)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3003)
 at
org.wso2.carbon.rhino.store.site.pages.error_pages.c0.call(/store/site/pages/error-pages/500.jag)
at
org.wso2.carbon.rhino.store.site.pages.error_pages.c0.exec(/store/site/pages/error-pages/500.jag)
 at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:446)
... 27 more


Further more, I have noticed that this might be caused because of a missing
line in subscriptions-list.jag. It has a code segment as follows.

*var mod, obj, result, username,*
*msg = require("/site/conf/ui-messages.jag"),*
*action = request.getParameter("action");*
*if (action == "getAllSubscriptions") {*
*if (!user) {*
*print({*
*error:true,*
*message:msg.error.loginRequired(action)*
*});*
*return;*
*}*

Shouldn't it be corrected as follows?

*var mod, obj, result, username,*
*msg = require("/site/conf/ui-messages.jag"),*
*action = request.getParameter("action");*
*user = jagg.getUser();*
*if (action == "getAllSubscriptions") {*
*if (!user) {*
*print({*
*    error:true,*
*message:msg.error.loginRequired(action)*
*});*
*return;*
*}*

Thanks,
Janaka

-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


[Dev] NPE while tenant cleanup

2012-08-31 Thread Janaka Ranabahu
concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
 at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)

Thanks,
Janaka
-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Build error in features - org.wso2.carbon.identity.authenticator.iwa.ui.feature

2012-08-28 Thread Janaka Ranabahu
Hi Kishanthan,

I did a svn update today and the issue got resolved. I did a full build
including the kernel.

Thanks,
Janaka

On Tue, Aug 28, 2012 at 5:36 PM, Kishanthan Thangarajah  wrote:

> Is this fixed? I'm getting this a patch release features level.
>
> On Tue, Aug 28, 2012 at 10:02 AM, Janaka Ranabahu  wrote:
>
>> Hi All,
>>
>> Im getting the following error when building features.
>>
>> [INFO] STS Feature ... SUCCESS
>> [0.620s]
>> [INFO] SAML2 based authenticator UI Feature .. SUCCESS
>> [2.599s]
>> [INFO] SAML2 based authenticator Server Feature .. SUCCESS
>> [0.533s]
>> [INFO] SAML2 based Single Sign-On authenticator Feature .. SUCCESS
>> [3.211s]
>> [INFO] IWA based authenticator UI Feature  FAILURE
>> [0.820s]
>> [INFO] IWA based authenticator Server Feature  SKIPPED
>> [INFO] IWA based authenticator Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Api management Server Feature ... SKIPPED
>> [INFO] WSO2 Carbon - API Publisher Feature ... SKIPPED
>> [INFO] WSO2 Carbon - API Store Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Api management Feature .. SKIPPED
>> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module
>>  SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 12:59.051s
>> [INFO] Finished at: Tue Aug 28 09:55:47 IST 2012
>> [INFO] Final Memory: 195M/414M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.identity.authenticator.iwa.ui.feature: Could not resolve
>> dependencies for project
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui.feature:pom:4.0.1:
>> Failed to collect dependencies for
>> [org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1
>> (compile),
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.stub:jar:4.0.1
>> (compile)]: Failed to read artifact descriptor for
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1:
>> Could not find artifact org.wso2.carbon:iwa-authenticator:pom:4.0.1 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
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf
>> :org.wso2.carbon.identity.authenticator.iwa.ui.feature
>>
>>
>> Thanks,
>> Janaka
>>
>> --
>> Janaka Ranabahu
>> Software Engineer
>> WSO2 Inc.
>>
>> Mobile +94 718370861
>> Email : jan...@wso2.com
>> Blog : janakaranabahu.blogspot.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Software Engineer,
> Development Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Build error in features - org.wso2.carbon.identity.authenticator.iwa.ui.feature

2012-08-27 Thread Janaka Ranabahu
Hi Amila,

Im building using the patch release pom. Are you suggesting that I need to
build these separately?

Thanks,
Janaka

On Tue, Aug 28, 2012 at 10:11 AM, Amila Maha Arachchi wrote:

> You need to build the stub bundle and then ui bundle of iwa-authenticator.
> Also, there is a change in kernel/carbon.ui which you will have to up and
> build.
>
> On Tue, Aug 28, 2012 at 10:02 AM, Janaka Ranabahu  wrote:
>
>> Hi All,
>>
>> Im getting the following error when building features.
>>
>> [INFO] STS Feature ... SUCCESS
>> [0.620s]
>> [INFO] SAML2 based authenticator UI Feature .. SUCCESS
>> [2.599s]
>> [INFO] SAML2 based authenticator Server Feature .. SUCCESS
>> [0.533s]
>> [INFO] SAML2 based Single Sign-On authenticator Feature .. SUCCESS
>> [3.211s]
>> [INFO] IWA based authenticator UI Feature  FAILURE
>> [0.820s]
>> [INFO] IWA based authenticator Server Feature  SKIPPED
>> [INFO] IWA based authenticator Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Api management Server Feature ... SKIPPED
>> [INFO] WSO2 Carbon - API Publisher Feature ... SKIPPED
>> [INFO] WSO2 Carbon - API Store Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Api management Feature .. SKIPPED
>> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module
>>  SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 12:59.051s
>> [INFO] Finished at: Tue Aug 28 09:55:47 IST 2012
>> [INFO] Final Memory: 195M/414M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.identity.authenticator.iwa.ui.feature: Could not resolve
>> dependencies for project
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui.feature:pom:4.0.1:
>> Failed to collect dependencies for
>> [org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1
>> (compile),
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.stub:jar:4.0.1
>> (compile)]: Failed to read artifact descriptor for
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1:
>> Could not find artifact org.wso2.carbon:iwa-authenticator:pom:4.0.1 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
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf
>> :org.wso2.carbon.identity.authenticator.iwa.ui.feature
>>
>>
>> Thanks,
>> Janaka
>>
>> --
>> Janaka Ranabahu
>> Software Engineer
>> WSO2 Inc.
>>
>> Mobile +94 718370861
>> Email : jan...@wso2.com
>> Blog : janakaranabahu.blogspot.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amila Maharachchi*
> Technical Lead
> Member, Management Committee - Cloud & Platform TG
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


[Dev] Build error in features - org.wso2.carbon.identity.authenticator.iwa.ui.feature

2012-08-27 Thread Janaka Ranabahu
Hi All,

Im getting the following error when building features.

[INFO] STS Feature ... SUCCESS [0.620s]
[INFO] SAML2 based authenticator UI Feature .. SUCCESS [2.599s]
[INFO] SAML2 based authenticator Server Feature .. SUCCESS [0.533s]
[INFO] SAML2 based Single Sign-On authenticator Feature .. SUCCESS [3.211s]
[INFO] IWA based authenticator UI Feature  FAILURE [0.820s]
[INFO] IWA based authenticator Server Feature  SKIPPED
[INFO] IWA based authenticator Feature ... SKIPPED
[INFO] WSO2 Carbon - Api management Server Feature ... SKIPPED
[INFO] WSO2 Carbon - API Publisher Feature ... SKIPPED
[INFO] WSO2 Carbon - API Store Feature ... SKIPPED
[INFO] WSO2 Carbon - Api management Feature .. SKIPPED
[INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 12:59.051s
[INFO] Finished at: Tue Aug 28 09:55:47 IST 2012
[INFO] Final Memory: 195M/414M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.identity.authenticator.iwa.ui.feature: Could not resolve
dependencies for project
org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui.feature:pom:4.0.1:
Failed to collect dependencies for
[org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1
(compile),
org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.stub:jar:4.0.1
(compile)]: Failed to read artifact descriptor for
org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1:
Could not find artifact org.wso2.carbon:iwa-authenticator:pom:4.0.1 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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf
:org.wso2.carbon.identity.authenticator.iwa.ui.feature


Thanks,
Janaka

-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


[Dev] Update DB scripts default tenant ID value with the new one

2012-08-27 Thread Janaka Ranabahu
Hi All,

I have observed that all the DB scripts still have a default tenant ID of 0
in [1]. Shall we go ahead and replace them with -1234?

Thanks,
Janaka

[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.1/carbon-home/dbscripts

-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Build failure - CEP Server Feature

2012-08-26 Thread Janaka Ranabahu
Hi Ajith,

I believe building the Orbit patch release pom will solve this issue.

Thanks,
Janaka

On Mon, Aug 27, 2012 at 10:16 AM, Ajith Vitharana  wrote:

>
>
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.cep.server.feature: Could not resolve dependencies for
> project org.wso2.carbon:org.wso2.carbon.cep.server.feature:pom:4.0.1: Could
> not find artifact com.hazelcast.wso2:hazelcast:jar:2.2.wso2v1 in wso2-nexus
> (http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1]
> [ERROR]
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94714631794
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


[Dev] Bamboo kernel build failing - was{ Error in building kernel - r138299}

2012-08-19 Thread Janaka Ranabahu
Hi All,

The bamboo kernel build is still failing due to this issue. Can someone who
has access to bamboo builder, do the needful to resolve this issue.

Thanks,
Janaka

-- Forwarded message --
From: Asela Pathberiya 
Date: Fri, Aug 17, 2012 at 8:52 PM
Subject: Re: [Dev] Error in building kernel - r138299
To: Krishantha Samaraweera 
Cc: WSO2 Developers' List 




On Fri, Aug 17, 2012 at 5:37 PM, Krishantha Samaraweera  wrote:

> Removing .m2/repository/org/wso2/carbon/carbon-kernel-features solve the
> problem for me.


I got same error and fixed by using this..

Thanks,
Asela.


>
> Thanks,
> Krishantha.
>
> On Fri, Aug 17, 2012 at 11:36 AM, Kasun Weranga  wrote:
>
>>
>>
>> On Thu, Aug 16, 2012 at 10:37 PM, Janaka Ranabahu wrote:
>>
>>> Hi Pradeep,
>>>
>>> I see the same error on Bamboo build "WSO2 Carbon BRANCH › Kernel_4.0.0
>>> › #97 failed". Please let us know the correct fix for this.
>>
>>
>> I am also getting this.
>>
>>
>>>
>>> Thanks,
>>> Janaka
>>>
>>>
>>> On Thu, Aug 16, 2012 at 3:16 PM, Janaka Ranabahu wrote:
>>>
>>>> Hi,
>>>>
>>>> I did not get this error when building on a clean repo.
>>>>
>>>> Thanks,
>>>> Janaka
>>>>
>>>>
>>>> On Thu, Aug 16, 2012 at 12:32 PM, Senaka Fernando wrote:
>>>>
>>>>> Hi Pradeep,
>>>>>
>>>>> Can you have a look? We need to get the kernel build to pass.
>>>>>
>>>>> Thanks,
>>>>> Senaka.
>>>>>
>>>>>
>>>>> On Thu, Aug 16, 2012 at 12:21 PM, Malinga Perera wrote:
>>>>>
>>>>>> Any fixes? I too got this error!!
>>>>>>
>>>>>> On Thu, Aug 16, 2012 at 1:08 AM, Janaka Ranabahu wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Getting the following error. Any thoughts?
>>>>>>>
>>>>>>> [INFO] Apache Axis2 - Root ... SUCCESS
>>>>>>> [6.594s]
>>>>>>> [INFO] axis2.wso2  SUCCESS
>>>>>>> [41.673s]
>>>>>>> [INFO] axis2.json.wso2 ... SUCCESS
>>>>>>> [0.346s]
>>>>>>> [INFO] axis2.client.wso2 . SUCCESS
>>>>>>> [19.709s]
>>>>>>> [INFO] axis2.jaxbri.wso2 . SUCCESS
>>>>>>> [0.257s]
>>>>>>> [INFO] axis2.jibx.wso2 ... SUCCESS
>>>>>>> [0.246s]
>>>>>>> [INFO] WSO2 Carbon - Aggregate Pom ... SUCCESS
>>>>>>> [0.102s]
>>>>>>> [INFO] WSO2 Carbon - Patch releases - dependencies - Aggregator
>>>>>>> Module  SUCCESS [0.032s]
>>>>>>> [INFO] WSO2 Carbon - Patch releases - service-stubs - Aggregator
>>>>>>> Module  SUCCESS [0.026s]
>>>>>>> [INFO] WSO2 Carbon - Utilities ... SUCCESS
>>>>>>> [12.885s]
>>>>>>> [INFO] WSO2 Carbon - Caching . SUCCESS
>>>>>>> [4.210s]
>>>>>>> [INFO] WSO2 Carbon - User Manager Kernel . SUCCESS
>>>>>>> [12.989s]
>>>>>>> [INFO] WSO2 Carbon - Kernel .. SUCCESS
>>>>>>> [21.262s]
>>>>>>> [INFO] WSO2 Carbon - Carbon specific tomcat extensions ... SUCCESS
>>>>>>> [10.523s]
>>>>>>> [INFO] WSO2 Carbon - New Data Sources Core ... SUCCESS
>>>>>>> [4.119s]
>>>>>>> [INFO] WSO2 Carbon - Registry Kernel . SUCCESS
>>>>>>> [1:04.386s]
>>>>>>> [INFO] WSO2 Carbon - Patch releases - core - Aggregator Module
>>>>>>>  SUCCESS [0.009s]
>>>>>>> [INFO] WSO2 Carbon - Carbon Common Feature ... SUCCESS
>>>>>>> [26.285s]
>>>>>>> [INFO] WSO2 Carbon - Carbon Feature .. FAILURE
>>>>>>> [5:07.799s]
>>>>>>> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module
>>>>>>>  SKIPPED
>

Re: [Dev] Build error in automation api in clean repo

2012-08-17 Thread Janaka Ranabahu
Hi Again,

Seems this jar is not in our nexus. Please refer [1].

Thanks,
Janaka

[1]
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/qpid/qpid-client/

On Fri, Aug 17, 2012 at 10:44 PM, Janaka Ranabahu  wrote:

> Hi,
>
> Getting the following error when building with a clean repo. Is this qpid
> version correct? I see 0.12.wso2v1 in our nexus(Please note the '-' and the
> '.').
>
>  [INFO] WSO2 Cloud Gateway - P2 Profile Generation  SKIPPED
> [INFO] WSO2 Cloud Gateway - Distribution . SKIPPED
> [INFO] WSO2 Cloud Gateway - Integration Parent ... SKIPPED
> [INFO] product ... SKIPPED
> [INFO] WSO2 Carbon - Patch releases - products - Aggregator Module  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 25.921s
> [INFO] Finished at: Fri Aug 17 22:30:04 IST 2012
> [INFO] Final Memory: 132M/783M
> [INFO]
> 
> [ERROR] Failed to execute goal on project org.wso2.carbon.automation.api:
> Could not resolve dependencies for project
> org.wso2.carbon.automation:org.wso2.carbon.automation.api:jar:4.0.1:
> Failure to find org.apache.qpid:qpid-client:jar:0.12-wso2v1 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 -> [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
> janaka@janaka-TECRA-M11
> :/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/branches/4.0.0/patch-releases/4.0.1$
>
> Thanks,
> Janaka
> --
> Janaka Ranabahu
> Software Engineer
> WSO2 Inc.
>
> Mobile +94 718370861
> Email : jan...@wso2.com
> Blog : janakaranabahu.blogspot.com
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


[Dev] Build error in automation api in clean repo

2012-08-17 Thread Janaka Ranabahu
Hi,

Getting the following error when building with a clean repo. Is this qpid
version correct? I see 0.12.wso2v1 in our nexus(Please note the '-' and the
'.').

[INFO] WSO2 Cloud Gateway - P2 Profile Generation  SKIPPED
[INFO] WSO2 Cloud Gateway - Distribution . SKIPPED
[INFO] WSO2 Cloud Gateway - Integration Parent ... SKIPPED
[INFO] product ... SKIPPED
[INFO] WSO2 Carbon - Patch releases - products - Aggregator Module  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 25.921s
[INFO] Finished at: Fri Aug 17 22:30:04 IST 2012
[INFO] Final Memory: 132M/783M
[INFO]

[ERROR] Failed to execute goal on project org.wso2.carbon.automation.api:
Could not resolve dependencies for project
org.wso2.carbon.automation:org.wso2.carbon.automation.api:jar:4.0.1:
Failure to find org.apache.qpid:qpid-client:jar:0.12-wso2v1 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 -> [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
janaka@janaka-TECRA-M11
:/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/branches/4.0.0/patch-releases/4.0.1$

Thanks,
Janaka
-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] depsync UI component build failure

2012-08-17 Thread Janaka Ranabahu
Hi Pradeep,

It seems like the stubs are not properly built. Please check whether the
codegen happens without any issues. I have observed that the service stubs
build succeeds even if the codegen fails.

Thanks,
Janaka

On Fri, Aug 17, 2012 at 6:03 PM, Pradeep Fernando  wrote:

>
> Hi,
>
> please fix this.
>
>
>
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[25,57]
> package org.wso2.carbon.deployment.synchronizer.stub.types does not exist
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[26,62]
> package org.wso2.carbon.deployment.synchronizer.stub.types.util does not
> exist
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[27,62]
> package org.wso2.carbon.deployment.synchronizer.stub.types.util does not
> exist
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[33,12]
> cannot find symbol
> symbol  : class DeploymentSynchronizerAdminStub
> location: class
> org.wso2.carbon.deployment.synchronizer.ui.client.DeploymentSyncAdminClient
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[46,11]
> cannot find symbol
> symbol  : class DeploymentSynchronizerConfiguration
> location: class
> org.wso2.carbon.deployment.synchronizer.ui.client.DeploymentSyncAdminClient
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[54,35]
> cannot find symbol
> symbol  : class DeploymentSynchronizerConfiguration
> location: class
> org.wso2.carbon.deployment.synchronizer.ui.client.DeploymentSyncAdminClient
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[58,35]
> cannot find symbol
> symbol  : class DeploymentSynchronizerConfiguration
> location: class
> org.wso2.carbon.deployment.synchronizer.ui.client.DeploymentSyncAdminClient
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[78,11]
> cannot find symbol
> symbol  : class RepositoryConfigParameter
> location: class
> org.wso2.carbon.deployment.synchronizer.ui.client.DeploymentSyncAdminClient
> [ERROR]
> /home/pradeep/checkout/branch/platform/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.ui/4.0.1/src/main/java/org/wso2/carbon/deployment/synchronizer/ui/client/DeploymentSyncAdminClient.java:[39,19]
> cannot find symbol
> symbol  : class DeploymentSynchronizerAdminStub
> location: class
> org.wso2.carbon.deployment.synchronizer.ui.client.DeploymentSyncAdminClient
> [INFO] 9 errors
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Build failure in Kernal - Carbon-core feature

2012-08-17 Thread Janaka Ranabahu
Hi Sinthuja,

I believe the same error is discussed on "Error in building kernel -
r138299" mail thread.

Thanks,
Janaka

On Fri, Aug 17, 2012 at 6:05 PM, Sinthuja Ragendran wrote:

> Hi all,
>
> I'm getting this when building patch release of kernal.
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 1.222s
> [INFO] Finished at: Fri Aug 17 17:03:16 IST 2012
> [INFO] Final Memory: 8M/490M
> [INFO]
> 
> [ERROR] Failed to execute goal on project org.wso2.carbon.core.feature:
> Could not resolve dependencies for project
> org.wso2.carbon:org.wso2.carbon.core.feature:pom:4.0.1: The following
> artifacts could not be resolved:
> org.wso2.carbon:org.wso2.carbon.core.services:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.tomcat:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.tomcat.patch:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.tomcat.fragment.dummy:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.server.admin:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.context:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.logging:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.securevault:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.core.common:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.server.admin.common:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.user.mgt.common:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.application.deployer:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.cluster.mgt.core:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.user.mgt:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.registry.server:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.ui:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.ui.menu.general:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.i18n:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.server.admin.ui:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.user.mgt.ui:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.queuing:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.base:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.registry.api:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.user.api:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.feature.mgt.core:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.feature.mgt.services:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.authenticator.proxy:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.addressing:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.roles.mgt:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.roles.mgt.ui:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.roles.mgt.stub:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.core.bootup.validator:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.coordination.common:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.coordination.core:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.ndatasource.common:jar:4.0.1,
> org.wso2.carbon:org.wso2.carbon.ndatasource.rdbms:jar:4.0.1: The repository
> system is offline but the artifact
> org.wso2.carbon:org.wso2.carbon.core.services:jar:4.0.1 is not available in
> the local repository. -> [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
>
>
> Thanks,
> Sinthuja.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


Re: [Dev] Error building platform

2012-08-16 Thread Janaka Ranabahu
Thanks Suho for the quick response.

Thanks,
Janaka

On Fri, Aug 17, 2012 at 12:03 AM, Suhothayan Sriskandarajah
wrote:

> This is fixed in r138576
>
> Thanks
> Suho
>
>
>
> On Thu, Aug 16, 2012 at 10:27 PM, Janaka Ranabahu  wrote:
>
>> Hi All,
>>
>> I'm getting the following error. Please fix this.
>>
>> [INFO] Scanning for projects...
>> [ERROR] The build could not read 5 projects -> [Help 1]
>> [ERROR]
>> [ERROR]   The project org.wso2.carbon:org.wso2.carbon.cep.admin:4.0.1
>> (/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/branches/4.0.0/components/cep/org.wso2.carbon.cep.admin/4.0.1/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.wso2.carbon:cep:pom:4.0.0 in http://repo.maven.apache.org/maven2 was
>> 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 19, column 13 ->
>> [Help 2]
>> [ERROR]
>> [ERROR]   The project org.wso2.carbon:org.wso2.carbon.cep.core:4.0.1
>> (/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/branches/4.0.0/components/cep/org.wso2.carbon.cep.core/4.0.1/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.wso2.carbon:cep:pom:4.0.0 in http://repo.maven.apache.org/maven2 was
>> 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 21, column 13 ->
>> [Help 2]
>> [ERROR]
>> [ERROR]   The project org.wso2.carbon:org.wso2.carbon.cep.fusion:4.0.1
>> (/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/branches/4.0.0/components/cep/org.wso2.carbon.cep.fusion/4.0.1/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.wso2.carbon:cep:pom:4.0.0 in http://repo.maven.apache.org/maven2 was
>> 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 19, column 13 ->
>> [Help 2]
>> [ERROR]
>> [ERROR]   The project org.wso2.carbon:org.wso2.carbon.cep.siddhi:4.0.1
>> (/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/branches/4.0.0/components/cep/org.wso2.carbon.cep.siddhi/4.0.1/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.wso2.carbon:cep:pom:4.0.0 in http://repo.maven.apache.org/maven2 was
>> 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 5, column 13 ->
>> [Help 2]
>> [ERROR]
>> [ERROR]   The project org.wso2.carbon:org.wso2.carbon.cep.ui:4.0.1
>> (/media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/branches/4.0.0/components/cep/org.wso2.carbon.cep.ui/4.0.1/pom.xml)
>> has 1 error
>> [ERROR] Non-resolvable parent POM: Failure to find
>> org.wso2.carbon:cep:pom:4.0.0 in http://repo.maven.apache.org/maven2 was
>> 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 21, column 13 ->
>> [Help 2]
>> [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
>> [ERROR] [Help 2]
>> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>>
>>
>> Thanks,
>> Janaka
>>
>> --
>> Janaka Ranabahu
>> Software Engineer
>> WSO2 Inc.
>>
>> Mobile +94 718370861
>> Email : jan...@wso2.com
>> Blog : janakaranabahu.blogspot.com
>>
>>
>
>
> --
> *S. Suhothayan
> *
> Software Engineer,
> Data Technologies Team,
>  *WSO2, Inc. **http://wso2.com
>  <http://wso2.com/>*
> *lean.enterprise.middleware.*
>
> *email: **s...@wso2.com* * cell: (+94) 779 756 757
> blog: **http://suhothayan.blogspot.com/* <http://suhothayan.blogspot.com/>
> *
> twitter: **http://twitter.com/suhothayan* <http://twitter.com/suhothayan>*
> linked-in: **http://lk.linkedin.com/in/suhothayan*
> *
> *
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

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


  1   2   >