Finally worked with:
@WebServiceClient(name = "SalesService", targetNamespace =
"urn:sales.test.au/schema/common", wsdlLocation =
"classpath:SalesService.wsdl")
public class SalesService
extends Service
{
private final static URL SalesSERVICE_WSDL_LOCATION;
private final static
Hi,
This is getting very frustrating trying to get the project to find relative
paths to the WDSL.
Environment: Java 7
Build Tool: gradle
IDE: Intellij
The WSDL file runs fine in the IDE with :
@WebServiceClient(name = "SalesService", targetNamespace =
"urn:Sales.test.au/schema/common",
This is what worked for me for the benefit of anyone else:
// LOGGING
LoggingOutInterceptor loi = new LoggingOutInterceptor();
loi.setPrettyLogging(true);
LoggingInInterceptor lii = new LoggingInInterceptor();
lii.setPrettyLogging(true);
Using the Dispatch API can be tricky. I haven't tried it with SOAPMessage,
so I'm not sure if WS-Security works there or not. I've added two examples
though to show how to use the Dispatch API with Signature using payload:
Hi Arnaud,
This seems like an oversight to me. Can you open an issue on the JIRA site
[1]?
In Liberty, we test CXF 3.2.X with Servlet 4.0, but we also repackage the
modules which ends up re-writing the bundle manifests. I think we can make
this work for everybody by incrementing the
Hello,
Osgi application using cxf cannot be deployed on tomcat 9 because osgi
manifest exclude servlet 4.0. Are there any reasons for that ?
Are there any plan to support Servlet 4.0 api ?
Regards,
Arnaud
I do actually get the message on the console, but its all run together, no
new lines or indentation.
Is that what the pretty part would do if i had it going?
--
Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
