Thank you for your response. The WSDL suggestion should work for me so I'll progress with that.
The authentication provider looks like it might work for including my custom auth details but I also need to digitally sign the soap request and include that digest value in the soap header. This means I need to add the soap header after the soap body is created and I need to be able to access it from the authentication provider code, is this possible using the approach you suggest? Many thanks, Mike. On Tue, Jun 12, 2012 at 5:38 PM, Florian Müller <f...@apache.org> wrote: > Hi Mike, > > There is no way to change the endpoint after the WSDLs have been read. > But you can download the WSDL, change the URLs and save it to disk. The > WSDL session parameters accept file://... URLs. > > SOAPHandlers are deliberately not supported because they break content > streaming. > If your SOAPHandler only adds SOAP headers, then you can build your own > Authentication Provider [1]. > See the Standard Authentication Provider code [2] how to add SOAP headers > to requests. > > > Florian > > > [2] > http://chemistry.apache.org/java/developing/client/dev-client-bindings.html#OpenCMISClientBindings-CustomAuthenticationProvider > [1] > https://svn.apache.org/repos/asf/chemistry/opencmis/trunk/chemistry-opencmis-client/chemistry-opencmis-client-bindings/src/main/java/org/apache/chemistry/opencmis/client/bindings/spi/StandardAuthenticationProvider.java > > > > Hello, > > > > I've just started using the OpenCMIS libraries to build a client > > application to talk with CMIS repository using SOAP and have run into a > > couple of problems that are detailed below: > > > > 1) Creating a session using a SessionFactory appears to make a call to > the > > specified endpoint to retrieve the WSDL and then use its specified > endpoint > > for subsequent calls. Unfortunately I cannot use the endpoint address in > > the WSDL so would like to override this. Is there an easy way to do this > > please? > > > > 2) My server implements a different authentication mechanism than > > ws-security username/password. Ideally I'd like use some existing > > SOAPHandlers to do this but I'm not sure how to specify a soap handler > > chain, any suggestions on how to do this? > > > > > > Any help or pointers would be greatly appreciated. > > > > > > Many thanks, > > > > Mike. > > > > >
