[jboss-dev-forums] [Design of POJO Server] - Re: What supplies the destination ActivationConfigProperty?

[adrian@jboss.org]

This should be coming from the "getDestinationJNDIName" in
the MessageDrivenMetaData:

See the JBossJMSMessageEndpointFactory not the plain MEF


  |    /**
  |     * Add activation config properties
  |     * 
  |     * @throws DeploymentException for any error
  |     */
  |    protected void augmentActivationConfigProperties() throws DeploymentException
  |    {
  |       super.augmentActivationConfigProperties();
  |       
  |       // Hack for old style deployments (jms)
  |       if (messagingTypeClass.equals(MessageListener.class))
  |       {
  |          // Old style deployment
  |          if (metaData.getMessagingType() == null)
  |          {
  |             checkActivationConfig("destination", metaData.getDestinationJndiName());
  | 

As long as you don't specify the message-listener in the ejb-jar.xml
then it will assume it is not a jca1.5 deployment and then create the
activation config properties from the old JBoss/JMSContainerInvoker metadata.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095987#4095987

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095987