Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lifecycle states do not displayed correctly after restoring revision #2299

Closed
shnrndk opened this issue Dec 1, 2023 · 0 comments · Fixed by wso2/carbon-apimgt#12192
Closed
Assignees

Comments

@shnrndk
Copy link

shnrndk commented Dec 1, 2023

Description

Problem

After restoring an API, the states of the lifecycle is always in the created state. And the users can't publish the api. And also this API will not get appeared in the devportal.

Affected Component

APIM

Version

APIM 4.2

Steps to Reproduce

  1. Create and publish an API.
  2. Create and deploy a revision.
  3. Restore the previous revision.
  4. The available states for the published api are created and pre-released. It needs to be block, pre-release, demote to created and deprecate.
image

Affected Component

APIM

Version

4.2

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

If we click on the api rxt on the file in the (Ex - /apimgt/applicationdata/provider/admin/PizzaShackAPI/1.0.0/api). The logs will display the resource can't find.

Caused by: java.io.IOException: JSPException while including path '/resources/resource.jsp'. ServletException while including page.
	at org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:91) ~[tiles-jsp_2.0.5.wso2v2.jar:?]
	at org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82) ~[tiles-jsp_2.0.5.wso2v2.jar:?]
	at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465) ~[tiles-jsp_2.0.5.wso2v2.jar:?]
	at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140) ~[tiles-jsp_2.0.5.wso2v2.jar:?]

Suggested Labels

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants