Blocks i90370

It would be good to have this enhancement in version 3.1.1, so the target
milestone should be upgraded. Therefor CCed MD

added keyword

added usagetracking keyword

Where should the office version be added in the request? In which format?
Proposal:

...
xmlns:rds="urn:ReportDataService"
xmlns:apache="http://xml.apache.org/xml-soap"
SOAP-ENV:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<!-- Add Officeversion here -->
<rds:submitReport>
...

The OfficeVersion will be added as:
<Officeversion="SomeVersionString"/>

@fma: Would that work for you?

Yes, please in the SOAP-Body like:
Officeversion= MAJOR.MINOR.MICRO
Officeproduct= {OpenOffice.org, StarOffice, StarSuite, BrOffice.org,...}

Cant we just reuse the string as it gets written in the reportmail.xml?

If you mean
<officeinfo:officeinfo xmlns:officeinfo="http://openoffice.org/2002/officeinfo"
platform="Win32" language="es" build="310m11(Build:9399)" exceptiontype=""
product="OpenOffice.org 3.1 " />

-> product="OpenOffice.org 3.1 "
yes!!!

Cheers,
Frank

fixed in cws bjm02 with changeset 5699b326f2f1.

http://hg.services.openoffice.org/hg/cws/bjm02/rev/5699b326f2f1

Moved Office version from SOAP-Envelope-Body to request body with changeset
324d9e2690fb in cws bjm02

http://hg.services.openoffice.org/hg/cws/bjm02/rev/324d9e2690fb

@fma: please verify

CCed: es

reopening as this wasnt completely fixed in bjm02

Created attachment 64416 [details]
proposed patch

attached proposed patch, changing issue type to patch
@mba: please reassign to someone to drop the patch in a 3.2 cws (after
integration of bjm02). cc'ing myself.
removing es from cc as this is not in cws bjm02 anymore

Patch works for me.
Frank

this issue was fixed on master for m60

reassigning to fma for validation on master (m60)

Verified, so we can prepare multiple import queues for the OOo

Closing issue