Re: Swagger2feature / 3.1.12 (DOSGI)

Hi Sergey I just reforked the master branch (after commit 3b4ed05b1217040ead101fb14c0441d41241f32d ), apparently I failed doing so.. I will try 3.1.14-SNAPSHOT instead.. On 26 Oct 2017 16:20, "Sergey Beryozkin" wrote: > As I said, I've added a check there, try

Re: CXF wsdl2java generates SOAP 1.1 message

I figured this out. I am using a Grails plugin and it had a property to set the SOAP version to 1.2. proxyFactoryBindingId = "http://schemas.xmlsoap.org/wsdl/soap12/; The plugin checks if the value for property proxyFactoryBindingId contains the string "soap12" and if it does it sets the message

Re: Swagger2feature / 3.1.12 (DOSGI)

As I said, I've added a check there, try 3.1.14-SNAPSHOT Sergey On 26/10/17 13:09, nino martinez wael wrote: okay, I have what are happening.. First call are spring that sets the host property.. Immediately after this, the following happens: AbstractSwaggerFeature.initialize:67 are being

Re: Swagger2feature / 3.1.12 (DOSGI)

Hi again I've been stepping through the code, and something are definitely wrong. All other properties set in the app context xml have been processed and set in the swagger 2 feature and are acting logical.. BUT the HOST property are 0.0.0.0:9000 on initialization.. Which seems strange, I'll

Re: fediz production

comments below On 26/10/2017 13:46, Colm O hEigeartaigh wrote: Are you using Java 9? If so please try with Java 8 instead. The warnings should be harmless, however I haven't tested Fediz with Java 9. i am using openjdk 1.8.0.151 "when i first connect with fedizhelloworld it pops up a box

Re: fediz production

Are you using Java 9? If so please try with Java 8 instead. The warnings should be harmless, however I haven't tested Fediz with Java 9. "when i first connect with fedizhelloworld it pops up a box asking for a certificate." - can you reproduce this with a test-case? It sounds as if you are not

Re: fediz production

Hi Colm, I am not sure that would be very easy to provide a test case? Everything was working fine on localhost with the test certificates. Testing on production is completely different using letsencrypt certs and having to change lots of configuration files in the code? You would be

Re: fediz production

Could you create a test-case and upload it to github somewhere + I will take a look? Colm. On Wed, Oct 25, 2017 at 10:39 PM, Matthew Broadhead < matthew.broadh...@nbmlaw.co.uk> wrote: > Thanks for pointing me in the right direction. > > basically what the documentation lacks is that the

Re: In the java_first_jaxws sample of cxf there are no SayHi and SayHiResponse types.

So why is the wrapper type SayHi in java_first_jaxws not needed and in wsdl_first the wrapper type GetCustomersByName is needed? Thanks! On Thu, Oct 26, 2017 at 9:49 AM, Eric J. Van der Velden < ericjvandervel...@gmail.com> wrote: > Thanks. But I do not understand it 100%. In the wsdl_first

Re: In the java_first_jaxws sample of cxf there are no SayHi and SayHiResponse types.

Thanks. But I do not understand it 100%. In the wsdl_first sample there are generated: GetCustomersByName (and GetCustomersByNameReponse). I create the WAR with GetCustomersByName.class in WEB-INF/classes, deploy it in Tomcat and it works. Now I remove GetCustomersByName.class and restart Tomcat.