привет.

во вторых ejb mdb описывались примерно вот так:

 <message-driven >
         <description><![CDATA[.....]]></description>

         <ejb-name>SomeMDB</ejb-name>

        <ejb-class>SomeMDB</ejb-class>

        <transaction-type>Container</transaction-type>
            <message-driven-destination>
            <destination-type>javax.jms.Queue</destination-type>
            <subscription-durability>NonDurable</subscription-durability>
         </message-driven-destination>

         <env-entry>
            <env-entry-name>siteID</env-entry-name>
            <env-entry-type>java.lang.Integer</env-entry-type>
            <env-entry-value><![CDATA[@@SITEID@@]]></env-entry-value>
         </env-entry>
         

      </message-driven>

собстна на 3-х можно описать примерно вот так

@MessageDriven(name = "SomeMDB",
        activationConfig = { 
        @ActivationConfigProperty(
                propertyName = "connectionFactoryJndiName",
                propertyValue = "java:/JmsXA"),

            @ActivationConfigProperty(
                    propertyName="destinationType",
                    propertyValue="javax.jms.Queue"),
            @ActivationConfigProperty(
                    propertyName="subscriptionDurability",
                    propertyValue="NonDurable"),
            @ActivationConfigProperty(
                    propertyName="destinationName",
                    propertyValue="queue/@@SITEID@@_E1")
        }
)
public class SomeMDB implements MessageListener {

а что делать с env-entry?