<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Re: JBossWS/CXF configuration / extensions
</h3>
<span style="margin-bottom: 10px;">
created by <a href="http://community.jboss.org/people/asoldano">Alessio Soldano</a> in <i>JBoss AS 7 Development</i> - <a href="http://community.jboss.org/message/641483#641483">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>Hi Robert,</p><blockquote class="jive-quote"><p>We have the situation, that we must support JBoss7 for new projects (but still have to support JBoss4 <span> X-( </span>).</p><p>The same code has to work in JBoss7 and JBoss4 - so we cannot use "custom" annotations like @Endpoint.</p></blockquote><p>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:</p><blockquote class="jive-quote"><p>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?</p></blockquote><p>Yes, we can consider this. Please create a jira and provide a basic description of an example of extension that would need those changes.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><blockquote class="jive-quote"><p>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.</p></blockquote><p>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.</p><p>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.</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/641483#641483">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss AS 7 Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2225">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>