Re: 7.0.0 release vote

@David: we needed a version >= 5 (think I voted for 5) just to not break auto-tools like maven version comparison etc. Then I guess users desired ee=tomee but when you pointed out this confusion to me I made it clear in a thread. @all: now we had milestones 7.x we need for the same reason a 7.0.0 o

Re: 7.0.0 release vote

Hi all, from a Customers or User perspective i totally agree with using version 2.x and wait with 7.x for the EE compliance. Thats pretty straight forward David. That would not confusing me. Eduard Matej schrieb am Di., 3. Mai 2016 um 07:08: > Hi all. Not developer. But I also think jumping to

Re: 7.0.0 release vote

Hi all. Not developer. But I also think jumping to 7.x for no reason will only confuse everyone. If ee7 will not be provided like 98 - 99 % compliant. Then it would really be better to maybe just go 2.x route. I think already now people that choose Tomee, dont really care about being 100% compliant

Re: 7.0.0 release vote

> On May 2, 2016, at 5:05 AM, Romain Manni-Bucau wrote: > > Fully agree that's why it has been stated tomee 7 != javaee 7. My memory of that vote was we intentionally aligned the TomEE version number specifically to align to the Java EE version number and further that it would not be changed

Re: TomEE 1.7.x on Java8

I'll have a look at the fix this evening. No rush for this... yet ;-) On 2 May 2016 at 15:54, Romain Manni-Bucau wrote: > if it helps: there is a system property for that in the JVM to revert to > the old sort algo, should solve it. Also think it has been fixed further on > 7.x branch. > > > Rom

Re: TomEE 1.7.x on Java8

if it helps: there is a system property for that in the JVM to revert to the old sort algo, should solve it. Also think it has been fixed further on 7.x branch. Romain Manni-Bucau @rmannibucau | Blog | Github

Re: TomEE 1.7.x on Java8

OK, wasn't sure. So now I have an issue. It's maybe an app issue as it is only one app from 85, but feel like TomEE should cope with this. https://issues.apache.org/jira/browse/TOMEE-1795 Will post more info when available. Andy. On 2 May 2016 at 15:21, Romain Manni-Bucau wrote: > Hi Andy, >

Re: TomEE 1.7.x on Java8

Hi Andy, yes we do for default distributions Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn | Tomitriber | JavaE

TomEE 1.7.x on Java8

Are we supporting TomEE 1.7.x on Java8? Andy. -- Andy Gumbrecht https://twitter.com/AndyGeeDe http://www.tomitribe.com

Re: 7.0.0 release vote

I'm not sure if you're interpretting it as hibernate ORM is AL or not, but ORM is LGPL. OGM and search are also LGPL. Bean validation is pretty much the only ALv2 component. On Mon, May 2, 2016 at 8:31 AM Andy Gumbrecht wrote: > Yep, misleading use of the word 'OR' on this page - > http://hibe

Re: 7.0.0 release vote

did the same and got an enthousistic moment, didnt last :( Romain Manni-Bucau @rmannibucau | Blog | Github | LinkedIn | Tomitriber

Re: 7.0.0 release vote

Yep, misleading use of the word 'OR' on this page - http://hibernate.org/community/license/ - "Hibernate projects are licensed under either the LGPL 2.1 or the ASL 2.0" On 2 May 2016 at 14:05, Romain Manni-Bucau wrote: > 2016-05-02 14:00 GMT+02:00 Andy Gumbrecht : > > > I still feel we are due a

Re: 7.0.0 release vote

2016-05-02 14:00 GMT+02:00 Andy Gumbrecht : > I still feel we are due another Milestone release until TomEE is a little > closer to the mark. There needs to be a really strong statement as to what > is available and what is not. There has already been some negative feedback > from power users that

Re: 7.0.0 release vote

I still feel we are due another Milestone release until TomEE is a little closer to the mark. There needs to be a really strong statement as to what is available and what is not. There has already been some negative feedback from power users that expected more, and were disappointed to find missing

Re: 7.0.0 release vote

Some JAX-RS tests are using JPA 2.1 features which is not supported yet. From: John D. Ament To: dev@tomee.apache.org Sent: Monday, May 2, 2016 12:11 PM Subject: Re: 7.0.0 release vote On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau wrote: > Not portable test, jpa on not jpa test

Re: 7.0.0 release vote

Fixed several in my fork - guess it has been merged but there was too much issues to fix them all alone. The build output shows what it is generally - excepted when the tests are not passing at all like angular example was. Le 2 mai 2016 13:11, "John D. Ament" a écrit : > On Mon, May 2, 2016 at 2

Re: 7.0.0 release vote

On Mon, May 2, 2016 at 2:44 AM Romain Manni-Bucau wrote: > Not portable test, jpa on not jpa tests etc. We pass really more tests > AFAIK. Could you elaborate on that a little? What is not portable? If you want to raise issues in our ticket system please feel free: https://github.com/javaee-sa

Aw: Re: Container has suffered a SystemException

Hallo and Thank you!! Now I see: The problem has nothing to do with TomEE. It is a problem on the client side and how I mange the connection. Ingo > Gesendet: Montag, 02. Mai 2016 um 09:09 Uhr > Von: "Romain Manni-Bucau" > An: "dev@tomee.apache.org" > Betreff: Re: Container has suffered a

Re: Container has suffered a SystemException

Hi did you tune tomee.security.identity.schedule and tomee.security.identity.timeout? Defaults are 1mn (6 - value in ms) and 30mn (180 - value in ms) and can lead to that if second value is reached without interactions with the logged in session (remote ejb). Romain Manni-Bucau @rmannibu