Re: CXF bean property validation

Thanks for the link; we have sort of decided to let hibernate do it, I thought of web services layer validation as to avoid unnecessary data layer hits, but it may be not such a big deal. Josef Dabernig-4 wrote: > > hello vitaly, > > i don't know, if cfx has such a thing. > > maybe hibernate

Re: CXF & Camel & Spring & ActiveMQ Integration Problems

It's on the client side. The "NewServlet" is a client to the actual web service. In the simple front-end case, points CXF to the WSDL, and I figure that's how CXF can auto-generate the stub on the fly behind the scene. In my code first approach, I don't go through the step of generating bind

RE: unsupported operation exception

Hi Cyrille, Thanks very much for your response. I should've been more clear in my email that it was infact the wadl generation. The actual service deploys and runs fine. Thanks again. Cheers, Matt. -Original Message- From: Cyrille Le Clerc [mailto:cyri...@cyrilleleclerc.com] Sent: Mon

Re: CXF bean property validation

hello vitaly, i don't know, if cfx has such a thing. maybe hibernate validator https://www.hibernate.org/412.html i used it sucessfully two years ago, but i can't tell about the current state, as things seem to be changing because of JSR 303: Bean Validation http://jcp.org/en/jsr/detail?id=30

Re: [New feature] Logging in ATOM Feeds and pushing to client

Hi Andy - At the moment the log events are embedded inside feeds, [...] it would make sense to let users choose that a single Atom entry Agree, can be done easily as next strategy (converter class) so user has full control of pair of format (converter) and batch size. I have to take a look o

CXF bean property validation

Hi All, Does anybody know if there is a standard way to deal with property validation? For example if my request POJO has N properties can I somehow enforce validation of things such as String length, null, Not Null etc. Common stuff.. Just don't want to reinvent the wheel in case CXF already has

Re: Fake the understanding of a "soap:mustUnderstand" header

You can step on normal processing by making a following hack: 1. Make a custom interceptor either extending AbstractSoapInterceptor or AbstractPhaseInterceptor 2. Install it right after CXF default ReadHeadersInterceptor for example: public IgnoreMustUnderstandHeadersInterceptor(Bus b) {

Re: URI parsing (for fun and profit)

Hi John You might want to try UriInfo.getPathParameters(false) which will return the multivalued map of path template variables to the list of values pairs...Unless you have the same template variable used in multiple path annotations (probably not a good idea), every list will contain a single

URI parsing (for fun and profit)

I managed to hook into our departmental logging infrastructure by building inbound and outbound logging interceptors... Cool stuff! I'm using JAX-RS, by the way. Anyway, on that note, I'd like to record an event like: GET /fooapi/v1/myresource/TCAS81121/subresource/EenieMeenie?a=b&c=d as, s

Re: unsupported operation exception

Hi Cyrille Thanks for your patch... It's very unfortunate the existing WADL tests have proved to be rather primitive in that they don't expect that ObjectFactories or some other artifacts such as jaxb.index can be available and thus haven't isolated this issue. I have actually missed the messa

Re: unsupported operation exception

Hello Matthew, I faced the same problem in my JAX-RS application. I created CXF-2556 "UnsupportedOperationException in WadlGenerator" and proposed a patch. Unfortunately, I don't see any workaround waiting for the patch. As our application doesn't really need the WADL generation, we will wa

Re: unsupported operation exception

Hello Matthew, I faced the same problem in my JAX-RS application. I created CXF-2556 "UnsupportedOperationException in WadlGenerator" and proposed a patch. Unfortunately, I don't see any workaround waiting for the patch. As our application doesn't really need the WADL generation, we will

Re: [New feature] Logging in ATOM Feeds and pushing to client

Hi Sergey, good points Sergey Beryozkin-2 wrote: > > Just CC-ing to the dev list, as this feature is still being developed, > given that CXF 2.2.6 will only be released early next year. > Agreed. I mentioned 2.2.6 in documentation to avoid confusion like this "I am using latest available relea

To implement chat application between server and client

Hi all, I need to create an application to have a chat between server and client. I did it using java networking concept. But i m unaware of doing the same in cxf. Where am i supposed to start with ? and How to get client side response to server and vice versa? Thanks for your time, Any help i

Re: [New feature] Logging in ATOM Feeds and pushing to client

Hi Andy I've just had a chance to read the documentation you put in place, I think it is very impressive. Just CC-ing to the dev list, as this feature is still being developed, given that CXF 2.2.6 will only be released early next year. I have just few comments. They're more about some additio

Fake the understanding of a "soap:mustUnderstand" header

Hi, I have a CXF endpoint that uses @WebServiceProvider to process the SOAP XML. The sender uses WS-Security so the message includes in its SOAP header: xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; soap:mustUnderstand="1"> This causes CXF to

CXF JAX-WS implementation creates a new JAXBContext for each webservice published

Hi All, With CXF 2.2.2 and 2.3.0, I observed that CXF JAX-WS implementation creates a new JAXBContext instance for each webservice published. Similar issue was raised with CXF JAX-RS implementation, bug #CXF-1406 (http://issues.apache.org/jira/browse/CXF-1406) and it has been mentioned that