Error creating SAAj Factory Instnace on Jboss and Cxf 2.0.4

Hello All, We have upgraded to CX's latest version, But We need to support one environmnet in the old CXF version 2.0.4. When I try to call Service from my CXF cLient, I get the following exception: I am not even able to construct soap request. javax.xml.ws.WebServiceException: Cannot create SAAJ

Getting javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.

All, I am trying to publish some services to client using CXF 2.1.4. It used to work till last week and suddenly theserver start up is failing. Jboss 4.2. I see the following error in logs. I do notknow why is it checking in jboss bin folder for all enums etc.. Can you please help since I am st

Re: Unmarshalling error while processing soap fault.

e: > > > just for those elements if you don't want the entire schema to be be > unqualified. > > Dan > > > On Thu November 12 2009 11:34:03 am deepika vadapalli wrote: > > But this time error is slightly different. > > > > Unmarshalling Error: une

Re: Unmarshalling error while processing soap fault.

ication.wdw.com/}severity> Can you help me out... Thanks, Deepika On Thu, Nov 12, 2009 at 11:25 AM, deepika vadapalli < deepikavadapa...@gmail.com> wrote: > Thanks for the response. > > But I get the same exception even if I change my schema from atrributes to > elements. >

Re: Unmarshalling error while processing soap fault.

d according to that schema. In the > schema, > they are all and thus should be attributes, not child > elements. > > Dan > > > On Wed November 11 2009 4:02:30 pm deepika vadapalli wrote: > > Dan, > > > > I am sorry. Actual for that call, I g

Re: Unmarshalling error while processing soap fault.

.valueobject.application.wdw.com/"; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"/<http://www.w3.org/2001/XMLSchema-instance%22/> > On Wed, Nov 11, 2009 at 3:54 PM, Daniel Kulp wrote: > > What does your ValidationServiceExcepti

Unmarshalling error while processing soap fault.

Hi All, I use CXF 2.1.7. I have a soap message which generates valid fault. I am able to unmarshall faults from other services properly. When I call this particular service, in my client code, I get Unmarshlling exception. When I check, the object has all the attributes, the fault messgae has sen

Re: LoggingInterceptor called twice if CachedOutStream writes to temp file (message larget than 64kb)

I tried the below work around but its not passing. I mean if (message.containsKey("logging was done")) is false when it enters next time. On Wed, Oct 28, 2009 at 4:03 PM, Daniel Kulp wrote: > On Wed October 28 2009 3:47:07 pm deepika vadapalli wrote: > > No.the request is hu

Re: LoggingInterceptor called twice if CachedOutStream writes to temp file (message larget than 64kb)

d turn > off > streaming on the sending side? Authentication things? Redirect? > Chunking? > Etc > > How large is the SENT message? > > Dan > > > On Wed October 28 2009 5:01:14 pm deepika vadapalli wrote: > > But the problem is with CXF 2.1.7, its

Re: LoggingInterceptor called twice if CachedOutStream writes to temp file (message larget than 64kb)

Is there any way that I can make it work for cxf 2.1.7 latest version also? Please let me know. Thanks, Deepika On Wed, Oct 28, 2009 at 5:28 PM, deepika vadapalli < deepikavadapa...@gmail.com> wrote: > *The most important thing is it is working with CXF 2.0.4 incubator > versio

Re: LoggingInterceptor called twice if CachedOutStream writes to temp file (message larget than 64kb)

something on the http conduit that would turn > off > streaming on the sending side? Authentication things? Redirect? > Chunking? > Etc > > How large is the SENT message? > > Dan > > > On Wed October 28 2009 5:01:14 pm deepika vadapalli wrote: > >

Re: LoggingInterceptor called twice if CachedOutStream writes to temp file (message larget than 64kb)

org.apache.cxf.jaxws.JaxWsClientProxy.invoke(*JaxWsClientProxy.java:127*) On Wed, Oct 28, 2009 at 4:03 PM, Daniel Kulp wrote: > On Wed October 28 2009 3:47:07 pm deepika vadapalli wrote: > > No.the request is huge but the resposne is just confirmation number. > > I get the resposne, log it once and then I get Null po

Re: LoggingInterceptor called twice if CachedOutStream writes to temp file (message larget than 64kb)

; Without a reproducible test case, I'm not sure if there is anything I'm > going > to be able to do. > > One thought: is the message coming back a fault? (hard to imagine a > fault > that big, but I suppose it's possible) > > Dan > > > On Wed Oc

LoggingInterceptor called twice if CachedOutStream writes to temp file (message larget than 64kb)

Hello, I have my own SELoggingInterceptor. But it is same as LoggingInInterceptor code with no difference. I see that when message is larger than 64kb i.e. when CachedOutputStream write to temp file, this interceptor is called twice. First time, I process the message and second time I get Stream

Re: CXF calling custom interceptor twice

org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) 15:43:54,705 ERROR [STDERR] at java.lang.Thread.run(Unknown Source) On Tue, Oct 27, 2009 at 3:15 PM, Daniel Kulp wrote: > On Tue October 27 2009 2:06:49 pm deepika vadapalli wrote: > > Hello, > > > > I create a

CXF calling custom interceptor twice

Hello, I create a CXF client and add my custom interceptors to it. When I call the service, in some scenarios when request is long, I see that my interceptor is called twice. For the first time, I recieve response , handle it and log it. Since its automatically goes into second time, I get Stream

Unexpected EOF in prolog problem using CXF 2.1.5 with WebSphere 6.1

Hi, I am using CXF 2.1.5 client and the server is WebSphere 6.1. This error is blocking me since many days. Caould you please help me out.. When I make a service call from the client, I get Stream is closed exception. But in the logs, I see there is resposne from the server. But I am not able to