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; } } }

LiveSite Taglib on Websphere Portal

System

Hi,

I'm trying to render a Livesite page in a portlet. I have created a JSR168 portlet and have created JSP with livesite tags in them. The JSP is unable to recognize the following tag
<%@taglib uri="http://www.interwoven.com/livesite/embedded"prefix="ls"%>

Its throwing up the following error
"Cannot find the tag library descriptor for "http://www.interwoven.com/livesite/embedded"

Any pointers would be appreciated.

Thanks
-san

Find more posts tagged with

Comments

Faizi

Hi,

I'm trying to render a Livesite page in a portlet. I have created a JSR168 portlet and have created JSP with livesite tags in them. The JSP is unable to recognize the following tag
<%@taglib uri="http://www.interwoven.com/livesite/embedded"prefix="ls"%>

Its throwing up the following error
"Cannot find the tag library descriptor for "http://www.interwoven.com/livesite/embedded"

Any pointers would be appreciated.

Thanks
-san

AFAIK to include the LiveSite Taglib add the below tag in jsp:

<%@ taglib uri="http://www.interwoven.com/livesite/tags/livesite-rendering" prefix="ls" %>

Try this one, hope it will resolve the error.

vpatel

Something is missing from your posts! Please correct it.

mvusthipalli

Any solution to this problem?

Migrateduser

Yes, its resolved now

mvusthipalli

Could you please let me know how it is resolved? We too have the same issue.

We are trying this:
http://www.interwoven.com/livesite/tags/livesite-rendering and
http://www.interwoven.com/livesite/embedded

None of them work and getting the same error that you mentioned.

Vijay_K

Hi ,

We are in the process of developing a POC where we have to render a Livesite page in a portlet.I would like to have your valuable inputs for that.

As per my understanding,we render a Livesite page by calling a jsp from the portlet.In this scenario,how do we manage content authoring(adding / modifying content from the site).Should the content authoring be done from the portal side or should it be done from the Livesite side?

We will be using Livesite 7.1.

Regards
Krishna

vpatel

With LiveSite 7.1:

If you want control over your look and feel to be controlled by business (aka from CMS) then you can have that by using SP Pages served up by LSDS (LiveSite Display Services). In this case, authoring will be controlled via CMS.

Alternatively, you could have JSP / Portlet retrieve relevant content directly from LSCS (LiveSite Content Services). In this case authoring will be managed on the JSP side.

It depends on what your requirements are. You have flexibility to do few different things.

cute_guy

Hi ,

We are in the process of developing a POC where we have to render a Livesite page in a portlet.I would like to have your valuable inputs for that.

As per my understanding,we render a Livesite page by calling a jsp from the portlet.In this scenario,how do we manage content authoring(adding / modifying content from the site).Should the content authoring be done from the portal side or should it be done from the Livesite side?

We will be using Livesite 7.1.

Regards
Krishna

Content authoring should be done from the sitepublisher side. Smiley Happy

Murugan_P

Content authoring should be done from the sitepublisher side.

Thought of continuing this thread relevant to LiveSite tag libs and portlets.

Scenario: In authoring mode users will preview and edit the .pages and navigate between .pages using sitepublisher. In runtime they need to navigate between .jsps.

We're not going to render contents using LSDS. but will deploy the entire site to our custom web application and include the .pages in .jsp and render using livesite taglibs.

We end up rendering a .page in a jsp. Fine. What will happen if we try to navigate through a link in the .page when rendered through a jsp ? With links, i mean the hrefs we build as part of our .page content
Usually we build the links in .page pointing to another .page.

so if i want to reproduce the same navigation or the link between two Jsps rendering two different .pages what needs to be done for the links inside the .page ?
i guess, my .page links has to point to a .Jsp . Obviously Smiley Wink

What will be the advisable approach for this conversion ?
Any issues foreseen ?
Or is there any other way to achieve this ?

Please share your thoughts.

Thanks,
Mruugan
TS 7.1, LS 7.1

vpatel

Thought of continuing this thread relevant to LiveSite tag libs and portlets.

Scenario: In authoring mode users will preview and edit the .pages and navigate between .pages using sitepublisher. In runtime they need to navigate between .jsps.

We're not going to render contents using LSDS. but will deploy the entire site to our custom web application and include the .pages in .jsp and render using livesite taglibs.

We end up rendering a .page in a jsp. Fine. What will happen if we try to navigate through a link in the .page when rendered through a jsp ? With links, i mean the hrefs we build as part of our .page content
Usually we build the links in .page pointing to another .page.

so if i want to reproduce the same navigation or the link between two Jsps rendering two different .pages what needs to be done for the links inside the .page ?
i guess, my .page links has to point to a .Jsp . Obviously

What will be the advisable approach for this conversion ?
Any issues foreseen ?
Or is there any other way to achieve this ?

Please share your thoughts.

Thanks,
Mruugan
TS 7.1, LS 7.1

If every single .page is going to be embedded within a JSP page, then you should NOT be using "page links" in SitePublisher as they link to stand-alone .page files. Just user the regular "URL links".

Alternatively you could go around rewriting those URLs if there is some sort of consistency in the way these links are created and mapped to JSP pages. Again, this is your implementation specific.

Murugan_P

If every single .page is going to be embedded within a JSP page, then you should NOT be using "page links" in SitePublisher as they link to stand-alone .page files. Just user the regular "URL links".

Alternatively you could go around rewriting those URLs if there is some sort of consistency in the way these links are created and mapped to JSP pages. Again, this is your implementation specific.

Thanks Patel.
I would also like to know about the licensing for LSDS and livesite taglibs.
When i installed LSDS it doesn't require a license file to start up. same for the taglibs as well.
With one single installer(LSDS as well as taglibs) can i install or use it in multiple servers or instances ?

Thanks,
Murugan

vpatel

Thanks Patel.
I would also like to know about the licensing for LSDS and livesite taglibs.
When i installed LSDS it doesn't require a license file to start up. same for the taglibs as well.
With one single installer(LSDS as well as taglibs) can i install or use it in multiple servers or instances ?

Thanks,
Murugan

License information is something you should discuss with your Account Executive. Additionally, just because a license file doesn't stop the product from technically starting up and performing normally it doesn't mean that its OK to use. You still need to be licensed to avoid the "out of compliance" headaches.