Mined Opinions For API: liferay

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • There is no clear way to find Assets with certain Tags on them through the JSONWS.. details
  • I am able to find the correct CODETERM3 , then the CODETERM4 under that CODETERM5 , but I cannot determine how to actually use that information in any other APIs.. details
  • I have looked through all the CODETERM6 calls and nothing references any kind of CODETERM7 or CODETERM8 parameter.. details
  • But the following URL works for liferay.com site: URL_http://www.liferay.com/tunnel-web/jsonws .. details
  • But the following URL works for liferay.com site: URL_http://www.liferay.com/tunnel-web/jsonws .. details
  • Another option would be to use Tags in this as well, but the same problem arises.. details
  • It is a known fact that Liferay doesn't expose all local services to the JSON api.. details
  • I have error 404 if open URL_http://localhost:8080/tunnel-web/jsonws [ URL_http://localhost:8080/tunnel-web/jsonws ] on default Liferay installtion.. details
Summaries the opinions about liferay using topic modeling.
  • 0. vocabulary find category parameter journalarticle follow url determine jsonws asset: 4
    • There is no clear way to find Assets with certain Tags on them through the JSONWS.. details
    • I have looked through all the JournalArticle calls and nothing references any kind of Vocabulary or Category parameter.. details
    • I am able to find the correct Vocabulary , then the Categories under that Vocabulary , but I cannot determine how to actually use that information in any other APIs.. details
    • But the following URL works for liferay.com site: .. details
  • 0. tag option expose local fact service open installtion: 3
    • Another option would be to use Tags in this as well, but the same problem arises.. details
    • It is a known fact that Liferay doesn't expose all local services to the JSON api.. details
    • I have error 404 if open on default Liferay installtion.. details
Summaries of the opinions about liferay using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • But the following URL works for liferay com site: .
  • I am able to find the correct Vocabulary , then the Categories under that Vocabulary , but I cannot determine how to actually use that information in any other APIs .
  • I have looked through all the JournalArticle calls and nothing references any kind of Vocabulary or Category parameter .
  • There is no clear way to find Assets with certain Tags on them through the JSONWS .
  • But the following URL works for liferay com site: .
  • I am able to find the correct Vocabulary , then the Categories under that Vocabulary , but I cannot determine how to actually use that information in any other APIs .
  • I have looked through all the JournalArticle calls and nothing references any kind of Vocabulary or Category parameter .
  • There is no clear way to find Assets with certain Tags on them through the JSONWS .
  • But the following URL works for liferay com site: .
  • I am able to find the correct Vocabulary , then the Categories under that Vocabulary , but I cannot determine how to actually use that information in any other APIs .
  • I have looked through all the JournalArticle calls and nothing references any kind of Vocabulary or Category parameter .
  • There is no clear way to find Assets with certain Tags on them through the JSONWS .
  • I have error 404 if open on default Liferay installtion .
  • Another option would be to use Tags in this as well, but the same problem arises .
  • It is a known fact that Liferay doesn't expose all local services to the JSON api .
  • I have error 404 if open on default Liferay installtion .
  • Another option would be to use Tags in this as well, but the same problem arises .
  • It is a known fact that Liferay doesn't expose all local services to the JSON api .
  • I have error 404 if open on default Liferay installtion .
  • Another option would be to use Tags in this as well, but the same problem arises .
  • It is a known fact that Liferay doesn't expose all local services to the JSON api .
Summaries of the opinions about liferay using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about liferay using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Documentation:
  • But the following URL works for liferay.com site: URL_http://www.liferay.com/tunnel-web/jsonws .
  • N/A
Features:
  • There is no clear way to find Assets with certain Tags on them through the JSONWS.
  • I have error 404 if open URL_http://localhost:8080/tunnel-web/jsonws [ URL_http://localhost:8080/tunnel-web/jsonws ] on default Liferay installtion.
Usability:
  • I am able to find the correct CODETERM3 , then the CODETERM4 under that CODETERM5 , but I cannot determine how to actually use that information in any other APIs.
  • Another option would be to use Tags in this as well, but the same problem arises.
  • Documentation: 1
    1. general: 1
      • But the following URL works for liferay.com site: URL_http://www.liferay.com/tunnel-web/jsonws .. details
  • Features: 2
    1. general: 2
      • There is no clear way to find Assets with certain Tags on them through the JSONWS.. details
      • I have looked through all the CODETERM6 calls and nothing references any kind of CODETERM7 or CODETERM8 parameter.. details
  • Usability: 2
    1. general: 2
      • I am able to find the correct CODETERM3 , then the CODETERM4 under that CODETERM5 , but I cannot determine how to actually use that information in any other APIs.. details
      • But the following URL works for liferay.com site: URL_http://www.liferay.com/tunnel-web/jsonws .. details
  • Features: 1
    1. general: 1
      • I have error 404 if open URL_http://localhost:8080/tunnel-web/jsonws [ URL_http://localhost:8080/tunnel-web/jsonws ] on default Liferay installtion.. details
  • Usability: 2
    1. general: 2
      • Another option would be to use Tags in this as well, but the same problem arises.. details
      • It is a known fact that Liferay doesn't expose all local services to the JSON api.. details