1The folder contains extensions which need to be updated through a web site.
2The "Updates dialog" of the Extension Manager will mark the updates for these
3extensions as "browser based update". The Extension Manager will open a browser
4for each of the extensions and navigate to the respective website.
5
6================================================================================
7web1.oxt - web5.oxt:
8================================================================================
9They contain <update-information>. That is they reference directly the respective
10webX.update.xml (for example, web1.update.xml) files which are available at
11http://extensions.openoffice.org/testarea/desktop/website_update/update/...
12For example:
13http://extensions.openoffice.org/testarea/desktop/website_update/update/web2.update.xml
14
15The update information contain multiple URLs to "localized" web sites. Each URL is
16assigned to a particular local. For example:
17
18<src xlink:href="http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_de.html" lang="de"/>
19
20The Extension Manager will choose the URLs where the lang attribute matches most
21closely the locale of the office.
22
23The following table shows what localized web site  is used, when the office uses the locale
24en-US. The web page will display the locale used. See update/web1_de.html, etc.
25
26
27Localization:
28
29Installed office en-US
30         | publisher     | release notes
31=============================================
32web1.oxt | en-US         | en-US
33---------------------------------------------
34web2.oxt | en-US-region1 | en-US-region1
35---------------------------------------------
36web3.oxt | en            | en
37---------------------------------------------
38web4.oxt | en-GB         | en-GB
39---------------------------------------------
40web5.oxt | de            | de
41
42
43================================================================================
44web6.oxt
45================================================================================
46Need not be committed in extensions/www/testarea/desktop.
47
48web6.oxt is intended for tests with extensions.services.openoffice.org.
49It does not contain <update-information>. That is, the Extension Manager will obtain
50the update information from the repository as feed:
51
52http://updateext.services.openoffice.org/ProductUpdateService/check.Update
53
54Test
55----
56Repository:
57
58-Create the new extension in the repository.
59-Provide a company name and a URL to the company website. In our case this should be
60 http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
61
62-Create a new release for the extension. Upload the description.xml of version 2.0
63(update/web6/description.xml). Provide a download URL for the web site (field
64 "Download from page / Open follow up page URL", which should be
65  http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
66  Provide release notes.
67
68
69Office:
70-Install version 1.0 of the extension:
71 desktop/test/deployment/update/website_update/web6.oxt
72
73-Run the update in the Extension Manager
74
75
76Result:
77The Update Dialog should show the publisher name as provided in "Provider URL" field
78of the extension edit page (not release).
79
80A release notes link is displayed with an URL to the release notes as provided in
81the "Provider Title" field of the extension release edit page.
82
83When running the update then the web browser should navigate to
84http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
85
86
87================================================================================
88web7.oxt
89================================================================================
90Need not be committed in extensions/www/testarea/desktop
91
92web7.oxt is intended for tests with extensions.services.openoffice.org.
93It does not contain <update-information>. That is, the Extension Manager will obtain
94the update information from the repository as feed:
95
96http://updateext.services.openoffice.org/ProductUpdateService/check.Update
97
98The description.xml which will be uploaded contains URLs for release notes and publisher
99names/ URLs. That is, these information are not generated from the information of the
100repository web site.
101
102Test
103-----------
104Repository:
105
106-Create the new extension in the repository.
107-Provide a company name and a URL to the company website. In our case these should be different
108 to those provided in the description.xml. These should NOT go into the update feed.
109 Choose for example as "Provider Title": FOO and as "Provider URL" some valid URL but NOT
110 http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
111
112-Create a new release for the extension. Upload the description.xml of version 2.0
113(update/web7/description.xml). Provide a download URL for the web site (field
114 "Download from page / Open follow up page URL", which should be
115  http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
116  Provide release notes.
117
118Office:
119-Install version 1.0 of the extension:
120 desktop/test/deployment/update/website_update/web7.oxt
121
122-Run the update in the Extension Manager
123
124Result:
125The Update Dialog should show the publisher name as provided in the description.xml.
126That is: My OpenOffice en-US and NOT "FOO".
127
128A release notes link is displayed with an URL to the release notes as provided in
129the description.xml. That is:
130http://extensions.openoffice.org/testarea/desktop/publisher/release-notes_xxx.html
131
132When running the update then the web browser should navigate to
133http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
134