Hi
On 21/05/13 00:10, Penmatsa, Vinay wrote:
Hi Sergey,
Do these annotations apply to Provider based REST services? I have used these
in JAX-RS services, but not for JAX-WS provider based stuff.
What I've done with XML payloads (payload mode) is
1. take the request xml, manually unmarshal using
Hi,
Not sure if this will suffice, but you can reference spring bean id's in
java first @Policy annotations, for example:
https://github.com/pellcorp/cxf/blob/master/JavaFirst/src/main/java/com/pellcorp/server/security/SecuritySimpleServiceImpl.java
See that I have used:
Hi,
Redirecting it to the users list.
I think you need to configure Tomcat not to decode URI, looks like it
decodes %20 before delegating to CXF.
Cheers, Sergey
On 21/05/13 12:10, Bhaskar wrote:
Hi CXF gurus,
I am getting the following error with the environment as Tomcat 7.0.40
CXF 2.7.5
Hi all
I'm currently debugging an issue w/ CXF where fields are coming in wrong to
our webservice (CXF is the client). I have debug logging turned on but the
payloads are too large so I can only see the first 64kb of the message. Is
it possible to have CXF keep the files that it creates rather
Hi, does anyone knows how can I do a cxf web service with user validation
with kerberos?
Saludos cordiales/kind regards,
Diego Cando
JR Electric Supply / Consorcio MTE Latinus
Hi Diego,
Sergey has written a blog article about this:
http://sberyozkin.blogspot.de/2012/08/master-kerberos-security-with-apache-cxf.html
Christian
On 21.05.2013 17:05, Diego Cando wrote:
Hi, does anyone knows how can I do a cxf web service with user validation
with kerberos?
Saludos
Hi Christian
thanks for pointing to that entry, it may be a JAX-WS related question
though,
Diego - please follow the links to blog entries which Colm did if it is
WS related
Thanks, Sergey
On 21/05/13 16:32, Christian Schneider wrote:
Hi Diego,
Sergey has written a blog article about
Not sure what is the best approach to suggest, as your question is somehow
indirect and maybe there is another way to analyze the issue..
If you are talking about the temporary files that are created during
processing, you need to write an interceptor to interfere with the normal
operation of
Haven't seen any response to this so far. Any ideas?
BTW- This is using CXF 2.5.8
-Nick
-Original Message-
From: Nick Komen [mailto:nick.ko...@ldschurch.org]
Sent: Friday, May 17, 2013 3:04 PM
To: users@cxf.apache.org
Subject: Request Wrapper Rendered as Nillable in WSDL
I recently
This is honestly not something I'm planning on spending much more time on as,
IMO, it's not a bug in CXF or, even if it is, would require some support for
Oracle. If it's an interaction problem between CXF and JAXB, then Oracle has
the same problem with their JAX-WS tools and the root of the
aki
In my case, the request body is too large to show in the debug logging.
That limits it to 64kb. This is for an outbound web service call we're
making using CXF as our runtime, so I'm not sure how to enable interceptors
that way.
On Tue, May 21, 2013 at 12:44 PM, Aki Yoshida
Hi Fernando,
Colm means that, accordingly WS-Security, signature of message body or body
elements should be placed into SOAP security header, not SOAP body.
Do you have good reasons not to use CXF security features to sign your message
elements and do it manually?
Regarding your problem:
Currently, I use the JVM option
org.apache.cxf.logging.enabled
and I see this output:
Message (saved to tmp file):
Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
(message truncated to 65536 bytes)
On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp dk...@apache.org wrote:
On May 21,
On May 21, 2013, at 1:11 PM, John D. Ament john.d.am...@gmail.com wrote:
aki
In my case, the request body is too large to show in the debug logging.
That limits it to 64kb.
Actually, I think the debug logging defaults to 100K, not 64K.
This is for an outbound web service call we're
Yes, basically I followed the restful_dispatch sample, but built over it
somewhat complex.
I try to show an example:
@XmlRootElement(name=customer)
@XmlAccessorType(XmlAccessType.FIELD)
public class Customer {
@XMLElement
private String id;
//
On May 21, 2013, at 1:41 PM, John D. Ament john.d.am...@gmail.com wrote:
Currently, I use the JVM option
org.apache.cxf.logging.enabled
and I see this output:
Message (saved to tmp file):
Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
(message truncated to 65536 bytes)
Ah.
Hmmm
Looking at http://cxf.apache.org/docs/debugging-and-logging.html
I don't see any option to specify the limit. I do see in the code the
alternate constructors, but since I'm using JBoss AS 7 and just the JVM
option I don't see a way to tell it to use the alternate limit.
John
On Tue, May
On May 21, 2013, at 1:58 PM, John D. Ament john.d.am...@gmail.com wrote:
Hmmm
Looking at http://cxf.apache.org/docs/debugging-and-logging.html
I don't see any option to specify the limit. I do see in the code the
alternate constructors, but since I'm using JBoss AS 7 and just the JVM
Daniel,
Thanks. I added
@org.apache.cxf.annotations.Logging(limit =
Integer.MAX_VALUE,inLocation=file:///tmp/cxf/in.txt,outLocation=file:///tmp/cxf/out.txt)
To my interface (AppPortType.class). Is there somewhere else it should go?
John
On Tue, May 21, 2013 at 2:13 PM, Daniel Kulp
On May 21, 2013, at 2:35 PM, John D. Ament john.d.am...@gmail.com wrote:
Daniel,
Thanks. I added
@org.apache.cxf.annotations.Logging(limit =
Integer.MAX_VALUE,inLocation=file:///tmp/cxf/in.txt,outLocation=file:///tmp/cxf/out.txt)
To my interface (AppPortType.class). Is there
They do, I use CXF annotations in other places.
When I instantiate, all I'm doing is
App a = new App(http://my-host/myservice;);
AppPortType apt = a.getPortType();
apt.doSomething();
anything special needed?
On Tue, May 21, 2013 at 2:38 PM, Daniel Kulp dk...@apache.org wrote:
On May 21,
On May 21, 2013, at 2:42 PM, John D. Ament john.d.am...@gmail.com wrote:
They do, I use CXF annotations in other places.
When I instantiate, all I'm doing is
App a = new App(http://my-host/myservice;);
AppPortType apt = a.getPortType();
apt.doSomething();
anything special needed?
HI folks. Can anybody provide info on why I may be seeing this runtime
error:
[java] java.lang.RuntimeException:
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration
problem: Unable to locate Spring NamespaceHandler for XML schema
namespace
I need to include a unique value in an http header field for each request from
my CXF client to the web service provider.
It's my understanding that I can do this when I initialize a port:
ServiceControllerAdapter svc =
adapter.getServiceControllerAdapter();
Client
Hi
On 21/05/13 18:42, Penmatsa, Vinay wrote:
Yes, basically I followed the restful_dispatch sample, but built over it
somewhat complex.
I try to show an example:
@XmlRootElement(name=customer)
@XmlAccessorType(XmlAccessType.FIELD)
public class Customer {
@XMLElement
Thank you, that helped us get it working!
Steve
From: Freeman Fang freeman.f...@gmail.com
To: users@cxf.apache.org; Steve Wardell ok...@yahoo.com
Sent: Monday, May 20, 2013 9:18 PM
Subject: Re: Can't Add ReplyTo Header
Hi,
Ensure you add
Fixed now - thanks
Sergey
On 30/04/13 20:23, wiz...@yahoo.com wrote:
Okay thanks Sergey..
yes for now we are on 2.1.4 so it's fine and if we must move to 2.2.0 then I'll
just have a wrapper for the
jackson provider by extending it myself and adding implements message reader
and writer to it..
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋
www.camelone.org : The open source integration
Hi,
Ensure you have cxf-rt-transports-http-jetty.jar on your class path.
If you use maven, add dependency like
groupIdorg.apache.cxf/groupId
artifactIdcxf-rt-transports-http-jetty/artifactId
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web:
Hi,
As you already have port(the proxy) pool, which means there won't be multiple
thread access same proxy at the same time, you actually needn't set
thread.local.request.context.
If there's only one proxy, you need set thread.local.request.context, using
code like
30 matches
Mail list logo
