[jboss-dev-forums] [JBoss AS 7 Development] - Re: JBossWS/CXF configuration / extensions

[Alessio Soldano]

Alessio Soldano [http://community.jboss.org/people/asoldano] created the discussion

"Re: JBossWS/CXF configuration / extensions"

To view the discussion, visit: http://community.jboss.org/message/641483#641483

--------------------------------------------------------------
Hi Robert,
> 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.
I see... generally speaking this is going to be quite an issue, as JBoss AS7 is a major change in pretty much all area (and similarly there's no jbossws stack running on both JBoss 4 and 7). So I understand you're doing some kind of advanced hacking with the ws stack... unfortunately that's a bit beyond what we'd usually support, however reasonable needs/requests are still considered:
> 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?
Yes, we can consider this. Please create a jira and provide a basic description of an example of extension that would need those changes.

> 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.
The @EndpointConfig is not an app server specific annotation to be honest. It comes from JBossWS and has been introduced in JBossWS 4. To be honest an equivalent annotation was there for jbossws native since years, with the 4 major release that's being converted in a stack independent new annotation. That will be available on all app server the JBossWS 4 series will support as target containers.
In theory, you have *real* portability as long as you only leverage standards / specification APIs. Anything else, any additional feature usage (being that from JBoss AS, JBossWS, Apache CXF, etc.) is likely to break portability, depending on which are your target containers.
--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/641483#641483]

Start a new discussion in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2225]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20111214/556f25ec/attachment.html