Actually in my project, I made some modifications in JMSConduit.java and in
order to benefit Spring framework, I will inject in JMSConduit some beans. The
Idea is I will do some works ( save the messageID into my database for example
) before sending the JMS message.
Like I couldn't inject it directly in my conduit, I'll do it via
JMSConfiguration in using <jms:jmsConfig-ref> : put my bean in jmsConfig and
call it in JMSConduit.java ( with getJmsConfig() )
Any suggestion of doing it in another way, or can you correct me in
somepoints that I miss?
Thanks
=========================================================================
NGUYEN Tien Luong | M2PGI - UFRIMAG
13 Rue Blanche MONIER | Tel : 06.45.42.46.33
38000 GRENOBLE | http://tienluong.info
----- Original Message ----
From: Christian Schneider <[email protected]>
To: [email protected]
Sent: Fri, 7 May, 2010 22:40:15
Subject: Re: Using the JMS via Configuration
When you use jms-config-ref then it overrides the settings in conduit.
So it is important to inject a completely configured connectionfactory
into it. Like I wrote the best way is to not use conduit at all in this
case.
Is there any reason why the solution of only having a client and a
jmsconfig does not work for you?
Greetingss
Christian
Am 07.05.2010 16:40, schrieb Nguyen Tien Luong:
> In addition to my question, I wanna to understand how CXF gets/stocks
> their informations in the declaration<jms:conduit ...> </jms:conduit>? Which
> classes hold these information ( like jndiConnectionFactoryName,
> jndiDestinationName,jndiReplyDestinationName ... )
>
> The reason I ask this question is, normaly I have connectionFactory
> declared in<jms:address jndiConnectionFactoryName="cf" .../>
>
> And when I add<jms:jmsConfig-ref>jmsConf1</jms:jmsConfig-ref> in my bean's
> config, this reference jmsConf1 suddenly requires the property
> 'connectionFactory' !!!!!! This exception raised when I tried to take away
> 'connectionFactory' from the definition of jmsConf1
>
> Caused by:
> at
> org.springframework.beans.factory.annotation.RequiredAnnotationBeanPostProcessor.postProcessPropertyValues(
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(
> ... 16 more
>
> org.springframework.beans.factory.BeanInitializationException: Property
> 'connectionFactory' is required for bean
> 'jmsConf1'RequiredAnnotationBeanPostProcessor.java:121)AbstractAutowireCapableBeanFactory.java:998)AbstractAutowireCapableBeanFactory.java:472)
> So if someone can explain to me how CXF can use all of JMS's information
> (declared in the bean's configuration) and use them for its transport layer (
> in this case, it's JMS )
>
> Thanks
>
> =========================================================================
> NGUYEN Tien Luong | M2PGI - UFRIMAG
>
> 13 Rue Blanche MONIER | Tel : 06.45.42.46.33
> 38000 GRENOBLE | http://tienluong.info
>
>
>
>
> ----- Original Message ----
> From: Nguyen Tien Luong<[email protected]>
> To: [email protected]
> Sent: Fri, 7 May, 2010 10:38:18
> Subject: Re: Using the JMS via Configuration
>
> Hi Christian ,
>
> As I see the constructeur of
> org.objectweb.joram.client.jms.tcp.QueueTcpConnectionFactory, there are no
> parameters and it attemps only to create an empty QueueTcpConnectionFactory
> instance.
>
> (http://joram.ow2.org/current/javadoc/org/objectweb/joram/client/jms/tcp/QueueTcpConnectionFactory.html)
>
> And in its methods, where we can put parameters to create a
> QueueTcpConnectionFactory .
>
> Any suggestions ?
>
> Thanks
>
> =========================================================================
> NGUYEN Tien Luong | M2PGI - UFRIMAG
>
> 13 Rue Blanche MONIER | Tel : 06.45.42.46.33
> 38000 GRENOBLE | http://tienluong.info
>
>
>
>
> ----- Original Message ----
> From: Christian Schneider<[email protected]>
> To: [email protected]
> Sent: Fri, 7 May, 2010 8:01:25
> Subject: Re: Using the JMS via Configuration
>
> Your connectionfactory bean does not contain any configuration. When
> using the JmsConfiguration aproach then the contents of jmsconduit are
> not used (at least I think so).
> So you have to use the normal spring style to configure the
> connectionfactory. The good thing is that you can either keep using jndi
> or create a connectionfactory in the bean.
> The easisest way will probably be to simply use the following:
>
> <bean id="connectionFactory"
> class="org.objectweb.joram.client.jms.tcp.QueueTcpConnectionFactory">
> <constructor-arg value="your joram host url"/>
> </bean>
>
> This could already solve the propblem.
>
>
> Greetings
>
> Christian
>
>
>
>
>
>
--
----
http://www.liquid-reality.de
