Re: [Dev] Fwd: [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #82 has FAILED. Change made by supunm.

2012-08-13 Thread Supun Malinga 
Hi Maheshika,

Can you please check if the core/org.wso2.carbon.core/4.0.1 is built
and Version.aar exists in its target directory?

thanks,

On Tue, Aug 14, 2012 at 11:20 AM, Maheshika Goonetilleke  wrote:

>
>
> -- Forwarded message --
> From: Bamboo 
> Date: Tue, Aug 14, 2012 at 10:43 AM
> Subject: [Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #82 has
> FAILED. Change made by supunm.
> To: dev@wso2.org
>
>
>  [image: Failed]  WSO2 Carbon 
> BRANCH›
> Kernel_4.0.0  › 
> #82
> failed
>
> Code has been updated by supunm
> .
>
> No failed tests found, a possible compilation error.
>Failing Jobs  Job
> Duration Tests[image: Failed]  Default 
> Job (Default
> Stage)  56 minutes  No tests found  
> Logs|
> Artifacts  
> Code
> Changes   View
> full change details
> supunm 
> adding updated axis2 version  137828 View 
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian Bamboo .
>
> If you wish to stop receiving these emails edit your user 
> profileor notify
> your administrator .
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
> Hi all
>
> Kernel_4.0.0 has failed due to the following error;
>
> 13-Aug-2012 22:13:02 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:attached (2-dist)
> on project wso2carbon-core: Failed to create assembly: Error adding file to
> archive:
> /home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER000-JOB1/distribution/kernel/4.0.0/../../../core/org.wso2.carbon.core/4.0.1/target/Version.aar
> isn't a file. -> [Help 1] 13-Aug-2012 22:13:02 [ERROR]
>
>
> --
>
> Thanks & Best Regards,
>
> Maheshika Goonetilleke
> Engineering Process Coordinator
> WSO2 Inc
>
> www.wso2.com/
>
> M : 0773 596707
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

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

[Dev] Fwd: [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #82 has FAILED. Change made by supunm.

2012-08-13 Thread Maheshika Goonetilleke 
-- Forwarded message --
From: Bamboo 
Date: Tue, Aug 14, 2012 at 10:43 AM
Subject: [Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #82 has
FAILED. Change made by supunm.
To: dev@wso2.org


 [image: Failed]  WSO2 Carbon
BRANCH›
Kernel_4.0.0  ›
#82
failed

Code has been updated by supunm
.

No failed tests found, a possible compilation error.
  Failing Jobs Job
Duration Tests[image: Failed]  Default
Job (Default
Stage)  56 minutes  No tests found
Logs|
Artifacts 
Code
Changes   View full
change details 
supunm 
adding updated axis2 version  137828 View
Online
| Add Comments

This message was sent by Atlassian Bamboo .

If you wish to stop receiving these emails edit your user
profileor
notify
your administrator .

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


Hi all

Kernel_4.0.0 has failed due to the following error;

13-Aug-2012 22:13:02[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:attached (2-dist)
on project wso2carbon-core: Failed to create assembly: Error adding file to
archive:
/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB001-KER000-JOB1/distribution/kernel/4.0.0/../../../core/org.wso2.carbon.core/4.0.1/target/Version.aar
isn't a file. -> [Help 1]13-Aug-2012 22:13:02[ERROR]


-- 

Thanks & Best Regards,

Maheshika Goonetilleke
Engineering Process Coordinator
WSO2 Inc

www.wso2.com/

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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #82 has FAILED. Change made by supunm.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Kernel_4.0.0 > #82 failed.
---
Code has been updated by supunm.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER000-82/


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



--
Code Changes
--
supunm (137828):

>adding updated axis2 version



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

[Dev] Carbon 4.0.1 still bundle org.wso2.carbon.core 4.0.0 ?

2012-08-13 Thread Rajika Kumarasiri 
I just updated the 4.0.1 kernel and built it from the patch release. It
seems kernel 4.0.1 still bundle the 4.0.0 of org.wso2.carbon.core ?
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] carbon core 4.0.1 build failure

2012-08-13 Thread Janaka Ranabahu 
Hi,

Did this issue got resolved? I'm also getting this error.

Thanks,
Janaka

On Fri, Aug 10, 2012 at 5:18 PM, Supun Malinga  wrote:

> Hi,
>
> [INFO] Compiling 132 source files to
> /home/disk1/carbon_builds/newTrunk/kernel/branches/4.0.0/core/org.wso2.carbon.core/4.0.1/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/disk1/carbon_builds/newTrunk/kernel/branches/4.0.0/core/org.wso2.carbon.core/4.0.1/src/main/java/org/wso2/carbon/core/util/PasswordUpdater.java:[160,45]
> cannot find symbol
> symbol  : constructor
> JDBCUserStoreManager(org.apache.commons.dbcp.BasicDataSource,org.wso2.carbon.user.api.RealmConfiguration)
> location: class org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager
> [INFO] 1 error
>
> thanks,
> --
> Supun Malinga,
>
> Software Engineer,
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
> email - sup...@wso2.com 
> mobile - 071 56 91 321
>
>
> ___
> 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] Missing Requirements for org.wso2.carbon.registry.extensions.server.feature when trying to install API-Manager Feature Category from repository

2012-08-13 Thread Dileepa Jayakody 
Thanks Senaka. Will try on a clean repo.
But I still face the issue of unsatisfied org.codehaus.plexus [1.7.0,2.0.0)
dependency* *when installing registry extensions feature to carbon4 in
feature manager.

Thanks,
Dileepa

On Mon, Aug 13, 2012 at 7:45 PM, Senaka Fernando  wrote:

> Hi Dileepa,
>
> Are you building on a fresh repo? Never ran into such issues during the AM
> build in the past, so there might have been some issues in the build itself.
>
> Thanks,
> Senaka.
>
> On Mon, Aug 13, 2012 at 5:52 PM, Dileepa Jayakody wrote:
>
>> Has anybody come across this error when installing registry.extensions
>> feature to carbon4?
>> I see a somewhat similar issue when trying to build c4_release_tag's
>> apimanager's p2-profile;
>>
>> *
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Governance Metadata Feature
>> 4.0.0 (org.wso2.carbon.governance.metadata.feature.group 4.0.0)
>>  Missing requirement: org.wso2.carbon.registry.extensions 4.0.0
>> (org.wso2.carbon.registry.extensions 4.0.0) requires 'package 
>> org.apache.maven.scm
>> [1.7.0,2.0.0)' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Governance Metadata Feature 4.0.0
>> (org.wso2.carbon.governance.metadata.feature.group 4.0.0)
>>   To: org.wso2.carbon.governance.metadata.server.feature.group [4.0.0]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Governance Metadata Server Feature 4.0.0
>> (org.wso2.carbon.governance.metadata.server.feature.group 4.0.0)
>>   To: org.wso2.carbon.governance.services [4.0.0]
>>  Cannot satisfy dependency:
>>   From: org.wso2.carbon.governance.services 4.0.0
>> (org.wso2.carbon.governance.services 4.0.0)
>>   To: package org.wso2.carbon.registry.extensions.utils 0.0.0*
>>
>> Both org.codehaus.plexus and org.apache.maven.scm packages are exported
>> by dependencies/orbit/maven-scm bundle and the default version attached to
>> all exported packages is : 1.7.0.ws o2v1.
>>
>> Could this be version issue with the exported packages?
>>
>> Thanks,
>> Dileepa
>>
>>
>> On Mon, Aug 13, 2012 at 11:50 AM, Dileepa Jayakody wrote:
>>
>>> Hi All,
>>>
>>> I tried installing API-Manager category to carbon-4.0.0 from the feature
>>> repository of 4.0.0 branch, And got following unsatisfied dependency for
>>> org.wso2.carbon.registry.extensions 4.0.0;
>>>
>>> Cannot complete the install because one or more required items could not
>>> be found. Software being installed: WSO2 Carbon - Registry Extensions
>>> Feature 4.0.0 (org.wso2.carbon.registry.extensions.feature.group 4.0.0)
>>> Missing requirement: org.wso2.carbon.registry.extensions 4.0.0
>>> (org.wso2.carbon.registry.extensions 4.0.0) requires 'package 
>>> *org.codehaus.plexus
>>> [1.7.0,2.0.0)*' but it could not be found Cannot satisfy dependency:
>>> From: WSO2 Carbon - Registry Extensions Feature 4.0.0
>>> (org.wso2.carbon.registry.extensions.feature.group 4.0.0) To:
>>> org.wso2.carbon.registry.extensions.server.feature.group [4.0.0] Cannot
>>> satisfy dependency: From: WSO2 Carbon - Registry Extensions Server Feature
>>> 4.0.0 (org.wso2.carbon.registry.extensions.server.feature.group 4.0.0) To:
>>> org.wso2.carbon.registry.extensions [4.0.0]
>>>
>>> Which bundle exports org.codehaus.plexus [1.7.0,2.0.0)?
>>> Any idea on resolving this?
>>>
>>> Thanks,
>>> Dileepa
>>> --
>>> Dileepa Jayakody,
>>> Software Engineer, WSO2 Inc.
>>> Lean . Enterprise . Middleware
>>>
>>> Mobile : +94777-857616
>>>
>>>
>>
>>
>> --
>> Dileepa Jayakody,
>> Software Engineer, WSO2 Inc.
>> Lean . Enterprise . Middleware
>>
>> Mobile : +94777-857616
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Senaka Fernando*
> Member - Integration Technologies Management Committee;
> Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *
> Lean . Enterprise . Middleware
>
>


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

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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #81 has FAILED. Change made by supunm.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Kernel_4.0.0 > #81 failed.
---
Code has been updated by supunm.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER000-81/


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



--
Code Changes
--
supunm (137827):

>fixing build failure

supunm (137825):

>adding axis2



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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #129 has FAILED. Change made by udayanga.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #129 failed.
---
Code has been updated by udayanga.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-129/


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



--
Code Changes
--
udayanga (137823):

>including mediation lib stub patch component

udayanga (137816):

>commiting mediation lib fixes/updates for 4.0.1

udayanga (137824):

>commiting mediation lib patch components for 4.0.1



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

Re: [Dev] Help - Invoking basic-auth secured WS

2012-08-13 Thread Denis Weerasiri 
On Mon, Aug 13, 2012 at 9:14 PM, Mohammad Benslimne <
mohammad.benslim...@gmail.com> wrote:

> Please, any help ... ?
>
You have to try this in a BPS distribution from our latest nightly builds.


>
> On 10 August 2012 14:11, Mohammad Benslimne  > wrote:
>
>> Hi,
>>
>> So any recipes to invoke a basic-auth secured WS within a BPEL process to
>> be executed in WSO2 BPS ?
>> Thanks in advance ...
>>
>> Mohammad
>>
>> On 10 August 2012 13:49, Denis Weerasiri  wrote:
>>
>>>
>>>
>>> On Fri, Aug 10, 2012 at 7:53 PM, Mohammad Benslimne <
>>> mohammad.benslim...@gmail.com> wrote:
>>>
 Hello folks,

 I am using WSO2 BPS 2.1.2
 Please, would you have examples for invoking basic-auth secured WS ?
 How could I insert Authorization http header in secured WS request ?

 I tried unified endpoints, but I got java.lang.NullPointerException at
 org.wso2.carbon.bpel.core.ode.integration.config.EndpointConfiguration.getUnifiedEndpoint
 when defining  tag (cf.
 http://osdir.com/ml/general/2012-05/msg47734.html).

 I tried also defining the Autorization header in  in
 deploy.xml (cf.
 http://wso2.org/project/bps/2.0.2/docs/user_guide.html#Using-Manipulating-Endpoints),
 no effect!

>>> Hi,
>>> AFAIK, this feature is not included in 2.1.2. But it is included in the
>>> upcoming WSO2 BPS release.
>>>
  Many thanks for any help ...


 Best regards,
 Mohammad

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


>>>
>>>
>>> --
>>> Thanks,
>>> Denis
>>> --
>>> *Denis Weerasiri*
>>> Senior Software Engineer
>>> Integration Technologies Team, WSO2 Inc.; http://wso2.com,
>>> *email: denis ** [AT] wso2.com
>>> *
>>> *phone: +94117639629
>>> *
>>> *site: 
>>> **https://sites.google.com/site/ddweerasiri/*
>>> *blog: **http://ddweerasiri.blogspot.com*
>>> *
>>> twitter: **http://twitter.com/ddweerasiri*
>>> *
>>> linked-in: 
>>> **http://lk.linkedin.com/in/ddweerasiri*
>>>
>>>
>>
>>
>> --
>>
>>
>> Mohammad
>>
>>
>
>
> --
>
>
> Mohammad
>
>


-- 
Thanks,
Denis
--
*Denis Weerasiri*
Senior Software Engineer
Integration Technologies Team, WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com *
*phone: +94117639629
*
*site: 
**https://sites.google.com/site/ddweerasiri/*
*blog: **http://ddweerasiri.blogspot.com* 
*
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #128 has FAILED. Change made by udayanga.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #128 failed.
---
Code has been updated by udayanga.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-128/


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



--
Code Changes
--
udayanga (137814):

>commititng Synapse Library Fix for lib based class loading



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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #127 has FAILED. Change made by kasunw.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #127 failed.
---
This build occurred because it is a dependant of WCB001-KER000-80.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-127/


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



--
Code Changes
--
kasunw (137811):

>Fixed BAM-709 and several issues



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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #126 has FAILED. Change made by tharindu, suho and nuwanw.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #126 failed.
---
This build occurred because it is a dependant of WCB001-KER000-79.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-126/


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



--
Code Changes
--
nuwanw (137801):

>removed sleep

nuwanw (137799):

>added esb integration test cases by patches

nuwanw (137800):

>added esb integration test cases by patches



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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #125 has FAILED. Change made by 7 authors.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #125 failed.
---
This build occurred because it is a dependant of WCB001-KER000-78.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-125/


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



--
Code Changes
--
shammi (137797):

>Upgrading the andes-client version

ajithn (137776):

>add 4.0.1 bundle
>

prabatha (137786):

>improving result filtering



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

Re: [Dev] Help - Invoking basic-auth secured WS

2012-08-13 Thread Mohammad Benslimne 
Please, any help ... ?

On 10 August 2012 14:11, Mohammad Benslimne
wrote:

> Hi,
>
> So any recipes to invoke a basic-auth secured WS within a BPEL process to
> be executed in WSO2 BPS ?
> Thanks in advance ...
>
> Mohammad
>
> On 10 August 2012 13:49, Denis Weerasiri  wrote:
>
>>
>>
>> On Fri, Aug 10, 2012 at 7:53 PM, Mohammad Benslimne <
>> mohammad.benslim...@gmail.com> wrote:
>>
>>> Hello folks,
>>>
>>> I am using WSO2 BPS 2.1.2
>>> Please, would you have examples for invoking basic-auth secured WS ? How
>>> could I insert Authorization http header in secured WS request ?
>>>
>>> I tried unified endpoints, but I got java.lang.NullPointerException at
>>> org.wso2.carbon.bpel.core.ode.integration.config.EndpointConfiguration.getUnifiedEndpoint
>>> when defining  tag (cf.
>>> http://osdir.com/ml/general/2012-05/msg47734.html).
>>>
>>> I tried also defining the Autorization header in  in
>>> deploy.xml (cf.
>>> http://wso2.org/project/bps/2.0.2/docs/user_guide.html#Using-Manipulating-Endpoints),
>>> no effect!
>>>
>> Hi,
>> AFAIK, this feature is not included in 2.1.2. But it is included in the
>> upcoming WSO2 BPS release.
>>
>>>  Many thanks for any help ...
>>>
>>>
>>> Best regards,
>>> Mohammad
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks,
>> Denis
>> --
>> *Denis Weerasiri*
>> Senior Software Engineer
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com,
>> *email: denis ** [AT] wso2.com 
>> *
>> *phone: +94117639629
>> *
>> *site: 
>> **https://sites.google.com/site/ddweerasiri/*
>> *blog: **http://ddweerasiri.blogspot.com*
>> *
>> twitter: **http://twitter.com/ddweerasiri*
>> *
>> linked-in: 
>> **http://lk.linkedin.com/in/ddweerasiri*
>>
>>
>
>
> --
>
>
> Mohammad
>
>


-- 


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

Re: [Dev] Changing JIRA project name of API Manager

2012-08-13 Thread Hiranya Jayathilaka 
On Mon, Aug 13, 2012 at 12:08 PM, Samisa Abeysinghe  wrote:

>
>
> On Mon, Aug 13, 2012 at 12:00 PM, Sumedha Rubasinghe wrote:
>
>> Project ID will be either AM or APIMANAGER. Name remains the same ('WSO2
>> API Manager ').
>> There will be components to reflect store, publisher, gateway, etc..
>
>
> +1 for creating a new one.
>

+1 for APIMANAGER and the suggested components.


>
>
>>
>>
>>
>> On Mon, Aug 13, 2012 at 11:56 AM, Samisa Abeysinghe wrote:
>>
>>> What is the new name?
>>>
>>> On Mon, Aug 13, 2012 at 11:54 AM, Sumedha Rubasinghe 
>>> wrote:
>>>
 Due to historical reasons JIRA project id for API Manager is 'APISTORE'
 - https://wso2.org/jira/browse/APISTORE.  JIRA doesn't allow us to
 change the string 'APISTORE' once used.
 During one of the discussions, it was decided to change this after
 1.0.0 release. I am thinking of doing this now & moving all unresolved
 issues to new project. Any concerns?

 --
 /sumedha
 +94 773017743

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

 Thanks,
>>> Samisa...
>>>
>>> Samisa Abeysinghe
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>>
>>>
>>>
>>
>>
>> --
>> /sumedha
>> +94 773017743
>>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] [ANN] WSO2 Message Broker 2.0.0 -Beta Released !!!

2012-08-13 Thread Shammi Jayasinghe 
*WSO2 Message Broker 2.0.0- BetaReleased!*

WSO2 MB team is pleased to announce the 2.0.0-Beta release of the WSO2 Message
Broker.

WSO2 Message Broker 2.0.0 , JMS message broker backed up with the wso2
distributed message brokering engine "Andes" is compliant with AMQP 0-91
version.

You can download this distribution and the documentation from
http://people.wso2.com/~shammi/MessageBroker-2.0-Beta/

*How to Run,*

   1. Extract the downloaded zip
   2. Go to the bin directory in the extracted folder
   3. Run the wso2server.sh or wso2server.bat as appropriate
   4. Point your browser to the URL https://localhost:9443/carbon
   5. Use "admin", "admin" as the username and password to login as an
admin and create a user account
   6. Use the documentation to get to know on how to creating clients,
using clients and deployment guide to do clustering.

Release Notes - WSO2 Message Broker - Version WSO2 MB 2.0 - Beta
Bug

   - [MB-26 ] - Fix Shut down errors
   - [MB-29 ] - Pagination is not
   working on Queue Listing page
   - [MB-30 ] - Fix OOM errors occur in
   sending large # of messages

Improvement

   - [MB-14 ] - Prepare valid samples
   for MB2.0
   - [MB-27 ] - Update the
   documentation of specifying the maximum number of sessions for connection

New Feature

   - [MB-8 ] - Message Broker Cluster
   Management Component



Cheers...
Best Regards,*
*
WSO2 Message Broker Team..
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #124 has FAILED. Change made by 20 authors.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #124 failed.
---
This build occurred because it is a dependant of WCB001-KER000-77.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-124/


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



--
Code Changes
--
ishan (137741):

>Created new version.

sinthuja (137752):

>adding 4.0.1 to fix https://wso2.org/jira/browse/BAM-612

nuwand (137692):

>Fixing ESBJAVA-1408



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

Re: [Dev] Missing Requirements for org.wso2.carbon.registry.extensions.server.feature when trying to install API-Manager Feature Category from repository

2012-08-13 Thread Senaka Fernando 
Hi Dileepa,

Are you building on a fresh repo? Never ran into such issues during the AM
build in the past, so there might have been some issues in the build itself.

Thanks,
Senaka.

On Mon, Aug 13, 2012 at 5:52 PM, Dileepa Jayakody  wrote:

> Has anybody come across this error when installing registry.extensions
> feature to carbon4?
> I see a somewhat similar issue when trying to build c4_release_tag's
> apimanager's p2-profile;
>
> *
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: WSO2 Carbon - Governance Metadata Feature 4.0.0
> (org.wso2.carbon.governance.metadata.feature.group 4.0.0)
>  Missing requirement: org.wso2.carbon.registry.extensions 4.0.0
> (org.wso2.carbon.registry.extensions 4.0.0) requires 'package 
> org.apache.maven.scm
> [1.7.0,2.0.0)' but it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Governance Metadata Feature 4.0.0
> (org.wso2.carbon.governance.metadata.feature.group 4.0.0)
>   To: org.wso2.carbon.governance.metadata.server.feature.group [4.0.0]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Governance Metadata Server Feature 4.0.0
> (org.wso2.carbon.governance.metadata.server.feature.group 4.0.0)
>   To: org.wso2.carbon.governance.services [4.0.0]
>  Cannot satisfy dependency:
>   From: org.wso2.carbon.governance.services 4.0.0
> (org.wso2.carbon.governance.services 4.0.0)
>   To: package org.wso2.carbon.registry.extensions.utils 0.0.0*
>
> Both org.codehaus.plexus and org.apache.maven.scm packages are exported by
> dependencies/orbit/maven-scm bundle and the default version attached to all
> exported packages is : 1.7.0.ws o2v1.
>
> Could this be version issue with the exported packages?
>
> Thanks,
> Dileepa
>
>
> On Mon, Aug 13, 2012 at 11:50 AM, Dileepa Jayakody wrote:
>
>> Hi All,
>>
>> I tried installing API-Manager category to carbon-4.0.0 from the feature
>> repository of 4.0.0 branch, And got following unsatisfied dependency for
>> org.wso2.carbon.registry.extensions 4.0.0;
>>
>> Cannot complete the install because one or more required items could not
>> be found. Software being installed: WSO2 Carbon - Registry Extensions
>> Feature 4.0.0 (org.wso2.carbon.registry.extensions.feature.group 4.0.0)
>> Missing requirement: org.wso2.carbon.registry.extensions 4.0.0
>> (org.wso2.carbon.registry.extensions 4.0.0) requires 'package 
>> *org.codehaus.plexus
>> [1.7.0,2.0.0)*' but it could not be found Cannot satisfy dependency:
>> From: WSO2 Carbon - Registry Extensions Feature 4.0.0
>> (org.wso2.carbon.registry.extensions.feature.group 4.0.0) To:
>> org.wso2.carbon.registry.extensions.server.feature.group [4.0.0] Cannot
>> satisfy dependency: From: WSO2 Carbon - Registry Extensions Server Feature
>> 4.0.0 (org.wso2.carbon.registry.extensions.server.feature.group 4.0.0) To:
>> org.wso2.carbon.registry.extensions [4.0.0]
>>
>> Which bundle exports org.codehaus.plexus [1.7.0,2.0.0)?
>> Any idea on resolving this?
>>
>> Thanks,
>> Dileepa
>> --
>> Dileepa Jayakody,
>> Software Engineer, WSO2 Inc.
>> Lean . Enterprise . Middleware
>>
>> Mobile : +94777-857616
>>
>>
>
>
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

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

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

Re: [Dev] Multirooted JSON this time Facebook ... 441 documentation ? where

2012-08-13 Thread Dushan Abeyruwan 
Hi
  When provide  JSONStreamBuilder/JSONStreamFormatter *did work*, but
with JSONOMBuilder/Formatter request getting hanged and never return
response

Trying 127.0.0.1... connected
> GET
/services/facebookProfile?access_token=AAAFBlVaM5ZAQBABZBKLQt2VCZAyJhoH4k2BxrzClmcY8kqMBDgx1eG7FEdiWxL2FYrUFZCvsuqlhcMy7Ryo19s4QEHWnXSYRWxZBoZChYJcgZDZD
HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: localhost:8281
> Accept: */*
> Content-Type: text/javascript
>
* Empty reply from server
* Connection #0 to host localhost left intact
curl: (52) Empty reply from server
* Closing connection #0


this is curl command
curl -v -H "Content-Type: text/javascript"
http://localhost:8281/services/facebookProfile?access_token=

proxy

   





https://graph.facebook.com/me";
format="rest"/>









cheers
Dushan



On Mon, Aug 13, 2012 at 11:11 AM, Ishan Jayawardena  wrote:

> Also ayya, if you don't need to do anything to the JSON payload within the
> ESB, just use JSONStreamBuilder/JSONStreamFormatter for your purpose. You
> only need to modify axis2.xml for text/javascript content type.
>
> On Mon, Aug 13, 2012 at 11:08 AM, Ishan Jayawardena wrote:
>
>> Your request line must be;
>> curl -v -H "Content-Type: text/javascript"
>> http://localhost:8280/services/facebookProfile?access_token=...
>>
>>
>> you have to mention the correct content type.
>> bye...
>>
>> On Mon, Aug 13, 2012 at 5:25 AM, Dushan Abeyruwan wrote:
>>
>>> HI
>>>   I have following requirement,
>>>  When I access facebook profile as this
>>>   curl  -v 
>>> https://graph.facebook.com/me?access_token=>> TOKE>
>>>
>>>it returns me  json response as follows
>>>
>>> {"id":"","name":"xx xx
>>> xx","first_name":"xx","middle_name":"xx","last_name":"xx","link":"http:\/\/
>>> www.facebook.com
>>> \/xx","username":"xxx","work":[{"employer":{"id":"xx","name":"xx"},"position":{"id":"xx","name":"xx"},"start_date":"-00"}],"
>>>
>>> its a multirooted element : ) content type  is script/text
>>> *
>>> *
>>> *Now wann a process this via ESB...  btw ( where is sample 441
>>> documented ?)   *
>>>
>>>
>>> created a proxy as follows  (as sample 441 suggested to handle root
>>> element)
>>>
>>> >> trace="disable">
>>> 
>>> 
>>> 
>>> 
>>> 
>>> https://graph.facebook.com/me"/>
>>> 
>>> 
>>> 
>>> 
>>>  *   mc.setPayloadJSON(*
>>> *   {*
>>> * "Profie" : {*
>>> *"id" : "dd",*
>>> *"name" :  "dd",*
>>> *   .*
>>> *} *
>>> * },*
>>> *   *
>>> *   });*
>>> >> scope="axis2"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> but still  i am getting ..when access
>>>  http://localhost:8281/services/facebookProfile?access_toke= via
>>> ESB..   Connection #0 to host localhost left intact
>>> * Closing connection #0
>>> *{"id":""}   Seems like JSON payload is not replaced... wher should
>>> probably i went wrong..*
>>>
>>> Am I missing something.?   SOS
>>>
>>> btw.. question,
>>>
>>> If client needs the same *original FACEBOOK* json response.BECAUSE
>>> their applicaiton handles multiroot... what shall we do?.. cos we are
>>> modifiying the original response with some root..because our *ESB*
>>>
>>>
>>>
>>> cheers,
>>> Dushan Abeyruwan
>>> *Senior Software Engineer*
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/*
>>> *Mobile:(+94)714408632*
>>>
>>>
>>
>>
>> --
>> Ishan Jayawardena
>> Software Engineer
>> WSO2, Inc. http://wso2.com/
>> *Mobile: +94-774-082-330*
>>
>>
>>
>
>
> --
> Ishan Jayawardena
> Software Engineer
> WSO2, Inc. http://wso2.com/
> *Mobile: +94-774-082-330*
>
>
>


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

Re: [Dev] ESB , IS , BAM2 and LB building with carbon kernel - 4.0.0

2012-08-13 Thread Ishan Jayawardena 
Hi Ajith, we have already modified the ESB to use kernel 4.0.1.
Thanks,
Ishan.

On Mon, Aug 13, 2012 at 5:48 PM, Ajith Vitharana  wrote:

> Hi All,
>
> Please update your product to build with carbon-kernel 4.0.1.
> Currently ,those packs are not compatible to use with AS (using
> kernel-4.0.1).
>
> Thanks
> Ajithn
>
> --
> 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
>
>


-- 
Ishan Jayawardena
Software Engineer
WSO2, Inc. http://wso2.com/
*Mobile: +94-774-082-330*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Missing Requirements for org.wso2.carbon.registry.extensions.server.feature when trying to install API-Manager Feature Category from repository

2012-08-13 Thread Dileepa Jayakody 
Has anybody come across this error when installing registry.extensions
feature to carbon4?
I see a somewhat similar issue when trying to build c4_release_tag's
apimanager's p2-profile;

*Cannot complete the install because one or more required items could not
be found.
 Software being installed: WSO2 Carbon - Governance Metadata Feature 4.0.0
(org.wso2.carbon.governance.metadata.feature.group 4.0.0)
 Missing requirement: org.wso2.carbon.registry.extensions 4.0.0
(org.wso2.carbon.registry.extensions 4.0.0) requires 'package
org.apache.maven.scm
[1.7.0,2.0.0)' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Governance Metadata Feature 4.0.0
(org.wso2.carbon.governance.metadata.feature.group 4.0.0)
  To: org.wso2.carbon.governance.metadata.server.feature.group [4.0.0]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Governance Metadata Server Feature 4.0.0
(org.wso2.carbon.governance.metadata.server.feature.group 4.0.0)
  To: org.wso2.carbon.governance.services [4.0.0]
 Cannot satisfy dependency:
  From: org.wso2.carbon.governance.services 4.0.0
(org.wso2.carbon.governance.services 4.0.0)
  To: package org.wso2.carbon.registry.extensions.utils 0.0.0*

Both org.codehaus.plexus and org.apache.maven.scm packages are exported by
dependencies/orbit/maven-scm bundle and the default version attached to all
exported packages is : 1.7.0.ws o2v1.

Could this be version issue with the exported packages?

Thanks,
Dileepa

On Mon, Aug 13, 2012 at 11:50 AM, Dileepa Jayakody  wrote:

> Hi All,
>
> I tried installing API-Manager category to carbon-4.0.0 from the feature
> repository of 4.0.0 branch, And got following unsatisfied dependency for
> org.wso2.carbon.registry.extensions 4.0.0;
>
> Cannot complete the install because one or more required items could not
> be found. Software being installed: WSO2 Carbon - Registry Extensions
> Feature 4.0.0 (org.wso2.carbon.registry.extensions.feature.group 4.0.0)
> Missing requirement: org.wso2.carbon.registry.extensions 4.0.0
> (org.wso2.carbon.registry.extensions 4.0.0) requires 'package 
> *org.codehaus.plexus
> [1.7.0,2.0.0)*' but it could not be found Cannot satisfy dependency:
> From: WSO2 Carbon - Registry Extensions Feature 4.0.0
> (org.wso2.carbon.registry.extensions.feature.group 4.0.0) To:
> org.wso2.carbon.registry.extensions.server.feature.group [4.0.0] Cannot
> satisfy dependency: From: WSO2 Carbon - Registry Extensions Server Feature
> 4.0.0 (org.wso2.carbon.registry.extensions.server.feature.group 4.0.0) To:
> org.wso2.carbon.registry.extensions [4.0.0]
>
> Which bundle exports org.codehaus.plexus [1.7.0,2.0.0)?
> Any idea on resolving this?
>
> Thanks,
> Dileepa
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
>


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

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

[Dev] ESB , IS , BAM2 and LB building with carbon kernel - 4.0.0

2012-08-13 Thread Ajith Vitharana 
Hi All,

Please update your product to build with carbon-kernel 4.0.1.
Currently ,those packs are not compatible to use with AS (using
kernel-4.0.1).

Thanks
Ajithn

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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #123 has FAILED. Change made by 15 authors.

2012-08-13 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #123 failed.
---
This build occurred because it is a dependant of WCB001-KER000-76.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-123/


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



--
Code Changes
--
pradeep (137608):

>commiting the fix provided by azeez: handling unversioned files withing 
>deployment/server respository

Kishanthan Thangarajah (137643):

>removing unwanted info level log from webapp deployer

ishan (137635):

>Setting JSONBuilder/JSONMessageFormatter default.



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

Re: [Dev] Build error in BPEL4People Extension - 4.0.1 branch.

2012-08-13 Thread Muhammed Shariq 
Building the 4.0.0 branch fixed the issue, thanks Nandika for pointing it
out! :)

On Mon, Aug 13, 2012 at 2:21 PM, Muhammed Shariq  wrote:

> On Mon, Aug 13, 2012 at 1:24 PM, Sanjaya Vithanagama wrote:
>
>> Hi Shariq,
>>
>> Is your components/business-processes updated and built?
>>
>
> Um yes it is up-to-date and I am still getting this error, any other
> places that needs to updated ?!
>
>>
>> Regards,
>> SanjayaV.
>>
>> On Mon, Aug 13, 2012 at 1:13 PM, Muhammed Shariq  wrote:
>>
>>> [INFO] WSO2 Carbon - BPEL BPEL4People Extension .. FAILURE
>>> [2.143s]
>>> [INFO] WSO2 Carbon - BPEL BAM publishing Extension ... SKIPPED
>>> [INFO] WSO2 Carbon - Human Task Engine ... SKIPPED
>>> [INFO] WSO2 Carbon - HumanTask Deployer Component  SKIPPED
>>> [INFO] WSO2 Carbon - HumanTask UI  SKIPPED
>>> [INFO] WSO2 Carbon - HumanTask Cleanup SchedulerComponent  SKIPPED
>>> [INFO] WSO2 Carbon - Attachment Management BE Component .. SKIPPED
>>> [INFO] WSO2 Carbon - Patch releases - components - Aggregator Module
>>>  SKIPPED
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 33.497s
>>> [INFO] Finished at: Mon Aug 13 13:10:16 IST 2012
>>> [INFO] Final Memory: 139M/798M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>> (default-compile) on project org.wso2.carbon.bpel.b4p: Compilation failure:
>>> Compilation failure:
>>> [ERROR]
>>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[36,44]
>>> package org.wso2.carbon.bpel.common.constants does not exist
>>> [ERROR]
>>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[36,44]
>>> package org.wso2.carbon.bpel.common.constants does not exist
>>> [ERROR]
>>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[111,33]
>>> cannot find symbol
>>> [ERROR] symbol  : variable Constants
>>> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
>>> [ERROR]
>>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[112,40]
>>> cannot find symbol
>>> [ERROR] symbol  : variable Constants
>>> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
>>> [ERROR]
>>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[113,43]
>>> cannot find symbol
>>> [ERROR] symbol  : variable Constants
>>> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
>>> [ERROR]
>>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[114,42]
>>> cannot find symbol
>>> [ERROR] symbol  : variable Constants
>>> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
>>> [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.bpel.b4p
>>>
>>>
>>> --
>>> Thanks,
>>> Shariq.
>>> Phone: +94 777 202 225
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sanjaya Vithanagama
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 342 2881
>>
>>
>
>
> --
> Thanks,
> Shariq.
> Phone: +94 777 202 225
>
>


-- 
Thanks,
Shariq.
Phone: +94 777 202 225
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to correctly define a Feature Category in p2 repository

2012-08-13 Thread Dileepa Jayakody 
On Fri, Aug 10, 2012 at 6:36 PM, Dileepa Jayakody  wrote:

> Hi all,
>
> This is to clarify the process of defining a category in
> features/repository pom correctly. A feature category in the p2-repo should
> represent a product. (eg: Application Server, Data Services Server etc..)
> It should make life easy for a user to install all features relevant to a
> product at once by selecting the relevant product category.
> eg: if the user wants to install Application Server on top of Carbon, the
> user can simply select the "Application Server" category and install all
> features grouped under that category.
>
> The process of adding a feature category to represent a product should
> follow below steps;
>
> 1. First you need to know all the features required to install your
> product; this is defined in the product's p2-profile-gen.
>
> Then in the features/repository/pom.xml;
> 2. Make sure all the required features are published to the repository;
> this happens in carbon-p2-plugin's p2-repo-gen goal. So all required
> features should be included under .
> 3. Now create a  to represent your product under 
> section.
> 4. Include the relevant feature list as s under your category
> except the product's styles feature.
>Note:  Please note that,  and  are required for a.
>
>   is the feature's p2-artifact-id given in the feature's
> pom under p2-feature-gen goal of the carbon-p2-plugin. If a version for the
> p2-artifact isn't explicitly defined, it will inherit the feature's maven
> artifact's version.
>   eg: In
> platform/features/admin-mgt/org.wso2.carbon.admin.mgt.feature/pom.xml
>The p2 artifact-id given for
> org.wso2.carbon.admin.mgt.feature is *org.wso2.carbon.admin.mgt*
> 5. The styles feature should not be grouped under the Product category by
> default, because then if the user selects several product categories at
> once, it will try to install several product styles at once and break the
> server's style. The solution is to have a seperate feature category for
> Product Styles. Then the user can select the product style to install
> separately.
>

6. Another important thing is to test the installation of your category on
carbon at-least once, to see if there are any missing requirements for the
installation. Please make sure you test your category installation on
carbon at-least once before committing.

>
> For reference of above category samples; you can refer to the Application
> Server and Data Services Server categories defined in Trunk's
> features/repository pom.
>
> Thanks,
> Dileepa
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
>


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

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

Re: [Dev] Build error in BPEL4People Extension - 4.0.1 branch.

2012-08-13 Thread Muhammed Shariq 
On Mon, Aug 13, 2012 at 1:24 PM, Sanjaya Vithanagama wrote:

> Hi Shariq,
>
> Is your components/business-processes updated and built?
>

Um yes it is up-to-date and I am still getting this error, any other places
that needs to updated ?!

>
> Regards,
> SanjayaV.
>
> On Mon, Aug 13, 2012 at 1:13 PM, Muhammed Shariq  wrote:
>
>> [INFO] WSO2 Carbon - BPEL BPEL4People Extension .. FAILURE
>> [2.143s]
>> [INFO] WSO2 Carbon - BPEL BAM publishing Extension ... SKIPPED
>> [INFO] WSO2 Carbon - Human Task Engine ... SKIPPED
>> [INFO] WSO2 Carbon - HumanTask Deployer Component  SKIPPED
>> [INFO] WSO2 Carbon - HumanTask UI  SKIPPED
>> [INFO] WSO2 Carbon - HumanTask Cleanup SchedulerComponent  SKIPPED
>> [INFO] WSO2 Carbon - Attachment Management BE Component .. SKIPPED
>> [INFO] WSO2 Carbon - Patch releases - components - Aggregator Module
>>  SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 33.497s
>> [INFO] Finished at: Mon Aug 13 13:10:16 IST 2012
>> [INFO] Final Memory: 139M/798M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.bpel.b4p: Compilation failure:
>> Compilation failure:
>> [ERROR]
>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[36,44]
>> package org.wso2.carbon.bpel.common.constants does not exist
>> [ERROR]
>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[36,44]
>> package org.wso2.carbon.bpel.common.constants does not exist
>> [ERROR]
>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[111,33]
>> cannot find symbol
>> [ERROR] symbol  : variable Constants
>> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
>> [ERROR]
>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[112,40]
>> cannot find symbol
>> [ERROR] symbol  : variable Constants
>> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
>> [ERROR]
>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[113,43]
>> cannot find symbol
>> [ERROR] symbol  : variable Constants
>> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
>> [ERROR]
>> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[114,42]
>> cannot find symbol
>> [ERROR] symbol  : variable Constants
>> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
>> [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.bpel.b4p
>>
>>
>> --
>> Thanks,
>> Shariq.
>> Phone: +94 777 202 225
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sanjaya Vithanagama
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 342 2881
>
>


-- 
Thanks,
Shariq.
Phone: +94 777 202 225
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build error in BPEL4People Extension - 4.0.1 branch.

2012-08-13 Thread Sanjaya Vithanagama 
Hi Shariq,

Is your components/business-processes updated and built?

Regards,
SanjayaV.

On Mon, Aug 13, 2012 at 1:13 PM, Muhammed Shariq  wrote:

> [INFO] WSO2 Carbon - BPEL BPEL4People Extension .. FAILURE [2.143s]
> [INFO] WSO2 Carbon - BPEL BAM publishing Extension ... SKIPPED
> [INFO] WSO2 Carbon - Human Task Engine ... SKIPPED
> [INFO] WSO2 Carbon - HumanTask Deployer Component  SKIPPED
> [INFO] WSO2 Carbon - HumanTask UI  SKIPPED
> [INFO] WSO2 Carbon - HumanTask Cleanup SchedulerComponent  SKIPPED
> [INFO] WSO2 Carbon - Attachment Management BE Component .. SKIPPED
> [INFO] WSO2 Carbon - Patch releases - components - Aggregator Module
>  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 33.497s
> [INFO] Finished at: Mon Aug 13 13:10:16 IST 2012
> [INFO] Final Memory: 139M/798M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.bpel.b4p: Compilation failure:
> Compilation failure:
> [ERROR]
> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[36,44]
> package org.wso2.carbon.bpel.common.constants does not exist
> [ERROR]
> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[36,44]
> package org.wso2.carbon.bpel.common.constants does not exist
> [ERROR]
> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[111,33]
> cannot find symbol
> [ERROR] symbol  : variable Constants
> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
> [ERROR]
> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[112,40]
> cannot find symbol
> [ERROR] symbol  : variable Constants
> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
> [ERROR]
> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[113,43]
> cannot find symbol
> [ERROR] symbol  : variable Constants
> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
> [ERROR]
> /home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[114,42]
> cannot find symbol
> [ERROR] symbol  : variable Constants
> [ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
> [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.bpel.b4p
>
>
> --
> Thanks,
> Shariq.
> Phone: +94 777 202 225
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sanjaya Vithanagama
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 342 2881
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build error in BPEL4People Extension - 4.0.1 branch.

2012-08-13 Thread Muhammed Shariq 
[INFO] WSO2 Carbon - BPEL BPEL4People Extension .. FAILURE [2.143s]
[INFO] WSO2 Carbon - BPEL BAM publishing Extension ... SKIPPED
[INFO] WSO2 Carbon - Human Task Engine ... SKIPPED
[INFO] WSO2 Carbon - HumanTask Deployer Component  SKIPPED
[INFO] WSO2 Carbon - HumanTask UI  SKIPPED
[INFO] WSO2 Carbon - HumanTask Cleanup SchedulerComponent  SKIPPED
[INFO] WSO2 Carbon - Attachment Management BE Component .. SKIPPED
[INFO] WSO2 Carbon - Patch releases - components - Aggregator Module
 SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 33.497s
[INFO] Finished at: Mon Aug 13 13:10:16 IST 2012
[INFO] Final Memory: 139M/798M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.bpel.b4p: Compilation failure:
Compilation failure:
[ERROR]
/home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[36,44]
package org.wso2.carbon.bpel.common.constants does not exist
[ERROR]
/home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[36,44]
package org.wso2.carbon.bpel.common.constants does not exist
[ERROR]
/home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[111,33]
cannot find symbol
[ERROR] symbol  : variable Constants
[ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
[ERROR]
/home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[112,40]
cannot find symbol
[ERROR] symbol  : variable Constants
[ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
[ERROR]
/home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[113,43]
cannot find symbol
[ERROR] symbol  : variable Constants
[ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
[ERROR]
/home/shariq/src/4.0.0-branch/platform/components/business-processes/bpel/org.wso2.carbon.bpel.b4p/4.0.1/src/main/java/org/wso2/carbon/bpel/b4p/utils/SOAPHelper.java:[114,42]
cannot find symbol
[ERROR] symbol  : variable Constants
[ERROR] location: class org.wso2.carbon.bpel.b4p.utils.SOAPHelper
[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.bpel.b4p


-- 
Thanks,
Shariq.
Phone: +94 777 202 225
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Where is Siddhi 1.0.0.wso2v2

2012-08-13 Thread Suhothayan Sriskandarajah 
Siddhi is in dependencies/commons and siddhi-1.0.0-wso2v2 dont have an
orbit
Its all ready added to the patch release pom. I think your code is not up
to date please do take an update.

Suho


On Mon, Aug 13, 2012 at 12:20 PM, Nuwan Bandara  wrote:

> hi
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 8.414s
> [INFO] Finished at: Mon Aug 13 12:17:46 IST 2012
> [INFO] Final Memory: 77M/554M
> [INFO]
> 
> [ERROR] Failed to execute goal on project org.wso2.carbon.cep.siddhi:
> Could not resolve dependencies for project
> org.wso2.carbon:org.wso2.carbon.cep.siddhi:bundle:4.0.1: The following
> artifacts could not be resolved:
> org.wso2.siddhi:siddhi-api:jar:1.0.0-wso2v2,
> org.wso2.siddhi:siddhi-core:jar:1.0.0-wso2v2,
> org.wso2.siddhi:siddhi-query:jar:1.0.0-wso2v2: Failure to find
> org.wso2.siddhi:siddhi-api:jar:1.0.0-wso2v2 in
> http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
> local repository, resolution will not be reattempted until the update
> interval of wso2-nexus has elapsed or updates are forced -> [Help 1]
>
> ??
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Associate Technical Lead & Member, MC, Development Technologies
> WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
> blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
> 9629
> *
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*S. Suhothayan
*
Software Engineer,
Data Technologies Team,
 *WSO2, Inc. **http://wso2.com
 *
*lean.enterprise.middleware.*

*email: **s...@wso2.com* * cell: (+94) 779 756 757
blog: **http://suhothayan.blogspot.com/* *
twitter: **http://twitter.com/suhothayan* *
linked-in: **http://lk.linkedin.com/in/suhothayan*
*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev