<!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">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;">
CXF jms integration
</h3>
<span style="margin-bottom: 10px;">
reply from <a href="http://community.jboss.org/people/richard.opalka%40jboss.com">Richard Opalka</a> in <i>JBoss Web Services Development</i> - <a href="http://community.jboss.org/message/541050#541050">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 Jim,</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>    let me agree with Alessio. We really don't need to introduce<br/>another DD (jbossws-endpoints.xml namely). There are two reasons for that:<br/> * XML configuration duplicity (as Alessio properly said users can just provide jbossws-cxf.xml with all the configuration)<br/> * simplicity (our current SPI facade should be enough for you to do the job).</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>What you're doing (providing jbossws-endpoints.xml) is just creating WS stack agnostic configuration.<br/>But our SPI is intended exactly for that purpose.<br/>Providing additional DD is the same thing like our SPI (just different XML-ized form of it).</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>If you will follow my suggestions I wrote few days before you shoudn't face "real" problems.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Another thing/issue is our SPI is not perfect (and we know that).<br/>We will improve/rewrite our SPI once we'll be done with all the<br/>highier priority tasks we have these days.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><blockquote class="jive-quote"><p>Jim Ma wrote:<br/>    I evaluated to make new SPI metadata to extend the current SPI Endpoint.  But I did not find benifit from it, as our DeploymentAspects was intended to process the SPI HttpEndpoint. It can not be reused to process JMSEndpoint too.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p></blockquote><p>Let me disagree. This is the way you had to go IMHO <span> ;) </span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>We need these abstractions in our SPI:<br/> * Endpoint<br/>   - ServletEndpoint -> url address<br/>   - JMSEndpoint -> jms address<br/> * DA<br/>   - ServletDA<br/>   - JMSDA</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Our ASIL deployers will accept DA abstraction<br/>and will be able to distinguish between HTTP and JMS.<br/>In deployer, before specifying inputs/outputs,<br/>you should have code like this:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>// pseudocode ensuring proper deployers ordering<br/>if (DA instanceof ServletDA) {<br/>  this.addInput(WebMetaData.class);<br/>  ...<br/>} else if (DA instanceof JMSDA) {<br/>  this.addInput(JMSMetaData.class);<br/>  ...<br/>}</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Both HTTP and JMS endpoints should use the same deployers flow.<br/>Don't create another deployer flow just for JMS endpoints.<br/>but reuse our current architeture.</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/541050#541050">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss Web Services Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2047">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>