Re: sealing violation problem

2008-05-23 Thread Craig Tataryn
I'll bet you its from an input in one of our other packages, one of our other packages has some mule deps... Craig. On Fri, May 23, 2008 at 9:28 AM, Benson Margulies <[EMAIL PROTECTED]> wrote: > I've seen this before. It results from two different versions of Jetty > in the classpath. > > On Thu,

Re: sealing violation problem

2008-05-23 Thread Benson Margulies
I've seen this before. It results from two different versions of Jetty in the classpath. On Thu, May 22, 2008 at 11:04 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > I've honestly never even heard of a sealing violation. A google search > yielded info like: > http://www.visi.com/~gyles19/fom-ser

Re: sealing violation problem

2008-05-22 Thread Daniel Kulp
I've honestly never even heard of a sealing violation. A google search yielded info like: http://www.visi.com/~gyles19/fom-serve/cache/173.html I would suggest looking at the classpath and other dependencies to see if there are multiple versions of jetty being picked up. Other than th

sealing violation problem

2008-05-22 Thread Craig Tataryn
Hi, I'm writing a unit test for one of my service implementations and followed the code listed here: http://cwiki.apache.org/CXF20DOC/a-simple-jax-ws-service.html#AsimpleJAX-WSservice-Publishingyourservice However, when it gets to the line: svrFactory.create(); I get a stack trace that indicates