Hello
Hello CXF users/developers, I'm happy user of CXF 2.4 and trying to upgrade
to CXF 3.0 to take advantage of JAx-RS 2.0.
I'm trying to deploy the services in weblogic 10.3.6 with jdk 7 but ending
with the following error. Not sure where to trouble shoot and looking
forward for any help.
I
Hi
As far as I recall it should work with JSONProvider pre-configured to
support application/x+javascript or similar which is not possible with
Jackson which is where a writer interceptor comes in where it
temporarily sets application/json for Jackson to write the data out
I'll double check
Is there any way you could create a full test case for this? Maybe attach it
to a JIRA or as a github repo?
Thanks!
Dan
On Jun 28, 2014, at 12:27 PM, Shriram wrote:
> Thanks Dan
>
> I've just tried uploading a image of more than 5gb size with local
> transport.
> This is just an example p
Hi,
thanks for posting the code, I'll look at what can be done at Jettison
level asap when I will be working on the new release
Cheers, Sergey
On 01/07/14 13:19, Lambert, Michael wrote:
If I understood you properly Sergey, you wanted me to paste the generated
class here. I hope this helps!
Hopefully next week.
New builds of WSS4J were just built today and vote started. If the vote for
that goes fine, we should be able to build the next CXF builds next week.
Dan
On Jun 30, 2014, at 11:02 AM, Ariel Cassan wrote:
>
> Hi everyone,
>
> I'm a member of the architecture team in
If this helps this is the ouput of
http://localhost:8080/user-service/userService?xsd=../schema/entity/user-v1.xsd
:
This XML file does not appear to have any style information associated with
it. The document tree is shown below.
http://www.w3.org/2001/XMLSchema";
xmlns:tns="urn:healthmedia:schem
Is there a way to ignore ALL mustUnderstand?
E.g. not matter if the Consumer sends:
"http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd";
or:
"
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
"
or whatever.
On Thu, Jun 26, 2014 at 11:34 AM, Col
Thats part of the problem Andrei. I have followed the examples and its just
not working for me. Can you take a look at my policy file and wsdl and see
if anything obvious sticks out as wrong?
https://github.com/MacFlecknoe/service-repository-sample/blob/master/schema/src/main/resources/policy/auth
I had the same error - the problem was that I had a wrong import :
javax.xml.ws.handler.MessageContext instead of
org.apache.cxf.jaxrs.ext.MessageContext.
--
View this message in context:
http://cxf.547215.n5.nabble.com/JAX-RS-error-in-start-up-server-tp5729730p5745892.html
Sent from the cxf
Hi all,
the JMS transport in CXF 2.x supports different settings for
replyDestination (ie. where the client looks for the reply) and
replyToDestination (what the client writes into the ReplyTo header, ie.
where the service provider actually sends the reply).
We make heavy use of this feature bec
Hi,
> -Original Message-
> From: Lambert, Michael [mailto:mich...@michaellambert.com]
> Sent: Mittwoch, 2. Juli 2014 14:05
> To: users@cxf.apache.org
> Subject: RE: policy attachment
>
> Thanks Andrei! That helps a lot... I'll try your suggestion and let you know
> how it
> goes.
>
OK.
Thanks Andrei! That helps a lot... I'll try your suggestion and let you
know how it goes.
Any insight as to why I can't get end point references to work? Is there a
trick to configuring it? I followed the example on the samples but can't
seem to get it to work with my wsdl. Does the end point need
On 01/07/14 16:33, David Karlsen wrote:
Great - that worked just fine!
Maybe the wiki should be updated?
Sure, I should've done it earlier, Colm reported it too.
I updated the migration page and that wiki page
Cheers, Sergey
2014-07-01 16:27 GMT+02:00 Sergey Beryozkin :
Hi
On 01/07/14 14
Hi,
If you use CXF >= 3.0.0, 2.7.12,
you should register
org.apache.cxf.ws.policy.attachment.external.URIDomainExpressionBuilder as bus
extension.
It supports all policy attachment URL syntaxes (except extension).
By default CXF registers the
org.apache.cxf.ws.policy.attachment.external.Endpoi
14 matches
Mail list logo
