Paul Clapham wrote:
A Kao wrote:Business requirement prevent changing the xsd file.
I'm surprised that you have a business requirement which is so important that it protects the document by making it unusable.
But fine, let's suppose the business managers know what they're doing. Then make a copy of the document and edit it to be usable.
Paul Clapham wrote:Seems to me that the easiest way to do that would be to edit those documents and make the appropriate changes. For example where you have
you could change that to
and so on. No?
Cay Horstmann wrote:When I first saw the new HTTP client, I had high hopes that it would come with support for REST. At the very least, a JSON content handler. But nooo...I was told that JSON was not a part of the core platform, so that not something they'd sully their hands with. The HTTP client doesn't do forms or file upload either. This is one of the few times that I may end up breaking my own rules and cover a non-core API in Core Java. But I don't think I'll write a whole book on REST.
Cay Horstmann wrote:Hi, it's good feedback that you want HTTP/2 push covered.
Generally, I stick to use cases that (a) aren't bleeding edge and (b) are of interest to application programmers, not system programmers. If in a year or two, application programmers have to worry about this, I'll put it into the book.
I think it's an important skill to eyeball a new feature and gauge whether it has a broad impact. For example, someone who should remain nameless (Simon Ritter) gives presentations about new features in Java 9 that contain such gems as "PKCS12 key stores by default" and "Spin-Wait Hints". These are important features only for the small number of heroes who give us application programmers better-performing libraries and tools. The service that I aim to provide is that I don't put them in my books.
Of course, I am sometimes wrong, so if you feel that I am missing the boat on an important feature, let me know.
Pierre-Yves Saumont wrote:The default value (for the year) is used by the formatter, not by the parser. You need an additional format string:
Tim Moores wrote:Which SSL/TLS protocols does the server support?
Tim Moores wrote:What are you trying to achieve by setting that property?