Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
"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)];

In reply to Re^3: JSON WebService Description with PERl by Rhandom
in thread JSON WebService Description with PERl by several

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (4)
As of 2024-03-29 14:44 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found