This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Having trouble to add new Application to the WAS(using Administrative console). Application file is jar that contains MDB class implementation and ejb-jar.xml. If deployment descriptor contains activation config property then I am getting an error that file is corrupted, removing activation config property solve my problem with creating new application that is bound to our JCA Adaptor/Resource Activation Spec. Not sure why I am getting an error, since <activation-config> is standard element that can be specified in MDB deployment descriptor, or I have to do something special for WAS, same deccriptor works fine with JBoss. So is anybody aware why I am getting this error if <activation-config> is defined in my ejb-jar.xml.
Well just for anybody who is wondering why it was a failure in my case, according ESB 2.1 message-agnostic element <activation-config> must be defined along with <message-destination-type> element for JMS based MDB (it could be javax.jms.Queue or javax.jms.Topic) and it is IMPORTANT!! to specify it
In short just adding <message-destination-type>javax.jms.Queue</message-destination-type> to deployment descriptor just solve problem