to handle maps like that in the
java_first_jaxws
sample in the CXF distribution.
Dan
On Wednesday, December 07, 2011 10:10:05 AM Default SPAM wrote:
Hi all,
I would like to submit a question since I have noticed an inconsistency
between WSDL generated
Hi all,
I would like to submit a question since I have noticed an inconsistency
between WSDL generated by org.apache.cxf.tools.java2ws.JavaToWS and
response sent by CXF.
I have a service like this:
@WebService(endpointInterface = be.eft.cbkv3.ws.WSExampleService,
serviceName =
Hi all,
I'm digging into including SPNEGO support for the web services (based on
CXF 2.2.4) I'm implementing.
On server side, using 'Servlet Transport
http://cxf.apache.org/docs/servlet-transport.html', it shouldn't be an
issue since handling of (SPNEGO) authentication is performed by Tomcat.
On
2009 3:44:38 am Spam wrote:
In my 'web.xml' I load services related configuration with:
servlet
servlet-nameCXFServlet/servlet-name
display-nameCXF Servlet/display-name
servlet
is picking up (in which case it IS needed)?
Dan
On Mon October 5 2009 4:37:25 am Spam wrote:
Hi All,
I answer by myself.
Even if I don't really know why, removing following lines from my
services configuration is fixing the issue (services are visible
Spam a écrit :
Hi All,
I've followed the guidelines from
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html; to
configure my web services inside Tomcat 6.0.
If I use the following configuration, everything in the cxf (log4j) log
file looks like the services are deployed successfully
Hi all,
I've written a two web services using Simple frontend.
For the first service (called 'WSClaimService') the (runtime) generated
WSDL looks like:
xs:schema attributeFormDefault=unqualified
elementFormDefault=unqualified
For the second service (called 'WSUserService') the (runtime)
Hi All,
I've followed the guidelines from
http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html; to
configure my web services inside Tomcat 6.0.
If I use the following configuration, everything in the cxf (log4j) log
file looks like the services are deployed successfully, but checking
with
