[
http://jira.jboss.com/jira/browse/JBWS-1672?page=comments#action_12366369 ]
Alessio Soldano commented on JBWS-1672:
---------------------------------------
OK, here are my 2 cents: I took a look at sunri's WSServiceDelegate, performed a
couple of tests and verified that @HandlerChain is not respected on SEI, even if running
on the Sun Java System Application Server; as expected this is a Sun issue.
@HandlerChain is respected on custom Service class by sunri, while jbws native stack
respects it only on SEI.
There's offcourse a little difference between these choices, anyway users can still
add handlers through annotations using both stacks. Moreover, as far as I get from JAX-WS
specifications, implementations are not strictly required to support @HandlerChain on
client side on SEI or Service.
SunRI does not respect @HandlerChain on client SEI
--------------------------------------------------
Key: JBWS-1672
URL:
http://jira.jboss.com/jira/browse/JBWS-1672
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: integration-sunri
Reporter: Thomas Diesler
Assigned To: Alessio Soldano
Fix For: jbossws-2.1.0
tests-run-internal:
[junit] Running org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase
[junit] FIXME: [JBWS-1671] SunRI client handler cannot set mime header
[junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 4.209 sec
[junit] Test org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase
FAILED
@WebService(name="Endpoint")
@SOAPBinding(style = SOAPBinding.Style.RPC)
@HandlerChain(file = "jaxws-handlers-client.xml") // relative path from the
class file
public interface EndpointWithHandlerChain
{
public String echo(String input);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira