.
- Ursprüngliche Mail -
Von: "Roberto Cortez"
An: users@tomee.apache.org
Gesendet: Donnerstag, 27. Dezember 2018 17:09:05
Betreff: Re: ActiveMQ websocket transport in TomEE 7
Hi Thomas,
Yes, using a standalone server is an option.
I think that if you manage to just include the Jetty li
ll JSR356
> implementation.
>
> I think that using a standalone activemq server as a proxy is my only
> remaining option.
>
> - Ursprüngliche Mail -
> Von: "Roberto Cortez"
> An: users@tomee.apache.org
> Gesendet: Montag, 24. Dezember 2018 13:29:2
Impl.java:43)
> ~[?:1.8.0_162]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
> at
> org.apache.openejb.resource.activemq.ActiveMQFactory.createBroker(ActiveMQFactory.java:122)
> ~[?:?]
> ... 21 more
>
> And if i add the ja
)
~[?:?]
... 21 more
And if i add the jar file to the lib folder the aforementioned error occurs.
- Ursprüngliche Mail -
Von: "Roberto Cortez"
An: users@tomee.apache.org
Gesendet: Freitag, 21. Dezember 2018 23:48:39
Betreff: Re: ActiveMQ websocket transport in TomEE 7
Hi Thomas,
Can you please detail what dependencies did you add?
Cheers,
Roberto
> On 20 Dec 2018, at 16:31, Thomas Butz wrote:
>
> I'm currently trying to setup the ActiveMQ websocket transport for our
> applicationserver (TomEE 7.0.4)
> So far i've added all needed dependencies but jettys
I'm currently trying to setup the ActiveMQ websocket transport for our
applicationserver (TomEE 7.0.4)
So far i've added all needed dependencies but jettys
ServletContainerInitializer annotations seem to cause problems:
2018-12-20 16:14:30,664 [localhost-startStop-1] ERROR
