Announcement Announcement Module
No announcement yet.
Best Practice for Spring 3.1 in an EAR in JBoss? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Best Practice for Spring 3.1 in an EAR in JBoss?


    Are there any pointers to any form of "Best Practice" for using Spring within an EAR (within a JEE 5 environment at present, if it matters.)

    It's a new app that's under development, with JBoss being the corporate standard appserver. The app consists of a number of wars, (ejb) jars & pojo jars, deployed as an ear. At present the main use of Spring is for DI, which is typically being initiated via settings (empty bean.xml or minimal applicationContext.xml files) in the individual components. I'm considering adding Spring-amqp to the mix, which will probably need some explict configuring, which lead me to wonder about whether there was a better way of arranging the config than having multiple XML files?

    Does anyone have any thoughts or comments, please...