[
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)
Investigate JAX-WS/JAX-RPC decoupling
-------------------------------------
Key: JBWS-2318
URL:
https://jira.jboss.org/jira/browse/JBWS-2318
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-integration, jbossws-native
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: jbossws-native-3.0.5
Whether it is possible in a BC way, if it's easy doable, identify possible problems.
--
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