At last!
The final roadblock was a 7k cxf-rt-core-2.2.5.jar that some way some
how got downloaded to my repository from somewhere instead of the proper
389.3 Kb one. This, of course, did not contain any
org.apache.cxf.bus.CXFBusFactory class.
Not sure how such a thing could happen, and it was a
On Thu, 21 Jan 2010, Christian Landbo Frederiksen wrote:
Ok - got past this problem by starting from scratch with with
EAR-project etc. and adding the jars one at a time.
Some of my other jars was causing this - haven't figured out which one
yet, though
Spring 2.5.6.SEC01 + latest official re
Hi Sergey, Dan,
I got it working successfully using 2.2.7-SNAPSHOT! I appreciate the
continuing support!
Now, I'm going to build the client to parse this data.
best regards,
Allan
http://old.nabble.com/file/p27279908/fastinfoset2.png fastinfoset2.png
Sergey Beryozkin-2 wrote:
>
> Actually
Actually, it is not finished yet, should be ready shortly
- Original Message -
From: "Sergey Beryozkin"
To:
Sent: Friday, January 22, 2010 4:42 PM
Subject: Re: CXF 2.2.5 and Fastinfoset
Hi Allan
I can see the trunk build is done [1]
I did not know 2.2.x had fastinfoset intercepto
Hi Allan
I can see the trunk build is done [1]
I did not know 2.2.x had fastinfoset interceptors. Will merge there now...
cheers, Sergey
[1]
http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-Trunk-JDK15/lastBuild/changes
Hi Sergey,
Thank you! What version did you check in the fix?
Hi Sergey,
Thank you! What version did you check in the fix? 2.2.5 or 2.3? Am I going
to download the snapshot version?
Please advice.
Best regards,
Allan
Sergey Beryozkin-2 wrote:
>
>
> Hi Allan
>
> Sorry for a delay, I just fixed it. JAXBElementProvider was not checking
> for stax in/
I'm working on a web-service client using a set of CXF-based tools
developed by a colleague who knows a lot more about WSs than I do
(although he couldn't explain the following problem).
The client passes a byte[] and a parameter list to a WS method, which
returns a response containing an XML elem
Hi Allan
Sorry for a delay, I just fixed it. JAXBElementProvider was not checking for stax in/out factories, it was only checking for already
created readers/writers. There also was a minor issue to do with reading the fastinfoset on the client side
One thing I observed is that on the client
Hi Dan,
Yes - that did it. Thanks a lot!
Regards,
John
On 21 Jan 2010, at 15:22, Daniel Kulp wrote:
>
> Can you may a small (compatible) change to the xsd file?
>
> You probably have something like:
>
>
>
>
> .
>
>
> If you change that to:
>
>
>
>
>
Hi
Hi All,
Found the cause for most. Still an odd error though. So here is the cause:
The service explicitely says @Consumes("text/xml") , while my client
specified:
RequestEntity re = new FileRequestEntity(
new File("somefile.txt"),
"application/xml; charset=IS
Hi Gabo
Hi Team,
Sorry this would be a bit lengthy. Just want to put everything needed to debug this available. I would summarize the issue later
in the end of the post.
No problems. will just do some snips...
I have the following class declaration:
@WebService(name="MyService",
t
Hi All,
Found the cause for most. Still an odd error though. So here is the cause:
The service explicitely says @Consumes("text/xml") , while my client
specified:
RequestEntity re = new FileRequestEntity(
new File("somefile.txt"),
"application/xml; charset=ISO-885
Thanks, Daniel. That got me past that roadblock. Now on to the next one:
I make it through the service constructor - but I still can't use the
service.
Jan 22, 2010 7:19:49 AM org.apache.cxf.BusFactory newInstance
SEVERE: Failed to instantiate bus factory.
java.lang.ClassNotFoundException: org.
Hi Team,
Sorry this would be a bit lengthy. Just want to put everything needed to
debug this available. I would summarize the issue later in the end of
the post.
I have the following class declaration:
@WebService(name="MyService",
targetNamespace="http://some.domain.com/";)
@SOAPBind
Hi,
One option is to register your own WebApplicationExceptionMapper which will return only the status for all cases (same as the
default one) except for a case when a caught WebApplicationException contains Response with 403.
If WebApplication is thrown from a RequestHandler then the simpler op
15 matches
Mail list logo