[ https://jira.jboss.org/jira/browse/JBWS-2318?page=com.atlassian.jira.plug... ] Richard Opalka commented on JBWS-2318: -------------------------------------- This will enable us to support JAX-RPC even with metro in the future. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2318?page=com.atlassian.jira.plug... ] Richard Opalka commented on JBWS-2318: -------------------------------------- This would be even more complicated than JBWS-2386 because JAX-RPC has hardcoded dependencies on: * JBossWS SAAJ Impl (which is tightly coupled with our JAX-WS implementation) * UMDM (which is union of JAX-RPC + JAX-WS + JBossWS extensions with ugly relationships) The next problem is both JAX-RPC and JAX-WS JBossWS implementations share the same invocation framework. In other words JAX-WS and JAX-RPC are like siamese twins, i.e. their separation would be really time consuming and painful because: * they share the same UMDM (which needs refactoring - affects BC) * they share the same invocations framework (again needs refactoring that affects BC) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira