Uploaded image for project: 'PUBLIC - Liferay Documentation'
  1. PUBLIC - Liferay Documentation
  2. LRDOCS-8664

Issues with "Creating Remote Services"

    Details

    • Type of Documentation:
      Developer

      Description

      Flagged by Jose Jimenez

      Article Link: https://help.liferay.com/hc/en-us/articles/360018166311#building-and-deploying-the-wsdd

      Comments: 

       

       

      yourportaladdress/o/your.apps.service.module.context/api/axis

      axis servlet is registered always using the bundle symbolicName as context: yourportaladdress/o/your.apps.service.module.bundle-SymbolicName/api/axis

      See https://github.com/liferay/liferay-portal/blob/7.0.x/modules/apps/foundation/portal-remote/portal-remote-axis-extender/src/main/java/com/liferay/portal/remote/axis/extender/internal/AxisExtender.java#L133-L135 https://github.com/liferay/liferay-portal/blob/7.1.x/modules/apps/portal-remote/portal-remote-axis-extender/src/main/java/com/liferay/portal/remote/axis/extender/internal/AxisExtender.java#L136-L138

       

       

      For example, if an app called Foo consists of the modules foo-api, foo-service, and foo-web, then the app's service module context is foo-service. If this app is deployed to a local Liferay DXP instance running at http://localhost:8080, you could access its SOAP services at:

      Also, we should avoid the "app's service module context" expression here

       

       

      If you don't know an app's *-service module context, you can find it by searching for the app in the App Manager where the app is running. For example, the following screenshot shows the Foo app's modules in the App Manager. The name of the *-service module in the App Manager, foo-service, is also its context. Also note that the app's WSDD module is grayed out and listed as Resolved instead of Active. This is normal. WSDD modules are OSGi fragments, which can't be activated. They still work as intended, though.

      in this particular example works because the contextName is equals to the symbolicName, but is the SymbolicName what the portal use

      Same issue in 7.0 and 7.1 doc:

      Creating Remote Services
      Creating Remote Services

      I was not able to find a similar documentation for 7.2 or 7.3, if you can... please, apply the changes in all the versions using OSGI 

       

      thank you

       

        Attachments

          Activity

            People

            Assignee:
            richard.sezov Rich Sezov
            Reporter:
            jay.lee Jay Lee
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support

                  Packages

                  Version Package
                  7.0.x
                  7.1.x
                  7.2.x
                  7.3.x