Re: [Carbon-dev] WS02 BPS - WS-HumanTask support - Architecture review
On Saturday, January 28, 2012, Denis Weerasiri de...@wso2.com wrote: On Sat, Jan 28, 2012 at 5:57 AM, Senaka Fernando sen...@wso2.com wrote: Hi Denis, The completion of this should introduce a work list UI for Carbon as discussed offline. The main purpose of this UI and the BE API is to: 1. Allocate work items to humans. 2. Review and perform pending items. 3. See a timeline of what others do. Regarding the #3, Suppose there's a business process that incorporate with several human tasks. What you meant by timeline is, the sequence of activities pending, completed, who completed them etc for that business process? I'm talking in a user's PoV. So, what I intend is the sequence of all activities that would either involve me or another user in my role for all processes. 3 is possible only in the context of 1and 2. Thanks, Senaka. Or are you referring to a timeline for each human task? like in Facebook. Thanks, Senaka. On Thursday, January 26, 2012, Denis Weerasiri de...@wso2.com wrote: FYI, Here I have attached the high level architecture diagram for WS_HT engine. /mail/u/0/s/?view=attth=135185ef58bc6ed8attid=0.0.1disp=embrealattid=ii_135185e03166b04dzw On Thu, Jan 26, 2012 at 3:23 AM, Denis Weerasiri de...@wso2.com wrote: Hi all, Recently we had an architectural discussion regarding the WS-Human Task compliant engine which is planned to be shipped with next WSO2 BPS major release. In BPS 2.0.1 release, we added the Human Task support WSO2 BPS and it was removed due to lack of tooling and multi-tenancy support. Currently we are working on multi-tenanted Human Task implementation for WSO2 BPS with Eclipse based tooling support. Here I have summarised the meeting notes and some points which need some clarifications. Push based notifications for new human tasks - In the initial implementation, task assigned users have to check their task box/list for new tasks. We are going to improve s.t to push task notifications to subscribed users. Client-API - Client-API is the management API component in the human-task engine and we have to finalise it based on the general use cases. And we are hoping some practical use cases from the community so we can come up with a well defined management API and decide new features/improvements. WSO2 Carbon Studio-BPEL and HumanTask editor - We have included the BPEL4People compliant extension activity to our BPEL editor. The implementation of the HumanTask editor is still not PoC ready as there are some considerable amount of work to be done. Seamless authentication - We haven't finalised on how to enable authentication for human task admin console and task list UI web app. (One use case is once the user logged into the task list UI web app, then it should authenticated with human task engine.) You can find the initial Client-API wsdl which expose some of the management functionalities for the ws-human task engine from https://svn.wso2.org/repos/wso2/trunk/carbon/service-stubs/org.wso2.carbon.humantask.skeleton/src/main/resources/ws-humantask-api.wsdl And the source code from https://svn.wso2.org/repos/wso2/trunk/carbon/components/business-processes/humantask -- Thanks, Denis -- Denis Weerasiri Software Engineer; WSO2 Inc.; http://wso2.com, email: denis [AT] wso2.com phone: +94117639629 site: ddweerasiri blog: http://ddweerasiri.blogspot.com twitter: http://twitter.com/ddweerasiri linked-in: http://lk.linkedin.com/in/ddweerasiri -- Thanks, Denis -- Denis Weerasiri Software Engineer; WSO2 Inc.; http://wso2.com, email: denis [AT] wso2.com phone: -- 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 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Thanks, Denis -- Denis Weerasiri Software Engineer; WSO2 Inc.; http://wso2.com, email: denis [AT] wso2.com phone: +94117639629 site: ddweerasiri blog: http://ddweerasiri.blogspot.com twitter: http://twitter.com/ddweerasiri linked-in: http://lk.linkedin.com/in/ddweerasiri -- *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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ResourceNotFoundException thrown when resourceExists() is true
Hi Dimuthu,
Well that probably explains my point. If you test something across two
nodes you need to turn off caching in registry or properly setup
distributed or replicated caching. If not each node caches locally, and
will not sync until timeout.
Thanks,
Senaka.
On Thursday, January 26, 2012, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi Senaka,
On Thu, Jan 26, 2012 at 5:26 AM, Senaka Fernando sen...@wso2.com wrote:
Hi Pradeeban,
Probably, due to caching not properly setup.
AFAIK registry reads from database when it is not in the cache. From my
experience Registry worked perfectly when multicasting ports were closed in
the switch as well.
thanks,
dimuthu
Thanks,
Senaka.
On Wed, Jan 25, 2012 at 11:39 PM, Kathiravelu Pradeeban
pradee...@wso2.com wrote:
The deployment was with the SVN based deployment synchronizer. Ghost
deployer is disabled.
Regards,
Pradeeban.
On Wed, Jan 25, 2012 at 7:43 PM, Kathiravelu Pradeeban
pradee...@wso2.com wrote:
Hi,
Azeez and I were testing a Stratos deployment with 2 nodes of Appserver.
We did a minor modification in the getService() of
ServicePersistenceManager as below.
Then we uploaded a service; accessed it from two browsers; and deleted
it.
Interestingly the highlighted code-segment is executed, and prints true,
in the terminal of the other node.
That means, the resourceExists, but the ResourceNotFoundException is
thrown. Can someone explains this behavior?
public Resource getService(AxisService axisService) throws Exception
{
try {
String serviceResourcePath =
PersistenceUtils.getResourcePath(axisService);
if (configRegistry.resourceExists(serviceResourcePath)) {
Resource resource = null;
try {
resource = configRegistry.get(serviceResourcePath);
} catch (ResourceNotFoundException e) {
System.out.println(++ +
configRegistry.resourceExists(serviceResourcePath));
if(configRegistry.resourceExists(serviceResourcePath)){
throw e;
}
}
}
Complete log for the interested:
Node 1:
[2012-01-25 05:52:04,562] @3000.abw [6451] [WSO2 Stratos Application
Server] INFO {org.wso2.carbon.service.mgt.ServiceAdmin} - Undeploying Web
service: /mnt/
209.126.198.68/wso2stratos-as-1.5.2/repository/tenants/6451/axis2services/Chad.aar
[2012-01-25 05:52:10,101] INFO
{org.apache.axis2.deployment.DeploymentEngine} -
org.apache.axis2.deployment.DeploymentException: The Chad service group
name is not valid.
Node2:
++true
[2012-01-25 05:51:57,467] @3000.abw [6451] [WSO2 Stratos Application
Server]ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager}
- Could not get the Service resource from Config Registry
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path
/_system/config/repository/axis2/service-groups/Chad/services/Chad
at
org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:426)
at
org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2378)
at
org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)
at
org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:814)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)
at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)
at
org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:528)
at
org.wso2.carbon.core.persistence.ServicePersistenceManager.getService(ServicePersistenceManager.java:89)
at
org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:254)
at
org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
at
org.apache.axis2.engine.AxisConfiguration.removeServiceGroup(AxisConfiguration.java:516)
at
org.apache.axis2.deployment.ServiceDeployer.undeploy(ServiceDeployer.java:188)
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Dimuthu Leelarathne
Technical Lead
WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com
Lean . Enterprise . Middleware
--
*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
___
Carbon-dev mailing list
Carbon-dev@wso2.org
Re: [Carbon-dev] Ensure that we do not swallow exceptions
Hi Hasini, On Saturday, January 28, 2012, Hasini Gunasinghe has...@wso2.com wrote: Hi Senaka, On Sat, Jan 28, 2012 at 7:13 AM, Senaka Fernando sen...@wso2.com wrote: Hi Hasini, On Tuesday, January 24, 2012, Hasini Gunasinghe has...@wso2.com wrote: Hi Senaka, On Mon, Jan 23, 2012 at 11:16 PM, Senaka Fernando sen...@wso2.com wrote: Hi Hasini, On Mon, Jan 23, 2012 at 10:06 PM, Hasini Gunasinghe has...@wso2.com wrote: Hi Senaka, On Mon, Jan 23, 2012 at 8:41 PM, Senaka Fernando sen...@wso2.com wrote: Hi Azeez, Sorry lost track of this. 1. The first one is the easiest. Insert malformed XML into user-mgt.xml and start the server. Console is clean (no exceptions). Server hangs and does not start-up. There is no clue to what went wrong. Just make Configuration into !--Configuration. Error reporting needs to be fixed here. Thanks for reporting. This was fixed in trunk. 2. Create any possible error that would result in the user profiles section being corrupted. No exceptions on the BE. The front-end returns the same error message for all types of errors making debugging a nightmare. We reproduced this by a an accidentally corrupted database, but there could be many other ways to get to this. I couldn't reproduce this with user profiles feature. Can you please mention couple of examples out of the many ways you observed this? As I said I got it reproduced using an accidentally corrupted DB, but there could be many other ways - by looking at the code. Since you have already identified the related code, can you please point to it? So that it will be easy to rectify it if there are any issues. Great. I misunderstood you earlier. Find the exception in the index.jsp, add.jsp and edit.jsp pages of the identity user profile UI. There you catch the exception and send an error message to the UI. It is the same error message in all 3 cases, so it should be easy to locate. Now, check the corresponding code in BE. You'll see that all exceptions are simply propagated to FE, and at times, the cause is not carried forward. You need to dig deeper and deeper into the BE code until you get to the low-level LDAP layer up until the admin service. Thanks for the information. It will help to identify where to fix. However, since I haven't written the code in this component, I am not quite sure whether the error handling was done that way on any purpose. Anyway, it's clearly not the model we follow. Please log and forward. But, I have not attempted to. What I'm trying to get to is that, any error will produce no stack traces but a single error message in the UI. Though not quite related, we noticed that usernames on Carbon 3.2.3 are case-sensitive, I guess you meant to say case insensitive - we have mentioned this in sign-in help docs as follows: Please note that due to the inherited behaviour of default user store - which is embedded-ldap, user names are case insensitive in 3.2.0 based carbon products. Are you sure the login failure you encountered is due to a case sensitive issue? Because username is case insensitive as mentioned above - and allows you to login even if you change the case of the username. Actually, if the username was 'U12345' you cannot login as 'u12345', which is the concern. I tried this case with IS 3.2.3 and it is possible to login with both the above usernames with default user store - which is embedded ldap. Did you encounter this with any other custom LDAP? In that case, it is not a regression issue, but it is due to a behavior of that particular LDAP that you connected to. Not really. When connected to same custom LDAP, the sensitivity is not effective in older releases (very clear in 3.1.0 and perhaps in 3.2.0). So, this is clearly a regression. Can you please let me know what is the LDAP server you tried to connect to - i.e: OpenLDAP, ApacheDS etc? (So that we can try to reproduce.) Because this could not be reproduced with embedded-apacheds and was able to login with the same user name in both lower and upper case. Will try to get this asap. But, can u first connect to LDAP and create a user with mixed cases or all uppercase, then connect Carbon, and try to login with all lowercase? That's what seemed to have happened. Thanks, Senaka. Thanks, Hasini. Thanks, Senaka. Thanks, Hasini. Thanks, Senaka. Thanks, Hasini. which is a L1 regression. Also, just as in 1 and 2 above, the error is failed login attempt, and BE is dead silent to what went wrong. It took at least a dozen retries to figure out and a fair amount on time wasted in understanding what went wrong. Though the FE might give out a simple authentication failure, I'd expect the BE to be more specific to what went wrong. Thanks, Senaka. On Mon, Jan 23, 2012 at 8:19 PM, Afkham Azeez az...@wso2.com wrote: Please post the relevant code segments. This is something we keep repeating during code reviews.
Re: [Carbon-dev] [Carbon Studio] ESB Graphical editor - Example 1
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 sam...@wso2.com 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.comwrote: 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 be automated. - File name should be appeared in the editor header. - Defined endpoints should also go to the pallet as re-usable components. - Endpoints in the border should be handled in a better way. - When open the sequence editor diagram, area for the diagram should be auto generated. - Name of the sequence should be displayed in the top of the page as well as in the sequence. - Name of the mediators and endpoints should be appeared in their figure. - Mediator grouping should be added. - A suitable extensions should be used for ESB Graphical editor files and for Sequence editor files. Thanks, On Tue, Jan 24, 2012 at 12:18 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi , I tried to generate a Sample Synapse Configuration (See attached file Synapse Configuration - Example 1.txt) using the ESB Graphical editor. There were some issues while design the diagram. - How can we represent the Local Entry graphically ? - Send mediator has only input connector and output connector (See attached Send_Mediator.png). How can we represent the value of the receive attribute in Send mediator.(For a example, send receive=geoResponseSeq .In this case geoResponseSeq is a defined sequence.How can we represent this relationship between sequence and Send mediator inside the graphical editor.) ? Please comment on these issues if you have any idea. Screen shots for Relevant Diagram for the Synapse Configuration - Example 1 and the generated Synapse configuration are attached with this. Thanks, -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ 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 -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ 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
We still do not have the reverse engineering support since it is technically quite hard. 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 vi...@wso2.com 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 sam...@wso2.comwrote: 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.comwrote: 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 be automated. - File name should be appeared in the editor header. - Defined endpoints should also go to the pallet as re-usable components. - Endpoints in the border should be handled in a better way. - When open the sequence editor diagram, area for the diagram should be auto generated. - Name of the sequence should be displayed in the top of the page as well as in the sequence. - Name of the mediators and endpoints should be appeared in their figure. - Mediator grouping should be added. - A suitable extensions should be used for ESB Graphical editor files and for Sequence editor files. Thanks, On Tue, Jan 24, 2012 at 12:18 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi , I tried to generate a Sample Synapse Configuration (See attached file Synapse Configuration - Example 1.txt) using the ESB Graphical editor. There were some issues while design the diagram. - How can we represent the Local Entry graphically ? - Send mediator has only input connector and output connector (See attached Send_Mediator.png). How can we represent the value of the receive attribute in Send mediator.(For a example, send receive=geoResponseSeq .In this case geoResponseSeq is a defined sequence.How can we represent this relationship between sequence and Send mediator inside the graphical editor.) ? Please comment on these issues if you have any idea. Screen shots for Relevant Diagram for the Synapse Configuration - Example 1 and the generated Synapse configuration are attached with this. Thanks, -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ 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
[Carbon-dev] Why committing JARs to SVN repo?
Hi, Do we really need to commit jar files to SVN? Can't we add them as dependencies in the pom? I've noticed many jars been committed to dependencies. See [1] for few. Thanks. [1] Abroker2/java/lib/org.eclipse.swt_3.4.1.v3449c.jar Abroker2/java/lib/zookeeper-3.4.1.jar Abroker2/java/lib/org.eclipse.core.contenttype_3.3.0.v20080604-1400.jar Abroker2/java/lib/org.apache.felix.framework-2.0.5.jar Abroker2/java/lib/org.eclipse.jface_3.4.1.M20080827-2000.jar Abroker2/java/lib/guava-r08.jar Abroker2/java/lib/mina-core-1.1.7.jar Abroker2/java/lib/perf4j-0.9.12.wso2v1.jar -- regards, Nirmal Software Engineer, WSO2 Inc. mobile: +94715779733 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Bad API in registry.core HandlerManager
No ack .. Azeez maybe you should create an issue .. that way it doesn't get lost! On Thu, Jan 26, 2012 at 5:38 PM, Afkham Azeez az...@wso2.com wrote: This class in in really bad shape. It has about 20 maps each correspond to a method, and in the addHandler methods check for the method doing a String comparison add to the relevant map! Really bad OO design. I guess introducing another class which has the Map method will greatly reduce the LOC in this class. On Thu, Jan 26, 2012 at 5:31 PM, Afkham Azeez az...@wso2.com wrote: See attached screenshot. This type of code should be properly refactored to use enums. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ 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] Bad API in registry.core HandlerManager
Created an issue assigned to Janaka - https://wso2.org/jira/browse/CARBON-12299 /sumedha On Sun, Jan 29, 2012 at 9:43 PM, Sanjiva Weerawarana sanj...@wso2.comwrote: No ack .. Azeez maybe you should create an issue .. that way it doesn't get lost! On Thu, Jan 26, 2012 at 5:38 PM, Afkham Azeez az...@wso2.com wrote: This class in in really bad shape. It has about 20 maps each correspond to a method, and in the addHandler methods check for the method doing a String comparison add to the relevant map! Really bad OO design. I guess introducing another class which has the Map method will greatly reduce the LOC in this class. On Thu, Jan 26, 2012 at 5:31 PM, Afkham Azeez az...@wso2.com wrote: See attached screenshot. This type of code should be properly refactored to use enums. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ 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 -- /sumedha +94 773017743 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] redefining dependency version under component/feature modules
Hi devs, Please always try to use the platform pom defined versions. Below is only some example of $subject. There is no need of redefining these properties since its already defined in parent poms. ./components/jaggery/pom.xml: axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version ./components/hostobjects/pom.xml: axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version ./features/jaggery/pom.xml: axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version Also similar redundant definitions are in components/pom.xml, etc. For eg: in components/pom.xml, wso2carbon.version4.0.0-SNAPSHOT/wso2carbon.version axis2.wso2.version1.6.1.wso2v5/axis2.wso2.version axis2.version1.6.1-wso2v5/axis2.version axis2.osgi.version.range[1.6.1.wso2v1, 1.7.0)/axis2.osgi.version.range axiom.osgi.version.range[1.2.11.wso2v1, 1.3.0)/axiom.osgi.version.range These are already defined in the platform pom. So why are we redefining? thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com 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] redefining dependency version under component/feature modules
Jaggery guys please fix Supun .. could you run a grep for [0-9.]*.wso2* and other similar patterns to find other places we are not using platform pom version and send a report? We should do this time to time On Mon, Jan 30, 2012 at 1:50 AM, Supun Malinga sup...@wso2.com wrote: Hi devs, Please always try to use the platform pom defined versions. Below is only some example of $subject. There is no need of redefining these properties since its already defined in parent poms. ./components/jaggery/pom.xml: axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version ./components/hostobjects/pom.xml: axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version ./features/jaggery/pom.xml: axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version Also similar redundant definitions are in components/pom.xml, etc. For eg: in components/pom.xml, wso2carbon.version4.0.0-SNAPSHOT/wso2carbon.version axis2.wso2.version1.6.1.wso2v5/axis2.wso2.version axis2.version1.6.1-wso2v5/axis2.version axis2.osgi.version.range[1.6.1.wso2v1, 1.7.0)/axis2.osgi.version.range axiom.osgi.version.range[1.2.11.wso2v1, 1.3.0)/axiom.osgi.version.range These are already defined in the platform pom. So why are we redefining? thanks, -- 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 -- 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
Re: [Carbon-dev] Why committing JARs to SVN repo?
Wathsala and Charith .. I think answer is we do not need to commit the jars .. just we have to fix the builds. Lets get them removed On Sun, Jan 29, 2012 at 7:44 PM, Nirmal Fernando nir...@wso2.com wrote: Hi, Do we really need to commit jar files to SVN? Can't we add them as dependencies in the pom? I've noticed many jars been committed to dependencies. See [1] for few. Thanks. [1] A broker2/java/lib/org.eclipse.swt_3.4.1.v3449c.jar A broker2/java/lib/zookeeper-3.4.1.jar A broker2/java/lib/org.eclipse.core.contenttype_3.3.0.v20080604-1400.jar A broker2/java/lib/org.apache.felix.framework-2.0.5.jar A broker2/java/lib/org.eclipse.jface_3.4.1.M20080827-2000.jar A broker2/java/lib/guava-r08.jar A broker2/java/lib/mina-core-1.1.7.jar A broker2/java/lib/perf4j-0.9.12.wso2v1.jar -- regards, Nirmal Software Engineer, WSO2 Inc. mobile: +94715779733 ___ 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/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Why committing JARs to SVN repo?
On Mon, Jan 30, 2012 at 7:17 AM, Srinath Perera srin...@wso2.com wrote: Wathsala and Charith .. I think answer is we do not need to commit the jars .. just we have to fix the builds. Hi Srinath, Hasitha is currently working on this. Thanks Shammi Lets get them removed On Sun, Jan 29, 2012 at 7:44 PM, Nirmal Fernando nir...@wso2.com wrote: Hi, Do we really need to commit jar files to SVN? Can't we add them as dependencies in the pom? I've noticed many jars been committed to dependencies. See [1] for few. Thanks. [1] Abroker2/java/lib/org.eclipse.swt_3.4.1.v3449c.jar Abroker2/java/lib/zookeeper-3.4.1.jar A broker2/java/lib/org.eclipse.core.contenttype_3.3.0.v20080604-1400.jar Abroker2/java/lib/org.apache.felix.framework-2.0.5.jar Abroker2/java/lib/org.eclipse.jface_3.4.1.M20080827-2000.jar Abroker2/java/lib/guava-r08.jar Abroker2/java/lib/mina-core-1.1.7.jar Abroker2/java/lib/perf4j-0.9.12.wso2v1.jar -- regards, Nirmal Software Engineer, WSO2 Inc. mobile: +94715779733 ___ 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/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Best Regards,* Shammi Jayasinghe* Senior Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Why committing JARs to SVN repo?
You can get rid of most of these jars even though they are just there on the Qpid trunk. We used to have the minimum set of jars before. Ideally we should have maven dependency plugin downloading jars from Maven repo into the lib dir. Please take a look at [1]. [1] - http://stackoverflow.com/questions/1580562/maven-antrun-and-dependencies Danushka On Mon, Jan 30, 2012 at 7:17 AM, Srinath Perera srin...@wso2.com wrote: Wathsala and Charith .. I think answer is we do not need to commit the jars .. just we have to fix the builds. Lets get them removed On Sun, Jan 29, 2012 at 7:44 PM, Nirmal Fernando nir...@wso2.com wrote: Hi, Do we really need to commit jar files to SVN? Can't we add them as dependencies in the pom? I've noticed many jars been committed to dependencies. See [1] for few. Thanks. [1] Abroker2/java/lib/org.eclipse.swt_3.4.1.v3449c.jar Abroker2/java/lib/zookeeper-3.4.1.jar A broker2/java/lib/org.eclipse.core.contenttype_3.3.0.v20080604-1400.jar Abroker2/java/lib/org.apache.felix.framework-2.0.5.jar Abroker2/java/lib/org.eclipse.jface_3.4.1.M20080827-2000.jar Abroker2/java/lib/guava-r08.jar Abroker2/java/lib/mina-core-1.1.7.jar Abroker2/java/lib/perf4j-0.9.12.wso2v1.jar -- regards, Nirmal Software Engineer, WSO2 Inc. mobile: +94715779733 ___ 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/ ___ 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] Error when building System-test-framework in trunk
Hi, I'm getting following [1] error. How can I get rid of it? [1] Downloading: http://repo1.maven.org/maven2/com/oracle/ojdbc14/10.2.0.2.0/ojdbc14-10.2.0.2.0.jar [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 8:07.864s [INFO] Finished at: Sun Jan 29 21:30:51 IST 2012 [INFO] Final Memory: 19M/487M [INFO] [ERROR] Failed to execute goal on project platform-integration-core: Could not resolve dependencies for project org.wso2.platform:platform-integration-core:jar:4.0.0-SNAPSHOT: Could not find artifact com.oracle:ojdbc14:jar:10.2.0.2.0 in carbon-plugin-repo ( http://maven.wso2.org/nexus/content/repositories/wso2archtype) - [Help 1] -- 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] Inconsistencies in minimum password length requirement
Please fix this to do the password requirements validation from a single place. The length should be the same in all cases. -- Afkham Azeez Sent from my phone On Jan 28, 2012 10:27 AM, Nirmal Fernando nir...@wso2.com wrote: Hi, When you create a new domain in Stratos minimum password length requirement is 6, but after logged in when you adding a new user minimum password length requirement is 5 (which can only be seen in the error message pop up, when u enter a 5 character password). Is this a design decision? If we have this inconsistency isn't it better to add a tip mentioning minimum password length requirement when you create a new user. PS: this is related to issue at https://wso2.org/jira/browse/CARBON-12290 Thanks -- regards, Nirmal Software Engineer, WSO2 Inc. mobile: +94715779733 ___ 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] What is the correct required features version?
Hi All, What is the correct required features version that should go in for application-deployers descriptor file (required-features.xml)? [4.0.0, 5.0.0) ? Thanks, -- *Kishanthan Thangarajah* Software Engineer, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] What is the correct required features version?
On Mon, Jan 30, 2012 at 9:41 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi All, What is the correct required features version that should go in for application-deployers descriptor file (required-features.xml)? [4.0.0, 5.0.0) ? AFAIR, correct. what is the real issue ? (why this question) Thanks, -- *Kishanthan Thangarajah* Software Engineer, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ 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] Identity Server code needs some refactoring
Hi folks, Some of the code in identity components haven't evolved since it's first carbon migration... We need some refactoring in identity.core/identity.provider/identity.relyingparty components.. 1. We have centralized persistence code - identity.core - we need to move those logic to the corresponding components [This is same as the BIG PersistenceManager we had in Carbon] 2. OpenID/SAML2/XMPP code need to be separated out from the identity.provider code 3. Need to remove some data stored in registry and need to maintain a separate DB 4. We also need to maintain OpenID statistics and possibly write a BAM agent to publish those stats to BAM 5. Once we have [1] and [2] done - we can have a better set of Carbon features I am currently working on 1 and 2 - please let me know if you have any concerns... -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Error when building System-test-framework in trunk
Fixed. Thanks, Krishantha. On Mon, Jan 30, 2012 at 8:56 AM, Nirmal Fernando nir...@wso2.com wrote: Hi, I'm getting following [1] error. How can I get rid of it? [1] Downloading: http://repo1.maven.org/maven2/com/oracle/ojdbc14/10.2.0.2.0/ojdbc14-10.2.0.2.0.jar [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 8:07.864s [INFO] Finished at: Sun Jan 29 21:30:51 IST 2012 [INFO] Final Memory: 19M/487M [INFO] [ERROR] Failed to execute goal on project platform-integration-core: Could not resolve dependencies for project org.wso2.platform:platform-integration-core:jar:4.0.0-SNAPSHOT: Could not find artifact com.oracle:ojdbc14:jar:10.2.0.2.0 in carbon-plugin-repo ( http://maven.wso2.org/nexus/content/repositories/wso2archtype) - [Help 1] -- 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] What is the correct required features version?
On Mon, Jan 30, 2012 at 10:05 AM, Pradeep Fernando prad...@wso2.com wrote: On Mon, Jan 30, 2012 at 9:41 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi All, What is the correct required features version that should go in for application-deployers descriptor file (required-features.xml)? [4.0.0, 5.0.0) ? AFAIR, correct. what is the real issue ? (why this question) Because, in trunk, it is still pointing to [3.1.0, 4.0.0), so the application deployers will not deploy artifacts with 4.0.0-SNAPSHOT. So we need to update this in trunk. Thanks. Thanks, -- *Kishanthan Thangarajah* Software Engineer, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ 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 -- *Kishanthan Thangarajah* Software Engineer, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Identity Server code needs some refactoring
I found the security component could have some code level improvements. May be you need to add that to the list too. Rajika On Mon, Jan 30, 2012 at 10:13 AM, Prabath Siriwardena prab...@wso2.comwrote: Hi folks, Some of the code in identity components haven't evolved since it's first carbon migration... We need some refactoring in identity.core/identity.provider/identity.relyingparty components.. 1. We have centralized persistence code - identity.core - we need to move those logic to the corresponding components [This is same as the BIG PersistenceManager we had in Carbon] 2. OpenID/SAML2/XMPP code need to be separated out from the identity.provider code 3. Need to remove some data stored in registry and need to maintain a separate DB 4. We also need to maintain OpenID statistics and possibly write a BAM agent to publish those stats to BAM 5. Once we have [1] and [2] done - we can have a better set of Carbon features I am currently working on 1 and 2 - please let me know if you have any concerns... -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ 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] What is the correct required features version?
Hi, On Mon, Jan 30, 2012 at 9:41 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi All, What is the correct required features version that should go in for application-deployers descriptor file (required-features.xml)? [4.0.0, 5.0.0) ? how about, [4.0.0, 4.x.0) ? x - next major release version. thanks, Thanks, -- *Kishanthan Thangarajah* Software Engineer, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ 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 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] Identity Server code needs some refactoring
On Mon, Jan 30, 2012 at 5:24 AM, Rajika Kumarasiri raj...@wso2.com wrote: I found the security component could have some code level improvements. May be you need to add that to the list too. +1 Thanks regards, -Prabath Rajika On Mon, Jan 30, 2012 at 10:13 AM, Prabath Siriwardena prab...@wso2.comwrote: Hi folks, Some of the code in identity components haven't evolved since it's first carbon migration... We need some refactoring in identity.core/identity.provider/identity.relyingparty components.. 1. We have centralized persistence code - identity.core - we need to move those logic to the corresponding components [This is same as the BIG PersistenceManager we had in Carbon] 2. OpenID/SAML2/XMPP code need to be separated out from the identity.provider code 3. Need to remove some data stored in registry and need to maintain a separate DB 4. We also need to maintain OpenID statistics and possibly write a BAM agent to publish those stats to BAM 5. Once we have [1] and [2] done - we can have a better set of Carbon features I am currently working on 1 and 2 - please let me know if you have any concerns... -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ 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 -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Identity Server code needs some refactoring
On Mon, Jan 30, 2012 at 10:13 AM, Prabath Siriwardena prab...@wso2.comwrote: Hi folks, Some of the code in identity components haven't evolved since it's first carbon migration... We need some refactoring in identity.core/identity.provider/identity.relyingparty components.. 1. We have centralized persistence code - identity.core - we need to move those logic to the corresponding components [This is same as the BIG PersistenceManager we had in Carbon] 2. OpenID/SAML2/XMPP code need to be separated out from the identity.provider code 3. Need to remove some data stored in registry and need to maintain a separate DB 4. We also need to maintain OpenID statistics and possibly write a BAM agent to publish those stats to BAM 5. Once we have [1] and [2] done - we can have a better set of Carbon features I am currently working on 1 and 2 - please let me know if you have any concerns... +1. Thanks, Thilina -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ 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] What is the plan on fixing issues found by Sonar?
Hi, What frequency does Sonar run? It would be nice to see the fixes done after it was run on 9th Jan 2012 for the last time[1], reflected on the dashboard. [1] http://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-platform Thanks Regards, Keheliya On Mon, Jan 9, 2012 at 8:54 AM, Samisa Abeysinghe sam...@wso2.com wrote: On Mon, Jan 9, 2012 at 8:52 AM, Srinath Perera srin...@wso2.com wrote: Yes .. I think until we build confidence in people about these automation efforts and report, we should let go few problems undetected rather than risking fails positives and loosing confidence about the system. Can we make it such that, we have them all in one report and only those filtered ones in another? In other words, is the config global for all plans or per plan in Sonar? --Srinath On Mon, Jan 9, 2012 at 8:44 AM, Samisa Abeysinghe sam...@wso2.comwrote: On Mon, Jan 9, 2012 at 8:09 AM, Afkham Azeez az...@wso2.com wrote: Let's configure Sonar so that things like catching Throwable are ignored. But sometimes we loose the real trail due to this, do we not? On Mon, Jan 9, 2012 at 8:04 AM, Srinath Perera srin...@wso2.comwrote: There are some (e.g. catching throwble due to OSGI limitation as per chat with Azeez). May be there is a way to turn them off. I general, we should avoid false positives to get people to look at these seriously. --Srinath On Mon, Jan 9, 2012 at 7:05 AM, Samisa Abeysinghe sam...@wso2.comwrote: Whoever who is going to work on this, should focuse making critical count to zero, and then major ones to zero and so on. On Mon, Jan 9, 2012 at 6:58 AM, Afkham Azeez az...@wso2.com wrote: We need to have a hackathon like the FindBugs hackathon we had sometime back, and fix these issues. The team in office this week can start on this immediately. On Mon, Jan 9, 2012 at 6:36 AM, Samisa Abeysinghe sam...@wso2.comwrote: http://wso2.org/sonar/dashboard/index/156 There are way too many issues. What is the plan to fix those? Violations 22,761http://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-platform [image: 2-red-small] Rules compliance 88.6%http://wso2.org/sonar/drilldown/measures/156?highlight=weighted_violationsmetric=weighted_violations [image: Blocker] Blockerhttp://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-platform?priority=BLOCKER 0 [image: Critical] Criticalhttp://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-platform?priority=CRITICAL 607 [image: 2-red-small] [image: Major] Majorhttp://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-platform?priority=MAJOR 13,033 [image: 2-red-small] [image: Minor] Minorhttp://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-platform?priority=MINOR 6,705 [image: 2-red-small] [image: Info] Infohttp://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-platform?priority=INFO 2,416 [image: 2-red-small] 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 -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ 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 -- 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 -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org
Re: [Carbon-dev] redefining dependency version under component/feature modules
These are the versions repeatedly defined in the componets/pom.xml
-wso2carbon.version4.0.0-SNAPSHOT/wso2carbon.version
-axis2.wso2.version1.6.1.wso2v5/axis2.wso2.version
-axis2.version1.6.1-wso2v5/axis2.version
-axis2.osgi.version.range[1.6.1.wso2v1,
1.7.0)/axis2.osgi.version.range
-axiom.osgi.version.range[1.2.11.wso2v1,
1.3.0)/axiom.osgi.version.range
-synapse.version2.1.0-wso2v3/synapse.version
-axiom.wso2.version1.2.11.wso2v1/axiom.wso2.version
-wsdl4j.wso2.version1.6.2.wso2v2/wsdl4j.wso2.version
-
geronimo.stax.api.wso2.version1.0.1.wso2v1/geronimo.stax.api.wso2.version
-rampart.version1.6.1-wso2v2/rampart.version
-wss4j.version1.5.11.wso2v1/wss4j.version
-axis2-transports.version1.1.0-wso2v4/axis2-transports.version
-rampart.wso2.version1.6.1.wso2v2/rampart.wso2.version
These can be changed to
+wso2carbon.version${carbon.platform.version}/wso2carbon.version
+axis2.wso2.version${orbit.version.axis2}/axis2.wso2.version
+axis2.version${version.axis2}/axis2.version
+
axis2.osgi.version.range${imp.pkg.version.axis2}/axis2.osgi.version.range
+
axiom.osgi.version.range${orbit.version.axiom}/axiom.osgi.version.range
+synapse.version${version.synapse}/synapse.version
+axiom.wso2.version${orbit.version.axiom}/axiom.wso2.version
+wsdl4j.wso2.version${orbit.version.wsdl4j}/wsdl4j.wso2.version
+
geronimo.stax.api.wso2.version${orbit.version.geronimo-jms_1.1_spec}/geronimo.stax.api.wso2.version
+rampart.version${rampart.version}/rampart.version
+wss4j.version${orbit.version.wss4j}/wss4j.version
+
axis2-transports.version${version.axis2.transport}/axis2-transports.version
+
rampart.wso2.version${rampart.osgi.version}/rampart.wso2.version
But, ideally, above properties should not be there in the
components/pom.xml. They can be referred from the platform pom. But if we
remove them now, we'll have to modify some componet poms.
Another thing I found is, same version is repeated in the platform pom. For
example,
axis2.osgi.version1.6.1.wso2v5/axis2.osgi.version
orbit.version.axis21.6.1.wso2v5/orbit.version.axis2
rampart.version1.6.1-wso2v3/rampart.version
rampart.osgi.version1.6.1.wso2v3/rampart.osgi.version
There are few more.
Regards,
AmilaM.
On Mon, Jan 30, 2012 at 11:24 AM, Supun Malinga sup...@wso2.com wrote:
Hi,
On Mon, Jan 30, 2012 at 7:11 AM, Srinath Perera srin...@wso2.com wrote:
Jaggery guys please fix
Supun .. could you run a grep for [0-9.]*.wso2* and other similar
patterns to find other places we are not using platform pom version
and send a report?
attached, result of, $ grep -r [0-9.]*.wso2* . --include pom.xml
this is excluding dependencies and the platform pom.
Not all places need to be changed here. but there is quite a lot.
thanks,
We should do this time to time
On Mon, Jan 30, 2012 at 1:50 AM, Supun Malinga sup...@wso2.com wrote:
Hi devs,
Please always try to use the platform pom defined versions. Below is
only
some example of $subject. There is no need of redefining these
properties
since its already defined in parent poms.
./components/jaggery/pom.xml:
axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version
./components/hostobjects/pom.xml:
axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version
./features/jaggery/pom.xml:
axis2.wso2.version1.6.1.wso2v4/axis2.wso2.version
Also similar redundant definitions are in components/pom.xml, etc.
For eg: in components/pom.xml,
wso2carbon.version4.0.0-SNAPSHOT/wso2carbon.version
axis2.wso2.version1.6.1.wso2v5/axis2.wso2.version
axis2.version1.6.1-wso2v5/axis2.version
axis2.osgi.version.range[1.6.1.wso2v1,
1.7.0)/axis2.osgi.version.range
axiom.osgi.version.range[1.2.11.wso2v1,
1.3.0)/axiom.osgi.version.range
These are already defined in the platform pom. So why are we redefining?
thanks,
--
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
--
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
--
Supun Malinga,
Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 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
--
*Amila Maharachchi*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
