Re: [Dev] [ES] Errors while running server - latest build
Hi All,
Great, Thanks for the quick resolution.
Best Regards,
Pulasthi
On Sat, Jan 17, 2015 at 11:05 AM, Sameera Medagammaddegedara
samee...@wso2.com wrote:
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
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] [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
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] [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
