My JAX-RPC Wish­list

1. we need­ed to be able to send/re­ceive asyn­chro­nous (one-way) doc­u­ment/lit­er­al SOAP mes­sages
2. we need­ed a con­ve­nient way to parse/gen­er­ate the XML
3. we need­ed to be able to send cus­tom SOAP faults for asyn­chro­nous er­ror con­di­tions
4. we need­ed to be able to process head­er blocks eas­i­ly
5. we need­ed rea­son­able sup­port for head­er bind­ings in the WSDL doc­u­ment
6. we need­ed to be able to as­so­ciate serv­er-side head­er in­for­ma­tion with thread-spe­cif­ic in­for­ma­tion in the ser­vice be­ing called
7. If pos­si­ble, we want­ed to be able to as­so­ciate han­dlers with cus­tom, servlet-based end­points (not JAX-RPC end­points)

With the cur­rent state of the art in Java's JAX-RPC and JAXB, this was cer­tain­ly pos­si­ble but not at all straight­for­ward. 1 and 2 are not so much of a prob­lem, but the Java web ser­vices stack falls short on all the oth­er items. So if any of the JAX-RPC com­mit­tee mem­bers read this: I hope these com­ments or ex­pe­ri­ences can help in im­prov­ing/clar­i­fy­ing the JAX-RPC tech­nol­o­gy...