I assume this will be part of Monday's discussion on the structure of
the specification, but I would prefer the spec bundle to include the
pre-generated XML samples.
Regards,
Dave
On 1 Apr 2009, at 16:05, Julian Reschke wrote:
> Al Brown wrote:
>> The examples were moved to the schema. The schema zip now contains
>> an eclipse project with an ant build script that generates jaxb and
>> jax-ws bindings from the xsd's plus a junit test case that
>> generates the examples.
>> The prior HTTP examples I do not believe are required as they are
>> standard HTTP calls with no specific CMIS headers. That left the
>> sample XML which are generated as junit and thus should always be
>> correct.
>> -Al
>
> I looked at the project, and it appears to have a lot of
> dependencies to things I don't have here. Is there a document
> somewhere explaining what exactly needs to be installed?
>
> That being said, I'm not convinced that automatically generated code
> can replace carefully written examples, in particular when it
> involves questions like HTTP status codes, methods != GET/POST,
> response headers, ETags and so on...
>
> BR, Julian
>
> --
> <green/>bytes GmbH, Hafenweg 16, D-48155 Münster, Germany
> Amtsgericht Münster: HRB5782
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
