[
https://issues.jboss.org/browse/JBWS-3396?page=com.atlassian.jira.plugin....
]
Robert Stupp commented on JBWS-3396:
------------------------------------
I had the usecase, where all necessary information was in web.xml, webservices.xml and
mapping.xml - worked without jbossws-cxf.xml file. But just the presence of the
jbossws-cxf.xml file made all webservices inaccessible (all webservices needed to be
mentioned in jbossws-cxf.xml).
I need the jbossws-cxf.xml file just to add this small piece snippet:
{noformat}
<bean name=".*\.jaxws-endpoint" abstract="true"
class="org.apache.cxf.jaxws22.EndpointImpl">
<property name="invoker"
ref="com.mycompany.jboss7.cxf.FrameworkCxfInvoker"/>
<property name="inInterceptors">
<list>
<ref bean="FrameworkCxfPreInvokeInterceptor"/>
<ref bean="FrameworkCxfPostInvokeInterceptor"/>
</list>
</property>
</bean>
{noformat}
that adds my own interceptors and my own invoker.
Evaluate partial generation of jbossws-cxf.xml descriptor
---------------------------------------------------------
Key: JBWS-3396
URL:
https://issues.jboss.org/browse/JBWS-3396
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Alessio Soldano
See
http://community.jboss.org/message/640779#640779 . Basically the issue with the need
for user to specify every endpoint in the jbossws-cxf.xml, while in some case the info
might come from the metadata created from the web.xml / annotations. At least we could
have defaults.
The same applies to defaults for the address attribute in jaxws:endpoint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira