jBPM afaik has the xsd's in a local resolver so should not need to go to the internet. But it could be that (since the xsd changed in 4.2) this was overlooked.
Regarding the logging.... Well, I (ofcourse ;-)) meant logging of what happens DURING the deploy. So if it turns out not to be a internet access thing, turn on logging of lots of other libraries. And before you say 'which?' I'd go for 'all' OR maybe run JBoss in debugging mode and put a breakpoint on the deploy and go from there. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270053#4270053 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270053 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
