[gpinkham]

Is anyone doing WSDL first in an incremental fashion? IE: Create a WSDL.. generate XFire code. make XFire generated code talk to biz services etc.. Test.. Enhance WSDL.. Regnerate Xfire code.. Make Xfire generated code talk to biz services etc.. Test..

That 2nd generate will overly any of the work done by the 1st “make xfire generated code talk to Biz services”. So I’m curious how people are handling this? In other things (like Hibernate generation) there is a base class (always generated) and extensible classes (generated once).

Or is everyone doing Pojo first?… 😀

Thanks!
Gary

[Riyad Kalla]

Gary,
I’ve asked someone from our team to weigh in on best-practices, but they are swamped so I don’t know when they will reply.

[Russ]

Gary:

What I do is keep the last working copy of my Web Service Implementation class in a separate location. When I add a new method to the WSDL, I let ME regenerate the classes again, then I cut and paste the methods I’ve already worked. This approach works for ME 5.1.1. For my more advance service, ME 5.5M1 allows you the option to overwrite the existing Web Service Interface and Implementation class. I choose not to overwrite the Implementation class, but instead I just add the stub using the interface definition version and build the method in the implementation class this way….

This may not be the ideal practice and I am sure it can be automated better, but it does work with the tools and it keeps the development process going. I hope this helps you…..

Russ

[Author]

Posts