I think this is just a case of encoding the ampersand in the broker URL:

& = &

Andy.

On 2017-10-23 10:34, COURTAULT Francois <francois.courta...@gemalto.com> wrote: 
> Hello Romain,
> 
> Get it I think :-)
> 
> In my tomee.xml file (which is empty), I have added:
> <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter">
>         BrokerXmlConfig =  
> broker:(tcp://localhost:61616)?useJmx=false&persistent=false
>         ServerUrl       =  vm://localhost
>   </Resource>
> 
> 
> But when I started TomEE, I got:
> 23-Oct-2017 10:25:02.708 INFO [main] 
> org.apache.openejb.config.ConfigurationFactory.init TomEE configuration file 
> is ' C:\Users\.....\target\apache-tomee\conf\tomee.xml'
> 23-Oct-2017 10:25:02.736 SEVERE [main] 
> org.apache.openejb.OpenEJB$Instance.<init> OpenEJB has encountered a fatal 
> error and cannot be started: Assembler failed to build the container system.
>  org.apache.openejb.OpenEJBException: Unable to read OpenEJB configuration 
> file
> at C:\Users\...\target\apache-tomee\conf\tomee.xml: The reference to entity 
> "persistent" must end with the ';' delimiter.
> 
> Any idea ?
> 
> Best Regards.
> 
> -----Original Message-----
> From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> Sent: lundi 23 octobre 2017 09:56
> To: users@tomee.apache.org
> Cc: us...@cxf.apache.org
> Subject: 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 <francois.courta...@gemalto.com>:
> > 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 WEB-INF/lib): do you know if it will work ? (avoid TomEE
> > customization except for activemq.xml and tomee.xml)
> >
> > Best Regards.
> >
> > -----Original Message-----
> > From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> > Sent: lundi 23 octobre 2017 09:33
> > To: users@tomee.apache.org
> > Cc: us...@cxf.apache.org
> > Subject: 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&persistent=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 
> > <francois.courta...@gemalto.com>:
> >> 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 <broker 
> >> persistent="false" ....
> >>
> >> *         Have a tomee.xml file which refers the activemq.xml.
> >>
> >> The issue I have is that, for TomEE/ActiveMQ to read these files, we have 
> >> to use some Spring libraries like activemq-spring.jar either in TomEE/lib 
> >> (preferred way, right ?) or war WEB-INF/lib.
> >>
> >> So, the question is: does it exist another way to disable persistence for 
> >> JMS without having to use some Spring  libraries ?
> >>
> >> Best Regards.
> >> ________________________________
> >> This message and any attachments are intended solely for the addressees 
> >> and may contain confidential information. Any unauthorized use or 
> >> disclosure, either whole or partial, is prohibited.
> >> E-mails are susceptible to alteration. Our company shall not be liable for 
> >> the message if altered, changed or falsified. If you are not the intended 
> >> recipient of this message, please delete it and notify the sender.
> >> Although all reasonable efforts have been made to keep this transmission 
> >> free from viruses, the sender will not be liable for damages caused by a 
> >> transmitted virus.
> > ________________________________
> >  This message and any attachments are intended solely for the addressees 
> > and may contain confidential information. Any unauthorized use or 
> > disclosure, either whole or partial, is prohibited.
> > E-mails are susceptible to alteration. Our company shall not be liable for 
> > the message if altered, changed or falsified. If you are not the intended 
> > recipient of this message, please delete it and notify the sender.
> > Although all reasonable efforts have been made to keep this transmission 
> > free from viruses, the sender will not be liable for damages caused by a 
> > transmitted virus.
> ________________________________
>  This message and any attachments are intended solely for the addressees and 
> may contain confidential information. Any unauthorized use or disclosure, 
> either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for 
> the message if altered, changed or falsified. If you are not the intended 
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free 
> from viruses, the sender will not be liable for damages caused by a 
> transmitted virus.
> 

Reply via email to