The blog post you linked was interesting. The reasons for avoiding JAXB might, then, be either to avoid changing existing code or to continue using a familiar binding framework. The first of these doesn't apply to me since I've chosen to implement an Adapter to translate between my business level components (most of which are used in other applications) and my service operation class (I want as little coupling between my chosen Web Service implementation and business logic as I can get away with). The second of those reasons is closer to my situation but not quite the same motivation. My motivation is the choice of binding framework on the basis of it working as easily, and as effectively, as possible with Axis2 (my current requirements allow me to use ADB).
Do you think that the wish to use Axis2 is a sufficient reason to avoid JAXB, or is this restriction imposed by the use of Axis2 (in it's current implementation) not a reasonable compromise in your opinion? Would the wish to use JAXB prompt you to find an alternative to Axis2 in this case?
My current feeling is that the most pragmatic approach is for me to stick with Axis2 and ADB for now, and migrate to JAXB if a compelling reason appears later on and Axis2 has more evolved support for JAXB. A potential pitfall here is the possibility of that compelling reason emerging before Axis2 works well with JAXB, but I figure that's a bridge I may never need to cross. My experience in this area is fairly limited so I'd appreciate your views on the use of frameworks such as Axis2, XFire, or others?
I know you must be very busy and this is perhaps getting a little lengthy, but any overview comments from your experience would be much appreciated.