My Adventures as an Only Developer™: Fun with third party integration.
-
Given what you've demonstrated so far, they are probably using StringBuilders.
Because, you know, it makes sense. It's in the name!
They don't have XmlBuilders in Java? Maybe this is where they're going wrong...
Filed under: who even uses <strong> tags...
-
You can have a tool create all the code from a WSDL:
TL;DR: $ wsgen -keep -cp . com.mkyong.ws.ServerInfo -wsdl
Fuck, that's the only good thing about SOAP
Who said anything about SOAP? If you're making that assumption off the fact that my APIs provide a WSDL, you're wrong. RESTful services can have WSDLs, too.
-
Filed under: who even uses <strong> tags...
Me, because Dickhorse refuses to bold parts of the words when using Brokendown.
-
You can have a tool create all the code from a WSDL:
From the context of this thread, it is slowly becoming clear to me that WSDL doesn't stand for Windows Software Developer License.
(Well, I mean, it does, but it presumably also stands for something else as well, which would be the thing people are talking about here...)
-
Me, because Dickhorse refuses to bold parts of the words when using Brokendown.
You know that <b> is a thing? Of course, being Diskwhores, there's probably 500,000,000 other ways to achieve the same effect...
-
Not if someone on the other side has decided that the best way to parse XML is with regexps…
Why is there a sideways dick on a red plate?
-
The b element represents a span of text to which attention is being drawn for utilitarian purposes without conveying any extra importance and with no implication of an alternate voice or mood, such as key words in a document abstract, product names in a review, actionable words in interactive text-driven software, or an article lede.
HTML — Living Standard, WHATWG
> While <em> and <strong> have remained pretty much the same, there has been a slight realignment in their meanings. In HTML4 they meant ‘emphasis’ and ‘strong emphasis’. Now their meanings have been differentiated into <em> representing stress emphasis (i.e., something you’d pronounce differently), and <strong> representing importance.<em>mine.
-
How about
<em<, is that yours too?(Damnit, forgot to wait 54 seconds again... :/)
-
Why is there a sideways dick on a red plate.
That would've made a pretty stupid question, if only there was a
?.
-
Yes, I brained,
<instead of>...FUCKING HELL IT SAID 2m, HOW LONG IS THE NINJA WINDOW?
(I actually wanted to have it in edit history so your post makes sense)
EDIT: So I wanted to emulate it and... look at edit history... I just... no...
-
-
54 seconds.
Then Dickhorse is lying. Or it's taking the time of clicking the edit button as the relevant one, not when you submit it.
-
-
Fuck, that's the only good thing about SOAP.
WSDL != SOAP.
A lot of non-SOAP REST APIs have them.
-
Usually XML + WSDL is a SOAP API. Also, I didn't imply this thing was a SOAP WS, just that one of the only good things of SOAP is the WSDL generated code because SOAP forces you to provide a WSDL.
And there's nothing in REST about a WSDL, so good for you, but it has nothing to do with it.
-
Also, I didn't imply this thing was a SOAP WS,.
Both @blakeyrat and I thought you were implying that, so maybe you need to take a second look at your post and rethink the wording.
-
JAXB generates boilerplate Java classes from the WSDL schema. Maybe they have no idea what to do with them?
I also suffered from having to consume web services with badly built schemas that generated a garbage class structure on my end, but I don't think that's the case here. At least it doesn't justify building the XML manually.
-
SOAP forces you to provide a WSDL
Nope. Thanks for playing.
A lot of non-SOAP REST APIs have them.
While I've read about how WSDL 2.0 supports REST, I've yet to see an instance actually using that in the wild.
-
@Eldelshell said:
SOAP forces you to provide a WSDL
Nope. Thanks for playing.Which reminds me... HP's on-board management software (called iLO) has an XML based API. There are no URLs, you just send it an XML document and it sends back XML as a response. However, it usually responds with invalid XML. For example:
<?xml version="1.0"?> <RIBCL VERSION="2.22"/> <RESPONSE STATUS="0x0000" MESSAGE='No error' /> </RIBCL>or if you send it two commands, you get two responses in the same (malformed) XML document:
<?xml version="1.0"?> <RIBCL VERSION="2.22"/> <RESPONSE STATUS="0x0000" MESSAGE='No error' /> </RIBCL> <?xml version="1.0"?> <RIBCL VERSION="2.22"/> <RESPONSE STATUS="0x0000" MESSAGE='No error' /> </RIBCL>So, not only does it not have a schema, it cannot be described by a schema and no XML parser will load it. You either have to note all of the little problems and run the response through a pre-processor, or parse it as text, defeating the entire point of using XML.
JAX-WS : wsgen tool example - Mkyong.com
