[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scoped deployments

[clebert.suconic@jboss.com]

The Class-path entry worked smoothly...

For both compilation and runtime. Adding for instance common-loggin to the ClassPathEntry solved a compilation I had on a test.

I was also considering declaring other dependencies into jboss-messaing-client.jar on that Class-path entry, just to make it easier to customers using jboss-messaging-client.jar instead of jboss-all-client.jar. since this doesn't cost anything and would be helpful.

For example.. declaring JNDI libraries would be helpful.

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

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