date:20120622

Dude!
It is not working perfectly. Look at the bottom of the page. The line does
not connect to the bottom. The copyright statement has gone missing. Take
another look at the image you have sent.


On Fri, Jun 22, 2012 at 11:41 AM, Kathiravelu Pradeeban
pradee...@wso2.comwrote:

 Hi Azeez,
 Actually it is working perfectly, You just don't have enough tenants to
 show the pagination. As 15 tenants fit into one page, the next buttons are
 not shown for the usability, by the paginator, when you don't have more
 than 15 tenants.

 See the attachment with 16 tenants added. The pagination is shown properly
 at the top and the bottom, with the 16th tenant in the 2nd page. This was a
 recent fix or enhancement made by Ashansa.

 Thank you.
 Regards,
 Pradeeban.


 On Fri, Jun 22, 2012 at 2:13 AM, Afkham Azeez az...@wso2.com wrote:

 See attachment. The bottom part of the page is missing.



 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 Kathiravelu Pradeeban.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Tenant list page is malformed - most probably some HTML closing tags are missing

2012-06-22 Thread Amila Maha Arachchi

Hi Pradeeban,

Page footer is missing.

AmilaM.

On Fri, Jun 22, 2012 at 11:41 AM, Kathiravelu Pradeeban
pradee...@wso2.comwrote:

 Hi Azeez,
 Actually it is working perfectly, You just don't have enough tenants to
 show the pagination. As 15 tenants fit into one page, the next buttons are
 not shown for the usability, by the paginator, when you don't have more
 than 15 tenants.

 See the attachment with 16 tenants added. The pagination is shown properly
 at the top and the bottom, with the 16th tenant in the 2nd page. This was a
 recent fix or enhancement made by Ashansa.

 Thank you.
 Regards,
 Pradeeban.


 On Fri, Jun 22, 2012 at 2:13 AM, Afkham Azeez az...@wso2.com wrote:

 See attachment. The bottom part of the page is missing.



 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 Kathiravelu Pradeeban.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976


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




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

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

Re: [Dev] Tenant list page is malformed - most probably some HTML closing tags are missing

On Fri, Jun 22, 2012 at 11:45 AM, Amila Maha Arachchi ami...@wso2.comwrote:

 Hi Pradeeban,

 Page footer is missing.


Now I got that. Thought Azeez was referring to the pagination links in the
bottom part. Thanks for clarifying AmilaM.
Will fix it.

Regards,
Pradeeban.



 AmilaM.

 On Fri, Jun 22, 2012 at 11:41 AM, Kathiravelu Pradeeban 
 pradee...@wso2.com wrote:

 Hi Azeez,
 Actually it is working perfectly, You just don't have enough tenants to
 show the pagination. As 15 tenants fit into one page, the next buttons are
 not shown for the usability, by the paginator, when you don't have more
 than 15 tenants.

 See the attachment with 16 tenants added. The pagination is shown
 properly at the top and the bottom, with the 16th tenant in the 2nd page.
 This was a recent fix or enhancement made by Ashansa.

 Thank you.
 Regards,
 Pradeeban.


 On Fri, Jun 22, 2012 at 2:13 AM, Afkham Azeez az...@wso2.com wrote:

 See attachment. The bottom part of the page is missing.



 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 Kathiravelu Pradeeban.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976


 ___
 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





-- 
Kathiravelu Pradeeban.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
M: +94 776 477 976
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Kernel Beta2 : Packs for smoke testing

2012-06-22 Thread Rajika Kumarasiri

I did the below smoke test and didn't find any issues in CSG.

Rajika

On Fri, Jun 22, 2012 at 9:59 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:

 Hi RMs,

 Please run a smoke test on the below packs and provide status.

 http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-248/artifact

 Smoke testing means
 1) All samples are working
 2) No errors on startup
 3) Login for super tenants and tenants working

 thanks,
 dimuthu

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


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

[Dev] Invitation: url mapper review @ Mon Jun 25 2:30pm - 3:30pm (dev@wso2.org)

2012-06-22 Thread Reka Thirunavukkarasu

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20120625T09Z
DTEND:20120625T10Z
DTSTAMP:20120622T064927Z
ORGANIZER;CN=Reka Thirunavukkarasu:mailto:r...@wso2.com
UID:4kob3mlr00su0u0ok1se6l2...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Selvaratnam Uthaiyashankar;X-NUM-GUESTS=0:mailto:shan...@wso2.com
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
 UE;CN=LK #59 2nd Floor Room;X-NUM-GUESTS=0:mailto:wso2.com_3832343234393438
 393...@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Pradeep Fernando;X-NUM-GUESTS=0:mailto:prad...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Afkham Azeez;X-NUM-GUESTS=0:mailto:az...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Sanjeewa Malalgoda;X-NUM-GUESTS=0:mailto:sanje...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Reka Thirunavukkarasu;X-NUM-GUESTS=0:mailto:r...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@wso2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Amani Soysa;X-NUM-GUESTS=0:mailto:am...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Dimuthu Leelarathne;X-NUM-GUESTS=0:mailto:dimut...@wso2.com
CREATED:20120622T064927Z
DESCRIPTION:Review the functionality of  context mapping for webapps and se
 rvices in AS with fronting LB.\nView your event at http://www.google.com/ca
 lendar/event?action=VIEWeid=NGtvYjNtbHIwMHN1MHUwb2sxc2U2bDI2YWMgZGV2QHdzbz
 Iub3Jntok=MTMjcmVrYUB3c28yLmNvbTNjODZkYWYzNjk3YWExMTE0YmQ3N2YxNmQ1Mjg1NDkw
 Yjc0Y2Y3OTcctz=Asia/Colombohl=en.
LAST-MODIFIED:20120622T064927Z
LOCATION:LK #59 2nd Floor Room
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:url mapper review
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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

[Dev] WSO2 Application Server Milestone4 (wso2as-5.0.0-SNAPSHOT_M4) released !

2012-06-22 Thread Kishanthan Thangarajah

Hi Folks,
The WSO2 is happy to announce the release of WSO2 Application Server
Milestone4.
Packs are hosted at [1].

New features included in this release are,

   - Merging of Service features (Application Server-as-a-Service) with
   Product.
   - Addition of Jaggery features with Product.
   - Merging of Mashup features with Product.
   - Samples for Jaggery and Mashup.


Thanks,
WSO2 Development Technologies Team.
[1] http://builder1.us1.wso2.org/~carbon320/releases/carbon/wso2as-5.0.0_M4/

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

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to do secondary indexing with bam-data-publisher for Stratos-Logging

This will be useful for folks who want real time data access, but BAM is
not designed to be real time. I don't want the Agent API to be specific to
Cassandra, either.

There should be a clean way to do this. How did you decide to do it this
way? Was there a discussion?

On Fri, Jun 22, 2012 at 8:45 AM, Amani Soysa am...@wso2.com wrote:

 Hi,

 Currently we are sending LogEvent data through bam data publisher to bam
 event receiver using a custom log4j appender. And we retrieve logs using
 the hector API for the carbon log viewer. However, we need to have
 secondary indexes for several columns so that we can filter log information
 for a given column ( such as date, applicationName, priority,logger etc)
 when creating the data publisher (keyspace). From the current Bam Data
 publisher implementation we cannot do secondary indexing all we can do is
 define the column name and the data type of that column, and reciver
 creates the keyspaces for given columns with their data types.

  streamId = dataPublisher.defineEventStream({ + 
 'name':'org.wso2.carbon.logging.$tenantId.$serverName',
+   'version':'1.0.0', +   'nickName': 'Logs',
+   'description': 'Logging Event', + 
  'metaData':[
+{'name':'clientType','type':'STRING'} + 
  ],
+   'payloadData':[
+   {'name':'tenantID','type':'STRING'},
+   {'name':'serverName','type':'
 STRING'},
+   {'name':'appName','type':'STRING'},
+   {'name':'logTime','type':'LONG'},
+   {'name':'logger','type':'STRING'},
+   {'name':'priority','type':'STRING'},
+   {'name':'message','type':'STRING'},
+   {'name':'ip','type':'STRING'},
+   {'name':'stacktrace','type':'
 STRING'},
 +   {'name':'instance','type':'STRING'}
+   ]
+ });

 Is it possible to have a cassandra specific event receiver (for logging
 purposes) so that we can create key spaces with secondary 
 indexes?[1https://wso2.org/jira/browse/CARBON-13468]
 and it will create keyspaces when ever logs are published . Or do we need
 to create keyspaces at tenant creation time?. For a given tenant we need to
 create several keyspaces, depending on the server (and if possible for
 applications as well so we can have better performance when viewing logs).
 ie - keyspace1 - org_wso2_logging_tenant1_application_server (store AS
 specific logs)
  keyspace2 - org_wso2_logging_tenant1_data_services_server  (store DSS
 specific logs)

 Please note that we cannot use BAM analytics  to view logs because we need
 a real time log-viwer.

 [1] - https://wso2.org/jira/browse/CARBON-13468

 Regards,
 Amani




-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maven snapshot repo

2012-06-22 Thread Maheshika Goonetilleke

On Fri, Jun 22, 2012 at 11:31 AM, Maheshika Goonetilleke mahesh...@wso2.com
 wrote:



 On Fri, Jun 22, 2012 at 10:35 AM, Samisa Abeysinghe sam...@wso2.comwrote:

 What is the cuase of this break?


 On Fri, Jun 22, 2012 at 10:25 AM, Maheshika Goonetilleke 
 mahesh...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 9:40 AM, Samisa Abeysinghe sam...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 7:36 AM, Nuwan Bandara nu...@wso2.com wrote:

 Hi All,

 I am in the process of removing jaggery code from our platform, and
 making it an independent project. I have added the snapshot repo to get
 our dependencies. will test this once am done with re-factoring.


 While this is the test case for the sanp reo, we need to have the first
 cut repo published and working. Maheshika please make sure you keep this
 thread updated on the progress, plus keep people informed on the build
 breaks etc until this 100% works.,

 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


 Hi All,

 The SNAPSHOT REPO is not updated as Kernel build is still stuck;

 build   20-Jun-2012 21:03:42[INFO] Scanning for projects...
 build   20-Jun-2012 21:03:43[INFO]
 build   20-Jun-2012 21:03:48[INFO] 
 
 build   20-Jun-2012 21:03:48[INFO] Building WSO2 Carbon - Parent 
 Pom 4.0.0-SNAPSHOT
 build   20-Jun-2012 21:03:48[INFO] 
 
 build   20-Jun-2012 21:03:48[INFO]
 build   20-Jun-2012 21:03:48[INFO] --- 
 maven-clean-plugin:2.4.1:clean (default-clean) @ carbon-parent ---
 build   20-Jun-2012 21:03:48[INFO] Deleting 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSC001-SCK001-JOB1/parent/target
 build   20-Jun-2012 21:03:48[INFO]
 build   20-Jun-2012 21:03:48[INFO] --- 
 incremental-build-plugin:1.3:incremental-build (default) @ carbon-parent ---
 build   20-Jun-2012 21:03:49[INFO] Verifying module descriptor ...
 build   20-Jun-2012 21:03:49[INFO] Pom descriptor modification 
 detected.
 build   20-Jun-2012 21:03:49[INFO] Deleting 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSC001-SCK001-JOB1/parent/target
 build   20-Jun-2012 21:03:49[INFO]
 build   20-Jun-2012 21:03:49[INFO] --- 
 maven-install-plugin:2.3.1:install (default-install) @ carbon-parent ---
 build   20-Jun-2012 21:03:49[INFO] Installing 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSC001-SCK001-JOB1/parent/pom.xml
  to 
 /home/bamboo/Bamboo-3.4/Bamboo/.m2/AGENT-18579458/repository/org/wso2/carbon/carbon-parent/4.0.0-SNAPSHOT/carbon-parent-4.0.0-SNAPSHOT.pom
 build   20-Jun-2012 21:03:50[INFO]
 build   20-Jun-2012 21:03:50[INFO] --- 
 maven-deploy-plugin:2.5:deploy (default-deploy) @ carbon-parent ---
 build   20-Jun-2012 21:03:50Downloading: 
 scp://dist.wso2.org/home/httpd/dist.wso2.org/snapshots/maven2/org/wso2/carbon/carbon-parent/4.0.0-SNAPSHOT/maven-metadata.xml


 Infrateam  Harshana is currently looking into this.
 --

 Thanks  Best Regards,

 Maheshika Goonetilleke
 Engineering Process Coordinator
 WSO2 Inc

 www.wso2.com/

 M : 0773 596707

  Thanks,
 Samisa...

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



 Hi

 Connection reset ;  scp://
 dist.wso2.org/home/httpd/dist.wso2.org/snapshots/maven2/http://dist.wso2.org/home/httpd/dist.wso2.org/snapshots/maven2/org/wso2/carbon/carbon-parent/4.0.0-SNAPSHOT/maven-metadata.xml

 --

 Thanks  Best Regards,

 Maheshika Goonetilleke
 Engineering Process Coordinator
 WSO2 Inc

 www.wso2.com/

 M : 0773 596707


Hi All

The above mentioned issue has been resolved.

However, the Carbon-SNAPSHOT-Kernel build has failed due to the following
error.

http://wso2.org/bamboo/download/WSC001-SCK001-JOB1/build_logs/WSC001-SCK001-JOB1-12.log


build   22-Jun-2012 00:03:40[INFO] BUILD FAILURE
build   22-Jun-2012 00:03:40[INFO]

build   22-Jun-2012 00:03:40[INFO] Total time: 39:50.317s
build   22-Jun-2012 00:03:40[INFO] Finished at: Fri Jun 22 00:03:40 PDT 2012
build   22-Jun-2012 00:03:41[INFO] Final Memory: 464M/983M
build   22-Jun-2012 00:03:41[INFO]

build   22-Jun-2012 00:03:41[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.4.2:test
(default-test) on project axis2-jaxws-integration: There are test
failures.
build   22-Jun-2012 00:03:41[ERROR]
build   22-Jun-2012 00:03:41[ERROR] Please refer to

Re: [Dev] Maven snapshot repo

2012-06-22 Thread Samisa Abeysinghe

This is a test failure in Axis2

On Fri, Jun 22, 2012 at 1:27 PM, Maheshika Goonetilleke
mahesh...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 11:31 AM, Maheshika Goonetilleke 
 mahesh...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 10:35 AM, Samisa Abeysinghe sam...@wso2.comwrote:

 What is the cuase of this break?


 On Fri, Jun 22, 2012 at 10:25 AM, Maheshika Goonetilleke 
 mahesh...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 9:40 AM, Samisa Abeysinghe sam...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 7:36 AM, Nuwan Bandara nu...@wso2.com wrote:

 Hi All,

 I am in the process of removing jaggery code from our platform, and
 making it an independent project. I have added the snapshot repo to get
 our dependencies. will test this once am done with re-factoring.


 While this is the test case for the sanp reo, we need to have the
 first cut repo published and working. Maheshika please make sure you keep
 this thread updated on the progress, plus keep people informed on the 
 build
 breaks etc until this 100% works.,

 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


 Hi All,

 The SNAPSHOT REPO is not updated as Kernel build is still stuck;

 build  20-Jun-2012 21:03:42[INFO] Scanning for projects...
 build  20-Jun-2012 21:03:43[INFO]
 build  20-Jun-2012 21:03:48[INFO] 
 
 build  20-Jun-2012 21:03:48[INFO] Building WSO2 Carbon - Parent 
 Pom 4.0.0-SNAPSHOT
 build  20-Jun-2012 21:03:48[INFO] 
 
 build  20-Jun-2012 21:03:48[INFO]
 build  20-Jun-2012 21:03:48[INFO] --- 
 maven-clean-plugin:2.4.1:clean (default-clean) @ carbon-parent ---
 build  20-Jun-2012 21:03:48[INFO] Deleting 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSC001-SCK001-JOB1/parent/target
 build  20-Jun-2012 21:03:48[INFO]
 build  20-Jun-2012 21:03:48[INFO] --- 
 incremental-build-plugin:1.3:incremental-build (default) @ carbon-parent 
 ---
 build  20-Jun-2012 21:03:49[INFO] Verifying module descriptor ...
 build  20-Jun-2012 21:03:49[INFO] Pom descriptor modification 
 detected.
 build  20-Jun-2012 21:03:49[INFO] Deleting 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSC001-SCK001-JOB1/parent/target
 build  20-Jun-2012 21:03:49[INFO]
 build  20-Jun-2012 21:03:49[INFO] --- 
 maven-install-plugin:2.3.1:install (default-install) @ carbon-parent ---
 build  20-Jun-2012 21:03:49[INFO] Installing 
 /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSC001-SCK001-JOB1/parent/pom.xml
  to 
 /home/bamboo/Bamboo-3.4/Bamboo/.m2/AGENT-18579458/repository/org/wso2/carbon/carbon-parent/4.0.0-SNAPSHOT/carbon-parent-4.0.0-SNAPSHOT.pom
 build  20-Jun-2012 21:03:50[INFO]
 build  20-Jun-2012 21:03:50[INFO] --- 
 maven-deploy-plugin:2.5:deploy (default-deploy) @ carbon-parent ---
 build  20-Jun-2012 21:03:50Downloading: 
 scp://dist.wso2.org/home/httpd/dist.wso2.org/snapshots/maven2/org/wso2/carbon/carbon-parent/4.0.0-SNAPSHOT/maven-metadata.xml


 Infrateam  Harshana is currently looking into this.
 --

 Thanks  Best Regards,

 Maheshika Goonetilleke
 Engineering Process Coordinator
 WSO2 Inc

 www.wso2.com/

 M : 0773 596707

  Thanks,
 Samisa...

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



 Hi

 Connection reset ;  scp://
 dist.wso2.org/home/httpd/dist.wso2.org/snapshots/maven2/http://dist.wso2.org/home/httpd/dist.wso2.org/snapshots/maven2/org/wso2/carbon/carbon-parent/4.0.0-SNAPSHOT/maven-metadata.xml

 --

 Thanks  Best Regards,

 Maheshika Goonetilleke
 Engineering Process Coordinator
 WSO2 Inc

 www.wso2.com/

 M : 0773 596707


 Hi All

 The above mentioned issue has been resolved.

 However, the Carbon-SNAPSHOT-Kernel build has failed due to the following
 error.


 http://wso2.org/bamboo/download/WSC001-SCK001-JOB1/build_logs/WSC001-SCK001-JOB1-12.log


 build 22-Jun-2012 00:03:40[INFO] BUILD FAILURE
 build 22-Jun-2012 00:03:40[INFO] 
 
 build 22-Jun-2012 00:03:40[INFO] Total time: 39:50.317s
 build 22-Jun-2012 00:03:40[INFO] Finished at: Fri Jun 22 00:03:40 PDT 2012
 build 22-Jun-2012 00:03:41[INFO] Final Memory: 464M/983M
 build 22-Jun-2012 00:03:41[INFO] 
 
 build 22-Jun-2012 00:03:41[ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-surefire-plugin:2.4.2:test (default-test) on 
 project axis2-jaxws-integration: There are test failures.
 build 22-Jun-2012 00:03:41[ERROR]
 build 22-Jun-2012 00:03:41[ERROR] Please refer to

[Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

Hi All,

I have notified that Sandesha2 module cant be engaged in the way which was
described in 
[1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
In the client side it shows the follwoing error,

ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
Operation not found is and the WSA Action = . If this EPR was previously
reachable, please contact the server administrator.

When I did a SOAP tracing in AS, I found that the Addressing module is
not engaged properly in the response SOAP message. That causes the
Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
following SOAP message is the SOAP message which was returned to the first
handshaking SOAP message, and it doesn't have addressing headers.

soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
   soapenv:Header /
   soapenv:Body
  ns:greetResponse xmlns:ns=http://www.wso2.org/types;
 returnHello World, AndunSLG !!!/return
  /ns:greetResponse
   /soapenv:Body
/soapenv:Envelope

In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line has
the following Boolean check which have to return true for
the correct excution,

return (rolePlayer == null || rolePlayer.isUltimateDestination());

But in the current carbon trunk, the rolePlayer object is a instance
of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
method isUltimateDestination() implemented as follows,

public boolean isUltimateDestination() {
return false;
}

So because of that
Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
disables the AddressignOutHandler. So no addressing happens at the out
flow. That causes all the trouble in Addressing and Sandesha2. I put return
true experimentally and that makes all the troubles back to normal. So is
the implementation of public boolean isUltimateDestination()  is correct ?
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

These are the Jira Issues related to this,

https://wso2.org/jira/browse/CARBON-13490
https://wso2.org/jira/browse/CARBON-13499

Thanks
AndunSLG

On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.com wrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the way which was
 described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope
 
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line has
 the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?


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

[Dev] Active Directory support in the new release

2012-06-22 Thread Suresh Attanayaka

Hi all,

Active Directory Read/Write support has been implemented in the trunk user
core. This implementation supports both Active Directory Domain Services
(AD DS) http://technet.microsoft.com/en-us/library/cc770946 and Active
Directory Lightweight Directory Services (AD
LDS)http://technet.microsoft.com/en-us/library/cc731868server roles.

Thanks,
Suresh

-- 
Suresh Attanayake
Software Engineer; WSO2 Inc. http://wso2.com/
Blog : http://sureshatt.blogspot.com/
Twitter : https://twitter.com/sureshatt
LinkedIn : http://lk.linkedin.com/in/sureshatt
Mobile : +94755012060,+94770419136,+94710467976
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon Kernel #336 has FAILED (10 tests failed). Change made by asela.


---
WSO2 Carbon  Kernel  #336 failed.
---
Code has been updated by asela.
10/2560 tests failed.

http://wso2.org/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-336/


--
Failing Jobs
--
  - Default Job (Default Stage): 10 of 2560 tests failed.



--
Code Changes
--
asela (130862):

change persistUser modifier to protected



--
Tests
--
New Test Failures (10)
   - MessageContextTests: W s ctxt w s d l i n t e r f a c e read
   - MessageContextTests: W s ctxt w s d l d e s c r i p t i o n read
   - MessageContextTests: W s ctxt w s d l p o r t read
   - MessageContextTests: W s ctxt w s d l o p e r a t i o n read
   - MessageContextTests: W s ctxt w s d l s e r v i c e read
   - OMElementDispatchTest: O m element dispatch with parsed entity reader
   - RuntimeExceptionsAsyncMepTest: Async polling async m e p web service 
exception
   - RuntimeExceptionsAsyncMepTest: Async callback async m e p wsdl fault
   - RuntimeExceptionsAsyncMepTest: Async polling async m e p wsdl fault
   - DispatchXPayloadStringTests: Simple

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

Re: [Dev] InfoCard/OpenID Sign-in menu in G-Reg.

2012-06-22 Thread Thilina Buddhika

This is coming from the Identity RP UI feature which are installed as a
dependency of  GApp feature in Stratos. There was a discussion to remove
GApp Feature from merged products and add it during the SLive deployment.

DimuthuL will be able to provide a more recent update on this.

Thanks,
Thilina

On Fri, Jun 22, 2012 at 1:38 PM, Ajith Vitharana aji...@wso2.com wrote:

 Hi All,

 Do we need to keep this feature in merged product ?

 Thanks
 Ajith

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





-- 
Thilina Buddhika
Associate Technical Lead
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

phone : +94 77 44 88 727
blog : http://blog.thilinamb.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to do secondary indexing with bam-data-publisher for Stratos-Logging

2012-06-22 Thread Amani Soysa

On Fri, Jun 22, 2012 at 1:24 PM, Tharindu Mathew thari...@wso2.com wrote:

 This will be useful for folks who want real time data access, but BAM is
 not designed to be real time. I don't want the Agent API to be specific to
 Cassandra, either.

 There should be a clean way to do this. How did you decide to do it this
 way? Was there a discussion?

Yes there was a discussion on this some time back on Architecture -RFC:
Architecture for Stratos Log Processing  where we decided to push logs to
bam event receiver through the publisher and view logs using hector api.



 On Fri, Jun 22, 2012 at 8:45 AM, Amani Soysa am...@wso2.com wrote:

 Hi,

 Currently we are sending LogEvent data through bam data publisher to bam
 event receiver using a custom log4j appender. And we retrieve logs using
 the hector API for the carbon log viewer. However, we need to have
 secondary indexes for several columns so that we can filter log information
 for a given column ( such as date, applicationName, priority,logger etc)
 when creating the data publisher (keyspace). From the current Bam Data
 publisher implementation we cannot do secondary indexing all we can do is
 define the column name and the data type of that column, and reciver
 creates the keyspaces for given columns with their data types.

  streamId = dataPublisher.defineEventStream({ + 
 'name':'org.wso2.carbon.logging.$tenantId.$serverName',
+   'version':'1.0.0', +   'nickName': 'Logs',
+   'description': 'Logging Event', + 
  'metaData':[
+{'name':'clientType','type':'STRING'} + 
  ],
+   'payloadData':[
+   {'name':'tenantID','type':'STRING'},
+   {'name':'serverName','type':'
 STRING'},
+   {'name':'appName','type':'STRING'},
+   {'name':'logTime','type':'LONG'},
+   {'name':'logger','type':'STRING'},
+   {'name':'priority','type':'STRING'},
+   {'name':'message','type':'STRING'},
+   {'name':'ip','type':'STRING'},
+   {'name':'stacktrace','type':'
 STRING'},
 +   {'name':'instance','type':'STRING'}

+   ]
+ });

 Is it possible to have a cassandra specific event receiver (for logging
 purposes) so that we can create key spaces with secondary 
 indexes?[1https://wso2.org/jira/browse/CARBON-13468]
 and it will create keyspaces when ever logs are published . Or do we need
 to create keyspaces at tenant creation time?. For a given tenant we need to
 create several keyspaces, depending on the server (and if possible for
 applications as well so we can have better performance when viewing logs).
 ie - keyspace1 - org_wso2_logging_tenant1_application_server (store AS
 specific logs)
  keyspace2 - org_wso2_logging_tenant1_data_services_server  (store
 DSS specific logs)

 Please note that we cannot use BAM analytics  to view logs because we
 need a real time log-viwer.

 [1] - https://wso2.org/jira/browse/CARBON-13468

 Regards,
 Amani




 --
 Regards,

 Tharindu

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


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

[Dev] Getting build failure in Integration test module

2012-06-22 Thread Chamara Silva

@subject pls.


[INFO]

[INFO] Building WSO2 Carbon - Integration Tests 4.0.0-SNAPSHOT
[INFO]

[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
org.wso2.carbon.integration.tests ---
[INFO] Deleting
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
[INFO]
[INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
org.wso2.carbon.integration.tests ---
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (auto-clean) @
org.wso2.carbon.integration.tests ---
[INFO] Deleting
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
org.wso2.carbon.integration.tests ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/src/main/resources
[INFO]
[INFO] --- maven-antrun-plugin:1.3:run
(org.wso2.carbon.integration.tests-include-sources) @
org.wso2.carbon.integration.tests ---
[INFO] Executing tasks
 [copy] Copying 2 files to
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/test-classes
[INFO] Executed tasks
[INFO]
[INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
org.wso2.carbon.integration.tests ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-dependency-plugin:2.1:copy-dependencies (default) @
org.wso2.carbon.integration.tests ---
[INFO] Copying emma-2.1.5320.jar to
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/emma/emma-2.1.5320.jar
[INFO] Copying org.wso2.carbon.integration.framework-4.0.0-SNAPSHOT.jar to
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/emma/org.wso2.carbon.integration.framework-4.0.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-dependency-plugin:2.1:copy-dependencies (copy-secVerifier)
@ org.wso2.carbon.integration.tests ---
[INFO] Copying SecVerifier.aar to
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/security-verifier/SecVerifier.aar
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources)
@ org.wso2.carbon.integration.tests ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @
org.wso2.carbon.integration.tests ---
[INFO] Compiling 9 source files to
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @
org.wso2.carbon.integration.tests ---
[INFO] Surefire report directory:
/home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/surefire-reports
[WARNING] Invalid POM for
org.apache.maven.surefire:surefire-testng:jar:2.12, transitive dependencies
(if any) will not be available, enable debug logging for more details

---
 T E S T S
---
org.apache.maven.surefire.util.SurefireReflectionException:
java.lang.ClassNotFoundException:
org.apache.maven.surefire.testng.TestNGProvider; nested exception is
java.lang.ClassNotFoundException:
org.apache.maven.surefire.testng.TestNGProvider
java.lang.ClassNotFoundException:
org.apache.maven.surefire.testng.TestNGProvider
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:97)
at
org.apache.maven.surefire.util.ReflectionUtils.loadClass(ReflectionUtils.java:228)
at
org.apache.maven.surefire.util.ReflectionUtils.instantiateOneArg(ReflectionUtils.java:128)
at
org.apache.maven.surefire.booter.SurefireReflector.instantiateProvider(SurefireReflector.java:239)
at
org.apache.maven.surefire.booter.ProviderFactory.createProvider(ProviderFactory.java:122)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:81)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)

Results :

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


Regards,
Chamara Silva

-- 
Suminda Chamara Silva
WSO2

Re: [Dev] How to do secondary indexing with bam-data-publisher for Stratos-Logging

2012-06-22 Thread Deependra Ariyadewa

On Fri, Jun 22, 2012 at 1:45 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 1:24 PM, Tharindu Mathew thari...@wso2.comwrote:

 This will be useful for folks who want real time data access, but BAM is
 not designed to be real time. I don't want the Agent API to be specific to
 Cassandra, either.

 There should be a clean way to do this. How did you decide to do it this
 way? Was there a discussion?

 Yes there was a discussion on this some time back on Architecture -RFC:
 Architecture for Stratos Log Processing  where we decided to push logs to
 bam event receiver through the publisher and view logs using hector api.


Initially we tried to use flume as the Stratos log collector/manager but we
stop flume evaluation because BAM's capability to cover the same use case.

There are several workarounds like create relevant keyspaces in the tenant
creation or create extended event receiver only for logging.

Thanks,

Deependra.


 On Fri, Jun 22, 2012 at 8:45 AM, Amani Soysa am...@wso2.com wrote:

 Hi,

 Currently we are sending LogEvent data through bam data publisher to bam
 event receiver using a custom log4j appender. And we retrieve logs using
 the hector API for the carbon log viewer. However, we need to have
 secondary indexes for several columns so that we can filter log information
 for a given column ( such as date, applicationName, priority,logger etc)
 when creating the data publisher (keyspace). From the current Bam Data
 publisher implementation we cannot do secondary indexing all we can do is
 define the column name and the data type of that column, and reciver
 creates the keyspaces for given columns with their data types.

  streamId = dataPublisher.defineEventStream({ + 
 'name':'org.wso2.carbon.logging.$tenantId.$serverName',
+   'version':'1.0.0', +   'nickName': 'Logs',
+   'description': 'Logging Event', + 
  'metaData':[
+{'name':'clientType','type':'STRING'} + 
  ],
+   'payloadData':[
+   {'name':'tenantID','type':'
 STRING'},
+   {'name':'serverName','type':'
 STRING'},
+   {'name':'appName','type':'STRING'},
+   {'name':'logTime','type':'LONG'},
+   {'name':'logger','type':'STRING'},
+   {'name':'priority','type':'STRING'}
 ,
+   {'name':'message','type':'STRING'},
+   {'name':'ip','type':'STRING'},
+   {'name':'stacktrace','type':'
 STRING'},
 +   {'name':'instance','type':'
 STRING'}
+   ]
+ });

 Is it possible to have a cassandra specific event receiver (for logging
 purposes) so that we can create key spaces with secondary 
 indexes?[1https://wso2.org/jira/browse/CARBON-13468]
 and it will create keyspaces when ever logs are published . Or do we need
 to create keyspaces at tenant creation time?. For a given tenant we need to
 create several keyspaces, depending on the server (and if possible for
 applications as well so we can have better performance when viewing logs).
 ie - keyspace1 - org_wso2_logging_tenant1_application_server (store AS
 specific logs)
  keyspace2 - org_wso2_logging_tenant1_data_services_server  (store
 DSS specific logs)

 Please note that we cannot use BAM analytics  to view logs because we
 need a real time log-viwer.

 [1] - https://wso2.org/jira/browse/CARBON-13468

 Regards,
 Amani




 --
 Regards,

 Tharindu

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





-- 
Deependra Ariyadewa
WSO2, Inc. http://wso2.com/ http://wso2.org

email d...@wso2.com; cell +94 71 403 5996 ;
Blog http://risenfall.wordpress.com/
PGP info: KeyID: 'DC627E6F'
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Active Directory support in the new release

2012-06-22 Thread Asela Pathberiya

On Fri, Jun 22, 2012 at 1:36 PM, Suresh Attanayaka sur...@wso2.com wrote:

 Hi all,

 Active Directory Read/Write support has been implemented in the trunk user
 core. This implementation supports both Active Directory Domain Services
 (AD DS) http://technet.microsoft.com/en-us/library/cc770946 and Active
 Directory Lightweight Directory Services (AD 
 LDS)http://technet.microsoft.com/en-us/library/cc731868server roles.


+1  Great..!!  It is better, If we can test the Carbon 4 with these user
store also.

Thanks,
Asela.



 Thanks,
 Suresh

 --
 Suresh Attanayake
 Software Engineer; WSO2 Inc. http://wso2.com/
 Blog : http://sureshatt.blogspot.com/
 Twitter : https://twitter.com/sureshatt
 LinkedIn : http://lk.linkedin.com/in/sureshatt
 Mobile : +94755012060,+94770419136,+94710467976


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


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

Re: [Dev] Active Directory support in the new release

2012-06-22 Thread Thilina Buddhika

Good Job Suresh..!

Please update the User Mgt documentation as well.

Thanks,
Thilina

On Fri, Jun 22, 2012 at 1:36 PM, Suresh Attanayaka sur...@wso2.com wrote:

 Hi all,

 Active Directory Read/Write support has been implemented in the trunk user
 core. This implementation supports both Active Directory Domain Services
 (AD DS) http://technet.microsoft.com/en-us/library/cc770946 and Active
 Directory Lightweight Directory Services (AD 
 LDS)http://technet.microsoft.com/en-us/library/cc731868server roles.

 Thanks,
 Suresh

 --
 Suresh Attanayake
 Software Engineer; WSO2 Inc. http://wso2.com/
 Blog : http://sureshatt.blogspot.com/
 Twitter : https://twitter.com/sureshatt
 LinkedIn : http://lk.linkedin.com/in/sureshatt
 Mobile : +94755012060,+94770419136,+94710467976


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




-- 
Thilina Buddhika
Associate Technical Lead
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

phone : +94 77 44 88 727
blog : http://blog.thilinamb.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build failure in BAM2

Hi,
I took an svn update, and started building everything last night. It is
getting a build failure as below, for BAM2.
Is this fixed already?

Installing org.wso2.carbon.identity.relying.party.feature.group
4.0.0.SNAPSHOT.
Installing org.wso2.carbon.identity.core.feature.group 4.0.0.SNAPSHOT.
Installation failed.
Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 Carbon - Cassandra Explorer Feature
4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.explorer.feature.group
4.0.0.SNAPSHOT)
 Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Cassandra Explorer Feature 4.0.0.SNAPSHOT
(org.wso2.carbon.cassandra.explorer.feature.group 4.0.0.SNAPSHOT)
  To: org.wso2.carbon.cassandra.explorer.server.feature.group
[4.0.0.SNAPSHOT]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Cassandra Explorer server Feature 4.0.0.SNAPSHOT
(org.wso2.carbon.cassandra.explorer.server.feature.group 4.0.0.SNAPSHOT)
  To: apache-cassandra [1.1.0.wso2v1]
Application failed, log file location:
/home/pradeeban/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1340346466974.log

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Business Activity Monitor  SUCCESS [1.893s]
[INFO] WSO2 Business Activity Monitor Styles Parent .. SUCCESS [0.014s]
[INFO] WSO2 BAM UI styles  SUCCESS [9.403s]
[INFO] WSO2 Business Activity Monitor Features Parent  SUCCESS [0.014s]
[INFO] WSO2 BAM - Features Aggregator Module . SUCCESS [0.010s]
[INFO] WSO2 BAM - Style Features . SUCCESS [2.097s]
[INFO] WSO2 Business Activity Monitor P2 Profile Generation  FAILURE
[32.847s]
[INFO] WSO2 Business Activity Monitor - Product .. SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 48.517s
[INFO] Finished at: Fri Jun 22 11:57:55 IST 2012
[INFO] Final Memory: 32M/334M
[INFO]

[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5-SNAPSHOT:p2-profile-gen
(3-p2-profile-generation) on project wso2bam-p2-profile-gen: P2 publisher
return code was 13 - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn goals -rf :wso2bam-p2-profile-gen


Regards,
Pradeeban.

-- 
Kathiravelu Pradeeban.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
M: +94 776 477 976
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting build failure in Integration test module

2012-06-22 Thread Krishantha Samaraweera

Removing  /.m2/repository/org/apache/maven/surefire/surefire-testng and
building online should solve the problem.

Thanks,
Krishantha.

On Fri, Jun 22, 2012 at 1:48 PM, Chamara Silva cham...@wso2.com wrote:

 @subject pls.


 [INFO]
 
 [INFO] Building WSO2 Carbon - Integration Tests 4.0.0-SNAPSHOT
 [INFO]
 
 [INFO]
 [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
 org.wso2.carbon.integration.tests ---
 [INFO] Deleting
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
 [INFO]
 [INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
 org.wso2.carbon.integration.tests ---
 [INFO] Verifying module descriptor ...
 [INFO] Pom descriptor modification detected.
 [INFO] Deleting
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
 [INFO]
 [INFO] --- maven-clean-plugin:2.4.1:clean (auto-clean) @
 org.wso2.carbon.integration.tests ---
 [INFO] Deleting
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
 [INFO]
 [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
 org.wso2.carbon.integration.tests ---
 [debug] execute contextualize
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/src/main/resources
 [INFO]
 [INFO] --- maven-antrun-plugin:1.3:run
 (org.wso2.carbon.integration.tests-include-sources) @
 org.wso2.carbon.integration.tests ---
 [INFO] Executing tasks
  [copy] Copying 2 files to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/test-classes
 [INFO] Executed tasks
 [INFO]
 [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
 org.wso2.carbon.integration.tests ---
 [INFO] No sources to compile
 [INFO]
 [INFO] --- maven-dependency-plugin:2.1:copy-dependencies (default) @
 org.wso2.carbon.integration.tests ---
 [INFO] Copying emma-2.1.5320.jar to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/emma/emma-2.1.5320.jar
 [INFO] Copying org.wso2.carbon.integration.framework-4.0.0-SNAPSHOT.jar to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/emma/org.wso2.carbon.integration.framework-4.0.0-SNAPSHOT.jar
 [INFO]
 [INFO] --- maven-dependency-plugin:2.1:copy-dependencies
 (copy-secVerifier) @ org.wso2.carbon.integration.tests ---
 [INFO] Copying SecVerifier.aar to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/security-verifier/SecVerifier.aar
 [INFO]
 [INFO] --- maven-resources-plugin:2.5:testResources
 (default-testResources) @ org.wso2.carbon.integration.tests ---
 [debug] execute contextualize
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] Copying 2 resources
 [INFO]
 [INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @
 org.wso2.carbon.integration.tests ---
 [INFO] Compiling 9 source files to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/test-classes
 [INFO]
 [INFO] --- maven-surefire-plugin:2.12:test (default-test) @
 org.wso2.carbon.integration.tests ---
 [INFO] Surefire report directory:
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/surefire-reports
 [WARNING] Invalid POM for
 org.apache.maven.surefire:surefire-testng:jar:2.12, transitive dependencies
 (if any) will not be available, enable debug logging for more details

 ---
  T E S T S
 ---
 org.apache.maven.surefire.util.SurefireReflectionException:
 java.lang.ClassNotFoundException:
 org.apache.maven.surefire.testng.TestNGProvider; nested exception is
 java.lang.ClassNotFoundException:
 org.apache.maven.surefire.testng.TestNGProvider
 java.lang.ClassNotFoundException:
 org.apache.maven.surefire.testng.TestNGProvider
 at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
  at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
  at
 org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:97)
 at
 org.apache.maven.surefire.util.ReflectionUtils.loadClass(ReflectionUtils.java:228)
  at
 org.apache.maven.surefire.util.ReflectionUtils.instantiateOneArg(ReflectionUtils.java:128)
 at
 org.apache.maven.surefire.booter.SurefireReflector.instantiateProvider(SurefireReflector.java:239)
  at
 org.apache.maven.surefire.booter.ProviderFactory.createProvider(ProviderFactory.java:122)
 at

Re: [Dev] How to do secondary indexing with bam-data-publisher for Stratos-Logging

2012-06-22 Thread Amani Soysa

On Fri, Jun 22, 2012 at 2:02 PM, Deependra Ariyadewa d...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 1:45 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 1:24 PM, Tharindu Mathew thari...@wso2.comwrote:

 This will be useful for folks who want real time data access, but BAM is
 not designed to be real time. I don't want the Agent API to be specific to
 Cassandra, either.

 There should be a clean way to do this. How did you decide to do it this
 way? Was there a discussion?

 Yes there was a discussion on this some time back on Architecture -RFC:
 Architecture for Stratos Log Processing  where we decided to push logs to
 bam event receiver through the publisher and view logs using hector api.


 Initially we tried to use flume as the Stratos log collector/manager but
 we stop flume evaluation because BAM's capability to cover the same use
 case.

  There are several workarounds like create relevant keyspaces in the
 tenant creation or create extended event receiver only for logging.

If we do it in the tenant creation time their will be around 10 keyspaces
per each tenant (given that for each server, we create a keyspace as I
explained earlier) So even a user doesn't use a particular server their
will be a keyspace for it. So if there are 1000 tenants there will be 10
000 keyspace (even if some keyspaces are not used at all) So I think its
better to create keyspaces when ever logs are publishing to that particular
keyspace.


 Thanks,

 Deependra.


 On Fri, Jun 22, 2012 at 8:45 AM, Amani Soysa am...@wso2.com wrote:

 Hi,

 Currently we are sending LogEvent data through bam data publisher to
 bam event receiver using a custom log4j appender. And we retrieve logs
 using the hector API for the carbon log viewer. However, we need to have
 secondary indexes for several columns so that we can filter log information
 for a given column ( such as date, applicationName, priority,logger etc)
 when creating the data publisher (keyspace). From the current Bam Data
 publisher implementation we cannot do secondary indexing all we can do is
 define the column name and the data type of that column, and reciver
 creates the keyspaces for given columns with their data types.

  streamId = dataPublisher.defineEventStream({ + 
 'name':'org.wso2.carbon.logging.$tenantId.$serverName',
+   'version':'1.0.0', +   'nickName':
 'Logs',
+   'description': 'Logging Event', + 
  'metaData':[
+{'name':'clientType','type':'STRING'} +
   ],
+   'payloadData':[
+   {'name':'tenantID','type':'
 STRING'},
+   {'name':'serverName','type':'
 STRING'},
+   {'name':'appName','type':'STRING'}
 ,
+   {'name':'logTime','type':'LONG'},
+   {'name':'logger','type':'STRING'},
+   {'name':'priority','type':'STRING'}
 ,
+   {'name':'message','type':'
 STRING'},
+   {'name':'ip','type':'STRING'},
+   {'name':'stacktrace','type':'
 STRING'},
 +   {'name':'instance','type':'
 STRING'}
+   ]
+ });

 Is it possible to have a cassandra specific event receiver (for logging
 purposes) so that we can create key spaces with secondary 
 indexes?[1https://wso2.org/jira/browse/CARBON-13468]
 and it will create keyspaces when ever logs are published . Or do we need
 to create keyspaces at tenant creation time?. For a given tenant we need to
 create several keyspaces, depending on the server (and if possible for
 applications as well so we can have better performance when viewing logs).
 ie - keyspace1 - org_wso2_logging_tenant1_application_server (store AS
 specific logs)
  keyspace2 - org_wso2_logging_tenant1_data_services_server  (store
 DSS specific logs)

 Please note that we cannot use BAM analytics  to view logs because we
 need a real time log-viwer.

 [1] - https://wso2.org/jira/browse/CARBON-13468

 Regards,
 Amani




 --
 Regards,

 Tharindu

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





 --
 Deependra Ariyadewa
 WSO2, Inc. http://wso2.com/ http://wso2.org

 email d...@wso2.com; cell +94 71 403 5996 ;
 Blog http://risenfall.wordpress.com/
 PGP info: KeyID: 'DC627E6F'


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

Re: [Dev] Build failure in BAM2

Hi Pradeeban,

 This is due to cassandra. Though you update the entire platform ,
Cassandra dependency is not getting build with it , since Cassandra build
is removed from build. So you will be able to get rid of this by building
cassandra dependency/orbit/component/feature manually.

Thanks
Shammi

On Fri, Jun 22, 2012 at 2:08 PM, Kathiravelu Pradeeban
pradee...@wso2.comwrote:

 Hi,
 I took an svn update, and started building everything last night. It is
 getting a build failure as below, for BAM2.
 Is this fixed already?

 Installing org.wso2.carbon.identity.relying.party.feature.group
 4.0.0.SNAPSHOT.
 Installing org.wso2.carbon.identity.core.feature.group 4.0.0.SNAPSHOT.
 Installation failed.
 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.explorer.feature.group
 4.0.0.SNAPSHOT)
  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.cassandra.explorer.server.feature.group
 [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer server Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.server.feature.group 4.0.0.SNAPSHOT)
   To: apache-cassandra [1.1.0.wso2v1]
 Application failed, log file location:
 /home/pradeeban/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1340346466974.log

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Business Activity Monitor  SUCCESS [1.893s]
 [INFO] WSO2 Business Activity Monitor Styles Parent .. SUCCESS [0.014s]
 [INFO] WSO2 BAM UI styles  SUCCESS [9.403s]
 [INFO] WSO2 Business Activity Monitor Features Parent  SUCCESS [0.014s]
 [INFO] WSO2 BAM - Features Aggregator Module . SUCCESS [0.010s]
 [INFO] WSO2 BAM - Style Features . SUCCESS [2.097s]
 [INFO] WSO2 Business Activity Monitor P2 Profile Generation  FAILURE
 [32.847s]
 [INFO] WSO2 Business Activity Monitor - Product .. SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 48.517s
 [INFO] Finished at: Fri Jun 22 11:57:55 IST 2012
 [INFO] Final Memory: 32M/334M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5-SNAPSHOT:p2-profile-gen
 (3-p2-profile-generation) on project wso2bam-p2-profile-gen: P2 publisher
 return code was 13 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :wso2bam-p2-profile-gen


 Regards,
 Pradeeban.

 --
 Kathiravelu Pradeeban.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976


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




-- 
Best Regards,*

Shammi Jayasinghe*
Senior Software Engineer; WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

2012-06-22 Thread Isuru Suriarachchi

Lakmali,

Can you please explain why we need this SuperTenantRolePlayer and why it
always returns false for isUltimateDestination()? Looks like, we can't
always return false here and have to figure out whether this is the
ultimate destination of the message. If the message is going into a tenant,
returning false is ok. But for the super tenant case, it should return
true. In any case, please look into this urgently and fix. This has
introduced a fundamental bug in addressing and RM.

Thanks,
~Isuru

On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.com wrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the way which was
 described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope
 
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line has
 the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

[Dev] [Bamboo-Build] WSO2 Carbon Products #251 Default Job has FAILED. Change made by 7 authors.


WSO2 Carbon  Products  #251  Default Job failed.

The build was triggered because the code has been changed.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-251/


--
Code Changes
--
senaka (130873):

Fixing typo.

isuruw (130864):

changing the userguide.html

madhuka (130865):

Fixed try it for AS and jaggery (path issue is fixed)



--
Error Summary
--
   Failed to prepare the build 'WSO2CARBON-PRODUCTS-JOB1-251'


--
This message is automatically generated by Atlassian Bamboo

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

Re: [Dev] How to do secondary indexing with bam-data-publisher for Stratos-Logging

This can be a useful feature for realtime requirements. But we need to
follow some proper convention as this changes the event stream definition
This is then an extensive change, and we are close to feature freezing.

On Fri, Jun 22, 2012 at 2:15 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 2:02 PM, Deependra Ariyadewa d...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 1:45 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 1:24 PM, Tharindu Mathew thari...@wso2.comwrote:

 This will be useful for folks who want real time data access, but BAM
 is not designed to be real time. I don't want the Agent API to be specific
 to Cassandra, either.

 There should be a clean way to do this. How did you decide to do it
 this way? Was there a discussion?

 Yes there was a discussion on this some time back on Architecture -RFC:
 Architecture for Stratos Log Processing  where we decided to push logs to
 bam event receiver through the publisher and view logs using hector api.


 Initially we tried to use flume as the Stratos log collector/manager but
 we stop flume evaluation because BAM's capability to cover the same use
 case.

  There are several workarounds like create relevant keyspaces in the
 tenant creation or create extended event receiver only for logging.

 If we do it in the tenant creation time their will be around 10 keyspaces
 per each tenant (given that for each server, we create a keyspace as I
 explained earlier) So even a user doesn't use a particular server their
 will be a keyspace for it. So if there are 1000 tenants there will be 10
 000 keyspace (even if some keyspaces are not used at all) So I think its
 better to create keyspaces when ever logs are publishing to that particular
 keyspace.

10 keryspaces per tenant?? Are you sure that's right...


 Thanks,

 Deependra.


 On Fri, Jun 22, 2012 at 8:45 AM, Amani Soysa am...@wso2.com wrote:

 Hi,

 Currently we are sending LogEvent data through bam data publisher to
 bam event receiver using a custom log4j appender. And we retrieve logs
 using the hector API for the carbon log viewer. However, we need to have
 secondary indexes for several columns so that we can filter log 
 information
 for a given column ( such as date, applicationName, priority,logger etc)
 when creating the data publisher (keyspace). From the current Bam Data
 publisher implementation we cannot do secondary indexing all we can do is
 define the column name and the data type of that column, and reciver
 creates the keyspaces for given columns with their data types.

  streamId = dataPublisher.defineEventStream({ + 
 'name':'org.wso2.carbon.logging.$tenantId.$serverName',
+   'version':'1.0.0', +   'nickName':
 'Logs',
+   'description': 'Logging Event', + 
  'metaData':[
+{'name':'clientType','type':'STRING'} +
   ],
+   'payloadData':[
+   {'name':'tenantID','type':'
 STRING'},
+   {'name':'serverName','type':'
 STRING'},
+   {'name':'appName','type':'STRING'}
 ,
+   {'name':'logTime','type':'LONG'},
+   {'name':'logger','type':'STRING'},
 
+   {'name':'priority','type':'
 STRING'},
+   {'name':'message','type':'
 STRING'},
+   {'name':'ip','type':'STRING'},
+   {'name':'stacktrace','type':'
 STRING'},
 +   {'name':'instance','type':'
 STRING'}
+   ]
+ });

 Is it possible to have a cassandra specific event receiver (for
 logging purposes) so that we can create key spaces with secondary 
 indexes?[
 1 https://wso2.org/jira/browse/CARBON-13468] and it will create
 keyspaces when ever logs are published . Or do we need to create keyspaces
 at tenant creation time?. For a given tenant we need to create several
 keyspaces, depending on the server (and if possible for applications as
 well so we can have better performance when viewing logs).
 ie - keyspace1 - org_wso2_logging_tenant1_application_server (store AS
 specific logs)
  keyspace2 - org_wso2_logging_tenant1_data_services_server  (store
 DSS specific logs)

 Please note that we cannot use BAM analytics  to view logs because we
 need a real time log-viwer.

 [1] - https://wso2.org/jira/browse/CARBON-13468

 Regards,
 Amani




 --
 Regards,

 Tharindu

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





 --
 Deependra Ariyadewa
 WSO2, Inc. http://wso2.com/ http://wso2.org

 email d...@wso2.com; cell +94 71 403 5996 ;
 Blog http://risenfall.wordpress.com/
 PGP info: KeyID: 'DC627E6F'





-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list

Re: [Dev] Getting build failure in Integration test module

2012-06-22 Thread Chamara Silva

Problem resolved. Thanks.

Regards,
Chamara Silva

On Fri, Jun 22, 2012 at 2:09 PM, Krishantha Samaraweera krishan...@wso2.com
 wrote:

 Removing  /.m2/repository/org/apache/maven/surefire/surefire-testng and
 building online should solve the problem.

 Thanks,
 Krishantha.

 On Fri, Jun 22, 2012 at 1:48 PM, Chamara Silva cham...@wso2.com wrote:

 @subject pls.


 [INFO]
 
 [INFO] Building WSO2 Carbon - Integration Tests 4.0.0-SNAPSHOT
 [INFO]
 
 [INFO]
 [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
 org.wso2.carbon.integration.tests ---
 [INFO] Deleting
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
 [INFO]
 [INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
 org.wso2.carbon.integration.tests ---
 [INFO] Verifying module descriptor ...
 [INFO] Pom descriptor modification detected.
 [INFO] Deleting
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
 [INFO]
 [INFO] --- maven-clean-plugin:2.4.1:clean (auto-clean) @
 org.wso2.carbon.integration.tests ---
 [INFO] Deleting
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target
 [INFO]
 [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
 org.wso2.carbon.integration.tests ---
 [debug] execute contextualize
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/src/main/resources
 [INFO]
 [INFO] --- maven-antrun-plugin:1.3:run
 (org.wso2.carbon.integration.tests-include-sources) @
 org.wso2.carbon.integration.tests ---
 [INFO] Executing tasks
  [copy] Copying 2 files to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/test-classes
 [INFO] Executed tasks
 [INFO]
 [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
 org.wso2.carbon.integration.tests ---
 [INFO] No sources to compile
 [INFO]
 [INFO] --- maven-dependency-plugin:2.1:copy-dependencies (default) @
 org.wso2.carbon.integration.tests ---
 [INFO] Copying emma-2.1.5320.jar to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/emma/emma-2.1.5320.jar
 [INFO] Copying org.wso2.carbon.integration.framework-4.0.0-SNAPSHOT.jar
 to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/emma/org.wso2.carbon.integration.framework-4.0.0-SNAPSHOT.jar
 [INFO]
 [INFO] --- maven-dependency-plugin:2.1:copy-dependencies
 (copy-secVerifier) @ org.wso2.carbon.integration.tests ---
 [INFO] Copying SecVerifier.aar to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/security-verifier/SecVerifier.aar
 [INFO]
 [INFO] --- maven-resources-plugin:2.5:testResources
 (default-testResources) @ org.wso2.carbon.integration.tests ---
 [debug] execute contextualize
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] Copying 2 resources
 [INFO]
 [INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile)
 @ org.wso2.carbon.integration.tests ---
 [INFO] Compiling 9 source files to
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/test-classes
 [INFO]
 [INFO] --- maven-surefire-plugin:2.12:test (default-test) @
 org.wso2.carbon.integration.tests ---
 [INFO] Surefire report directory:
 /home/chamara/wso2/project/CARBON/kernel/trunk/distribution/integration/tests/target/surefire-reports
 [WARNING] Invalid POM for
 org.apache.maven.surefire:surefire-testng:jar:2.12, transitive dependencies
 (if any) will not be available, enable debug logging for more details

 ---
  T E S T S
 ---
 org.apache.maven.surefire.util.SurefireReflectionException:
 java.lang.ClassNotFoundException:
 org.apache.maven.surefire.testng.TestNGProvider; nested exception is
 java.lang.ClassNotFoundException:
 org.apache.maven.surefire.testng.TestNGProvider
 java.lang.ClassNotFoundException:
 org.apache.maven.surefire.testng.TestNGProvider
 at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
  at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
  at
 org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:97)
 at
 org.apache.maven.surefire.util.ReflectionUtils.loadClass(ReflectionUtils.java:228)
  at
 org.apache.maven.surefire.util.ReflectionUtils.instantiateOneArg(ReflectionUtils.java:128)
 at
 org.apache.maven.surefire.booter.SurefireReflector.instantiateProvider(SurefireReflector.java:239)
  at

Re: [Dev] How to do secondary indexing with bam-data-publisher for Stratos-Logging

2012-06-22 Thread Amani Soysa

On Fri, Jun 22, 2012 at 2:29 PM, Tharindu Mathew thari...@wso2.com wrote:

 This can be a useful feature for realtime requirements. But we need to
 follow some proper convention as this changes the event stream definition
 This is then an extensive change, and we are close to feature freezing.

 On Fri, Jun 22, 2012 at 2:15 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 2:02 PM, Deependra Ariyadewa d...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 1:45 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 1:24 PM, Tharindu Mathew thari...@wso2.comwrote:

 This will be useful for folks who want real time data access, but BAM
 is not designed to be real time. I don't want the Agent API to be specific
 to Cassandra, either.

 There should be a clean way to do this. How did you decide to do it
 this way? Was there a discussion?

 Yes there was a discussion on this some time back on Architecture
 -RFC: Architecture for Stratos Log Processing  where we decided to push
 logs to bam event receiver through the publisher and view logs using hector
 api.


 Initially we tried to use flume as the Stratos log collector/manager but
 we stop flume evaluation because BAM's capability to cover the same use
 case.

  There are several workarounds like create relevant keyspaces in the
 tenant creation or create extended event receiver only for logging.

 If we do it in the tenant creation time their will be around 10 keyspaces
 per each tenant (given that for each server, we create a keyspace as I
 explained earlier) So even a user doesn't use a particular server their
 will be a keyspace for it. So if there are 1000 tenants there will be 10
 000 keyspace (even if some keyspaces are not used at all) So I think its
 better to create keyspaces when ever logs are publishing to that particular
 keyspace.

 10 keryspaces per tenant?? Are you sure that's right...

Yes for each sever (maybe more than 10 :) )
ie - data services,appserver,esb,mb,cep,bps,brs etc all the products we
offer for stratos deployment , because we store logs for each server in
different keyspace(if not we have to keep everything in a single keyspace
per tenant and it will be an expensive search when we filter the logs from
the server level because we give users server specific logs)
In our earlier syslog implementation we divided logs per each server for
fast result (as logs generates). Thats why its very important to not to
create keyspaces if users are not using a particular product.


 Thanks,

 Deependra.


 On Fri, Jun 22, 2012 at 8:45 AM, Amani Soysa am...@wso2.com wrote:

 Hi,

 Currently we are sending LogEvent data through bam data publisher to
 bam event receiver using a custom log4j appender. And we retrieve logs
 using the hector API for the carbon log viewer. However, we need to have
 secondary indexes for several columns so that we can filter log 
 information
 for a given column ( such as date, applicationName, priority,logger etc)
 when creating the data publisher (keyspace). From the current Bam Data
 publisher implementation we cannot do secondary indexing all we can do is
 define the column name and the data type of that column, and reciver
 creates the keyspaces for given columns with their data types.

  streamId = dataPublisher.defineEventStream({ + 
 'name':'org.wso2.carbon.logging.$tenantId.$serverName',
+   'version':'1.0.0', +   'nickName':
 'Logs',
+   'description': 'Logging Event', + 
  'metaData':[
+{'name':'clientType','type':'STRING'}
 +   ],
+   'payloadData':[
+   {'name':'tenantID','type':'
 STRING'},
+   {'name':'serverName','type':'
 STRING'},
+   {'name':'appName','type':'
 STRING'},
+   {'name':'logTime','type':'LONG'}
 ,
+   {'name':'logger','type':'
 STRING'},
+   {'name':'priority','type':'
 STRING'},
+   {'name':'message','type':'
 STRING'},
+   {'name':'ip','type':'STRING'},
+   {'name':'stacktrace','type':'
 STRING'},
 +   {'name':'instance','type':'
 STRING'}
+   ]
+ });

 Is it possible to have a cassandra specific event receiver (for
 logging purposes) so that we can create key spaces with secondary 
 indexes?[
 1 https://wso2.org/jira/browse/CARBON-13468] and it will create
 keyspaces when ever logs are published . Or do we need to create 
 keyspaces
 at tenant creation time?. For a given tenant we need to create several
 keyspaces, depending on the server (and if possible for applications as
 well so we can have better performance when viewing logs).
 ie - keyspace1 - org_wso2_logging_tenant1_application_server (store
 AS

Re: [Dev] Build failure in BAM2

Hi Shammi,
Thanks for the message. But these cassandra dependency/component/feature
are indeed not removed. There are still there. Hence the issue is something
else.

The builder has also failed this morning for the same reason, [Bamboo-Build]
WSO2 Carbon  Products  #248  Default Job has FAILED. I can see
discussions around this. So this is something else that should be fixed, I
guess.

Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 Carbon - Cassandra Explorer Feature
4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.
explorer.feature.group 4.0.0.SNAPSHOT)
 *Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
it could not be found
* Cannot satisfy dependency:


Thank you.
Regards,
Pradeeban.


On Fri, Jun 22, 2012 at 2:16 PM, Shammi Jayasinghe sha...@wso2.com wrote:

 Hi Pradeeban,

  This is due to cassandra. Though you update the entire platform ,
 Cassandra dependency is not getting build with it , since Cassandra build
 is removed from build. So you will be able to get rid of this by building
 cassandra dependency/orbit/component/feature manually.

 Thanks
 Shammi

 On Fri, Jun 22, 2012 at 2:08 PM, Kathiravelu Pradeeban pradee...@wso2.com
  wrote:

 Hi,
 I took an svn update, and started building everything last night. It is
 getting a build failure as below, for BAM2.
 Is this fixed already?

 Installing org.wso2.carbon.identity.relying.party.feature.group
 4.0.0.SNAPSHOT.
 Installing org.wso2.carbon.identity.core.feature.group 4.0.0.SNAPSHOT.
 Installation failed.
 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.explorer.feature.group
 4.0.0.SNAPSHOT)
  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.cassandra.explorer.server.feature.group
 [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer server Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.server.feature.group 4.0.0.SNAPSHOT)
   To: apache-cassandra [1.1.0.wso2v1]
 Application failed, log file location:
 /home/pradeeban/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1340346466974.log

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Business Activity Monitor  SUCCESS
 [1.893s]
 [INFO] WSO2 Business Activity Monitor Styles Parent .. SUCCESS
 [0.014s]
 [INFO] WSO2 BAM UI styles  SUCCESS
 [9.403s]
 [INFO] WSO2 Business Activity Monitor Features Parent  SUCCESS
 [0.014s]
 [INFO] WSO2 BAM - Features Aggregator Module . SUCCESS
 [0.010s]
 [INFO] WSO2 BAM - Style Features . SUCCESS
 [2.097s]
 [INFO] WSO2 Business Activity Monitor P2 Profile Generation  FAILURE
 [32.847s]
 [INFO] WSO2 Business Activity Monitor - Product .. SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 48.517s
 [INFO] Finished at: Fri Jun 22 11:57:55 IST 2012
 [INFO] Final Memory: 32M/334M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5-SNAPSHOT:p2-profile-gen
 (3-p2-profile-generation) on project wso2bam-p2-profile-gen: P2 publisher
 return code was 13 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :wso2bam-p2-profile-gen


 Regards,
 Pradeeban.

 --
 Kathiravelu Pradeeban.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976


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




 --
 Best Regards,*

 Shammi Jayasinghe*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com,
 mobile: +94 71 4493085





-- 
Kathiravelu Pradeeban.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna]

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

2012-06-22 Thread Lakmali Baminiwatta

Hi,

On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.com wrote:

 Lakmali,

 Can you please explain why we need this SuperTenantRolePlayer and why it
 always returns false for isUltimateDestination()? Looks like, we can't
 always return false here and have to figure out whether this is the
 ultimate destination of the message. If the message is going into a tenant,
 returning false is ok. But for the super tenant case, it should return
 true. In any case, please look into this urgently and fix. This has
 introduced a fundamental bug in addressing and RM.


We need to set the SuperTenantRolePlayer to invoke secure services by
tenants. This was actually had been a module inside products previously
(ex: AS org.wso2.stratos.appserver.deployment) and I just made it common by
adding it as a stratos component. This was done as a fix for the issue [1].

Previously this was only added to the services. Now after product-service
merging this SuperTenantRolePlayer might be an issue to the products. Will
look in this.

[1] 
https://wso2.org/jira/browse/STRATOS-1953https://wso2.org/jira/browse/STRATOS-1953

Thanks,
Lakmali



 Thanks,
 ~Isuru

 On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.com wrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the
 way which was described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope
 
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line
 has the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] WSO2 Carbon platform #393 has FAILED. Change made by 7 authors.

Hi Greg Team ,

 Build is failed due to the following reason. Have you done a recent change
in directory structure.

Note: Build is not checking out source for each and every build and it does
svn up


Thanks
Shammi

error   22-Jun-2012 01:20:20java.lang.RuntimeException:
com.atlassian.bamboo.repository.RepositoryException: Unable to
retrieve source code for revision '130873', plan
'WSO2CARBON-PLATFORM-JOB1': svn: URL
'https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.services.ui/src/main/resources/web/services/docs'
of existing directory
'components/governance/org.wso2.carbon.governance.generic.ui/src/main/resources/web/generic/docs'
does not match expected URL
'https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.generic.ui/src/main/resources/web/generic/docs'
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:119)
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.executor.RetryingTaskExecutor.runTask(RetryingTaskExecutor.java:79)
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:174)
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.execute(VcsCheckoutTask.java:101)
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:183)
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.task.TaskExecutorImpl.executePreparationTasks(TaskExecutorImpl.java:67)
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.build.pipeline.tasks.PrepareBuildTask.call(PrepareBuildTask.java:67)
error   22-Jun-2012 01:20:20at
sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source)
error   22-Jun-2012 01:20:20at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
error   22-Jun-2012 01:20:20at 
java.lang.reflect.Method.invoke(Method.java:597)
error   22-Jun-2012 01:20:20at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
error   22-Jun-2012 01:20:20at
org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:117)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
error   22-Jun-2012 01:20:20at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
error   22-Jun-2012 01:20:20at $Proxy541.call(Unknown Source)
error   22-Jun-2012 01:20:20at
sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source)
error   22-Jun-2012 01:20:20at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
error   22-Jun-2012 01:20:20at 
java.lang.reflect.Method.invoke(Method.java:597)
error   22-Jun-2012 01:20:20at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
error   22-Jun-2012 01:20:20at
org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:117)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
error   22-Jun-2012 01:20:20at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
error   22-Jun-2012 01:20:20at $Proxy542.call(Unknown Source)
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:204)
error   22-Jun-2012 01:20:20at
com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:103)
error   22-Jun-2012 01:20:20at

[Dev] xml files under platform/products/as/modules/distribution/target by the maven PMD plugin.

Hi,
There are a few .xml's created as above, while building the product, are
used by the Maven PMD pluginhttp://maven.apache.org/plugins/maven-pmd-plugin/
.

basic.xml
cpd.xml
imports.xml
pmd.xml
unusedcode.xml

I was just wondering what are they, and found out this.
Just sharing.

Thank you.
Regards,
Pradeeban.

-- 
Kathiravelu Pradeeban.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
M: +94 776 477 976
?xml version=1.0?

ruleset name=Unused Code Rules
xmlns=http://pmd.sf.net/ruleset/1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://pmd.sf.net/ruleset/1.0.0 http://pmd.sf.net/ruleset_xml_schema.xsd;
xsi:noNamespaceSchemaLocation=http://pmd.sf.net/ruleset_xml_schema.xsd;
  description
The Unused Code Ruleset contains a collection of rules that find unused code.
  /description

  rule name=UnusedPrivateField
  		  since=0.1
message=Avoid unused private fields such as ''{0}''.
class=net.sourceforge.pmd.rules.UnusedPrivateFieldRule
externalInfoUrl=http://pmd.sourceforge.net/rules/unusedcode.html#UnusedPrivateField;
description
Detects when a private field is declared and/or assigned a value, but not used.
/description
  priority3/priority
example
![CDATA[
public class Something {
  private static int FOO = 2; // Unused
  private int i = 5; // Unused
  private int j = 6;
  public int addOne() {
return j++;
  }
}
]]
/example
  /rule

rule name=UnusedLocalVariable
		  since=0.1
message=Avoid unused local variables such as ''{0}''.
class=net.sourceforge.pmd.rules.UnusedLocalVariableRule
externalInfoUrl=http://pmd.sourceforge.net/rules/unusedcode.html#UnusedLocalVariable;
description
Detects when a local variable is declared and/or assigned, but not used.
/description
priority3/priority

example
![CDATA[
public class Foo {
 public void doSomething() {
  int i = 5; // Unused
 }
}
]]
/example
  /rule

rule name=UnusedPrivateMethod
	  since=0.7
message=Avoid unused private methods such as ''{0}''.
class=net.sourceforge.pmd.rules.UnusedPrivateMethodRule
externalInfoUrl=http://pmd.sourceforge.net/rules/unusedcode.html#UnusedPrivateMethod;
description
Unused Private Method detects when a private method is declared but is unused.
/description
priority3/priority
example
![CDATA[
public class Something {
 private void foo() {} // unused
}
]]
/example
  /rule


  rule name=UnusedFormalParameter
  		  since=0.8
message=Avoid unused {0} parameters such as ''{1}''.
class=net.sourceforge.pmd.rules.UnusedFormalParameterRule
externalInfoUrl=http://pmd.sourceforge.net/rules/unusedcode.html#UnusedFormalParameter;
description
Avoid passing parameters to methods or constructors and then not using those parameters.
/description
  priority3/priority

example
![CDATA[
public class Foo {
 private void bar(String howdy) {
  // howdy is not used
 }
]]
/example
  /rule

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

[Dev] Can not activate instance of component org.wso2.carbon.ntask.core.internal.TasksDSComponent.

2012-06-22 Thread Dilshan Edirisuriya

Hi,

When adding ntask feature to Jaggery it doesnt get activated due to missing
dependency of slf4j.


=
osgi ls -c 149
Components in bundle org.wso2.carbon.ntask.core:
ID  Component details
28  Component[
name = tasks.component
factory = null
autoenable = true
immediate = true
implementation =
org.wso2.carbon.ntask.core.internal.TasksDSComponent
state = Unsatisfied
properties = {service.pid=tasks.component}
serviceFactory = false
serviceInterface = null
references = {
Reference[name = registry.service, interface =
org.wso2.carbon.registry.core.service.RegistryService, policy = dynamic,
cardinality = 1..1, target = null, bind = setRegistryS
ervice, unbind = unsetRegistryService]
Reference[name = coordination.service, interface =
org.wso2.carbon.coordination.core.services.CoordinationService, policy =
dynamic, cardinality = 1..1, target = null, bind =
 setCoordinationService, unbind = unsetCoordinationService]
Reference[name = user.realmservice.default, interface =
org.wso2.carbon.user.core.service.RealmService, policy = dynamic,
cardinality = 1..1, target = null, bind = setRealmSe
rvice, unbind = unsetRealmService]
Reference[name = config.context.service, interface =
org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
cardinality = 1..1, target = null, bind = setConfigu
rationContextService, unbind = unsetConfigurationContextService]
}
located in bundle = org.wso2.carbon.ntask.core_4.0.0.SNAPSHOT [149]
]
Dynamic information :
  The component is satisfied
  All component references are satisfied
  Component configurations :
Configuration properties:
  service.pid = tasks.component
  component.name = tasks.component
  component.id = 40
Instances:
No instances were created because: Can not activate instance of
component org.wso2.carbon.ntask.core.internal.TasksDSComponent. The
activation throws: java.lang.NoClassDefFoundError: org
/slf4j/LoggerFactory


=

osgi bundle 149
org.wso2.carbon.ntask.core_4.0.0.SNAPSHOT [149]
  Id=149, Status=ACTIVE  Data
Root=E:\svn\platform\trunk\products\jaggery\modules\distribution\target\jaggery-0.9.0-ALPHA\carbon\repository\components\configuration\org.eclipse.osgi\bund
les\149\data
  No registered services.
  No services in use.
  Exported packages
org.wso2.carbon.ntask.core.internal; version=0.0.0[exported]
org.wso2.carbon.ntask.core; version=0.0.0[exported]
org.wso2.carbon.ntask.core.service; version=0.0.0[exported]
org.wso2.carbon.ntask.core.impl; version=0.0.0[exported]
org.wso2.carbon.ntask.core.service.impl; version=0.0.0[exported]
  Imported packages
org.quartz; version=2.1.1quartz_2.1.1.wso2v1 [184]
org.quartz.impl; version=2.1.1quartz_2.1.1.wso2v1 [184]
org.quartz.impl.matchers; version=2.1.1quartz_2.1.1.wso2v1 [184]
org.apache.commons.logging;
version=1.1.1org.wso2.carbon.logging_4.0.0.SNAPSHOT [143]
org.osgi.service.component;
version=1.1.0org.eclipse.osgi.services_3.3.0.v20110513 [99]
org.wso2.carbon.user.core.service;
version=4.0.0.SNAPSHOTorg.wso2.carbon.user.core_4.0.0.SNAPSHOT [172]
org.wso2.carbon.registry.core.service;
version=1.0.1org.wso2.carbon.registry.core_4.0.0.SNAPSHOT [154]
org.wso2.carbon.coordination.core.services;
version=0.0.0org.wso2.carbon.coordination.core_4.0.0.SNAPSHOT [112]
org.wso2.carbon.utils;
version=4.0.0.SNAPSHOTorg.wso2.carbon.utils_4.0.0.SNAPSHOT [177]
  No fragment bundles
  Named class space
org.wso2.carbon.ntask.core; bundle-version=4.0.0.SNAPSHOT[provided]
  No required bundles

=


Regards,

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

Re: [Dev] [Bamboo-Build] WSO2 Carbon platform #393 has FAILED. Change made by 7 authors.

2012-06-22 Thread Isuru Wimalasundera

Hi Shammi

Yes we have removed some svn externals related to docs
in org.wso2.carbon.governance.generic.ui and to overcome this you may have
to remove src/main/resources/web/generic locally from the bamboo and svn up
again. Similarly this has been done for org.wso2.carbon.governance.wsdl.ui
, org.wso2.carbon.governance.schema.ui
and org.wso2.carbon.governance.policy.ui as well. Therefor you have to
remove the folder inside src/main/resources/web/ in these components as
well.

Thanks
Isuruw

On Fri, Jun 22, 2012 at 2:42 PM, Shammi Jayasinghe sha...@wso2.com wrote:

 Hi Greg Team ,

  Build is failed due to the following reason. Have you done a recent
 change in directory structure.

 Note: Build is not checking out source for each and every build and it
 does svn up


 Thanks
 Shammi

 error 22-Jun-2012 01:20:20java.lang.RuntimeException: 
 com.atlassian.bamboo.repository.RepositoryException: Unable to retrieve 
 source code for revision '130873', plan 'WSO2CARBON-PLATFORM-JOB1': svn: URL 
 'https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.services.ui/src/main/resources/web/services/docs'
  of existing directory 
 'components/governance/org.wso2.carbon.governance.generic.ui/src/main/resources/web/generic/docs'
  does not match expected URL 
 'https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.generic.ui/src/main/resources/web/generic/docs'
 error 22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:119)
 error 22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.executor.RetryingTaskExecutor.runTask(RetryingTaskExecutor.java:79)
 error 22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:174)
 error 22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.execute(VcsCheckoutTask.java:101)
 error 22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:183)
 error 22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.task.TaskExecutorImpl.executePreparationTasks(TaskExecutorImpl.java:67)
 error 22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.build.pipeline.tasks.PrepareBuildTask.call(PrepareBuildTask.java:67)
 error 22-Jun-2012 01:20:20at 
 sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source)
 error 22-Jun-2012 01:20:20at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 error 22-Jun-2012 01:20:20at 
 java.lang.reflect.Method.invoke(Method.java:597)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
 error 22-Jun-2012 01:20:20at 
 org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:117)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 error 22-Jun-2012 01:20:20at $Proxy541.call(Unknown Source)
 error 22-Jun-2012 01:20:20at 
 sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source)
 error 22-Jun-2012 01:20:20at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 error 22-Jun-2012 01:20:20at 
 java.lang.reflect.Method.invoke(Method.java:597)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
 error 22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
 error 22-Jun-2012 01:20:20at 
 org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:117)
 error 22-Jun-2012 01:20:20at

Re: [Dev] [Bamboo-Build] WSO2 Carbon platform #393 has FAILED. Change made by 7 authors.

Thanks isuru for information, Will configure bamboo to clean source for
every build  until it gets stable.

Thanks
Shammi

On Fri, Jun 22, 2012 at 2:52 PM, Isuru Wimalasundera isu...@wso2.comwrote:

 Hi Shammi

 Yes we have removed some svn externals related to docs
 in org.wso2.carbon.governance.generic.ui and to overcome this you may have
 to remove src/main/resources/web/generic locally from the bamboo and svn up
 again. Similarly this has been done for org.wso2.carbon.governance.wsdl.ui
 , org.wso2.carbon.governance.schema.ui
 and org.wso2.carbon.governance.policy.ui as well. Therefor you have to
 remove the folder inside src/main/resources/web/ in these components as
 well.

 Thanks
 Isuruw

 On Fri, Jun 22, 2012 at 2:42 PM, Shammi Jayasinghe sha...@wso2.comwrote:

 Hi Greg Team ,

  Build is failed due to the following reason. Have you done a recent
 change in directory structure.

 Note: Build is not checking out source for each and every build and it
 does svn up


 Thanks
 Shammi

 error22-Jun-2012 01:20:20java.lang.RuntimeException: 
 com.atlassian.bamboo.repository.RepositoryException: Unable to retrieve 
 source code for revision '130873', plan 'WSO2CARBON-PLATFORM-JOB1': svn: URL 
 'https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.services.ui/src/main/resources/web/services/docs'
  of existing directory 
 'components/governance/org.wso2.carbon.governance.generic.ui/src/main/resources/web/generic/docs'
  does not match expected URL 
 'https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.generic.ui/src/main/resources/web/generic/docs'
 error22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:119)
 error22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.executor.RetryingTaskExecutor.runTask(RetryingTaskExecutor.java:79)
 error22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:174)
 error22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.execute(VcsCheckoutTask.java:101)
 error22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:183)
 error22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.task.TaskExecutorImpl.executePreparationTasks(TaskExecutorImpl.java:67)
 error22-Jun-2012 01:20:20at 
 com.atlassian.bamboo.build.pipeline.tasks.PrepareBuildTask.call(PrepareBuildTask.java:67)
 error22-Jun-2012 01:20:20at 
 sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source)
 error22-Jun-2012 01:20:20at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 error22-Jun-2012 01:20:20at 
 java.lang.reflect.Method.invoke(Method.java:597)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
 error22-Jun-2012 01:20:20at 
 org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:117)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 error22-Jun-2012 01:20:20at $Proxy541.call(Unknown 
 Source)
 error22-Jun-2012 01:20:20at 
 sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source)
 error22-Jun-2012 01:20:20at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 error22-Jun-2012 01:20:20at 
 java.lang.reflect.Method.invoke(Method.java:597)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
 error22-Jun-2012 01:20:20at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
 error

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

2012-06-22 Thread Isuru Suriarachchi

On Fri, Jun 22, 2012 at 2:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi,

 On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Lakmali,

 Can you please explain why we need this SuperTenantRolePlayer and why it
 always returns false for isUltimateDestination()? Looks like, we can't
 always return false here and have to figure out whether this is the
 ultimate destination of the message. If the message is going into a tenant,
 returning false is ok. But for the super tenant case, it should return
 true. In any case, please look into this urgently and fix. This has
 introduced a fundamental bug in addressing and RM.


 We need to set the SuperTenantRolePlayer to invoke secure services by
 tenants. This was actually had been a module inside products previously
 (ex: AS org.wso2.stratos.appserver.deployment) and I just made it common by
 adding it as a stratos component. This was done as a fix for the issue [1].

 Previously this was only added to the services. Now after product-service
 merging this SuperTenantRolePlayer might be an issue to the products.


Yes, correct..


 Will look in this.


You can fix this either by not registering the Role Player for super tenant
or by writing the logic inside that method to determine whether it is
called by the super tenant or not.

Thanks,
~Isuru



 [1] 
 https://wso2.org/jira/browse/STRATOS-1953https://wso2.org/jira/browse/STRATOS-1953

 Thanks,
 Lakmali



 Thanks,
 ~Isuru

 On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.comwrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the
 way which was described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope
 
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line
 has the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Lakmali Baminiwatta*
 *
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 mobile:  +94 71 2335936
 *
 *




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

Re: [Dev] Build failure in BAM2

Yes, in platform/dependencies, orbit/cassandra was commented out.
!--moduleorbit/cassandra/module--

So have to build platform/dependencies/orbit/cassandra manually as
suggested by Shammi and then the features/cassandra.

Regards,
Pradeeban.

On Fri, Jun 22, 2012 at 2:39 PM, Kathiravelu Pradeeban
pradee...@wso2.comwrote:

 Hi Shammi,
 Thanks for the message. But these cassandra dependency/component/feature
 are indeed not removed. There are still there. Hence the issue is something
 else.

 The builder has also failed this morning for the same reason, [Bamboo-Build]
 WSO2 Carbon  Products  #248  Default Job has FAILED. I can see
 discussions around this. So this is something else that should be fixed, I
 guess.

 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.
 explorer.feature.group 4.0.0.SNAPSHOT)
  *Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
 * Cannot satisfy dependency:


 Thank you.
 Regards,
 Pradeeban.



 On Fri, Jun 22, 2012 at 2:16 PM, Shammi Jayasinghe sha...@wso2.comwrote:

 Hi Pradeeban,

  This is due to cassandra. Though you update the entire platform ,
 Cassandra dependency is not getting build with it , since Cassandra build
 is removed from build. So you will be able to get rid of this by building
 cassandra dependency/orbit/component/feature manually.

 Thanks
 Shammi

 On Fri, Jun 22, 2012 at 2:08 PM, Kathiravelu Pradeeban 
 pradee...@wso2.com wrote:

 Hi,
 I took an svn update, and started building everything last night. It is
 getting a build failure as below, for BAM2.
 Is this fixed already?

 Installing org.wso2.carbon.identity.relying.party.feature.group
 4.0.0.SNAPSHOT.
 Installing org.wso2.carbon.identity.core.feature.group 4.0.0.SNAPSHOT.
 Installation failed.
 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.explorer.feature.group
 4.0.0.SNAPSHOT)
  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.cassandra.explorer.server.feature.group
 [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer server Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.server.feature.group 4.0.0.SNAPSHOT)
   To: apache-cassandra [1.1.0.wso2v1]
 Application failed, log file location:
 /home/pradeeban/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1340346466974.log

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Business Activity Monitor  SUCCESS
 [1.893s]
 [INFO] WSO2 Business Activity Monitor Styles Parent .. SUCCESS
 [0.014s]
 [INFO] WSO2 BAM UI styles  SUCCESS
 [9.403s]
 [INFO] WSO2 Business Activity Monitor Features Parent  SUCCESS
 [0.014s]
 [INFO] WSO2 BAM - Features Aggregator Module . SUCCESS
 [0.010s]
 [INFO] WSO2 BAM - Style Features . SUCCESS
 [2.097s]
 [INFO] WSO2 Business Activity Monitor P2 Profile Generation  FAILURE
 [32.847s]
 [INFO] WSO2 Business Activity Monitor - Product .. SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 48.517s
 [INFO] Finished at: Fri Jun 22 11:57:55 IST 2012
 [INFO] Final Memory: 32M/334M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5-SNAPSHOT:p2-profile-gen
 (3-p2-profile-generation) on project wso2bam-p2-profile-gen: P2 publisher
 return code was 13 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :wso2bam-p2-profile-gen


 Regards,
 Pradeeban.

 --
 Kathiravelu Pradeeban.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M:

Re: [Dev] Build failure in BAM2

Hi Pradeeban,

On Fri, Jun 22, 2012 at 2:39 PM, Kathiravelu Pradeeban
pradee...@wso2.comwrote:

 Hi Shammi,
 Thanks for the message. But these cassandra dependency/component/feature
 are indeed not removed. There are still there. Hence the issue is something
 else.


Have you built dependencies/orbit/cassandra ?


The builder has also failed this morning for the same reason, [Bamboo-Build]
 WSO2 Carbon  Products  #248  Default Job has FAILED.


Deep has uploaded the new jars.


 I can see discussions around this. So this is something else that should
 be fixed, I guess.

 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.
 explorer.feature.group 4.0.0.SNAPSHOT)
  *Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
 * Cannot satisfy dependency:


 Thank you.
 Regards,
 Pradeeban.



 On Fri, Jun 22, 2012 at 2:16 PM, Shammi Jayasinghe sha...@wso2.comwrote:

 Hi Pradeeban,

  This is due to cassandra. Though you update the entire platform ,
 Cassandra dependency is not getting build with it , since Cassandra build
 is removed from build. So you will be able to get rid of this by building
 cassandra dependency/orbit/component/feature manually.

 Thanks
 Shammi

 On Fri, Jun 22, 2012 at 2:08 PM, Kathiravelu Pradeeban 
 pradee...@wso2.com wrote:

 Hi,
 I took an svn update, and started building everything last night. It is
 getting a build failure as below, for BAM2.
 Is this fixed already?

 Installing org.wso2.carbon.identity.relying.party.feature.group
 4.0.0.SNAPSHOT.
 Installing org.wso2.carbon.identity.core.feature.group 4.0.0.SNAPSHOT.
 Installation failed.
 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.explorer.feature.group
 4.0.0.SNAPSHOT)
  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.cassandra.explorer.server.feature.group
 [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer server Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.server.feature.group 4.0.0.SNAPSHOT)
   To: apache-cassandra [1.1.0.wso2v1]
 Application failed, log file location:
 /home/pradeeban/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1340346466974.log

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Business Activity Monitor  SUCCESS
 [1.893s]
 [INFO] WSO2 Business Activity Monitor Styles Parent .. SUCCESS
 [0.014s]
 [INFO] WSO2 BAM UI styles  SUCCESS
 [9.403s]
 [INFO] WSO2 Business Activity Monitor Features Parent  SUCCESS
 [0.014s]
 [INFO] WSO2 BAM - Features Aggregator Module . SUCCESS
 [0.010s]
 [INFO] WSO2 BAM - Style Features . SUCCESS
 [2.097s]
 [INFO] WSO2 Business Activity Monitor P2 Profile Generation  FAILURE
 [32.847s]
 [INFO] WSO2 Business Activity Monitor - Product .. SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 48.517s
 [INFO] Finished at: Fri Jun 22 11:57:55 IST 2012
 [INFO] Final Memory: 32M/334M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5-SNAPSHOT:p2-profile-gen
 (3-p2-profile-generation) on project wso2bam-p2-profile-gen: P2 publisher
 return code was 13 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :wso2bam-p2-profile-gen


 Regards,
 Pradeeban.

 --
 Kathiravelu Pradeeban.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976


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




 --
 Best

[Dev] Enabling trace logs in carbon trunk?

Hi,

I have some trace logs in my component.

But setting the necessary package to trace level does not seem to print it
to the console. Nor, does it append it to the trace log file. When I turn
it to trace I can see *debug* logs from the component. So, something should
be stopping trace logs.

What could be the reason for this?

-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

2012-06-22 Thread Lakmali Baminiwatta

Hi Isuru,


On Fri, Jun 22, 2012 at 2:58 PM, Isuru Suriarachchi is...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 2:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi,

 On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Lakmali,

 Can you please explain why we need this SuperTenantRolePlayer and why it
 always returns false for isUltimateDestination()? Looks like, we can't
 always return false here and have to figure out whether this is the
 ultimate destination of the message. If the message is going into a tenant,
 returning false is ok. But for the super tenant case, it should return
 true. In any case, please look into this urgently and fix. This has
 introduced a fundamental bug in addressing and RM.


 We need to set the SuperTenantRolePlayer to invoke secure services by
 tenants. This was actually had been a module inside products previously
 (ex: AS org.wso2.stratos.appserver.deployment) and I just made it common by
 adding it as a stratos component. This was done as a fix for the issue [1].

 Previously this was only added to the services. Now after product-service
 merging this SuperTenantRolePlayer might be an issue to the products.


 Yes, correct..


 Will look in this.


 You can fix this either by not registering the Role Player for super
 tenant or by writing the logic inside that method to determine whether it
 is called by the super tenant or not.


Thanks for the suggestions. If we don't register the Role Player for super
tenant, stratos secure services will fail in its super tenant flow while
trying to process must understand fields for security headers. Because the
rampart is engaged for services, only in sub tenants flow.

So I think we have to take the second approach.

Thanks,
Lakmali


 Thanks,
 ~Isuru



 [1] 
 https://wso2.org/jira/browse/STRATOS-1953https://wso2.org/jira/browse/STRATOS-1953

 Thanks,
 Lakmali



 Thanks,
 ~Isuru

 On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.comwrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the
 way which was described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=
 http://www.w3.org/2003/05/soap-envelope;
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line
 has the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Lakmali Baminiwatta*
 *
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 mobile:  +94 71 2335936
 *
 *




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in BAM2

On Fri, Jun 22, 2012 at 3:05 PM, Nirmal Fernando nir...@wso2.com wrote:

 Hi Pradeeban,

 On Fri, Jun 22, 2012 at 2:39 PM, Kathiravelu Pradeeban pradee...@wso2.com
  wrote:

 Hi Shammi,
 Thanks for the message. But these cassandra dependency/component/feature
 are indeed not removed. There are still there. Hence the issue is something
 else.


 Have you built dependencies/orbit/cassandra ?


Yes, as indicated in my second mail, I have built it, and that fixed the
build issue of BAM.



 The builder has also failed this morning for the same reason, [Bamboo-Build]
 WSO2 Carbon  Products  #248  Default Job has FAILED.


 Deep has uploaded the new jars.


Great.

Regards,
Pradeeban.




 I can see discussions around this. So this is something else that should
 be fixed, I guess.

 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.
 explorer.feature.group 4.0.0.SNAPSHOT)
  *Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
 * Cannot satisfy dependency:


 Thank you.
 Regards,
 Pradeeban.



 On Fri, Jun 22, 2012 at 2:16 PM, Shammi Jayasinghe sha...@wso2.comwrote:

 Hi Pradeeban,

  This is due to cassandra. Though you update the entire platform ,
 Cassandra dependency is not getting build with it , since Cassandra build
 is removed from build. So you will be able to get rid of this by building
 cassandra dependency/orbit/component/feature manually.

 Thanks
 Shammi

 On Fri, Jun 22, 2012 at 2:08 PM, Kathiravelu Pradeeban 
 pradee...@wso2.com wrote:

 Hi,
 I took an svn update, and started building everything last night. It is
 getting a build failure as below, for BAM2.
 Is this fixed already?

 Installing org.wso2.carbon.identity.relying.party.feature.group
 4.0.0.SNAPSHOT.
 Installing org.wso2.carbon.identity.core.feature.group 4.0.0.SNAPSHOT.
 Installation failed.
 Cannot complete the install because one or more required items could
 not be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.explorer.feature.group
 4.0.0.SNAPSHOT)
  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.cassandra.explorer.server.feature.group
 [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer server Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.server.feature.group 4.0.0.SNAPSHOT)
   To: apache-cassandra [1.1.0.wso2v1]
 Application failed, log file location:
 /home/pradeeban/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1340346466974.log

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Business Activity Monitor  SUCCESS
 [1.893s]
 [INFO] WSO2 Business Activity Monitor Styles Parent .. SUCCESS
 [0.014s]
 [INFO] WSO2 BAM UI styles  SUCCESS
 [9.403s]
 [INFO] WSO2 Business Activity Monitor Features Parent  SUCCESS
 [0.014s]
 [INFO] WSO2 BAM - Features Aggregator Module . SUCCESS
 [0.010s]
 [INFO] WSO2 BAM - Style Features . SUCCESS
 [2.097s]
 [INFO] WSO2 Business Activity Monitor P2 Profile Generation  FAILURE
 [32.847s]
 [INFO] WSO2 Business Activity Monitor - Product .. SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 48.517s
 [INFO] Finished at: Fri Jun 22 11:57:55 IST 2012
 [INFO] Final Memory: 32M/334M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5-SNAPSHOT:p2-profile-gen
 (3-p2-profile-generation) on project wso2bam-p2-profile-gen: P2 publisher
 return code was 13 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with
 the command
 [ERROR]   mvn goals -rf :wso2bam-p2-profile-gen


 Regards,
 Pradeeban.

 --
 Kathiravelu Pradeeban.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog:

Re: [Dev] Build failure in BAM2

On Fri, Jun 22, 2012 at 3:15 PM, Kathiravelu Pradeeban
pradee...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 3:05 PM, Nirmal Fernando nir...@wso2.com wrote:

 Hi Pradeeban,

 On Fri, Jun 22, 2012 at 2:39 PM, Kathiravelu Pradeeban 
 pradee...@wso2.com wrote:

 Hi Shammi,
 Thanks for the message. But these cassandra dependency/component/feature
 are indeed not removed. There are still there. Hence the issue is something
 else.


 Have you built dependencies/orbit/cassandra ?


 Yes, as indicated in my second mail, I have built it, and that fixed the
 build issue of BAM.


Awesome :-)




 The builder has also failed this morning for the same reason, [Bamboo-Build]
 WSO2 Carbon  Products  #248  Default Job has FAILED.


 Deep has uploaded the new jars.


 Great.

 Regards,
 Pradeeban.




 I can see discussions around this. So this is something else that should
 be fixed, I guess.

 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.
 explorer.feature.group 4.0.0.SNAPSHOT)
  *Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' but
 it could not be found
 * Cannot satisfy dependency:


 Thank you.
 Regards,
 Pradeeban.



 On Fri, Jun 22, 2012 at 2:16 PM, Shammi Jayasinghe sha...@wso2.comwrote:

 Hi Pradeeban,

  This is due to cassandra. Though you update the entire platform ,
 Cassandra dependency is not getting build with it , since Cassandra build
 is removed from build. So you will be able to get rid of this by building
 cassandra dependency/orbit/component/feature manually.

 Thanks
 Shammi

 On Fri, Jun 22, 2012 at 2:08 PM, Kathiravelu Pradeeban 
 pradee...@wso2.com wrote:

 Hi,
 I took an svn update, and started building everything last night. It
 is getting a build failure as below, for BAM2.
 Is this fixed already?

 Installing org.wso2.carbon.identity.relying.party.feature.group
 4.0.0.SNAPSHOT.
 Installing org.wso2.carbon.identity.core.feature.group 4.0.0.SNAPSHOT.
 Installation failed.
 Cannot complete the install because one or more required items could
 not be found.
  Software being installed: WSO2 Carbon - Cassandra Explorer Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.cassandra.explorer.feature.group
 4.0.0.SNAPSHOT)
  Missing requirement: apache-cassandra 1.1.0.wso2v1 (apache-cassandra
 1.1.0.wso2v1) requires 'package com.google.common.base [11.0.1.wso2v1]' 
 but
 it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.cassandra.explorer.server.feature.group
 [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Cassandra Explorer server Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.cassandra.explorer.server.feature.group 4.0.0.SNAPSHOT)
   To: apache-cassandra [1.1.0.wso2v1]
 Application failed, log file location:
 /home/pradeeban/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1340346466974.log

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Business Activity Monitor  SUCCESS
 [1.893s]
 [INFO] WSO2 Business Activity Monitor Styles Parent .. SUCCESS
 [0.014s]
 [INFO] WSO2 BAM UI styles  SUCCESS
 [9.403s]
 [INFO] WSO2 Business Activity Monitor Features Parent  SUCCESS
 [0.014s]
 [INFO] WSO2 BAM - Features Aggregator Module . SUCCESS
 [0.010s]
 [INFO] WSO2 BAM - Style Features . SUCCESS
 [2.097s]
 [INFO] WSO2 Business Activity Monitor P2 Profile Generation  FAILURE
 [32.847s]
 [INFO] WSO2 Business Activity Monitor - Product .. SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 48.517s
 [INFO] Finished at: Fri Jun 22 11:57:55 IST 2012
 [INFO] Final Memory: 32M/334M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5-SNAPSHOT:p2-profile-gen
 (3-p2-profile-generation) on project wso2bam-p2-profile-gen: P2 publisher
 return code was 13 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with
 the command
 [ERROR]   mvn goals -rf

[Dev] [Bamboo-Build] WSO2 Carbon Kernel #337 was SUCCESSFUL (with 2801 tests). Change made by suresh.


---
WSO2 Carbon  Kernel  #337 was successful.
---
Code has been updated by suresh.
2801 tests in total.

http://wso2.org/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-337/


--
Code Changes
--
suresh (130890):

removing privileged actions extension codes from the kernal core. these codes 
will be committed to another location with few more modifications



--
Tests
--
Fixed Tests (10)
   - MessageContextTests: W s ctxt w s d l s e r v i c e read
   - MessageContextTests: W s ctxt w s d l i n t e r f a c e read
   - MessageContextTests: W s ctxt w s d l d e s c r i p t i o n read
   - MessageContextTests: W s ctxt w s d l o p e r a t i o n read
   - MessageContextTests: W s ctxt w s d l p o r t read
   - OMElementDispatchTest: O m element dispatch with parsed entity reader
   - RuntimeExceptionsAsyncMepTest: Async polling async m e p web service 
exception
   - RuntimeExceptionsAsyncMepTest: Async polling async m e p wsdl fault
   - RuntimeExceptionsAsyncMepTest: Async callback async m e p wsdl fault
   - DispatchXPayloadStringTests: Simple

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

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

2012-06-22 Thread Isuru Suriarachchi

On Fri, Jun 22, 2012 at 3:13 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi Isuru,


 On Fri, Jun 22, 2012 at 2:58 PM, Isuru Suriarachchi is...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 2:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi,

 On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Lakmali,

 Can you please explain why we need this SuperTenantRolePlayer and why
 it always returns false for isUltimateDestination()? Looks like, we can't
 always return false here and have to figure out whether this is the
 ultimate destination of the message. If the message is going into a tenant,
 returning false is ok. But for the super tenant case, it should return
 true. In any case, please look into this urgently and fix. This has
 introduced a fundamental bug in addressing and RM.


 We need to set the SuperTenantRolePlayer to invoke secure services by
 tenants. This was actually had been a module inside products previously
 (ex: AS org.wso2.stratos.appserver.deployment) and I just made it common by
 adding it as a stratos component. This was done as a fix for the issue [1].

 Previously this was only added to the services. Now after
 product-service merging this SuperTenantRolePlayer might be an issue to the
 products.


 Yes, correct..


 Will look in this.


 You can fix this either by not registering the Role Player for super
 tenant or by writing the logic inside that method to determine whether it
 is called by the super tenant or not.


 Thanks for the suggestions. If we don't register the Role Player for super
 tenant, stratos secure services will fail in its super tenant flow while
 trying to process must understand fields for security headers. Because the
 rampart is engaged for services, only in sub tenants flow.

 So I think we have to take the second approach.


I just looked into this and looks like we can't figure out whether the
incoming request is going to a service hosted in super tenant or to a
service hosted in a sub tenant. That is because isUltimateDestination()
doesn't have the message context or any other information.

Therefore we'll have to figure out a proper solution for this. Azeez, have
you got any idea?

Thanks,
~Isuru



 Thanks,
 Lakmali


 Thanks,
 ~Isuru



 [1] 
 https://wso2.org/jira/browse/STRATOS-1953https://wso2.org/jira/browse/STRATOS-1953

 Thanks,
 Lakmali



 Thanks,
 ~Isuru

 On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.comwrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the
 way which was described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=
 http://www.w3.org/2003/05/soap-envelope;
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line
 has the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put 
 return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Lakmali Baminiwatta*
 *
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 mobile:  +94 71 2335936
 *
 *




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Lakmali Baminiwatta*
 *
 Software Engineer
 WSO2, Inc.: http://wso2.com

[Dev] [Bamboo-Build] WSO2 Carbon platform #394 has FAILED. Change made by 11 authors.


---
WSO2 Carbon  platform  #394 failed.
---
Code has been updated by pradeeban, hiranya, rajika, sinthuja, tharindu, 
subash, dinusha, lakmali, sanjayav, lalaji, chanaka.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-394/


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



--
Code Changes
--
dinusha (130876):

upgrading cassandra-jdbc driver.

hiranya (130884):

Fixing APISTORE-383

rajika (130874):

Fixed the role names to be nouns and to indicate the context.



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

Re: [Dev] Integration test failure in AS

2012-06-22 Thread Kasun Gajasinghe

I think this may be because of the issue with addressing module that
affected RM as well.

Regards,
--KasunG

On Fri, Jun 22, 2012 at 9:24 AM, Afkham Azeez az...@wso2.com wrote:


 ---
 Test set: TestSuite

 ---
 Tests run: 52, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 210.746
 sec  FAILURE!
 securityScenariosTestCase(org.wso2.appserver.integration.tests.HelloWorldSampleTestCase)
  Time elapsed: 1.277 sec   FAILURE!
 org.apache.axis2.AxisFault: SOAP header missing
 at
 org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
  at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
  at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
 at
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
  at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
  at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
  at
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
 at
 org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.doGreetWithSec(HelloWorldSampleTestCase.java:205)
  at
 org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.securityScenariosTestCase(HelloWorldSampleTestCase.java:370)
 Caused by: org.apache.rampart.RampartException: SOAP header missing
  at org.apache.rampart.RampartEngine.process(RampartEngine.java:117)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
  ... 47 more

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




-- 
*Kasun Gajasinghe*
Software Engineer;
Development Technologies Team, WSO2 Inc.; http://wso2.com ,
*email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe*
*
*blog: **http://blog.kasunbg.org* http://blog.kasunbg.org*
twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can not activate instance of component org.wso2.carbon.ntask.core.internal.TasksDSComponent.

2012-06-22 Thread Nuwan Bandara

Hi DIlshan,

I believe if you add slf4j to dependencies this can be mitigated.

Regards,
/Nuwan

On Fri, Jun 22, 2012 at 2:51 PM, Dilshan Edirisuriya dils...@wso2.comwrote:

 Hi,

 When adding ntask feature to Jaggery it doesnt get activated due to
 missing dependency of slf4j.


 =
 osgi ls -c 149
 Components in bundle org.wso2.carbon.ntask.core:
 ID  Component details
 28  Component[
 name = tasks.component
 factory = null
 autoenable = true
 immediate = true
 implementation =
 org.wso2.carbon.ntask.core.internal.TasksDSComponent
 state = Unsatisfied
 properties = {service.pid=tasks.component}
 serviceFactory = false
 serviceInterface = null
 references = {
 Reference[name = registry.service, interface =
 org.wso2.carbon.registry.core.service.RegistryService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setRegistryS
 ervice, unbind = unsetRegistryService]
 Reference[name = coordination.service, interface =
 org.wso2.carbon.coordination.core.services.CoordinationService, policy =
 dynamic, cardinality = 1..1, target = null, bind =
  setCoordinationService, unbind = unsetCoordinationService]
 Reference[name = user.realmservice.default, interface =
 org.wso2.carbon.user.core.service.RealmService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setRealmSe
 rvice, unbind = unsetRealmService]
 Reference[name = config.context.service, interface =
 org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setConfigu
 rationContextService, unbind = unsetConfigurationContextService]
 }
 located in bundle = org.wso2.carbon.ntask.core_4.0.0.SNAPSHOT [149]
 ]
 Dynamic information :
   The component is satisfied
   All component references are satisfied
   Component configurations :
 Configuration properties:
   service.pid = tasks.component
   component.name = tasks.component
   component.id = 40
 Instances:
 No instances were created because: Can not activate instance of
 component org.wso2.carbon.ntask.core.internal.TasksDSComponent. The
 activation throws: java.lang.NoClassDefFoundError: org
 /slf4j/LoggerFactory


 =

 osgi bundle 149
 org.wso2.carbon.ntask.core_4.0.0.SNAPSHOT [149]
   Id=149, Status=ACTIVE  Data
 Root=E:\svn\platform\trunk\products\jaggery\modules\distribution\target\jaggery-0.9.0-ALPHA\carbon\repository\components\configuration\org.eclipse.osgi\bund
 les\149\data
   No registered services.
   No services in use.
   Exported packages
 org.wso2.carbon.ntask.core.internal; version=0.0.0[exported]
 org.wso2.carbon.ntask.core; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.service; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.impl; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.service.impl; version=0.0.0[exported]
   Imported packages
 org.quartz; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.quartz.impl; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.quartz.impl.matchers; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.apache.commons.logging;
 version=1.1.1org.wso2.carbon.logging_4.0.0.SNAPSHOT [143]
 org.osgi.service.component;
 version=1.1.0org.eclipse.osgi.services_3.3.0.v20110513 [99]
 org.wso2.carbon.user.core.service;
 version=4.0.0.SNAPSHOTorg.wso2.carbon.user.core_4.0.0.SNAPSHOT [172]
 org.wso2.carbon.registry.core.service;
 version=1.0.1org.wso2.carbon.registry.core_4.0.0.SNAPSHOT [154]
 org.wso2.carbon.coordination.core.services;
 version=0.0.0org.wso2.carbon.coordination.core_4.0.0.SNAPSHOT [112]
 org.wso2.carbon.utils;
 version=4.0.0.SNAPSHOTorg.wso2.carbon.utils_4.0.0.SNAPSHOT [177]
   No fragment bundles
   Named class space
 org.wso2.carbon.ntask.core; bundle-version=4.0.0.SNAPSHOT[provided]
   No required bundles

 =


 Regards,

 Dilshan


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




-- 
*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
*
http://www.nuwanbando.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to do secondary indexing with bam-data-publisher for Stratos-Logging

2012-06-22 Thread Suhothayan Sriskandarajah

On Fri, Jun 22, 2012 at 2:36 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 2:29 PM, Tharindu Mathew thari...@wso2.comwrote:

 This can be a useful feature for realtime requirements. But we need to
 follow some proper convention as this changes the event stream definition
 This is then an extensive change, and we are close to feature freezing.

 On Fri, Jun 22, 2012 at 2:15 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 2:02 PM, Deependra Ariyadewa d...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 1:45 PM, Amani Soysa am...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 1:24 PM, Tharindu Mathew thari...@wso2.comwrote:

 This will be useful for folks who want real time data access, but BAM
 is not designed to be real time. I don't want the Agent API to be 
 specific
 to Cassandra, either.

 There should be a clean way to do this. How did you decide to do it
 this way? Was there a discussion?

 Yes there was a discussion on this some time back on Architecture
 -RFC: Architecture for Stratos Log Processing  where we decided to push
 logs to bam event receiver through the publisher and view logs using 
 hector
 api.


 Initially we tried to use flume as the Stratos log collector/manager
 but we stop flume evaluation because BAM's capability to cover the same use
 case.

  There are several workarounds like create relevant keyspaces in the
 tenant creation or create extended event receiver only for logging.

 If we do it in the tenant creation time their will be around 10
 keyspaces per each tenant (given that for each server, we create a keyspace
 as I explained earlier) So even a user doesn't use a particular server
 their will be a keyspace for it. So if there are 1000 tenants there will be
 10 000 keyspace (even if some keyspaces are not used at all) So I think its
 better to create keyspaces when ever logs are publishing to that particular
 keyspace.

 10 keryspaces per tenant?? Are you sure that's right...

 Yes for each sever (maybe more than 10 :) )
 ie - data services,appserver,esb,mb,cep,bps,brs etc all the products we
 offer for stratos deployment , because we store logs for each server in
 different keyspace(if not we have to keep everything in a single keyspace
 per tenant and it will be an expensive search when we filter the logs from
 the server level because we give users server specific logs)
 In our earlier syslog implementation we divided logs per each server for
 fast result (as logs generates). Thats why its very important to not to
 create keyspaces if users are not using a particular product.


I also agree with tharindu, that we should not make stream definition
Cassandra specific, since this can also be used for JDBC data-store or
InMemory data-store for CEP.

Since this is an Cassandra specific issue and since we know the stream
definition in advance, I believe its appropriate to have a Cassandra data
store configuration which maps the stream definition to the appropriate
Cassandra create key store query. Through this when the client request sent
for defineEventStream the Cassandra data-store can first checks if it match
one of the entry in the configuration, if so it runs the create key store
query given in the configuration to create the key store with indexes, else
it will create the key store in the normal way.
Through this we can also restrict the number of unnecessary key store
creation.

Regards
Suho


 Thanks,

 Deependra.


 On Fri, Jun 22, 2012 at 8:45 AM, Amani Soysa am...@wso2.com wrote:

 Hi,

 Currently we are sending LogEvent data through bam data publisher to
 bam event receiver using a custom log4j appender. And we retrieve logs
 using the hector API for the carbon log viewer. However, we need to have
 secondary indexes for several columns so that we can filter log 
 information
 for a given column ( such as date, applicationName, priority,logger etc)
 when creating the data publisher (keyspace). From the current Bam Data
 publisher implementation we cannot do secondary indexing all we can do 
 is
 define the column name and the data type of that column, and reciver
 creates the keyspaces for given columns with their data types.

  streamId = dataPublisher.defineEventStream({ + 
 'name':'org.wso2.carbon.logging.$tenantId.$serverName',
+   'version':'1.0.0', +   'nickName':
 'Logs',
+   'description': 'Logging Event', + 
  'metaData':[
+{'name':'clientType','type':'STRING'}
 +   ],
+   'payloadData':[
+   {'name':'tenantID','type':'
 STRING'},
+   {'name':'serverName','type':'
 STRING'},
+   {'name':'appName','type':'
 STRING'},
+   {'name':'logTime','type':'LONG'}
 ,
+   {'name':'logger','type':'
 STRING'},
+   {'name':'priority','type':'
 STRING'},

Re: [Dev] Jaggery - Alpha Release Dashboard

2012-06-22 Thread Ruchira Wageesha

Hi all,

We are in the process of moving the Jaggery codebase into github. So, Alpha
will be released from github repo in next week.

/Ruchira

On Wed, Jun 13, 2012 at 5:38 PM, Ruchira Wageesha ruch...@wso2.com wrote:

 Hi,

 We have planned to release Jaggery Alpha on 22nd of June, 2012. You can
 find the JIRA dashboard at [1].

 FYI.

 [1] https://wso2.org/jira/secure/Dashboard.jspa?selectPageId=10300

 regards,
 Ruchira

 --
 *Ruchira Wageesha
 Senior Software Engineer  Member, Management Committee, Development
 Technologies*
 *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
 *
 email: ruch...@wso2.com,   blog: ruchirawageesha.blogspot.com,   mobile: +94
 77 5493444*




-- 
*Ruchira Wageesha
Senior Software Engineer  Member, Management Committee, Development
Technologies*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: ruch...@wso2.com,   blog: ruchirawageesha.blogspot.com,   mobile:
+94 77 5493444*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] Compilation Failure (directory-server-manager)

2012-06-22 Thread Vijitha Kumara

FYA...




[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.directory.server.manager:
Compilation failure
[ERROR]
/home/vijitha/Src-Repo/carbon/platform/trunk/components/directory-server-manager/org.wso2.carbon.directory.server.manager/src/main/java/org/wso2/carbon/directory/server/manager/internal/LDAPServerStoreManager.java:[366,98]
cannot find symbol
[ERROR] symbol  : variable USER_FILTER
[ERROR] location: class org.wso2.carbon.user.core.ldap.LDAPConstants
[ERROR] - [Help 1]




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

[Dev] Build failure Apache Synapse - Core

2012-06-22 Thread Malinga Perera

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
(default-compile) on project synapse-core: Compilation failure: Compilation
failure:
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[31,15]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[27,15]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[26,36]
cannot find symbol
[ERROR] symbol  : class SynapseImportFactory
[ERROR] location: package org.apache.synapse.config.xml
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[29,15]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/endpoints/algorithms/RoundRobin.java:[27,26]
sun.security.action.LoadLibraryAction is Sun proprietary API and may be
removed in a future release
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[37,15]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[141,22]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[117,22]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MultiXMLConfigurationSerializer.java:[330,16]
cannot find symbol
[ERROR] symbol  : variable SynapseImportSerializer
[ERROR] location: class
org.apache.synapse.config.xml.MultiXMLConfigurationSerializer
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MultiXMLConfigurationSerializer.java:[646,35]
cannot find symbol
[ERROR] symbol  : variable SynapseImportSerializer
[ERROR] location: class
org.apache.synapse.config.xml.MultiXMLConfigurationSerializer
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/SynapseXMLConfigurationSerializer.java:[243,34]
cannot find symbol
[ERROR] symbol  : variable SynapseImportSerializer
[ERROR] location: class
org.apache.synapse.config.xml.SynapseXMLConfigurationSerializer
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[49,38]
cannot find symbol
[ERROR] symbol  : variable SynapseImportFactory
[ERROR] location: class org.apache.synapse.deployers.ImportDeployer
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[100,38]
cannot find symbol
[ERROR] symbol  : variable SynapseImportFactory
[ERROR] location: class org.apache.synapse.deployers.ImportDeployer
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/SynapseXMLConfigurationFactory.java:[295,34]
cannot find symbol
[ERROR] symbol  : variable SynapseImportFactory
[ERROR] location: class
org.apache.synapse.config.xml.SynapseXMLConfigurationFactory
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[117,22]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[115,25]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR] - [Help 1]


-- 
-Malinga
___
Dev mailing list
Dev@wso2.org

Re: [Dev] Writing unit tests for Cassandra operations

On Fri, Jun 22, 2012 at 4:58 PM, Tharindu Mathew thari...@wso2.com wrote:

 Hi everyone,

 I have been able to do $subject using Cassandra unit and they were very
 effective in writing the revamped Cassandra store for BAM2.

 Please use it for tests if you are planning to use Cassandra for any
 feature.


Hi Tharindu,
 Is it necessary to use data-access feature with cassandra for these tests ?

Thanks
Shammi



 Tests are at:
 https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/event-bridge/org.wso2.carbon.eventbridge.streamdefn.cassandra/src/test/java/org/wso2/carbon/eventbridge/streamdefn/cassandra

 --
 Regards,

 Tharindu

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


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




-- 
Best Regards,*

Shammi Jayasinghe*
Senior Software Engineer; WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Writing unit tests for Cassandra operations

On Fri, Jun 22, 2012 at 5:11 PM, Shammi Jayasinghe sha...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 4:58 PM, Tharindu Mathew thari...@wso2.comwrote:

 Hi everyone,

 I have been able to do $subject using Cassandra unit and they were very
 effective in writing the revamped Cassandra store for BAM2.

 Please use it for tests if you are planning to use Cassandra for any
 feature.


 Hi Tharindu,
  Is it necessary to use data-access feature with cassandra for these tests
 ?

No Shammi. This starts an embedded Cassandra instance to perform Cassandra
operations without the need for an OSGI container.


 Thanks
 Shammi



 Tests are at:
 https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/event-bridge/org.wso2.carbon.eventbridge.streamdefn.cassandra/src/test/java/org/wso2/carbon/eventbridge/streamdefn/cassandra

 --
 Regards,

 Tharindu

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


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




 --
 Best Regards,*

 Shammi Jayasinghe*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com,
 mobile: +94 71 4493085





-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] send a mail to openstack

2012-06-22 Thread Damitha Kumarage

Hi Sajith,*
*When nova create the first instance on the compute node, it download the
image from the glance server and store at
*/var/lib/nova/instances/_base. *So from the second instance onward
the instance creation is faster because
instance is created from the already downloaded image.
So nova correctly don't delete this image location.

I created a patch for nova source so that it will not unmount the last
instance(and don't unmount any instance for that matter) and delete the
file stystem using python rmtree function.  With this patch nova function
properly.  Only thing is that some of the storage is still not deleted even
when instance is deleted, which I think we can bear with until openstack
fix this issue properly.

I also noted that openstack does not support qcow2 format for lxc yet(from
their code comments). But this is not an issue since in production, raw
devices are recommended.

In summary I can say that we are now good for using lxc containers with
openstack.

Damitha

On Wed, Jun 20, 2012 at 6:16 PM, Sajith Kariyawasam saj...@wso2.com wrote:


 On Wed, Jun 20, 2012 at 5:45 PM, Sajith Kariyawasam saj...@wso2.comwrote:

 On Wed, Jun 20, 2012 at 4:41 PM, Damitha Kumarage dami...@wso2.comwrote:

 Hi Sajith,

 Sending this thread to dev.
 I think we can patch the python code to get rid of this problem. If it
 is not a proper patch, at least I figured out a kind of hack to avoid that
 problem by modifying the lxc destroy method(perhaps comment it completely
 and let our daemon to handle the cleaning the disk space of containers)


 Seems we'll have to modify the image deletion functionality as well,
 because, even though an image is deleted through the management console, it
 is not deleted from the file system, it's still there in
 /var/lib/glance/images location.


 Correction : location is */var/lib/nova/instances/_base*




 Nirmal,
 In case of containers for carbon servers, is there a way we can ensure
 that when down scaling we first shutdown the latest container spawned?

 Thanks,
 Damitha


 On Wed, Jun 20, 2012 at 2:17 PM, Sajith Kariyawasam saj...@wso2.comwrote:

 Seems the problem i had regarding heap space problem is the qemu
 type..

 I reinstalled with option lxc and now im not getting any of those
 issues, carbon servers getting started up properly 


 On Wed, Jun 20, 2012 at 12:32 PM, Sajith Kariyawasam 
 saj...@wso2.comwrote:


 On Wed, Jun 20, 2012 at 6:36 AM, Damitha Kumarage dami...@wso2.comwrote:

 Hi Sajith,
 Can you ask Openstack community whether they have any solution for
 this problem[1]?

 Also if qemu does not work for your testing please use lxc again.
 qemu is inevitably slow since it is full software virtualization.

 Ya, with qemu I experience a considerable slowness.. even the ssh
 connectivity also seems very slower than lxc.. also, still I'm getting 
 that
 Could not reserve enough space for object heap error even though I
 increased the heap size values in wso2server.sh file. Will try with lxc s
 again.


 Thanks,
 Damitha

 [1]https://bugs.launchpad.net/nova/+bug/971621

 --
 __
 Damitha Kumarage
 Senior Technical Lead; WSO2 Inc.
 Oxygenating the Web Service Platform
 http://www.wso2.com/
 blog:
 http://damithakumarage.wordpress.com/
 __




 --
 Regards,
 *
 *
 *Sajith Kariyawasam*
 *Senior Software Engineer; WSO2, Inc.; http://wso2.com*




 --
 Regards,
 *
 *
 *Sajith Kariyawasam*
 *Senior Software Engineer; WSO2, Inc.; http://wso2.com*




 --
 __
 Damitha Kumarage
 Senior Technical Lead; WSO2 Inc.
 Oxygenating the Web Service Platform
 http://www.wso2.com/
 blog:
 http://damithakumarage.wordpress.com/
 __




 --
 Regards,
 *
 *
 *Sajith Kariyawasam*
 *Senior Software Engineer; WSO2, Inc.; http://wso2.com*




 --
 Regards,
 *
 *
 *Sajith Kariyawasam*
 *Senior Software Engineer; WSO2, Inc.; http://wso2.com*




-- 
__
Damitha Kumarage
Senior Technical Lead; WSO2 Inc.
Oxygenating the Web Service Platform
http://www.wso2.com/
blog:
http://damithakumarage.wordpress.com/
__
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure Apache Synapse - Core

2012-06-22 Thread Ishan Somasiri

I too got a similar error.


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
(default-compile) on project synapse-core: Compilation failure: Compilation
failure:
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[27,15]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[26,36]
cannot find symbol
[ERROR] symbol  : class SynapseImportFactory
[ERROR] location: package org.apache.synapse.config.xml
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[37,15]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/endpoints/algorithms/RoundRobin.java:[27,26]
sun.security.action.LoadLibraryAction is Sun proprietary API and may be
removed in a future release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[29,15]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[31,15]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[117,22]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/SynapseXMLConfigurationSerializer.java:[243,34]
cannot find symbol
[ERROR] symbol  : variable SynapseImportSerializer
[ERROR] location: class
org.apache.synapse.config.xml.SynapseXMLConfigurationSerializer
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[49,38]
cannot find symbol
[ERROR] symbol  : variable SynapseImportFactory
[ERROR] location: class org.apache.synapse.deployers.ImportDeployer
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[100,38]
cannot find symbol
[ERROR] symbol  : variable SynapseImportFactory
[ERROR] location: class org.apache.synapse.deployers.ImportDeployer
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[115,25]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[117,22]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[141,22]
sun.misc.Service is Sun proprietary API and may be removed in a future
release
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MultiXMLConfigurationSerializer.java:[330,16]
cannot find symbol
[ERROR] symbol  : variable SynapseImportSerializer
[ERROR] location: class
org.apache.synapse.config.xml.MultiXMLConfigurationSerializer
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MultiXMLConfigurationSerializer.java:[646,35]
cannot find symbol
[ERROR] symbol  : variable SynapseImportSerializer
[ERROR] location: class
org.apache.synapse.config.xml.MultiXMLConfigurationSerializer
[ERROR]
[ERROR]
/home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/SynapseXMLConfigurationFactory.java:[295,34]
cannot find symbol
[ERROR] symbol  : variable SynapseImportFactory

Re: [Dev] Can not activate instance of component org.wso2.carbon.ntask.core.internal.TasksDSComponent.

2012-06-22 Thread Dilshan Edirisuriya

Hi Nuwan,

I believe this slf4j dependency should be added to ntask component. As
products like AS already had this there was no issue when activating. But
this fails in Jaggery.

Regards,

Dilshan


On Fri, Jun 22, 2012 at 4:18 PM, Nuwan Bandara nu...@wso2.com wrote:

 Hi DIlshan,

 I believe if you add slf4j to dependencies this can be mitigated.

 Regards,
 /Nuwan

 On Fri, Jun 22, 2012 at 2:51 PM, Dilshan Edirisuriya dils...@wso2.comwrote:

 Hi,

 When adding ntask feature to Jaggery it doesnt get activated due to
 missing dependency of slf4j.


 =
 osgi ls -c 149
 Components in bundle org.wso2.carbon.ntask.core:
 ID  Component details
 28  Component[
 name = tasks.component
 factory = null
 autoenable = true
 immediate = true
 implementation =
 org.wso2.carbon.ntask.core.internal.TasksDSComponent
 state = Unsatisfied
 properties = {service.pid=tasks.component}
 serviceFactory = false
 serviceInterface = null
 references = {
 Reference[name = registry.service, interface =
 org.wso2.carbon.registry.core.service.RegistryService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setRegistryS
 ervice, unbind = unsetRegistryService]
 Reference[name = coordination.service, interface =
 org.wso2.carbon.coordination.core.services.CoordinationService, policy =
 dynamic, cardinality = 1..1, target = null, bind =
  setCoordinationService, unbind = unsetCoordinationService]
 Reference[name = user.realmservice.default, interface =
 org.wso2.carbon.user.core.service.RealmService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setRealmSe
 rvice, unbind = unsetRealmService]
 Reference[name = config.context.service, interface =
 org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setConfigu
 rationContextService, unbind = unsetConfigurationContextService]
 }
 located in bundle = org.wso2.carbon.ntask.core_4.0.0.SNAPSHOT
 [149]
 ]
 Dynamic information :
   The component is satisfied
   All component references are satisfied
   Component configurations :
 Configuration properties:
   service.pid = tasks.component
   component.name = tasks.component
   component.id = 40
 Instances:
 No instances were created because: Can not activate instance of
 component org.wso2.carbon.ntask.core.internal.TasksDSComponent. The
 activation throws: java.lang.NoClassDefFoundError: org
 /slf4j/LoggerFactory


 =

 osgi bundle 149
 org.wso2.carbon.ntask.core_4.0.0.SNAPSHOT [149]
   Id=149, Status=ACTIVE  Data
 Root=E:\svn\platform\trunk\products\jaggery\modules\distribution\target\jaggery-0.9.0-ALPHA\carbon\repository\components\configuration\org.eclipse.osgi\bund
 les\149\data
   No registered services.
   No services in use.
   Exported packages
 org.wso2.carbon.ntask.core.internal; version=0.0.0[exported]
 org.wso2.carbon.ntask.core; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.service; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.impl; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.service.impl; version=0.0.0[exported]
   Imported packages
 org.quartz; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.quartz.impl; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.quartz.impl.matchers; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.apache.commons.logging;
 version=1.1.1org.wso2.carbon.logging_4.0.0.SNAPSHOT [143]
 org.osgi.service.component;
 version=1.1.0org.eclipse.osgi.services_3.3.0.v20110513 [99]
 org.wso2.carbon.user.core.service;
 version=4.0.0.SNAPSHOTorg.wso2.carbon.user.core_4.0.0.SNAPSHOT [172]
 org.wso2.carbon.registry.core.service;
 version=1.0.1org.wso2.carbon.registry.core_4.0.0.SNAPSHOT [154]
 org.wso2.carbon.coordination.core.services;
 version=0.0.0org.wso2.carbon.coordination.core_4.0.0.SNAPSHOT [112]
 org.wso2.carbon.utils;
 version=4.0.0.SNAPSHOTorg.wso2.carbon.utils_4.0.0.SNAPSHOT [177]
   No fragment bundles
   Named class space
 org.wso2.carbon.ntask.core; bundle-version=4.0.0.SNAPSHOT[provided]
   No required bundles

 =


 Regards,

 Dilshan


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




 --
 *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
 *
 http://www.nuwanbando.com/

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

Re: [Dev] Build failure Apache Synapse - Core

2012-06-22 Thread Hiranya Jayathilaka

Udayanga, looks like one of your changes. Please fix asap.

Thanks,
Hiranya

On Fri, Jun 22, 2012 at 5:54 PM, Ishan Somasiri ish...@wso2.com wrote:

 I too got a similar error.


 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
 (default-compile) on project synapse-core: Compilation failure: Compilation
 failure:
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[27,15]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[26,36]
 cannot find symbol
 [ERROR] symbol  : class SynapseImportFactory
 [ERROR] location: package org.apache.synapse.config.xml
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[37,15]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/endpoints/algorithms/RoundRobin.java:[27,26]
 sun.security.action.LoadLibraryAction is Sun proprietary API and may be
 removed in a future release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[29,15]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[31,15]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[117,22]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/SynapseXMLConfigurationSerializer.java:[243,34]
 cannot find symbol
 [ERROR] symbol  : variable SynapseImportSerializer
 [ERROR] location: class
 org.apache.synapse.config.xml.SynapseXMLConfigurationSerializer
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[49,38]
 cannot find symbol
 [ERROR] symbol  : variable SynapseImportFactory
 [ERROR] location: class org.apache.synapse.deployers.ImportDeployer
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[100,38]
 cannot find symbol
 [ERROR] symbol  : variable SynapseImportFactory
 [ERROR] location: class org.apache.synapse.deployers.ImportDeployer
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[115,25]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[117,22]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[141,22]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MultiXMLConfigurationSerializer.java:[330,16]
 cannot find symbol
 [ERROR] symbol  : variable SynapseImportSerializer
 [ERROR] location: class
 org.apache.synapse.config.xml.MultiXMLConfigurationSerializer
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MultiXMLConfigurationSerializer.java:[646,35]
 cannot find symbol
 [ERROR] symbol  : variable SynapseImportSerializer
 [ERROR] location: class
 org.apache.synapse.config.xml.MultiXMLConfigurationSerializer
 [ERROR]
 [ERROR]

[Dev] ntask integrated to Mashup and Jaggery

2012-06-22 Thread Dilshan Edirisuriya

Hi,

The ntask component integration to Mashup and Jaggery has been completed.
Mashup ntask changes are already committed to svn. Jaggery changes will
be committed to svn once Nuwan has committed his jagery re-factoring tasks.

With those changes Jaggery will support new API methods such as
setTimeout() and setInterval().


Regards,

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

Re: [Dev] ntask integrated to Mashup and Jaggery

2012-06-22 Thread Nuwan Bandara

Dilshan, can you explain a little bit how setTimeout and setInterval works
in the context of jaggery. better if you can send the note to dev@jaggeryjs

Regards,
/Nuwan

On Fri, Jun 22, 2012 at 6:29 PM, Dilshan Edirisuriya dils...@wso2.comwrote:

 Hi,

 The ntask component integration to Mashup and Jaggery has been completed.
 Mashup ntask changes are already committed to svn. Jaggery changes will
 be committed to svn once Nuwan has committed his jagery re-factoring tasks.

 With those changes Jaggery will support new API methods such as
 setTimeout() and setInterval().


 Regards,

 Dilshan

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




-- 
*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
*
http://www.nuwanbando.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] G-Reg 4.5.0 is feature frozen

On Fri, Jun 22, 2012 at 9:47 AM, Samisa Abeysinghe sam...@wso2.com wrote:

On Fri, Jun 22, 2012 at 8:16 AM, Senaka Fernando sen...@wso2.com wrote:

Hi Samisa,

The main reason for this delay is a recent commit that got rid of @scr
annotation processing in some of the key components of G-Reg and across the
platform. What we should have been doing is simply get rid of version and
execution phase declarations, but in certain POM files the entire plugin
was removed (which is wrong).

The actual reasons were revealed yesterday and we had to drag the smoke
testing to validate these. To make best use of the wasted time, we decided
to continue with fixes ensuring that they do not introduce instabilities.
The plan is to announce the availability of the pack once smoke testing is
complete and we are confident that they are no show stoppers. Also, on a
separate front, we are making progress of isolating issues reported by the
500 odd tests that were added into the G-Reg integration.

I can understand on the reasoning for the slip in the milestone.

However, I would still like to highlight the need to have proactive
updates on the delays.

I am not the release manager for this product, however, there was no
update form the team working on the milestone nor the RMs that there is a
delay on the milestone, until I sent the ping this morning.
If these were discussed withing the team, there is no point, as the
community need to see what is going on. If these were discussed on the
other threads, I might have missed those, yet this thread was the one that
was originally discussing the milestone plans, so there needs to be an
update here.

Bottom line is:
1. Update proactively
2. Meet the deadlines, somehow, rather than discussing for not meeting
those after the deadline elapsed - this means plan for the unexpected

I am so aggressive on these milestone deadlines, because, we have more
issues to come, as we have not completed the whole test cycle, and we need
future time to fix those issues that are yet to come.

Hi All,

We still haven't a successful product build from bamboo due to various
failures in kernel and platform.
However, we did a smoke test cycle with the build [1] that announced by
dimuthuL and we didn't find any blocker.
We are looking forward to a successful bamboo build to announce as the
alpha pack.

[1]http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-248/artifact

Thanks
Ajith

Thanks,
Senaka.

On Fri, Jun 22, 2012 at 6:43 AM, Samisa Abeysinghe sam...@wso2.comwrote:

On Fri, Jun 22, 2012 at 6:39 AM, Samisa Abeysinghe sam...@wso2.comwrote:

On Fri, Jun 22, 2012 at 6:32 AM, Ajith Vitharana aji...@wso2.comwrote:

On Fri, Jun 22, 2012 at 6:10 AM, Samisa Abeysinghe sam...@wso2.comwrote:

On Mon, Jun 18, 2012 at 5:48 AM, Samisa Abeysinghe
sam...@wso2.comwrote:

On Sun, Jun 17, 2012 at 11:09 PM, Ajith Vitharana
aji...@wso2.comwrote:

Hi All,

G-Reg 4.5.0 M2 is available to download and following is the plan
for the next milestone build.
We are going to fix another 41 issues [1] (all remain L1 and L2) in
next milestone build( Friday ).

Tasks - 5 (L1)
improvements - 1
L1 bugs - 13
L2 bugs - 22

Already fixed issues for the next build - 4 :)

However, the milestone was supposed to be on Friday, but came on
Sunday. So more time anyway means more issues to be fixed.

Please do not plan to work on milestone over the weekend.

Schedule the next one to a Thursday and deliver at least by Friday.
Never plan milestones for a Friday, hereafter.

Looks like we missed M3 deadline set for yesterday?

Hi Samisa,

We have to wait for a successful build cycle of Bamboo.

If Bamboo is broken and you guys cannot proceed, please make all the
noise possible, pick up who broke the build and get them fixed.

As experience shows, the build never get fixed without set of folks
working and looking at it aggressively and picking and pingging those who
broke it to fix it, so some folks got to own this, and unfortunately, this
time around, G-Reg team got to be that some folks as they are the ones
going first with the release :)

We have already fixed enough issues[1] for the alpha milestone and
pack will be available EOD today.

Furthermore, fixed issues are of no use, if we do not have a working
pack, as they cannot be tried and be tested without a pack.
So meeting the milestone deadline means not only fixing issues, but also
ensuring the sipping of the packs - and to ship packs, you need to manage
not only the internal team plans, but also external factors such as
platform builds - except for acts of God.

Milestone means the pack availability, on time, and all other matters
are irrelevant form a release perspective.

[1]
https://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+REGISTRY+AND+fixVersion+%3D+%224.5.0+Alpha%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide

Thanks
Ajith

Re: [Dev] Can not activate instance of component org.wso2.carbon.ntask.core.internal.TasksDSComponent.

On Fri, Jun 22, 2012 at 6:16 PM, Dilshan Edirisuriya dils...@wso2.comwrote:

 Hi Nuwan,

 I believe this slf4j dependency should be added to ntask component. As
 products like AS already had this there was no issue when activating. But
 this fails in Jaggery.


I think you should import the slf4j bundle in ntask feature.



 Regards,

 Dilshan


 On Fri, Jun 22, 2012 at 4:18 PM, Nuwan Bandara nu...@wso2.com wrote:

 Hi DIlshan,

 I believe if you add slf4j to dependencies this can be mitigated.

  Regards,
 /Nuwan

 On Fri, Jun 22, 2012 at 2:51 PM, Dilshan Edirisuriya dils...@wso2.comwrote:

 Hi,

 When adding ntask feature to Jaggery it doesnt get activated due to
 missing dependency of slf4j.


 =
 osgi ls -c 149
 Components in bundle org.wso2.carbon.ntask.core:
 ID  Component details
 28  Component[
 name = tasks.component
 factory = null
 autoenable = true
 immediate = true
 implementation =
 org.wso2.carbon.ntask.core.internal.TasksDSComponent
 state = Unsatisfied
 properties = {service.pid=tasks.component}
 serviceFactory = false
 serviceInterface = null
 references = {
 Reference[name = registry.service, interface =
 org.wso2.carbon.registry.core.service.RegistryService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setRegistryS
 ervice, unbind = unsetRegistryService]
 Reference[name = coordination.service, interface =
 org.wso2.carbon.coordination.core.services.CoordinationService, policy =
 dynamic, cardinality = 1..1, target = null, bind =
  setCoordinationService, unbind = unsetCoordinationService]
 Reference[name = user.realmservice.default, interface =
 org.wso2.carbon.user.core.service.RealmService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setRealmSe
 rvice, unbind = unsetRealmService]
 Reference[name = config.context.service, interface =
 org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
 cardinality = 1..1, target = null, bind = setConfigu
 rationContextService, unbind = unsetConfigurationContextService]
 }
 located in bundle = org.wso2.carbon.ntask.core_4.0.0.SNAPSHOT
 [149]
 ]
 Dynamic information :
   The component is satisfied
   All component references are satisfied
   Component configurations :
 Configuration properties:
   service.pid = tasks.component
   component.name = tasks.component
   component.id = 40
 Instances:
 No instances were created because: Can not activate instance of
 component org.wso2.carbon.ntask.core.internal.TasksDSComponent. The
 activation throws: java.lang.NoClassDefFoundError: org
 /slf4j/LoggerFactory


 =

 osgi bundle 149
 org.wso2.carbon.ntask.core_4.0.0.SNAPSHOT [149]
   Id=149, Status=ACTIVE  Data
 Root=E:\svn\platform\trunk\products\jaggery\modules\distribution\target\jaggery-0.9.0-ALPHA\carbon\repository\components\configuration\org.eclipse.osgi\bund
 les\149\data
   No registered services.
   No services in use.
   Exported packages
 org.wso2.carbon.ntask.core.internal; version=0.0.0[exported]
 org.wso2.carbon.ntask.core; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.service; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.impl; version=0.0.0[exported]
 org.wso2.carbon.ntask.core.service.impl; version=0.0.0[exported]
   Imported packages
 org.quartz; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.quartz.impl; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.quartz.impl.matchers; version=2.1.1quartz_2.1.1.wso2v1 [184]
 org.apache.commons.logging;
 version=1.1.1org.wso2.carbon.logging_4.0.0.SNAPSHOT [143]
 org.osgi.service.component;
 version=1.1.0org.eclipse.osgi.services_3.3.0.v20110513 [99]
 org.wso2.carbon.user.core.service;
 version=4.0.0.SNAPSHOTorg.wso2.carbon.user.core_4.0.0.SNAPSHOT [172]
 org.wso2.carbon.registry.core.service;
 version=1.0.1org.wso2.carbon.registry.core_4.0.0.SNAPSHOT [154]
 org.wso2.carbon.coordination.core.services;
 version=0.0.0org.wso2.carbon.coordination.core_4.0.0.SNAPSHOT [112]
 org.wso2.carbon.utils;
 version=4.0.0.SNAPSHOTorg.wso2.carbon.utils_4.0.0.SNAPSHOT [177]
   No fragment bundles
   Named class space
 org.wso2.carbon.ntask.core; bundle-version=4.0.0.SNAPSHOT[provided]
   No required bundles

 =


 Regards,

 Dilshan


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




 --
 *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
 *
 http://www.nuwanbando.com/



 ___
 Dev mailing list
 Dev@wso2.org

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

On Fri, Jun 22, 2012 at 3:47 PM, Isuru Suriarachchi is...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 3:13 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 I just looked into this and looks like we can't figure out whether the
 incoming request is going to a service hosted in super tenant or to a
 service hosted in a sub tenant. That is because isUltimateDestination()
 doesn't have the message context or any other information.

 Therefore we'll have to figure out a proper solution for this. Azeez, have
 you got any idea?


I think the root cause of this issue is the MustUnderstand check.  Amila,
can you remember how this worked earlier?
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

Amila has sent the following response on 26th March 2010.

Unfortunately we can not do this since axiom method looks like this.

.setProcessed();

it does not allow to unset it.

But when I am going through the code I saw Axis2 only gets the relevant
soap headers to do the must understand header check.
i.e.

Iterator headerBlocks = envelope.getHeader().getHeadersToProcess((
RolePlayer)msgContext.getConfigurationContext().getAxisConfiguration().
getParameterValue(rolePlayer));

so I could solve this by setting the following RolePlayer to supper tenant.

public class SuperTenantRolePlayer implements RolePlayer{

private List roles;

public SuperTenantRolePlayer() {
this.roles = new ArrayList();
this.roles.add(supertenant);
}

public List getRoles() {
return this.roles;
}

public boolean isUltimateDestination() {
return false;
}
}

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

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

OK, now I realize the problem. This has been there since 2010, but we
didn't deploy RM enabled services on the ST in Stratos AS, so we didn't see
the problem. After the merging, things have started to fail.

Let me think of a solution.

On Fri, Jun 22, 2012 at 8:10 PM, Afkham Azeez az...@wso2.com wrote:


 Amila has sent the following response on 26th March 2010.

 Unfortunately we can not do this since axiom method looks like this.

 .setProcessed();

 it does not allow to unset it.

 But when I am going through the code I saw Axis2 only gets the relevant
 soap headers to do the must understand header check.
 i.e.

 Iterator headerBlocks = envelope.getHeader().getHeadersToProcess((
 RolePlayer)msgContext.getConfigurationContext().getAxisConfiguration().
 getParameterValue(rolePlayer));

 so I could solve this by setting the following RolePlayer to supper tenant.

 public class SuperTenantRolePlayer implements RolePlayer{

 private List roles;

 public SuperTenantRolePlayer() {
 this.roles = new ArrayList();
 this.roles.add(supertenant);
 }

 public List getRoles() {
 return this.roles;

 }

 public boolean isUltimateDestination() {
 return false;
 }
 }

 thanks,
 Amila.




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

The following solution came to my mind. We need to use a ThreadLocal
variable + Axis2 handler combination.

We have to introduce a TenantCheckHandler which will set a ThreadLocal
boolean variable called isSuperTenantRequest to true if it is a super
tenant request  false if it is a tenant request.

Next we modify the isUltimateDestination to use this ThreadLocal as follows:

public boolean isUltimateDestination() {
return TenantCheckHandler.getTenantRequest();
}


This solution will work right?

On Fri, Jun 22, 2012 at 8:12 PM, Afkham Azeez az...@wso2.com wrote:

 OK, now I realize the problem. This has been there since 2010, but we
 didn't deploy RM enabled services on the ST in Stratos AS, so we didn't see
 the problem. After the merging, things have started to fail.

 Let me think of a solution.


 On Fri, Jun 22, 2012 at 8:10 PM, Afkham Azeez az...@wso2.com wrote:


 Amila has sent the following response on 26th March 2010.

 Unfortunately we can not do this since axiom method looks like this.

 .setProcessed();

 it does not allow to unset it.

 But when I am going through the code I saw Axis2 only gets the relevant
 soap headers to do the must understand header check.
 i.e.

 Iterator headerBlocks = envelope.getHeader().getHeadersToProcess((
 RolePlayer)msgContext.getConfigurationContext().getAxisConfiguration().
 getParameterValue(rolePlayer));

 so I could solve this by setting the following RolePlayer to supper
 tenant.

 public class SuperTenantRolePlayer implements RolePlayer{

 private List roles;

 public SuperTenantRolePlayer() {
 this.roles = new ArrayList();
 this.roles.add(supertenant);
 }

 public List getRoles() {
 return this.roles;

 }

 public boolean isUltimateDestination() {
 return false;
 }
 }

 thanks,
 Amila.




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

Small mistake, method should be;

 public boolean isUltimateDestination() {
return TenantCheckHandler.isSuperTenantRequest();
}

On Fri, Jun 22, 2012 at 8:17 PM, Afkham Azeez az...@wso2.com wrote:

 The following solution came to my mind. We need to use a ThreadLocal
 variable + Axis2 handler combination.

 We have to introduce a TenantCheckHandler which will set a ThreadLocal
 boolean variable called isSuperTenantRequest to true if it is a super
 tenant request  false if it is a tenant request.

 Next we modify the isUltimateDestination to use this ThreadLocal as
 follows:

 public boolean isUltimateDestination() {
 return TenantCheckHandler.getTenantRequest();
 }


 This solution will work right?

 On Fri, Jun 22, 2012 at 8:12 PM, Afkham Azeez az...@wso2.com wrote:

 OK, now I realize the problem. This has been there since 2010, but we
 didn't deploy RM enabled services on the ST in Stratos AS, so we didn't see
 the problem. After the merging, things have started to fail.

 Let me think of a solution.


 On Fri, Jun 22, 2012 at 8:10 PM, Afkham Azeez az...@wso2.com wrote:


 Amila has sent the following response on 26th March 2010.

 Unfortunately we can not do this since axiom method looks like this.

 .setProcessed();

 it does not allow to unset it.

 But when I am going through the code I saw Axis2 only gets the relevant
 soap headers to do the must understand header check.
 i.e.

 Iterator headerBlocks = envelope.getHeader().getHeadersToProcess((
 RolePlayer)msgContext.getConfigurationContext().getAxisConfiguration().
 getParameterValue(rolePlayer));

 so I could solve this by setting the following RolePlayer to supper
 tenant.

 public class SuperTenantRolePlayer implements RolePlayer{

 private List roles;

 public SuperTenantRolePlayer() {
 this.roles = new ArrayList();
 this.roles.add(supertenant);
 }

 public List getRoles() {
 return this.roles;

 }

 public boolean isUltimateDestination() {
 return false;
 }
 }

 thanks,
 Amila.




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

I think the solution is even simpler. We just need the following:

public boolean isUltimateDestination() {
return (CarbonContext.getCurrentContext().getTenantId() ==
MultitenantConstants.SUPER_TENANT_ID);
}

On Fri, Jun 22, 2012 at 8:18 PM, Afkham Azeez az...@wso2.com wrote:

 Small mistake, method should be;

  public boolean isUltimateDestination() {
 return TenantCheckHandler.isSuperTenantRequest();
 }

 On Fri, Jun 22, 2012 at 8:17 PM, Afkham Azeez az...@wso2.com wrote:

 The following solution came to my mind. We need to use a ThreadLocal
 variable + Axis2 handler combination.

 We have to introduce a TenantCheckHandler which will set a ThreadLocal
 boolean variable called isSuperTenantRequest to true if it is a super
 tenant request  false if it is a tenant request.

 Next we modify the isUltimateDestination to use this ThreadLocal as
 follows:

 public boolean isUltimateDestination() {
 return TenantCheckHandler.getTenantRequest();
 }


 This solution will work right?

 On Fri, Jun 22, 2012 at 8:12 PM, Afkham Azeez az...@wso2.com wrote:

 OK, now I realize the problem. This has been there since 2010, but we
 didn't deploy RM enabled services on the ST in Stratos AS, so we didn't see
 the problem. After the merging, things have started to fail.

 Let me think of a solution.


 On Fri, Jun 22, 2012 at 8:10 PM, Afkham Azeez az...@wso2.com wrote:


 Amila has sent the following response on 26th March 2010.

 Unfortunately we can not do this since axiom method looks like this.

 .setProcessed();

 it does not allow to unset it.

 But when I am going through the code I saw Axis2 only gets the relevant
 soap headers to do the must understand header check.
 i.e.

 Iterator headerBlocks = envelope.getHeader().getHeadersToProcess((
 RolePlayer)msgContext.getConfigurationContext().getAxisConfiguration().
 getParameterValue(rolePlayer));

 so I could solve this by setting the following RolePlayer to supper
 tenant.

 public class SuperTenantRolePlayer implements RolePlayer{

 private List roles;

 public SuperTenantRolePlayer() {
 this.roles = new ArrayList();
 this.roles.add(supertenant);
 }

 public List getRoles() {
 return this.roles;

 }

 public boolean isUltimateDestination() {
 return false;
 }
 }

 thanks,
 Amila.




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

This fix should work. I have committed the fix. I have verified that the
proper tenant IDs are coming into the conditions. Please verify  resolve
the Jiras.

On Fri, Jun 22, 2012 at 8:24 PM, Afkham Azeez az...@wso2.com wrote:

 I think the solution is even simpler. We just need the following:

 public boolean isUltimateDestination() {
 return (CarbonContext.getCurrentContext().getTenantId() ==
 MultitenantConstants.SUPER_TENANT_ID);
 }

 On Fri, Jun 22, 2012 at 8:18 PM, Afkham Azeez az...@wso2.com wrote:

 Small mistake, method should be;

  public boolean isUltimateDestination() {
 return TenantCheckHandler.isSuperTenantRequest();
 }

 On Fri, Jun 22, 2012 at 8:17 PM, Afkham Azeez az...@wso2.com wrote:

 The following solution came to my mind. We need to use a ThreadLocal
 variable + Axis2 handler combination.

 We have to introduce a TenantCheckHandler which will set a ThreadLocal
 boolean variable called isSuperTenantRequest to true if it is a super
 tenant request  false if it is a tenant request.

 Next we modify the isUltimateDestination to use this ThreadLocal as
 follows:

 public boolean isUltimateDestination() {
 return TenantCheckHandler.getTenantRequest();
 }


 This solution will work right?

 On Fri, Jun 22, 2012 at 8:12 PM, Afkham Azeez az...@wso2.com wrote:

 OK, now I realize the problem. This has been there since 2010, but we
 didn't deploy RM enabled services on the ST in Stratos AS, so we didn't see
 the problem. After the merging, things have started to fail.

 Let me think of a solution.


 On Fri, Jun 22, 2012 at 8:10 PM, Afkham Azeez az...@wso2.com wrote:


 Amila has sent the following response on 26th March 2010.

 Unfortunately we can not do this since axiom method looks like this.

 .setProcessed();

 it does not allow to unset it.

 But when I am going through the code I saw Axis2 only gets the
 relevant soap headers to do the must understand header check.
 i.e.

 Iterator headerBlocks = envelope.getHeader().getHeadersToProcess((
 RolePlayer)msgContext.getConfigurationContext().
 getAxisConfiguration().getParameterValue(rolePlayer));

 so I could solve this by setting the following RolePlayer to supper
 tenant.

 public class SuperTenantRolePlayer implements RolePlayer{

 private List roles;

 public SuperTenantRolePlayer() {
 this.roles = new ArrayList();
 this.roles.add(supertenant);
 }

 public List getRoles() {
 return this.roles;

 }

 public boolean isUltimateDestination() {
 return false;
 }
 }

 thanks,
 Amila.




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org

Re: [Dev] Integration test failure in AS

2012-06-22 Thread Supun Malinga

Hi Andun,

Please test this with your changes related to addressing module fix as well.

thanks,

On Fri, Jun 22, 2012 at 4:08 PM, Kasun Gajasinghe kas...@wso2.com wrote:


 I think this may be because of the issue with addressing module that
 affected RM as well.

 Regards,
 --KasunG


 On Fri, Jun 22, 2012 at 9:24 AM, Afkham Azeez az...@wso2.com wrote:


 ---
 Test set: TestSuite

 ---
 Tests run: 52, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 210.746
 sec  FAILURE!
 securityScenariosTestCase(org.wso2.appserver.integration.tests.HelloWorldSampleTestCase)
  Time elapsed: 1.277 sec   FAILURE!
 org.apache.axis2.AxisFault: SOAP header missing
 at
 org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
  at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
  at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
 at
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
  at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
  at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
  at
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
 at
 org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.doGreetWithSec(HelloWorldSampleTestCase.java:205)
  at
 org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.securityScenariosTestCase(HelloWorldSampleTestCase.java:370)
 Caused by: org.apache.rampart.RampartException: SOAP header missing
  at org.apache.rampart.RampartEngine.process(RampartEngine.java:117)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
  ... 47 more

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Kasun Gajasinghe*
 Software Engineer;
 Development Technologies Team, WSO2 Inc.; http://wso2.com ,
 *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe*
 *
  *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org*
 twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg*
 *


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




-- 
Supun Malinga,

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

[Dev] [Bamboo-Build] WSO2 Carbon platform #395 has FAILED. Change made by 10 authors.


---
WSO2 Carbon  platform  #395 failed.
---
Code has been updated by denis, kasunw, sinthuja, tharindu, waruna, isuruw, 
udayanga, lakmali, chanaka, lalaji.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-395/


--
Failing Jobs
--
  - Default Job (Default Stage): 1347 tests passed.



--
Code Changes
--
udayanga (130892):

commiting s

udayanga (130906):

replacing logs with log4j

udayanga (130914):

including mediation library stub 



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

Re: [Dev] [Bamboo-Build] WSO2 Carbon platform #395 has FAILED. Change made by 10 authors.

This is broken for a few hours...

@ESB team, can you please fix this ASAP?

On Fri, Jun 22, 2012 at 8:33 PM, Bamboo cbuil...@wso2.org wrote:

  [image: Failed]  WSO2 Carbonhttp://wso2.org/bamboo/browse/WSO2CARBON/›
 platform http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM/ › 
 #395http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-395/
 failed

 Code has been updated by denishttp://wso2.org/bamboo/browse/author/denis,
 kasunw http://wso2.org/bamboo/browse/author/kasunw, 
 sinthujahttp://wso2.org/bamboo/browse/author/sinthuja,
 tharindu http://wso2.org/bamboo/browse/author/tharindu, 
 warunahttp://wso2.org/bamboo/browse/author/waruna,
 isuruw http://wso2.org/bamboo/browse/author/isuruw, 
 udayangahttp://wso2.org/bamboo/browse/author/udayanga,
 lakmali http://wso2.org/bamboo/browse/author/lakmali, 
 chanakahttp://wso2.org/bamboo/browse/author/chanaka,
 lalaji http://wso2.org/bamboo/browse/author/lalaji.

 *0/1347* tests failed.
Failing Jobs http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-395/
 Job
 Duration Tests[image: Failed]  Default 
 Jobhttp://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-395/ (Default
 Stage)  125 minutes  1347 passed  
 Logshttp://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-395/log|
 Artifactshttp://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-395/artifact
  Code
 Changes http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-395/commit/  View
 all 20 code 
 changeshttp://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-395/commit/
 udayanga http://wso2.org/bamboo/browse/author/udayanga
 commiting fix for 
 CARBON-13089http://wso2.org/bamboo/project/jiraRedirect.action?jiraIssueKey=CARBON-13089bambooProjectKey=WSO2CARBON
 130916udayanga http://wso2.org/bamboo/browse/author/udayanga
 including mediation library stub  130914
 warunahttp://wso2.org/bamboo/browse/author/waruna
 Adding an integration testcase for B4P fault handling  130913   17 more
 changes… http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-395/commit 
 View
 Online http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-395 | Add
 Commentshttp://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-395?commentMode=true

 This message was sent by Atlassian Bamboo http://wso2.org/bamboo.

 If you wish to stop receiving these emails edit your user 
 profilehttp://wso2.org/bamboo/profile/userNotifications.actionor notify
 your administrator http://wso2.org/bamboo/viewAdministrators.action.

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




-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

Hi All,

I have verified that the issues are not there after the Revision 130953.
So resolved the issues.

Thanks
AndunSLG

On Fri, Jun 22, 2012 at 8:36 PM, Afkham Azeez az...@wso2.com wrote:

 This fix should work. I have committed the fix. I have verified that the
 proper tenant IDs are coming into the conditions. Please verify  resolve
 the Jiras.


 On Fri, Jun 22, 2012 at 8:24 PM, Afkham Azeez az...@wso2.com wrote:

 I think the solution is even simpler. We just need the following:

 public boolean isUltimateDestination() {
 return (CarbonContext.getCurrentContext().getTenantId() ==
 MultitenantConstants.SUPER_TENANT_ID);
 }

 On Fri, Jun 22, 2012 at 8:18 PM, Afkham Azeez az...@wso2.com wrote:

 Small mistake, method should be;

  public boolean isUltimateDestination() {
 return TenantCheckHandler.isSuperTenantRequest();
 }

 On Fri, Jun 22, 2012 at 8:17 PM, Afkham Azeez az...@wso2.com wrote:

 The following solution came to my mind. We need to use a ThreadLocal
 variable + Axis2 handler combination.

 We have to introduce a TenantCheckHandler which will set a ThreadLocal
 boolean variable called isSuperTenantRequest to true if it is a super
 tenant request  false if it is a tenant request.

 Next we modify the isUltimateDestination to use this ThreadLocal as
 follows:

 public boolean isUltimateDestination() {
 return TenantCheckHandler.getTenantRequest();
 }


 This solution will work right?

 On Fri, Jun 22, 2012 at 8:12 PM, Afkham Azeez az...@wso2.com wrote:

 OK, now I realize the problem. This has been there since 2010, but we
 didn't deploy RM enabled services on the ST in Stratos AS, so we didn't 
 see
 the problem. After the merging, things have started to fail.

 Let me think of a solution.


 On Fri, Jun 22, 2012 at 8:10 PM, Afkham Azeez az...@wso2.com wrote:


 Amila has sent the following response on 26th March 2010.

 Unfortunately we can not do this since axiom method looks like this.

 .setProcessed();

 it does not allow to unset it.

 But when I am going through the code I saw Axis2 only gets the
 relevant soap headers to do the must understand header check.
 i.e.

 Iterator headerBlocks = envelope.getHeader().getHeadersToProcess((
 RolePlayer)msgContext.getConfigurationContext().
 getAxisConfiguration().getParameterValue(rolePlayer));

 so I could solve this by setting the following RolePlayer to supper
 tenant.

 public class SuperTenantRolePlayer implements RolePlayer{

 private List roles;

 public SuperTenantRolePlayer() {
 this.roles = new ArrayList();
 this.roles.add(supertenant);
 }

 public List getRoles() {
 return this.roles;

 }

 public boolean isUltimateDestination() {
 return false;
 }
 }

 thanks,
 Amila.




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter:

Re: [Dev] Integration test failure in AS

Will check it.

On Fri, Jun 22, 2012 at 8:38 PM, Supun Malinga sup...@wso2.com wrote:

 Hi Andun,

 Please test this with your changes related to addressing module fix as
 well.

 thanks,

 On Fri, Jun 22, 2012 at 4:08 PM, Kasun Gajasinghe kas...@wso2.com wrote:


 I think this may be because of the issue with addressing module that
 affected RM as well.

 Regards,
 --KasunG


 On Fri, Jun 22, 2012 at 9:24 AM, Afkham Azeez az...@wso2.com wrote:


 ---
 Test set: TestSuite

 ---
 Tests run: 52, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 210.746
 sec  FAILURE!
 securityScenariosTestCase(org.wso2.appserver.integration.tests.HelloWorldSampleTestCase)
  Time elapsed: 1.277 sec   FAILURE!
 org.apache.axis2.AxisFault: SOAP header missing
 at
 org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
  at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
  at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
 at
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
  at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
  at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
  at
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
 at
 org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.doGreetWithSec(HelloWorldSampleTestCase.java:205)
  at
 org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.securityScenariosTestCase(HelloWorldSampleTestCase.java:370)
 Caused by: org.apache.rampart.RampartException: SOAP header missing
  at org.apache.rampart.RampartEngine.process(RampartEngine.java:117)
 at
 org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
  ... 47 more

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




 --
 *Kasun Gajasinghe*
 Software Engineer;
 Development Technologies Team, WSO2 Inc.; http://wso2.com ,
 *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe*
 *
  *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org*
 twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg*
 *


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




 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321


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

Re: [Dev] Build failure Apache Synapse - Core

2012-06-22 Thread Udayanga Wickramasinghe

On Fri, Jun 22, 2012 at 6:20 PM, Hiranya Jayathilaka hira...@wso2.comwrote:

 Udayanga, looks like one of your changes. Please fix asap.

 sorry my bad..this is fixed now


 Thanks,
 Hiranya


 On Fri, Jun 22, 2012 at 5:54 PM, Ishan Somasiri ish...@wso2.com wrote:

 I too got a similar error.


 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
 (default-compile) on project synapse-core: Compilation failure: Compilation
 failure:
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[27,15]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[26,36]
 cannot find symbol
  [ERROR] symbol  : class SynapseImportFactory
 [ERROR] location: package org.apache.synapse.config.xml
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[37,15]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/endpoints/algorithms/RoundRobin.java:[27,26]
 sun.security.action.LoadLibraryAction is Sun proprietary API and may be
 removed in a future release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[29,15]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[31,15]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorSerializerFinder.java:[117,22]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/SynapseXMLConfigurationSerializer.java:[243,34]
 cannot find symbol
  [ERROR] symbol  : variable SynapseImportSerializer
 [ERROR] location: class
 org.apache.synapse.config.xml.SynapseXMLConfigurationSerializer
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[49,38]
 cannot find symbol
  [ERROR] symbol  : variable SynapseImportFactory
 [ERROR] location: class org.apache.synapse.deployers.ImportDeployer
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/deployers/ImportDeployer.java:[100,38]
 cannot find symbol
  [ERROR] symbol  : variable SynapseImportFactory
 [ERROR] location: class org.apache.synapse.deployers.ImportDeployer
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[115,25]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/ConfigurationFactoryAndSerializerFinder.java:[117,22]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorFactoryFinder.java:[141,22]
 sun.misc.Service is Sun proprietary API and may be removed in a future
 release
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MultiXMLConfigurationSerializer.java:[330,16]
 cannot find symbol
  [ERROR] symbol  : variable SynapseImportSerializer
 [ERROR] location: class
 org.apache.synapse.config.xml.MultiXMLConfigurationSerializer
 [ERROR]
 [ERROR]
 /home/ishan/coding/wso2/repo/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/MultiXMLConfigurationSerializer.java:[646,35]
 cannot find symbol
  [ERROR] symbol  : variable SynapseImportSerializer

Re: [Dev] [DEV] Compilation Failure (directory-server-manager)

On Fri, Jun 22, 2012 at 4:31 PM, Vijitha Kumara viji...@wso2.com wrote:

 FYA...



 

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.directory.server.manager:
 Compilation failure
 [ERROR]
 /home/vijitha/Src-Repo/carbon/platform/trunk/components/directory-server-manager/org.wso2.carbon.directory.server.manager/src/main/java/org/wso2/carbon/directory/server/manager/internal/LDAPServerStoreManager.java:[366,98]
 cannot find symbol
 [ERROR] symbol  : variable USER_FILTER
 [ERROR] location: class org.wso2.carbon.user.core.ldap.LDAPConstants
 [ERROR] - [Help 1]


 


Hi All,

Is this fixed ? The platform build of bamboo  failing due to this
compilation failure .

Thanks
Ajith



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




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

Re: [Dev] [DEV] Compilation Failure (directory-server-manager)

2012-06-22 Thread Asela Pathberiya

Fixed the build failure in directory-server-manager component. Please take
svn up of it.

Thanks,
Asela.

On Fri, Jun 22, 2012 at 9:36 PM, Ajith Vitharana aji...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 4:31 PM, Vijitha Kumara viji...@wso2.com wrote:

 FYA...



 

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.directory.server.manager:
 Compilation failure
 [ERROR]
 /home/vijitha/Src-Repo/carbon/platform/trunk/components/directory-server-manager/org.wso2.carbon.directory.server.manager/src/main/java/org/wso2/carbon/directory/server/manager/internal/LDAPServerStoreManager.java:[366,98]
 cannot find symbol
 [ERROR] symbol  : variable USER_FILTER
 [ERROR] location: class org.wso2.carbon.user.core.ldap.LDAPConstants
 [ERROR] - [Help 1]


 


 Hi All,

 Is this fixed ? The platform build of bamboo  failing due to this
 compilation failure .

 Thanks
 Ajith



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




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

Re: [Dev] [DEV] Compilation Failure (directory-server-manager)

On Fri, Jun 22, 2012 at 9:54 PM, Asela Pathberiya as...@wso2.com wrote:

 Fixed the build failure in directory-server-manager component. Please take
 svn up of it.


Thanks for the quick response.

/Ajith


 Thanks,
 Asela.


 On Fri, Jun 22, 2012 at 9:36 PM, Ajith Vitharana aji...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 4:31 PM, Vijitha Kumara viji...@wso2.com wrote:

 FYA...



 

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.directory.server.manager:
 Compilation failure
 [ERROR]
 /home/vijitha/Src-Repo/carbon/platform/trunk/components/directory-server-manager/org.wso2.carbon.directory.server.manager/src/main/java/org/wso2/carbon/directory/server/manager/internal/LDAPServerStoreManager.java:[366,98]
 cannot find symbol
 [ERROR] symbol  : variable USER_FILTER
 [ERROR] location: class org.wso2.carbon.user.core.ldap.LDAPConstants
 [ERROR] - [Help 1]


 


 Hi All,

 Is this fixed ? The platform build of bamboo  failing due to this
 compilation failure .

 Thanks
 Ajith



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




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






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

[Dev] [Jaggery] Error while accessing the API Store App in trunk build

2012-06-22 Thread Lalaji Sureshika

Hi,

With the latest build of API Manager in trunk,it's unable to access the API
Store App and following null pointer exception[1] appears in the
console.[Note that API Provider app can be accessed and its functionalities
are working without any issue.]

According to the below stack trace,the error coming from 4th line
of /apistore/site/themes/fancy/templates/ui/dialogs/template.jag file,and
that line contains the code as;

* var showLogin = %=session.get(showLogin)%;*

Is this happening due to a change done in session host object? Appreciate
any help regarding this.

[1] [2012-06-22 22:15:19,456]  INFO - CarbonAuthenticationUtil
'admin@carbon.super [-1234]' logged in at [2012-06-22 22:15:19,456+0430]
from IP address 175.157.133.6
[2012-06-22 22:15:26,158] ERROR - RhinoEngine
org.mozilla.javascript.WrappedException: Wrapped
java.lang.NullPointerException
(/apistore/site/themes/fancy/templates/ui/dialogs/template.jag#4)
[2012-06-22 22:15:26,165] ERROR - WebAppManager
org.mozilla.javascript.WrappedException: Wrapped
java.lang.NullPointerException
(/apistore/site/themes/fancy/templates/ui/dialogs/template.jag#4)
org.wso2.carbon.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
java.lang.NullPointerException
(/apistore/site/themes/fancy/templates/ui/dialogs/template.jag#4)
at
org.wso2.carbon.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:448)
at
org.wso2.carbon.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:202)
at
org.wso2.carbon.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:224)
at org.wso2.carbon.jaggery.core.JaggeryServlet.doGet(JaggeryServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
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:169)
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:143)
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:48)
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:999)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
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.WrappedException: Wrapped
java.lang.NullPointerException
(/apistore/site/themes/fancy/templates/ui/dialogs/template.jag#4)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1654)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:175)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:411)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:97)
at
org.wso2.carbon.rhino.site.themes.fancy.templates.ui.dialogs.c0._c1(/apistore/site/themes/fancy/templates/ui/dialogs/template.jag:4)
at
org.wso2.carbon.rhino.site.themes.fancy.templates.ui.dialogs.c0.call(/apistore/site/themes/fancy/templates/ui/dialogs/template.jag)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:86)
at org.wso2.carbon.rhino.jagg.c0._c23(/apistore/jagg/jagg.jag:161)
at org.wso2.carbon.rhino.jagg.c0.call(/apistore/jagg/jagg.jag)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:97)
at org.wso2.carbon.rhino.jagg.c0._c38(/apistore/jagg/jagg.jag:444)
at org.wso2.carbon.rhino.jagg.c0.call(/apistore/jagg/jagg.jag)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:76)
at
org.wso2.carbon.rhino.site.themes.fancy.templates.page.base.c0._c1(/apistore/site/themes/fancy/templates/page/base/template.jag:46)
at
org.wso2.carbon.rhino.site.themes.fancy.templates.page.base.c0.call(/apistore/site/themes/fancy/templates/page/base/template.jag)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:86)
at

Re: [Dev] Don't group test methods using one method

2012-06-22 Thread Kishanthan Thangarajah

On Fri, Jun 22, 2012 at 8:52 AM, Afkham Azeez az...@wso2.com wrote:

 @Test(groups = {wso2.as})
 public void testWebappExample() {
 testUserManagerAndAuthenticationDemo();
 testRegistryUsageDemo();
 testCarbonCachingDemo();
 }


Fixed.

Thanks,
Kishanthan.


 Don't write tests like the above. Use TestNG dependency model.

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*




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

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] BAM 2.0.0 Milestone 5 released!

*WSO2 Business Activity Monitor 2.0.0 - Milestone 5 Released!**Date : 23rd
June 2012*
*
*
This milestone is available at -
http://people.wso2.com/~tharindu/m5/wso2bam-2.0.0-SNAPSHOT.zip

P2 Repo containing Agents for ESB and AS available at :
http://people.wso2.com/~kasunw/BAM2-M5-p2-repo/p2-repo/

Note: This M5 does not work on Windows due to a known issue with Hadoop.
This will be fixed for a future milestone.
This release can be tested *end-end. *This release is NOT compatible with
older milestone releases of BAM 2.0.0.* *Please check out the samples
located in the $BAM_HOME/samples directory to try out the features.


Main highlights of this release are:

*Agent API*

- A new Agent API model with the capability to define event streams

- A new fast Apache Thrift based API for high performance event capturing

- Java SDK for high performance Thrift clients

- A complete REST API for event capturing


*Scalable Storage*

- New versioned, stream definition based data model

- Implemented on top of Apache Cassandra for maximum scalability an write
throughput

*
*
*Scalable Analytics*

- SQL like scalable analytics query language on top of Apache Hive

- Specially built Hive JDBC handler only available for WSO2 BAM

- Big Data Scalable analytics with the integration of Apache Hadoop

*
*
*BAM Toolboxes*

- One click deployment of complete monitoring scenarios with BAM Toolboxes.
Ex: KPI Definition

- Ability to package BAM artifacts for easy deployment

*
*
*BAM Mediators and Statistic collectors*
*
*
- ESB Mediator for capturing data from mediation flows

- Statistic Collectors for AS, ESB and other WSO2 products

*
*
*Gadget Generation*

- Simplified dashboard generation with a step by step wizard



We welcome your feedback and would love to hear your thoughts on this
release of WSO2 BAM.

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

Re: [Dev] JavaScript Caching in Jaggery

2012-06-22 Thread Chris Haddad

Does option 1 or 2 provide us with any performance/footprint advantage over 
node.js/v8?

/Chris
+1.678.431.1656


On Jun 21, 2012, at 8:58, Ruchira Wageesha ruch...@wso2.com wrote:

 Hi all,
 
 We are using Rhino's script compilation support in Jaggery product to improve 
 the performance of JS execution.
 
 When we compiled a JS file using Rhino, we can get either 
 An object(Script) of the *.class file
 This will be kept in memory and executed when ever needed
 When n webapps of m size in a jaggery server are equally accessed, n x m 
 memory will be needed in order keep all webapp objects in memory
 If the server doesn't have enough memory, then we will have to recompile the 
 same webapp time to time 
 A *.class file for that script
 In this way, we can save the *.class file to the disk and load it using a 
 custom classloader. 
 In a muti-tenant environment, we can release the memory of unused 
 classloaders and load the classes on demand using saved *.class files
 As per my understanding, it would be able to server n webapps of m size using 
 less amount of memory than above 1 by unloading unused classloaders and 
 loading *.class on demand  
 Currently it has been implemented to work in both modes, but I am not sure 
 which one would be ideal for the case.
 
 Welcome your thoughts 
 
 regards,
 Ruchira
 
 -- 
 Ruchira Wageesha
 Senior Software Engineer  Member, Management Committee, Development 
 Technologies
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com
 
 email: ruch...@wso2.com,   blog: ruchirawageesha.blogspot.com,   mobile: +94 
 77 5493444
 
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Add new user failed in latest packs.

Hi DimuthuL,

This is a real blocker for the milestone release.

[1]https://wso2.org/jira/browse/CARBON-13513


[2012-06-23 05:14:38,936] ERROR
{org.wso2.carbon.server.admin.privilegedaction.extension.messagereceiver.PrivilegedActionExtensionMessageReceiver}
-  No privilaged action extension found
org.wso2.carbon.server.admin.privilegedaction.extension.core.PrivilegedActionExtensionException:
No extension found for the action
at
org.wso2.carbon.server.admin.privilegedaction.extension.core.PrivilegedActionExtensionRegistry.getPrivilegedActionExtensions(PrivilegedActionExtensionRegistry.java:55)
at
org.wso2.carbon.server.admin.privilegedaction.extension.messagereceiver.PrivilegedActionExtensionMessageReceiver.invokeBusinessLogic(PrivilegedActionExtensionMessageReceiver.java:57)
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:181)
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:205)
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:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
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:169)
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:143)
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:48)
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:999)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
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)
[2012-06-23 05:14:38,940] ERROR
{org.wso2.carbon.user.mgt.ui.UserAdminClient} -  No privilaged action
extension found
org.apache.axis2.AxisFault: No privilaged action extension found
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
at
org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnlyOperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at
org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1314)
at
org.wso2.carbon.user.mgt.ui.UserAdminClient.addUser(UserAdminClient.java:87)
at
org.apache.jsp.user.add_002dfinish_jsp._jspService(add_002dfinish_jsp.java:132)
at

Re: [Dev] G-Reg 4.5.0 is feature frozen

Hi All,

We can't create new users in latest G-Reg product [1].
Therefore, we still haven't a proper build to release as the alpha pack.

[1] https://wso2.org/jira/browse/CARBON-13513
[2]http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-252/artifact

Thanks
Ajith

On Fri, Jun 22, 2012 at 7:19 PM, Ajith Vitharana aji...@wso2.com wrote:



 On Fri, Jun 22, 2012 at 9:47 AM, Samisa Abeysinghe sam...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 8:16 AM, Senaka Fernando sen...@wso2.com wrote:

 Hi Samisa,

 The main reason for this delay is a recent commit that got rid of @scr
 annotation processing in some of the key components of G-Reg and across the
 platform. What we should have been doing is simply get rid of version and
 execution phase declarations, but in certain POM files the entire plugin
 was removed (which is wrong).

 The actual reasons were revealed yesterday and we had to drag the smoke
 testing to validate these. To make best use of the wasted time, we decided
 to continue with fixes ensuring that they do not introduce instabilities.
 The plan is to announce the availability of the pack once smoke testing is
 complete and we are confident that they are no show stoppers. Also, on a
 separate front, we are making progress of isolating issues reported by the
 500 odd tests that were added into the G-Reg integration.


 I can understand on the reasoning for the slip in the milestone.

 However, I would still like to highlight the need to have proactive
 updates on the delays.

 I am not the release manager for this product, however, there was no
 update form the team working on the milestone nor the RMs that there is a
 delay on the milestone, until I sent the ping this morning.
 If these were discussed withing the team, there is no point, as the
 community need to see what is going on. If these were discussed on the
 other threads, I might have missed those, yet this thread was the one that
 was originally discussing the milestone plans, so there needs to be an
 update here.

 Bottom line is:
 1. Update proactively
 2. Meet the deadlines, somehow, rather than discussing for not meeting
 those after the deadline elapsed - this means plan for the unexpected

 I am so aggressive on these milestone deadlines, because, we have more
 issues to come, as we have not completed the whole test cycle, and we need
 future time to fix those issues that are yet to come.


 Hi All,

 We still haven't a successful product build from bamboo due to various
 failures in kernel and platform.
 However, we did a smoke test cycle with the build [1] that announced by
 dimuthuL and we didn't find any blocker.
 We are looking forward to a successful bamboo build to announce as the
 alpha pack.

 [1]http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-248/artifact

 Thanks
 Ajith





 Thanks,
 Senaka.


 On Fri, Jun 22, 2012 at 6:43 AM, Samisa Abeysinghe sam...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 6:39 AM, Samisa Abeysinghe sam...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 6:32 AM, Ajith Vitharana aji...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 6:10 AM, Samisa Abeysinghe 
 sam...@wso2.comwrote:



 On Mon, Jun 18, 2012 at 5:48 AM, Samisa Abeysinghe 
 sam...@wso2.comwrote:



 On Sun, Jun 17, 2012 at 11:09 PM, Ajith Vitharana 
 aji...@wso2.comwrote:

 Hi All,

 G-Reg 4.5.0 M2 is available to download and following is the plan
 for the next milestone build.
 We are going to fix another 41 issues [1] (all remain L1 and L2)
 in next milestone build( Friday ).

 Tasks - 5 (L1)
 improvements - 1
 L1 bugs - 13
 L2 bugs -  22

 Already fixed issues for the  next build - 4   :)


 However, the milestone was supposed to be on Friday, but came on
 Sunday. So more time anyway means more issues to be fixed.

 Please do not plan to work on milestone over the weekend.

 Schedule the next one to a Thursday and deliver at least by Friday.
 Never plan milestones for a Friday, hereafter.


 Looks like we missed M3 deadline set for yesterday?


 Hi Samisa,

 We have to wait for a successful build cycle of Bamboo.


 If Bamboo is broken and you guys cannot proceed, please make all the
 noise possible, pick up who broke the build and get them fixed.

 As experience shows, the build never get fixed without set of folks
 working and looking at it aggressively and picking and pingging those who
 broke it to fix it, so some folks got to own this, and unfortunately, this
 time around, G-Reg team got to be that some folks as they are the ones
 going first with the release :)




 We have already fixed enough issues[1] for the alpha milestone and
 pack will be available EOD today.


 Furthermore, fixed issues are of no use, if we do not have a working
 pack, as they cannot be tried and be tested  without a pack.
 So meeting the milestone deadline means not only fixing issues, but
 also ensuring the sipping of the packs - and to ship packs, you need to
 manage not only the internal team plans, but also external factors such as
 platform builds -

Re: [Dev] [Dev-Jaggery] JavaScript Caching in Jaggery

2012-06-22 Thread Sanjiva Weerawarana

I can't see the advantages of option 2 ... we have to assume every bit of
JS is different so its not about sharing a .class. If we can have a lazy
loading + unloading scheme in place then option 1 is fine IMO.

We should be able to piggyback off the webapp lazyloading stuff?

Sanjiva.

On Thu, Jun 21, 2012 at 6:28 PM, Ruchira Wageesha ruch...@wso2.com wrote:

 Hi all,

 We are using Rhino's script compilation support in Jaggery product to
 improve the performance of JS execution.

 When we compiled a JS file using Rhino, we can get either

1. An object(Script) of the *.class file
   - This will be kept in memory and executed when ever needed
   - When n webapps of m size in a jaggery server are equally
   accessed, n x m memory will be needed in order keep all webapp objects 
 in
   memory
   - If the server doesn't have enough memory, then we will have to
   recompile the same webapp time to time
2. A *.class file for that script
   - In this way, we can save the *.class file to the disk and load it
   using a custom classloader.
   - In a muti-tenant environment, we can release the memory of unused
   classloaders and load the classes on demand using saved *.class files
   - As per my understanding, it would be able to server n webapps of
   m size using less amount of memory than above 1 by unloading unused
   classloaders and loading *.class on demand

 Currently it has been implemented to work in both modes, but I am not sure
 which one would be ideal for the case.

 Welcome your thoughts 

 regards,
 Ruchira

 --
 *Ruchira Wageesha
 Senior Software Engineer  Member, Management Committee, Development
 Technologies*
 *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
 *
 email: ruch...@wso2.com,   blog: ruchirawageesha.blogspot.com,   mobile: +94
 77 5493444*


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




-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman  CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

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

[Dev] [Bamboo-Build] WSO2 Carbon platform #396 has FAILED (1 tests failed). Change made by 17 authors.


---
WSO2 Carbon  platform  #396 failed.
---
Code has been updated by hiranya, sinthuja, nuwanw, kishanthan, udayanga, 
sanjayav, senaka, asela, kasunw, tharindu, maninda, waruna, azeez, ajithn, 
isuruw, lakmali, rathav.
1/2019 tests failed.

http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-396/


--
Failing Jobs
--
  - Default Job (Default Stage): 1 of 2019 tests failed.



--
Code Changes
--
kasunw (130955):

adding bam data agents category

udayanga (130958):

fixing missing synapse import  changes

lakmali (130972):

Adding ndatasource component



--
Tests
--
New Test Failures (1)
   - CompensationHandling20Test: Compensation handlers

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

[Dev] Why using apiprovider as the webapp name for API Publisher

2012-06-22 Thread Denis Weerasiri

Hi,
In API manager admin console, web app name for API Publisher is
apiprovider.
As a new user to API Manager, it was confusing to me.
Is it ok to rename it to apipublisher?

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

[Dev] OSGi version range issue when deploying a bundle in dropins

Hi All,

Here's the problem scenario:

I've added a bundle into dropins folder which has an import like
org.apache.commons
.io.input;version=[1.4,2), so this should ideally means that I need to
have a package org.apache.commons .io.input
whose range (r) is s.t. 1.4 = r 2

But it seems that this validation is not correctly happen. See following
[1] outputs from OSGi console of a carbon server.

Can some one please explain this behaviour? Isn't this a bug?

FYI: it fails (quite correctly) when you try to install a feature having
these two bundles.
Missing requirement: jclouds sshj ssh client 1.5.0.beta_2 (jclouds-sshj
1.5.0.beta_2) requires 'package org.apache.commons.io.input [1.4.0,2.0.0)'
but it could not be found

[1]
osgi b 42
commons-io_2.0.0.wso2v1 [42]
  Id=42, Status=ACTIVE  Data
Root=/media/wso2/new-carbon/graphite/products/as/modules/distribution/target/wso2as-5.0.0-SNAPSHOT/repository/components/configuration/org.eclipse.osgi/bundles/42/data
  No registered services.
  No services in use.
  Exported packages
org.apache.commons.io.output; version=2.0.0[exported]
org.apache.commons.io.monitor; version=2.0.0[exported]
org.apache.commons.io.filefilter; version=2.0.0[exported]
org.apache.commons.io.comparator; version=2.0.0[exported]
*org.apache.commons.io.input; version=2.0.0[exported]*
org.apache.commons.io; version=2.0.0[exported]
  No imported packages
  No fragment bundles
  Named class space
commons-io; bundle-version=2.0.0.wso2v1[provided]
  No required bundles

osgi packages org.apache.commons.io.input
org.apache.commons.io.input; version=2.0.0commons-io_2.0.0.wso2v1 [42]
  axis2_1.6.1.wso2v5 [19] imports
  jclouds-sshj_1.5.0.beta_2 [79] imports
  org.apache.commons.io_1.4.0 [114] imports
  org.wso2.carbon.registry.core_4.0.0.SNAPSHOT [355] imports

osgi b 79
jclouds-sshj_1.5.0.beta_2 [79]
  Id=79, Status=ACTIVE  Data
Root=/media/wso2/new-carbon/graphite/products/as/modules/distribution/target/wso2as-5.0.0-SNAPSHOT/repository/components/configuration/org.eclipse.osgi/bundles/79/data
  No registered services.
  No services in use.
  Exported packages
org.jclouds.sshj.config; version=1.5.0.beta2[exported]
org.jclouds.sshj; version=1.5.0.beta2[exported]
  Imported packages
com.google.common.base; version=12.0.0.wso2v1guava_12.0.0.wso2v1
[55]
com.google.common.collect; version=12.0.0.wso2v1guava_12.0.0.wso2v1
[55]
com.google.common.io; version=12.0.0.wso2v1guava_12.0.0.wso2v1 [55]
com.google.common.net; version=12.0.0.wso2v1guava_12.0.0.wso2v1 [55]
com.google.inject; version=1.3.0com.google.inject_3.0.0 [34]
com.google.inject.binder; version=1.3.0com.google.inject_3.0.0 [34]
javax.annotation; version=0.0.0org.eclipse.osgi_3.7.0.v20110613 [0]
javax.inject; version=3.0.0.wso2v1guice_3.0.0.wso2v1 [56]
net.schmizz.sshj; version=0.8.0net.schmizz.sshj_0.8.0 [101]
net.schmizz.sshj.common; version=0.8.0net.schmizz.sshj_0.8.0 [101]
net.schmizz.sshj.connection; version=0.8.0net.schmizz.sshj_0.8.0
[101]
net.schmizz.sshj.connection.channel.direct;
version=0.8.0net.schmizz.sshj_0.8.0 [101]
net.schmizz.sshj.sftp; version=0.8.0net.schmizz.sshj_0.8.0 [101]
net.schmizz.sshj.transport; version=0.8.0net.schmizz.sshj_0.8.0
[101]
net.schmizz.sshj.transport.verification;
version=0.8.0net.schmizz.sshj_0.8.0 [101]
net.schmizz.sshj.userauth; version=0.8.0net.schmizz.sshj_0.8.0 [101]
net.schmizz.sshj.userauth.keyprovider;
version=0.8.0net.schmizz.sshj_0.8.0 [101]
net.schmizz.sshj.xfer; version=0.8.0net.schmizz.sshj_0.8.0 [101]
org.apache.commons.io.input; version=2.0.0commons-io_2.0.0.wso2v1
[42]
org.jclouds.compute.domain;
version=1.5.0.beta2jclouds-compute_1.5.0.beta_2 [71]
org.jclouds.crypto; version=1.5.0.beta2jclouds-core_1.5.0.beta_2
[72]
org.jclouds.domain; version=1.5.0.beta2jclouds-core_1.5.0.beta_2
[72]
org.jclouds.http.handlers;
version=1.5.0.beta2jclouds-core_1.5.0.beta_2 [72]
org.jclouds.io; version=1.5.0.beta2jclouds-core_1.5.0.beta_2 [72]
org.jclouds.io.payloads;
version=1.5.0.beta2jclouds-core_1.5.0.beta_2 [72]
org.jclouds.logging; version=1.5.0.beta2jclouds-core_1.5.0.beta_2
[72]
org.jclouds.predicates; version=1.5.0.beta2jclouds-core_1.5.0.beta_2
[72]
org.jclouds.rest; version=1.5.0.beta2jclouds-core_1.5.0.beta_2 [72]
org.jclouds.ssh; version=1.5.0.beta2jclouds-compute_1.5.0.beta_2
[71]
org.jclouds.util; version=1.5.0.beta2jclouds-core_1.5.0.beta_2 [72]
  No fragment bundles
  Named class space
jclouds-sshj; bundle-version=1.5.0.beta_2[provided]
  No required bundles



-- 

Thanks  regards,
Nirmal

Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OSGi version range issue when deploying a bundle in dropins