I, also am running Axis 1.2.1 on WebSphere 5.1. In my case, however, we're using a custom transport for JMS because the existing one didn't support our needs--so if there are conflicts with the HTTP/HTTPS handling, I wouldn't run into them.
WSDL2Java generation worked great once I got the WSAD jars off my classpath... (I was fooled for several days because I didn't realize I was generating the old classes from the WSAD built-in WSDL2Java code). I am also running only as a client, and not a service, so it's possible I've managed to avoid some problems that way. The marshalling/unmarshalling for rpc-encoded xml seems to be working wonderfully, though, and that's the piece I really wanted Axis for, since JAXB 1.5 cannot read the Siebel-generated WSDL I have, and can't handle rpc-encoded services anyway (at least, from what I've been able to learn). XMLBeans reads the WSDL, but also can't seem to handle the rpc-encoded messages (at least, not without me hand-creating some schemas for the message elements). Meghan Pietila Granite Consulting
