The latter sounds reasonable to make clients aware of violation of
protocol, but probably as a configurable option (strict mode?). Spec does
not tell how server should behave in these cases?
14. jan. 2014 00:21 skrev Daniel Kulp dk...@apache.org følgende:
On Jan 13, 2014, at 2:52 PM, Jose María
The client is a web browser and we can live with it, just wanted to ensure
it wasn't an unexpected error.
On Monday, 13 January 2014, Sergey Beryozkin wrote:
Hi,
On 13/01/14 10:46, Paul O'Brien wrote:
Thanks Sergey,
Your information was helpful and I narrowed the problem down to the
At the end i was able to set this up thanks to your advices and some google.
I used JAAS and CXF JAASAuthenticationFilter.
To not overcomplicate things i've used BASIC authentication using property
file to store credentials in plain text.
The only point here is to be aware of Base64 encode the
Hello,
How can i setup a different annotation for checking authorization with
SecureAnnotationsInterceptor?
By default it expects javax.annotation.security.RolesAllowed but since it
is not part of Java SE i am not able to use it. However i've read that i
could use a different annotation ... it
Hi
On 14/01/14 10:54, blacar wrote:
Hello,
How can i setup a different annotation for checking authorization with
SecureAnnotationsInterceptor?
By default it expects javax.annotation.security.RolesAllowed but since it
is not part of Java SE i am not able to use it. However i've read that i
Hi,
Thanks a lot for the reply. We are using the non Spring Servlet. Presumably,
then, in web.xml I would need only to include the entry...
init-param
param-namejaxrs.properties/param-name
param-value
serializeAsArray=true
/param-value
/init-param
Is that it?
Hi
On 14/01/14 11:34, rpd wrote:
Hi,
Thanks a lot for the reply. We are using the non Spring Servlet. Presumably,
then, in web.xml I would need only to include the entry...
init-param
param-namejaxrs.properties/param-name
param-value
serializeAsArray=true
I was wrong, in fact it is already being tested, you need to do
something like:
init-param
param-namejaxrs.providers/param-name
param-value
org.apache.cxf.jaxrs.provider.json.JSONProvider(
dropRootElement=false
Hi Sergey,
I've created a custom annotation. My intention is to use it as
@Secured(admin). I've configured it as you told and i can see it defined
at runtime as annotationClassName attribute ... so, Thanks!
@Target({ElementType.METHOD, ElementType.TYPE})
@Retention(RetentionPolicy.RUNTIME)
Hi
On 14/01/14 13:22, blacar wrote:
Hi Sergey,
I've created a custom annotation. My intention is to use it as
@Secured(admin). I've configured it as you told and i can see it defined
at runtime as annotationClassName attribute ... so, Thanks!
@Target({ElementType.METHOD, ElementType.TYPE})
I am not sure but it looks like findRoles code is executed before
annotationClassName is setted with the new value then the methodRolesAllowed
gets fill with wrong information.
I'll have to confirm this point.
--
View this message in context:
Yes ... changing the order of the properties fixes it.
Thanks!
--
View this message in context:
http://cxf.547215.n5.nabble.com/SecureAnnotationsInterceptor-using-non-default-annotation-tp5738528p5738544.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi,
We have a spring-cxf ( Spring 3.0.4, CXF 2.5.10, Java 6) web service
application deployed in WAS 8.0.0.7 @ Linux machine. We are able to access
all services through soap ui by directly using ip on url (through Linux IP
in which application installed). Now the app server is behind the Web
Ok thanks - will investigate this too. Rob
From: Sergey Beryozkin [via CXF] ml-node+s547215n5738536...@n5.nabble.com
To: rpd robpodol...@yahoo.co.uk
Sent: Tuesday, 14 January 2014, 12:25
Subject: Re: NON-SPRING JSON array serialization workaround please??
Thanks - useful to know and it would indeed be a handy feature to be able to do
this. By writing my own application do you mean that I would follow...
http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAX-RSservicesprogrammatically
using
On 14/01/14 15:34, rpd wrote:
Thanks - useful to know and it would indeed be a handy feature to be able to do this. By
writing my own application do you mean that I would follow...
Hi,
you may remember I've had problems with this on the client side before (and,
for the record, I still believe the current code is suboptimal, tying the
correlation method used to sync/async etc.), and I'm now fighting with this
on the server side as well.
I have a CXF service implementation
Hi all,
I am having problems figuring out how to log the Request and Response
objects after successfully calling a .NET Web Service. I created the
client using Eclipse Kepler that generated all the skeleton code for me.
I'm using the 2.7.8 version of CXF and Java jdk1.7.0_45.
I've read a lot
Hello,
If I put property checkFaults=false (in sringframework application
context file), only SoapFault Messages runs as expected.
My service return a Response object. The service response is 200 (OK), send
me a Response (I see it, in the server-log), my client obtain a Response
object but, all
http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-LoggingMessages
Client client = ClientProxy.getClient(port);
client.getInInterceptors().add(new LoggingInInterceptor());
client.getOutInterceptors().add(new LoggingOutInterceptor())
In spring application context:
Ah, I missed that I should be adding the Client object via the
getClient(port) method.
Thanks much for nudging me in the correct direction.
On Tue, Jan 14, 2014 at 12:35 PM, José Manuel Prieto
joseman...@prietopalacios.net wrote:
Hi Sergey.
Sure, so long as it's possible for the service implementation to map an
attachment to the the generated temp file, that'd work. I guess for the
particular use case I was describing it's slightly less clean, since the user
needs to take into account the fact that the data may be in
If any idea on same...please help...we are struggling on it...
--
View this message in context:
http://cxf.547215.n5.nabble.com/Error-reading-XMLStreamReader-SOAPUI-but-works-fine-in-browser-tp5738545p5738566.html
Sent from the cxf-user mailing list archive at Nabble.com.
23 matches
Mail list logo