The mechanism by which the AxisService registers its service is questionable as instead of including a war with the required config it is explictly creating a DeploymentInfo object for the war and calling the web deployer. This broke when I made a change to use the DeploymentInfo.ucl as the web context parent class loader because the AxisService was not populating this. What is the reason for not bundling a war in the jboss-net.sar instead of the current behavior?
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
