My project builds and deploys as an ear properly in 3.2.4, but fails with a classloader problem in 4.0.0. I would greatly appreciate help solving this problem.
The ear contains (among other things) a jar containing all our app code, including the code specifying and used by a few mbeans. The mbeans are deployed as a sar file inside the ear. The sar file contains nothing but a jboss-service.xml and a manifest file; the latter has only header info (it's autogenerated by the xdoclet jar task).
The jboss-service.xml looks like this:
<?xml version="1.0" encoding="UTF-8"?> <service> <mbean code="com.portblue.mgmt.ConfigurationManager" name="com.portblue.mgmt:service=ConfigurationManager"> </mbean> <mbean code="com.portblue.mgmt.SweeperManager" name="com.portblue.mgmt:service=SweeperManager"> <depends>com.portblue.mgmt:service=ConfigurationManager</depends> <depends>jboss.j2ee:jndiName=com.portblue.model.admin.user.SweeperFacadeRemoteHome,service=EJB</depends> <depends>user:name=QuartzService,service=QuartzService</depends> </mbean> </service>