Hi,
I'm using CXF in a client that is consuming the MS Exchange Web Service
(EWS).
I'm finding that one of the elements returned by this service (UniqueHash)
contains characters that are invalid in XML v1.0. As I have no control over
this I'm trying to use an inbound interceptor to drop the
Hello
Really, no one has this problem? I have the same problem with version
2.6.13.
thank you
Le 14/03/2014 15:40, Michel Labarre a écrit :
Hello
We running CXF 1.6.7 version with SOAP 1.1 wsdl. All run fine.
New services are required with SOAP 1.2. I run the Web Service
generator under
Hi all,
I am having a strange case of where despite the response being defined, the
code generated by wadl2java returns void instead.
The generated code looks like this:
@POST
@Consumes(application/x-www-form-urlencoded)
@Path(/password/{mail})
void
Note that there was a mistake in my first mail: see 2.6.7 and not 1.6.7!
Le 17/03/2014 15:05, Michel Labarre a écrit :
Hello
Really, no one has this problem? I have the same problem with version
2.6.13.
thank you
Le 14/03/2014 15:40, Michel Labarre a écrit :
Hello
We running CXF 1.6.7
Hi,Il giorno 15/mar/2014, alle ore 13:38, Andrei Shakirin ashaki...@talend.com ha scritto:Hi Marco,I would suggest to try simple Kerberos login using JAAS directly (with debug=true), perhaps it helps to spot the problem:Test code: URL conf =
Hi
How do you configure it with curl ?
In your opinion, what is the difference between the way you set it up in
curl and in CXF ?
Cheers, Sergey
On 17/03/14 15:53, Marco Di Sabatino Di Diodoro wrote:
Hi,
Il giorno 15/mar/2014, alle ore 13:38, Andrei Shakirin
ashaki...@talend.com
You have several response representations nearly all of them
representing errors, only one of them has a 204 status, which is 'void'
in JAX-RS.
You can use a -noVoidForEmptyResponses option to get Response generated
Sergey
On 17/03/14 13:37, Graham Leggett wrote:
Hi all,
I am having a
Hi Parwiz,
On 15/03/14 06:51, wiz...@yahoo.com wrote:
Hi,
for JAXRSClientFactory and WebClient
methods that allow user to pass in true for creating
thread safe proxies there is no way to pass in
long timeToKeepState to specify how long before cleaning up that state
to be passed down to
Hi,
I am deploying a sample CXF JAXRS service on WebLogic 12c. I can see the
service listing page on WebLogic 12c at
http://myserverip:7001/ecaching/services. However, when I access the
http://myserverip:7001/ecaching/Greet?_wadl link I get the following error:
Mar 17, 2014 12:35:10 PM
Hi,
The 1st exception to do with the getWriter() seems unrelated, and FYI it
has been fixed few days back.
Re the wadl query: please check the migration guide for 3.0,
cxf-rt-rs-service-description module is needed to support WADL queries
Cheers, Sergey
On 17/03/14 18:44, Sonam
Hi Andrei!
I monitor the exchanged messages and the service receives the request and
correctly sends the answer to the decoupled-endpoint (http-conduit). When
the service processing delays more than 60segs, a timeout occurs on the
client. I attach the Client Project
regards
Guzmán
Thanks Sergey.
Btw which version has the fix for getWriter()? I am already using the
3.0.0-milestone2.
thanks
-Sonam
-Original Message-
From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Sent: Monday, March 17, 2014 1:08 PM
To: users@cxf.apache.org
Subject: Re: Jaxrs Weblogic
You’ll likely need to do:
((ClientImpl)ClientProxy.getClient(proxy)).setSynchronousTimeout(18);
or similar. Unfortunately, there isn’t any other way to configure this. :-(
That said, I’d recommend a different approach….
There are a few different “types” of timeouts that may apply in
This is one of the “issues” I have with JAX-WS. The “interface” that is
generated is supposed to be completely generated from the portType. Thus, it
does not know from the portType that this is 1.1 or 1.2. The SOAPBinding
annotation should only go on the actual service object which
Using a transform for this won’t work as the XML parser (woodstox in our case)
would still not be able to parse the XML.
The only way to handle this would be to write an interceptor that would run
prior to the StaxInInterceptor that would take the InputSteam and wrapper it
with a new
On Mar 14, 2014, at 9:01 AM, Karnam, Jayashankar
jayashankar.kar...@in.pega.com wrote:
Is CXF trying to cache the Authorization objects somewhere? I have been
trying NTLM authentication with CXF, it works fine for the first invocation
if I provide wrong credentials, throws a 401 but the
On Mar 16, 2014, at 1:02 PM, Kaji Yuy tribeca.k...@gmail.com wrote:
Is it possible to generate the JAXB mapping classes in a way that would
allow the client to consume the response without a namespace?
This “looks” like the root element in the soap:Body. If that’s the case, it
would be
Thanks Daniel.
I worked that out about an hour ago and am implementing it now!
Thanks for the quick reply though.
It's a shame there's not an out of the box interceptor for this as it's
probably a pretty common use case.
Regards
Mike
On 18/03/2014 9:06 AM, Daniel Kulp dk...@apache.org wrote:
Hi all,
I am new to CXF.
I am using CXF v2.7.3.
I have incoming post request that contains JSON format data that needs to be
converted to a valid XML document.
Does CXF provide conversion of json to a valid xml directly with without
JAXB in the middle?
Which JSON provider can be used for this
Hi All:
We do custom validation on output of the SOAP body org.w3c.dom.Node against
a Schema object in a custom interceptor.
The problem is that org.w3c.dom.Node is implemented by SAAJ
(com.sun.xml.internal.messaging.saaj.soap.ver1_1.BodyElement1_1Impl) which
fails when we validate it with the
20 matches
Mail list logo
