On Wednesday 12 January 2011 5:01:39 pm mschipperheyn wrote: > No. No debugger. > > I realize that the underlying issue might be elsewhere. The problem is that > cxf hides these (real) exceptions, which in an of itself is the real and > imho very serious issue.
It's actually spring hiding these things. Not us. :-( My SUGGESTION would be to run a wireshark at startup time on both a working server and a non-working server and see if any network related things could be happening. For example, maybe something is trying to load a schema of the internet or similar and that is being dis-allowed on the production server. Dan > With previous issues, I handled that by simply disabling cxf. However, now, > the only difference between a perfect startup and this issue is enabling > that portion of cxf configuration which works fine on other systems. > > I'm not really sure where look. -- Daniel Kulp [email protected] http://dankulp.com/blog
