Wow, I totally forgot I had done this xslt trick eons ago: [WayBack] detect availability of node-set() function in xslt implementation of icecast server – Stack Overflow
–jeroen
Archive for the ‘XML/XSD’ Category
detect availability of node-set() function in xslt implementation of icecast server – Stack Overflow
Posted by jpluimers on 2019/03/07
Posted in Development, Software Development, XML/XSD, XSLT | Leave a Comment »
Reminder to self: make a start for an XSD that validates Delphi dproj files
Posted by jpluimers on 2018/11/07
Below are a few interesting things from this thread [WayBack] Any idea why Delphi (At least since Seattle) does this to Dproj filesand… – Tommi Prami – Google+.
It’s likely that the WordPress system deleted parts between angle brackets because it thinks it’s invalid HTML and WordPress is PHP.
Anyhow: maybe by now I’ve found time for creating an XSD for .dproj files in addition to the one I mentioned yesterday for the .groupproj files: Validating a nested XML element with an empty namespace using XSD – Stack Overflow.
Oh and in the mean time for various Delphi versions, there is a (binary, because it uses some commercially licensed parts) [WayBack] Dproj changed or not changed? Normalize it! | The Art of Delphi Programming.
Files and directories I need to research:
- https://github.com/project-jedi/jcl/blob/master/jcl/source/windows/JclMsBuild.pas
- https://github.com/project-jedi/jcl/tree/master/jcl/packages/xml
- https://github.com/project-jedi/jvcl/blob/master/jvcl/devtools/Common/PackageInformation.pas
- https://github.com/project-jedi/jvcl/blob/master/jvcl/devtools/PackagesGenerator/PackageGenerator.pas
- https://github.com/project-jedi/jvcl/blob/master/jvcl/install/JVCLInstall/JVCLInstall.dpr
- https://github.com/project-jedi/jvcl/blob/master/jvcl/install/JVCLInstall/PackageUtils.pas
- https://github.com/project-jedi/jvcl/tree/master/jvcl/packages/xml
In the mean time, QualityPortal indicates that:
- fixed: RAD Studio – RSP-11308: Inconsistent sort order in dproj files causes havoc with version control systems.
- bit they missed fixing: RAD StudioRSP-18069: Inconsistent DeployFile sort order in .dproj
Achim Kalwa:
That is a long living bug: https://quality.embarcadero.com/browse/RSP-11308
Still exists in Berlin Update 2.Jeroen Wiert Pluimers
For more than a decade, the IDE rewriting dproj files in different order/indentation/spacing, properties appearing/disappearing in DFM files and writing DFM files despite no changes have driven me even more nuts than I was.Walter Prins
+Jeroen Wiert Pluimers Yes. Given that .dproj is XML I’ve been almost annoyed enough to look at making some kind of pre-checkin script to force sort things to try and avoid the issue. Almost… Edit: Ah, just checked that RSP, which references this: https://github.com/joshkel/RadCli Seems someone has already done it.Lübbe Onken
Did you try tidy_proj +Walter Prins? For me it fails with a “Unicode Encode Error” when I try to write an output file. In my case this is caused by German umlauts in the excluded bpl section descriptions. Changing the umlauts to something low-ascii allows tidy_proj to finish.Walter Prins
+Lübbe Onken No, but I have just done so. Unicode bites again. To fix that error, change line 125 from:print(proj.toxml())
to:
print(proj.toxml().encode(‘utf-8’))
Note: This will likely not display correctly if you allow the output to go to the console but will ensure it is correct if redirected back to file.
Edit: Ha, I was about to go report this issue ad suggest this fix, but I see you’ve already suggested essentially the same fix. ;)
Jeroen Wiert Pluimers’s profile photo
Jeroen Wiert Pluimers
+Walter Prins interesting tool! Do you know of a tool that can downgrade .dproj files so you can use them with older Delphi versions? (the opposite of what the IDE does)?Or someone that has written more than my XSD on .dproj files? My one is so small that’s hardly a real attempt. https://wiert.me/2013/08/31/delphi-first-try-on-an-xsd-for-groupproj-files/
Walter Prins
+Jeroen Wiert Pluimers No, but interesting idea. I suppose you’re probably aware that the JEDI JCL/JVCL takes a somewhat similar (ish) related approach, in that it generates project and package files that are compatible with every desired version of Delphi from minimalist (XML) template files. Every so often I think it might be worth looking whether one can re-use the code from there easily but haven’t gotten around to it. Always something else to do first. :/Jeroen Wiert Pluimers
+Walter Prins no I didn’t. Where should I start reading on that minimalist template approach?Walter Prins
+Jeroen Wiert Pluimers Sorry I see I missed out the word installer in my comment: It’s the Jedi JCL/JVCL installers that uses xml templates etc.But the point stands: I guess it should be (perhaps) possible to reuse its infrastructure for ones own projects, though as I say I keep meaning to look into this but haven’t really done so.
(BTW I’m assuming you are familiar with the JCL/JVCL and in in particular their installers that bootstrap from source code? If not then perhaps my comments may not be that useful?)
Anyway, not sure if or where there’s particular documentation about this (kind of doubt it), but if you have the JCL/JVCL installed somewhere, then first of all have a look at the “xml” folders e.g. “<jclroot>\jcl\packages\xmls” and “<jvclroot>\jvcl\packages\xml”.
These files appear to define projects and packages in a seemingly abstract/somewhat minimal way using XML. This seemingly is then used to automatically produce .dproj and .dpk files which are placed in e.g. “<jclroot>\jcl\packages\dXX” and “<jvclroot>\jvcl\packages\dXX” where dXX corresponds to a folder for each of the supported Delphi versions and compiled/used during installation.
Having just looked into this briefly a bit further as a result of this conversation: Key units here (in the case of JVCL) seems to be “<jvclroot>\devtools\PackagesGenerator\PackageGenerator.pas”, “<jvclroot>\install\JVCLInstall\PackageUtils.pas” and “<jvclroot>\devtools\common\PackageInformation.pas” (used predictably by <jvclroot>\JVCLInstall.dproj)
(Additionally, having looked at this a bit more closely, it also appears that the JCL does not actually replace all or even most of its .dproj and .dpk files after all, but ships version specific .dproj and .dpk files in most cases, though the JVCL does appear to mostly do so. )
Edit: The JCL also has this interesting sounding unit “jclroot>\source\windows\JclMsBuild.pas” which appears to be an MSBuild project file parser…
–jeroen
Share this:
Posted in Conference Topics, Conferences, Continuous Integration, Delphi, Development, Event, msbuild, Software Development, XML, XML/XSD, XSD | Leave a Comment »
Validating a nested XML element with an empty namespace using XSD – Stack Overflow
Posted by jpluimers on 2018/11/06
In a quest for making Delphi Group Project XML files (with extension .groupproj) validate with XSD, I had to find out about [WayBack] Validating a nested XML element with an empty namespace using XSD – Stack Overflow.
I needed the XSD so I could import it in Delphi in order to write a good .groupproj file generator.
They are here:
- https://bitbucket.org/jeroenp/wiert.me/src/tip/Native/Delphi/Scripts/GroupProj.xsd
- https://bitbucket.org/jeroenp/wiert.me/src/tip/Native/Delphi/Apps/Console/GenerateGroupProjConsoleProject
And some more background posts are here:
- Delphi versions
- GenerateGroupProjConsoleProject fix for Delphi 2007 – jeroenp / BeSharp.net / commit / f7c23ffe4cb1 — Bitbucket
- XSD regular expressions are a tad different: creating GroupProj.xsd
- XSD/XML Schemas: resolving `Namespace ” is not available to be referenced in this schema` (via: StackOverflow)
–jeren
Share this:
Posted in Delphi, Development, Software Development, XML, XML/XSD, XSD | 1 Comment »
Schema Central: XML vocabularies with all their XSD schema’s in a nice browsable overview including references, explanations and examples
Posted by jpluimers on 2018/09/11
Schema Central, by [WayBack] Datypic, Inc. (Priscilla Walmsley) is to golden that I quote the whole index page below.
The index refers to XML vocabularies. Each vocabulary page links the corresponding XSD pages. Each XSD page lists documentation, elements, etc. Each element page then documents the element, shows where it is referenced from.
Welcome to Schema Central, an interactive tool to traverse and search XML schemas. Please choose your XML vocabulary of interest to get started. Don’t see the XML vocabulary you use? Ask us to add it.
Core XML Technologies
- XML Schema: 1.0 and 1.1
- XML 1.0
- ISO Schematron
- XLink
- XProc
- XSLT: 1.0 and 2.0
- XInclude
- XForms: 1.0 and 1.1
- XML Catalogs 1.1
Presentation-Oriented Standards
- XHTML 1.0: (strict), (transitional) and (frameset)
- XSL-FO 1.1
- CALS Table Model (Oasis XML Exchange Table Model)
- MathML 2.0 and 3.0
- SVG 1.1
Office/Narrative Document Standards
Business Document Standards
- OAGIS® 9.4.1, 10
- UBL 2.0, 2.1 and 2.2
- StratML
- FpML
- 5.5: Confirmation, Pretrade, Recordkeeping, Reporting, Transparency
- 5.0: Confirmation and Reporting
- XBRL 2.1
NIEM-related Standards
- NIEM: 2.0, 2.1, 3.0, 3.1, 3.2 and 4.0
- LEXS: 3.1.4 and 4.0
- ULEX: 1.0 and 2.0
- N-DEx IA (Incident/Arrest) 2.1
- N-DEx IBP2 (Incarceration/Booking Probation/Parole) 2.1
- ANSI/NIST-ITL 2011
Miscellaneous
Web Services Technologies
- WSDL: 1.1 and 2.0
- SOAP: 1.1 and 1.2
- WS-Addressing 1.0
- WS-AtomicTransaction 1.1/1.2
- WS-BPEL 2.0
- WS-BusinessActivity 1.2
- WS-CDL 1.0
- WS-Coordination 1.2
- WS-Discovery 1.0 and 1.1
- WS-Eventing
- WS-Notification 1.3 (includes WS-BaseNotification, WS-BrokeredNotification and WS-Topics)
- WS-Policy 1.5
- WS-ReliableMessaging 2005 and 1.1/1.2
- WSRF (Resource Framework) 1.2 (includes WS-BaseFaults, WS-Resource, WS-ResourceProperties, WS-ResourceLifetime and WS-ServiceGroup)
Security-Related Technologies
- IC Trusted Data Format (Public version; includes IC-ARH, IC-EDH, IC-ID, IC-TDF, IC-ISM, IC-NTK)
- SAML 2.0
- WS-Security
- WS-SecurityPolicy 1.2 and 1.3
- WS-SecureConversation 1.4
- WS-Trust 1.3 and 1.4
- XML Encryption
- XML Signature
- XACML 2.0 and 3.0
Site developed and hosted by Datypic, Inc.
Please report errors or comments about this site to contrib@functx.com
[WayBack]
If I ever need a long term XML/XSD/XSLT/XQuery hire, this is the “about” information I need:
Datypic provides consulting services and training, specializing in XML, content management and SOA/Web Services architecture and development. We are experts in XML-related technologies such as XML Schema, XSLT and XQuery, and have extensive experience with software development and implementation.
We participate in consulting projects ranging from one day to many months, anywhere in the world. We can arrange to work remotely or at your site, whichever you prefer.
For more information, please read about our services or our company, or contact us as pwalmsley@datypic.com.
Recent news from Priscilla Walmsley
- I recently updated my book XQuery to match the final XQuery 3.1 recommendation. You can read more about it or order it from O’Reilly or Amazon.
- I recently taught a course at the XML Summer School on Refactoring XSLT. Slides are available as a PDF.
- More information about my recent books and articles is available on this site.
–jeroen
Share this:
Posted in Development, Software Development, XML, XML/XSD, XPath, XSD, XSLT | Leave a Comment »
Delphi XE6 and up regression: “‘9999-12-31 23:59:59,1000’ is not a valid date and time” when passing a SOAP message with 9999-11-31T23:59:59.9999999; QC144171
Posted by jpluimers on 2018/09/06
A valid SOAP message with <urn:timeStamp>9999-11-31T23:59:59.9999999</urn:timeStamp> in a xs:dateTime field return '9999-12-31 23:59:59,1000' is not a valid date and time from a Delphi application with this SOAP response:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>'9999-12-31 23:59:59,1000' is not a valid date and time</faultstring>
<faultactor/>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The reason is this exception:
exception class EConvertError with message ''9999-12-31 23:59:59,1000' is not a valid date and time'.
This is from a .NET based test case passing in timeStamp = DateTime.MaxValuewhich is handled perfectly fine by other SOAP web services tested.
I know about different resolutions of time stamps, but would never expect the 999.9999 milliseconds to be rounded up to 1000 as it is always safer to truncated away from an upper limit.
A test using Soap UI [WayBack] with this parameter finally worked (max 3 digits second fraction):
<urn:timeStamp>9999-12-31T23:59:59.999</urn:timeStamp>
The true origin of problem is in this method in the Soap.XSBuiltIns unit which has been unchanged since at least Delphi 7:
function TXSBaseTime.GetMilliSecond: Word; begin Result := Round(FractionalSeconds*1000); end;
The problem exposed itself because as of Delphi XE6 the core of function TXSBaseCustomDateTime.GetAsDateTime piece was changed from
Result := EncodeDateTime(Year, Month, Day, Hour, Minute, Second, 0);
to
Result := EncodeDateTime(Year, Month, Day, Hour, Minute, Second, Millisecond);
A combination of lack of test cases and understanding XML specifications failed to reveal this bug.
The standards specify (among others):
'.' s+ (if present) represents the fractional seconds;
The above is not limiting the amount of digits, not talking about milliseconds either.All ·minimally conforming· processors ·must· support year values with a minimum of 4 digits (i.e., YYYY) and a minimum fractional second precision of milliseconds or three decimal digits (i.e. s.sss). However, ·minimally conforming· processors ·may· set an application-defined limit on the maximum number of digits they are prepared to support in these two cases, in which case that application-defined maximum number ·must· be clearly documented.
Delphi not only limits the fractional second precission, it changes the limit over time and does not document the limit. Three strikes…s -- represents a digit used in the time element "second". The two digits in a ss format can have values from 0 to 60. In the formats described in this specification the whole number of seconds ·may· be followed by decimal seconds to an arbitrary level of precision. This is represented in the picture by "ss.sss". A value of 60 or more is allowed only in the case of leap seconds.
Given buggy the fractional second handling through milliseconds, the leap second handling is ripe for a test case as well.
Strictly speaking, a value of 60 or more is not sensible unless the month and day could represent March 31, June 30, September 30, or December 31 in UTC. Because the leap second is added or subtracted as the last second of the day in UTC time, the long (or short) minute could occur at other times in local time. In cases where the leap second is used with an inappropriate month and day it, and any fractional seconds, should considered as added or subtracted from the following minute.
The reproduction is quite simple:
Share this:
Posted in .NET, C#, Conference Topics, Conferences, Delphi, Development, Event, SOAP/WebServices, Software Development, XML, XML/XSD | Leave a Comment »
Some search links on Delphi and C# WSDL imports I need to investigate further
Posted by jpluimers on 2018/09/05
Sometimes, the Delphi WSDL importer imports fine, but the generated code does not accept test cases sent by other tools.
Below are some links for messages and comment fragments that I want to investigate further.
// Cannot unwrap:
// - Input element wrapper name does not match operation's name
// - The output part is not a complex type// CODEGEN: Generating message contract since the operation prematchChanged is neither RPC nor document wrapped.
I have included the .NET message, because my experience is that searching on those gives more accurate results for something that could be broken in more than one environment.
Based on those:
- [Archive.is] Creating doc-lit WSDLs that “unwrap” nicely | Paul Fremantle’s Blogvia [Archive.is] Creation of proxy code from WSDL using svcutil.exe: Getting “CODEGEN: Generating message contract since…”
- Svcutil.exe issues: generates twice the same elements or generates codes that do not compile.
- Put your headers in a separate message part.
- Rename the “body” message part to “parameters”.
- Remove references to the message part in the soap:body binding. (Each of your message should have only one part. Hence, the soap:body binding will use that one.)
- [WayBack] wcf – Add Service Reference is generating Message Contracts – Stack Overflow
ReplyAction="*"seems to be causing a lot of questions:
Some on-line tools prefer the WSDL to be in one document, but a lot of WSDL documents use import and or include features, so here are some links on that too:
- [WayBack] GitHub – lenardg/WSDLMerge: A tool to merge WSDL files (which initially did only support
wsdl:import, but now also supportswsdl:include) - [WayBack] Is there a simple tool to flatten a wsdl file? – Stack Overflow
- [WayBack] Is there a simple tool to flatten a wsdl file? | CODE Q&A [English]
- [WayBack] xmlHelpline.com: tools: WSDLFlattener xslt
- [WayBack] WSDLFlattener.java example
- [WayBack] c# – Using WSDL.exe with local WSDL file that has external .xsd files – Stack Overflow
Bruneau Babet correctly informed me that – though Delphi SOAP clients support both document literal and RPC encoded – Delphi SOAP servers cannot support document literal, as they can only support RPC encoded. Through that I found
- [WayBack] web services – Delphi SOAP Server – Document/Literal – Possible? – Stack Overflow.
- [WayBack] Delphi 2007: Using Web Services which has not changed since then: [WayBack] 10.2 Tokyo: Using Web Services – RAD Studio
- [WayBack] Release Notes for Delphi 2009 and C++Builder 2009 mention as part of the SOAP Server Notes:
The Win32/native SOAP server is currently on the Deprecated list and is classified as “Other Consideration: Need alternative.” If you want a document/literal server, you should build your SOAP server using Delphi for .NET (RAD Studio), which supports the SOAP specifications that are supported by the .NET framework.
- [WayBack] Release Notes for Embarcadero Delphi 2010 and C++Builder 2010 rephrase the SOAP Server Notes in terms of Delphi Prism instead of Delphi for .NET:
The Win32 SOAP server support generates the older RPC|Encoded style WebServices. If you want a document/literal service or a service of any other WS-I compliant style, you should build your SOAP server using Delphi Prism, which supports the SOAP specifications that are supported by the .NET framework, including WS-I compliant styles.
- This continued until [WayBack] Release Notes for XE3 – RAD Studio XE3, as after that [WayBack] No more Delphi for .NET: Prism removed from RAD Studio XE4 | Tim Anderson’s IT Writing. Here the SOAP Server Notes magically have disappeared from the [Archive.is] Release Notes for XE4 – RAD Studio.
- [WayBack] RPC Encoded and RPC Literal Delphi SOAP Server? – embarcadero.delphi.webservices
- [RSP-16581] WS-I Basic Profile 1.1 Compliance – Embarcadero Technologies
Unable to create a SOAP Server Application (WebService) with [WayBack] WS-I Basic Profile 1.1 compliance.
As far as I know, with delphi we can developed RPC/Encoded web services but there is no way to create Document/Literal service.
There are some companies that continue to use SOAP for information transfer, SAP one of them and we had to use C # to develop the application server.
With C# only [WayBack]
[SoapDocumentMethod]or [WayBack][SoapRpcMethod]is assigned to the Web Method. - I remember from the Delphi 7-2010 days that issues were raised in the private forums to press for document literal support as that is where the Java and .NET world were headed too
- A few notes on Delphi, WSDL and SOAP: passing nil values, Document/Literal versus RPC Encoded (yup: 5 years ago, I bumped into a few posts writing about this)
- [WayBack] c# – Delphi SOAP Envelope and WCF – Stack Overflow (the Delphi client side can do document/literal)
- Delphi 6 already added document literal support on the client: [WayBack] Using .NET complex types in a Delphi web service client
- Delphi 2010 added SOAP 1.2 support on the client: [WayBack] QualityCentral: Report #: 66864; Add SOAP 1.2 support to importer and clients, though people still bump into document literal issues from the client side: [WayBack] HILFE! SOAP-Client für document literal Webservice!?
- I wonder why both are still not supported on the server.
- Validating WSDL
- Online, this used to be possible at the [WayBack] eXtc WSDL Validator, which moved to [Wayback] www.validwsdl.com, but is defunct now.
- It looks like this has become defunct too: WayBack: Online WSDL Viewer and Validator.
- Validation tools on the console:
- [WayBack] Apache CXF — WSDLValidator
- Check the WSDL document for XML well-formedness.
- Validate the WSDL document against its XML schema.
- Validate the WSDL document using some of the semantic rules defined in the WSDL specification.
- Validate the WSDL document against custom validation rules, such as those defined by the Web Services Interoperability (WS-I) organization (i.e. WS-I Basic Profile rules).
- Validate the WSDL against strange exceptions, incorrectly generated code and general bad WSDL issues.
Back on those days, the big plan was to move everything Delphi to the .NET platform which supports both document literal and RPC encoded.
All in all, document literal has been on the radar with the Delphi R&D team since at least 2009, and nothing has been done.
References:
- [WayBack] SOAP Binding: Difference between Document and RPC Style Web Services
- Web Services Description Language – Wikipedia (note that despite WSDL 2.0 – which was originally named WSDL 1.2 – being out for 10+ years, most tools still only support WSDL 1.1, and some not even fully).
- [WayBack] Which style of WSDL should I use?,
[WayBack] IBM Knowledge Center – Literal vs. Encoded, RPC- vs. Document-Style[WayBack]
web services – What is the difference between Document style and RPC style communication? – Stack Overflow
[WayBack] Mike’s Software Development Blog: WSDL SOAP bindings confusion – RPC vs documentall with explanations (and some examples) of:- RPC/encoded
- RPC/literal
- Document/encoded
- Document/literal
- XSD
- WSDL 1.1
- [WayBack] Web Service Definition Language (WSDL)
- [WayBack] Web Service Definition Language (WSDL): 2.1 Document structure (which only shows
import, but notinclude) - [WayBack] Web Service Definition Language (WSDL): 2.3.1 Message parts
- [WayBack] Web Service Definition Language (WSDL): 2.1 Document structure (which only shows
- [WayBack] WSDL 1.1 Element Identifiers
- [WayBack] Web Service Description Usage Scenarios
- [WayBack] Web Services Description Requirements
- [WayBack] Web Service Definition Language (WSDL)
- WSDL 2.0:
- [WayBack] Web Services Description Language (WSDL) Version 2.0 Part 0: Primer
- [WayBack] Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language
- [WayBack] Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts; RPC signature definition
- [WayBack] Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding
- SOAP 1.1: [WayBack] Simple Object Access Protocol (SOAP) 1.1
- SOAP 1.2:
- [WayBack] Java Solution Architect: WSDL 2.0 VS WSDL 1.1
WS-I Basic Profile v1.1 provides guidance for using SOAP 1.1, WSDL 1.1, and UDDI 2.0.
WS-I Basic Profile v2.0 provides guidance for using SOAP 1.2, WSDL 1.1, UDDI 2.0, WS-Addressing, and MTOM.
- WS-I:
- [WayBack] WS-I Deliverables – Find Deliverables
- [WayBack] WS-I Basic Profile – Version 1.1 (Final)
- [WayBack] Basic Profile Version 1.1 (2006-04-10) Errata (Final)
- [WayBack] Basic Profile – Version 1.1 (Final): WSDL and Schema Import via [WayBack] web services – Importing xsd into wsdl – Stack Overflow:
wsdl:importis for a WSDL importing another WSDL- if used, it must be in a
wsdl:definitionselement and it hasnamespaceandlocationattributes
- if used, it must be in a
xsd:importis for a schema in a WSDL importing an XSD having a different namespace (many sites incorrectly refer to this as “WSDL import element”)- if used, it must be in an
xsd:schemaelement and it hasid,namespaceandschemaLocationattributes
- if used, it must be in an
xsd:includeis for a schema in a WSDL including an XSD having the same namespace- if used, it must be in an
xsd:schemaelement and it hasidandschemaLocationattributes
- if used, it must be in an
- [WayBack] WS-I Basic Profile – Version 2.0 (Final) (which is not at www.ws-i.org/Profiles/BasicProfile-2.0.html)
- [Archive.is] WS-I Deliverables – Testing Tools
- [Archive.is] A Preview of WS-I Basic Profile 1.1
- [WayBack] Deliverables – Basic Profile 1.2
- SOAP HTTP: a SOAP Fault should always translate into a HTTP status code 500 (Internal Server error). This even holds when a different status could be more appropriate (so no “403” for Forbidden, but a SOAP Fault indicating forbidden with a status code 500:
- Via [WayBack] Webservice response HTTP statuscodes – Programming – GoT and [WayBack] SOAP Fault & HTTP Status Code » karpisek.net
- [WayBack] Simple Object Access Protocol (SOAP) 1.1: SOAP HTTP ResponseIn case of a SOAP error while processing the request, the SOAP HTTP server MUST issue an HTTP 500 “Internal Server Error” response and include a SOAP message in the response containing a SOAP Fault element (see section 4.4) indicating the SOAP processing error.
- [WayBack] Basic Profile – Version 1.0 (Final): 4.3.9 HTTP Server Error Status CodesHTTP uses the 5xx series of status codes to indicate failure due to a server error.
R1126An INSTANCE MUST use a “500 Internal Server Error” HTTP status code if the response message is a SOAP Fault. - [WayBack] SOAP Version 1.2 Part 2: Adjuncts (Second Edition): Table 17: HTTP status code dependent transitions
- [WayBack] SOAP Version 1.2 Part 2: Adjuncts (Second Edition)Suggests that for
env:Server, a statuscode400is to be used, but WS-I mandates500. - [WayBack] RFC 2616 – Hypertext Transfer Protocol — HTTP/1.1: 10.5 Server Error 5xx
- Yes it is possible to use [WayBack] java – SOAP over non-HTTP protocol – Stack Overflow, but not from Delphi, despite most of SOAP being abstracted away from the protocol.
- Via [WayBack] Webservice response HTTP statuscodes – Programming – GoT and [WayBack] SOAP Fault & HTTP Status Code » karpisek.net
- Imports in various environments:
- Uniface:
- Delphi
- [WayBack] delphi – WSDL importer generates faulty server – Stack Overflow
- [WayBack] Cannot unwrap: More than one strictly out element was found
- [WayBack] Verschillen WSDL import XE7 D10
- (from a newsgroup server that – unlike forums.embarcadero.com – did keep history)
[WayBack] WSDL – Cannot Unwrap issues / on embarcadero.public.delphi.webservices / NNTP Conversation
with the below thread messages covering many topics:- “Cannot unwrap” hint comments in Delphi generated WSDL import code
- WS-addressing (needs manual implementation)
- rpc-encoded versus document-literal
- wrapped document-literal to make using document-literal easier to use than the bare document-literal ones
- Passing SOAP headers from Delphi and C# (see also [WayBack] Defining and Using SOAP Headers)
- Inspecting SOAP request output in the RIO using the OnBeforeExecute event
- The WSDL used in the thread:
- [cannot be archived] tapstaging.tax.utah.gov/efile/MFET/WSDL/?wsdl
- [cannot be archived] tapstaging.tax.utah.gov/efile/MFET/WSDL/?wsdl=wsdl0
- [WayBack] tax.utah.gov/fuel/handbook.pdf
- [WayBack] Article 1649 Subject WSDL – Cannot Unwrap issues on embarcadero.public.delphi.webservices
- [WayBack] Article 1650 Subject Re: WSDL – Cannot Unwrap issues on embarcadero.public.delphi.webservices
- [WayBack] Article 1653 Subject Re: WSDL – Cannot Unwrap issues on embarcadero.public.delphi.webservices
- [WayBack] Article 1657 Subject Re: WSDL – Cannot Unwrap issues [Edit] on embarcadero.public.delphi.webservices
- [WayBack] Article 1665 Subject Re: WSDL – Cannot Unwrap issues [Edit] on embarcadero.public.delphi.webservices
- [WayBack] Article 1667 Subject Re: WSDL – Cannot Unwrap issues on embarcadero.public.delphi.webservices
I looks like a wsdl message request part entries need to be named parameters for some tooling to correctly infer document/literal in a wrapped way. Some links for further research on this:
- wrapper “wsdl:part name=” “parameters” – Google Search and wrapper “wsdl:part name=”parameters” – Google Search
- [WayBack] WSDL Reading, a Beginner’s Guide
- [WayBack] schema – What is the difference between Type and Element in WSDL? – Stack Overflow
Note how the word “wrapped” does not appear. What IBM in their document is calling “document/literal/wrapped” is simply “document/literal”, that happens to use a single message part, that happens to have a name derived from the name of the service, and that happens to refer to an element, and which happens to contain both the parameters to the operation.
- [WayBack] WSDL 1.1 Binding Extension for SOAP 1.2
- IBM: [WayBack] Which style of WSDL should I use? and [WayBack] Tip: Implement implicit and explicit SOAP headers
- [WayBack] WSDL and Service Contracts | Microsoft Docs
- [WayBack] Modifying auto generated .net’s WSDL to take actual types instead of wrapper elements?
- [WayBack] strong-soap/doc_literal_wrapped_test.wsdl at master · strongloop/strong-soap · GitHub
- [WayBack] Utilities- Interoperability gotcha in wsdl.exe tool – Keep it Simple
When you are surely running SOAP over HTTP, you can use this small class to raise exceptions which automatically get translated into SOAP Faults having the right return code using a trick I bumped into a few years ago from [WayBack] web services – Accessing the original TWebRequest object in a Delphi SOAP Server – Stack Overflow:
unit SoapFaultWithHttpCodeExceptionUnit;
interface
uses
System.SysUtils;
type
ESoapFaultWithHttpCodeException = class(Exception)
strict private
FHttpStatusCode: Integer;
public
constructor Create(const AHttpStatusCode: Integer);
property HttpStatusCode: Integer read FHttpStatusCode;
end;
implementation
uses
Winapi.WinHTTP,
Soap.WebBrokerSOAP,
Web.HTTPApp,
IdCustomHTTPServer;
constructor ESoapFaultWithHttpCodeException.Create(const AHttpStatusCode: Integer);
var
IdHTTPResponseInfo: TIdHTTPResponseInfo;
ReasonString: string;
WebDispatcher: IWebDispatcherAccess;
begin
IdHTTPResponseInfo := TIdHTTPResponseInfo.Create(nil, nil, nil);
try
FHttpStatusCode := AHttpStatusCode;
IdHTTPResponseInfo.ResponseNo := AHttpStatusCode;
ReasonString := Format('%d: %s', [AHttpStatusCode, IdHTTPResponseInfo.ResponseText]);
inherited Create(ReasonString);
// https://stackoverflow.com/questions/10405227/accessing-the-original-twebrequest-object-in-a-delphi-soap-server
if Supports(GetSOAPWebModule, IWebDispatcherAccess, WebDispatcher) then
begin
WebDispatcher.Response.StatusCode := HTTP_STATUS_SERVER_ERROR;
WebDispatcher.Response.ReasonString := ReasonString;
end
finally
IdHTTPResponseInfo.Free;
end;
end;
end.
—jeroen
Share this:
Posted in .NET, C#, Conference Topics, Conferences, Delphi, Development, Event, SOAP/WebServices, Software Development, XML/XSD | Leave a Comment »
Argumate — program languages “What if …”
Posted by jpluimers on 2017/11/02
Quoted in full because even 2.5 years later, it’s just too funny:
- Python: What if everything was a dict?
- Java: What if everything was an object?
- JavaScript: What if everything was a dict *and* an object?
- C: What if everything was a pointer?
- APL: What if everything was an array?
- Tcl: What if everything was a string?
- Prolog: What if everything was a term?
- LISP: What if everything was a pair?
- Scheme: What if everything was a function?
- Haskell: What if everything was a monad?
- Assembly: What if everything was a register?
- Coq: What if everything was a type/proposition?
- COBOL: WHAT IF EVERYTHING WAS UPPERCASE?
- C#: What if everything was like Java, but different?
- Ruby: What if everything was monkey patched?
- Pascal: BEGIN What if everything was structured? END
- C++: What if we added everything to the language?
- C++11: What if we forgot to stop adding stuff?
- Rust: What if garbage collection didn’t exist?
- Go: What if we tried designing C a second time?
- Perl: What if shell, sed, and awk were one language?
- Perl6: What if we took the joke too far?
- PHP: What if we wanted to make SQL injection easier?
- VB: What if we wanted to allow anyone to program?
- VB.NET: What if we wanted to stop them again?
- Forth: What if everything was a stack?
- ColorForth: What if the stack was green?
- PostScript: What if everything was printed at 600dpi?
- XSLT: What if everything was an XML element?
- Make: What if everything was a dependency?
- m4: What if everything was incomprehensibly quoted?
- Scala: What if Haskell ran on the JVM?
- Clojure: What if LISP ran on the JVM?
- Lua: What if game developers got tired of C++?
- Mathematica: What if Stephen Wolfram invented everything?
- Malbolge: What if there is no god?
–jeroen
Share this:
Posted in .NET, APL, Assembly Language, BASIC, C, C#, C++, COBOL, Development, EPS/PostScript, Fun, Go (golang), Java, Java Platform, JavaScript/ECMAScript, LISP, Makefile, Pascal, Perl, PHP, Python, Quotes, Ruby, Rust, Scala, Scripting, Smalltalk, Software Development, T-Shirt quotes, TCL, Turbo Prolog, VB.NET, Visual BASIC, XML/XSD, XSLT | Leave a Comment »
Sending various HTTP request kinds using curl
Posted by jpluimers on 2017/07/25
I’ve been using cURL but always had a feeling not to its potential basically because the cURL man page [WayBack] is both massive and lacks concrete useful practical examples.
For instance, I knew about the --header and --verbose options (I always use verbose names even though shorter -H and -v exist) to pass a specific header and get verbose output, but the man page basic examples like this by Tader:
curl --header --verbose "X-MyHeader: 123" www.google.comsource: How to send a header using a HTTP request through a curl call? – Stack Overflow [WayBack]
There are some more examples at bropages.org/curl but they’re hardly organised or documented.
So I was really glad I found the below answer [WayBack] by Amith Koujalgi to web services – HTTP POST and GET using cURL in Linux – Stack Overflow.
But first note that recent versions (around 7.22 or higher) of cURL now need to combine the --silent and --show-error (or in short -sS) parameters to suppress progress but show errors: linux – How do I get cURL to not show the progress bar? – Stack Overflow [WayBack]
Back to the examples
Share this:
Posted in *nix, Communications Development, cURL, Delphi, Development, HTTP, https, Internet protocol suite, JavaScript/ECMAScript, JSON, Power User, REST, Scripting, Security, Software Development, TCP, TLS, XML, XML/XSD | 1 Comment »
Some links that helped me with XML processing
Posted by jpluimers on 2017/06/29
XML processing never gets easy. So here are some links that helped me:
- .NET: Schema Validation using XPathNavigator
- Source: c# – How to get the XPath (or Node) for the location of an XML schema validation failure? – Stack Overflow
- Source: xpath – xmllint, bash and mixing single and double qoutes – Stack Overflow
- Source: Get Node value from a XML using xmllint – Unix & Linux Stack Exchange
- Source: xmllint – Native shell command set to extract node value from XML – Stack Overflow
- Source: xml – pattern using xmllint command-line – Stack Overflow
- Source: How to get xpath and data value from xml schema validation c# – Stack Overflow
–jeroen
Share this:
Posted in Development, Software Development, XML, XML/XSD, XPath | Leave a Comment »
When someone writes UTF-8 and UTF-16 strings to the same file in binary format without converting between them…
Posted by jpluimers on 2017/06/21
A while ago, I had to fix some stuff in an application that would write – using a binary mechanism – UTF-8 and UTF-16 strings (part of it XML in various flavours) to the same byte stream without converting between the two encodings.
Some links that helped me investigate what was wrong, choose what encoding to use for storage and fix it:
- unicode – How to Convert Ansi to UTF 8 with TXMLDocument in Delphi – Stack Overflow
- delphi – What should I use? UTF8 or UTF16? – Stack Overflow
- IXMLDocument.SaveToStream does not always use UTF-16 encoding | Marc Durdin’s Blog
- delphi – Length() vs Sizeof() on Unicode strings – Stack Overflow
TEncoding.UTF8.GetBytes: utf 8 – String to byte array in UTF-8? – Stack OverflowSysUtils.ByteLength()is not the nicest function, so use only for a quick-fix Delphi Unicode String Length in Bytes – Stack OverflowAnsiString,UnicodeStringet al: String Types (Delphi) – RAD Studio- Question about type identity – delphi
- On the type compatibility in Delphi | The Programming Works
- Joe White’s Blog » Blog Archive » Grammar details of Delphi’s “type type” feature
- Type Compatibility and Identity (Delphi) – RAD Studio
- Delphi “type types”: similar types but not the same type identity, some examples.
- Converting in various Delphi versions (pre-Unicode and post-Unicode versions): Delphi: Encoding Strings as Python do – Stack Overflow
- UTF-8 Conversion Routines – RAD Studio
–jeroen
Share this:
Posted in Delphi, Delphi 10 Seattle, Delphi 10.1 Berlin (BigBen), Delphi XE8, Development, Encoding, Software Development, UTF-16, UTF-8, UTF16, UTF8, XML, XML/XSD | 3 Comments »
The Wiert Corner - irregular stream of stuff 