i found it
true
On 22/10/2018 19:14, Matthew Broadhead wrote:
eclipse IDE is complaining if i have multiple persistence units and
they contain classes with the same name. e.g.
http://java.sun.com/xml/ns/persistence;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
Hello Roberto,
So if I have understood you well TomEE MP is TomEE Web Profile + MP
specifications, right ?
Best Regards.
-Original Message-
From: Roberto Cortez [mailto:radcor...@yahoo.com.INVALID]
Sent: lundi 22 octobre 2018 18:14
To: users@tomee.apache.org
Cc: d...@tomee.apache.org
eclipse IDE is complaining if i have multiple persistence units and they
contain classes with the same name. e.g.
http://java.sun.com/xml/ns/persistence;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
Hi Francois,
Thank you.
TomEE MP is build from TomEE WebProfile, so it does support Java EE, including
JPA and Concurrency.
Stuff, available in MP Plus, like JMS or JBatch are currently not available in
TomEE MP.
Regarding the error, I’ve only notice them after the release. I suspect that
Hi Francois,
Thank you.
You are correct. TomEE 8 targets Java EE 8, but please note that we don’t have
the TCK, so we cannot say we are fully compliant.
Yes, you are also correct regarding MP.
Cheers,
Roberto
> On 22 Oct 2018, at 01:44, COURTAULT Francois
> wrote:
>
> Hello everyone,
>
>
Hello,
sure! Regarding the runtime, we also have the postgresql driver in
lib, I think that's all. Hibernate is in our WAR for instance.
here's the activemq.xml =>
https://www.dropbox.com/s/ukttiupouyiv779/activemq.xml?dl=0
tomee.xml =>
Hello everyone,
I have performed some comparison between TomEE 8.0.0-M1 Plus and MP.
The average startup time for TomEE 8.0.0-M1 Plus using java 11, on my laptop
with Core i5, SSD and 16 GB of RAM is: 1,303 ms
The average startup time for TomEE 8.0.0-M1 MP using java 11, on my laptop
with
Hello,
we have a tomee+ 7.0.3 installation with activemq, using kahadb as
a persistent message storage. We have an activemq.xml, we plugged it
though :
BrokerXmlConfig = xbean:file:/opt/app/tomee/conf/activemq.xml
in the tomee.xml. The activemq broken runs within TOMEE:
ServerUrl
Hello everyone,
Congratulation for this intermediate release it provides visibility and shows
that you're working on it :)
Could you confirm that TomEE 8 will be Java EE 8 compliant ? Meaning that:
* JAX-RS 2.1
* CDI 2.0
* JSON-P 1.1
* JSON-B 1.0
will be