...
You can used esup-lecture in servlet mode. In this mode you don't have the notion of Portlet preference and you can't define more than one context in your esup-lecture.xml file. In servlet mode this context must have an id with value "default" ("context" before 1.1.0 version). Example:
| Bloc de code |
|---|
<context name="Simple context" id="contextdefault"> <description>Simple context</description> <refCategoryProfile refId="rss" /> </context> |
...
In servlet mode you can't used your portal for authentication. If you used CAS you don't have to modify the auth.xml file but you have to adapt CAS parameters. For this, you will find properties (:
- tomcat.host, tomcat.port
...
- in buil.properties file.
- casService.bean (it MUST be valued at servletCasService), ccasService.url, casService.proxyCallbackUrl in properties/config
...
- .properties file.
| Remarque |
|---|
With these properties ant deploy will automatically make appropriate changes in your web.xml file. |
Authorization
Authorizations defined in your esup-lecture.xml file or provided by news portlet are based in attributes or groups issued form uPortal. Of course, in servlet mode you don't have access to these informations naturally. So, you have to install (if not yet present in your uPortal distribution) esup-portal-ws (see http://sourcesup.cru.fr/projects/esup-portal-ws/).
| Remarque |
|---|
esup-portal-ws is now included in all 2.6-esup-2.0 and newer versions of esup-portail packaging of uPortal |
After, you have to configure esup-lecture to used this Web Service. For this, you have portalService.url, portalService.testUserId, portalService.testGroupId, portalService.testGroupName properties in the config.properties file. Finally, you can test the Web Service with ant test-portal.
...