Minimal dependencies

Hello, I'm using CXF as shown in Building your cxf project with mavenhttp://cwiki.apache.org/CXF20DOC/building-your-cxf-project-with-maven.html and comparing to what is shown in A simple JAX-WS servicehttp://cwiki.apache.org/CXF20DOC/a-simple-jax-ws-service.html I noticed that, following the

Publishing services via Endpoint

Hi, Our application is a library that needs to publish extra services to support its functionality. Our library is initialized in the client application's main method and then starts publishing its services. Suppose we want to publish these services via the Endpoint.publish method.

Re: [Newbie] problem : No binding factory for namespace http://schemas.xmlsoap.org/wsdl/http/ registered

Hi Dan, I'm using 2.0-incubator version as it was described in the maven doc section (http://cwiki.apache.org/CXF20DOC/maven-integration-and- plugin.html). I will try using 2.0.2, or maybe the 2.0.3 if it is available (I was cheking the roadmap, it was said that the 2.0.3 was waited for end of

Re: schema validation

Hi Dan, Thanks for your help as always - looks like upgrading to 2.0.3 upgrading XMLSchema resolved this issue. The only issue I have with this now is with xsd:restriction - they are not annotated, not supported, so am forced to reference the wsdl, not big deal, this works I am however still

Re: JAXWS WS Policy

Thanks for the reply James, maybe my understanding of this is incorrect, but I had hoped that by defining policy assertions for my endpoint (jaxws:endpoint) that these would be inserted into the served out wsld. The example seems to deal with a wsdl with the assertions already embedded, and

Re: JAXWS WS Policy

Hi Thanks for the reply James, maybe my understanding of this is incorrect, but I had hoped that by defining policy assertions for my endpoint (jaxws:endpoint) that these would be inserted into the served out wsld. +1. This is what shoud happen. As far as I'm aware no real WS-Policy work

Enumeration problem

Hi, Using CXF 2.0.2, I have a problem using CXF with a service which throws an exception which contains an enumeration field. The WSDL is generated correctly, and I use wsdl2java for generating client stubs. The WSDL shows the following : xs:simpleType name=fultyExceptionType

Monitoring CXF Webservices

Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially enumurate through the services, display basic info (basic config

Re: newb question - JDOMException with aegis binding?

The dependencies list on http://cwiki.apache.org/CXF20DOC/a-simple-jax-ws-service.html was what I was referring to. dkulp wrote: On Wednesday 07 November 2007, BrianP wrote: Thanks! Got it and it's working. Why is that not on the dependency list? What dependency list? It's in the

Re: Monitoring CXF Webservices

Could you use MBeans i.e. JMX? Vespa, Anthony J wrote: Hello, I am doing some planning for production deployment of the web services I am developing and am wondering about the best way to implement heart beats / diagnostics for the services themselves. Is there a way to trivially

RE: Monitoring CXF Webservices

That's generally what I'm looking at, I am wondering if there are examples or good patterns of use? -Original Message- From: Adrian C [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 9:17 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices Could you

RE: Gzip encoding

I've tried this and it doesn't seem to work. My config file is shown below. The http-conf works fine but not the jaxws:client. I've tried uisng a features instead of the inInterceptor but it makes no difference. The only time it works is when I use the config at the bottom which adds the

Re: Gzip encoding

Hi Richard, Which version of CXF do you use? I think it probably is a bug of the JaxWsClientProxyFactoryBean. Willem. Shaw, Richard A wrote: I've tried this and it doesn't seem to work. My config file is shown below. The http-conf works fine but not the jaxws:client. I've tried uisng a

Error calling simple JAX-WS service from Flex/Flash

I got my first simple JAX-WS service up and running. I got it deployed to Tomcat, and tested it successfully from a simple client (the client from 'a Simple JAX-WS service', but with a different address). Now I'm trying to connect to the service from a Flex/Flash client, and am getting the

Re: Error calling simple JAX-WS service from Flex/Flash

Remove geronimo-servlet_2.5_spec-1.1-M1.jar from you war first off and see how it goes from there BrianP wrote: I got my first simple JAX-WS service up and running. I got it deployed to Tomcat, and tested it successfully from a simple client (the client from 'a Simple JAX-WS service', but

Re: Error calling simple JAX-WS service from Flex/Flash

I removed it, and that produced the following error : Nov 9, 2007 10:22:38 AM org.apache.catalina.loader.WebappClassLoader modified SEVERE: Resource '/WEB-INF/lib/geronimo-servlet_2.5_spec-1.1-M1.jar' is missing And then a bit later in the log, I still have the '...geronimo-servlet... -

Re: Error calling simple JAX-WS service from Flex/Flash

are you sure its removed from the war your expanded web-inf/lib directory? I removed it, and that produced the following error : Nov 9, 2007 10:22:38 AM org.apache.catalina.loader.WebappClassLoader modified SEVERE: Resource '/WEB-INF/lib/geronimo-servlet_2.5_spec-1.1-M1.jar' is missing

Re: Error calling simple JAX-WS service from Flex/Flash

My bad, I wasn't doing a 'clean' in my script so it was reloading it from a temp/build area. So it's gone now, and I'm left with INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault ... Caused by: java.lang.IllegalArgumentException at

Re: Error calling simple JAX-WS service from Flex/Flash

are you logging the messages in out and out of cxf - is the soap action/ws-addressing correct? BrianP wrote: I got my first simple JAX-WS service up and running. I got it deployed to Tomcat, and tested it successfully from a simple client (the client from 'a Simple JAX-WS service', but

Re: Error calling simple JAX-WS service from Flex/Flash

I wasn't logging, so I searched here on how to do that in the beans.xml and added jaxws:features bean class=org.apache.cxf.feature.LoggingFeature / /jaxws:features to my endpoint. This enabled the logging, which enabled me to see the entire message. When I saw that I immediately saw my

Extending Security Interceptors

I'm implementing a simple web service using Apache CXF where I have to authenticate a user based on username and password. This is straightforward and I have the service working using the WSS4F Interceptors. The next phase of the project is making the service able to choose from a list of auth

RE: Monitoring CXF Webservices

Thank you for the tips! -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 10:28 AM To: cxf-user@incubator.apache.org Subject: Re: Monitoring CXF Webservices FYI You can get the published service name, port name and some performance metric

Re: Default WSDL generated from annotated class has elementFormDefault=unqualified

I'm looking for the same ability to set elementFormDefault=qualified using the Java -- WSDL approach, has anyone found an answer to this? I'm using the most basic approach of JAX-WS / JAXB / annotations. Thanks, Rich Jon Mountjoy wrote: Hi, The default WSDL generated from my annotated