Robert Stupp [
http://community.jboss.org/people/snazy0] created the discussion
"Re: JBossWS/CXF configuration / extensions"
To view the discussion, visit:
http://community.jboss.org/message/641328#641328
--------------------------------------------------------------
Hi Alessio,
thanks for your answer and posting the requests for enhancements :)
We have the situation, that we must support JBoss7 for new projects (but still have to
support JBoss4 X-( ).
The same code has to work in JBoss7 and JBoss4 - so we cannot use "custom"
annotations like @Endpoint.
For JBoss7 I have used Spring wildcard bean names in jbossws-cxf.xml to "inject"
my CXF invoker and interceptors.
It was a bit hard to figure out that this works (a lot of debugging sessions ;) ) - but
it works great.
The JAXWS handler does not work for us, because we need to intercept the Java reflection
method call. We have to "replay" web service calls and therefore need to collect
a lot of meta information.
BTW: It would be nice to remove the "final" keywork from the
org.jboss.ws.common.invocation.InvocationHandlerJAXWS and similiar classes - and from the
org.jboss.ws.common.invocation.AbstractInvocationHandlerJSE.invoke() method - to allow
users to override this functionality. I had to copy the code to my own implementations and
could not reuse existing classes. Is it ok to open a new issue (RFE) in Jira?
IMHO it is great to have app server specific annotations - but this means, that the
application is bound to a specific app server and maybe specific app server configuration
- means that the application is not portable. There should be an alternative to be able to
keep the code portable.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/641328#641328]
Start a new discussion in JBoss AS 7 Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]