Re: [Dev] Please merge pull request to ESB
Can some one from ESB team merge this pull request ? . Seems like this is still pending. Regards On Fri, Dec 19, 2014 at 11:26 AM, Dimuthu De Lanerolle dimut...@wso2.com wrote: Hi ESB Team, Please merge the pull request [1] to ESB which adds script mediator related json payload tests. [1] https://github.com/wso2-dev/product-esb/pull/126 Regards -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Generating code coverage report for AF integration tests
Hi Amalka, In this case there are some jars you need to avoid from instrumenting as example all equinox jars. To take coverage in certain product you need only to instrument jars which are related to particular product. In Instrumentation EMMA what happens is it updates a metatag in jar so it changes MD5 sum and some times default permisions of jars. Use following filters in filter.txt to eliminate unwated jars form instrumenting -*.stub*-*.stub_-*.stub_4.0.0-*.stub--org.eclipse.*-*.equinox.* -org.wso2.carbon.user.core.*-samples.*-*.log4j*-*.axis2*-*.ui*-*.tenant* -*.stratos*-*.eventing*-*transports*-org.wso2.carbon.mediation.statistics* -*startup* Thank You, Dharshana. On Wed, Jan 14, 2015 at 12:17 PM, Amalka Subasinghe ama...@wso2.com wrote: Hi all, Currently I'm trying to $subject. Since AF integration tests runs in platform mode, we can't generate code coverage report via our existing test framework. I found a blog we can use for this. [1] as specified in the blog when I execute the xargs -n 1 $JAVA_HOME/jre/bin/java -cp emma.jar emma instr -m overwrite -cp jarlist.txt. It changes file permissions on appfactory jars, because of that I can't up the appfactory setup to run the tests. Does anyone have ideas on how to do this? [1] http://charithaka.blogspot.com/2009/05/run-time-code-coverage-using-emma.html Thanks Amalka ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94770342233 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Why not a JSP mapped to a url pattern in web.xml does not work with carbon 4.2.0
Hi All, I created a very simple web app with a single jsp, with following configuration in the deployment descriptor. servlet servlet-namelogin/servlet-name jsp-file/index.jsp/jsp-file /servlet servlet-mapping servlet-namelogin/servlet-name url-pattern/login.do/url-pattern /servlet-mapping Then I deployed this web app in three severs. Then accessed /sample-webapp/login.do and got following. *Tomcat* URL: http://localhost:8080/sample-webapp/login.do index.jsp was successfully rendered in the browser. *Carbon server with carbon version 4.2.0* URL: http://localhost:9763/sample-webapp/login.do Got HTTP 404 error *Carbon server with carbon version 4.3.0* URL: http://localhost:9763/sample-webapp/login.do index.jsp was successfully rendered in the browser. Here, when the jsp was mapped to a url pattern via web.xml it worked as expected in both tomcat and the carbon sever with carbon version 4.3.0. But it's not working on carbon 4.2.0 Does anybody know the reason for this behaviour ? Thanks, Malithi. -- *Malithi Edirisinghe* Senior Software Engineer WSO2 Inc. Mobile : +94 (0) 718176807 malit...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Generating code coverage report for AF integration tests
Here i'm giving required list of jars using jarlist file (I have attached the file).. In that case, do I still need to specify the filter.txt? On Fri, Jan 16, 2015 at 2:18 PM, Dharshana Warusavitharana dharsha...@wso2.com wrote: Hi Amalka, In this case there are some jars you need to avoid from instrumenting as example all equinox jars. To take coverage in certain product you need only to instrument jars which are related to particular product. In Instrumentation EMMA what happens is it updates a metatag in jar so it changes MD5 sum and some times default permisions of jars. Use following filters in filter.txt to eliminate unwated jars form instrumenting -*.stub*-*.stub_-*.stub_4.0.0-*.stub--org.eclipse.*-*.equinox.* -org.wso2.carbon.user.core.*-samples.*-*.log4j*-*.axis2*-*.ui*-*.tenant* -*.stratos*-*.eventing*-*transports*-org.wso2.carbon.mediation.statistics* -*startup* Thank You, Dharshana. On Wed, Jan 14, 2015 at 12:17 PM, Amalka Subasinghe ama...@wso2.com wrote: Hi all, Currently I'm trying to $subject. Since AF integration tests runs in platform mode, we can't generate code coverage report via our existing test framework. I found a blog we can use for this. [1] as specified in the blog when I execute the xargs -n 1 $JAVA_HOME/jre/bin/java -cp emma.jar emma instr -m overwrite -cp jarlist.txt. It changes file permissions on appfactory jars, because of that I can't up the appfactory setup to run the tests. Does anyone have ideas on how to do this? [1] http://charithaka.blogspot.com/2009/05/run-time-code-coverage-using-emma.html Thanks Amalka ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94770342233 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware -- Amalka Subasinghe WSO2 Inc. Mobile: +94 77 9401267 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issue in accessing OSGI of multiple versions
Hi,
I am currently developing a G-Reg feature[1] and for that I use a 3rd party
library called membrane-soa-model. This library uses Groovy 2.0 which needs
ASM 4. I created an osgi bundle for the membrane. If we run the Registry
server ASM 3 bundle also get Active as product-AS uses it. When both ASM 3
and ASM 4 bundles are in Active state my feature gives an error as membrane
accesses ASM3 bundle.
11 ACTIVE asm_3.1.0.wso2v1
12 ACTIVE asm_4.0_1.0.0
I want membrane OSGI to use ASM4 only, to achieve this I introduce ASM 4
with proper osgi versioning and introduce groovy and asm as
private-packages. But couldn't resolve the problem. Below is what I added
in membrane osgi POM,
instructions
Bundle-Name${project.artifactId}/Bundle-Name
Bundle-SymbolicName${project.groupId}.${project.artifactId}/Bundle-SymbolicName
Bundle-DescriptionOSGI version of ${project.name
}/Bundle-Description
Export-Packagecom.predic8.*/Export-Package
Private-Package
org.codehaus.groovy;version=2.0.4,
org.ow2.asm;version=4.0,
/Private-Package
Import-Package
!com.predic8.*,
!org.ow2.asm,
!org.codehaus.groovy,
*;resolution:=optional
/Import-Package
/instructions
What is the proper way to overcome this issue?
[1] https://redmine.wso2.com/issues/3403
--
--
Sithumini Senevirathne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware | wso2.com
email: sithumi...@wso2.com, mobile: +94 756977999
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] SSO component in Enterprise Store
Hi guys, There is a component called org.wso2.store.sso.common [1] in Enterprise store that is used by the sso jaggery module. This is bundled with the Store feature in ES. How can we add this component to CDM? [1] - https://github.com/wso2/product-es/tree/master/modules/components/sso-common Cheers~ -- Dulitha Wijewantha (Chan) Software Engineer - Mobile Development WSO2 Inc Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [API-M] Exception occurs while testing the Encrypting passwords process
Hi, I followed the Encrypting passwords documentation at [1] to test the scenario. While doing that I got the below mentioned exception. Exception in thread main org.wso2.ciphertool.CipherToolException: Element for secret alias 'APIManager.WorkFlowExtensions.ApplicationCreation.Password' can not be found in api-manager.xml file or You have entered invalid Xpath value at org.wso2.ciphertool.CipherTool.handleException(CipherTool.java:882) at org.wso2.ciphertool.CipherTool.writeTokenToConfigFile(CipherTool.java:501) at org.wso2.ciphertool.CipherTool.writeSecureVaultConfigTokens(CipherTool.java:395) at org.wso2.ciphertool.CipherTool.main(CipherTool.java:83) And looking in to it I figured out that this has a new implementation as it is moved on to registry. So this content should be removed from the documentation as well. [2] How is secure vault testing with workflows done now? And is there a documentation I can refer to test this flow? [1] - https://docs.wso2.com/display/AM170/Encrypting+Passwords [2] - https://wso2.org/jira/browse/DOCUMENTATION-1413 Thanks Regards, Kala https://docs.wso2.com/display/AM170/Encrypting+Passwords-- Kala C. Weerawardana *Software Engineer - QA Team* *WSO2 Inc. * Mobile : +94 (0) 716189886 +94 (0) 772877683 k...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AM] App Manager 1.0.0 Testing
Another blocking issue : https://wso2.org/jira/browse/APPM-331 - Cannot login to 'Publisher' and 'Store' when the server is running with a port offset. Will update the thread when we encounter more blockers. Thanks, Sandapa On Fri, Jan 16, 2015 at 12:47 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, We have assigned Ruwan Chathura for fixing issues. will check on those issues. Regards, Dinusha. On Fri, Jan 16, 2015 at 12:35 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, We are currently testing the wso2appm-1.0.0-ALPHA pack. We will use this thread to update the progress and issues. ATM we are facing some blocking issues and they have being reported at [1], @AM_Team please do the needful to fix these issues ASAP for us to continue the testing without any delays. [1] - *https://wso2.org/jira/issues/?filter=12103 https://wso2.org/jira/issues/?filter=12103* With Regards, -- Yasassri Ratnayake Software Engineer - QA WSO2 Inc ; http://wso2.com lean.enterprise.middleware *Mobile : +94715933168 %2B94715933168* *Blog : http://yasassriratnayake.blogspot.com/ http://yasassriratnayake.blogspot.com/* -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- Sandapa Handakumbura Associate Technical Lead WSO2.Inc. ; http://wso2.com/ M : +94777115866 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AM] App Manager 1.0.0 Testing
Hi Sandapa, On Fri, Jan 16, 2015 at 3:25 PM, Sandapa Handakumbura sand...@wso2.com wrote: Another blocking issue : https://wso2.org/jira/browse/APPM-331 - Cannot login to 'Publisher' and 'Store' when the server is running with a port offset. This is not a blocking issue. You need to update the port used in sso-idp-config.xml and SSOConfiguration section in app-manager.xml Regards, Dinusha. Will update the thread when we encounter more blockers. Thanks, Sandapa On Fri, Jan 16, 2015 at 12:47 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, We have assigned Ruwan Chathura for fixing issues. will check on those issues. Regards, Dinusha. On Fri, Jan 16, 2015 at 12:35 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, We are currently testing the wso2appm-1.0.0-ALPHA pack. We will use this thread to update the progress and issues. ATM we are facing some blocking issues and they have being reported at [1], @AM_Team please do the needful to fix these issues ASAP for us to continue the testing without any delays. [1] - *https://wso2.org/jira/issues/?filter=12103 https://wso2.org/jira/issues/?filter=12103* With Regards, -- Yasassri Ratnayake Software Engineer - QA WSO2 Inc ; http://wso2.com lean.enterprise.middleware *Mobile : +94715933168 %2B94715933168* *Blog : http://yasassriratnayake.blogspot.com/ http://yasassriratnayake.blogspot.com/* -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- Sandapa Handakumbura Associate Technical Lead WSO2.Inc. ; http://wso2.com/ M : +94777115866 -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fixed version dependencies feature installation
We are all in agreement that it would be best to go with fixed version dependencies when it comes to components orbit bundles, rather than depending on snapshots. This means, that two features living within the same product, may depend on two versions of the same bundle. We have to ensure that this works in order for our fixed dependency strategy to work. In the OSGi world, it is perfectly OK to have two different versions of the same bundle. However, when it comes to Carbon, we have to solve the following additional problems. 1. We need to be able to properly choose from which bundle and OSGi service is linked when there are multiple versions of the same bundle which expose the same OSGi service 2. Port binding - we have bundles that open ports. So, when there are two bundles that try to open the same server socket, there will be issues. We need to ensure that only one bundle opens the socket. Also, we need to ensure that data from these sockets gets dispatched to the correct code. 3. Connecting reading/writing to DBs - if there are multiple versions of the same bundle, both may try to write conflicting entries to the DBs. Need a strategy to ensure that only one bundle connects reads/writes. Thoughts welcome. -- *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 3320919blog: **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 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] [AM] App Manager 1.0.0 Testing
Thanks Dinusha. Please update the documentation with these information. Regards, Sandapa On Fri, Jan 16, 2015 at 3:33 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Sandapa, On Fri, Jan 16, 2015 at 3:25 PM, Sandapa Handakumbura sand...@wso2.com wrote: Another blocking issue : https://wso2.org/jira/browse/APPM-331 - Cannot login to 'Publisher' and 'Store' when the server is running with a port offset. This is not a blocking issue. You need to update the port used in sso-idp-config.xml and SSOConfiguration section in app-manager.xml Regards, Dinusha. Will update the thread when we encounter more blockers. Thanks, Sandapa On Fri, Jan 16, 2015 at 12:47 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi Yasassri, We have assigned Ruwan Chathura for fixing issues. will check on those issues. Regards, Dinusha. On Fri, Jan 16, 2015 at 12:35 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, We are currently testing the wso2appm-1.0.0-ALPHA pack. We will use this thread to update the progress and issues. ATM we are facing some blocking issues and they have being reported at [1], @AM_Team please do the needful to fix these issues ASAP for us to continue the testing without any delays. [1] - *https://wso2.org/jira/issues/?filter=12103 https://wso2.org/jira/issues/?filter=12103* With Regards, -- Yasassri Ratnayake Software Engineer - QA WSO2 Inc ; http://wso2.com lean.enterprise.middleware *Mobile : +94715933168 %2B94715933168* *Blog : http://yasassriratnayake.blogspot.com/ http://yasassriratnayake.blogspot.com/* -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- Sandapa Handakumbura Associate Technical Lead WSO2.Inc. ; http://wso2.com/ M : +94777115866 -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- Sandapa Handakumbura Associate Technical Lead WSO2.Inc. ; http://wso2.com/ M : +94777115866 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [BAM] Exception when run hive script with oracle
I am getting below exception when it runs hive scripts in BAM and this is
when using oracle for statdb. I followed [1] and only bam-datasource.xml
[1]
https://docs.wso2.com/display/AM170/Publishing+API+Runtime+Statistics#PublishingAPIRuntimeStatistics-ConfiguringWSO2BAM
[2015-01-16 16:08:48,303] ERROR
{org.wso2.carbon.hadoop.hive.jdbc.storage.db.DBOperation} - Failed to
write data to database
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)
at
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
at
oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:863)
at
oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1153)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1275)
at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3576)
at
oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3620)
at
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491)
at
org.wso2.carbon.hadoop.hive.jdbc.storage.db.DBOperation.isRowExisting(DBOperation.java:149)
at
org.wso2.carbon.hadoop.hive.jdbc.storage.db.DBOperation.writeToDB(DBOperation.java:59)
at
org.wso2.carbon.hadoop.hive.jdbc.storage.db.DBRecordWriter.write(DBRecordWriter.java:35)
at
org.apache.hadoop.hive.ql.exec.FileSinkOperator.processOp(FileSinkOperator.java:589)
at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:467)
at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:758)
at
org.apache.hadoop.hive.ql.exec.SelectOperator.processOp(SelectOperator.java:84)
at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:467)
at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:758)
at
org.apache.hadoop.hive.ql.exec.SelectOperator.processOp(SelectOperator.java:84)
at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:467)
at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:758)
at
org.apache.hadoop.hive.ql.exec.GroupByOperator.forward(GroupByOperator.java:964)
at
org.apache.hadoop.hive.ql.exec.GroupByOperator.closeOp(GroupByOperator.java:1016)
at org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:553)
at org.apache.hadoop.hive.ql.exec.ExecReducer.close(ExecReducer.java:304)
at org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:528)
at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:419)
at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:257)
I tried the below and couldn't solve this.
- manually deleting all virtual tables from bam mgt console.
- grant admin privileges to user in oracle.
create user spstatdb identified by spstatdb;
grant connect,resource to spstatdb with admin option;
commit;
- cleared all cassandra and h2 tables and restarted bam with -Dsetup.
- tried once invoked apis as well(cassandra db exists data to publish)
- Below datasource been placed in bam-datasource.xml
* datasource*
*nameWSO2AM_STATS_DB/name*
*descriptionThe datasource used for API Manager
database/description*
*jndiConfig*
*namejdbc/WSO2AM_STATS_DB/name*
*/jndiConfig*
* definition type=RDBMS*
*configuration*
* urljdbc:oracle:thin:@192.168.18.77:1521/ora11g
http://jdbc:oracle:thin:@192.168.18.77:1521/ora11g/url*
* usernameuname/username*
* passwordpword/password*
*
driverClassNameoracle.jdbc.driver.OracleDriver/driverClassName*
* maxActive50/maxActive*
* maxWait6/maxWait*
* testOnBorrowfalse/testOnBorrow*
* validationQuerySELECT 1/validationQuery*
* validationInterval3/validationInterval*
*/configuration*
*/definition*
* /datasource*
Any help please?
--
Thanks Regards
*Chaminda Jayawardena*
Senior Software Engineer - QA
WSO2 Inc. - http://wso2.com
+94-77-7725234
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fast Track Training Help - Hot deployment for Jaggery
Hi All, Is there a way to reflect changes to the server in a more convenient manner than uploading on every change? Please share your thoughts. Thanks! -- Thusitha Kalugamage *Software Engineer* Mobile : +94 (0) 774 074370 Tel : +94 (0) 112 145 345 thusi...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fast Track Training Help - Hot deployment for Jaggery
Hi, You don't have to upload on every change. just change the deployed files. or make a link with the deployed folder to your project. Thanks, On Fri, Jan 16, 2015 at 4:56 PM, Thusitha Kalugamage thusi...@wso2.com wrote: Hi All, Is there a way to reflect changes to the server in a more convenient manner than uploading on every change? Please share your thoughts. Thanks! -- Thusitha Kalugamage *Software Engineer* Mobile : +94 (0) 774 074370 Tel : +94 (0) 112 145 345 thusi...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 AppFactory 2.1.0 Alpha Released!
WSO2 AppFactory 2.1.0 Alpha Released! WSO2 AppFactory team is pleased to announce the release of version 2.1.0 Alpha of the WSO2 App Factory. WSO2 App Factory is a multi-tenant, elastic and self-service enterprise platform that enables multiple project teams to collaboratively create, run and manage enterprise applications. Combining complete application lifecycle management and Platform-as-a-Service (PaaS) capabilities, WSO2 App Factory makes it possible to develop, test, deploy to production and retire applications with a single click. It also provides an easy way to discover and consume apps and APIs through a user-friendly storefront. The distribution is available to download at [1] . Bug fixes in this release can be found at [2]. Puppet manifests for App Factory can be found at [3]. We encourage you to report issues, documentation faults and feature requests regarding WSO2 AppFactory through the public WSO2 AppFactory JIRA. [1] https://svn.wso2.org/repos/wso2/scratch/appfactorycc_tags/2.1.0-alpha/packs/wso2appfactory-2.1.0.zip [2] https://wso2.org/jira/issues/?jql=project%20%3D%20APPFAC%20AND%20fixVersion%20%3D%20%222.1.0%20Alpha%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20updated%20DESC [3] https://svn.wso2.org/repos/wso2/scratch/appfactorycc_tags/2.1.0-M7/turing/products/appfactory/2.1.0/modules/puppet-manifests/ *Kasun de Silva* Software Engineer | *WSO2 Inc.*; http://wso2.com lean.enterprise.middleware email : kas...@wso2.com mobile : +94 77 794 4260 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fast Track Training Help - Hot deployment for Jaggery
Yeap, it works! Thanks Rajith. On Fri, Jan 16, 2015 at 4:59 PM, Rajith Vitharana raji...@wso2.com wrote: Hi, You don't have to upload on every change. just change the deployed files. or make a link with the deployed folder to your project. Thanks, On Fri, Jan 16, 2015 at 4:56 PM, Thusitha Kalugamage thusi...@wso2.com wrote: Hi All, Is there a way to reflect changes to the server in a more convenient manner than uploading on every change? Please share your thoughts. Thanks! -- Thusitha Kalugamage *Software Engineer* Mobile : +94 (0) 774 074370 Tel : +94 (0) 112 145 345 thusi...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ -- Thusitha Kalugamage *Software Engineer* Mobile : +94 (0) 774 074370 Tel : +94 (0) 112 145 345 thusi...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] APP Manager - rest API for publisher login
Hi, Currently I am writing automated test for APP Manager. We use ES 1.0.0 in APP Manager and currently there is no rest end point to login to Publisher app. But ES 2.0.0-snapshot has an endpoint to login to publisher( https://localhost:9443/publisher/apis/authenticate https://www.google.com/url?q=https%3A%2F%2Flocalhost%3A9443%2Fpublisher%2Fapis%2Fauthenticatesa=Dsntz=1usg=AFQjCNEtrmT-Fqob5-8RdzVn4RS-Aocgsw ) curl --insecure --request POST https://localhost:9443/publisher/apis/authenticate https://www.google.com/url?q=https%3A%2F%2Flocalhost%3A9443%2Fpublisher%2Fapis%2Fauthenticatesa=Dsntz=1usg=AFQjCNEtrmT-Fqob5-8RdzVn4RS-Aocgsw --form 'username=admin' --form 'password=admin' So, to backport this to APP Manager ,can anyone point me to the code where this endpoint is implemented? -- Jenananthan Yogendran *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fwd: Invitation: [Code Review] MB CQL Store Upgrade @ Fri Jan 16, 2015 2:30pm - 3:30pm (Hemika Kodikara)
adding dev@ -- Forwarded message -- From: Hemika Kodikara hem...@wso2.com Date: Fri, Jan 16, 2015 at 4:02 PM Subject: Re: Invitation: [Code Review] MB CQL Store Upgrade @ Fri Jan 16, 2015 2:30pm - 3:30pm (Hemika Kodikara) To: Asitha Nanayakkara asi...@wso2.com Cc: Asanka Abeyweera asank...@wso2.com, Srinath Perera srin...@wso2.com, Indika Sampath indi...@wso2.com, Hasitha Amal De Silva hasit...@wso2.com, Madhawa Gunasekara madha...@wso2.com, Sajini De Silva saj...@wso2.com, Sewwandi Perera sewwa...@wso2.com, Ramith Jayasinghe ram...@wso2.com, Akalanka Pagoda Arachchi darsha...@wso2.com, Hasitha Hiranya hasit...@wso2.com, Pamod Sylvester pa...@wso2.com Hi All, Code Review notes are as follows. 1. Allow a retry policy. 2. Deciding which exceptions to throw when executing CQL commands. 3. If NetworkTopologyStratergy is different, how the initialization can be carried out. For now keeping it in simple mode. 4. Discussion on “isLive” implementation. 5. Discussion on change in table structure in cassandra. 6. Prepared statements usage changed for performance purposes. 7. Deciding to finalize the schema so that dropping the data wont be a problem in the future. 8. Finding out the use of “getMetaData” method and whether to refactor the method. Called through “AMQMessage constructor. 9. Discussing EXPIRATION_TIME in CQL expressions. 10. Discussing message counting for CQL with relative to RDBMS. Please correct the terminology if they are incorrect. Thanks, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 On Fri, Jan 16, 2015 at 1:48 PM, Asitha Nanayakkara asi...@wso2.com wrote: more details » https://www.google.com/calendar/event?action=VIEWeid=dGNndTlqbGRiYjhibm9mbW9uam44bXY4bTQgaGVtaWthQHdzbzIuY29ttok=MTUjYXNpdGhhQHdzbzIuY29tYjQzMWI1MDM3NzQzMTQ3ZDA3N2M0MTZjYmY5MWE5M2M1NWU3NjY1MQctz=Asia/Colombohl=en [Code Review] MB CQL Store Upgrade *When* Fri Jan 16, 2015 2:30pm – 3:30pm Colombo *Where* LK 3rd Floor Meeting Room - Kernel (map https://maps.google.lk/maps?q=LK+3rd+Floor+Meeting+Room+-+Kernelhl=en) *Video call* https://plus.google.com/hangouts/_/wso2.com/code-review-mb https://plus.google.com/hangouts/_/wso2.com/code-review-mb?hceid=YXNpdGhhQHdzbzIuY29t.tcgu9jldbb8bnofmonjn8mv8m4 *Calendar* Hemika Kodikara *Who* • Asitha Nanayakkara - organizer • Asanka Abeyweera • Srinath Perera • Indika Sampath • Hasitha Amal De Silva • Madhawa Gunasekara • Sajini De Silva • Sewwandi Perera • Ramith Jayasinghe • Hemika Kodikara • Akalanka Pagoda Arachchi • Hasitha Hiranya • Pamod Sylvester Going? *Yes https://www.google.com/calendar/event?action=RESPONDeid=dGNndTlqbGRiYjhibm9mbW9uam44bXY4bTQgaGVtaWthQHdzbzIuY29trst=1tok=MTUjYXNpdGhhQHdzbzIuY29tYjQzMWI1MDM3NzQzMTQ3ZDA3N2M0MTZjYmY5MWE5M2M1NWU3NjY1MQctz=Asia/Colombohl=en - Maybe https://www.google.com/calendar/event?action=RESPONDeid=dGNndTlqbGRiYjhibm9mbW9uam44bXY4bTQgaGVtaWthQHdzbzIuY29trst=3tok=MTUjYXNpdGhhQHdzbzIuY29tYjQzMWI1MDM3NzQzMTQ3ZDA3N2M0MTZjYmY5MWE5M2M1NWU3NjY1MQctz=Asia/Colombohl=en - No https://www.google.com/calendar/event?action=RESPONDeid=dGNndTlqbGRiYjhibm9mbW9uam44bXY4bTQgaGVtaWthQHdzbzIuY29trst=2tok=MTUjYXNpdGhhQHdzbzIuY29tYjQzMWI1MDM3NzQzMTQ3ZDA3N2M0MTZjYmY5MWE5M2M1NWU3NjY1MQctz=Asia/Colombohl=en* more options » https://www.google.com/calendar/event?action=VIEWeid=dGNndTlqbGRiYjhibm9mbW9uam44bXY4bTQgaGVtaWthQHdzbzIuY29ttok=MTUjYXNpdGhhQHdzbzIuY29tYjQzMWI1MDM3NzQzMTQ3ZDA3N2M0MTZjYmY5MWE5M2M1NWU3NjY1MQctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account hem...@wso2.com because you are subscribed for invitations on calendar Hemika Kodikara. To stop receiving these emails, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Wso2 developer studio 3.7.1 does not support maven project creation
Hi All, I downloaded a fresh pack of developer-studio-eclipse-jee-kepler-linux-gtk-x86_64-3.7.1.zip from wso2.com. After installing I tried to create a maven project and was given with the following error prompt. *The selected wizard could not be started.* *Plug-in org.eclipse.m2e.core.ui was unable to load class org.eclipse.m2e.core.ui.internal.wizards.MavenModuleWizard.* *An error occurred while automatically activating bundle org.eclipse.m2e.core.ui (522).* Is it regarding the m2e-WTP plugin that is installed? Any help on resolving this will be useful. Thanks Regards, Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 himas...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M] Exception occurs while testing the Encrypting passwords process
Hi Kala, On 16 January 2015 at 15:13, Kala Weerawardana k...@wso2.com wrote: Hi, I followed the Encrypting passwords documentation at [1] to test the scenario. While doing that I got the below mentioned exception. Exception in thread main org.wso2.ciphertool.CipherToolException: Element for secret alias 'APIManager.WorkFlowExtensions.ApplicationCreation.Password' can not be found in api-manager.xml file or You have entered invalid Xpath value at org.wso2.ciphertool.CipherTool.handleException(CipherTool.java:882) at org.wso2.ciphertool.CipherTool.writeTokenToConfigFile(CipherTool.java:501) at org.wso2.ciphertool.CipherTool.writeSecureVaultConfigTokens(CipherTool.java:395) at org.wso2.ciphertool.CipherTool.main(CipherTool.java:83) And looking in to it I figured out that this has a new implementation as it is moved on to registry. So this content should be removed from the documentation as well. [2] +1. Yes we need to. How is secure vault testing with workflows done now? Since the workflow configuration file is moved to registry, now we don't have a password encryption related functionality on that. Thanks, Lakmali And is there a documentation I can refer to test this flow? [1] - https://docs.wso2.com/display/AM170/Encrypting+Passwords [2] - https://wso2.org/jira/browse/DOCUMENTATION-1413 Thanks Regards, Kala https://docs.wso2.com/display/AM170/Encrypting+Passwords-- Kala C. Weerawardana *Software Engineer - QA Team* *WSO2 Inc. * Mobile : +94 (0) 716189886 +94 (0) 772877683 k...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [APIM] Use Nimbus for JWT token generation
Hi, org.wso2.carbon.apimgt.impl has manually build the JWT token. However I guess it is better to use Nimbuz standard library to easily generate the JWT token like [1]. Additionally there is an Nimbuz orbit bundle created now. [1] https://github.com/wso2-dev/carbon-identity/blob/master/components/identity/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/openidconnect/DefaultIDTokenBuilder.java -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery Server Feature installation fails in IS Server P2 profile
Try to build after updating Jaggery version to 0.9.0-SNAPSHOT On Fri, Jan 16, 2015 at 1:05 PM, Hasintha Indrajee hasin...@wso2.com wrote: Hi all, Please note $subject. Appreciate if someone from Jaggery team can attend to this. Refer the following trace for the error message logged. Cannot complete the install because one or more required items could not be found. Software being installed: Jaggery Server Feature 0.0.0.0_9_0_ALPHA5_wso2v1_SNAPSHOT (org.jaggeryjs.server.feature.group 0.0.0.0_9_0_ALPHA5_wso2v1_SNAPSHOT) Missing requirement: WSO2 Carbon - Addressing 4.3.0.SNAPSHOT (org.wso2.carbon.addressing 4.3.0.SNAPSHOT) requires 'package org.apache.axis2 [1.6.1.wso2v11-SNAPSHOT,1.7.0)' but it could not be found Cannot satisfy dependency: From: Jaggery Server Feature 0.0.0.0_9_0_ALPHA5_wso2v1_SNAPSHOT (org.jaggeryjs.server.feature.group 0.0.0.0_9_0_ALPHA5_wso2v1_SNAPSHOT) To: org.wso2.carbon.addressing [4.3.0.SNAPSHOT,4.4.0) -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : 1 4087864651 | 94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Urgent] [Greg] - Greg 5.0.0 server start up delays for several minutes
Hi APIM team After further looking into this with sameera. we found out that the org.wso2.carbon.apimgt.keymgt.stub structure and exports are wrong. The package structure does not have stub hence it exports org.wso2.carbon.apimgt.impl.dto.xsd which should be org.wso2.carbon.apimgt.stub.impl.dto.xsd. And the bundle exports org.wso2.carbon.apimgt.* and this should be org.wso2.carbon.apimgt.stub* since this is a stub bundle. Can someone from the API Manager team look into this an provide the necessary changes as soon as possible since this is blocking the Greg 5.0.0 M1 release. Regards, Pulasthi On Thu, Jan 15, 2015 at 5:09 PM, Prasanna Dangalla prasa...@wso2.com wrote: Hi apim team, Greg server hangs for several minutes after printing JAVA_HOME environment variable is set to /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home CARBON_HOME environment variable is set to /Users/prasanna/workspace/wso2/greg/git/prasanna/product-greg/modules/distribution/target/wso2greg-5.0.0-SNAPSHOT We debug in osgi console. Then we found following two apimanager osgi bundles were not started. 161INSTALLED org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT 165INSTALLED org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT diag 161 and diag 165 describes the following osgi diag 161 reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.internal_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. osgi diag 165 reference:file:../plugins/org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT.jar [165] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dao; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dto; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.handler_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.utils_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.valve_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.usage.publisher.internal_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. Leaf constraints in the dependency chain which are unresolved: reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161] Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. We also found that in repository/components/plugins org.wso2.carbon.apimgt.impl is contained in two jars as follows Binary file org.wso2.carbon.apimgt.impl_4.3.0.SNAPSHOT.jar matches Binary file org.wso2.carbon.apimgt.keymgt.stub_4.3.0.SNAPSHOT.jar matches Then we removed repository/components/plugins/org.wso2.carbon.apimgt.impl_4.3.0.SNAPSHOT.jar Then the server start up lag was not there and server starts up quickly, but several osgi bundles were not starting properly. Thanks -- Prasanna Dangalla Software Engineer, WSO2, Inc.; http://wso2.com/ lean.enterprise.middleware cell: +94 777 55 80 30 | +94 718 11 27 51 twitter: @prasa77 -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES] Errors while running server - latest build
Hi Ayesha,
This could be due to the following [1]. Could you check on with the app
factory team on their change on life cycle management which affects the
adding lifecycle to G-Reg? What I understood was this has caused issues in
adding lifecycle to G-Reg at start up. So that's why when trying to attach
the lifecycle it complains saying there's no lifecycle.
[1] https://github.com/wso2-dev/carbon-governance/pull/28/
[2] https://github.com/wso2-dev/carbon-governance/pull/23
[3] https://github.com/wso2-dev/product-greg/pull/55
regards
Shazni Nazeer
Senior Software Engineer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com
On Fri, Jan 16, 2015 at 2:58 AM, Ayesha Dissanayaka aye...@wso2.com wrote:
Hi,
I am getting below error at the server startup.
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} - Configuration
file name configurations not matched with aspect name ServiceLifeCycle
Further, life-cycles are not attached to the default assets. (with the
changes in carbon-governance
https://github.com/wso2/carbon-governance/commit/bf13572edc127faa7a54dd9636568d3c6f7ad014
)
ERROR {JAGGERY.config.app:js} - org.mozilla.javascript.WrappedException:
Wrapped org.wso2.carbon.governance.api.exception.GovernanceException: No
lifecycle associated with the artifact path /gadgets/admin/WSO2 Jira/1.0.0
(carbon/scripts/registry/artifacts.js#285)
at
org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0._c_anonymous_21(carbon/scripts/registry/artifacts.js:285)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0.call(carbon/scripts/registry/artifacts.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher..config.defaults.c0._c_onAttachLifecycle_13(/publisher//config/defaults/install.js:273)
at
org.jaggeryjs.rhino.publisher..config.defaults.c0.call(/publisher//config/defaults/install.js)
at
org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at
org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at
org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_16(/publisher/modules/asset.deployment.js:428)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_5(/publisher/modules/asset.deployment.js:166)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_9(/publisher/modules/asset.deployment.js:297)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c8._c_anonymous_13(/publisher/modules/bundler.js:168)
at
org.jaggeryjs.rhino.publisher.modules.c8.call(/publisher/modules/bundler.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_8(/publisher/modules/asset.deployment.js:283)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_7(/publisher/modules/asset.deployment.js:221)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c8._c_anonymous_13(/publisher/modules/bundler.js:168)
at
org.jaggeryjs.rhino.publisher.modules.c8.call(/publisher/modules/bundler.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_6(/publisher/modules/asset.deployment.js:212)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)
at
org.jaggeryjs.rhino.publisher.modules.c6._c_anonymous_3(/publisher/modules/publisher.js:101)
at
Re: [Dev] Please merge pull request to ESB
On Friday, 16 January 2015, Dimuthu De Lanerolle dimut...@wso2.com wrote: Can some one from ESB team merge this pull request ? . Seems like this is still pending. Regards On Fri, Dec 19, 2014 at 11:26 AM, Dimuthu De Lanerolle dimut...@wso2.com javascript:_e(%7B%7D,'cvml','dimut...@wso2.com'); wrote: Hi ESB Team, Please merge the pull request [1] to ESB which adds script mediator related json payload tests. [1] https://github.com/wso2-dev/product-esb/pull/126 Regards -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com javascript:_e(%7B%7D,'cvml','dimut...@wso2.com'); -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com javascript:_e(%7B%7D,'cvml','dimut...@wso2.com'); -- Dimuthu De Lanerolle Software Engineer WSO2 Inc. lean . enterprise . middlewear. http://wso2.com/ Tel. : +94 11 2145345 Fax : +94 11 2145300 email : dimut...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Wso2 developer studio 3.7.1 does not support maven project creation
Hi Himasha, Can you please state the Eclipse IDE that you have used to install DevS 3.7.1? DevS 3.7.1 is compatible with Eclipse Kepler and please make sure that you have used 'Eclipse Kepler SR2 for Java EE Developers' at [1]. You can also use the standalone DevS 3.7.1 which can be download as Binary at [2] [1] https://eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/keplersr2 [2] http://wso2.com/products/developer-studio/ Thanks, Sohani Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Fri, Jan 16, 2015 at 5:19 PM, Himasha Guruge himas...@wso2.com wrote: Hi All, I downloaded a fresh pack of developer-studio-eclipse-jee-kepler-linux-gtk-x86_64-3.7.1.zip from wso2.com. After installing I tried to create a maven project and was given with the following error prompt. *The selected wizard could not be started.* *Plug-in org.eclipse.m2e.core.ui was unable to load class org.eclipse.m2e.core.ui.internal.wizards.MavenModuleWizard.* *An error occurred while automatically activating bundle org.eclipse.m2e.core.ui (522).* Is it regarding the m2e-WTP plugin that is installed? Any help on resolving this will be useful. Thanks Regards, Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 himas...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Urgent] [Greg] - Greg 5.0.0 server start up delays for several minutes
Hi Pulasthi, I have made a pull request for above concern [1] Please have a review on it. But I am not clear about one thing which is , *The package structure does not have stub* could you please clarify more on the same?. Furthermore if below given pull request is wrong would it be possible to share a correct service stub repo for us to follow the same structure?. However I already followed [2] repo structure to create my pull request. [1] https://github.com/wso2-dev/carbon-apimgt/pull/16 [2] https://github.com/wso2-dev/carbon-governance/tree/master/service-stubs/governance/org.wso2.carbon.governance.lcm.stub Thanks. Regards Roshan. On Fri, Jan 16, 2015 at 7:56 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi APIM team After further looking into this with sameera. we found out that the org.wso2.carbon.apimgt.keymgt.stub structure and exports are wrong. The package structure does not have stub hence it exports org.wso2.carbon.apimgt.impl.dto.xsd which should be org.wso2.carbon.apimgt.stub.impl.dto.xsd. And the bundle exports org.wso2.carbon.apimgt.* and this should be org.wso2.carbon.apimgt.stub* since this is a stub bundle. Can someone from the API Manager team look into this an provide the necessary changes as soon as possible since this is blocking the Greg 5.0.0 M1 release. Regards, Pulasthi On Thu, Jan 15, 2015 at 5:09 PM, Prasanna Dangalla prasa...@wso2.com wrote: Hi apim team, Greg server hangs for several minutes after printing JAVA_HOME environment variable is set to /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home CARBON_HOME environment variable is set to /Users/prasanna/workspace/wso2/greg/git/prasanna/product-greg/modules/distribution/target/wso2greg-5.0.0-SNAPSHOT We debug in osgi console. Then we found following two apimanager osgi bundles were not started. 161INSTALLED org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT 165INSTALLED org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT diag 161 and diag 165 describes the following osgi diag 161 reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.internal_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. osgi diag 165 reference:file:../plugins/org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT.jar [165] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dao; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dto; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.handler_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.utils_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.valve_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.usage.publisher.internal_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. Leaf constraints in the dependency chain which are unresolved: reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161] Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. We also found that in repository/components/plugins org.wso2.carbon.apimgt.impl is contained in two jars as follows Binary file org.wso2.carbon.apimgt.impl_4.3.0.SNAPSHOT.jar matches Binary file org.wso2.carbon.apimgt.keymgt.stub_4.3.0.SNAPSHOT.jar matches Then we removed repository/components/plugins/org.wso2.carbon.apimgt.impl_4.3.0.SNAPSHOT.jar Then the server start up lag was not there and server starts
Re: [Dev] [ES] Errors while running server - latest build
Hi,
According to the comment at
https://github.com/wso2-dev/carbon-governance/pull/23, I noticed that
relevant file at *[ES_HOME]/repository/resources/lifecycles location *is
still configuration.xml. So I've changed it to ServiceLifeCycle.xml.
Then the earlier mentioned server startup error is not present.(shown below)
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} - Configuration
file name configurations not matched with aspect name ServiceLifeCycle
But the issue in attaching lifecycles with assets still persist.(Lifecycles
are not get attached to the artifacts)
Can app-factory team give us some light on this considering above
discussion, and the changes made to lifecycle management in above pull
requests.
Thanks!
-Ayesha
On Fri, Jan 16, 2015 at 8:58 PM, Shazni Nazeer sha...@wso2.com wrote:
Hi Ayesha,
This could be due to the following [1]. Could you check on with the app
factory team on their change on life cycle management which affects the
adding lifecycle to G-Reg? What I understood was this has caused issues in
adding lifecycle to G-Reg at start up. So that's why when trying to attach
the lifecycle it complains saying there's no lifecycle.
[1] https://github.com/wso2-dev/carbon-governance/pull/28/
[2] https://github.com/wso2-dev/carbon-governance/pull/23
[3] https://github.com/wso2-dev/product-greg/pull/55
regards
Shazni Nazeer
Senior Software Engineer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com
On Fri, Jan 16, 2015 at 2:58 AM, Ayesha Dissanayaka aye...@wso2.com
wrote:
Hi,
I am getting below error at the server startup.
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} - Configuration
file name configurations not matched with aspect name ServiceLifeCycle
Further, life-cycles are not attached to the default assets. (with the
changes in carbon-governance
https://github.com/wso2/carbon-governance/commit/bf13572edc127faa7a54dd9636568d3c6f7ad014
)
ERROR {JAGGERY.config.app:js} - org.mozilla.javascript.WrappedException:
Wrapped org.wso2.carbon.governance.api.exception.GovernanceException: No
lifecycle associated with the artifact path /gadgets/admin/WSO2 Jira/1.0.0
(carbon/scripts/registry/artifacts.js#285)
at
org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0._c_anonymous_21(carbon/scripts/registry/artifacts.js:285)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0.call(carbon/scripts/registry/artifacts.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher..config.defaults.c0._c_onAttachLifecycle_13(/publisher//config/defaults/install.js:273)
at
org.jaggeryjs.rhino.publisher..config.defaults.c0.call(/publisher//config/defaults/install.js)
at
org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at
org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at
org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_16(/publisher/modules/asset.deployment.js:428)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_5(/publisher/modules/asset.deployment.js:166)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_9(/publisher/modules/asset.deployment.js:297)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c8._c_anonymous_13(/publisher/modules/bundler.js:168)
at
org.jaggeryjs.rhino.publisher.modules.c8.call(/publisher/modules/bundler.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_8(/publisher/modules/asset.deployment.js:283)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_7(/publisher/modules/asset.deployment.js:221)
at
[Dev] [ES] Cannot browse registry with the latest build
Hi,
With the build today (16/01/2015) I can't browse the registry. I tried this
with a fresh pack and I'm getting the following error:
==
[2015-01-16 22:28:42,736] ERROR
{org.apache.catalina.core.ApplicationDispatcher} - Servlet.service() for
servlet bridgeservlet threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [24] in the generated java file:
[/home/buddhima/test/carbide/wso2es-2.0.0-SNAPSHOT/lib/tomcat/work/Catalina/localhost/_/proxytemp/hc_625652537/org/apache/jsp/lifecycles/lifecycles_005fajaxprocessor_jsp.java]
Only a type can be imported. org.apache.juddi.v3.error.RegistryException
resolves to a package
An error occurred at line: 181 in the jsp file:
/lifecycles/lifecycles_ajaxprocessor.jsp
RegistryException cannot be resolved to a type
178: LifecycleServiceClient lifecycleServiceClient = new
LifecycleServiceClient(config, session);
179:
180: bean = lifecycleServiceClient.getLifecycleBean(path);
181: } catch (RegistryException e) {
182: bean = null;
183: }
184:
Stacktrace:
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:103)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:366)
at
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:468)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:378)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
..
[2015-01-16 22:28:42,739] ERROR
{org.apache.catalina.core.ApplicationDispatcher} - Servlet.service() for
servlet bridgeservlet threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [24] in the generated java file:
[/home/buddhima/test/carbide/wso2es-2.0.0-SNAPSHOT/lib/tomcat/work/Catalina/localhost/_/proxytemp/hc_625652537/org/apache/jsp/lifecycles/lifecycles_005fajaxprocessor_jsp.java]
Only a type can be imported. org.apache.juddi.v3.error.RegistryException
resolves to a package
An error occurred at line: 181 in the jsp file:
/lifecycles/lifecycles_ajaxprocessor.jsp
RegistryException cannot be resolved to a type
178: LifecycleServiceClient lifecycleServiceClient = new
LifecycleServiceClient(config, session);
179:
180: bean = lifecycleServiceClient.getLifecycleBean(path);
181: } catch (RegistryException e) {
182: bean = null;
183: }
184:
Stacktrace:
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:103)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:366)
at
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:468)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:378)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
.
Would appreciate if someone can have a look at this issue since accessing
registry is really essential in many occasions.
Thank You!
--
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,
Mobile: +94 71 427 9966
Email: buddh...@wso2.com
Blog: https://buddhimawijeweera.wordpress.com
GitHub Profile: https://github.com/Buddhima
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES] Errors while running server - latest build
Hi Ayesha,
If there is no error in the start up, then the lifecycle aspects,
configured in the configuration file, should be loaded to the registry.
Could you please check through the management console whether the required
lifecycles are loaded?
Thanks.
Mahendran Pirinthapan
Software Engineer | WSO2 Inc.
Mobile +94772378732.
On Fri, Jan 16, 2015 at 10:08 PM, Ayesha Dissanayaka aye...@wso2.com
wrote:
Hi,
According to the comment at
https://github.com/wso2-dev/carbon-governance/pull/23, I noticed that
relevant file at *[ES_HOME]/repository/resources/lifecycles location *is
still configuration.xml. So I've changed it to ServiceLifeCycle.xml.
Then the earlier mentioned server startup error is not present.(shown
below)
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} - Configuration
file name configurations not matched with aspect name ServiceLifeCycle
But the issue in attaching lifecycles with assets still
persist.(Lifecycles are not get attached to the artifacts)
Can app-factory team give us some light on this considering above
discussion, and the changes made to lifecycle management in above pull
requests.
Thanks!
-Ayesha
On Fri, Jan 16, 2015 at 8:58 PM, Shazni Nazeer sha...@wso2.com wrote:
Hi Ayesha,
This could be due to the following [1]. Could you check on with the app
factory team on their change on life cycle management which affects the
adding lifecycle to G-Reg? What I understood was this has caused issues in
adding lifecycle to G-Reg at start up. So that's why when trying to attach
the lifecycle it complains saying there's no lifecycle.
[1] https://github.com/wso2-dev/carbon-governance/pull/28/
[2] https://github.com/wso2-dev/carbon-governance/pull/23
[3] https://github.com/wso2-dev/product-greg/pull/55
regards
Shazni Nazeer
Senior Software Engineer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com
On Fri, Jan 16, 2015 at 2:58 AM, Ayesha Dissanayaka aye...@wso2.com
wrote:
Hi,
I am getting below error at the server startup.
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} - Configuration
file name configurations not matched with aspect name ServiceLifeCycle
Further, life-cycles are not attached to the default assets. (with the
changes in carbon-governance
https://github.com/wso2/carbon-governance/commit/bf13572edc127faa7a54dd9636568d3c6f7ad014
)
ERROR {JAGGERY.config.app:js} -
org.mozilla.javascript.WrappedException: Wrapped
org.wso2.carbon.governance.api.exception.GovernanceException: No lifecycle
associated with the artifact path /gadgets/admin/WSO2 Jira/1.0.0
(carbon/scripts/registry/artifacts.js#285)
at
org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0._c_anonymous_21(carbon/scripts/registry/artifacts.js:285)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0.call(carbon/scripts/registry/artifacts.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher..config.defaults.c0._c_onAttachLifecycle_13(/publisher//config/defaults/install.js:273)
at
org.jaggeryjs.rhino.publisher..config.defaults.c0.call(/publisher//config/defaults/install.js)
at
org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at
org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at
org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_16(/publisher/modules/asset.deployment.js:428)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_5(/publisher/modules/asset.deployment.js:166)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_9(/publisher/modules/asset.deployment.js:297)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c8._c_anonymous_13(/publisher/modules/bundler.js:168)
at
org.jaggeryjs.rhino.publisher.modules.c8.call(/publisher/modules/bundler.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
Re: [Dev] Fwd: Pull request to include tenant deletion support
Hi, This feature will be merged into Kernel 4.4.0-SNAPSHOT. The downstream projects should depend on kernel 4.3.0. So, there won't be any build breaks. Further, repo is currently depending carbon-multitenancy kernel 4.3.0. So, we might have to wait until a release happens from that repo. Otherwise, we will have to create a parallel branch. On Fri, Jan 16, 2015 at 12:28 PM, Lakshman Udayakantha lakshm...@wso2.com wrote: Hi All, when I delete tenant in wso2as-6.0.0-SNAPSHOT, got the following exception Error executing query DELETE FROM UM_CLAIM_BEHAVIOR WHERE UM_TENANT_ID = ? for tenant: 1 org.h2.jdbc.JdbcSQLException: Table UM_CLAIM_BEHAVIOR not found; SQL statement: DELETE FROM UM_CLAIM_BEHAVIOR WHERE UM_TENANT_ID = ? [42102-140] at org.h2.message.DbException.getJdbcSQLException(DbException.java:327) at org.h2.message.DbException.get(DbException.java:167) seems like UM_CLAIM_BEHAVIOR table is not in database. How should I proceed in this case? On Thu, Jan 15, 2015 at 8:45 PM, Johann Nallathamby joh...@wso2.com wrote: Was this code reviewed ? The new method in the listener does not follow the same convention as others. It says onPreDelete, but other methods don't follow pre/post convention and you don't have hooks for all pre process actions. Can you please add pre process hooks for all the methods in that case ? Because if we miss to add it this time we won't be able to add it until next major release of this repo. So please use the opportunity to fix it. Also the comment on the interface is not correct. It says something specific to your implementation. On Wed, Jan 14, 2015 at 3:10 PM, Aruna Karunarathna ar...@wso2.com wrote: I believe we need to merge all these PR's related to tenant deletion at onetime coordinated manner. Otherwise there will be build breaks. Regards, Aruna On Wed, Jan 14, 2015 at 3:06 PM, Shashika Karunatilaka shashi...@wso2.com wrote: Hi all, I have created PRs for the respective repositories(I have added a comment in each PR). Please merge the Tenant deletion PRs and merge the following PRs. *carbon-multitenancy* JIRA : http://goog_2064092294/https://wso2.org/jira/browse/WSAS-1882 PR : https://github.com/wso2-dev/carbon-multitenancy/pull/16 *carbon-storage-management* JIRA : https://wso2.org/jira/browse/SS-454 https://github.com/wso2-dev/carbon-event-processing/pull/45 PR : https://github.com/wso2-dev/carbon-storage-management/pull/97 *carbon-event-processing* JIRA : https://wso2.org/jira/browse/CEP-1000 https://github.com/wso2-dev/carbon-event-processing/pull/45 PR : https://github.com/wso2-dev/carbon-event-processing/pull/45 *carbon-identity* JIRA : https://wso2.org/jira/browse/IDENTITY-2984 https://github.com/wso2-dev/carbon-event-processing/pull/45 PR : https://github.com/wso2-dev/carbon-identity/pull/63 Thank You On Mon, Jan 12, 2015 at 10:48 AM, Shashika Karunatilaka shashi...@wso2.com wrote: HI all, Below are my findings for the wso2 repos that uses the above listener class, please correct me if i missed any. Repo Componenent class carbon-multitenancy (org.wso2.carbon.theme.mgt.util) ThemeLoadingListener.java (org.wso2.carbon.keystore.mgt) KeystoreTenantMgtListener.java carbon-storage-management (org.wso2.carbon.cassandra.server) TenantCreationListener.java (org.wso2.carbon.hdfs.mgt) HDFSTenantCreationListener.java carbon-event-processing (org.wso2.carbon.event.stream.manager.core.internal.util.helper) TenantMgtListenerImpl.java carbon-identity (org.wso2.carbon.idp.mgt.internal ) TenantManagementListener.java (org.wso2.carbon.identity.application.authentication.framework.listener) AuthenticationEndpointTenantActivityListener.java product-af (org.wso2.carbon.appfactory.listners.tenant) AppFactoryTenantMgtListener.java (org.wso2.carbon.appfactory.s2.listeners) CloudEnvironmentPermissionListener.java (org.wso2.carbon.appfactory.stratos.listeners) CloudEnvironmentPermissionListener.java (org.wso2.carbon.appfactory.listners.tenant) DefaultRolesCreatorForTenant.java (org.wso2.carbon.appfactory.stratos.listeners) AppFactoryTenantKeyStoreMgtListener.java (org.wso2.carbon.appfactory.s2.listeners) AppFactoryTenantKeyStoreMgtListener.java (org.wso2.carbon.appfactory.listners.tenant) AppFactoryTenantActivationListener.java (org.wso2.carbon.appfactory.stratos.listeners) S2IntegrationTenantActivationListener.java (org.wso2.carbon.appfactory.s2.listeners) S2IntegrationTenantActivationListener.java private-paas (org.apache.stratos.theme.mgt.util) ThemeLoadingListener.java On Fri, Jan 9, 2015 at 8:47 PM, Shashika Karunatilaka shashi...@wso2.com wrote: Hi all, I will include newly added method to all respective repositories of *TenantMgtListener* interface, and also will create necessary JIRAs Thank you On Fri, Jan 9, 2015 at 1:02 PM, Lakshman Udayakantha lakshm...@wso2.com wrote: [fowarding to
Re: [Dev] [Urgent] [Greg] - Greg 5.0.0 server start up delays for several minutes
Hi Roshan, Could you get someone from the API manager team to review it and merge it as soon as possible. the governance lcm stub structure should be accurate. Best Regards, Pulasthi On Fri, Jan 16, 2015 at 10:03 PM, Roshan Wijesena ros...@wso2.com wrote: Hi Pulasthi, I have made a pull request for above concern [1] Please have a review on it. But I am not clear about one thing which is , *The package structure does not have stub* could you please clarify more on the same?. Furthermore if below given pull request is wrong would it be possible to share a correct service stub repo for us to follow the same structure?. However I already followed [2] repo structure to create my pull request. [1] https://github.com/wso2-dev/carbon-apimgt/pull/16 [2] https://github.com/wso2-dev/carbon-governance/tree/master/service-stubs/governance/org.wso2.carbon.governance.lcm.stub Thanks. Regards Roshan. On Fri, Jan 16, 2015 at 7:56 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi APIM team After further looking into this with sameera. we found out that the org.wso2.carbon.apimgt.keymgt.stub structure and exports are wrong. The package structure does not have stub hence it exports org.wso2.carbon.apimgt.impl.dto.xsd which should be org.wso2.carbon.apimgt.stub.impl.dto.xsd. And the bundle exports org.wso2.carbon.apimgt.* and this should be org.wso2.carbon.apimgt.stub* since this is a stub bundle. Can someone from the API Manager team look into this an provide the necessary changes as soon as possible since this is blocking the Greg 5.0.0 M1 release. Regards, Pulasthi On Thu, Jan 15, 2015 at 5:09 PM, Prasanna Dangalla prasa...@wso2.com wrote: Hi apim team, Greg server hangs for several minutes after printing JAVA_HOME environment variable is set to /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home CARBON_HOME environment variable is set to /Users/prasanna/workspace/wso2/greg/git/prasanna/product-greg/modules/distribution/target/wso2greg-5.0.0-SNAPSHOT We debug in osgi console. Then we found following two apimanager osgi bundles were not started. 161INSTALLED org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT 165INSTALLED org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT diag 161 and diag 165 describes the following osgi diag 161 reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.internal_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. osgi diag 165 reference:file:../plugins/org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT.jar [165] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dao; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dto; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.handler_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.utils_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.valve_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.usage.publisher.internal_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. Leaf constraints in the dependency chain which are unresolved: reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161] Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. We also found that in repository/components/plugins org.wso2.carbon.apimgt.impl is contained in two jars as follows Binary file
Re: [Dev] [APIM] Use Nimbus for JWT token generation
Hi, Also need to use Nimbuz for [1] since this is the default JWT builder in identity.xml TokenGeneratorImplClassorg.wso2.carbon.identity.oauth2.authcontext.JWTTokenGenerator/TokenGeneratorImplClass [1] https://github.com/wso2-dev/carbon-identity/blob/master/components/identity/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/authcontext/JWTTokenGenerator.java On Fri, Jan 16, 2015 at 5:36 PM, Udara Liyanage ud...@wso2.com wrote: Hi, org.wso2.carbon.apimgt.impl has manually build the JWT token. However I guess it is better to use Nimbuz standard library to easily generate the JWT token like [1]. Additionally there is an Nimbuz orbit bundle created now. [1] https://github.com/wso2-dev/carbon-identity/blob/master/components/identity/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/openidconnect/DefaultIDTokenBuilder.java -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Gayan Gunawardana Software Engineer; WSO2 Inc.; http://wso2.com/ Email: ga...@wso2.com Mobile: +94 (71) 8020933 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES] [APPM] Creating a duplicate assets exception is shown
Hi, ES 1.0.0 has a check which compares the value entered for the name field with the set of all assets of a given type to ensure that there is no duplicates.Can we check if this check is been performed? (If the value name does not contain a duplicate a green tick will be placed next to the field) Thank You, Sameera On Fri, Jan 16, 2015 at 1:44 AM, Chathura Dilan chathu...@wso2.com wrote: Hi, Regarding the issue[1], IMO this is a user error and this should not be shown to the backend as a exception. Exception should be thrown to the UI layer to handle. WDYT? [1]- https://wso2.org/jira/browse/APPM-310 -- Regards, Chatura Dilan Perera *(Senior Software Engineer** - WSO2 Inc.**)* www.dilan.me -- Sameera Medagammaddegedara Software Engineer Contact: Email: samee...@wso2.com Mobile: + 94 077 255 3005 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Urgent] [Greg] - Greg 5.0.0 server start up delays for several minutes
Hi NuwanD, Please review and merge https://github.com/wso2-dev/carbon-apimgt/pull/16 pull request to wso2-dev carbon-apimgt. Regards Roshan. On Sat, Jan 17, 2015 at 12:28 AM, Pulasthi Supun pulas...@wso2.com wrote: Hi Roshan, Could you get someone from the API manager team to review it and merge it as soon as possible. the governance lcm stub structure should be accurate. Best Regards, Pulasthi On Fri, Jan 16, 2015 at 10:03 PM, Roshan Wijesena ros...@wso2.com wrote: Hi Pulasthi, I have made a pull request for above concern [1] Please have a review on it. But I am not clear about one thing which is , *The package structure does not have stub* could you please clarify more on the same?. Furthermore if below given pull request is wrong would it be possible to share a correct service stub repo for us to follow the same structure?. However I already followed [2] repo structure to create my pull request. [1] https://github.com/wso2-dev/carbon-apimgt/pull/16 [2] https://github.com/wso2-dev/carbon-governance/tree/master/service-stubs/governance/org.wso2.carbon.governance.lcm.stub Thanks. Regards Roshan. On Fri, Jan 16, 2015 at 7:56 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi APIM team After further looking into this with sameera. we found out that the org.wso2.carbon.apimgt.keymgt.stub structure and exports are wrong. The package structure does not have stub hence it exports org.wso2.carbon.apimgt.impl.dto.xsd which should be org.wso2.carbon.apimgt.stub.impl.dto.xsd. And the bundle exports org.wso2.carbon.apimgt.* and this should be org.wso2.carbon.apimgt.stub* since this is a stub bundle. Can someone from the API Manager team look into this an provide the necessary changes as soon as possible since this is blocking the Greg 5.0.0 M1 release. Regards, Pulasthi On Thu, Jan 15, 2015 at 5:09 PM, Prasanna Dangalla prasa...@wso2.com wrote: Hi apim team, Greg server hangs for several minutes after printing JAVA_HOME environment variable is set to /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home CARBON_HOME environment variable is set to /Users/prasanna/workspace/wso2/greg/git/prasanna/product-greg/modules/distribution/target/wso2greg-5.0.0-SNAPSHOT We debug in osgi console. Then we found following two apimanager osgi bundles were not started. 161INSTALLED org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT 165INSTALLED org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT diag 161 and diag 165 describes the following osgi diag 161 reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.internal_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. osgi diag 165 reference:file:../plugins/org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT.jar [165] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dao; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dto; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.handler_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.utils_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.valve_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.usage.publisher.internal_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. Leaf constraints in the dependency chain which are unresolved: reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161]
Re: [Dev] SSO component in Enterprise Store
If this a re-usable component, why don't we take it out of the store specific bits and make it available a separate feature? Cheers, Prabath On Fri, Jan 16, 2015 at 3:10 PM, Dulitha Wijewantha duli...@wso2.com wrote: Hi guys, There is a component called org.wso2.store.sso.common [1] in Enterprise store that is used by the sso jaggery module. This is bundled with the Store feature in ES. How can we add this component to CDM? [1] - https://github.com/wso2/product-es/tree/master/modules/components/sso-common Cheers~ -- Dulitha Wijewantha (Chan) Software Engineer - Mobile Development WSO2 Inc Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES] Cannot browse registry with the latest build
Hi Buddima,
We are also facing above errors when browsing assets in the management
console.
I am not sure whether these are related to the changes discussed in the
thread [Dev][ES] Errors while running server - latest build
We are currently trying to fix this with Shazni and SameeraM.
Thanks!
- Ayesha
On Fri, Jan 16, 2015 at 10:38 PM, Buddhima Wijeweera buddh...@wso2.com
wrote:
Hi,
With the build today (16/01/2015) I can't browse the registry. I tried
this with a fresh pack and I'm getting the following error:
==
[2015-01-16 22:28:42,736] ERROR
{org.apache.catalina.core.ApplicationDispatcher} - Servlet.service() for
servlet bridgeservlet threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [24] in the generated java file:
[/home/buddhima/test/carbide/wso2es-2.0.0-SNAPSHOT/lib/tomcat/work/Catalina/localhost/_/proxytemp/hc_625652537/org/apache/jsp/lifecycles/lifecycles_005fajaxprocessor_jsp.java]
Only a type can be imported. org.apache.juddi.v3.error.RegistryException
resolves to a package
An error occurred at line: 181 in the jsp file:
/lifecycles/lifecycles_ajaxprocessor.jsp
RegistryException cannot be resolved to a type
178: LifecycleServiceClient lifecycleServiceClient = new
LifecycleServiceClient(config, session);
179:
180: bean = lifecycleServiceClient.getLifecycleBean(path);
181: } catch (RegistryException e) {
182: bean = null;
183: }
184:
Stacktrace:
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:103)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:366)
at
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:468)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:378)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
..
[2015-01-16 22:28:42,739] ERROR
{org.apache.catalina.core.ApplicationDispatcher} - Servlet.service() for
servlet bridgeservlet threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [24] in the generated java file:
[/home/buddhima/test/carbide/wso2es-2.0.0-SNAPSHOT/lib/tomcat/work/Catalina/localhost/_/proxytemp/hc_625652537/org/apache/jsp/lifecycles/lifecycles_005fajaxprocessor_jsp.java]
Only a type can be imported. org.apache.juddi.v3.error.RegistryException
resolves to a package
An error occurred at line: 181 in the jsp file:
/lifecycles/lifecycles_ajaxprocessor.jsp
RegistryException cannot be resolved to a type
178: LifecycleServiceClient lifecycleServiceClient = new
LifecycleServiceClient(config, session);
179:
180: bean = lifecycleServiceClient.getLifecycleBean(path);
181: } catch (RegistryException e) {
182: bean = null;
183: }
184:
Stacktrace:
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:103)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:366)
at
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:468)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:378)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
.
Would appreciate if someone can have a look at this issue since accessing
registry is really essential in many occasions.
Thank You!
--
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,
Mobile: +94 71 427 9966
Email: buddh...@wso2.com
Blog: https://buddhimawijeweera.wordpress.com
GitHub Profile: https://github.com/Buddhima
Re: [Dev] Wso2 developer studio 3.7.1 does not support maven project creation
Hi Sohani, Eclipse IDE version I'm using is Eclipse Kepler. Will try out the standalone version. Thanks Regards, Himasha On Fri, Jan 16, 2015 at 9:36 PM, Sohani Weerasinghe soh...@wso2.com wrote: Hi Himasha, Can you please state the Eclipse IDE that you have used to install DevS 3.7.1? DevS 3.7.1 is compatible with Eclipse Kepler and please make sure that you have used 'Eclipse Kepler SR2 for Java EE Developers' at [1]. You can also use the standalone DevS 3.7.1 which can be download as Binary at [2] [1] https://eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/keplersr2 [2] http://wso2.com/products/developer-studio/ Thanks, Sohani Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Fri, Jan 16, 2015 at 5:19 PM, Himasha Guruge himas...@wso2.com wrote: Hi All, I downloaded a fresh pack of developer-studio-eclipse-jee-kepler-linux-gtk-x86_64-3.7.1.zip from wso2.com. After installing I tried to create a maven project and was given with the following error prompt. *The selected wizard could not be started.* *Plug-in org.eclipse.m2e.core.ui was unable to load class org.eclipse.m2e.core.ui.internal.wizards.MavenModuleWizard.* *An error occurred while automatically activating bundle org.eclipse.m2e.core.ui (522).* Is it regarding the m2e-WTP plugin that is installed? Any help on resolving this will be useful. Thanks Regards, Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 himas...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 himas...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ES] Errors while running server - latest build
Hi all,
We (SameeraM and me) did some changes to governance api and some related
changes to jaggery extension to work with the changed governance api. Now
all the issues encountered above are sorted.
Shazni Nazeer
Senior Software Engineer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com
On Fri, Jan 16, 2015 at 12:17 PM, Pirinthapan Mahendran
pirintha...@wso2.com wrote:
Hi Ayesha,
If there is no error in the start up, then the lifecycle aspects,
configured in the configuration file, should be loaded to the registry.
Could you please check through the management console whether the required
lifecycles are loaded?
Thanks.
Mahendran Pirinthapan
Software Engineer | WSO2 Inc.
Mobile +94772378732.
On Fri, Jan 16, 2015 at 10:08 PM, Ayesha Dissanayaka aye...@wso2.com
wrote:
Hi,
According to the comment at
https://github.com/wso2-dev/carbon-governance/pull/23, I noticed that
relevant file at *[ES_HOME]/repository/resources/lifecycles location *is
still configuration.xml. So I've changed it to ServiceLifeCycle.xml.
Then the earlier mentioned server startup error is not present.(shown
below)
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} - Configuration
file name configurations not matched with aspect name ServiceLifeCycle
But the issue in attaching lifecycles with assets still
persist.(Lifecycles are not get attached to the artifacts)
Can app-factory team give us some light on this considering above
discussion, and the changes made to lifecycle management in above pull
requests.
Thanks!
-Ayesha
On Fri, Jan 16, 2015 at 8:58 PM, Shazni Nazeer sha...@wso2.com wrote:
Hi Ayesha,
This could be due to the following [1]. Could you check on with the app
factory team on their change on life cycle management which affects the
adding lifecycle to G-Reg? What I understood was this has caused issues in
adding lifecycle to G-Reg at start up. So that's why when trying to attach
the lifecycle it complains saying there's no lifecycle.
[1] https://github.com/wso2-dev/carbon-governance/pull/28/
[2] https://github.com/wso2-dev/carbon-governance/pull/23
[3] https://github.com/wso2-dev/product-greg/pull/55
regards
Shazni Nazeer
Senior Software Engineer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com
On Fri, Jan 16, 2015 at 2:58 AM, Ayesha Dissanayaka aye...@wso2.com
wrote:
Hi,
I am getting below error at the server startup.
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} - Configuration
file name configurations not matched with aspect name ServiceLifeCycle
Further, life-cycles are not attached to the default assets. (with the
changes in carbon-governance
https://github.com/wso2/carbon-governance/commit/bf13572edc127faa7a54dd9636568d3c6f7ad014
)
ERROR {JAGGERY.config.app:js} -
org.mozilla.javascript.WrappedException: Wrapped
org.wso2.carbon.governance.api.exception.GovernanceException: No lifecycle
associated with the artifact path /gadgets/admin/WSO2 Jira/1.0.0
(carbon/scripts/registry/artifacts.js#285)
at
org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0._c_anonymous_21(carbon/scripts/registry/artifacts.js:285)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0.call(carbon/scripts/registry/artifacts.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher..config.defaults.c0._c_onAttachLifecycle_13(/publisher//config/defaults/install.js:273)
at
org.jaggeryjs.rhino.publisher..config.defaults.c0.call(/publisher//config/defaults/install.js)
at
org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at
org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at
org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_16(/publisher/modules/asset.deployment.js:428)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_5(/publisher/modules/asset.deployment.js:166)
at
org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)
at
org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.modules.c7._c_anonymous_9(/publisher/modules/asset.deployment.js:297)
at
Re: [Dev] [ES] Errors while running server - latest build
Hi,
We did the following changes in order to rectify the above changes:
- product-es:
https://github.com/wso2-dev/product-es/commit/0be72ac3a88356225161056791e2f90a5a1276da
- Changed the version of the carbon module to 1.2.0-SNAPSHOT in order
to pick the changes done in the commit below
- jaggery-extensions:
https://github.com/wso2/jaggery-extensions/commit/304c9982aa0a6a46a5cd3745fd1b646781b126a3
- Modified all lifecycle operations in the artifact.js to invoke the
GovernanceArtifact methods with the name of the lifecycle
- This is done to adopt to the changes to the Governance API which
allow multiple lifecycles
- In order to provide support for multiple lifecycles in the carbon
module we will need to refactor all methods to accept an
optional lifecycle
attribute.Currently the default lifecycle is picked up
*Important*
- This fix also requires renaming the configuration.xml file found under
repository/resources/lifecycles to ServiceLifeCycle.xml
- The above file is picked up from from the carbon-core feature (The
file needs to be renamed in the component)
Thank You,
Sameera
On Sat, Jan 17, 2015 at 12:25 AM, Shazni Nazeer sha...@wso2.com wrote:
Hi all,
We (SameeraM and me) did some changes to governance api and some related
changes to jaggery extension to work with the changed governance api. Now
all the issues encountered above are sorted.
Shazni Nazeer
Senior Software Engineer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com
On Fri, Jan 16, 2015 at 12:17 PM, Pirinthapan Mahendran
pirintha...@wso2.com wrote:
Hi Ayesha,
If there is no error in the start up, then the lifecycle aspects,
configured in the configuration file, should be loaded to the registry.
Could you please check through the management console whether the required
lifecycles are loaded?
Thanks.
Mahendran Pirinthapan
Software Engineer | WSO2 Inc.
Mobile +94772378732.
On Fri, Jan 16, 2015 at 10:08 PM, Ayesha Dissanayaka aye...@wso2.com
wrote:
Hi,
According to the comment at
https://github.com/wso2-dev/carbon-governance/pull/23, I noticed that
relevant file at *[ES_HOME]/repository/resources/lifecycles location *is
still configuration.xml. So I've changed it to ServiceLifeCycle.xml.
Then the earlier mentioned server startup error is not present.(shown
below)
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} - Configuration
file name configurations not matched with aspect name ServiceLifeCycle
But the issue in attaching lifecycles with assets still
persist.(Lifecycles are not get attached to the artifacts)
Can app-factory team give us some light on this considering above
discussion, and the changes made to lifecycle management in above pull
requests.
Thanks!
-Ayesha
On Fri, Jan 16, 2015 at 8:58 PM, Shazni Nazeer sha...@wso2.com wrote:
Hi Ayesha,
This could be due to the following [1]. Could you check on with the app
factory team on their change on life cycle management which affects the
adding lifecycle to G-Reg? What I understood was this has caused issues in
adding lifecycle to G-Reg at start up. So that's why when trying to attach
the lifecycle it complains saying there's no lifecycle.
[1] https://github.com/wso2-dev/carbon-governance/pull/28/
[2] https://github.com/wso2-dev/carbon-governance/pull/23
[3] https://github.com/wso2-dev/product-greg/pull/55
regards
Shazni Nazeer
Senior Software Engineer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com
On Fri, Jan 16, 2015 at 2:58 AM, Ayesha Dissanayaka aye...@wso2.com
wrote:
Hi,
I am getting below error at the server startup.
ERROR {org.wso2.carbon.governance.lcm.util.CommonUtil} -
Configuration file name configurations not matched with aspect name
ServiceLifeCycle
Further, life-cycles are not attached to the default assets. (with the
changes in carbon-governance
https://github.com/wso2/carbon-governance/commit/bf13572edc127faa7a54dd9636568d3c6f7ad014
)
ERROR {JAGGERY.config.app:js} -
org.mozilla.javascript.WrappedException: Wrapped
org.wso2.carbon.governance.api.exception.GovernanceException: No lifecycle
associated with the artifact path /gadgets/admin/WSO2 Jira/1.0.0
(carbon/scripts/registry/artifacts.js#285)
at
org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at
org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0._c_anonymous_21(carbon/scripts/registry/artifacts.js:285)
at
org.jaggeryjs.rhino.carbon.scripts.registry.c0.call(carbon/scripts/registry/artifacts.js)
at
[Dev] Network failure errors in PR build ERROR: Could not transfer artifact
Hi All, Please refer [1]. This error is due to some network failure. Because the requested file is there in the nexus [2]. [1] https://wso2.org/jenkins-pr-builder/job/product-cep/131/console [2] http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.webapp.mgt.server.feature/4.3.0-SNAPSHOT/ This is something unavoidable and we don't have access to re-trigger the build also. What can we do for that? Thanks, -Ayash -- Ayashkantha Ramasinghe Software Engineer WSO2, Inc. email: ayashkan...@wso2.com sanj...@wso2.com; TP: +94 77 7 487 669 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in accessing OSGI of multiple versions
I think what you should do is to depend on the correct version. Can you
attach full pom.xml.
On Jan 16, 2015 5:39 PM, Sithumini Senevirathne sithumi...@wso2.com
wrote:
Hi,
I am currently developing a G-Reg feature[1] and for that I use a 3rd
party library called membrane-soa-model. This library uses Groovy 2.0 which
needs ASM 4. I created an osgi bundle for the membrane. If we run the
Registry server ASM 3 bundle also get Active as product-AS uses it. When
both ASM 3 and ASM 4 bundles are in Active state my feature gives an error
as membrane accesses ASM3 bundle.
11 ACTIVE asm_3.1.0.wso2v1
12 ACTIVE asm_4.0_1.0.0
I want membrane OSGI to use ASM4 only, to achieve this I introduce ASM 4
with proper osgi versioning and introduce groovy and asm as
private-packages. But couldn't resolve the problem. Below is what I added
in membrane osgi POM,
instructions
Bundle-Name${project.artifactId}/Bundle-Name
Bundle-SymbolicName${project.groupId}.${project.artifactId}/Bundle-SymbolicName
Bundle-DescriptionOSGI version of ${project.name
}/Bundle-Description
Export-Packagecom.predic8.*/Export-Package
Private-Package
org.codehaus.groovy;version=2.0.4,
org.ow2.asm;version=4.0,
/Private-Package
Import-Package
!com.predic8.*,
!org.ow2.asm,
!org.codehaus.groovy,
*;resolution:=optional
/Import-Package
/instructions
What is the proper way to overcome this issue?
[1] https://redmine.wso2.com/issues/3403
--
--
Sithumini Senevirathne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware | wso2.com
email: sithumi...@wso2.com, mobile: +94 756977999
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Urgent] [Greg] - Greg 5.0.0 server start up delays for several minutes
@Ruwan, can you have a quick look and merge? On Sat, Jan 17, 2015 at 8:47 AM, Roshan Wijesena ros...@wso2.com wrote: Hi NuwanD, Please review and merge https://github.com/wso2-dev/carbon-apimgt/pull/16 pull request to wso2-dev carbon-apimgt. Regards Roshan. On Sat, Jan 17, 2015 at 12:28 AM, Pulasthi Supun pulas...@wso2.com wrote: Hi Roshan, Could you get someone from the API manager team to review it and merge it as soon as possible. the governance lcm stub structure should be accurate. Best Regards, Pulasthi On Fri, Jan 16, 2015 at 10:03 PM, Roshan Wijesena ros...@wso2.com wrote: Hi Pulasthi, I have made a pull request for above concern [1] Please have a review on it. But I am not clear about one thing which is , *The package structure does not have stub* could you please clarify more on the same?. Furthermore if below given pull request is wrong would it be possible to share a correct service stub repo for us to follow the same structure?. However I already followed [2] repo structure to create my pull request. [1] https://github.com/wso2-dev/carbon-apimgt/pull/16 [2] https://github.com/wso2-dev/carbon-governance/tree/master/service-stubs/governance/org.wso2.carbon.governance.lcm.stub Thanks. Regards Roshan. On Fri, Jan 16, 2015 at 7:56 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi APIM team After further looking into this with sameera. we found out that the org.wso2.carbon.apimgt.keymgt.stub structure and exports are wrong. The package structure does not have stub hence it exports org.wso2.carbon.apimgt.impl.dto.xsd which should be org.wso2.carbon.apimgt.stub.impl.dto.xsd. And the bundle exports org.wso2.carbon.apimgt.* and this should be org.wso2.carbon.apimgt.stub* since this is a stub bundle. Can someone from the API Manager team look into this an provide the necessary changes as soon as possible since this is blocking the Greg 5.0.0 M1 release. Regards, Pulasthi On Thu, Jan 15, 2015 at 5:09 PM, Prasanna Dangalla prasa...@wso2.com wrote: Hi apim team, Greg server hangs for several minutes after printing JAVA_HOME environment variable is set to /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home CARBON_HOME environment variable is set to /Users/prasanna/workspace/wso2/greg/git/prasanna/product-greg/modules/distribution/target/wso2greg-5.0.0-SNAPSHOT We debug in osgi console. Then we found following two apimanager osgi bundles were not started. 161INSTALLED org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT 165INSTALLED org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT diag 161 and diag 165 describes the following osgi diag 161 reference:file:../plugins/org.wso2.carbon.apimgt.core_4.3.0.SNAPSHOT.jar [161] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.internal_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. osgi diag 165 reference:file:../plugins/org.wso2.carbon.apimgt.interceptor_4.3.0.SNAPSHOT.jar [165] Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dao; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.dto; version=0.0.0 Package uses conflict: Import-Package: org.wso2.carbon.apimgt.impl.utils; version=0.0.0 Direct constraints which are unresolved: Missing optionally imported package org.wso2.carbon.apimgt.core_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.authenticate_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.gateway_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.throttle_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.core.usage_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.handler_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.utils_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.interceptor.valve_0.0.0. Missing optionally imported package org.wso2.carbon.apimgt.usage.publisher.internal_0.0.0. Missing optionally imported package org.wso2.carbon.throttle.core_4.3.0.SNAPSHOT. Leaf constraints in the
Re: [Dev] [APIM] Use Nimbus for JWT token generation
May be we need to update nimbus version since there is a new version released. On Jan 17, 2015 3:14 AM, Gayan Gunawardana ga...@wso2.com wrote: Hi, Also need to use Nimbuz for [1] since this is the default JWT builder in identity.xml TokenGeneratorImplClassorg.wso2.carbon.identity.oauth2.authcontext.JWTTokenGenerator/TokenGeneratorImplClass [1] https://github.com/wso2-dev/carbon-identity/blob/master/components/identity/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/authcontext/JWTTokenGenerator.java On Fri, Jan 16, 2015 at 5:36 PM, Udara Liyanage ud...@wso2.com wrote: Hi, org.wso2.carbon.apimgt.impl has manually build the JWT token. However I guess it is better to use Nimbuz standard library to easily generate the JWT token like [1]. Additionally there is an Nimbuz orbit bundle created now. [1] https://github.com/wso2-dev/carbon-identity/blob/master/components/identity/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/openidconnect/DefaultIDTokenBuilder.java -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Gayan Gunawardana Software Engineer; WSO2 Inc.; http://wso2.com/ Email: ga...@wso2.com Mobile: +94 (71) 8020933 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Network failure errors in PR build ERROR: Could not transfer artifact
Maheshika should retrigger the build if such errors occur On Jan 17, 2015 11:39 AM, Ayash ayashkan...@wso2.com wrote: Hi All, Please refer [1]. This error is due to some network failure. Because the requested file is there in the nexus [2]. [1] https://wso2.org/jenkins-pr-builder/job/product-cep/131/console [2] http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.webapp.mgt.server.feature/4.3.0-SNAPSHOT/ This is something unavoidable and we don't have access to re-trigger the build also. What can we do for that? Thanks, -Ayash -- Ayashkantha Ramasinghe Software Engineer WSO2, Inc. email: ayashkan...@wso2.com sanj...@wso2.com; TP: +94 77 7 487 669 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in accessing OSGI of multiple versions
Hi,
This was solved using embedding dependencies Embed-Dependency. Below is
the code snippet,
instructions
Bundle-Name${project.artifactId}/Bundle-Name
Bundle-SymbolicName${project.groupId}.${project.artifactId}/Bundle-SymbolicName
Bundle-DescriptionOSGI version of ${project.name
}/Bundle-Description
Export-Packagecom.predic8.*;version=1.4.1/Export-Package
Import-Package
!com.predic8.wso2.*,
*;resolution:=optional
/Import-Package
*Embed-Dependency*
*
soa-model-core|groovy|asm-all;scope=compile|runtime;inline=false*
*/Embed-Dependency*
/instructions
Thank you,
Regards,
Sithumini
On Sat, Jan 17, 2015 at 11:47 AM, Danushka Fernando danush...@wso2.com
wrote:
I think what you should do is to depend on the correct version. Can you
attach full pom.xml.
On Jan 16, 2015 5:39 PM, Sithumini Senevirathne sithumi...@wso2.com
wrote:
Hi,
I am currently developing a G-Reg feature[1] and for that I use a 3rd
party library called membrane-soa-model. This library uses Groovy 2.0 which
needs ASM 4. I created an osgi bundle for the membrane. If we run the
Registry server ASM 3 bundle also get Active as product-AS uses it. When
both ASM 3 and ASM 4 bundles are in Active state my feature gives an error
as membrane accesses ASM3 bundle.
11 ACTIVE asm_3.1.0.wso2v1
12 ACTIVE asm_4.0_1.0.0
I want membrane OSGI to use ASM4 only, to achieve this I introduce ASM 4
with proper osgi versioning and introduce groovy and asm as
private-packages. But couldn't resolve the problem. Below is what I added
in membrane osgi POM,
instructions
Bundle-Name${project.artifactId}/Bundle-Name
Bundle-SymbolicName${project.groupId}.${project.artifactId}/Bundle-SymbolicName
Bundle-DescriptionOSGI version of ${
project.name}/Bundle-Description
Export-Packagecom.predic8.*/Export-Package
Private-Package
org.codehaus.groovy;version=2.0.4,
org.ow2.asm;version=4.0,
/Private-Package
Import-Package
!com.predic8.*,
!org.ow2.asm,
!org.codehaus.groovy,
*;resolution:=optional
/Import-Package
/instructions
What is the proper way to overcome this issue?
[1] https://redmine.wso2.com/issues/3403
--
--
Sithumini Senevirathne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware | wso2.com
email: sithumi...@wso2.com, mobile: +94 756977999
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
--
Sithumini Senevirathne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware | wso2.com
email: sithumi...@wso2.com, mobile: +94 756977999
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
