Re^2: JSON WebService Description with PERl

Thanks for your opinion on this - I'm a fan of rather simple things that over-enginered ones! The fact that there is no standard or default way to do this implies that the work needed to define, implement one is higher than just documenting and doing it the fast way - which is just fine!

Thanks for the profile example - looks good, but probably lots of implementation needed when it comes to binding Java Services to it :)

Comment on Re^2: JSON WebService Description with PERl

Replies are listed 'Best First'.

Re^3: JSON WebService Description with PERl
by Rhandom (Curate) on May 08, 2012 at 14:45 UTC

"but probably lots of implementation needed when it comes to binding Java Services to it

Possibly true.

My consumers have typically been perl, javascript, php, or python - all dynamic folk. Yes - potentially there could be a little more work for those using Java, but I don't really think there would be that much more. In actuality I doubt any existing JSON service would be much easier to bind to Java. Unless you are using a WSDL I doubt there are many (if any) JSON web service libraries that would do the automatic type conversions that you get with WSDL.

Either way, Java will likely have top-notch JSON classes - and if they do then constructing an appropriate JSON message would not be difficult, nor would getting information out of a JSON response and type casting. Ultimately that isn't really that more work than fiddling with WDSLs and having to pull information out of the automatically parsed structure returned by the SOAP libraries. The real time it is faster and easier with SOAP is when you are passing struct type objects and consuming those objects on the client end - very little of my work has ever wanted to deal with information in that form.

my @a=qw(random brilliant braindead); print $a[rand(@a)];

[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks