Definitely right David. It seems like the test (handler ? yes/no) in EjbInterceptor makes all more complex. For the moment, I don't really know if we can do without this test, but we need to keep in mind when using handlers the SOAP message is serialized twice.
I can probably have a look in order try removing this test ... Regards, JLouis David Blevins wrote: > > Definitely not my primary area of expertise, but it seems like a bug > to me. > > On a related note, I wonder if you have any feedback on the > "directEjbInvoke" optimization also in the EjbInterceptor. I've never > had a good feel for how much of an optimization that really is. Seems > it costs us a lot in terms of getting two sets of bugs depending on > whether or not there are handlers in the chain. It's like we have to > test everything with handlers and without handlers just because of > that optimization. > > -David > > On Feb 17, 2009, at 4:12 AM, Monteiro Jean-Louis wrote: > >> Feedback on this issue would be appreciated. >> >> Jean-Louis >> >> -----Message d'origine----- >> De : Jean-Louis MONTEIRO (JIRA) [mailto:[email protected]] >> Envoyé : mardi 17 février 2009 13:05 >> À : Monteiro Jean-Louis >> Objet : [jira] Created: (OPENEJB-1001) Can not use SOAP headers >> >> Can not use SOAP headers >> ------------------------ >> >> Key: OPENEJB-1001 >> URL: https://issues.apache.org/jira/browse/ >> OPENEJB-1001 >> Project: OpenEJB >> Issue Type: Bug >> Components: webservices >> Affects Versions: 3.1 >> Environment: all >> Reporter: Jean-Louis MONTEIRO >> Fix For: 3.1.1 >> >> >> Can not use SOAP headers when SOAP handlers are defined. >> >> @WebMethod(action="doSmth") >> @WebResult(name="response") >> DoSmthResponse doSmth ( >> @WebParam(name="request") DoSmthRequest request, >> @WebParam(name="datetime", header=true, >> mode=WebParam.Mode.OUT) Holder<Date> datetime); >> >> It only appears when SOAP handlers are defined. >> >> -- >> This message is automatically generated by JIRA. >> - >> You can reply to this email to add a comment to the issue online. >> >> >> >> >> Ce message et les pièces jointes sont confidentiels et réservés à >> l'usage exclusif de ses destinataires. Il peut également être >> protégé par le secret professionnel. Si vous recevez ce message par >> erreur, merci d'en avertir immédiatement l'expéditeur et de le >> détruire. L'intégrité du message ne pouvant être assurée sur >> Internet, la responsabilité du groupe Atos Origin ne pourra être >> recherchée quant au contenu de ce message. Bien que les meilleurs >> efforts soient faits pour maintenir cette transmission exempte de >> tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa >> responsabilité ne saurait être recherchée pour tout dommage >> résultant d'un virus transmis. >> >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive >> this e-mail in error, please notify the sender immediately and >> destroy it. As its integrity cannot be secured on the Internet, the >> Atos Origin group liability cannot be triggered for the message >> content. Although the sender endeavours to maintain a computer virus- >> free network, the sender does not warrant that this transmission is >> virus-free and will not be liable for any damages resulting from any >> virus transmitted. > > > -- View this message in context: http://www.nabble.com/TR%3A--jira--Created%3A-%28OPENEJB-1001%29-Can-not-use-SOAP-headers-tp22055979p22119614.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
