Attached is a bigger than usual WSDL file. If you use it in a reference binding and generate the Java Interfaces you'll end up with roughly 800 classes if message parts are wrapped.
Then create the required JAXB transformers as well in the configruation.

Now if the packaged service jar is deployed it takes about 4 minutes and a very big chunck of ram to deploy.

18:51:57,910 INFO  [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-1) Apache Camel 1.0.0.Final (CamelContext: camel-12) started in 0.010 seconds
18:55:52,986 INFO  [org.switchyard.component.soap.OutboundHandler] (MSC service thread 1-1) Creating dispatch with WSDL vfs:/D:/test/bin/content/cadebill-service.jar/CadebillWebService.wsdl

It would be great if the load time and the memory footprint could be reduced.

A workaround is or course to reduce the WSDL and break it into multiple services but in some cases that may be impractical or not desired.