nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom JSP Tags

work4u

I have a page that consist of 4 components and one of the component is role based, meaning when the page is generated as a JSP and deployed that role based component should only show up if you belong to the group. So in order to accomplish that I was thinking that at the time of generation using the SitePublisher workflow is it possible to replace that one component with a custom JSP tag that can that be rendered at runtime on the webSphere app as we are also not using Livesite environment. The XML for the role based component will be the DCR which will also be deployed so it can be parsed and populated on the app server.

I am not sure how to replace the component with a TAGLIB directive within SitePublisher and wanted to see if someone has implemented this solution or a have a suggestion for a better approach.

All help is greatly appreciated.

Find more posts tagged with

Comments

work4u

Any ideas from anybody

kaalraa

I have a page that consist of 4 components and one of the component is role based, meaning when the page is generated as a JSP and deployed that role based component should only show up if you belong to the group. So in order to accomplish that I was thinking that at the time of generation using the SitePublisher workflow is it possible to replace that one component with a custom JSP tag that can that be rendered at runtime on the webSphere app as we are also not using Livesite environment. The XML for the role based component will be the DCR which will also be deployed so it can be parsed and populated on the app server.

I am not sure how to replace the component with a TAGLIB directive within SitePublisher and wanted to see if someone has implemented this solution or a have a suggestion for a better approach.

All help is greatly appreciated.

I suggest to generate the page and once thats done, place an external script in your workflow, which could parse the file and replace the content as per your need.

After that, you could deploy the page to respective app server.

HTH