[
https://jira.jboss.org/jira/browse/JBWS-2661?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBWS-2661:
---------------------------------------
I'm leaving the ws-trust tests (as well as non ws-policy based ws-security ones) as
they are because:
- we need to test both approaches (programmatic bus configuration and bus configuration
through user provided config file) in our integration stack
- users can still choose what to do, also considering those are interop tests regarding
ws-trust, not samples. Also even moving the bus configuration to config file would not
make those tests portable (one would still need to configure the ws-trust stuff..)
I'm going to update the doc for the modified samples (ws-a and ws-rm) where required.
Remove proprietary CXF API usage from our samples/tests and update
CXF documentation
------------------------------------------------------------------------------------
Key: JBWS-2661
URL:
https://jira.jboss.org/jira/browse/JBWS-2661
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Affects Versions: jbossws-cxf-3.1.1
Reporter: Richard Opalka
Assignee: Alessio Soldano
Priority: Minor
Fix For: jbossws-cxf-3.2.0
Don't use the following classes directly:
- org.apache.cxf.Bus
- org.apache.cxf.BusFactory
- org.apache.cxf.bus.spring.SpringBusFactory
Replace it with providing META-INF/cxf.xml files in client jars to show our users how to
do it properly (so their code can be migrated cross JAX-WS implementations).
--
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