Thanks for your input , Alessio.
"alessio.soldano(a)jboss.com" wrote :
| - consider taking a look at the CXF JMSTransportFactory, perhaps there's an easy
hook for getting/setting the address. We currently overwrite the SoapTransportFactory in
the bus in CXFServletExt.loadBus(..) in order to implement our own soap address rewriting
rules for http endpoints. Perhaps a similar approach might be useful here (extending the
jms transport factory, etc.) for the jms case.
Do you mean we can specify the jms address in servlet initial parameter and set it in the
JMSDestination when initialize servlet ?
<servlet>
| <servlet-name>MyServletName</servlet-name>
| <servlet-class>com.mycompany.MyServlet</servlet-class>
| <init-param>
| <param-name>jmsJndiRequestQueue</param-name>
| <param-value>queue/RequestQueue</param-value>
| </init-param>
| </servlet>
"alessio.soldano(a)jboss.com" wrote :
| - we might think about something (an annotation?) to mark a jms endpoint when doing
java-first, assuming there's not an equivalent way in CXF yet. That could be looked
for in the DA to properly write the jbossws-cxf that is generated on the fly when not
provided by the user.
Annotation is another way to specify jms transport and address. IMHO, It's flexible to
define the jms configuration in web.xml. You do not need to compile the code when you
change the queue name .
"alessio.soldano(a)jboss.com" wrote :
| - is the CXF JMSFeature (
http://cxf.apache.org/docs/using-the-jmsconfigfeature.html)
configuration of any use to us?
IMO, it is another format to attach the jms configuraiton to the client and endpoint. If
user provides the jbossws-cxf.xml like this format , we do not support to parse ,extract
the jms address information and register the endpoint. We will just support one format
like the jbossws-cxf.xml in current jms transport sample.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263846#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...