feedGet Some Interop
March 22, 2007 | 
co.mments
Kohsuke Kawaguchi on a bug with Hudson/JIRA integration
I believe my WSDL came from the latest 3.7.4. And so it sounds like JIRA is indeed breaking web interface compatibility between dot releases, which is bad. This kind of errors is exactly why people should be using JAX-WS and JAXB, which is much more robust in the face of changing service definitions! With JAX-WS this change would have worked no problem. Presumably people aren't updating JIRA installations that frequently?
I just came across this problem today, with Hudson 1.87 and JIRA 3.5-#131.
So here's a better idea - JIRA stops using this stuff altogether and replaces it with Atom+POST, so client apps like Hudson can function properly and beyond some other systems release cycle. The root problem here, isn't library selection. It's WS-* based proxy service generation pretending to not be an RMI call that requires binary compatibility. And a binary compatible wire call is still a binary compatible wire call, no matter how much XML you put on it.
Closing thought: "information can be utterly, utterly application-specific and still 100% XML compliant."
March 22, 2007 03:48 PM
Comments
If the jira code just pulled out the xpath soap11:env/soap11:body/tns:body they'd be somewhat more robust against failure too. There's nothing like the irony of one of the JAXWS people complaining about the brittleness of JAXWS/JAXB endpoints.
Amen, Bill!
Post a comment
Trackback Pings
TrackBack URL for this entry:
http://www.dehora.net/mt/mt-tb.cgi/2063