Re: [Carbon-dev] [Carbon Studio] ESB Graphical editor - Example 1

[Paul Fremantle]

I'm sure there are code utils in Eclipse to help with this. For example a
quick google found this:
http://www.eclipse.org/gef/zest/

Paul

On 6 February 2012 06:11, Sumedha Rubasinghe  wrote:

> Viraj,
> Layout is a general problem seen in these type of tools.
> For example, If you use MySQL Workbench & reverse engineer a database, all
> tables will appear overlapped (with links created). We need to manually
> layout the tables in a visually appealing way.
>
> /sumedha
>
>
> On Mon, Feb 6, 2012 at 10:40 AM, Viraj Rajaguru  wrote:
>
>> Hi,
>>
>> When we are going to implement reverse engineering support, the main
>> issue is the layout management of the diagram as we are handling many
>> mediators in a single compartment.
>> As a solution we thought of using grouping mechanism for the proxy
>> services (A proxy service will have a certain group box and relevant
>> mediators and endpoints goes in to that group box.). This will help us to
>> manage the layout to some extent as this will split the whole diagram in
>> to manageable sections. If we would success with this approach we can give
>> the reverse engineering support for the initial release.
>>
>>
>> Thanks,
>> Viraj.
>>
>>
>> On Mon, Feb 6, 2012 at 7:22 AM, Samisa Abeysinghe wrote:
>>
>>>
>>>
>>> On Sun, Jan 29, 2012 at 6:41 PM, Chathuri Wimalasena 
>>> wrote:
>>>
 We still do not have the reverse engineering support since it is
 technically quite hard.
>>>
>>>
>>>
>>> Why is that so hard?
>>>
>>> In the Graphic first model, we have:
>>>
>>> Graphic -- represents --> Object Model -- serialize --> XML model
>>>
>>> In the reverse directions we have:
>>>
>>> XML model -- de-serialize --> Object Model -- represents --> Graphic
>>>
>>> If the design is right, I see no issues doing this.
>>>
>>>
 At the moment, we are focusing on completing the mediators and
 improving look and feel of the editor.

 Review is scheduled for this Wednesday (01/02/2012) and we will be able
 to give a pack for testing after that. At the moment, this editor is not
 being connected with C-App concepts (i.e it is there as a separate feature
 where users can create a synapse configuration).

 Regards,
 Chathuri



 On Sun, Jan 29, 2012 at 4:21 PM, Viraj Rajaguru  wrote:

> Hi,
>
> Fixes for the above mentioned issues will be available in "Overall
> Milestone Plan CS 2.0.0" [1]. Some fixes are already done.
>
> We do not have the reverse engineering support yet.
>
> We are supporting following mediators.
>
>- Log Mediator
>- Drop Mediator
>- Property Mediator
>- Enrich Mediator
>- Send Mediator
>- Filter Mediator
>- Switch Mediator
>- XSLT Mediator
>- Fault Mediator
>- Header Mediator
>- DBLookup Mediator
>- DBReport Mediator
>- Clone Mediator
>- Iterate Mediator
>- Aggregate Mediator
>- Callout Mediator
>- Transaction Mediator
>- RMSequence Mediator
>
> And also graphical implementation of around 12 new mediators have been
> done. Only serialization logic has to be implemented for them.
>
>
> Thanks,
>
> [1]
> https://docs.google.com/a/wso2.com/document/d/1gTLfLBuEphtHesJf_eSyHNLcisrogEW8Aw4v-2R-iFQ/edit?hl=en_US
>
>
> On Sun, Jan 29, 2012 at 7:22 AM, Samisa Abeysinghe wrote:
>
>> What is the ETA for these fixes? In other words, in which milestone
>> would these fixes be available?
>>
>> Do we have reverse engineering support now? Meaning, can I edit the
>> source and it will reflect the changes in the graphical view.
>>
>> How many meadiators are supported?
>>
>> What is the plan for testing?
>>
>> On mediators, Jan 25, 2012 at 9:53 AM, Viraj Rajaguru > > wrote:
>>
>>> Hi,
>>>
>>> We had a discussion on ESB Graphical Editor with Hiranya. In this
>>> discussion we figured out how to overcome existing issues in the editor.
>>> Followings are the proposed solutions.
>>>
>>>- We are not going to represent Local Entries graphically inside
>>>the editor, Instead we put them on the tool palette.Then user can 
>>> add them
>>>to relevant mediators using the context menu.
>>>- And also we can add defined sequences to "receive" attribute
>>>in the "Send Mediator" using the context menu as above. It is not 
>>> necessary
>>>to represent this relationship in graphically.
>>>
>>> And also following issues were recognized in this discussion.
>>>
>>>- When we add a new Sequence, a dialog box should not be
>>>appeared to request a name for sequence.
>>>- In Failover endpoint, Loadbalance endpoint, Switch mediator
>>>and Clone mediator, there should not be an option to add output 
>>> connectors
>>>manually.It should 

Re: [Carbon-dev] Fix for Registry Deadlocking

[Senaka Fernando]

Hi Amila, Anjana,

DimuthuG did this sometime back and also produced a spreadsheet (should be
on google docs) on the sequences. But something that we probably missed (as
in this case) is the locking granularity. There is a subtle difference when
row-level and table-level locks are acquired in and not-in combination,
which is not a frequent use-case; but some like these might still exist
unnoticed.

Thanks,
Senaka.

On Mon, Feb 6, 2012 at 12:04 PM, Anjana Fernando  wrote:

> Hi Amila,
>
> On Mon, Feb 6, 2012 at 11:50 AM, Amila Suriarachchi wrote:
>
>>
>>
>> On Mon, Feb 6, 2012 at 11:35 AM, Anjana Fernando  wrote:
>>
>>> Hi Amila,
>>>
>>> On Mon, Feb 6, 2012 at 10:30 AM, Amila Suriarachchi wrote:
>>>


 On Mon, Feb 6, 2012 at 12:50 AM, Senaka Fernando wrote:

> Hi all,
>
> We discussed this offline, and the issue here is valid, Anjana can
> explain further if someone wants to understand it.


 Can you please do that?

 I also thought (as Senaka mentioned) update sequence should be
 consistent across different transaction scenarios. In that case we need to
 study all the sql update patterns of the registry and put them to same lock
 acquiring sequence.

>>>
>>> I guess, that's what we just did. Updating scenarios are basically
>>> registry "put" and "delete". The "put" operations actually does "delete"
>>> ones internally (when updating), so we aligned the actual inserts/delete
>>> sequences. So now, the separate "delete" operation also will also run in
>>> the same lock acquiring sequence.
>>>
>>
>> In that case you need to check all the transaction scenarios of the
>> registry and see whether they acquire the locks in same order. Otherwise
>> you will get deadlocks when the incompatible two transactions executed in
>> parallel. It does not matter whether one registry transaction calls or not
>> but finally all the database level transactions should acquire the locks in
>> same order.
>>
>
> Yes, I just assume these are the only locations we are doing the updates,
> or else if there any more related updates to the same tables, we should
> check those. Anyways, the most frequently occurred deadlock (maybe the only
> one), is the one to do with the put/delete, this should be fixed by this,
> and I don't think this change will give way to new deadlock situations,
> best thing to do is test it and see.
>
> Cheers,
> Anjana.
>
>
>>
>> thanks,
>> Amila.
>>
>>
>>>
>>> Cheers,
>>> Anjana.
>>>
>>>

 thanks,
 Amila.


> But out of the three options, right now, only #3 seems to be possible
> without breaking consistency. But even this needs to be tested against all
> DBs, because we are momentarily fooling the DB, by inserting a NULL value
> as the content id.
>
> Anjana will work with someone (perhaps Ajith), who knows the registry
> kernel and get this fix checked in. We can easily test this with a bulk
> WSDL upload operation, that produces deadlocks.
>
> Thanks,
> Senaka.
>
>
> On Mon, Feb 6, 2012 at 12:08 AM, Senaka Fernando wrote:
>
>> Hi again,
>>
>> And with regard to #3, if that's a safe option go for it. That's
>> probably due to somebody not realizing the possibility. Anyway, I'm not 
>> the
>> expert when it comes to SQL stuff, may be Sumedha can provide some 
>> insight?
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Mon, Feb 6, 2012 at 12:06 AM, Senaka Fernando wrote:
>>
>>> Hi Anjana,
>>>
>>> So is this a complete sequence of operations? If so, once a write
>>> lock is acquired, IIRC it will be held until the transaction completes 
>>> - am
>>> I missing something?
>>>
>>> Also, there are some INSERT statements above the deletes. What about
>>> those?
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> On Mon, Feb 6, 2012 at 12:00 AM, Anjana Fernando wrote:
>>>
 Hi,

 I may have possibly found a solution for the registry deadlocking
 for concurrent puts/deletes. I was checking the SQL statements 
 executed for
 a put, and the list is as follows.

 SELECT REG_PATH_ID FROM REG_PATH WHERE
 REG_PATH_VALUE='/_system/config/abc1' AND REG_TENANT_ID=0
 SELECT REG_VERSION FROM REG_RESOURCE WHERE REG_PATH_ID=4 AND
 REG_NAME='abc1' AND REG_TENANT_ID=0
 SELECT REG_PATH_ID FROM REG_PATH WHERE
 REG_PATH_VALUE='/_system/config/abc1' AND REG_TENANT_ID=0
 SELECT REG_MEDIA_TYPE, REG_CREATOR, REG_CREATED_TIME,
 REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME, REG_VERSION, REG_DESCRIPTION,
 REG_CONTENT_ID FROM REG_RESOURCE WHERE REG_PATH_ID=4 AND REG_NAME = 
 'abc1'
 AND REG_TENANT_ID=0
 SELECT REG_CONTENT_DATA FROM REG_CONTENT WHERE REG_CONTENT_ID = 105
 AND REG_TENANT_ID=0
 SELECT REG_NAME, REG_VALUE FROM REG_PROPERTY P,
 R

[Carbon-dev] Jaggery Jira components

[Samisa Abeysinghe]

Folks,
   I added components into  https://wso2.org/jira/browse/JAGGERY

   Please make sure you pick the right components when you add issues.

   If you do not find the right components, please holler.

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #176 has FAILED. Change made by dharshana, prabatha and supunm.

[Bamboo]

---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #176 failed.
---
Code has been updated by dharshana, prabatha, supunm.
No failed tests found, a possible compilation error.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-176/


--
Failing Jobs
--
  - WSO2 Carbon Trunk Build Process (Default Stage): No tests found.


--
Code Changes
--
dharshana (120149):

>Updated  Framework Factory added all product modules

prabatha (120147):

>changing the url to tasks.jsp

supunm (120148):

>fiing CARBON-12307



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

Re: [Carbon-dev] [Carbon Studio] ESB Graphical editor - Example 1

[Kalpa Senanayake]

Hi,
   I have done POC on zest while ago for check the feasibility to use node
like structure within the data service wizard.AFAIK it
has several algorithms to manage it's graph nodes. In our case
SpringLayoutAlgorithm [1] will be useful.


[1]
http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.5.2/org.eclipse.zest/layouts/1.1.0/org/eclipse/zest/layouts/algorithms/SpringLayoutAlgorithm.java

On Mon, Feb 6, 2012 at 1:30 PM, Paul Fremantle  wrote:

> I'm sure there are code utils in Eclipse to help with this. For example a
> quick google found this:
> http://www.eclipse.org/gef/zest/
>
> Paul
>
>
> On 6 February 2012 06:11, Sumedha Rubasinghe  wrote:
>
>> Viraj,
>> Layout is a general problem seen in these type of tools.
>> For example, If you use MySQL Workbench & reverse engineer a database,
>> all tables will appear overlapped (with links created). We need to manually
>> layout the tables in a visually appealing way.
>>
>> /sumedha
>>
>>
>> On Mon, Feb 6, 2012 at 10:40 AM, Viraj Rajaguru  wrote:
>>
>>> Hi,
>>>
>>> When we are going to implement reverse engineering support, the main
>>> issue is the layout management of the diagram as we are handling many
>>> mediators in a single compartment.
>>> As a solution we thought of using grouping mechanism for the proxy
>>> services (A proxy service will have a certain group box and relevant
>>> mediators and endpoints goes in to that group box.). This will help us to
>>> manage the layout to some extent as this will split the whole diagram in
>>> to manageable sections. If we would success with this approach we can give
>>> the reverse engineering support for the initial release.
>>>
>>>
>>> Thanks,
>>> Viraj.
>>>
>>>
>>> On Mon, Feb 6, 2012 at 7:22 AM, Samisa Abeysinghe wrote:
>>>


 On Sun, Jan 29, 2012 at 6:41 PM, Chathuri Wimalasena >>> > wrote:

> We still do not have the reverse engineering support since it is
> technically quite hard.



 Why is that so hard?

 In the Graphic first model, we have:

 Graphic -- represents --> Object Model -- serialize --> XML model

 In the reverse directions we have:

 XML model -- de-serialize --> Object Model -- represents --> Graphic

 If the design is right, I see no issues doing this.


> At the moment, we are focusing on completing the mediators and
> improving look and feel of the editor.
>
> Review is scheduled for this Wednesday (01/02/2012) and we will be
> able to give a pack for testing after that. At the moment, this editor is
> not being connected with C-App concepts (i.e it is there as a separate
> feature where users can create a synapse configuration).
>
> Regards,
> Chathuri
>
>
>
> On Sun, Jan 29, 2012 at 4:21 PM, Viraj Rajaguru wrote:
>
>> Hi,
>>
>> Fixes for the above mentioned issues will be available in "Overall
>> Milestone Plan CS 2.0.0" [1]. Some fixes are already done.
>>
>> We do not have the reverse engineering support yet.
>>
>> We are supporting following mediators.
>>
>>- Log Mediator
>>- Drop Mediator
>>- Property Mediator
>>- Enrich Mediator
>>- Send Mediator
>>- Filter Mediator
>>- Switch Mediator
>>- XSLT Mediator
>>- Fault Mediator
>>- Header Mediator
>>- DBLookup Mediator
>>- DBReport Mediator
>>- Clone Mediator
>>- Iterate Mediator
>>- Aggregate Mediator
>>- Callout Mediator
>>- Transaction Mediator
>>- RMSequence Mediator
>>
>> And also graphical implementation of around 12 new mediators have
>> been done. Only serialization logic has to be implemented for them.
>>
>>
>> Thanks,
>>
>> [1]
>> https://docs.google.com/a/wso2.com/document/d/1gTLfLBuEphtHesJf_eSyHNLcisrogEW8Aw4v-2R-iFQ/edit?hl=en_US
>>
>>
>> On Sun, Jan 29, 2012 at 7:22 AM, Samisa Abeysinghe 
>> wrote:
>>
>>> What is the ETA for these fixes? In other words, in which milestone
>>> would these fixes be available?
>>>
>>> Do we have reverse engineering support now? Meaning, can I edit the
>>> source and it will reflect the changes in the graphical view.
>>>
>>> How many meadiators are supported?
>>>
>>> What is the plan for testing?
>>>
>>> On mediators, Jan 25, 2012 at 9:53 AM, Viraj Rajaguru <
>>> vi...@wso2.com> wrote:
>>>
 Hi,

 We had a discussion on ESB Graphical Editor with Hiranya. In this
 discussion we figured out how to overcome existing issues in the 
 editor.
 Followings are the proposed solutions.

- We are not going to represent Local Entries graphically
inside the editor, Instead we put them on the tool palette.Then 
 user can
add them to relevant mediators using th

[Carbon-dev] [Carbon Trunk] email-admin-config.xml is duplicated in products

[Thilina Buddhika]

It is prompted to replace the existing file when extracting the binary.

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

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

Re: [Carbon-dev] [Carbon Trunk] email-admin-config.xml is duplicated in products

[Supun Malinga]

Hi,

On Mon, Feb 6, 2012 at 2:53 PM, Thilina Buddhika  wrote:

> It is prompted to replace the existing file when extracting the binary.
>

I also saw this in AS, bit weird though. When I open the zip and checked
same file was duplicated in same directory(repository/conf) with same name
and size.

thanks,

>
> Thanks,
> Thilina
> --
> Thilina Buddhika
> Associate Technical Lead
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 77 44 88 727
> blog : http://blog.thilinamb.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Supun Malinga,

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

Re: [Carbon-dev] Build has been running 33 hours

[Dhanushka Ranasinghe]

Hi...

Seems like some bind ports not getting released,and we restart the Bamboo

Thank You
Dhanushka



On Mon, Feb 6, 2012 at 6:03 AM, Srinath Perera  wrote:
> Please note the $subject .. something wrong
>
> infra team, could you look at this (build team will help). Please try
> to check a bit weather we can find the problem .. restart will fix
> that but ..
>
> --Srinath
>
> --
> 
> Srinath Perera, Ph.D.
>   Senior Software Architect, WSO2 Inc.
>   Visiting Faculty, University of Moratuwa
>   Member, Apache Software Foundation
>   Research Scientist, Lanka Software Foundation
>   Blog: http://srinathsview.blogspot.com/
>   Photos: http://www.flickr.com/photos/hemapani/
>  Phone: 0772360902



-- 
Dhanushka Ranasinghe,
WSO2 lnc  http://wso2.com
E-mail : dhanush...@wso2.com
Mobile : +94771928269
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Carbon Trunk] email-admin-config.xml is duplicated in products

[Kathiravelu Pradeeban]

Yes, it was reported by Supun last week, and I fixed it. Can you take an
svn up from the products?

Regards,
Pradeeban.

On Mon, Feb 6, 2012 at 2:56 PM, Supun Malinga  wrote:

> Hi,
>
> On Mon, Feb 6, 2012 at 2:53 PM, Thilina Buddhika wrote:
>
>> It is prompted to replace the existing file when extracting the binary.
>>
>
> I also saw this in AS, bit weird though. When I open the zip and checked
> same file was duplicated in same directory(repository/conf) with same name
> and size.
>
> thanks,
>
>>
>> Thanks,
>> Thilina
>> --
>> Thilina Buddhika
>> Associate Technical Lead
>> WSO2 Inc. ; http://wso2.com
>> lean . enterprise . middleware
>>
>> phone : +94 77 44 88 727
>> blog : http://blog.thilinamb.com
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Supun Malinga,
>
> Software Engineer,
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
> email - sup...@wso2.com 
> mobile - 071 56 91 321
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

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

Re: [Carbon-dev] Bootup self test component for carbon

[Afkham Azeez]

Please create a Crucible project to review this component & add me as a
reviewer. I will go through the code & provide feedback. Hope that all the
recommendations from the previous review have been incorporated.

On Mon, Feb 6, 2012 at 12:40 AM, Dileepa Jayakody  wrote:

> Hi All,
>
> The bootup validator's purpose is to validate certain recommended
> configurations/settings at server bootup and give warnings if they are not
> satisfied. This includes JVM configurations (init/max heap, permGen size),
> system configurations such as CPU, RAM, Swap, supported operating systems
> etc.  The component can be extended by adding new validators and specifying
> them in the config-validation.xml in repository/conf. A sample
> config-validation.xml can be found at svn location [1].
>
> The component is committed to Trunk under Revision: 120131 and can be
> found at [2]. It is not yet integrated with the carbon build as the
> component is not yet finalised.
> Suggestions to improve the code/component are most welcome.
>
> Thanks,
> Dileepa
>
> [1]
> https://svn.wso2.org/repos/wso2/trunk/carbon/core/distribution/carbon-home/repository/conf/config-validation.xml
> [2]
> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.core.bootup.validator/
>
>
> On Sat, Feb 4, 2012 at 3:12 AM, Afkham Azeez  wrote:
>
>> No need to complicate stuff.  We have recommend memory settings for
>> production. If somebody is running with lower values we just warn them
>> about it.  That is it.
>>
>> --
>> Afkham Azeez
>> Sent from my phone
>> On Feb 4, 2012 2:01 AM, "Senaka Fernando"  wrote:
>>
>>> Hi all,
>>>
>>> I'm just running through the discussion. Does it make sense to actually
>>> validate memory? I mean, memory settings are defined in
>>> wso2server.sh/bat anyway. And, it "should have" the recommended minimum
>>> values. If someone is setting it lower than expected, they are deliberately
>>> doing that, so is it necessary to validate memory settings?
>>>
>>> Or if your counter argument is to validate whether the OS has enough
>>> memory (as allocated), to run the application, the JVM actually does that
>>> and if there is insufficient memory, it will get back to you. So, can
>>> someone please clarify the necessity?
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> On Tue, Jan 24, 2012 at 1:17 PM, Dileepa Jayakody wrote:
>>>


 On Tue, Jan 24, 2012 at 12:49 PM, Sameera Jayasoma wrote:

> Hi Dileepa,
>
> I got one question. Is there a way to disable this validator? If a use
> wants to execute this once in his system and for all the other restarts, 
> he
> wants to disable this validation step. I guess we need to support this as
> well.
>
> We can do something like below.
>
> 
>
> +1 will add this feature.


> Great work btw,
>
> Thanks,
> Sameera.
>
>
> On Mon, Jan 23, 2012 at 7:19 AM, Afkham Azeez  wrote:
>
>> Most of our deployments are on Linux. It is ok to go with OS specific
>> commands. Please schedule a review.
>>
>> --
>> Afkham Azeez
>> Sent from my phone
>> On Jan 23, 2012 12:37 PM, "Dileepa Jayakody" 
>> wrote:
>>
>>> Dear all,
>>>
>>> The bootup validator component now can be configured with custom
>>> Configuration Validators and Data Collectors as shown in the below 
>>> sample
>>> [1]. A Data collector basically retrieves system information using some
>>> mechanism (OS independent library etc.) and the collected data can be 
>>> used
>>> for the validation process by Configuration Validators.
>>>
>>> In HWDataCollector, system hardware related data such as CPU
>>> frequency, physical memory are collected; For this I have used a 3rd 
>>> party
>>> library named JavaSysMon [2]. The initial attempt was to use SIGAR API, 
>>> but
>>> it was unsuccessful as I had issues with loading native libraries of it.
>>> JavaSysMon seems to be a very good alternative for this requirement.
>>>
>>> Last few days I was looking at ways of retrieving the number of open
>>> file handles as per a requirement of the bootup validator component [3].
>>> But AFAIU listing open files is OS dependent and cannot be achieved 
>>> through
>>> regular Java APIs.
>>> For example in Linux the command to list open files for a particular
>>> process is: lsof -p 
>>> Does anybody have an idea of retrieving the number of open file
>>> handles in Java? The only mechanism I can think of, at the moment is to 
>>> use
>>> Runtime.getRuntime().exec("the cmd to list open files"); But this
>>> doesn't look like the smoothest solution for this, does anybody have a
>>> better idea?
>>> Appreciate your views on this.
>>>
>>> Thanks,
>>> Dileepa
>>>
>>> [1]Sample  config_recommendations.xml to configure bootup validator:
>>> 
>>> 
>>> 
>>> >> class="org.wso2

[Carbon-dev] WSO2 Committers += Nirmal Fernando

[Dimuthu Leelarathne]

Hi Nirmal,

Congratulations!

It is with great pleasure that we welcome you as a WSO2 committer. Thank
you for your contributions.

thanks and best regards,
Dimuthu

-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

[Carbon-dev] WSO2 Committers += Ajanthan Balachandran

[Dimuthu Leelarathne]

Hi Ajanthan,

Congratulations!

It is with great pleasure that we welcome you as a WSO2 committer. Thank
you for your contributions.

thanks and best regards,
Dimuthu

-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon

[Amila Suriarachchi]

On Mon, Feb 6, 2012 at 12:57 PM, Sameera Jayasoma  wrote:

> I agree that the orbits project should not be a part of the Carbon or
> Carbon based products. Therefore we can make it a top level project, say
> carbon-orbits. But I am not sure whether we need to remove dependencies
> from the carbon svn project. It will complicate things. When we release
> Carbon core, we need to release only the dependencies of Carbon. Therefore
> we need to have a separation of dependencies.


What I thought was not the dependencies as a whole. we don't need a new
dependency version for each carbon core release.

Lets say we did carbon 3.0.0 on axis2 1.6.1.wso2v1.

Then we can either do the carbon 4.0.0 on axis2 1.6.1.wsov1 or v2.

in the former case we don't need to do any axis2 release. But for latter
case we can only release axis2 1.6.1.wso2v2.

Same way for the components. if the dependency is not part of carbon core,
then new release version can be done and release the component.

if the dependencies you have mentioned only pointing to the such newer
versions both do the same.

thanks,
Amila.


> IMV, service-stubs are part of the project. And aslo they are still
> undergoing changes. Therefore I would consider keeping the service-stubs
> separately in each of the projects. Please comment, if you have different
> views.
>

> Here is revised svn structure based on the received comments.
>
> carbon-orbits
>
> carbon
> |--dependencies
>|--orbits (To wrap dependencies as orbit bundles. These cannot be
> added to the top level carbon-orbits project. )
> |--service-stubs
> |--core (core set of bundles.)
> |--features (Carbon core features)
> |--product (Carbon product)
>
> X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva
> once mentioned this name. :) )
> |--dependencies
>|--orbits  (To wrap dependencies as orbit bundles. These cannot be
> added to the top level carbon-orbits project. )
> |--service-stubs
> |--components
> |--features
> |--products
>
>
> Thanks,
> Sameera
>
> On Sun, Feb 5, 2012 at 11:50 AM, Amila Suriarachchi wrote:
>
>> I think first we need to remove the dependencies and orbit from the
>> carbon structure since they have nothing to do with carbon. Simply they
>> produce a set of
>> third party osgi bundles to be used with carbon.
>>
>> Same thing may be applied to service stubs since they only depend on the
>> wsdl version. we can increment the service stubs version when the wsdl
>> version or axis2 version changes (if required).
>>
>> for carbon we can have the structure you have suggested.
>>
>> If we think carbon components and features as independent entities, then
>> they can have an independent truck branches etc .. Same thing
>> can be done with products. Products can have its own trunk and branches
>> and branch can always refer to released feature versions.
>>
>> But this model can lead to complications when installing other features
>> to different products.
>>
>> thanks,
>> Amila.
>>
>>
>> On Sat, Feb 4, 2012 at 8:15 PM, Tharindu Mathew wrote:
>>
>>> ++1, for the execution
>>>
>>> On Sat, Feb 4, 2012 at 5:57 PM, Senaka Fernando  wrote:
>>>
 Hi Sameera, Pradeep,

 +1, but X should probably be a name of a derivative/allotrope of
 Carbon (like Diamond or Graphite) which makes our code names more
 meaningful.

 I really like the idea of having two-levels of dependencies and orbits
 very much, which simplifies the effort of doing a carbon release and
 sticking to that. Carbon must be just like the Linux kernel, and it can
 have its own release schedule.

 Please also note that carbon should continue to have a concept of
 service-stubs which can be reused by other components, and should also have
 an integration area.

 Thanks,
 Senaka.

 On Sat, Feb 4, 2012 at 5:16 PM, Pradeep Fernando wrote:

> +1
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


 --
 *Senaka Fernando*
 Product Manager - WSO2 Governance Registry;
 Associate Technical Lead; WSO2 Inc.; http://wso2.com*
 Member; Apache Software Foundation; http://apache.org

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

 *
 Lean . Enterprise . Middleware


 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Regards,
>>>
>>> Tharindu
>>>
>>> blog: http://mackiemathew.com/
>>> M: +9459908
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Amila Su

Re: [Carbon-dev] WSO2 Committers += Nirmal Fernando

[Nirmal Fernando]

Hi Dimuthu,

On Mon, Feb 6, 2012 at 3:03 PM, Dimuthu Leelarathne wrote:

> Hi Nirmal,
>
> Congratulations!
>

Thanks!

>
> It is with great pleasure that we welcome you as a WSO2 committer. Thank
> you for your contributions.
>

It's a great privilege for me!! :)


> thanks and best regards,
> Dimuthu
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 

Thanks & regards,
Nirmal

Software Engineer- Platform, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] WSO2 Committers += Ajanthan Balachandran

[Ajanthan Balachandran]

On Mon, Feb 6, 2012 at 3:06 PM, Dimuthu Leelarathne wrote:

> Hi Ajanthan,
>
> Congratulations!
>
> It is with great pleasure that we welcome you as a WSO2 committer. Thank
> you for your contributions.
>
> thanks and best regards,
> Dimuthu
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
Thank You!!


-- 
ajanthan
-- 
Ajanthan Balachandiran
Software Engineer; WSO2, Inc.;  http://wso2.com/
email: ajanthan @wso2.com; cell: +94775581497
blog: http://bkayts.blogspot.com/

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

Re: [Carbon-dev] Bootup self test component for carbon

[Dileepa Jayakody]

Hi Azeez,

Created a crucible project : https://wso2.org/crucible/cru/COMPONENT-70
And added you as a reviewer.

Thanks,
Dileepa

On Mon, Feb 6, 2012 at 3:03 PM, Afkham Azeez  wrote:

> Please create a Crucible project to review this component & add me as a
> reviewer. I will go through the code & provide feedback. Hope that all the
> recommendations from the previous review have been incorporated.
>
>
> On Mon, Feb 6, 2012 at 12:40 AM, Dileepa Jayakody wrote:
>
>> Hi All,
>>
>> The bootup validator's purpose is to validate certain recommended
>> configurations/settings at server bootup and give warnings if they are not
>> satisfied. This includes JVM configurations (init/max heap, permGen size),
>> system configurations such as CPU, RAM, Swap, supported operating systems
>> etc.  The component can be extended by adding new validators and specifying
>> them in the config-validation.xml in repository/conf. A sample
>> config-validation.xml can be found at svn location [1].
>>
>> The component is committed to Trunk under Revision: 120131 and can be
>> found at [2]. It is not yet integrated with the carbon build as the
>> component is not yet finalised.
>> Suggestions to improve the code/component are most welcome.
>>
>> Thanks,
>> Dileepa
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/trunk/carbon/core/distribution/carbon-home/repository/conf/config-validation.xml
>> [2]
>> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.core.bootup.validator/
>>
>>
>> On Sat, Feb 4, 2012 at 3:12 AM, Afkham Azeez  wrote:
>>
>>> No need to complicate stuff.  We have recommend memory settings for
>>> production. If somebody is running with lower values we just warn them
>>> about it.  That is it.
>>>
>>> --
>>> Afkham Azeez
>>> Sent from my phone
>>> On Feb 4, 2012 2:01 AM, "Senaka Fernando"  wrote:
>>>
 Hi all,

 I'm just running through the discussion. Does it make sense to actually
 validate memory? I mean, memory settings are defined in
 wso2server.sh/bat anyway. And, it "should have" the recommended
 minimum values. If someone is setting it lower than expected, they are
 deliberately doing that, so is it necessary to validate memory settings?

 Or if your counter argument is to validate whether the OS has enough
 memory (as allocated), to run the application, the JVM actually does that
 and if there is insufficient memory, it will get back to you. So, can
 someone please clarify the necessity?

 Thanks,
 Senaka.

 On Tue, Jan 24, 2012 at 1:17 PM, Dileepa Jayakody wrote:

>
>
> On Tue, Jan 24, 2012 at 12:49 PM, Sameera Jayasoma 
> wrote:
>
>> Hi Dileepa,
>>
>> I got one question. Is there a way to disable this validator? If a
>> use wants to execute this once in his system and for all the other
>> restarts, he wants to disable this validation step. I guess we need to
>> support this as well.
>>
>> We can do something like below.
>>
>> 
>>
>> +1 will add this feature.
>
>
>> Great work btw,
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Mon, Jan 23, 2012 at 7:19 AM, Afkham Azeez  wrote:
>>
>>> Most of our deployments are on Linux. It is ok to go with OS
>>> specific commands. Please schedule a review.
>>>
>>> --
>>> Afkham Azeez
>>> Sent from my phone
>>> On Jan 23, 2012 12:37 PM, "Dileepa Jayakody" 
>>> wrote:
>>>
 Dear all,

 The bootup validator component now can be configured with custom
 Configuration Validators and Data Collectors as shown in the below 
 sample
 [1]. A Data collector basically retrieves system information using some
 mechanism (OS independent library etc.) and the collected data can be 
 used
 for the validation process by Configuration Validators.

 In HWDataCollector, system hardware related data such as CPU
 frequency, physical memory are collected; For this I have used a 3rd 
 party
 library named JavaSysMon [2]. The initial attempt was to use SIGAR 
 API, but
 it was unsuccessful as I had issues with loading native libraries of 
 it.
 JavaSysMon seems to be a very good alternative for this requirement.

 Last few days I was looking at ways of retrieving the number of
 open file handles as per a requirement of the bootup validator 
 component
 [3]. But AFAIU listing open files is OS dependent and cannot be 
 achieved
 through regular Java APIs.
 For example in Linux the command to list open files for a
 particular process is: lsof -p 
 Does anybody have an idea of retrieving the number of open file
 handles in Java? The only mechanism I can think of, at the moment is 
 to use
 Runtime.getRuntime().exec("the cmd to list open files"); Bu

Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon

[Dimuthu Leelarathne]

Hi all,

+1.

When installing other features to different products, it should mention the
carbon core version. Currently, the carbon core is the intersection of
products, so there is no problem at all. But if we go ahead with minimizing
carbon-core it can be tricky to handle. Just had an offline chat with
Sameera, and according to him P2 handles it nicely.

thanks,
dimuthu

On Mon, Feb 6, 2012 at 8:24 AM, Sumedha Rubasinghe  wrote:

> +1 for the idea. B4 doing the actual change, how about running through
> different scenarios (like Amila mentioned) - like how we did for branching
> approach. Figuring out problems later would be costly in terms of time.
>
> /sumedha
>
> On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma  wrote:
>
>> *Objective*:
>> Make Carbon core a top level project in WSO2 trunk. At the moment
>> complete Carbon platform code lies under
>> https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its
>> own problems.
>>
>> *Motivations*:
>> 1) Carbon core can be treated as a separate product which has its own
>> dependencies, orbit and Carbon core can be released independently of other
>> Carbon components, products.
>> 2) To ensure that the Carbon based products can depend on a stable, well
>> tested and released version of Carbon instead of the Carbon trunk.
>> 3) This will also ensure the stability of the Carbon based products,
>> because they are no longer depend on the Carbon trunk which might undergo
>> drastic changes time to time.
>>
>> *Execution*:
>> Here is my proposal.
>> 1) We need to create two top level directories for Carbon and for
>> components, features and Carbon based products. Sample structure is shown
>> below.
>>
>> carbon
>> |--dependencies
>> |--orbits
>> |--core (core set of bundles.)
>> |--features (Carbon core features)
>> |--product (Carbon product)
>>
>> X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva
>> once mentioned this name. :) )
>> |--dependencies
>> |--orbits
>> |--components
>> |--features
>> |--products
>>
>> 2) In order to change the existing svn structure to a structure like
>> above, we need to hold all the commits, say for two to three days and
>> restructure the SVN, test properly and release for commits.
>>
>> Please feel free to comment.
>>
>> Thanks,
>> Sameera.
>>
>> --
>> Sameera Jayasoma
>> Technical Lead and Product Manager, WSO2 Carbon
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> /sumedha
> +94 773017743
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

Re: [Carbon-dev] [Carbon Trunk] email-admin-config.xml is duplicated in products

[Thilina Buddhika]

Thanks Pradeeban, I will take an update and see.

Thanks,
Thilina

On Mon, Feb 6, 2012 at 2:59 PM, Kathiravelu Pradeeban wrote:

> Yes, it was reported by Supun last week, and I fixed it. Can you take an
> svn up from the products?
>
> Regards,
> Pradeeban.
>
>
> On Mon, Feb 6, 2012 at 2:56 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> On Mon, Feb 6, 2012 at 2:53 PM, Thilina Buddhika wrote:
>>
>>> It is prompted to replace the existing file when extracting the binary.
>>>
>>
>> I also saw this in AS, bit weird though. When I open the zip and checked
>> same file was duplicated in same directory(repository/conf) with same name
>> and size.
>>
>> thanks,
>>
>>>
>>> Thanks,
>>> Thilina
>>> --
>>> Thilina Buddhika
>>> Associate Technical Lead
>>> WSO2 Inc. ; http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> phone : +94 77 44 88 727
>>> blog : http://blog.thilinamb.com
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>> email - sup...@wso2.com 
>> mobile - 071 56 91 321
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Kathiravelu Pradeeban.
> Software Engineer.
> Cloud Technologies Team.
> WSO2 Inc.
>
> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
> M: +94 776 477 976
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-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
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Build has been running 33 hours

[Srinath Perera]

is it ports while running tests or something in Bamboo ?

--Srinath

On Mon, Feb 6, 2012 at 2:58 PM, Dhanushka Ranasinghe
 wrote:
> Hi...
>
> Seems like some bind ports not getting released,and we restart the Bamboo
>
> Thank You
> Dhanushka
>
>
>
> On Mon, Feb 6, 2012 at 6:03 AM, Srinath Perera  wrote:
>> Please note the $subject .. something wrong
>>
>> infra team, could you look at this (build team will help). Please try
>> to check a bit weather we can find the problem .. restart will fix
>> that but ..
>>
>> --Srinath
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>>   Photos: http://www.flickr.com/photos/hemapani/
>>  Phone: 0772360902
>
>
>
> --
> Dhanushka Ranasinghe,
> WSO2 lnc  http://wso2.com
> E-mail : dhanush...@wso2.com
> Mobile : +94771928269



-- 

Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] WSO2 Committers += Lakmali

[Anjana Fernando]

Hi Lakmali,

Congratulations and welcome aboard as a WSO2 Committer. Keep up the good
work.

Cheers,
Anjana.

-- 
*Anjana Fernando*
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] WSO2 Committers += Shelan

[Anjana Fernando]

Hi Shelan,

Congratulations and welcome aboard as a WSO2 Committer. Thank you for your
contributions!.

Cheers,
Anjana.
-- 
*Anjana Fernando*
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] WSO2 Committers += Lakmali

[Lakmali Baminiwatta]

Thanks! It is my great pleasure to become a WSO2 Committer and will give my
best contribution in future.

Thanks,
Lakmali

On Mon, Feb 6, 2012 at 4:57 PM, Anjana Fernando  wrote:

> Hi Lakmali,
>
> Congratulations and welcome aboard as a WSO2 Committer. Keep up the good
> work.
>
> Cheers,
> Anjana.
>
> --
> *Anjana Fernando*
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

Re: [Carbon-dev] Build has been running 33 hours

[Dhanushka Ranasinghe]

Hi...



We went via the bamoo log , but couldn't find out any facts to suggest
that bamboo hang cause by the something in bamboo. When bamboo on full
operational state its consuming more than 90% of the RAM space, and
only few left to carry out the system operations.This maybe the reason
for bamboo  port to get freeze.


Thank you
Dhanushka

On Mon, Feb 6, 2012 at 4:16 PM, Srinath Perera  wrote:
> is it ports while running tests or something in Bamboo ?
>
> --Srinath
>
> On Mon, Feb 6, 2012 at 2:58 PM, Dhanushka Ranasinghe
>  wrote:
>> Hi...
>>
>> Seems like some bind ports not getting released,and we restart the Bamboo
>>
>> Thank You
>> Dhanushka
>>
>>
>>
>> On Mon, Feb 6, 2012 at 6:03 AM, Srinath Perera  wrote:
>>> Please note the $subject .. something wrong
>>>
>>> infra team, could you look at this (build team will help). Please try
>>> to check a bit weather we can find the problem .. restart will fix
>>> that but ..
>>>
>>> --Srinath
>>>
>>> --
>>> 
>>> Srinath Perera, Ph.D.
>>>   Senior Software Architect, WSO2 Inc.
>>>   Visiting Faculty, University of Moratuwa
>>>   Member, Apache Software Foundation
>>>   Research Scientist, Lanka Software Foundation
>>>   Blog: http://srinathsview.blogspot.com/
>>>   Photos: http://www.flickr.com/photos/hemapani/
>>>  Phone: 0772360902
>>
>>
>>
>> --
>> Dhanushka Ranasinghe,
>> WSO2 lnc  http://wso2.com
>> E-mail : dhanush...@wso2.com
>> Mobile : +94771928269
>
>
>
> --
> 
> Srinath Perera, Ph.D.
>   Senior Software Architect, WSO2 Inc.
>   Visiting Faculty, University of Moratuwa
>   Member, Apache Software Foundation
>   Research Scientist, Lanka Software Foundation
>   Blog: http://srinathsview.blogspot.com/
>   Photos: http://www.flickr.com/photos/hemapani/
>  Phone: 0772360902



-- 
Dhanushka Ranasinghe,
WSO2 lnc  http://wso2.com
E-mail : dhanush...@wso2.com
Mobile : +94771928269
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] WSO2 Committers += Shelan

[Shelan Perera]

Hi,

On Mon, Feb 6, 2012 at 5:01 PM, Anjana Fernando  wrote:

> Hi Shelan,
>
> Congratulations and welcome aboard as a WSO2 Committer. Thank you for your
> contributions!.
>

Thank you very much and hoping to contribute more to the success story. :)

Regards,


>
> Cheers,
> Anjana.
> --
> *Anjana Fernando*
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Shelan Perera*

Software Engineer
**
*WSO2, Inc. : wso2.com*
lean.enterprise.middleware.

*Home Page*  :shelan.org
*Blog* : blog.shelan.org
*Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
*Twitter* :https://twitter.com/#!/shelan

*Mobile*  : +94 772 604 402
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Enabling Broker component to support all JMS brokers

[Suhothayan Sriskandarajah]

On Mon, Feb 6, 2012 at 12:34 PM, Suhothayan Sriskandarajah wrote:

>
> Currently Broker component only supports Qpid broker and it doesn't have
> the ability to send messages to other JMS brokers.
> This is because the provider url used to create the connection is
> programmatically build using the username, password, ip address, port and
> virtual machine name.
>
> Now I'm is the process of extending Broker's functionality to support
> ActiveMQ.
> In this process I can either programmatically build the provider url of
> the ActiveMQ or I can generalize the process by asking the user to add the
> provider url itself.
> In both cases users need to add the relevant broker jars (activemq or
> other ) to the libs.
>
> Here since we are shipping Qpid I thought it will be appropriate for the
> user to have two UIs, one Qpid specific and the other a general JMS UI
> which will ask for prover url and JNDI class name.
>
> Please give your ideas on this approach
>
> I have attached the patch to the Jira[1]

Thanks
Suho

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

Thanks
> Suho
>
>
> --
> *S. Suhothayan
> *
> Software Engineer
>  *WSO2, Inc. *http://wso2.com
> lean.enterprise.middleware.
>
> *email: **s...@wso2.com* * cell: (+94) 779 756 757
> blog: **http://suhothayan.blogspot.com/* 
> *
> twitter: **http://twitter.com/suhothayan* *
> linked-in: **http://lk.linkedin.com/in/suhothayan*
> *
> *
>
>


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

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

[Carbon-dev] Cannot build latest svn trunk carbon core

[Samisa Abeysinghe]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 10.774s
[INFO] Finished at: Mon Feb 06 18:08:23 IST 2012
[INFO] Final Memory: 47M/981M
[INFO]

[ERROR] Failed to execute goal on project org.wso2.carbon.base: Could not
resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.base:jar:4.0.0-SNAPSHOT: Failed to collect
dependenc
ies for [org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1
(compile), org.wso2.carbon:org.wso2.carbon.logging:jar:4.0.0-SNAPSHOT
(compile), org.wso2.carbon:org.wso2.carbon.queuing:jar:
4.0.0-SNAPSHOT (compile),
org.wso2.securevault:org.wso2.securevault:jar:1.0.0 (compile),
org.wso2.carbon:org.wso2.carbon.securevault:jar:4.0.0-SNAPSHOT (compile),
javax.servlet:servlet-api:ja
r:2.4 (compile)]: Failed to read artifact descriptor for
org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1: Failure to find
org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in http:/
/maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local
repository, resolution will not be reattempted until the update interval of
wso2-nexus has elapsed or updates are for
ced -> [Help 1]
[ERROR]

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Urgent - Builds Broken

[Samisa Abeysinghe]

OK, though Bamboo was successful, I was unable to build Carbon core :(

On Mon, Feb 6, 2012 at 4:50 AM, Samisa Abeysinghe  wrote:

> It is good to see green back on the builder. :)
>
> Thanks for all the hard work folks...
>
>
> On Wed, Feb 1, 2012 at 10:39 AM, Srinath Perera  wrote:
>
>> Actually we are moving the build to SL as SVN is in LK. Now if we start
>> building a clean repo from SL it will take forever.
>>
>> However, we we can have a SVN repo in LK as well, then things are
>> different.
>>
>> --Srinath
>>
>>
>> On Wed, Feb 1, 2012 at 9:46 AM, Kasun Indrasiri  wrote:
>>
>>>
>>>
>>> On Wed, Feb 1, 2012 at 9:43 AM, Hiranya Jayathilaka wrote:
>>>


 On Wed, Feb 1, 2012 at 7:08 AM, Srinath Perera wrote:

> It does not .. it will take longer (now it take about 4 hours)
>
> We can start doing that if needed?
>

 I think we need it. Until we do that all these small errors will go
 unnoticed and a new user can always run into issues building the trunk.


>>> +1.
>>> We should build with clean repo.
>>>

> --Srinath
>
> On Tue, Jan 31, 2012 at 10:34 PM, Hiranya Jayathilaka <
> hiranya...@gmail.com> wrote:
>
>> I'm in the process of setting up my dev environment in a new laptop.
>> So I installed Java, Maven etc, took a fresh checkout from the trunk and
>> started a build. Ran into issues almost immediately. Some of the problems
>> were quite obvious too, like wrong relative paths in pom files. I'm 
>> fixing
>> these issues locally and continuing to build. I wonder why these problems
>> do not show up in the builder machine. Doesn't it build with a clean 
>> repo?
>>
>> Thanks,
>> Hiranya
>>
>>
>> On Tue, Jan 31, 2012 at 9:25 PM, Srinath Perera wrote:
>>
>>> Sorry I mean to say .. Test cases were passing until then
>>>
>>> On Tue, Jan 31, 2012 at 9:24 PM, Srinath Perera 
>>> wrote:
>>> > Hi Samisa,
>>> >
>>> > Onces we moved the SVN to LK, it look like build get to crazy
>>> state.
>>> > It has been running for 3 days before it was killed today AFAIK.
>>> Not
>>> > sure what the solution can be.
>>> >
>>> > Test was passing until then .. but build failure earlier was due to
>>> > assembly errors.
>>> >
>>> > --Srinath
>>> >
>>> > On Tue, Jan 31, 2012 at 9:04 PM, Samisa Abeysinghe <
>>> sam...@wso2.com> wrote:
>>> >> Folks, the build has been broken for more than a week, and I see
>>> that almost
>>> >> 20 back to back builds broken.
>>> >>
>>> >> To make matters worst, I see that people keep on adding code -
>>> not sure how
>>> >> they are testing these commits if the build is broken.
>>> >>
>>> >> It seems that we need a scrum on the build again...
>>> >>
>>> >> Thanks,
>>> >> Samisa...
>>> >>
>>> >> Samisa Abeysinghe
>>> >> VP Engineering
>>> >> WSO2 Inc.
>>> >> http://wso2.com
>>> >> http://wso2.org
>>> >>
>>> >>
>>> >> ___
>>> >> Carbon-dev mailing list
>>> >> Carbon-dev@wso2.org
>>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > 
>>> > Srinath Perera, Ph.D.
>>> >http://www.cs.indiana.edu/~hperera/
>>> >http://srinathsview.blogspot.com/
>>>
>>>
>>>
>>> --
>>> 
>>> Srinath Perera, Ph.D.
>>>http://www.cs.indiana.edu/~hperera/
>>>http://srinathsview.blogspot.com/
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> 
> Srinath Perera, Ph.D.
>   Senior Software Architect, WSO2 Inc.
>   Visiting Faculty, University of Moratuwa
>   Member, Apache Software Foundation
>   Research Scientist, Lanka Software Foundation
>   Blog: http://srinathsview.blogspot.com/
>   Photos: http://www.flickr.com/photos/hemapani/
>  Phone: 0772360902
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


 --
 Hiranya Jayathilaka
 Associate Technical Lead;
 WSO2 Inc.;  http://wso2.org
 E-m

Re: [Carbon-dev] Cannot build latest svn trunk carbon core

[Dileepa Jayakody]

Hi,

This is due to some dependency artifacts not been downloaded from
maven.wso2.org/nexus/content/groups/wso2-public/
I think this happens because LK cache repo is not yet synced properly.

Regards,
Dileepa

On Mon, Feb 6, 2012 at 6:09 PM, Samisa Abeysinghe  wrote:

> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 10.774s
> [INFO] Finished at: Mon Feb 06 18:08:23 IST 2012
> [INFO] Final Memory: 47M/981M
> [INFO]
> 
> [ERROR] Failed to execute goal on project org.wso2.carbon.base: Could not
> resolve dependencies for project
> org.wso2.carbon:org.wso2.carbon.base:jar:4.0.0-SNAPSHOT: Failed to collect
> dependenc
> ies for [org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1
> (compile), org.wso2.carbon:org.wso2.carbon.logging:jar:4.0.0-SNAPSHOT
> (compile), org.wso2.carbon:org.wso2.carbon.queuing:jar:
> 4.0.0-SNAPSHOT (compile),
> org.wso2.securevault:org.wso2.securevault:jar:1.0.0 (compile),
> org.wso2.carbon:org.wso2.carbon.securevault:jar:4.0.0-SNAPSHOT (compile),
> javax.servlet:servlet-api:ja
> r:2.4 (compile)]: Failed to read artifact descriptor for
> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1: Failure to find
> org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in http:/
> /maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local
> repository, resolution will not be reattempted until the update interval of
> wso2-nexus has elapsed or updates are for
> ced -> [Help 1]
> [ERROR]
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

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

Re: [Carbon-dev] Enabling Broker component to support all JMS brokers

[Paul Fremantle]

Suho

What is the use case for this? Users can already use ActiveMQ with the ESB
and other products via the JMS transport. There was (I think) a lot more
work involved in adding QPid as a broker including tying into the Identity
/ User Manager as well as support for Multi-tenancy.

Paul

On 6 February 2012 07:04, Suhothayan Sriskandarajah  wrote:

>
> Currently Broker component only supports Qpid broker and it doesn't have
> the ability to send messages to other JMS brokers.
> This is because the provider url used to create the connection is
> programmatically build using the username, password, ip address, port and
> virtual machine name.
>
> Now I'm is the process of extending Broker's functionality to support
> ActiveMQ.
> In this process I can either programmatically build the provider url of
> the ActiveMQ or I can generalize the process by asking the user to add the
> provider url itself.
> In both cases users need to add the relevant broker jars (activemq or
> other ) to the libs.
>
> Here since we are shipping Qpid I thought it will be appropriate for the
> user to have two UIs, one Qpid specific and the other a general JMS UI
> which will ask for prover url and JNDI class name.
>
> Please give your ideas on this approach
>
> Thanks
> Suho
>
>
> --
> *S. Suhothayan
> *
> Software Engineer
>  *WSO2, Inc. *http://wso2.com
> lean.enterprise.middleware.
>
> *email: **s...@wso2.com* * cell: (+94) 779 756 757
> blog: **http://suhothayan.blogspot.com/* 
> *
> twitter: **http://twitter.com/suhothayan* *
> linked-in: **http://lk.linkedin.com/in/suhothayan*
> *
> *
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

UK: +44 207 096 0336
US: +1 646 595 7614

blog: http://pzf.fremantle.org
twitter.com/pzfreo
p...@wso2.com

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Enabling Broker component to support all JMS brokers

[Danushka Menikkumbura]

Correct!. In fact we opted for Qpid taking lot of things into consideration
leaving ActiveMQ behind.

Danushka

On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle  wrote:

> Suho
>
> What is the use case for this? Users can already use ActiveMQ with the ESB
> and other products via the JMS transport. There was (I think) a lot more
> work involved in adding QPid as a broker including tying into the Identity
> / User Manager as well as support for Multi-tenancy.
>
> Paul
>
> On 6 February 2012 07:04, Suhothayan Sriskandarajah  wrote:
>
>>
>> Currently Broker component only supports Qpid broker and it doesn't have
>> the ability to send messages to other JMS brokers.
>> This is because the provider url used to create the connection is
>> programmatically build using the username, password, ip address, port and
>> virtual machine name.
>>
>> Now I'm is the process of extending Broker's functionality to support
>> ActiveMQ.
>> In this process I can either programmatically build the provider url of
>> the ActiveMQ or I can generalize the process by asking the user to add the
>> provider url itself.
>> In both cases users need to add the relevant broker jars (activemq or
>> other ) to the libs.
>>
>> Here since we are shipping Qpid I thought it will be appropriate for the
>> user to have two UIs, one Qpid specific and the other a general JMS UI
>> which will ask for prover url and JNDI class name.
>>
>> Please give your ideas on this approach
>>
>> Thanks
>> Suho
>>
>>
>> --
>> *S. Suhothayan
>> *
>> Software Engineer
>>  *WSO2, Inc. *http://wso2.com
>> lean.enterprise.middleware.
>>
>> *email: **s...@wso2.com* * cell: (+94) 779 756 757
>> blog: **http://suhothayan.blogspot.com/*
>> *
>> twitter: **http://twitter.com/suhothayan* 
>> *
>> linked-in: **http://lk.linkedin.com/in/suhothayan*
>> *
>> *
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Cannot build latest svn trunk carbon core

[Samisa Abeysinghe]

On Mon, Feb 6, 2012 at 6:20 PM, Dileepa Jayakody  wrote:

> Hi,
>
> This is due to some dependency artifacts not been downloaded from
> maven.wso2.org/nexus/content/groups/wso2-public/
> I think this happens because LK cache repo is not yet synced properly.
>

Is there any workaround?


>
> Regards,
> Dileepa
>
> On Mon, Feb 6, 2012 at 6:09 PM, Samisa Abeysinghe  wrote:
>
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 10.774s
>> [INFO] Finished at: Mon Feb 06 18:08:23 IST 2012
>> [INFO] Final Memory: 47M/981M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project org.wso2.carbon.base: Could not
>> resolve dependencies for project
>> org.wso2.carbon:org.wso2.carbon.base:jar:4.0.0-SNAPSHOT: Failed to collect
>> dependenc
>> ies for [org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1
>> (compile), org.wso2.carbon:org.wso2.carbon.logging:jar:4.0.0-SNAPSHOT
>> (compile), org.wso2.carbon:org.wso2.carbon.queuing:jar:
>> 4.0.0-SNAPSHOT (compile),
>> org.wso2.securevault:org.wso2.securevault:jar:1.0.0 (compile),
>> org.wso2.carbon:org.wso2.carbon.securevault:jar:4.0.0-SNAPSHOT (compile),
>> javax.servlet:servlet-api:ja
>> r:2.4 (compile)]: Failed to read artifact descriptor for
>> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1: Failure to find
>> org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in http:/
>> /maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
>> local repository, resolution will not be reattempted until the update
>> interval of wso2-nexus has elapsed or updates are for
>> ced -> [Help 1]
>> [ERROR]
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Enabling Broker component to support all JMS brokers

[Suhothayan Sriskandarajah]

On Mon, Feb 6, 2012 at 6:32 PM, Danushka Menikkumbura <
danushka.menikkumb...@gmail.com> wrote:

> Correct!. In fact we opted for Qpid taking lot of things into
> consideration leaving ActiveMQ behind.
>
> Danushka
>
>
> On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle  wrote:
>
>> Suho
>>
>> What is the use case for this? Users can already use ActiveMQ with the
>> ESB and other products via the JMS transport. There was (I think) a lot
>> more work involved in adding QPid as a broker including tying into the
>> Identity / User Manager as well as support for Multi-tenancy.
>>
>>
In the current implementation WSO2CEP can only subscribe to a Qpid Broker
and publish its events.
The use case here is to allow WSO2CEP to subscribe to other custom JMS
Brokers other than Qpid, to send and receive messages.

Regards
Suho


Paul
>>
>> On 6 February 2012 07:04, Suhothayan Sriskandarajah wrote:
>>
>>>
>>> Currently Broker component only supports Qpid broker and it doesn't have
>>> the ability to send messages to other JMS brokers.
>>> This is because the provider url used to create the connection is
>>> programmatically build using the username, password, ip address, port and
>>> virtual machine name.
>>>
>>> Now I'm is the process of extending Broker's functionality to support
>>> ActiveMQ.
>>> In this process I can either programmatically build the provider url of
>>> the ActiveMQ or I can generalize the process by asking the user to add the
>>> provider url itself.
>>> In both cases users need to add the relevant broker jars (activemq or
>>> other ) to the libs.
>>>
>>> Here since we are shipping Qpid I thought it will be appropriate for the
>>> user to have two UIs, one Qpid specific and the other a general JMS UI
>>> which will ask for prover url and JNDI class name.
>>>
>>> Please give your ideas on this approach
>>>
>>> Thanks
>>> Suho
>>>
>>>
>>> --
>>> *S. Suhothayan
>>> *
>>> Software Engineer
>>>  *WSO2, Inc. *http://wso2.com
>>> lean.enterprise.middleware.
>>>
>>> *email: **s...@wso2.com* * cell: (+94) 779 756 757
>>> blog: **http://suhothayan.blogspot.com/*
>>> *
>>> twitter: **http://twitter.com/suhothayan*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/suhothayan*
>>> *
>>> *
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> UK: +44 207 096 0336
>> US: +1 646 595 7614
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo
>> p...@wso2.com
>>
>> wso2.com Lean Enterprise Middleware
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

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

Re: [Carbon-dev] Enabling Broker component to support all JMS brokers

[Amila Suriarachchi]

On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle  wrote:

> Suho
>
> What is the use case for this? Users can already use ActiveMQ with the ESB
> and other products via the JMS transport. There was (I think) a lot more
> work involved in adding QPid as a broker including tying into the Identity
> / User Manager as well as support for Multi-tenancy.
>

Here we don't add ActiveMQ as a broker to carbon platform.

This use case comes from the CEP side. This broker refers to the brokers
CEP used to receive events from different real brokers.

Idea is to be able to consume messages publish to a jms topic in an
ActiveMQ broker in an CEP Bucket.

thanks,
Amila.



>
> Paul
>
> On 6 February 2012 07:04, Suhothayan Sriskandarajah  wrote:
>
>>
>> Currently Broker component only supports Qpid broker and it doesn't have
>> the ability to send messages to other JMS brokers.
>> This is because the provider url used to create the connection is
>> programmatically build using the username, password, ip address, port and
>> virtual machine name.
>>
>> Now I'm is the process of extending Broker's functionality to support
>> ActiveMQ.
>> In this process I can either programmatically build the provider url of
>> the ActiveMQ or I can generalize the process by asking the user to add the
>> provider url itself.
>> In both cases users need to add the relevant broker jars (activemq or
>> other ) to the libs.
>>
>> Here since we are shipping Qpid I thought it will be appropriate for the
>> user to have two UIs, one Qpid specific and the other a general JMS UI
>> which will ask for prover url and JNDI class name.
>>
>> Please give your ideas on this approach
>>
>> Thanks
>> Suho
>>
>>
>> --
>> *S. Suhothayan
>> *
>> Software Engineer
>>  *WSO2, Inc. *http://wso2.com
>> lean.enterprise.middleware.
>>
>> *email: **s...@wso2.com* * cell: (+94) 779 756 757
>> blog: **http://suhothayan.blogspot.com/*
>> *
>> twitter: **http://twitter.com/suhothayan* 
>> *
>> linked-in: **http://lk.linkedin.com/in/suhothayan*
>> *
>> *
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Amila Suriarachchi*

Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

phone : +94 71 3082805
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Cannot build latest svn trunk carbon core

[Sameera Jayasoma]

Hi Samisa,

There is a workaround. Can you please comment out the following section
from the  platform pom.xml

default
  
true
  



Then invoke the 'mvn clean install' from the top level. This will allow the
platform pom to be added to the .m2 repo.

Then try to build carbon core.

Thanks,
Sameera.

On Mon, Feb 6, 2012 at 6:47 PM, Samisa Abeysinghe  wrote:

>
>
> On Mon, Feb 6, 2012 at 6:20 PM, Dileepa Jayakody  wrote:
>
>> Hi,
>>
>> This is due to some dependency artifacts not been downloaded from
>> maven.wso2.org/nexus/content/groups/wso2-public/
>> I think this happens because LK cache repo is not yet synced properly.
>>
>
> Is there any workaround?
>
>
>>
>> Regards,
>> Dileepa
>>
>> On Mon, Feb 6, 2012 at 6:09 PM, Samisa Abeysinghe wrote:
>>
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 10.774s
>>> [INFO] Finished at: Mon Feb 06 18:08:23 IST 2012
>>> [INFO] Final Memory: 47M/981M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal on project org.wso2.carbon.base: Could
>>> not resolve dependencies for project
>>> org.wso2.carbon:org.wso2.carbon.base:jar:4.0.0-SNAPSHOT: Failed to collect
>>> dependenc
>>> ies for [org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1
>>> (compile), org.wso2.carbon:org.wso2.carbon.logging:jar:4.0.0-SNAPSHOT
>>> (compile), org.wso2.carbon:org.wso2.carbon.queuing:jar:
>>> 4.0.0-SNAPSHOT (compile),
>>> org.wso2.securevault:org.wso2.securevault:jar:1.0.0 (compile),
>>> org.wso2.carbon:org.wso2.carbon.securevault:jar:4.0.0-SNAPSHOT (compile),
>>> javax.servlet:servlet-api:ja
>>> r:2.4 (compile)]: Failed to read artifact descriptor for
>>> org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1: Failure to find
>>> org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in http:/
>>> /maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
>>> local repository, resolution will not be reattempted until the update
>>> interval of wso2-nexus has elapsed or updates are for
>>> ced -> [Help 1]
>>> [ERROR]
>>>
>>> Thanks,
>>> Samisa...
>>>
>>> Samisa Abeysinghe
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Dileepa Jayakody,
>> Software Engineer, WSO2 Inc.
>> Lean . Enterprise . Middleware
>>
>> Mobile : +94777-857616
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Carbon-dev] Tomcat OSGification - progress update

[Afkham Azeez]

Did you write any code to parse the server.xml file or did Tomcat
automatically parse the file when the location was provided?

On Mon, Feb 6, 2012 at 2:02 AM, Pradeep Fernando  wrote:

> Hi,
>
> I was able to configure the tomcat with tomcat-shipped server.xml file.
> this means we can register connectors Hosts, valves, listeners without
> hard-coding them.
>
> I the current code has some issues related to JNDI. Think this is related
> non-OSGi/OSGi env jar duplication. I need some help to get this done. We
> have to move each and every library that resides under /ib (relevant) to
> plugins.
>
> For the moment i have moved only tomcat related libs.
>
> --Pradeep
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


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

Re: [Carbon-dev] Urgent - Builds Broken

[Afkham Azeez]

Perhaps there are build issues on Windows. We need a Bamboo Windows agent
too.

On Mon, Feb 6, 2012 at 6:11 PM, Samisa Abeysinghe  wrote:

> OK, though Bamboo was successful, I was unable to build Carbon core :(
>
>
> On Mon, Feb 6, 2012 at 4:50 AM, Samisa Abeysinghe  wrote:
>
>> It is good to see green back on the builder. :)
>>
>> Thanks for all the hard work folks...
>>
>>
>> On Wed, Feb 1, 2012 at 10:39 AM, Srinath Perera  wrote:
>>
>>> Actually we are moving the build to SL as SVN is in LK. Now if we start
>>> building a clean repo from SL it will take forever.
>>>
>>> However, we we can have a SVN repo in LK as well, then things are
>>> different.
>>>
>>> --Srinath
>>>
>>>
>>> On Wed, Feb 1, 2012 at 9:46 AM, Kasun Indrasiri  wrote:
>>>


 On Wed, Feb 1, 2012 at 9:43 AM, Hiranya Jayathilaka 
 wrote:

>
>
> On Wed, Feb 1, 2012 at 7:08 AM, Srinath Perera wrote:
>
>> It does not .. it will take longer (now it take about 4 hours)
>>
>> We can start doing that if needed?
>>
>
> I think we need it. Until we do that all these small errors will go
> unnoticed and a new user can always run into issues building the trunk.
>
>
 +1.
 We should build with clean repo.

>
>> --Srinath
>>
>> On Tue, Jan 31, 2012 at 10:34 PM, Hiranya Jayathilaka <
>> hiranya...@gmail.com> wrote:
>>
>>> I'm in the process of setting up my dev environment in a new laptop.
>>> So I installed Java, Maven etc, took a fresh checkout from the trunk and
>>> started a build. Ran into issues almost immediately. Some of the 
>>> problems
>>> were quite obvious too, like wrong relative paths in pom files. I'm 
>>> fixing
>>> these issues locally and continuing to build. I wonder why these 
>>> problems
>>> do not show up in the builder machine. Doesn't it build with a clean 
>>> repo?
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>> On Tue, Jan 31, 2012 at 9:25 PM, Srinath Perera wrote:
>>>
 Sorry I mean to say .. Test cases were passing until then

 On Tue, Jan 31, 2012 at 9:24 PM, Srinath Perera 
 wrote:
 > Hi Samisa,
 >
 > Onces we moved the SVN to LK, it look like build get to crazy
 state.
 > It has been running for 3 days before it was killed today AFAIK.
 Not
 > sure what the solution can be.
 >
 > Test was passing until then .. but build failure earlier was due
 to
 > assembly errors.
 >
 > --Srinath
 >
 > On Tue, Jan 31, 2012 at 9:04 PM, Samisa Abeysinghe <
 sam...@wso2.com> wrote:
 >> Folks, the build has been broken for more than a week, and I see
 that almost
 >> 20 back to back builds broken.
 >>
 >> To make matters worst, I see that people keep on adding code -
 not sure how
 >> they are testing these commits if the build is broken.
 >>
 >> It seems that we need a scrum on the build again...
 >>
 >> Thanks,
 >> Samisa...
 >>
 >> Samisa Abeysinghe
 >> VP Engineering
 >> WSO2 Inc.
 >> http://wso2.com
 >> http://wso2.org
 >>
 >>
 >> ___
 >> Carbon-dev mailing list
 >> Carbon-dev@wso2.org
 >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
 >>
 >
 >
 >
 > --
 > 
 > Srinath Perera, Ph.D.
 >http://www.cs.indiana.edu/~hperera/
 >http://srinathsview.blogspot.com/



 --
 
 Srinath Perera, Ph.D.
http://www.cs.indiana.edu/~hperera/
http://srinathsview.blogspot.com/
 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

>>>
>>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Associate Technical Lead;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>>   Photos: http://www.flickr.com/photos/hemapani/

Re: [Carbon-dev] Tomcat OSGification - progress update

[Supun Malinga]

On Mon, Feb 6, 2012 at 7:05 PM, Afkham Azeez  wrote:

> Did you write any code to parse the server.xml file or did Tomcat
> automatically parse the file when the location was provided?


> On Mon, Feb 6, 2012 at 2:02 AM, Pradeep Fernando  wrote:
>
>> Hi,
>>
>> I was able to configure the tomcat with tomcat-shipped server.xml file.
>> this means we can register connectors Hosts, valves, listeners without
>> hard-coding them.
>>
>> +1

thanks,

> I the current code has some issues related to JNDI. Think this is related
>> non-OSGi/OSGi env jar duplication. I need some help to get this done. We
>> have to move each and every library that resides under /ib (relevant) to
>> plugins.
>>
>> For the moment i have moved only tomcat related libs.
>>
>> --Pradeep
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Supun Malinga,

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

Re: [Carbon-dev] Urgent - Builds Broken

[Charith Dhanushka]

--charith
Sent from my phone

On Feb 6, 2012, at 7:08 PM, Afkham Azeez  wrote:

Perhaps there are build issues on Windows. We need a Bamboo Windows  
agent too.


On Mon, Feb 6, 2012 at 6:11 PM, Samisa Abeysinghe   
wrote:

OK, though Bamboo was successful, I was unable to build Carbon core :(


On Mon, Feb 6, 2012 at 4:50 AM, Samisa Abeysinghe   
wrote:

It is good to see green back on the builder. :)

Thanks for all the hard work folks...


On Wed, Feb 1, 2012 at 10:39 AM, Srinath Perera   
wrote:
Actually we are moving the build to SL as SVN is in LK. Now if we  
start building a clean repo from SL it will take forever.


However, we we can have a SVN repo in LK as well, then things are  
different.


--Srinath


On Wed, Feb 1, 2012 at 9:46 AM, Kasun Indrasiri   
wrote:



On Wed, Feb 1, 2012 at 9:43 AM, Hiranya Jayathilaka  
 wrote:



On Wed, Feb 1, 2012 at 7:08 AM, Srinath Perera   
wrote:

It does not .. it will take longer (now it take about 4 hours)

We can start doing that if needed?

I think we need it. Until we do that all these small errors will go  
unnoticed and a new user can always run into issues building the  
trunk.


+1.
We should build with clean repo.

--Srinath

On Tue, Jan 31, 2012 at 10:34 PM, Hiranya Jayathilaka > wrote:
I'm in the process of setting up my dev environment in a new laptop.  
So I installed Java, Maven etc, took a fresh checkout from the trunk  
and started a build. Ran into issues almost immediately. Some of the  
problems were quite obvious too, like wrong relative paths in pom  
files. I'm fixing these issues locally and continuing to build. I  
wonder why these problems do not show up in the builder machine.  
Doesn't it build with a clean repo?


Thanks,
Hiranya


On Tue, Jan 31, 2012 at 9:25 PM, Srinath Perera   
wrote:

Sorry I mean to say .. Test cases were passing until then

On Tue, Jan 31, 2012 at 9:24 PM, Srinath Perera   
wrote:

> Hi Samisa,
>
> Onces we moved the SVN to LK, it look like build get to crazy state.
> It has been running for 3 days before it was killed today AFAIK. Not
> sure what the solution can be.
>
> Test was passing until then .. but build failure earlier was due to
> assembly errors.
>
> --Srinath
>
> On Tue, Jan 31, 2012 at 9:04 PM, Samisa Abeysinghe  
 wrote:
>> Folks, the build has been broken for more than a week, and I see  
that almost

>> 20 back to back builds broken.
>>
>> To make matters worst, I see that people keep on adding code -  
not sure how

>> they are testing these commits if the build is broken.
>>
>> It seems that we need a scrum on the build again...
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> 
> Srinath Perera, Ph.D.
>http://www.cs.indiana.edu/~hperera/
>http://srinathsview.blogspot.com/



--

Srinath Perera, Ph.D.
   http://www.cs.indiana.edu/~hperera/
   http://srinathsview.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev



--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

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




--

Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902

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




--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

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




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

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



--

Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902

Re: [Carbon-dev] Tomcat OSGification - progress update

[Pradeep Fernando]

Hi,

On Mon, Feb 6, 2012 at 7:05 PM, Afkham Azeez  wrote:

> Did you write any code to parse the server.xml file or did Tomcat
> automatically parse the file when the location was provided?
>

tomcat uses commons digester to configure its components. I used the same
mechanism. It took some time to learn how to use it.

thanks,
--Pradeep



>
> On Mon, Feb 6, 2012 at 2:02 AM, Pradeep Fernando  wrote:
>
>> Hi,
>>
>> I was able to configure the tomcat with tomcat-shipped server.xml file.
>> this means we can register connectors Hosts, valves, listeners without
>> hard-coding them.
>>
>> I the current code has some issues related to JNDI. Think this is related
>> non-OSGi/OSGi env jar duplication. I need some help to get this done. We
>> have to move each and every library that resides under /ib (relevant) to
>> plugins.
>>
>> For the moment i have moved only tomcat related libs.
>>
>> --Pradeep
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Pradeep Fernando
Software Engineer
WSO2 Inc; http://wso2.com/

blog: http://pradeepfernando.blogspot.com/
m: +94776603662
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Enabling Broker component to support all JMS brokers

[Paul Fremantle]

Aha ok that is much clearer :-)

So basically this is a JMS transport for CEP?

Paul

On 6 February 2012 13:25, Amila Suriarachchi  wrote:

>
>
> On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle  wrote:
>
>> Suho
>>
>> What is the use case for this? Users can already use ActiveMQ with the
>> ESB and other products via the JMS transport. There was (I think) a lot
>> more work involved in adding QPid as a broker including tying into the
>> Identity / User Manager as well as support for Multi-tenancy.
>>
>
> Here we don't add ActiveMQ as a broker to carbon platform.
>
> This use case comes from the CEP side. This broker refers to the brokers
> CEP used to receive events from different real brokers.
>
> Idea is to be able to consume messages publish to a jms topic in an
> ActiveMQ broker in an CEP Bucket.
>
> thanks,
> Amila.
>
>
>
>>
>> Paul
>>
>> On 6 February 2012 07:04, Suhothayan Sriskandarajah wrote:
>>
>>>
>>> Currently Broker component only supports Qpid broker and it doesn't have
>>> the ability to send messages to other JMS brokers.
>>> This is because the provider url used to create the connection is
>>> programmatically build using the username, password, ip address, port and
>>> virtual machine name.
>>>
>>> Now I'm is the process of extending Broker's functionality to support
>>> ActiveMQ.
>>> In this process I can either programmatically build the provider url of
>>> the ActiveMQ or I can generalize the process by asking the user to add the
>>> provider url itself.
>>> In both cases users need to add the relevant broker jars (activemq or
>>> other ) to the libs.
>>>
>>> Here since we are shipping Qpid I thought it will be appropriate for the
>>> user to have two UIs, one Qpid specific and the other a general JMS UI
>>> which will ask for prover url and JNDI class name.
>>>
>>> Please give your ideas on this approach
>>>
>>> Thanks
>>> Suho
>>>
>>>
>>> --
>>> *S. Suhothayan
>>> *
>>> Software Engineer
>>>  *WSO2, Inc. *http://wso2.com
>>> lean.enterprise.middleware.
>>>
>>> *email: **s...@wso2.com* * cell: (+94) 779 756 757
>>> blog: **http://suhothayan.blogspot.com/*
>>> *
>>> twitter: **http://twitter.com/suhothayan*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/suhothayan*
>>> *
>>> *
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> UK: +44 207 096 0336
>> US: +1 646 595 7614
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo
>> p...@wso2.com
>>
>> wso2.com Lean Enterprise Middleware
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Amila Suriarachchi*
>
> Software Architect
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 71 3082805
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

UK: +44 207 096 0336
US: +1 646 595 7614

blog: http://pzf.fremantle.org
twitter.com/pzfreo
p...@wso2.com

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #177 was SUCCESSFUL (with 7659 tests). Change made by waruna and thilinab.

[Bamboo]

---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #177 was successful.
---
Code has been updated by waruna, thilinab.
7659 tests in total.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-177/


--
Code Changes
--
thilinab (120153):

>Fixing CARBON-5184 - Applying the patch provided by Suresh.

thilinab (120154):

>Fixing CARBON-7160 - Applying the patch provided by Suresh.

waruna (120155):

>Adding Deadline processing logic



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

Re: [Carbon-dev] Cannot build latest svn trunk carbon core

[Harshana Martin]

On Feb 6, 2012 4:40 AM, "Samisa Abeysinghe"  wrote:
>
> [INFO] BUILD FAILURE
> [INFO]

> [INFO] Total time: 10.774s
> [INFO] Finished at: Mon Feb 06 18:08:23 IST 2012
> [INFO] Final Memory: 47M/981M
> [INFO]

> [ERROR] Failed to execute goal on project org.wso2.carbon.base: Could not
resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.base:jar:4.0.0-SNAPSHOT: Failed to collect
dependenc
> ies for [org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1
(compile), org.wso2.carbon:org.wso2.carbon.logging:jar:4.0.0-SNAPSHOT
(compile), org.wso2.carbon:org.wso2.carbon.queuing:jar:
> 4.0.0-SNAPSHOT (compile),
org.wso2.securevault:org.wso2.securevault:jar:1.0.0 (compile),
org.wso2.carbon:org.wso2.carbon.securevault:jar:4.0.0-SNAPSHOT (compile),
javax.servlet:servlet-api:ja
> r:2.4 (compile)]: Failed to read artifact descriptor for
org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1: Failure to find
org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in http:/
> /maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local
repository, resolution will not be reattempted until the update interval of
wso2-nexus has elapsed or updates are for
> ced -> [Help 1]

This is because you have not started thr.build from root. Therefore mvn
couldn't locate the platform pom in local m2.

Pls start the build from root so that mvn can install it :-)

Thanks.
Harshana
> [ERROR]
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Hadoop Build

[Deependra Ariyadewa]

On Thu, Feb 2, 2012 at 7:13 AM, Srinath Perera  wrote:

> any updates ?


Fixed the build after adding ant.jar to hadoop lib. It works on mac also.

Thanks,

Deependra.

>
>
> On Wed, Feb 1, 2012 at 10:56 AM, Srinath Perera  wrote:
>
>> Wathsala said ivy thing is working ..
>>
>> It failed on my machine through and I asked him to get a third person to
>> try to
>>
>> Deep, lets wait bit .. if we can get ivy thing to work, we do not need to
>> write a new mvn build
>>
>> --Srinath
>>
>>
>> On Wed, Feb 1, 2012 at 8:42 AM, Deependra Ariyadewa wrote:
>>
>>>
>>>
>>> On Tue, Jan 31, 2012 at 7:04 PM, Srinath Perera wrote:
>>>
 can we get rid of ivy and write a maven build to Hadoop  for our stuff?
>>>
>>>
>>> current ant build is triggered by mvn. We used the existing ant build to
>>> save time.
>>>
>>>  I ll check the possibility to write a maven build for hadoop. Hadoop
>>> has a complex project structure :(.
>>>
>>> Thanks,
>>>
>>> Deependra.
>>>


  On Wed, Feb 1, 2012 at 8:29 AM, Deependra Ariyadewa wrote:

>
>
> On Tue, Jan 31, 2012 at 5:49 PM, Srinath Perera wrote:
>
>> Hi Wathsala,
>>
>> I am getting this? Please resolve.
>>
>> Does build is connected with the other parts?
>>
>
> No. This is only for hadoop-core dependency.
>
>>
>> From today, please sit with the BAM team at #58, they need a build
>> ASAP as I told earlier.
>>
>
> try to cache it locally. It looks ivy can not get it from given
> default repos in build.xml
>
>
>>
>> --Srinath
>>
>> vy:resolve] :: com.sun.jmx#jmxri;1.2.1!jmxri.jar
>> [ivy:resolve] ::
>> [ivy:resolve]
>> [ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 29.787s
>> [INFO] Finished at: Wed Feb 01 07:14:10 IST 2012
>> [INFO] Final Memory: 7M/822M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-antrun-plugin:1.6:run (default) on project
>> hadoop-core: An Ant BuildException has occured: The following error
>> occurred while executing this line:
>> [ERROR]
>> /Users/srinath/code/wso2-projects/carbon-trunk/dependencies/hadoop/build.xml:2040:
>> impossible to resolve dependencies:
>> [ERROR] resolve failed - see output for details
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>>   Photos: http://www.flickr.com/photos/hemapani/
>>  Phone: 0772360902
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> 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'
>
>


 --
 
 Srinath Perera, Ph.D.
   Senior Software Architect, WSO2 Inc.
   Visiting Faculty, University of Moratuwa
   Member, Apache Software Foundation
   Research Scientist, Lanka Software Foundation
   Blog: http://srinathsview.blogspot.com/
   Photos: http://www.flickr.com/photos/hemapani/
  Phone: 0772360902

>>>
>>>
>>>
>>> --
>>> 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'
>>>
>>>
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>>   Photos: http://www.flickr.com/photos/hemapani/
>>  Phone: 0772360902
>>
>
>
>
> --

Re: [Carbon-dev] Enabling Broker component to support all JMS brokers

[Amila Suriarachchi]

On Mon, Feb 6, 2012 at 7:48 PM, Paul Fremantle  wrote:

> Aha ok that is much clearer :-)
>
> So basically this is a JMS transport for CEP?
>

yes.

thanks,
Amila.

>
> Paul
>
>
> On 6 February 2012 13:25, Amila Suriarachchi  wrote:
>
>>
>>
>> On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle  wrote:
>>
>>> Suho
>>>
>>> What is the use case for this? Users can already use ActiveMQ with the
>>> ESB and other products via the JMS transport. There was (I think) a lot
>>> more work involved in adding QPid as a broker including tying into the
>>> Identity / User Manager as well as support for Multi-tenancy.
>>>
>>
>> Here we don't add ActiveMQ as a broker to carbon platform.
>>
>> This use case comes from the CEP side. This broker refers to the brokers
>> CEP used to receive events from different real brokers.
>>
>> Idea is to be able to consume messages publish to a jms topic in an
>> ActiveMQ broker in an CEP Bucket.
>>
>> thanks,
>> Amila.
>>
>>
>>
>>>
>>> Paul
>>>
>>> On 6 February 2012 07:04, Suhothayan Sriskandarajah wrote:
>>>

 Currently Broker component only supports Qpid broker and it doesn't
 have the ability to send messages to other JMS brokers.
 This is because the provider url used to create the connection is
 programmatically build using the username, password, ip address, port and
 virtual machine name.

 Now I'm is the process of extending Broker's functionality to support
 ActiveMQ.
 In this process I can either programmatically build the provider url of
 the ActiveMQ or I can generalize the process by asking the user to add the
 provider url itself.
 In both cases users need to add the relevant broker jars (activemq or
 other ) to the libs.

 Here since we are shipping Qpid I thought it will be appropriate for
 the user to have two UIs, one Qpid specific and the other a general JMS UI
 which will ask for prover url and JNDI class name.

 Please give your ideas on this approach

 Thanks
 Suho


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

 *email: **s...@wso2.com* * cell: (+94) 779 756 757
 blog: **http://suhothayan.blogspot.com/*
 *
 twitter: **http://twitter.com/suhothayan*
 *
 linked-in: **http://lk.linkedin.com/in/suhothayan*
 *
 *


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


>>>
>>>
>>> --
>>> Paul Fremantle
>>> CTO and Co-Founder, WSO2
>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>>
>>> UK: +44 207 096 0336
>>> US: +1 646 595 7614
>>>
>>> blog: http://pzf.fremantle.org
>>> twitter.com/pzfreo
>>> p...@wso2.com
>>>
>>> wso2.com Lean Enterprise Middleware
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, retransmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Amila Suriarachchi*
>>
>> Software Architect
>> WSO2 Inc. ; http://wso2.com
>> lean . enterprise . middleware
>>
>> phone : +94 71 3082805
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omi

Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon

[Sanjiva Weerawarana]

+1 for going ahead (without opinion on timing) and to Amila's suggestion of
making the orbit stuff another TLP.

I'm +1 for graphite per Senaka for X.

Sanjiva.

On Mon, Feb 6, 2012 at 4:03 PM, Dimuthu Leelarathne wrote:

> Hi all,
>
> +1.
>
> When installing other features to different products, it should mention
> the carbon core version. Currently, the carbon core is the intersection of
> products, so there is no problem at all. But if we go ahead with minimizing
> carbon-core it can be tricky to handle. Just had an offline chat with
> Sameera, and according to him P2 handles it nicely.
>
> thanks,
> dimuthu
>
> On Mon, Feb 6, 2012 at 8:24 AM, Sumedha Rubasinghe wrote:
>
>> +1 for the idea. B4 doing the actual change, how about running through
>> different scenarios (like Amila mentioned) - like how we did for branching
>> approach. Figuring out problems later would be costly in terms of time.
>>
>> /sumedha
>>
>> On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma wrote:
>>
>>> *Objective*:
>>> Make Carbon core a top level project in WSO2 trunk. At the moment
>>> complete Carbon platform code lies under
>>> https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its
>>> own problems.
>>>
>>> *Motivations*:
>>> 1) Carbon core can be treated as a separate product which has its own
>>> dependencies, orbit and Carbon core can be released independently of other
>>> Carbon components, products.
>>> 2) To ensure that the Carbon based products can depend on a stable, well
>>> tested and released version of Carbon instead of the Carbon trunk.
>>> 3) This will also ensure the stability of the Carbon based products,
>>> because they are no longer depend on the Carbon trunk which might undergo
>>> drastic changes time to time.
>>>
>>> *Execution*:
>>> Here is my proposal.
>>> 1) We need to create two top level directories for Carbon and for
>>> components, features and Carbon based products. Sample structure is shown
>>> below.
>>>
>>> carbon
>>> |--dependencies
>>> |--orbits
>>> |--core (core set of bundles.)
>>> |--features (Carbon core features)
>>> |--product (Carbon product)
>>>
>>> X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva
>>> once mentioned this name. :) )
>>> |--dependencies
>>> |--orbits
>>> |--components
>>> |--features
>>> |--products
>>>
>>> 2) In order to change the existing svn structure to a structure like
>>> above, we need to hold all the commits, say for two to three days and
>>> restructure the SVN, test properly and release for commits.
>>>
>>> Please feel free to comment.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> --
>>> Sameera Jayasoma
>>> Technical Lead and Product Manager, WSO2 Carbon
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://tech.jayasoma.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> /sumedha
>> +94 773017743
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-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
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon

[Tharindu Mathew]

As per Amila's suggestion, we can also start moving products also similar
to carbon... have their own trunk and branch...

IMO, products should own which feature version they want to depend on. They
should only move to a new feature if they need a fix/ improvement in the
new version.

This would mean that Carbon and Feature versions are independent.

On Mon, Feb 6, 2012 at 9:25 PM, Sanjiva Weerawarana wrote:

> +1 for going ahead (without opinion on timing) and to Amila's suggestion
> of making the orbit stuff another TLP.
>
> I'm +1 for graphite per Senaka for X.
>
> Sanjiva.
>
> On Mon, Feb 6, 2012 at 4:03 PM, Dimuthu Leelarathne wrote:
>
>> Hi all,
>>
>> +1.
>>
>> When installing other features to different products, it should mention
>> the carbon core version. Currently, the carbon core is the intersection of
>> products, so there is no problem at all. But if we go ahead with minimizing
>> carbon-core it can be tricky to handle. Just had an offline chat with
>> Sameera, and according to him P2 handles it nicely.
>>
>> thanks,
>> dimuthu
>>
>> On Mon, Feb 6, 2012 at 8:24 AM, Sumedha Rubasinghe wrote:
>>
>>> +1 for the idea. B4 doing the actual change, how about running through
>>> different scenarios (like Amila mentioned) - like how we did for branching
>>> approach. Figuring out problems later would be costly in terms of time.
>>>
>>> /sumedha
>>>
>>> On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma wrote:
>>>
 *Objective*:
 Make Carbon core a top level project in WSO2 trunk. At the moment
 complete Carbon platform code lies under
 https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its
 own problems.

 *Motivations*:
 1) Carbon core can be treated as a separate product which has its own
 dependencies, orbit and Carbon core can be released independently of other
 Carbon components, products.
 2) To ensure that the Carbon based products can depend on a stable,
 well tested and released version of Carbon instead of the Carbon trunk.
 3) This will also ensure the stability of the Carbon based products,
 because they are no longer depend on the Carbon trunk which might undergo
 drastic changes time to time.

 *Execution*:
 Here is my proposal.
 1) We need to create two top level directories for Carbon and for
 components, features and Carbon based products. Sample structure is shown
 below.

 carbon
 |--dependencies
 |--orbits
 |--core (core set of bundles.)
 |--features (Carbon core features)
 |--product (Carbon product)

 X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva
 once mentioned this name. :) )
 |--dependencies
 |--orbits
 |--components
 |--features
 |--products

 2) In order to change the existing svn structure to a structure like
 above, we need to hold all the commits, say for two to three days and
 restructure the SVN, test properly and release for commits.

 Please feel free to comment.

 Thanks,
 Sameera.

 --
 Sameera Jayasoma
 Technical Lead and Product Manager, WSO2 Carbon

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://tech.jayasoma.org

 Lean . Enterprise . Middleware

 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> /sumedha
>>> +94 773017743
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Technical Lead
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>>
>>
>> Lean . Enterprise . Middleware
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-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
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Regards,

Tharindu

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

Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon

[Sanjiva Weerawarana]

Totally absolutely -1 :). If you want to take each FEATURE and make it into
a TLP I'm totally +1, however not a product. That would go against our
recent attempts at (re-)organizing around technology areas. A "product" for
us is simply a pre-packed and tested set of features and I want to go in
the opposite direction: Automate product creation to the point where
everything from docs to testing is automated. Then the manual work goes
towards features and products are simply distribution vehicles.

Sanjiva.

On Mon, Feb 6, 2012 at 9:37 PM, Tharindu Mathew  wrote:

> As per Amila's suggestion, we can also start moving products also similar
> to carbon... have their own trunk and branch...
>
> IMO, products should own which feature version they want to depend on.
> They should only move to a new feature if they need a fix/ improvement in
> the new version.
>
> This would mean that Carbon and Feature versions are independent.
>
> On Mon, Feb 6, 2012 at 9:25 PM, Sanjiva Weerawarana wrote:
>
>> +1 for going ahead (without opinion on timing) and to Amila's suggestion
>> of making the orbit stuff another TLP.
>>
>> I'm +1 for graphite per Senaka for X.
>>
>> Sanjiva.
>>
>> On Mon, Feb 6, 2012 at 4:03 PM, Dimuthu Leelarathne wrote:
>>
>>>  Hi all,
>>>
>>> +1.
>>>
>>> When installing other features to different products, it should mention
>>> the carbon core version. Currently, the carbon core is the intersection of
>>> products, so there is no problem at all. But if we go ahead with minimizing
>>> carbon-core it can be tricky to handle. Just had an offline chat with
>>> Sameera, and according to him P2 handles it nicely.
>>>
>>> thanks,
>>> dimuthu
>>>
>>> On Mon, Feb 6, 2012 at 8:24 AM, Sumedha Rubasinghe wrote:
>>>
 +1 for the idea. B4 doing the actual change, how about running through
 different scenarios (like Amila mentioned) - like how we did for branching
 approach. Figuring out problems later would be costly in terms of time.

 /sumedha

 On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma wrote:

> *Objective*:
> Make Carbon core a top level project in WSO2 trunk. At the moment
> complete Carbon platform code lies under
> https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its
> own problems.
>
> *Motivations*:
> 1) Carbon core can be treated as a separate product which has its own
> dependencies, orbit and Carbon core can be released independently of other
> Carbon components, products.
> 2) To ensure that the Carbon based products can depend on a stable,
> well tested and released version of Carbon instead of the Carbon trunk.
> 3) This will also ensure the stability of the Carbon based products,
> because they are no longer depend on the Carbon trunk which might undergo
> drastic changes time to time.
>
> *Execution*:
> Here is my proposal.
> 1) We need to create two top level directories for Carbon and for
> components, features and Carbon based products. Sample structure is shown
> below.
>
> carbon
> |--dependencies
> |--orbits
> |--core (core set of bundles.)
> |--features (Carbon core features)
> |--product (Carbon product)
>
> X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva
> once mentioned this name. :) )
> |--dependencies
> |--orbits
> |--components
> |--features
> |--products
>
> 2) In order to change the existing svn structure to a structure like
> above, we need to hold all the commits, say for two to three days and
> restructure the SVN, test properly and release for commits.
>
> Please feel free to comment.
>
> Thanks,
> Sameera.
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 /sumedha
 +94 773017743

 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Dimuthu Leelarathne
>>> Technical Lead
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: dimut...@wso2.com
>>>
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-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://sa

Re: [Carbon-dev] Tomcat OSGification - progress update

[Afkham Azeez]

Excellent work Pradeep!

--
Afkham Azeez
Sent from my phone
On Feb 6, 2012 7:32 PM, "Pradeep Fernando"  wrote:

> Hi,
>
> On Mon, Feb 6, 2012 at 7:05 PM, Afkham Azeez  wrote:
>
>> Did you write any code to parse the server.xml file or did Tomcat
>> automatically parse the file when the location was provided?
>>
>
> tomcat uses commons digester to configure its components. I used the same
> mechanism. It took some time to learn how to use it.
>
> thanks,
> --Pradeep
>
>
>
>>
>> On Mon, Feb 6, 2012 at 2:02 AM, Pradeep Fernando wrote:
>>
>>> Hi,
>>>
>>> I was able to configure the tomcat with tomcat-shipped server.xml file.
>>> this means we can register connectors Hosts, valves, listeners without
>>> hard-coding them.
>>>
>>> I the current code has some issues related to JNDI. Think this is
>>> related non-OSGi/OSGi env jar duplication. I need some help to get this
>>> done. We have to move each and every library that resides under /ib
>>> (relevant) to plugins.
>>>
>>> For the moment i have moved only tomcat related libs.
>>>
>>> --Pradeep
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Pradeep Fernando
> Software Engineer
> WSO2 Inc; http://wso2.com/
>
> blog: http://pradeepfernando.blogspot.com/
> m: +94776603662
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #179 has FAILED (1 tests failed). Change made by deep.

[Bamboo]

---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #179 failed.
---
Code has been updated by deep.
1/7615 tests failed.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-179/


--
Failing Jobs
--
  - WSO2 Carbon Trunk Build Process (Default Stage): 1 of 7615 tests failed.


--
Code Changes
--
deep (120178):

>Commiting ant.jar binary file to fix the build.  
>We will try to remove binary files from hadoop build in the future.
>



--
Tests
--
New Test Failures (1)
   - DSSTestServerManager: Start server

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

Re: [Carbon-dev] Cannot build latest svn trunk carbon core

[KasunG Gajasinghe]

On Mon, Feb 6, 2012 at 6:58 PM, Sameera Jayasoma  wrote:

> Hi Samisa,
>
> There is a workaround. Can you please comment out the following section
> from the  platform pom.xml
>

But, because of this, the pom installed to m2 also will has the modules
commented out. So, manual editing is needed. A better option would be to
issue to following command from the top-level. There's no need to comment
the modules section.

*mvn install -N*
*
*
Maven help says,
-N,--non-recursive -   Do not recurse into sub-projects


>
> default
>   
> true
>   
> 
> 
>
> Then invoke the 'mvn clean install' from the top level. This will allow
> the platform pom to be added to the .m2 repo.
>
> Then try to build carbon core.
>
> Thanks,
> Sameera.
>
> On Mon, Feb 6, 2012 at 6:47 PM, Samisa Abeysinghe  wrote:
>
>>
>>
>> On Mon, Feb 6, 2012 at 6:20 PM, Dileepa Jayakody wrote:
>>
>>> Hi,
>>>
>>> This is due to some dependency artifacts not been downloaded from
>>> maven.wso2.org/nexus/content/groups/wso2-public/
>>> I think this happens because LK cache repo is not yet synced properly.
>>>
>>
>> Is there any workaround?
>>
>>
>>>
>>> Regards,
>>> Dileepa
>>>
>>> On Mon, Feb 6, 2012 at 6:09 PM, Samisa Abeysinghe wrote:
>>>
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 10.774s
 [INFO] Finished at: Mon Feb 06 18:08:23 IST 2012
 [INFO] Final Memory: 47M/981M
 [INFO]
 
 [ERROR] Failed to execute goal on project org.wso2.carbon.base: Could
 not resolve dependencies for project
 org.wso2.carbon:org.wso2.carbon.base:jar:4.0.0-SNAPSHOT: Failed to collect
 dependenc
 ies for [org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1
 (compile), org.wso2.carbon:org.wso2.carbon.logging:jar:4.0.0-SNAPSHOT
 (compile), org.wso2.carbon:org.wso2.carbon.queuing:jar:
 4.0.0-SNAPSHOT (compile),
 org.wso2.securevault:org.wso2.securevault:jar:1.0.0 (compile),
 org.wso2.carbon:org.wso2.carbon.securevault:jar:4.0.0-SNAPSHOT (compile),
 javax.servlet:servlet-api:ja
 r:2.4 (compile)]: Failed to read artifact descriptor for
 org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v1: Failure to find
 org.wso2.carbon:carbon-platform:pom:4.0.0-SNAPSHOT in http:/
 /maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
 local repository, resolution will not be reattempted until the update
 interval of wso2-nexus has elapsed or updates are for
 ced -> [Help 1]
 [ERROR]

 Thanks,
 Samisa...

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


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


>>>
>>>
>>> --
>>> Dileepa Jayakody,
>>> Software Engineer, WSO2 Inc.
>>> Lean . Enterprise . Middleware
>>>
>>> Mobile : +94777-857616
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
>
> Lean . Enterprise . Middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Kasun Gajasinghe*
Software Engineer; WSO2 Inc.; http://wso2.com

,
*email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
*blog: **http://blog.kasunbg.org* 

*
twitter: **http://twitter.com/kasunbg* 

*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon

[Afkham Azeez]

For this approach to properly work, we need to have proper package export &
import versions. Otherwise, say for example, two different features require
different versions of a particular bundle, then these features may not be
able to coexist. When upgrading a versions of an orbit dependency, the
should be a way to track all its dependant &  change them accordingly to
avoid ending up with unnecessary jar duplication.

--
Afkham Azeez
Sent from my phone
On Feb 6, 2012 9:27 PM, "Sanjiva Weerawarana"  wrote:

> +1 for going ahead (without opinion on timing) and to Amila's suggestion
> of making the orbit stuff another TLP.
>
> I'm +1 for graphite per Senaka for X.
>
> Sanjiva.
>
> On Mon, Feb 6, 2012 at 4:03 PM, Dimuthu Leelarathne wrote:
>
>> Hi all,
>>
>> +1.
>>
>> When installing other features to different products, it should mention
>> the carbon core version. Currently, the carbon core is the intersection of
>> products, so there is no problem at all. But if we go ahead with minimizing
>> carbon-core it can be tricky to handle. Just had an offline chat with
>> Sameera, and according to him P2 handles it nicely.
>>
>> thanks,
>> dimuthu
>>
>> On Mon, Feb 6, 2012 at 8:24 AM, Sumedha Rubasinghe wrote:
>>
>>> +1 for the idea. B4 doing the actual change, how about running through
>>> different scenarios (like Amila mentioned) - like how we did for branching
>>> approach. Figuring out problems later would be costly in terms of time.
>>>
>>> /sumedha
>>>
>>> On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma wrote:
>>>
 *Objective*:
 Make Carbon core a top level project in WSO2 trunk. At the moment
 complete Carbon platform code lies under
 https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its
 own problems.

 *Motivations*:
 1) Carbon core can be treated as a separate product which has its own
 dependencies, orbit and Carbon core can be released independently of other
 Carbon components, products.
 2) To ensure that the Carbon based products can depend on a stable,
 well tested and released version of Carbon instead of the Carbon trunk.
 3) This will also ensure the stability of the Carbon based products,
 because they are no longer depend on the Carbon trunk which might undergo
 drastic changes time to time.

 *Execution*:
 Here is my proposal.
 1) We need to create two top level directories for Carbon and for
 components, features and Carbon based products. Sample structure is shown
 below.

 carbon
 |--dependencies
 |--orbits
 |--core (core set of bundles.)
 |--features (Carbon core features)
 |--product (Carbon product)

 X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva
 once mentioned this name. :) )
 |--dependencies
 |--orbits
 |--components
 |--features
 |--products

 2) In order to change the existing svn structure to a structure like
 above, we need to hold all the commits, say for two to three days and
 restructure the SVN, test properly and release for commits.

 Please feel free to comment.

 Thanks,
 Sameera.

 --
 Sameera Jayasoma
 Technical Lead and Product Manager, WSO2 Carbon

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://tech.jayasoma.org

 Lean . Enterprise . Middleware

 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> /sumedha
>>> +94 773017743
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Technical Lead
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>>
>>
>> Lean . Enterprise . Middleware
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-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
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #180 has FAILED (1 tests failed, no failures were new). Change made by wathsala.

[Bamboo]

---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #180 failed.
---
Code has been updated by wathsala.
1/7615 tests failed, no failures were new.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-180/


--
Failing Jobs
--
  - WSO2 Carbon Trunk Build Process (Default Stage): 1 of 7615 tests failed.


--
Code Changes
--
wathsala (120180):

>Fixed mgt and jobtracker bugs



--
Tests
--
Existing Test Failures (1)
   - DSSTestServerManager: Start server

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

Re: [Carbon-dev] Too many quartz logs in AS-4.5.0 startup

[Prabath Abeysekera]

Hi,

On Wed, Feb 1, 2012 at 9:02 AM, Anjana Fernando  wrote:

> Hi,
>
> Sorry for the delay, I've made quartz logs to WARN log level. This change
> is done in trunk. Also, in AS quartz dependency is coming from data
> services feature, which has scheduled tasks bundles with it, I'm going to



> separate out the data services task feature and only create a data
> services only feature, so when someone install the core data services
> feature, they won't get the scheduled tasks, which may not be required most
> of the time. If they want it, they can install it separately.
>

I've separated out the DSS tasks functionality and created a new feature
out of it. So by default, only the data services core features would be
installed and if anyone is interested in having DSS tasks functionality,
they can easily get it installed via the carbon feature manager or the OSGi
cosole.



> Cheers,
> Anjana.
>
>
> On Tue, Jan 31, 2012 at 10:02 PM, Supun Malinga  wrote:
>
>> HI,
>>
>> This was said in earlier mails as well.
>> Anjana, any update on the matter?
>>
>> thanks,
>>
>> org.quartz.simpl.SimpleThreadPool} -  Job execution threads will use
>> class loader of thread: Framework Event Dispatcher
>>
>>> [2012-01-31 21:42:41,031]  INFO {org.quartz.core.SchedulerSignalerImpl}
>>> -  Initialized Scheduler Signaller of type: class
>>> org.quartz.core.SchedulerSignalerImpl
>>> [2012-01-31 21:42:41,032]  INFO {org.quartz.core.QuartzScheduler} -
>>> Quartz Scheduler v.2.1.1 created.
>>> [2012-01-31 21:42:41,033]  INFO {org.quartz.simpl.RAMJobStore} -
>>> RAMJobStore initialized.
>>> [2012-01-31 21:42:41,034]  INFO {org.quartz.core.QuartzScheduler} -
>>> Scheduler meta-data: Quartz Scheduler (v2.1.1) 'DefaultQuartzScheduler'
>>> with instanceId 'NON_CLUSTERED'
>>>   Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
>>>   NOT STARTED.
>>>   Currently in standby mode.
>>>   Number of jobs executed: 0
>>>   Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10
>>> threads.
>>>   Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
>>> support persistence. and is not clustered.
>>>
>>> [2012-01-31 21:42:41,034]  INFO {org.quartz.impl.StdSchedulerFactory} -
>>> Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource
>>> file in Quartz package: 'quartz.properties'
>>> [2012-01-31 21:42:41,034]  INFO {org.quartz.impl.StdSchedulerFactory} -
>>> Quartz scheduler version: 2.1.1
>>> [2012-01-31 21:42:41,034]  INFO {org.quartz.core.QuartzScheduler} -
>>> Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
>>>
>>> Thanks!
>>> Charitha
>>>
>>>
>>>
>>> Charitha Kankanamge
>>> cell: +94 718 359 265
>>> blog: http://charithaka.blogspot.com 
>>>
>>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>> email - sup...@wso2.com 
>> mobile - 071 56 91 321
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Prabath Abeysekara
Software Engineer
WSO2 Inc.
Email: praba...@wso2.com 
Mobile: +94774171471


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