996814 wrote:That is reallly not relevant or necessary to share to be honest.
Thanks. I've actually made a much simpler web service before, using PowerBuilder. But I was in control of how the WSDL turned out on that one. With this one, it's a WSDL created by a standards committee. I work for an auto insurance company and I am required by a new state law to have this implemented within a few months so that the state can use the same client to communicate with different web services from all the auto insurance companies that serve our state. PowerBuilder was unable to generate a matching WSDL from the web service it generated, which is why I'm using Java instead (I've already found that the resulting WSDL matches).
The problem I was having is that all the tutorials I could find told me how to generate the web service, but then just ended with "now implement the generated objects."That's a problem with tutorials as a whole - they all suck. They tend to be written by novices that after reading a chapter on a book think they're experts and have to share their epic knowledge with the world. Then you get something with only half of the truth in it that lacks all the important nuances.
That's the part I've been stuck on, but I'm gradually getting it figured out. Java is a lot more complicated than it was 12 years ago, and I was hoping to find the magic book that would explain it all for me. :)Its not more complicated. Software engineering as a whole is complicated and stays complicated. The only thing that has changed is that the world wants more more more, so you have to know more more more. But that's your job.
Nico wrote:The Amazon user reviews are pretty much slashing this book into pieces though. I would not adopt actual code practices from it if I were you.
I'm reading "Java web services up and running". It is a good introduction to jax-ws that does not go into all details (300 page).