Historique de la page

...

• element channelConfig in esup-lecture.xml:
  

  Bloc de code
  <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE channelConfig SYSTEM "lecture-config.dtd" > <channelConfig> <!-- contexts definition --> <context> ... </context> <context> ... </context> ... <!-- category profile definition --> <categoryProfile> ... </categoryProfile> <categoryProfile> ... </categoryProfile> ... </channelConfig>

• element context:
  

  Bloc de code
  <context name = "Démonstration Esup-Lecture" id = "default"> <description>Context de démo</description> <refCategoryProfile refId="demo1"/> <refCategoryProfile refId="demo2"/> ... </context>

  Here is defined a context with:** id (You can use a specific context by configuring your portlet with a portlet preference. This portlet preference must have a name "context" and a value equals to the id you want for this portlet. If you don't define any context preference for your portlet then context with id "default" is used. With this mechanism you can define many channels with many contexts definitions in your portal environment with just one instance of the portlet.

  Remarque
  Before uPortal 2.5.4, because of a bug (http://www.ja-sig.org/issues/browse/UP-1040) you can't use this feature.

  • name (displayed on interface)
  • description (displayed on interface)
  • refCategoryProfile references on category profile declared in this context (using category profile id)You can declare as many category profiles as you want in a context. Each category profile must be defined in an element categoryProfile. A same categoryProfile can be declared in many contexts.
  • treeVisible (yes | no) : If "yes", users can see the left panel (tree of categories ans sources). Yes by default

...

Here is defined a category profile with:* id, name, and

...

** urlCategory : url to get back a xml category file on a remote server

• • trustCategory ( yes | no ) : If it is "yes", visibility rights used are those of remote category and sources. If it is "no", visibility rights on category and sources used are those of this category profile, defined in visibility element.
  • access ( public | cas ) : access of the category is public or cas because it needs CAS proxy ticket for authentication (for more information about CAS configuration see Configuration en déploiement portlet of the ESUP-Commons documentation and CAS en mode portletof the part Utilisation de CAS (French) of the of ESUP-Lecture documentation)
  • ttl (seconds) : time to live of the remote category and its sources
  • timeout (milliseconds) : time trying to get the category
  • visibility : define group visibility for category referenced by this category profile. It is used only if trustCategory is set to "no"
  • userCanMarkRead (yes | no) : If "yes", users can mark items of the category as read ot not read. Yes by default*

...