[Dev] WSO2 ELB is not there in the trunk
https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/ Where is the ELB? I want to test it with the new clustering implementation. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Improving Data Publisher Mediator to replace BAM Mediator
Currently there are lots of usability issues with BAM mediator, hence as an alternative we came up with the Data Publisher Mediator[1] as part of a client engagement. Data Publisher Mediator uses LoadBalancingDataPublisher to send events to BAM/CEP endpoints and it also supports XML configuration. The only drawback is that the Data Publisher Mediator doesn’t have a UI. I believe writing a UI to this mediator will enhance data publishing and solve the current usability issues that we are facing now. A sample XML configuration is as follows dataPublisher receiverUrltcp://localhost:7612/receiverUrl authenticatorUrlssl://localhost:7712/authenticatorUrl userNameadmin/userName passwordadmin/password streamNameAllLocationEvents/streamName streamVersion1.6.4/streamVersion attributes !-- meta attribute name=price type=string value=//m:price/ /meta-- payload attribute name=latitude type=double default=2.2 value=//m:latitude/ attribute name=longitude type=double default=67.78 value=//m:longitude/ attribute name=accuracy type=double value=//m:accuracy/ attribute name=updatedTime type=long value=//m:timestamp/ attribute name=device_uuid type=string value=//m:device-uuid/ /payload /attributes namespaces namespace prefix=m uri= http://schemas.google.com/latitude/2010/ /namespaces /dataPublisher Regards Suho [1]https://svn.wso2.org/repos/wso2/people/suho/data-publisher-mediator -- *S. Suhothayan * Associate Technical Lead, Management Committee Member, Data Technologies Team, *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan* * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Identity Server 4.5.0 - M2 build
Hi Darshana, I can not find identity-mgt.properties file in conf/security directory in this pack... Please make sure new pack contains it... Thanks, Asela. On Wed, Jun 5, 2013 at 6:00 PM, Asela Pathberiya as...@wso2.com wrote: On Fri, May 31, 2013 at 7:33 PM, Darshana Gunawardana darsh...@wso2.comwrote: Hi all, Please find the $subject at https://svn.wso2.org/repos/wso2/scratch/Identity-Server-4.5.0/M2/ and it contains number of bug fixes done during this week. I can not see registry browser UI in this build.. Is it issue with building? Please check Thanks, Asela. Thanks, Darshana. -- Forwarded message -- From: Hasini Gunasinghe has...@wso2.com Date: Fri, May 17, 2013 at 4:03 PM Subject: Identity Server 4.5.0 - M1 build To: dev@wso2.org dev@wso2.org, Prabath Siriwardana prab...@wso2.com, Asela Pathberiya as...@wso2.com, Suresh Attanayaka sur...@wso2.com, Johann Nallathamby joh...@wso2.com, Dulanja Liyanage dula...@wso2.com, Ishara Karunarathna isha...@wso2.com, Dinuka Malalanayake dinu...@wso2.com, Venura Kahawala ven...@wso2.com, Chamath Gunawardana chama...@wso2.com, Pushpalanka Rajaluxmie la...@wso2.com, Darshana Gunawardana darsh...@wso2.com Hi, Please find the $subject at https://svn.wso2.org/repos/wso2/scratch/Identity-Server-4.5.0/M1/ This is a milestone build from trunk after merging IS 4.1.1 improvements to trunk and fixing blocking issues related to tenant mgt, UI, jax webapps changes etc.. Currently the team is working on new features including following and bug fixes... - User Mgt configuration UI - Pushpalanka - Authenticator framework for OpenID, SAML2SSO, OAuth login - Ishara - New Permission API - Venura - Statistics for Identity Features - Darshana Branching will be done after the feature freeze. ChamathG, since you are getting familiarized with user.core code base, can you please test multiple user store feature and provide fixes as patches if any issues found? Thanks, Hasini. -- Regards, * Darshana Gunawardana *Software Engineer WSO2 Inc.; http://wso2.com* E-mail: darsh...@wso2.com **Mobile: +94718566859 *Lean . Enterprise . Middleware -- Thanks Regards, Asela Mobile : +94 777 625 933 -- Thanks Regards, Asela Mobile : +94 777 625 933 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Improving Data Publisher Mediator to replace BAM Mediator
On Thu, Jun 13, 2013 at 12:02 PM, Sriskandarajah Suhothayan s...@wso2.comwrote: Currently there are lots of usability issues with BAM mediator, hence as an alternative we came up with the Data Publisher Mediator[1] as part of a client engagement. We will fix most of the issues in BAM Mediator in the next release. If we are moving to new mediator, what are the new features available in the new one? Data Publisher Mediator uses LoadBalancingDataPublisher to send events to BAM/CEP endpoints and it also supports XML configuration. Present mediator also uses LoadBalancingDataPublisher to send events to BAM/CEP endpoints. Supporting XML configurations directly from the Synapse XML was the first plan we had when designing the BAM mediator. But as we wanted to configure all the server credential related configurations and stream definition related configuration related configuration in a one place. We have discussed about this topic in the mail thread BAM mediator for ESB. The future plan is to move all the stream related configuration into a single centralised server something like WSO2 Store. So supporting configuration inline in the synapse XML will ease the process in few mediators but will reduce the configurability as a whole. The only drawback is that the Data Publisher Mediator doesn’t have a UI. I believe writing a UI to this mediator will enhance data publishing and solve the current usability issues that we are facing now. A sample XML configuration is as follows dataPublisher receiverUrltcp://localhost:7612/receiverUrl authenticatorUrlssl://localhost:7712/authenticatorUrl userNameadmin/userName passwordadmin/password streamNameAllLocationEvents/streamName streamVersion1.6.4/streamVersion attributes !-- meta attribute name=price type=string value=//m:price/ /meta-- payload attribute name=latitude type=double default=2.2 value=//m:latitude/ attribute name=longitude type=double default=67.78 value=//m:longitude/ attribute name=accuracy type=double value=//m:accuracy/ attribute name=updatedTime type=long value=//m:timestamp/ attribute name=device_uuid type=string value=//m:device-uuid/ /payload /attributes namespaces namespace prefix=m uri= http://schemas.google.com/latitude/2010/ /namespaces /dataPublisher Regards Suho [1]https://svn.wso2.org/repos/wso2/people/suho/data-publisher-mediator -- *S. Suhothayan * Associate Technical Lead, Management Committee Member, Data Technologies Team, *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan* * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Identity Server 4.5.0 - M2 build
Noted On Thu, Jun 13, 2013 at 12:32 PM, Asela Pathberiya as...@wso2.com wrote: Hi Darshana, I can not find identity-mgt.properties file in conf/security directory in this pack... Please make sure new pack contains it... Thanks, Asela. On Wed, Jun 5, 2013 at 6:00 PM, Asela Pathberiya as...@wso2.com wrote: On Fri, May 31, 2013 at 7:33 PM, Darshana Gunawardana darsh...@wso2.comwrote: Hi all, Please find the $subject at https://svn.wso2.org/repos/wso2/scratch/Identity-Server-4.5.0/M2/ and it contains number of bug fixes done during this week. I can not see registry browser UI in this build.. Is it issue with building? Please check Thanks, Asela. Thanks, Darshana. -- Forwarded message -- From: Hasini Gunasinghe has...@wso2.com Date: Fri, May 17, 2013 at 4:03 PM Subject: Identity Server 4.5.0 - M1 build To: dev@wso2.org dev@wso2.org, Prabath Siriwardana prab...@wso2.com, Asela Pathberiya as...@wso2.com, Suresh Attanayaka sur...@wso2.com, Johann Nallathamby joh...@wso2.com, Dulanja Liyanage dula...@wso2.com, Ishara Karunarathna isha...@wso2.com, Dinuka Malalanayake dinu...@wso2.com, Venura Kahawala ven...@wso2.com, Chamath Gunawardana chama...@wso2.com, Pushpalanka Rajaluxmie la...@wso2.com, Darshana Gunawardana darsh...@wso2.com Hi, Please find the $subject at https://svn.wso2.org/repos/wso2/scratch/Identity-Server-4.5.0/M1/ This is a milestone build from trunk after merging IS 4.1.1 improvements to trunk and fixing blocking issues related to tenant mgt, UI, jax webapps changes etc.. Currently the team is working on new features including following and bug fixes... - User Mgt configuration UI - Pushpalanka - Authenticator framework for OpenID, SAML2SSO, OAuth login - Ishara - New Permission API - Venura - Statistics for Identity Features - Darshana Branching will be done after the feature freeze. ChamathG, since you are getting familiarized with user.core code base, can you please test multiple user store feature and provide fixes as patches if any issues found? Thanks, Hasini. -- Regards, * Darshana Gunawardana *Software Engineer WSO2 Inc.; http://wso2.com* E-mail: darsh...@wso2.com **Mobile: +94718566859 *Lean . Enterprise . Middleware -- Thanks Regards, Asela Mobile : +94 777 625 933 -- Thanks Regards, Asela Mobile : +94 777 625 933 -- Regards, * Darshana Gunawardana *Software Engineer WSO2 Inc.; http://wso2.com* E-mail: darsh...@wso2.com **Mobile: +94718566859 *Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Can we configure additional SSL configurations in NIOSSL Listener/Sender
Thanks... Actually i was looking for following whether protocol (TLS) that is passed to SSLContext is configurable via axis2.xml.. i guess not. SSLContext sslcontext = SSLContext.getInstance(TLS); Thanks, Asela. On Thu, Jun 13, 2013 at 10:25 AM, Jeewantha Dharmaparakrama jeewan...@wso2.com wrote: Hi Asela, We can add new configurations to it. I guess this answers your question. See how the parameters HostNameVerifier and CertificateRevocationVerifire are used in[1] final Parameter hvp = transportOut.getParameter(HostnameVerifier); final String hvs = hvp != null ? hvp.getValue().toString() : null; final Parameter cvp = transportOut.getParameter(CertificateRevocationVerifier); final String cvs = cvp != null ? cvp.getValue().toString() : null; [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/synapse/2.1.1-wso2v6/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/nhttp/config/ClientConnFactoryBuilder.java Jeewantha On Wed, Jun 12, 2013 at 7:42 PM, Asela Pathberiya as...@wso2.com wrote: Hi All, According to the NIOSSL listener/sender configuration in axis2.xml, we are supporting some parameters to configure. Are these only configurations that are supported by implementations? Or Can not we add new configurations to it? (such as sslProtocol that is supported by tomcat config) -- Thanks Regards, Asela Mobile : +94 777 625 933 -- Jeewantha Dharmaparakrama Software Engineer; WSO2, Inc.; http://wso2.com/ Phone : (+94) 774726790 Skype : prasad.jeewantha LinkedIn : http://www.linkedin.com/in/jeewanthad Twitter: https://twitter.com/jeewamp Blog: http://jeewanthad.blogspot.com/ -- Thanks Regards, Asela Mobile : +94 777 625 933 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test Failures in User core in kernel
Hi all, I have looked into this and this exception throws at * org.wso2.carbon.caching.core.BaseCache.clear(BaseCache.java:89)*. This seems like this happen because of the recent changes of caching strategy. Thanks On Thu, Jun 13, 2013 at 10:16 AM, Pulasthi Supun pulas...@wso2.com wrote: Hi Eranda, Yes these errors are in the trunk. Regards, Pulasthi On Thu, Jun 13, 2013 at 10:06 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Guys, Is this on trunk? thanks Eranda On Thu, Jun 13, 2013 at 10:02 AM, Pulasthi Supun pulas...@wso2.comwrote: Hi, Im also getting the same errors when building the user core i took a up just now and working on revision 174753. Tests in error: testTenantManager(org.wso2.carbon.user.core.tenant.TestTenantManager) testAddToCache(org.wso2.carbon.user.core.authorization.AuthorizationCacheTest) testAddCacheHit(org.wso2.carbon.user.core.authorization.AuthorizationCacheTest): Could not initialize class org.wso2.carbon.user.core.authorization.AuthorizationCache testStuff(org.wso2.carbon.user.core.authman.AdvancedPermissionTreeTest): nullType class java.lang.reflect.InvocationTargetException testStuff(org.wso2.carbon.user.core.jdbc.ReadOnlyJDBCRealmTest): nullType class java.lang.reflect.InvocationTargetException testStuff(org.wso2.carbon.user.core.jdbc.JDBCRealmTest): nullType class java.lang.reflect.InvocationTargetException testAuthorizationClearence(org.wso2.carbon.user.core.jdbc.JDBCRealmTest): Could not initialize class org.wso2.carbon.user.core.authorization.AuthorizationCache testStuff(org.wso2.carbon.user.core.jdbc.AdvancedJDBCRealmTest): nullType class java.lang.reflect.InvocationTargetException testStuff(org.wso2.carbon.user.core.jdbc.PermissionTest): nullType class java.lang.reflect.InvocationTargetException testStuff(org.wso2.carbon.user.core.jdbc.AdvancedReadOnlyJDBCRealmTest): nullType class java.lang.reflect.InvocationTargetException Regards, Pulasthi On Wed, Jun 12, 2013 at 4:20 PM, Shelan Perera she...@wso2.com wrote: Hi, I am in the 174710 and updated today as well. But i am still getting the errors. Should be a local one to me. Will build on a clean repo. Thanks On Wed, Jun 12, 2013 at 4:10 PM, Chamath Gunawardana chama...@wso2.com wrote: sorry. here its - http://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/org.wso2.carbon.user.core/src/test/resources Thanks, On Wed, Jun 12, 2013 at 4:01 PM, Shelan Perera she...@wso2.comwrote: Hi, Is you location correct ? Could you please give me the svn link? It seems it is not there. https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/org.wso2.carbon.user.core/ thanks On Wed, Jun 12, 2013 at 3:50 PM, Chamath Gunawardana chama...@wso2.com wrote: Hi Shelan, Seems its success for me. Is your h2 db in [1] got updated to latest? [1] - carbon/kernel/trunk/core/org.wso2.carbon.user.core/repository/database/WSO2CARBON_DB.h2.db Thanks, On Wed, Jun 12, 2013 at 3:30 PM, Shelan Perera she...@wso2.comwrote: Hi, I am getting the following when run with tests. --- T E S T S --- Running org.wso2.carbon.user.core.claim.AdvancedClaimManagerTest log4j:WARN No appenders could be found for logger (org.wso2.carbon.context.internal.CarbonContextDataHolder). log4j:WARN Please initialize the log4j system properly. Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.457 sec Running org.wso2.carbon.user.core.claim.ClaimDAOTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.753 sec Running org.wso2.carbon.user.core.authman.AdvancedPermissionTreeTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.03 sec FAILURE! Running org.wso2.carbon.user.core.authorization.AuthorizationCacheTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.001 sec FAILURE! Running org.wso2.carbon.user.core.jdbc.ReadOnlyJDBCRealmTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.039 sec FAILURE! Running org.wso2.carbon.user.core.jdbc.AdvancedJDBCRealmTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.905 sec FAILURE! Running org.wso2.carbon.user.core.jdbc.JDBCRealmTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.869 sec FAILURE! Running org.wso2.carbon.user.core.jdbc.AdvancedReadOnlyJDBCRealmTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.783 sec FAILURE! Running org.wso2.carbon.user.core.jdbc.PermissionTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.317 sec FAILURE! Running org.wso2.carbon.user.core.jdbc.JDBCConfigurationTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.wso2.carbon.user.core.tenant.TestTenantManager Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.719 sec
[Dev] Update 4.1.3 feature repository
Hi, 4.1.3 feature repo was missing and I have just created it. Respective product teams please update the repo. We need 4.1.3 p2-repo for trying out automation of feature management scenarios. QA team might also need this. Thanks, Krishantha. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Exclude product specific features from p2-repo
Hi all, We have a requirement to automate feature management use cases, in order to do that, having p2-repo build when running product integration tests is required. As I got to know, we cannot build complete p2-repo before product builds, since it depends on some product specific features. So in order to facilitate for feature mgt automation, can we just remove all product specific features from p2-repo, because those product features are mostly styles features or samples. AFAIK, don't have any real production use cases around those product specific features. Thanks, Krishantha. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Code Review Notes - Stratos 2 CLI Tool
Herewith I'm sending the notes for Stratos 2 CLI Tool Code Review Crucible Project: http://wso2.org/crucible/cru/WCP098-1http://www.google.com/url?q=http%3A%2F%2Fwso2.org%2Fcrucible%2Fcru%2FWCP098-1usd=2usg=AFQjCNGs8QcdUEG-7j7XKF-pNBDgodtSjA CLI Tool source code can be found [1]. jline2 [2] is used to handle console input and Apache Commons CLI [3] is used to handle command line arguments. Review Notes: 1. Need to print the usage for invalid options passed from the terminal. (I have already done this in commands. I missed this for the application) 2. It was questioned why slf4j is used instead of commons log. I explained that I have used slf4j since the CLI tool is a standalone application and it is easier to use logging methods in slf4j 3. Discussed the possibility of using CLI tool with Ant, Scripts. It should be possible since we take authentication details from the environment variables. 4. Purpose of policies command is not clear. Should rename appropriately. The Stratos Controller policy.xml file should also be renamed to reflect the meaning, i.e. autoscaling policy.xml 5. Discussed the use of privateRepo. Possibility of figuring out whether repository is private or public. Currently privateRepo is used to request authentication details. I have discussed some issues in a dev@mail thread with subject [Stratos2][UI Improvement] GIT related fields should come to one box. 6. CLI Tool should prompt username and password for Git Repository instead of printing an error message. Currently the CLI tool just prints an error saying authentication details are required, if the user has specified the given Git Repository URL as a private repository. 7. Should maintain consistency. We shouldn't use camel case for options. For example, privateRepo and repoURL in subscribe command. 8. In the help, it is good to give a URL to get detailed information about commands etc. (Can link Wiki docs) 9. Discussed to provide a manual page for CLI tool 10. Discussed the possibility of using make, make configure and make install to install the CLI tool. 11. Mention the Log4j log file location in Docs or README 12. Check instanceof the object, before casting directly to an Option. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/stratos/artifact-deployment-coordinator/org.wso2.carbon.adc.mgt.cli/2.1.3http://www.google.com/url?q=https%3A%2F%2Fsvn.wso2.org%2Frepos%2Fwso2%2Fcarbon%2Fplatform%2Fbranches%2F4.1.0%2Fcomponents%2Fstratos%2Fartifact-deployment-coordinator%2Forg.wso2.carbon.adc.mgt.cli%2F2.1.3usd=2usg=AFQjCNFbBIjL1joQDPoAAMtAy15jGL_Giw [2] http://jline.github.io/jline2/http://www.google.com/url?q=http%3A%2F%2Fjline.github.io%2Fjline2%2Fusd=2usg=AFQjCNHcJ2mxeFQg9OB74fqtHgothnpyyg [3] http://commons.apache.org/proper/commons-cli/http://www.google.com/url?q=http%3A%2F%2Fcommons.apache.org%2Fproper%2Fcommons-cli%2Fusd=2usg=AFQjCNF9JXf3S_XHPZqfg9Bs-34Q34UzCg -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware Twitter: http://twitter.com/chrishantha | LinkedIn: http://lk.linkedin.com/in/chrishantha/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Build failure in trunk stratos level
Hi, Today morning started building trunk from beginning (orbit, kernal and now platform). I'm getting following error. Please have a look at on. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 29.378s [INFO] Finished at: Thu Jun 13 14:59:36 IST 2013 [INFO] Final Memory: 498M/1385M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.adc.topology.mgt: Compilation failure: Compilation failure: [ERROR] /home/sanjeewa/carbon/trunk/trunk/components/stratos/artifact-deployment-coordinator/org.wso2.carbon.adc.topology.mgt/src/main/java/org/wso2/carbon/adc/topology/mgt/group/mgt/GroupMgtAgentBuilder.java:[64,39] cannot find symbol [ERROR] symbol : method addGroupManagementAgent(org.wso2.carbon.adc.topology.mgt.group.mgt.SubDomainAwareGroupManagementAgent,java.lang.String,java.lang.String,int) [ERROR] location: interface org.apache.axis2.clustering.ClusteringAgent [ERROR] /home/sanjeewa/carbon/trunk/trunk/components/stratos/artifact-deployment-coordinator/org.wso2.carbon.adc.topology.mgt/src/main/java/org/wso2/carbon/adc/topology/mgt/group/mgt/GroupMgtAgentBuilder.java:[85,27] cannot find symbol [ERROR] symbol : method addGroupManagementAgent(org.wso2.carbon.adc.topology.mgt.group.mgt.SubDomainAwareGroupManagementAgent,java.lang.String,java.lang.String,int) [ERROR] location: interface org.apache.axis2.clustering.ClusteringAgent [ERROR] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.adc.topology.mgt: Compilation failure Thanks, Sanjeewa. -- * * *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Integration test failures in AppServer trunk
Hi Azeez,
Noted and working on it.
Thanks.
On Thu, Jun 13, 2013 at 7:18 AM, Afkham Azeez az...@wso2.com wrote:
All Jaggery tests are failing due to a single root cause it seems:
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - ...
24 more
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - Caused
by: org.jaggeryjs.scriptengine.exceptions.ScriptException: A module cannot
be found with the specified name : ws
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.jaggeryjs.jaggery.core.manager.CommonManager.require(CommonManager.java:226)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.jaggeryjs.jaggery.core.manager.WebAppManager.require(WebAppManager.java:218)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
java.lang.reflect.Method.invoke(Method.java:597)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - ...
36 more
java.io.IOException: Server returned HTTP response code: 500 for URL:
http://localhost:9763/testapp/wsrequest.jag
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at
org.wso2.jaggery.integration.tests.hostObjects.WSRequestHostObjectTestCase.testWSRequestExist(WSRequestHostObjectTestCase.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:76)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
On Thu, Jun 13, 2013 at 7:13 AM, Afkham Azeez az...@wso2.com wrote:
Failed tests:
Re: [Dev] (no subject)
HI , Here is an update for the UI automation of the AppFactory covered User Stories 1. Log-in to App Factory 2. App Factory User Home details verification of the created application 3. Create an Application 4. Edit an Application 5. Basic application overview details verification 6. view application team verification 7. Add member to Team. 8. Repository Management.(this include branching the Application ) 9. Governing an application (Promoting in life Cycle Stages) 10. Complete Application Overview Verification. Uncovered User Stories 1. User registration - this is a email verification process and this has to be done manually. 2. view update user profile - this feature is not yet implemented 3. edit an Application - only the description could be edited 4. Delete an Application - application deletion feature is not yet implemented 5. configure data source resources - not yet implemented. To be covered 1. update team 2. configure database resources 3. configure data source resources 4. configure API resources 5. configure property resources 6. Application development 7. Build Application/deploy application 8. test application there are few user stories which should be verified manually (Obtain server logs,manage issues) working on a way to work on those areas.l regards Randika On Mon, Jun 3, 2013 at 2:27 PM, Shiroshica Kulatilake sh...@wso2.comwrote: Hi Randika, If that's the case - then OK ! A new version of the user stories has been posted to the WIP wireframe.. email thread. Thank you, Shiro On Mon, Jun 3, 2013 at 2:20 PM, Randika Ratnayake rand...@wso2.comwrote: hi Shiro, Development of this selenium tests are completely based on UI based functionality testing. one purpose of doing this is getting adhere to rapid UI change in our end. as you mentioned there would be a rework due to the UI changes, but will continue the UI automation in the Staging and tying to work out a mechanism to adhere to the UI changes Regards On Mon, Jun 3, 2013 at 2:02 PM, Shiroshica Kulatilake sh...@wso2.comwrote: Hi Randika, I have a few questions; 1. Will you be doing this based on the current UI's on staging ? 2. Would you be recording user movements ? 3. Would there be a functionality only test set which is not dependent on the UIs ? If the goal is to do this for the AF GA release there might be a bit of rework once the new front ends come. These are supposed to be released for QA incrementally (please see AF GA Release email thread). Letting you know before so that you can plan accordingly. Thank you, Shiro On Mon, Jun 3, 2013 at 1:31 PM, Randika Ratnayake rand...@wso2.comwrote: hi all , Selenium Automation test development is started for the AppFactory staging . will be referring the below attached user stories for the automation process. please update for any missing user stories / use case needed to automated to this thread. Regards -- Randika Ratnayake, Mobile : +94773-440677 rand...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867 -- Randika Ratnayake, Mobile : +94773-440677 rand...@wso2.com -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867 -- Randika Ratnayake, Mobile : +94773-440677 rand...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] App Factory Automation Status
HI , Here is an update for the UI automation of the AppFactory covered User Stories 1. Log-in to App Factory 2. App Factory User Home details verification of the created application 3. Create an Application 4. Edit an Application 5. Basic application overview details verification 6. view application team verification 7. Add member to Team. 8. Repository Management.(this include branching the Application ) 9. Governing an application (Promoting in life Cycle Stages) 10. Complete Application Overview Verification. Uncovered User Stories 1. User registration - this is a email verification process and this has to be done manually. 2. view update user profile - this feature is not yet implemented 3. edit an Application - only the description could be edited 4. Delete an Application - application deletion feature is not yet implemented 5. configure data source resources - not yet implemented. To be covered 1. update team 2. configure database resources 3. configure data source resources 4. configure API resources 5. configure property resources 6. Application development 7. Build Application/deploy application 8. test application there are few user stories which should be verified manually (Obtain server logs,manage issues) working on a way to work on those areas.l regards Randika -- Randika Ratnayake, Mobile : +94773-440677 rand...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] App Factory UI automation
Hi Randika, Thanks for the update. Lets pack completed test cases and give it to QA and Product team. So they and run the test suite for each update. Thanks, Krishantha. On Thu, Jun 13, 2013 at 5:07 PM, Randika Ratnayake rand...@wso2.com wrote: HI , Here is an update for the UI automation of the AppFactory covered User Stories 1. Log-in to App Factory 2. App Factory User Home details verification of the created application 3. Create an Application 4. Edit an Application 5. Basic application overview details verification 6. view application team verification 7. Add member to Team. 8. Repository Management.(this include branching the Application ) 9. Governing an application (Promoting in life Cycle Stages) 10. Complete Application Overview Verification. Uncovered User Stories 1. User registration - this is a email verification process and this has to be done manually. 2. view update user profile - this feature is not yet implemented 3. edit an Application - only the description could be edited 4. Delete an Application - application deletion feature is not yet implemented 5. configure data source resources - not yet implemented. To be covered 1. update team 2. configure database resources 3. configure data source resources 4. configure API resources 5. configure property resources 6. Application development 7. Build Application/deploy application 8. test application there are few user stories which should be verified manually (Obtain server logs,manage issues) working on a way to work on those areas.l regards Randika On Mon, Jun 3, 2013 at 2:27 PM, Shiroshica Kulatilake sh...@wso2.comwrote: Hi Randika, If that's the case - then OK ! A new version of the user stories has been posted to the WIP wireframe.. email thread. Thank you, Shiro On Mon, Jun 3, 2013 at 2:20 PM, Randika Ratnayake rand...@wso2.comwrote: hi Shiro, Development of this selenium tests are completely based on UI based functionality testing. one purpose of doing this is getting adhere to rapid UI change in our end. as you mentioned there would be a rework due to the UI changes, but will continue the UI automation in the Staging and tying to work out a mechanism to adhere to the UI changes Regards On Mon, Jun 3, 2013 at 2:02 PM, Shiroshica Kulatilake sh...@wso2.comwrote: Hi Randika, I have a few questions; 1. Will you be doing this based on the current UI's on staging ? 2. Would you be recording user movements ? 3. Would there be a functionality only test set which is not dependent on the UIs ? If the goal is to do this for the AF GA release there might be a bit of rework once the new front ends come. These are supposed to be released for QA incrementally (please see AF GA Release email thread). Letting you know before so that you can plan accordingly. Thank you, Shiro On Mon, Jun 3, 2013 at 1:31 PM, Randika Ratnayake rand...@wso2.comwrote: hi all , Selenium Automation test development is started for the AppFactory staging . will be referring the below attached user stories for the automation process. please update for any missing user stories / use case needed to automated to this thread. Regards -- Randika Ratnayake, Mobile : +94773-440677 rand...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867 -- Randika Ratnayake, Mobile : +94773-440677 rand...@wso2.com -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867 -- Randika Ratnayake, Mobile : +94773-440677 rand...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Integration test failures in AppServer trunk
Hi Piyum,
Please verify whether it has the proper AS_HOME/modules directory with
content. i.e. there should be child directories like ws within modules
directory.
On Thu, Jun 13, 2013 at 3:10 PM, Piyum Fernando pi...@wso2.com wrote:
Hi Azeez,
Noted and working on it.
Thanks.
On Thu, Jun 13, 2013 at 7:18 AM, Afkham Azeez az...@wso2.com wrote:
All Jaggery tests are failing due to a single root cause it seems:
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - ...
24 more
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - Caused
by: org.jaggeryjs.scriptengine.exceptions.ScriptException: A module cannot
be found with the specified name : ws
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.jaggeryjs.jaggery.core.manager.CommonManager.require(CommonManager.java:226)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.jaggeryjs.jaggery.core.manager.WebAppManager.require(WebAppManager.java:218)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
java.lang.reflect.Method.invoke(Method.java:597)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - ...
36 more
java.io.IOException: Server returned HTTP response code: 500 for URL:
http://localhost:9763/testapp/wsrequest.jag
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at
org.wso2.jaggery.integration.tests.hostObjects.WSRequestHostObjectTestCase.testWSRequestExist(WSRequestHostObjectTestCase.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:76)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at
[Dev] Why do we have different versions of axis2 in trunk...?
Please see https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/dependencies/axis2/ -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have different versions of axis2 in trunk...?
- we cant have two versions, we should remove one. However little complication here. We used to point the axis2 of trunk to current branched version of axis2 (say axis2-1.6wso2v1 of 4.1.0 branch) till we are done with releases in branch. Once we are done with releasing the branch we create 1.6.wso2v2 in the trunk. Now the situation is bit different. We are releasing in multiple branches. (4.1.0 and 4.2.0). I can't decide on a version number for axis2 in 4.2.0 branch since 4.1.0 branch development is in progress. However, since we are following a patching model in 4.1.0 kernel, there will not be any further versions of axis2 in 4.1.0 branch. Hence lets keep the 1.6.1-wso2v10 version, and remove other. thanks, --Pradeep On Thu, Jun 13, 2013 at 8:38 PM, Prabath Siriwardena prab...@wso2.comwrote: Please see https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/dependencies/axis2/ -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have different versions of axis2 in trunk...?
Hi Pradeep, On Thu, Jun 13, 2013 at 9:37 PM, Pradeep Fernando prad...@wso2.com wrote: - we cant have two versions, we should remove one. However little complication here. We used to point the axis2 of trunk to current branched version of axis2 (say axis2-1.6wso2v1 of 4.1.0 branch) till we are done with releases in branch. Once we are done with releasing the branch we create 1.6.wso2v2 in the trunk. Now the situation is bit different. We are releasing in multiple branches. (4.1.0 and 4.2.0). I can't decide on a version number for axis2 in 4.2.0 branch since 4.1.0 branch development is in progress. However, since we are following a patching model in 4.1.0 kernel, there will not be any further versions of axis2 in 4.1.0 branch. Hence lets keep the 1.6.1-wso2v10 version, and remove other. +1 , I did my json merge to 1.6.1-wso2v10. Actually not only axis2 , transport also has two versions and platform/dependencies/cassandra also has two versions. So we need to clean the trunk by removing all previous versions. We should have one version(latest version) of each dependencies in trunk. Thanks, Shamera. thanks, --Pradeep On Thu, Jun 13, 2013 at 8:38 PM, Prabath Siriwardena prab...@wso2.comwrote: Please see https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/dependencies/axis2/ -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.orgshame...@apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ESB Integration tests module compilation failure in trunk
Hi, I am getting the following error. It seems like clarity framework is out of date in trunk. Please have a look asap. [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSBrokerStartupTestCase.java:[36,12] cannot find symbol [ERROR] symbol : class JMSBrokerController [ERROR] location: class org.wso2.carbon.esb.jms.transport.test.JMSBrokerStartupTestCase [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSBrokerStartupTestCase.java:[101,12] cannot find symbol [ERROR] symbol : class JMSBrokerConfiguration [ERROR] location: class org.wso2.carbon.esb.jms.transport.test.JMSBrokerStartupTestCase [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[24,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[25,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[26,77] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.controller.config does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSQueueAsProxyEndpointTestCase.java:[24,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist Thanks, IsuruU -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB Integration tests module compilation failure in trunk
Yes. It is out of date. I will fix it On Thu, Jun 13, 2013 at 11:11 PM, Isuru Udana isu...@wso2.com wrote: Hi, I am getting the following error. It seems like clarity framework is out of date in trunk. Please have a look asap. [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSBrokerStartupTestCase.java:[36,12] cannot find symbol [ERROR] symbol : class JMSBrokerController [ERROR] location: class org.wso2.carbon.esb.jms.transport.test.JMSBrokerStartupTestCase [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSBrokerStartupTestCase.java:[101,12] cannot find symbol [ERROR] symbol : class JMSBrokerConfiguration [ERROR] location: class org.wso2.carbon.esb.jms.transport.test.JMSBrokerStartupTestCase [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[24,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[25,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[26,77] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.controller.config does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSQueueAsProxyEndpointTestCase.java:[24,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist Thanks, IsuruU -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB Integration tests module compilation failure in trunk
Fixed now. Thanks, Krishantha. On Thu, Jun 13, 2013 at 10:51 PM, Nuwan Wimalasekara nuw...@wso2.comwrote: Yes. It is out of date. I will fix it On Thu, Jun 13, 2013 at 11:11 PM, Isuru Udana isu...@wso2.com wrote: Hi, I am getting the following error. It seems like clarity framework is out of date in trunk. Please have a look asap. [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSBrokerStartupTestCase.java:[36,12] cannot find symbol [ERROR] symbol : class JMSBrokerController [ERROR] location: class org.wso2.carbon.esb.jms.transport.test.JMSBrokerStartupTestCase [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSBrokerStartupTestCase.java:[101,12] cannot find symbol [ERROR] symbol : class JMSBrokerConfiguration [ERROR] location: class org.wso2.carbon.esb.jms.transport.test.JMSBrokerStartupTestCase [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[24,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[25,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[26,77] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.controller.config does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSQueueAsProxyEndpointTestCase.java:[24,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist Thanks, IsuruU -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB Integration tests module compilation failure in trunk
However I cannot run the tests due to ESB startup failure. Thanks, Krishantha. On Thu, Jun 13, 2013 at 11:36 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Fixed now. Thanks, Krishantha. On Thu, Jun 13, 2013 at 10:51 PM, Nuwan Wimalasekara nuw...@wso2.comwrote: Yes. It is out of date. I will fix it On Thu, Jun 13, 2013 at 11:11 PM, Isuru Udana isu...@wso2.com wrote: Hi, I am getting the following error. It seems like clarity framework is out of date in trunk. Please have a look asap. [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSBrokerStartupTestCase.java:[36,12] cannot find symbol [ERROR] symbol : class JMSBrokerController [ERROR] location: class org.wso2.carbon.esb.jms.transport.test.JMSBrokerStartupTestCase [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSBrokerStartupTestCase.java:[101,12] cannot find symbol [ERROR] symbol : class JMSBrokerConfiguration [ERROR] location: class org.wso2.carbon.esb.jms.transport.test.JMSBrokerStartupTestCase [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[24,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[25,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSTransportProxyTestCase.java:[26,77] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.controller.config does not exist [ERROR] /media/isuru/WSO2/svn/public/trunk/platform/trunk/products/esb/modules/integration/tests/src/test/java/org/wso2/carbon/esb/jms/transport/test/JMSQueueAsProxyEndpointTestCase.java:[24,66] package org.wso2.carbon.automation.core.utils.jmsbrokerutils.client does not exist Thanks, IsuruU -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have a http proxy in the JMS to HTTP bridging sample (253)
Yeah, that should required to change, we need to stick to what header says..so ya as AmilaM mentioned that sample should need remodification.. JMS to HTTP and Replying with a 202 Accepted Responsehttp://docs.wso2.org/wiki/display/ESB460/Sample+253%3A+Bridging+from+JMS+to+HTTP+and+Replying+with+a+202+Accepted+Response On Wed, Jun 12, 2013 at 5:21 PM, Amila Maha Arachchi ami...@wso2.comwrote: You can find the sample at [1] [1] http://docs.wso2.org/wiki/display/ESB460/Sample+253%3A+Bridging+from+JMS+to+HTTP+and+Replying+with+a+202+Accepted+Response On Wed, Jun 12, 2013 at 5:21 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, Sample 253 of ESB is about bridging a message from JMS to HTTP. Sample documentation has two proxies defined. 1. proxy name=JMStoHTTPStockQuoteProxy transports=jms target inSequence property action=set name=OUT_ONLY value=true/ /inSequence endpoint address uri= http://localhost:9000/services/SimpleStockQuoteService;http://localhost:9000/services/SimpleStockQuoteService / /endpoint outSequence send/ /outSequence /target publishWSDL uri= file:repository/samples/resources/proxy/sample_proxy_1.wsdl/ /proxy Above proxy does the JMS to HTTP bridging and caters the sample's intention. 2. proxy name=OneWayProxy transports=http target inSequence log level=full/ /inSequence endpoint address uri= http://localhost:9000/services/SimpleStockQuoteService;http://localhost:9000/services/SimpleStockQuoteService / /endpoint outSequence send/ /outSequence /target publishWSDL uri= file:repository/samples/resources/proxy/sample_proxy_1.wsdl/ /proxy This is just a http proxy. Why have we put this proxy under this sample? For me it is irrelevant and confusing when going through the sample. WDYT? Regards, AmilaM. -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Build failure in API Manager - trunk
[INFO] Scanning for projects... [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.wso2.carbon:org.wso2.carbon.apimgt.api:4.2.0-SNAPSHOT (/usr/svn/wso2/trunk/platform/components/apimgt/org.wso2.carbon.apimgt.api/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.wso2.carbon:apimgt:pom:4.2.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 13, column 13 - [Help 2] -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Build failure in org.wso2.carbon.gadget.ide.ui - trunk - clean repo
[ERROR] No plugin found for prefix 'org.wso2.carbon.gadget.ide.ui' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/Users/prabath/.m3/repository), wso2-maven2-repository-1 ( http://dist.wso2.org/maven2), wso2-maven2-repository-2 ( http://dist.wso2.org/snapshots/maven2), central ( http://repo1.maven.org/maven2)] - [Help 1] org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix 'org.wso2.carbon.gadget.ide.ui' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/Users/prabath/.m3/repository), wso2-maven2-repository-1 (http://dist.wso2.org/maven2), wso2-maven2-repository-2 (http://dist.wso2.org/snapshots/maven2), central ( http://repo1.maven.org/maven2)] -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have different versions of axis2 in trunk...?
On Thu, Jun 13, 2013 at 9:30 AM, Shameera Rathnayaka shame...@wso2.comwrote: Hi Pradeep, On Thu, Jun 13, 2013 at 9:37 PM, Pradeep Fernando prad...@wso2.comwrote: - we cant have two versions, we should remove one. However little complication here. We used to point the axis2 of trunk to current branched version of axis2 (say axis2-1.6wso2v1 of 4.1.0 branch) till we are done with releases in branch. Once we are done with releasing the branch we create 1.6.wso2v2 in the trunk. Now the situation is bit different. We are releasing in multiple branches. (4.1.0 and 4.2.0). I can't decide on a version number for axis2 in 4.2.0 branch since 4.1.0 branch development is in progress. However, since we are following a patching model in 4.1.0 kernel, there will not be any further versions of axis2 in 4.1.0 branch. Hence lets keep the 1.6.1-wso2v10 version, and remove other. +1 , I did my json merge to 1.6.1-wso2v10. Actually not only axis2 , transport also has two versions and platform/dependencies/cassandra also has two versions. So we need to clean the trunk by removing all previous versions. We should have one version(latest version) of each dependencies in trunk. +1. Trunk should have only one version of dependencies. Another problem we have solved with patching model :) thanks, Amila. Thanks, Shamera. thanks, --Pradeep On Thu, Jun 13, 2013 at 8:38 PM, Prabath Siriwardena prab...@wso2.comwrote: Please see https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/dependencies/axis2/ -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.orgshame...@apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have different versions of axis2 in trunk...?
What if we move all orbits out of the main codebase? Any orbit project will immediately be graduated pushed to the Maven repo. Also, what if all dependencies that we change such as Axis2, Synapse, ODE etc. are maintained outside the mainstream repo, and those are built separately pushed as snapshots to the Maven repo until we do a release? Once we do a release, we can push the final fixed version. We don't need everybody building these. On Fri, Jun 14, 2013 at 8:40 AM, Amila Suriarachchi am...@wso2.com wrote: On Thu, Jun 13, 2013 at 9:30 AM, Shameera Rathnayaka shame...@wso2.comwrote: Hi Pradeep, On Thu, Jun 13, 2013 at 9:37 PM, Pradeep Fernando prad...@wso2.comwrote: - we cant have two versions, we should remove one. However little complication here. We used to point the axis2 of trunk to current branched version of axis2 (say axis2-1.6wso2v1 of 4.1.0 branch) till we are done with releases in branch. Once we are done with releasing the branch we create 1.6.wso2v2 in the trunk. Now the situation is bit different. We are releasing in multiple branches. (4.1.0 and 4.2.0). I can't decide on a version number for axis2 in 4.2.0 branch since 4.1.0 branch development is in progress. However, since we are following a patching model in 4.1.0 kernel, there will not be any further versions of axis2 in 4.1.0 branch. Hence lets keep the 1.6.1-wso2v10 version, and remove other. +1 , I did my json merge to 1.6.1-wso2v10. Actually not only axis2 , transport also has two versions and platform/dependencies/cassandra also has two versions. So we need to clean the trunk by removing all previous versions. We should have one version(latest version) of each dependencies in trunk. +1. Trunk should have only one version of dependencies. Another problem we have solved with patching model :) thanks, Amila. Thanks, Shamera. thanks, --Pradeep On Thu, Jun 13, 2013 at 8:38 PM, Prabath Siriwardena prab...@wso2.comwrote: Please see https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/dependencies/axis2/ -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.orgshame...@apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/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* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Integration test failures in AppServer trunk
Hi Ruchira,Azeez
We need to move some components and new test cases to the trunk. We are in
the process of doing it.
Will work on stabilizing the AppServer trunk once we done with moving.
Thanks.
On Thu, Jun 13, 2013 at 8:19 PM, Ruchira Wageesha ruch...@wso2.com wrote:
Hi Piyum,
Please verify whether it has the proper AS_HOME/modules directory with
content. i.e. there should be child directories like ws within modules
directory.
On Thu, Jun 13, 2013 at 3:10 PM, Piyum Fernando pi...@wso2.com wrote:
Hi Azeez,
Noted and working on it.
Thanks.
On Thu, Jun 13, 2013 at 7:18 AM, Afkham Azeez az...@wso2.com wrote:
All Jaggery tests are failing due to a single root cause it seems:
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - ...
24 more
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - Caused
by: org.jaggeryjs.scriptengine.exceptions.ScriptException: A module cannot
be found with the specified name : ws
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.jaggeryjs.jaggery.core.manager.CommonManager.require(CommonManager.java:226)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.jaggeryjs.jaggery.core.manager.WebAppManager.require(WebAppManager.java:218)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
java.lang.reflect.Method.invoke(Method.java:597)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - at
org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
[2013-06-13 07:10:38,292] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} - ...
36 more
java.io.IOException: Server returned HTTP response code: 500 for URL:
http://localhost:9763/testapp/wsrequest.jag
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at
org.wso2.jaggery.integration.tests.hostObjects.WSRequestHostObjectTestCase.testWSRequestExist(WSRequestHostObjectTestCase.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:76)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
[Dev] Trunk Build Status
I was able to build the trunk with a clean repo - after commenting out apimgmt and gadget-ide modules... Folks, please have a look at above two components.. -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Synapse version re-factoring in trunk
Hi All, 2.1.1-wso2v3 is the version we have in trunk for both synapse dependency and for the synapse features. I think this is wrong and we have to re-factor it to something like follows. For synapse dependency - 2.1.1-wso2v7-SNAPSHOT For synapse features - 4.2.0-SNAPSHOT This will going to be a significant re-factoring as we have to update many poms. Are the above suggested versions correct? If so, hall I proceed with this ? Thanks, IsuruU -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure in API Manager - trunk
Hi all; Please skip APIM component, we are in the middle of merging.. Will notify the thread once done! Thanks On 14 June 2013 10:17, Gihan Anuruddha gi...@wso2.com wrote: Getting same. Any update on this? On Fri, Jun 14, 2013 at 1:39 AM, Prabath Siriwardena prab...@wso2.comwrote: [INFO] Scanning for projects... [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.wso2.carbon:org.wso2.carbon.apimgt.api:4.2.0-SNAPSHOT (/usr/svn/wso2/trunk/platform/components/apimgt/org.wso2.carbon.apimgt.api/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.wso2.carbon:apimgt:pom:4.2.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 13, column 13 - [Help 2] -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- --- W.G. Gihan Anuruddha Senior Software Engineer | WSO2, Inc. M: +94772272595 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -Ratha mobile: (+94)755906608 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Trunk Build Status
gadget-ide module is no longer used by any products, I'll remove it from the components pom. On Fri, Jun 14, 2013 at 10:21 AM, Prabath Siriwardena prab...@wso2.comwrote: I was able to build the trunk with a clean repo - after commenting out apimgmt and gadget-ide modules... Folks, please have a look at above two components.. -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- With regards, *Manu*ranga Perera. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ELB is not there in the trunk
And I saw only AS is added into the build. On Thu, Jun 13, 2013 at 11:34 AM, Afkham Azeez az...@wso2.com wrote: https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/ Where is the ELB? I want to test it with the new clustering implementation. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure in API Manager - trunk
Please remove it from platform parent pom... Thanks regards, -Prabath On Fri, Jun 14, 2013 at 10:46 AM, Vijayaratha Vijayasingam rat...@wso2.comwrote: Hi all; Please skip APIM component, we are in the middle of merging.. Will notify the thread once done! Thanks On 14 June 2013 10:17, Gihan Anuruddha gi...@wso2.com wrote: Getting same. Any update on this? On Fri, Jun 14, 2013 at 1:39 AM, Prabath Siriwardena prab...@wso2.comwrote: [INFO] Scanning for projects... [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.wso2.carbon:org.wso2.carbon.apimgt.api:4.2.0-SNAPSHOT (/usr/svn/wso2/trunk/platform/components/apimgt/org.wso2.carbon.apimgt.api/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.wso2.carbon:apimgt:pom:4.2.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 13, column 13 - [Help 2] -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- --- W.G. Gihan Anuruddha Senior Software Engineer | WSO2, Inc. M: +94772272595 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -Ratha mobile: (+94)755906608 -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Improving Data Publisher Mediator to replace BAM Mediator
Hi Maninda, Reason for the new mediator is here Mediator for publishing event from ESB to BAM and CEP and Event Model. Above mediator was done so that it can be used to publish to BAM/ CEP/ and pub/sub brokers. Tharindu and BuddikaC was part of this chat, so BAM team knows. We cannot have two mediators to publish events out of ESB. Could Suho and you can have a chat? If it has all functionalities of the other, then it can replace. Otherwise, we have to merge. --Srinath On Thu, Jun 13, 2013 at 12:45 PM, Maninda Edirisooriya mani...@wso2.comwrote: On Thu, Jun 13, 2013 at 12:02 PM, Sriskandarajah Suhothayan s...@wso2.com wrote: Currently there are lots of usability issues with BAM mediator, hence as an alternative we came up with the Data Publisher Mediator[1] as part of a client engagement. We will fix most of the issues in BAM Mediator in the next release. If we are moving to new mediator, what are the new features available in the new one? Data Publisher Mediator uses LoadBalancingDataPublisher to send events to BAM/CEP endpoints and it also supports XML configuration. Present mediator also uses LoadBalancingDataPublisher to send events to BAM/CEP endpoints. Supporting XML configurations directly from the Synapse XML was the first plan we had when designing the BAM mediator. But as we wanted to configure all the server credential related configurations and stream definition related configuration related configuration in a one place. We have discussed about this topic in the mail thread BAM mediator for ESB. The future plan is to move all the stream related configuration into a single centralised server something like WSO2 Store. So supporting configuration inline in the synapse XML will ease the process in few mediators but will reduce the configurability as a whole. The only drawback is that the Data Publisher Mediator doesn’t have a UI. I believe writing a UI to this mediator will enhance data publishing and solve the current usability issues that we are facing now. A sample XML configuration is as follows dataPublisher receiverUrltcp://localhost:7612/receiverUrl authenticatorUrlssl://localhost:7712/authenticatorUrl userNameadmin/userName passwordadmin/password streamNameAllLocationEvents/streamName streamVersion1.6.4/streamVersion attributes !-- meta attribute name=price type=string value=//m:price/ /meta-- payload attribute name=latitude type=double default=2.2 value=//m:latitude/ attribute name=longitude type=double default=67.78 value=//m:longitude/ attribute name=accuracy type=double value=//m:accuracy/ attribute name=updatedTime type=long value=//m:timestamp/ attribute name=device_uuid type=string value=//m:device-uuid/ /payload /attributes namespaces namespace prefix=m uri= http://schemas.google.com/latitude/2010/ /namespaces /dataPublisher Regards Suho [1]https://svn.wso2.org/repos/wso2/people/suho/data-publisher-mediator -- *S. Suhothayan * Associate Technical Lead, Management Committee Member, Data Technologies Team, *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan* * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Srinath Perera, Ph.D. http://people.apache.org/~hemapani/ http://srinathsview.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have different versions of axis2 in trunk...?
On Fri, Jun 14, 2013 at 9:31 AM, Afkham Azeez az...@wso2.com wrote: What if we move all orbits out of the main codebase? Any orbit project will immediately be graduated pushed to the Maven repo. Also, what if all dependencies that we change such as Axis2, Synapse, ODE etc. are maintained outside the mainstream repo, and those are built separately pushed as snapshots to the Maven repo until we do a release? Once we do a release, we can push the final fixed version. We don't need everybody building these. This has a problem with patching. Lets say we release carbon 4.2.0 with axis2 1.6v10 and we need to patch some axis2 change for a later product release. Then we need to keep separate patch folder for all dependencies. Orbit bundles anyway in a separate repo. So we we can push oribit version to maven repo then no one wants to build the oribits. thanks, Amila. On Fri, Jun 14, 2013 at 8:40 AM, Amila Suriarachchi am...@wso2.comwrote: On Thu, Jun 13, 2013 at 9:30 AM, Shameera Rathnayaka shame...@wso2.comwrote: Hi Pradeep, On Thu, Jun 13, 2013 at 9:37 PM, Pradeep Fernando prad...@wso2.comwrote: - we cant have two versions, we should remove one. However little complication here. We used to point the axis2 of trunk to current branched version of axis2 (say axis2-1.6wso2v1 of 4.1.0 branch) till we are done with releases in branch. Once we are done with releasing the branch we create 1.6.wso2v2 in the trunk. Now the situation is bit different. We are releasing in multiple branches. (4.1.0 and 4.2.0). I can't decide on a version number for axis2 in 4.2.0 branch since 4.1.0 branch development is in progress. However, since we are following a patching model in 4.1.0 kernel, there will not be any further versions of axis2 in 4.1.0 branch. Hence lets keep the 1.6.1-wso2v10 version, and remove other. +1 , I did my json merge to 1.6.1-wso2v10. Actually not only axis2 , transport also has two versions and platform/dependencies/cassandra also has two versions. So we need to clean the trunk by removing all previous versions. We should have one version(latest version) of each dependencies in trunk. +1. Trunk should have only one version of dependencies. Another problem we have solved with patching model :) thanks, Amila. Thanks, Shamera. thanks, --Pradeep On Thu, Jun 13, 2013 at 8:38 PM, Prabath Siriwardena prab...@wso2.comwrote: Please see https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/dependencies/axis2/ -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/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* -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why do we have different versions of axis2 in trunk...?
Currently, orbit bundles are all over the place. Not in a single repo. On Fri, Jun 14, 2013 at 11:01 AM, Amila Suriarachchi am...@wso2.com wrote: On Fri, Jun 14, 2013 at 9:31 AM, Afkham Azeez az...@wso2.com wrote: What if we move all orbits out of the main codebase? Any orbit project will immediately be graduated pushed to the Maven repo. Also, what if all dependencies that we change such as Axis2, Synapse, ODE etc. are maintained outside the mainstream repo, and those are built separately pushed as snapshots to the Maven repo until we do a release? Once we do a release, we can push the final fixed version. We don't need everybody building these. This has a problem with patching. Lets say we release carbon 4.2.0 with axis2 1.6v10 and we need to patch some axis2 change for a later product release. Then we need to keep separate patch folder for all dependencies. Orbit bundles anyway in a separate repo. So we we can push oribit version to maven repo then no one wants to build the oribits. thanks, Amila. On Fri, Jun 14, 2013 at 8:40 AM, Amila Suriarachchi am...@wso2.comwrote: On Thu, Jun 13, 2013 at 9:30 AM, Shameera Rathnayaka shame...@wso2.comwrote: Hi Pradeep, On Thu, Jun 13, 2013 at 9:37 PM, Pradeep Fernando prad...@wso2.comwrote: - we cant have two versions, we should remove one. However little complication here. We used to point the axis2 of trunk to current branched version of axis2 (say axis2-1.6wso2v1 of 4.1.0 branch) till we are done with releases in branch. Once we are done with releasing the branch we create 1.6.wso2v2 in the trunk. Now the situation is bit different. We are releasing in multiple branches. (4.1.0 and 4.2.0). I can't decide on a version number for axis2 in 4.2.0 branch since 4.1.0 branch development is in progress. However, since we are following a patching model in 4.1.0 kernel, there will not be any further versions of axis2 in 4.1.0 branch. Hence lets keep the 1.6.1-wso2v10 version, and remove other. +1 , I did my json merge to 1.6.1-wso2v10. Actually not only axis2 , transport also has two versions and platform/dependencies/cassandra also has two versions. So we need to clean the trunk by removing all previous versions. We should have one version(latest version) of each dependencies in trunk. +1. Trunk should have only one version of dependencies. Another problem we have solved with patching model :) thanks, Amila. Thanks, Shamera. thanks, --Pradeep On Thu, Jun 13, 2013 at 8:38 PM, Prabath Siriwardena prab...@wso2.com wrote: Please see https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/dependencies/axis2/ -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/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* -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
