Richard Opalka commented on JBWS-2521:
It is not possible to use ".jaxws-client.proxyFactory" suggestion above.
We need to hook to JAX-WS runtime before Port/Dispatch construction.
The above suggestion doesn't fit this requirement.
Refactor / rewrite ServiceObjectFactory
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Alessio Soldano
Assignee: Richard Opalka
Fix For: jbossws-cxf-3.1.2, jbossws-cxf-3.2.0
The jbossws-cxf ServiceObjectFactory needs to be cleaned:
- Bus retrieval: this is currently performed through reflection on the Service class and
following cast to cxf ServiceImpl; leveraging the BusFactory should be enough to get the
default bus that is used by the cxf ProviderImpl for every Service creation
- ServiceRef stub properties setup: this is currently performed through reflection on
Service class to get the ServiceDelegate and then changing the ServiceDelegate instance at
runtime with a custom one that sets the properties. Instead of doing this hack, we should
evaluate leveraging the CXF configuration for runtime constructed objects
cxf ServiceImpl looks for a bean named portName.toString() +
".jaxws-client.proxyFactory" to configure the JaxWsProxyFactoryBean used to
build the port and that factory bean allows for setting the stub properties. We might be
able to generate on the fly and supply a bean configuration to the cxf bus for having our
stub properties automatically configured by the already existing cxf configuration
- perhaps even the handler chain configuration can be achieved in a way similar to the
described in the previous point.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira