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

Get value of context from LSCS client

Rohan_t1

Hi All,

We have created a LSCS client and can get document object by passing DCR path. Is there any method to get the value of context? Can see ways to get document id, uri etc but not context. Any suggestions?

com.interwoven.wcm.lscs.Document doc1=client.getDocumentByPath("templatedata/abc/cde/test_new3.xml");

Query returns:

[HTML]

<metadata>
cde

[/HTML]
Thanks,
TeamSite: 7.2.1 on Solaris
LSCS 7.2.1

Find more posts tagged with

Comments

Rick Poulin

Your options:

1) Parse it out of the doc.getContentURL()
2) Cast to the impl: ((DocumentImpl)doc).getLSCSContext() [not supported]
3) Query the URI using your own custom http wrapper

The real question is why do you even want this? I can't see how this information is of any use to custom code.

Rohan_t1

Thanks Rick. Looks like lscsclient.jar specific to 7.2.1 doesn't provide implementations when compared with that of 7.3.2.

1) Parse it out of the doc.getContentURL() - Doesn't have context but returns

2) Cast to the impl: ((DocumentImpl)doc).getLSCSContext() [not supported] - No getLSCSContext() in 7.2.1
3) Query the URI using your own custom http wrapper - This should work. Will try this.

We have usual LSCS query based implementation but for non-metadata items we were looking for options to read the DCR content which are deployed to LSCS. For eg:
using /lscs/v1/document/id/87c3fb5b7f76675b62068600eed9bdc7/context/e7a86e875f59c70a6400757afa2c6e58

However from my op we can also use doc1.getContentStream() to get this information.

Thanks

Rick Poulin

However from my op we can also use doc1.getContentStream() to get this information.

If that's all you need the context for, then yes you might as well just get the content that way.. Although in my cases, I've found that using doc1.getPath() combined with ExternalUtils.readXmlFile() to read it from the local LSDS root has much better performance, if you can make the assertion/assumption that the content will be identical in both locations.