RE: Dynamically changing endpoints

Hi, One option is set BindingProvider.ENDPOINT_ADDRESS_PROPERTY in request context: final Greeter port = service.getGreeterPort(); BindingProvider provider = (BindingProvider)port; provider.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, address);

Re: fediz production

Thanks for your help Colm.  I now have it working using the production certificate by following this example https://stackoverflow.com/a/2141229/3052312 to export the pems into jks files. but in the end i also had to copy idp-ssl-key.jks and idp-ssl-trust.jks into webapps/idp/WEB-INF/classes

Re: fediz production

sec:keyStore supports either JKS or PKCS12 keystores. There is also a sec:certStore that works with PEM files, but only for TrustStores I think. As a workaround you can just use the Java keytool command to import your PEM key/cert into a JKS keystore. > this document

Re: fediz production

this document http://svn.apache.org/viewvc/cxf/fediz/trunk/examples/samplekeys/HowToGenerateKeysREADME.html?view=co has idp-ssl-server.jks but no idp-ssl-key.jks. On 23/10/2017 17:11, Colm O hEigeartaigh wrote: I haven't used the APR connector. The following works for me in the tests, perhaps

Re: fediz production

Hi Colm, is there any way for sec:keyStore to be pointed at a pem certificate instead of a java keystore?  where is the doumentation for sec:keyStore? Matt On 23/10/2017 17:11, Colm O hEigeartaigh wrote: I haven't used the APR connector. The following works for me in the tests, perhaps you

Re: fediz production

I haven't used the APR connector. The following works for me in the tests, perhaps you could duplicate this config and get it working first before switching over to the APR connector: Yes you will need to specify the truststore and keystore in cxf-tls.xml to communicate with the STS from the

RE: [+SPAM+]: Re: [+SPAM+]: Re: How to setup ActiveMQ in TomEE to not use persistence for JMS ?

Hello Romain, Finally, with the following settings in tomee.xml: BrokerXmlConfig = broker:(tcp://localhost:61616)?useJmx=falsepersistent=false ServerUrl = vm://localhost In the logs I have: 23-Oct-2017 14:28:59.895 INFO [main]

Re: [+SPAM+]: Re: How to setup ActiveMQ in TomEE to not use persistence for JMS ?

2017-10-23 12:17 GMT+02:00 COURTAULT Francois : > Hello Romain, > > Sorry to haven't found this by myself :-( > > In my application, I have an MDB and in the log, I am able to see: > 23-Oct-2017 11:36:02.079 INFO [localhost-startStop-1] >

RE: [+SPAM+]: Re: How to setup ActiveMQ in TomEE to not use persistence for JMS ?

Hello Romain, Sorry to haven't found this by myself :-( In my application, I have an MDB and in the log, I am able to see: 23-Oct-2017 11:36:02.079 INFO [localhost-startStop-1] org.apache.openejb.config.InitEjbDeployments.deploy Auto-deploying ejb MyMDB: EjbDeployment(deployment-id=MyMDB)

Re: Swagger2feature / 3.1.12 (DOSGI)

Thanks, sure, I've added a guard there to avoid auto-setting the host value if it's not null, you can try 3.1.14-SNAPSHOT or 3.2.1-SNAPSHOT now. However, the question remains where '0.0.0.0' comes from in your case, when no host is set, which is a typical scenario, and I can see it is reported

Re: How to setup ActiveMQ in TomEE to not use persistence for JMS ?

& = in xml ;) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-10-23 10:34 GMT+02:00 COURTAULT Francois : > Hello Romain, > > Get it I think :-) > > In my tomee.xml file (which is empty), I have added: > > BrokerXmlConfig =

Re: cxf-java2wadl-plugin java2wadl questions

Hi, I think you'll need to enable the snapshot repositories Sergey On 22/10/17 09:14, Eyal Weingart wrote: Hi Sergey Should i download something manually for the 3.1.14-SNAPSHOT version (and if so how and from where)? Because i'm trying to do it thru the maven build (defining the version of

RE: How to setup ActiveMQ in TomEE to not use persistence for JMS ?

Hello Romain, Get it I think :-) In my tomee.xml file (which is empty), I have added: BrokerXmlConfig = broker:(tcp://localhost:61616)?useJmx=false=false ServerUrl = vm://localhost But when I started TomEE, I got: 23-Oct-2017 10:25:02.708 INFO [main]

Re: How to setup ActiveMQ in TomEE to not use persistence for JMS ?

in WEB-INF/lib it will not work but the previous url was for tomee.xml AMQ adapter and not related to any spring config Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-10-23 9:54 GMT+02:00 COURTAULT Francois : > Hello Romain, > >

RE: How to setup ActiveMQ in TomEE to not use persistence for JMS ?

Hello Romain, Thanks for your answer but my question is more on how to achieve that without using some Spring/ActiveMQ libraries which customizes TomEE distro => requires to copy some jars in TomEE/lib folder. Another solution could be to have those jars inside our application (in

Re: How to setup ActiveMQ in TomEE to not use persistence for JMS ?

Hi Francois, you are right, you can set the broker url to: broker:(tcp://localhost:61616)?useJmx=false=false to disable the persistence and jmx (for instance) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-10-23 9:30 GMT+02:00 COURTAULT Francois

How to setup ActiveMQ in TomEE to not use persistence for JMS ?

Hello, First, it seems that, by default, ActiveMQ in TomEE, in case we use some JMS stuff in our application, uses persistent repository, right ? Second, looking at some ActiveMQ docs, one way to disable persistence for JMS is to : * Have an activemq.xml file with the following setting