The new binaries are available at
http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/incubating-apache-servicemix/3.0-SNAPSHOT/

In the case of the JMS connection factory, it would easier to just create a
new bean,
but the WSNotification component already internally look up a jms connection
factory
in JNDI at "java:comp/env/jms/wsnotificationCF" (this can be changed).

Btw, if you need to retrieve any object from JNDI, just try something like
  <bean class="*org.springframework.jndi.JndiObjectFactoryBean*">
    <property name="jndiName" value="java:comp/env/jms/wsnotificationCF"/>
  </bean>

You should use that to retrieve a bean from an SU on the lwcontainer (for
example the BootstrapContext
or ConnectionManager for jca).

Cheers,
Guillaume Nodet

On 6/16/06, echolu <[EMAIL PROTECTED]> wrote:


It is changed a lot of the configuration files.
I want to download  the lasted version  binary SM from

http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/incubating-servicemix/3.0-SNAPSHOT/
but it seems the site could not word any more. Maybe change the location.

You have configured the connectionFactory like that:
<entry key="java:comp/env/jms/wsnotificationCF">
          <bean class="org.apache.activemq.ActiveMQConnectionFactory">
            <property name="brokerURL" value="tcp://localhost:61616" />
          </bean>
</entry>

So, If I wanna use the ws-notification in the lwcontainer,may i configure
the connection like following:
<sm:activationSpec>
        <sm:component>
          <bean class="org.apache.servicemix.wsn.spring.WSNSpringComponent
">
     <property name="connectionFactory"
ref-key="java:comp/env/jms/wsnotificationCF" />           </bean>
        </sm:component>
   </sm:activationSpec>

I wanna know whethere reference the JNDI entity  in the servicemix.xml or
not?


--
View this message in context:
http://www.nabble.com/How-to-confige-JMS-in-the-component-deployed-in-the-lwcontainer--t1759606.html#a4895480
Sent from the ServiceMix - User forum at Nabble.com.


Reply via email to